| MM Notification - How to build |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Nguyen Trong Tho New member Username: Trongtho Post Number: 2 Registered: 01-2004 |
Dear administrator, I am trying to encode a MMS Notification. But there are some things I don't understand. By specification, I built the MMS notification like this: 8C82 - X-Mms-Message-Type=m-notification-ind 9841303100 - X-Mms-Transaction-ID:413031 8D90 - X-Mms-MMS-Version: 1.0 8916802B38343939372F545950453D504C4D4E00 - From: +84997/TYPE=PLMN 8A80 - X-Mms-Message-Class: Persional 8E ? - X-Mms-Message-Size: ? 8805810302A300 - X-MMS-Expiry:... 83687474703A2F2F6D6D732E766965746E616D6E65742E766E2F31323300 X-Mms-Content-Location:http://mms.vietnamnet.vn/123 You pls tell if me my encoding is correct ? And what is the value of the X-Mms-Message-Size field in this case; how is it formatted ? (by definition, it is encoded as long-integer but I not sure about the task). That binary string can be written as follows: 8C8298413031008D908916802B38343939372F545950453D504C4D4E008A808E??8805810302A300 83687474703A2F2F6D6D732E766965746E616D6E65742E766E2F31323300 It means the full size of message is 70 octets (or 0x46). ==> The size of message is 0x0146. Is it true? regards, Tho. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1747 Registered: 10-2002 |
The length for the "From:" field does not seem correct. The transaction-id does not match your text explanation of its contents. The X-Mms-Message-Size header refers to the size of the MMS message, not the notification. Size encoding uses the "long-integer" format defined in WAP-WSP. There is a discussion of this in the following thread: http://support.nowsms.com/discus/messages/12/597.html | |||
| Nguyen Trong Tho New member Username: Trongtho Post Number: 3 Registered: 01-2004 |
thanks, It was my question from some month before. Now I am back to the job (but lost that track). Since MM Notification itself is MMS Message with only headers inside. The X-Mms-Message-Size header contains the size of MMS Message to be fetched by MS from the URL within the Notification. Is that true? Tho | |||
| Nguyen Trong Tho New member Username: Trongtho Post Number: 4 Registered: 01-2004 |
I that reason, I changed the Notification as follows. 8C82 X-Mms-Message-Type=m-notification-ind 983100 X-Mms-Transaction-ID:”1” 8D90 X-Mms-MMS-Version: 1.0 89 10 80 2B3939372F545950453D504C4D4E00965375626A6563743A2054686F2100 From: +84997/TYPE=PLMN 8A80 X-Mms-Message-Class: Persional 8E021FA6 X-Mms-Message-Size:8102 Bytes 88 06 80 044019FE91 X-MMS-Expiry: 83687474703A2F2F3230332E3136322E3136382E3135342F776170707573682F31323300 X-Mms-Content-Location: http://203.162.168.154/wappush/123 Pls check for me if there is something wrong. I sent this binary to mobile phone by SMS with destination and source port are 0x0B84 and 0x23F0, perspectively. On my phone (Nokia), I saw it retrieving MMS but after a while, it stopped and nothing appeared. I do push MMS as shown in this thread: http://support.nowsms.com/discus/messages/12/2193.html When receiving request from URL, I reply with the following information: Content-Type:application/vnd.wap.mms-message Content-Length:<size of mms content> <mms content> Pls correct me. regards, Tho | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1767 Registered: 10-2002 |
That is true. I looked over your notification, and I don't notice anything wrong with it. I also did a telnet fetch of the content from your server, and those headers look fine as well. Unfortunately, as fate would have it, I'm not getting any GPRS on my phone at the moment, so I can't try it on a live device. Hopefully my GPRS signal will come back in the next few hours ... | |||
| Nguyen Trong Tho New member Username: Trongtho Post Number: 5 Registered: 01-2004 |
I received MMS Message successfully  The problem is that I made st wrong in the MMS header (when u fetched it, I had corrected it, so it look fine :D) Thanks for your support, Tho. | |||
| jtaal New member Username: Mmoney Post Number: 1 Registered: 02-2004 |
Hi, I’m trying to understand the structure of a notification MMS message by using the following example: n.mms (89 bytes) a notification for m.mms (27.807 bytes) 8C 82 98 30 30 30 30 30 30 30 30 30 31 00 8D 90 89 16 80 67 6F 6C 64 70 6F 73 74 40 68 6F 74 6D 61 69 6C 2E 63 6F 6D 00 96 47 4F 4C 44 00 8A 82 8E 01 78 88 06 80 04 7A A7 7D 64 83 68 74 74 70 3A 2F 2F 31 32 38 2E 31 33 30 2E 39 30 2E 35 34 2F 67 2F 6D 2E 6D 6D 73 00 I decoded this message and came with this results 8C: X-Mms-Message Type 82: m-notification-ind 98: X-Mms-Transaction-ID 30 to 00: Transaction ID = 0000000001 8D: X-Mms-MMS-Version 90: 1.0 89: From 16: Length 80: Adress-present-token 67 t/m 00: goldpost@hotmail.com 96: Subject 47 - 00: GOLD 8A: X-Mms-Message-Class: 82: Informational 8E: X-Mms-Message-Size 01: Length 78: ??? 88: X-Mms-Expiry 06: Length 80: Absolute Token 04 - 64: ??? 83: X-Mms-Content-Location 68 t/m 00: http://128.130.90.54/g/m.mms You see, two things I don’t understand: 1. The Message Size: 78 gives 120 in dec, but when opening the file with Nokia Mobile Internet Toolkit is shows X-Mms-Message-Size = 100. And the size of the message is 89 bytes. Another notification MMS with the size of 101 bytes also uses this 78 value. Is the Message Size strict, or is it not? Who can help me out? 2. The Expiry field: I can see that the length is 6 tokens, with the Absolute Token as the first one. But the other 5? By opening the file with the Nokia Mobile Internet Toolkit it gives the date in GMT + 1 day. Another notification example reacts the same way in the NMIT but the codes are different: 88 06 80 04 7A A7 7D 64 for this example… 88 06 80 04 7A E9 92 4A for the other one… Is here someone able to explain how this stuff works? Greetings, Joram Ps. correct me if some of the other things I tried to decode are wrong… | |||
| Scott Yaung New member Username: Gzscott Post Number: 8 Registered: 01-2004 |
Answer for your question 1: 1.I found the MMS Size does not matter, seems the mobile do not check it. | |||
