Is NOWSMS decoding proper???? -- urgent plz help bryce

Is NOWSMS decoding proper???? -- urgent plz help bryce SearchSearch
Author Message
mayur
Unregistered guest
Posted on Tuesday, December 28, 2004 - 07:40 am:   

Hi bryce
I had sent the folling MMS-Send-Req to now sms

8C 80 ….. X-Mms-Message-Type is encoded as 8Ch, m-send-req as 80h.

98 30 31 32 ….. 98h means Transaction-ID, with value 012….

8D 92 8Dh is MMS-Version, and 90h corresponds to value 1.2

89 18 80 30 2b 33 31 34 ….

89h is From, 18h the length of the value, 80h is address-present-token, and the value is
+314

But I am receving Send_cnf with status as MMS message format corrupted
But when I remove 80 which means address token present it accepts properly
But according to the standards this field has t o be present in from field ..
According to std of from field:
From-value = Value-length (Address-present-token Encoded-string-value | Insert-address-token)
Address-present-token = <Octet 128>
Insert-address-token = <Octet 129>

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

Post Number: 3805
Registered: 10-2002
Posted on Thursday, December 30, 2004 - 05:22 pm:   

Hi Mayur,

I'd need to see the complete PDU, preferrably from the NowSMS MMSCDEBUG.LOG, in order to answer your question.

Is 18h the length of the phone number, or does that length include the length of the phone number and address-present-token?

The length specifies the length of the field, not just the phone number. So if the phone number is 18h bytes, the length must be 19h to include the 1 byte for the address-present-token.

(Also note that NowSMS is going to ignore the value in the from field and re-write it. Further note that many operator MMSCs will reject or mysteriously lose an MMS message if the From-value includes an address ... they expect From-Value to always be Insert-address-token ... and you must encode this as 89 01 81.)

-bn