One MMSC for users in multiple countries

One MMSC for users in multiple countries SearchSearch
Author Message
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1444
Registered: 08-2008
Posted on Thursday, November 19, 2009 - 05:28 pm:   

This question came in via e-mail support, but it may be of interest to others who are using a single MMSC to support users in multiple countries:


A few weeks ago we opened a support ticket asking how to include "+" sign in our users at the from field(for reference, the ticket is: XXXXXXXX) the conclusion on this was to add:

MSISDNHeaderDefaultCountryCode=503

to our MMSC.ini config file.

But in this server we have Honduras en El Salvador users, so the Honduras users are getting th "+503" in from of their countrycode(504), this is not a problem at this moment, since it is only on the from header.

The issue es faced when an Honduras user send a message to other Honduras user without using the countrycode:-(i.e 504899758308 -->89688512)

Here is a log that sets the idea more clearly:

2009-11-12 07:15:36,MMSIN,172.26.144.254,+50350489758308,+50389688512,20091112/07/23038478, SAR-+50389688512-57-2-1.req,11125

The MMS is adding "+503" at the destination address, hence the message will never be deliver to the destination.

Even if we do have a valid SMPP connection using the route "89*"

Here is a snip of the configuration file for this:
> > [SMPP - 172.27.161.193:5000]
> > SMPPVersion=v3.4
> > UserName=MMS
> > Password=MMS
> > SenderAddress=12345678912
> > SenderAddressOverride=Yes
> > Receive=No
> > ReceiveMMS=No
> > UseSSL=No
> > LongSMSAlt=Yes
> > KeepAlive=300
> > Route1=+50489*
> > Route2=89*
> > RoutePrefOnly=Yes

As you can see on the log, the message is not routed there, and instead the "+503" is being added, and then the NowSMS might try to deliver the message locally.

The main problem is that even if we have a SMPP route to catch all 89* numbers NowSMS is taking those numbers as invalid for that route and then try to send those messages via Internal MMSC Users.

There is also another question from user:

MSISDNHeaderDefaultCountryCode=503 is supported just on the global [MMSC] options ?, or can be added to the [Outbound MMS Routing] options ¿
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1445
Registered: 08-2008
Posted on Thursday, November 19, 2009 - 05:31 pm:   

And the solution:

As the MMSC is servicing users in more than one country, I would suggest removing the MSISDNHeaderDefaultCountryCode=503 setting.

Instead, add the following setting under the [MMSC] header of MMSC.INI:

MSISDNHeaderPrefixConvert=503:+503,504:+504

The above setting is more appropriate for your configuration.

Here is what it will do.

When the MSISDN header for a received message is from 504899758308, it will see that "504" is a prefix listed in the MSISDNHeaderPrefixConvert section, and it will convert "504" to "+504", making the sender address "+504899758308".

If this user tries to send to "89688512", NowSMS will recognise that it is a local number, and convert it to "+50489688512", applying the country code to the recipient address, based upon the country code of the sender.

Similar logic will be applied for submissions from "503" phone numbers.

The MSISDNHeaderPrefixConvert setting is applied when translating the sender MSISDN header as received from the WAP gateway. In this case, the MMSC needs these conversion rules to be applied to know that the numbers to full international format.