Abnormal decoding WAP push message

Abnormal decoding WAP push message SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Abnormal decoding WAP push message « Previous || Next »
Author Message
Stanley
Unregistered guest
Posted on Monday, March 01, 2004 - 05:20 am:   

I have received a MMS notification via WAP push mesasge as follow. The 2nd SMS is incorrectly decoded, could you tell the cause of this strange case. Maybe the error ocurrs in the radio path or the modem itseft. I am using sonyericsson GC75 GPRS modem.

13:32:27:196 [2] ModemReceiveMessages: Decoding received message index 2 from message storage ME
13:32:27:196 [2] ModemReceiveMessages: SMSC address len = 7
13:32:27:196 [2] ModemReceiveMessages: SMSC Address = +85290100001
13:32:27:196 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
13:32:27:196 [2] ModemReceiveMessages: User Data Header is present
13:32:27:196 [2] ModemReceiveMessages: Sender address len = 16
13:32:27:196 [2] ModemReceiveMessages: Sender Address = 9855566610100000
13:32:27:196 [2] ModemReceiveMessages: PID = 00
13:32:27:196 [2] ModemReceiveMessages: DCS = 04
13:32:27:196 [2] ModemReceiveMessages: Anticipated user data length = 109
13:32:27:216 [2] ModemReceiveMessages: Binary message = 0C0804B707020105040B8423F03B06396170706C69636174696F6E2F766E642E7761702E6D6D732D 6D65737361676500AF84456E636F64696E672D56657273696F6E00312E3400B4878C829832373733 303338008D90891D803C5374616E6C65795F536F40686B736D6172746F
13:32:27:216 [2] ModemReceiveMessages: AT+CMGD=2

13:32:27:937 [2] ModemReceiveMessages:
OK

13:32:27:937 [2] ModemReceiveMessages: Decoding received message index 3 from message storage ME
13:32:27:937 [2] ModemReceiveMessages: SMSC address len = 7
13:32:27:937 [2] ModemReceiveMessages: SMSC Address = +85290100001
13:32:27:937 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
13:32:27:937 [2] ModemReceiveMessages: User Data Header is present
13:32:27:937 [2] ModemReceiveMessages: Sender address len = 16
13:32:27:937 [2] ModemReceiveMessages: Sender Address = 9855566610100000
13:32:27:937 [2] ModemReceiveMessages: PID = 00
13:32:27:937 [2] ModemReceiveMessages: DCS = 04
13:32:27:937 [2] ModemReceiveMessages: Anticipated user data length = 102
13:32:27:957 [2] ModemReceiveMessages: Binary message = 0C0804B707323A3033008A808E024BA88805810302A2FF83687474703A2F2F3230322E3134302E39 362E39322F7365727665723F6D6573736167652D69643D3237373330333800
13:32:27:957 [2] ModemReceiveMessages: AT+CMGD=3

13:32:28:057 [3] ThreadProcessInboundSMS: Processing 40417666.in...
13:32:28:067 [3] ThreadProcessInboundSMS: SAR Segment Reference = B707, Count = 2, Current = 1
13:32:28:097 [3] ThreadProcessInboundSMS: Processing 40417667.in...
13:32:28:107 [3] ThreadProcessInboundSMS: SAR Segment Reference = B707, Count = 50, Current = 58
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2040
Registered: 10-2002
Posted on Wednesday, March 10, 2004 - 12:23 am:   

Hi Stanley,

Apologies for the delay in getting back to you on this, but I can definitely confirm that the received message is corrupt.

The user data header (UDH) of the message appears to be corrupt, and I have the same interpretation decoding the message manually.

In fact, studying it in some more detail, it appears that 31 bytes are missing from the mesasge.

As the GC75 is a PC card modem, I find this to be very unusual. On past occasions with external modems, I have suggested replacing the modem cable...but you can't do that with a PC card.

It may be worth trying to lower the speed that is configured for the modem driver in the Windows Control Panel ... Phone and Modem Options.

-bn

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