MT MMS using NowSMS and Agilent 8960

MT MMS using NowSMS and Agilent 8960 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through April 21, 2010 » MT MMS using NowSMS and Agilent 8960 « Previous || Next »
Author Message
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7886
Registered: 10-2002
Posted on Friday, February 05, 2010 - 01:47 pm:   

The following was received via e-mail, however since there is limited information available about using NowSMS with the Agilent 8960, I want to move this discussion here so that others with similar questions can benefit.



We have downloaded the NowSMS for evaluation. We are developing a reference platform for CDMA environment and as part of it, we have to test various scenarios including MT MMS, MO MMS and End to End MMS.

The location of development does not have any CDMA network, we are trying to simulate with NowSMS and Agilent 8960. NowSMS is has been configured for HTTP SMSC and also enabled MMSC. We are able to test MT and MO SMS with this setup.

We are also able to test MO MMS, but we are having issues for MT MMS. When we send MMS Message from the NowSMS web browser, the Agilent discard it by saying "HTTP request ignored; Request Parameters Out Of Range". We are not sure why Agilent is discard it. We had checked the Agilent documentation and followed all the steps. So in way, we are 95% sure that Agilent setup is fine.

We also had look at following article which gave us an indication that MT MMS will not work in NowSMS with HTTP SMSC. But we would like more inputs on this.

If its possible, we would like your inputs to get this setup complete. Once this done, our management will go ahead with the plan to guy the NowSMS software.

We have setup the HTTP SMSC with following URL template

ServerType: Custom
URL Template Binary: /sms/send?PhoneNumber=@@PhoneNumber@@&Binary=1&Data=@@Data@@&UDH=@@UDH@@&pid=@@p id@@&dcs=@@dcs@@&InboundMessage=Yes

We have tried "Direct Delivery" and "WAP PUSH with Web link" as Default Routing options.

Any pointers on this would be greatly appreciated.

Thanks and Best regards

Much of the information that is available from past discussions here is GSM oriented, or if it is CDMA based, dates back to earlier than 2006. In 2006, we worked with a group at Agilent to facilitate CDMA test lab environments.

Our notes on this effort can be found at the following link:

That link explains the problems/issues with MMS and WAP Push in CDMA environments.

There are three core issues that cause problems for MMS notifications in CDMA environments.

1.) The SMSC must set the "Teleservice" value of the MMS notification message to "WAP". (There is no equivalent requirement in GSM environments.)

2.) Most MMS notifications are too large to fit into a single message. The WAP specifications dictate that the same SMS message ID must be used for all segments of a multipart message. (In GSM environments, this is handled via user data header in the message submission. In CDMA environments, only the SMSC can generate this message ID.)

3.) The WAP Push PDU format is different in CDMA environments. (In GSM it is encoded in the user data header, in CDMA it is part of the user data.)

For CDMA mobile operator environments, the solution is relatively straight-forward ... the SMPP protocol is used, with a protocol option known as "WDP Adaptation". That is described more in the link that I referenced above.

Alternatively, if the operator already has a WAP Push Proxy Gateway deployed on their CDMA network, the NowSMS MMSC can interface through the existing PPG (, instead of using SMS directly.

However, if you're using an HTTP connection to an SMSC, it's not so easy.

The solution that we developed involves adding an additional HTTP URL template that is used only when sending MMS notification and WAP push messages.

You'll see this described toward the bottom of the link that I referenced above.

As this is a very specialised requirement for a limited number of configurations, it can only be manually configured via SMSGW.INI settings, specifically the CDMATemplateWAP= parameter.

To address #1, this template setting would normally include a parameter to set the CDMA teleservice value to WAP. For the Agilent 8960, I believe this parameter is "&TELESERVICE=WAP".

To address #2, you can either follow the advice in the document to try to shorten the MMS notification so that it will fit into a single message, or there is a @@CDMAWAPMMTS@@ variable that can be used in the template. We set this value to 1 for all message parts except the last part of a message, for which it is set to 0. An HTTP SMSC implementation can use this to know that it needs to keep using the same CDMA Message ID until the value is 0. For the CDMA 8960, there is an MMTS variable that corresponds to this. Your URL template should include "&MMTS=@@CDMAWAPMMTS@@".

To address #3, instead of using @@DATA@@ or @@TEXT@@, there is a @@CDMAWAPPDU@@ variable which tells NowSMS to build a raw WAP Push PDU in CDMA format. For the 8960, you would include "&DATA=@@CDMAWAPPDU@@" in the URL template ... also "&MSGENCODING=Octet" to indicate that the data is binary.

Agilent posted their GSM URL templates for NowSMS here:

DCS, PID and UDH have no meaning in CDMA environments, so do not include them in your templates. I would suggest the following:

Template Text URL:


Template Binary URL:

/sms/send/?DATA=@@UDH@@@@Data@@&MSGENCODING=OCTET&SENDER=@@Sender@@&garbage=@@ph onenumber@@

(Note: There is some question as to what type of binary data you would be sending in a CDMA environment, other than MMS notifications and WAP Push which will be handled by a separate template. If you want to try using EMS, you could try adding "&TELESERVICE=WEMT" to that URL, but based upon the documentation that I have, I'm not sure that the 8960 supports this teleservice.)

Finally, the following URL template would need to be manually configured in the SMSGW.INI file, under the appropriate [HTTP - server:port] section header for the HTTP SMSC definition:


(The discussion board software may have inserted blanks into the above, which should not be included in the actual configuration setting.)

All that said ... that's how I think it works. I've never used an Agilent 8960 directly, just remotely provided support for customers that were interfacing NowSMS with it.


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