Legacy handset configuration

Legacy handset configuration SearchSearch
Author Message
Xavier Berger
New member
Username: Xberger

Post Number: 3
Registered: 10-2006
Posted on Thursday, January 25, 2007 - 02:28 pm:   

Hi,

I'am configuring NowMMSC for one of my customer.
This customer has configured all its user in MMSC user database. There MSISDN have this format: +123*.
In this country, there is an other operator so, we assume that MSISDN starting with +123 but not provisionned in MMSC user database are form the other operator. We had added a route to operator2 MMSC with the filter +123*.

Now, we want to configure legacy handset using the MMS to SMS Web Link feature of MMSC.

What kind of filter should we configure in Routing page for legacy handset?

If we configure +123*, we may have some conflict in route and send SMS to operator2 users instead of forwarding MMS.

Thanks for your help,

Xavier Berger
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6893
Registered: 10-2002
Posted on Tuesday, January 30, 2007 - 09:36 pm:   

Hi Xavier,

There are no easy answers to this dilemma if number portability exists within the country.

If number portability does not exist, then it is easy, because you can define all of the prefixes in the routes (e.g., +123xx*,+123xy*,+123yy*)

If the MMSC user account exists locally, NowSMS will always ignore any defined route. So you can define a route for the "convert to SMS with web link" that defines all of the current operator's prefixes. If a user is already registered with the MMSC through auto-registration, they will receive it as an MMS instead of going through this route.

If number portability does exist, then the only solution is to provide an HTTP callback that NowSMS can use to determine which route is to be used. Each time the MMSC needs to route a message, it calls this HTTP callback to tell it which route to use.

There is a good description of this callback here:

http://support.nowsms.com/discus/messages/485/18159.html

I should mention that the callback is not performed if the user is in the "MMSC Users" list of the MMSC.

-bn