| Routing SMS to different operators |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Olaf Unregistered guest |
A potential customer want to send SMS-messages to different users from the Now SMS/MMS gateway. Users should pay for receiving the messages. The charge info is included in the message, and the user is charged by their operator. They have CPA agreements with the two real operators here. Each of these real operators are supporting several virtual operators. Their question is how to route the outbound messages to the right operator's SMSC. Even if they have access to subscriber lists, these are often not accurate, due to delayed updates. Users may also switch from one (virtual) operator to another and keep the same phone number. Is there a way for the SMS/MMS gateway to handle this situation? | |||
| Tony Unregistered guest |
You can define the Sender Adress and than you must uncheck "Support any outbound Messages" Than if you send SMS/MMS you must define the variable : Sender=(Your Sender Adress of the what you defined for this SMSC) | |||
| Olaf Unregistered guest |
Thanks. If I understand this correctly, this means that the sender has to know (exactly?) which SMSC to use in order to reach each and every recipient phone number? What will happen if a message is sent to another (incorrect) SMSC? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1056 Registered: 10-2002 |
Hi Olaf, Tony's response explains how you could do it if you had access to an accurate list. But basically, you're right ... there's no good way of handling this. I guess the question is ... what happens if the message is sent to the wrong SMSC? Can you find that out ... does the message get rejected? Is it rejected with a particular error code? In the old days, before interoperability was widespread, there were a number of SMS gateway providers that would try different SMSCs until they found one that would accept it. We haven't really seen this required these days because of interoperability agreements ... but if necessary it would not be very difficult to implement. -bn | |||
