HTTP and modem interfaces to SMSC send different content

HTTP and modem interfaces to SMSC send different content SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 02, 2006 » HTTP and modem interfaces to SMSC send different content « Previous || Next »
Author Message
Yew Thean Hoo
New member
Username: Theanhoo

Post Number: 1
Registered: 01-2006
Posted on Saturday, January 07, 2006 - 04:09 pm:   

I have both a GSM modem and a connection via HTTP to a bulk SMS provider. The problem is an MMS message sent via the HTTP interface doesn't show up on my phone, where the same message does when sent using GSM modem. When using the HTTP interface, the receiving phone just wakes up without showing any new MMS messages, as if the phone receives the WAP push but discards it due to some errors.

I notice the arriving content differs when sent over different interfaces, noticably there is "Encoding-Version 1.3" when using HTTP, and none when using a GSM modem. Perhaps there are other differences, maybe something that could cause the problem I am facing?

I am using NowSMS v5.51a.

Any help is much appreciated.

Thanks in advance.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5414
Registered: 10-2002
Posted on Friday, January 13, 2006 - 06:49 pm:   

Are you able to send regular WAP push messages successfully via the bulk SMS provider?

Assuming that you are ... next, try to send a WAP Push message with more than 140 characters in the text field, so that it is forced to go out as a 2 part message.

Does that work ok?

It would also be curious to send the MMS notification out via the bulk SMS provider to your GSM modem, so that we could see what comes back in to the GSM modem. (It would probably be best to enable the SMSDEBUG.LOG so that we can see the raw message that comes in for the MMS notification.)

I'm not sure what the "Encoding-Version: 1.3" difference is referring to. That is an HTTP header that might be present when a device retrieves an MMS message via a WAP proxy. But I don't really understand why this would be a difference in the two scenarios, because it sounds like in the HTTP SMSC scenario, the receiving device is not getting as far as retrieving the MMS message (which is when you might see this header).

-bn

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