Jump to:
| Project: | SMS Framework |
| Version: | 6.x-2.x-dev |
| Component: | Core Framework |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This is just an idea to take the smsframework to another level. I ran into a problem where by I needed to have two clickatell accounts - some background, most of our users were Australian but we do have a reasonable number from New Zealand and also a handful from other countries or some that travel to other countries.
The problem was that in Australian when people port (transfer) their number from one carrier to another it stuffs up clickatell's ability to route calls and they had to provide us with an account that gets around this problem but only works for Australian numbers.
I have also help launch a new site that is specifically for the US market and Clickatell has the ability ot setup a US profile account and get cheaper rates. The problem is there may be a few users from other countries as well.
I can also see a need to use a more expensive sms services where you are wanting a higher level of service for certain users of the site, or certain types of messages.
So my ideas was that rather then just have a page where you have radio buttons to select the carrier to use for all messages, what if you could dynamically add carriers to this list to allow you to route messages based on certain rules.
When a message is sent it goes it would go down the list and finds the first router where it matches its rules.
The rules could be based on:
* country code
* user roles
* days/times
Each route would specify a carrier and account to use.
What you would end up with is a module that allows for a range of user configurable routing options.
Comments
#1
Just to add to this....
With the recent problems of sending SMS to US numbers via clickatell it has highlighted the need more then ever to have backup solutions in place, particularly when your application relies on the SMS messages. The problem with any backup solution though is that it still requires you to manually switch over to a new service and you only know there is a problem when messages start failing.
Wouldn't it be good if we could try to detect a failed message (a lot of services provide that information) and if there was an alternative service setup on the site we could try routing the message via a different gateway.
This means when one service goes down our messages can keep getting sent without any interruptions to users.
#2
+1 on this. I have Guatemalan users, but many Guatemalan cell phones have been ported from Brazilian phones. So, I have to have one Clickatell account for the ported phones (Clickatell considers them Brazilian numbers, even though the only way to tell is if a message fails to go thru), and one for non-ported phones.