Legacy Terminals

Legacy Terminals SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2004 » Legacy Terminals « Previous || Next »
Author Message
Cris Nevalo
New member
Username: Cris

Post Number: 1
Registered: 05-2004
Posted on Friday, May 14, 2004 - 01:33 pm:   

I have some doubts about the notifications send to legacy terminals.
I sent an MMS to a terminal with WAP/GPRS capabilities but no MMS. I expected to recive an SMS with an URL to notify that an MMS was sent, but I didn´t receive anything.
What happen in the following scenarios:
- Send an MMS to a legacy terminal with WAP/GPRS capabilities (no MMS)?
- Send an MMS to a legacy terminal with only SMS capabilities (not WAP/GPRS)?
- How the MMSC knows that a terminal is a legacy one? it must be provisioned?
- In case provisining is needed, how is it done?

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2612
Registered: 10-2002
Posted on Monday, May 17, 2004 - 02:00 pm:   

Hi Cris,

NowSMS only has the ability to convert an MMS message into a WAP push format that can be read in a WAP browser (i.e., - "Send an MMS to a legacy terminal with WAP/GPRS capabilities (no MMS)?")

However, in order to activate this capability, phones that have MMS capability must be provisioned to the system.

How it works is like this ...

On the "MMSC routing" page, set the "Default Route" to be "Convert MMS to Multimedia WAP Push".

By default, NowSMS will then convert any MMS messages to a standard WAP push format for viewing in a WAP browser.

However, any users that are provisioned in NowSMS will receive MMS messages in the standard MMS message format.

There are several ways that you can provision these MMS accounts, either manually or automatically.

To manually provision MMS accounts, they can be defined on the "MMSC Users" dialog.

There is also a web interface for provisioning these accounts. An administrative interface for adding, deleting and modifying users is available via the HTTP port of the MMSC if an “Admin User” is defined on the MMSC dialog. If an administrative user is defined, then the administrative interface is available by connecting via a web browser to “/ADMIN” on the MMSC HTTP port (e.g.,, and supplying the defined administrative user name and password. The administrative interface provides functionality similar to that described for the “MMSC Users” tab dialog.

There is also an HTTP interface for provisioning these accounts via simple GET commands:


And, the better option is to provision accounts automatically. This is possible if NowSMS can receive MSISDN information from the WAP proxy, as described here:


In this event, NowSMS can automatically provision a user account for MMS the first time a user submits an MMS message through the MMSC.

Unfortunately, legacy terminals with only SMS capabilities (no WAP Push capabilities) are out of luck.

We have considered adding a feature where instead of the multimedia WAP push, a standard SMS link is sent out with a URL pointer to a location that the user can go to and enter their phone number and a code to receive the MMS message in a web browser. Our development team has gone so far as to write out a design for how it would be implemented. But so far, it just hasn't made the cut when we prioritise features. I'm going to see if I can get this bumped up on the priority list, as it would be a nice feature to have (as long as it is not as complicated for end users as some of the systems deployed by other vendors ... part of the reason we have resisted adding this feature is that our discussion boards here would receive several postings a week from people who were trying to receive MMS messages, that were sent via this type of SMS link to a web page, from Vodafone's web site, and there was certainly a lot of confusion surrounding that).

Cris Nevalo
New member
Username: Cris

Post Number: 2
Registered: 05-2004
Posted on Tuesday, May 18, 2004 - 04:13 pm:   

Hi Bryce,
Thanks for your answer. I´ve got another question related to terminals that not support MMS.
When you convert an MMS to multimedia WAP Push, what is received in a terminal that supports WAP Push? Is the Push SL (Service Loading) or SI (Service Indicating)?
Janek Shein
New member
Username: Janek

Post Number: 1
Registered: 04-2004
Posted on Thursday, May 20, 2004 - 12:40 pm:   


Was also curious about the handling of the legacy terminals and ended up here.

But how exactly does the provisioning of the terminals work? Or the information is tied to the MSISDN? What happens if the user changes his terminal?

Is there a possibility to make external lookups for terminal capabilities to another system or has this possibility been ever considered?

And maybe also forwarding the messages to another system (for example user's mailbox) instead of converting to wap push?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2654
Registered: 10-2002
Posted on Tuesday, May 25, 2004 - 04:36 pm:   


The Multimedia WAP Push is Service Indication (SI). Too few terminals support Service Load (SL).

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2655
Registered: 10-2002
Posted on Tuesday, May 25, 2004 - 04:46 pm:   


If MSISDN is provided by the WAP gateway, then the "MMSC Users" list can be automatically updated the first time that a user sends an MMS message through the MMSC.

If a user account appears in the "MMSC Users" list, then NowSMS will always try to deliver the message via MMS, regardless of any other configured "MMSC Routing".

If the user changes his terminal from a device that supports MMS to a device that doesn't support MMS, the system has no way of knowing that.

If the user changes his terminal from a device that doesn't support MMS to a device that does support MMS, the system can provision the account from the MSISDN on the first MMS message submission.

As an alternative to WAP Push, in the next major release, we are planning to add an option to convert to one of those annoying SMS messages instructing the user to go to a web site and enter a phone number and passcode to view the messsage. (I say annoying, because while in theory this is a good idea, it seems to be a great source of frustration to end users.)

We are considering an HTTP based callback interface for routing in the next major release. The idea is that this interface could specify which of the "MMSC Routings" should be used. We hadn't really thought about offering an option that the callback could also convert the phone number to an e-mail address, but that would be a reasonable addition to the interface.


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