Default Route & Additional Route do not work as expected

Default Route & Additional Route do not work as expected SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through August 22, 2012 » Default Route & Additional Route do not work as expected « Previous || Next »
Author Message
Zeeshan Riaz
New member
Username: Zeeshanriaz

Post Number: 12
Registered: 07-2011
Posted on Thursday, February 16, 2012 - 08:06 pm:   

We need your urgent attention regarding MMS delivery;

On MMSC Routing tab, we can set

• Default Route
Direct Delivery (Internal MMSC)
• Additional route
MMStoSMS (WAP Push with weblink)

Having these setting only works with high end handsets which support direct reception of MMS, but low end handsets did not receive any thing, which they supposed to get as we configured on additional route. See MMSC configuration file contents below.

MMSDir=C:\Program Files\NowSMS\MMS-IN

Note that, if we use “Convert to WAP push with WebLink” as default route, it works with all handsets.
Kindly let us know if we are missing anything?

Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3791
Registered: 08-2008
Posted on Thursday, February 16, 2012 - 08:36 pm:   

Hi Zeeshan,

The "UndeliverableRouteToSMS" setting only works with routes of the type "SMS with web link (code)".

That said, if you have been running your MMSC for any length of time, I would caution against enabling this setting. After this setting is applied, it will process all MMS messages that have not been delivered (up to DataRetainDays back), and perform the conversion and send them.

This will include any users that have received the previous "Convert to WAP Push with web link", but that have not bothered to connect to retrieve the message.

This may trigger an unexpected large batch of messages. (And is something we need to change.)

If you want to enable it, I'd recommend these steps:

1.) Define a "SMS with web link (code)" route, and verify that it is working as you want it to by explicitly routing a particular phone number to it before enabling it for the masses. (See

2.) Reduce DataRetainDays to a lower value, such a 3, before enabling this. This will limit the processing of conversions to undelivered/unretrieved messages from the last 3 days. You can set it back to a higher value after this batch of conversions has been sent out.


That said, I don't recommend using UndeliverableRouteToSMS for this purpose, especially in conjunction with setting "Direct Delivery" as the default route.

Your users on low end handsets will likely get a garbage SMS (the MMS notification) before the actual MMS message comes in as an SMS with web link.

Also, 2 minutes is a relatively low timeout. Someone loses coverage in a building, etc. You will have many users receiving MMS messages twice, once as an SMS then as an MMS. (Maybe that is not a problem, just confusion.)

I realize it is confusing, but I personally think the best way is to use one of the "Convert" options as a default route.

Require that users send an MMS first to get automatically provisioned. This is also the best way to confirm that the MMS settings in the subscriber phone are configured properly.

If you use the "SMS with web link (code)" as a default route instead of using WAP Push, you can modify the template that the end user sees. This way the page that prompts them for a code can also include text like "If you are using a phone that supports MMS and would like to receive MMS messages natively, please send an MMS message. MMS message delivery will be configured for your phone number the first time you successfully send an MMS."

That said, most phone are MMS compatible (they just don't always have the settings configured properly). So if you want to use "UndeliverableRouteToSMS", just follow the guidelines above.

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

Post Number: 8016
Registered: 10-2002
Posted on Thursday, February 16, 2012 - 11:47 pm:   

One note to possibly discourage you from using WAP Push.

The iPhone does not support WAP Push messages (Service Indication). That is one of the reasons that we encourage the use of including a link in a text message as an alternative.
Zeeshan Riaz
New member
Username: Zeeshanriaz

Post Number: 13
Registered: 07-2011
Posted on Friday, February 17, 2012 - 01:33 am:   

Thanks for the response.

Now, I have changed the additional route to SMS with web link (code) with following settings;
server address:
port: 80

But when I receive SMS on my handset and try to open a link, it says "pasge cannot be displayed"

Is there anything missing?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3795
Registered: 08-2008
Posted on Friday, February 17, 2012 - 02:06 pm:   

Does resolve to the NowSMS server?

(What is the local host name or IP address setting for the MMSC, as we know it works.)

Is another server using port 80 on that PC? (This is a separate port number from any other port number assignments used in NowSMS.) To troubleshoot ... Change the port number. From a command prompt window, if you issue the command NETSTAT -a it will show you what ports are being listened on. When you change the port number, you can use NETSTAT -a to see if some other service is conflicting with it.

Generally speaking, the idea is that you would be specifying a publicly accessible IP address here, not a private one. The idea is that the recipient may actually be a subscriber of a different mobile operator, not just one of your customers that does not have MMS enabled. For this reason, the service runs on a separate port from other NowSMS services, so that you are only opening up access for this part of the MMSC service, and not all MMSC services.

NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics