SMS Framework 2.x
After starting a patch for providing an extended new hook system in v2 (http://drupal.org/node/442748), I corresponded with Will to start efficient planing of the 2.x branch by introducing some main goals for development. You are welcome to join the discussion and leave proposals.
SMS Framework will be stated "on heavy development" so should not be used on production sites at the moment.
This list might grow in the next days, so feel free to propose new points or comment on existing ones.
- New hook system for sending and receiving messages
hook_sms() - with ops:pre send, send, post send, pre receive, receive, post receive (more in http://drupal.org/node/442748) - Rewrite existing modules to fit new hook system
- SMS as object ($sms)
- Extended gateway handling:
- selectable gateways for different dependencies (country, user account, sms type)
- cost management/logging
- Gateway as object ($gateway)
- overall sms types (like Default, Long message, Flash-SMS, MMS)
- SMS logging and storage
- Testform for simulating sending and receiving sms for test issues
- Automated node creation (sms mapper)
Groups:
Login to post comments
Yes! MMS support :)
I'd like to help work on MMS support. I'm already using SMS Framework to send/receive MMS messages but it did require some custom modules. Here are some related issues: http://drupal.org/node/373307 and http://drupal.org/node/490890
Location based services
I am not a specialist on how the telco's share location with SMS providers, but perhaps others are.
It would be real cool to be able to receive SMS senders location (with all authorisations etc). Either in the inbound SMS or through callbacks.
Are there people who know if there are any industry standards in this regard that we could take into account in the design at least?
I suggest to include this
I suggest to include this feature http://groups.drupal.org/node/21232 .