| Sending a MMS push msg |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through February 03, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Will Unregistered guest |
Hi, Bryce: I am trying to send a MMS push msg. I can send a wap push msg(SI) to my mobile equipment successfully now. I tried changing the Content Type of the SI msg to: application/vnd.wap.mms-message... but it doesn't work. Could you please tell me how to send a MMS push msg so tat it will trigger the MMS client to retrieve the MMS file? thx | |||
| Will Unregistered guest |
I made a mistake. I should not modify the SI directly. The MMS push msg (i.e. MMS Notification) is another kind of push msg. I've read the MMS Encapsulation. But Bryce, could u provide a PDU for such a msg so that we can analyze it and understand the encoding rule better? | |||
| Will Unregistered guest |
Hi, I read some of the threads about the encoded MMS nofication: http://support.nowsms.com/discus/messages/12/5617.h tml http://support.nowsms.com/discus/messages/12/208.ht ml and again I got stuck. 1. According to the MMS Encapsulation, the field name assignment for Message-Type is 0x0C, why all those threads got 0x8C instead? Same for the rest of the field names. 2. For the MMS-Version: 1.0 How would the encoded value be 90? isn't it 001 0000 (M.S. 3 digits: major version; L.S. 4 digits: minor version)? 3. Wat r the decoded values of the expiry date in the above two cases? one is 88 04 81 02 0E 10; the other one is 88 06 80 04 7A A7 7D 64. How to decode this field? Hope someone can explain. thx... | |||
| Will Unregistered guest |
I found the answer to my question 1 and 2 in the following thread: http://support.nowsms.com/discus/messages/12/3287.h tml but question 3 remains unsolved. Anyone? | |||
| Will Unregistered guest |
Regarding qn3, I made the following assumption: for 88 04 81 02 0E 10: 88 - expiry 04 - length 81 - relative-token delta-seconds-value 02 0E 10 - 134672 sec = 37.409 hrs which means the msg will expire in 37.409 hrs. for 88 06 80 04 7A A7 7D 64: 88 - expiry 06 - length 80 - absolute-token date-value 04 7A A7 7D 64 - 19237666148 sec = 610 yrs (approximately) which means the msg will expire in year 2580 (1970+610) Am I right? Pls correct me if I am wrong. | |||
| Will Unregistered guest |
Finally I find out the format of the Expiry field. for 88 04 81 02 0E 10: 88 - expiry 04 - length #1, length of the field 81 - relative-token delta-seconds-value 02 - length #2, length of the expiry time 0E 10 - 3600 sec = 1 hr which means the msg will expire in 1 hr. for 88 06 80 04 7A A7 7D 64: 88 - expiry 06 - length #1 80 - absolute-token date-value 04 - length #2 7A A7 7D 64 - 19237666148 sec = 65 yrs (approximately) which means the msg will expire in year 2035 (1970+65) so we can always find tat: length #1 = length #2 + 2 | |||
