| MMS Notification WAP Push ISSUE |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through April 10, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Nobin Mathew New member Username: Quantummachine Post Number: 1 Registered: 03-2006 |
Dear Friends, I got a problem with MMS notification WAP push. The Entire Wap Push is given below. It s attached as afile.
The User Data Part is pated Below: 0x00, 0x01, 0x00, 0x23, 0xf0, 0x0b, 0x84, 0x59, 0x06, 0x26, 0x61, 0x70, 0x70, 0x6c, 0x69, 0x63, 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x2f, 0x76, 0x6e, 0x64, 0x2e, 0x77, 0x61, 0x70, 0x2e, 0x6d, 0x6d, 0x73, 0x2d, 0x6d, 0x65, 0x73, 0x73, 0x61, 0x67, 0x65, 0x00, 0x8d, 0xdc, 0xaf, 0x84, 0xb4 , 0x80, 0x8c, 0x82‚ 0x98, 0x4d, 0x32, 0x30, 0x30, 0x36, 0x30, 0x32, 0x31, 0x37, 0x30, 0x30, 0x33, 0x34, 0x33, 0x38, 0x00, 0x8d, 0x90, 0x89, 0x02, 0x80, 0x00, 0x8a, 0x80, 0x8e, 0x01, 0x80, 0x88, 0x05, 0x81, 0x03, 0x01, 0x51, 0x80, 0x83, 0x68, 0x74, 0x74, 0x70, 0x3a, 0x2f, 0x2f, 0x31, 0x30, 0x2e, 0x30, 0x2e, 0x39, 0x2e, 0x32, 0x35, 0x2f, 0x4d, 0x32, 0x30, 0x30, 0x36, 0x30, 0x32, 0x31, 0x37, 0x30, 0x30, 0x33, 0x34, 0x33, 0x38, 0x00 This is a WAP PuSh over CDMA SMS. The problem with WAP Push is phone is recognizing a new WAP Push but it is not doing the whole processing, i think there some problems in the PDU. I strongly feel that User Data is the corrupted one. For further details you can refer attached file. Please help me on this, i got few questions regarding this WAP Push. Firstly i will explain fields i know.Correct me if i am going wrong. 0x00, 0x01, 0x00, 0x00 for WDP data on SMS, 0x01 is the total number of segments, 0x00 is the segment number 0x23, 0xf0, 0x0b, 0x84 These are source port and destination port. 0x59 is transaction ID and 0x06 is PUSH. 0x26 is the length of content type fields and headers, please tell me know how this is calculated from content type length and headers. After immediate 0x00 what the next two does(i.e.0x8d, 0xdc) mean???. After that 0xAF84 WAP-Push-Application-Id: MMS User Agent Next 0xB480 is bit misleading 0xB4 is Push Flag Header(calculated as 0x34|0x80) and 0x80 is the push value(0x00 | 0x80), so my question is is it possible to have 0 as WAPPushFlag value???. One more question, is it possible to have 7(0x07|0x80 = 0x87) as WAPPushFlag??? Next it is 0x8C82 Message-Type: MM1_Notification.IND and Please explain to me the remaining part of this Wap Push and also it's encoding. Help me also in finding the mistake in this WAP Push. Thanks, Nobin Mathew | ||||
| Nobin Mathew New member Username: Quantummachine Post Number: 2 Registered: 03-2006 |
Dear friends, How the different segments in user data part is distinguished. Thanks, Nobin Mathew | ||||
| Nobin Mathew New member Username: Quantummachine Post Number: 3 Registered: 03-2006 |
Dear friends, I am doubting (0x8d, 0xdc) after 0xAF84, i think these are just junk characters. I am not sure,I have only primary knowledge about these. Thanks, Nobin Mathew | ||||
| Nobin Mathew New member Username: Quantummachine Post Number: 4 Registered: 03-2006 |
Dear Friends, I almost decoded that Wap Push, Can u tell me where the problem is? Please tell me the importance of Push Flag I am pasting the decoded Wap Push Here CHARi [0x00] // Message Type: WDP CHARi [0x01] _ // Total # of segments CHARi [0x00] // Current segment CHARi [0x23] # // 0x23f0 "Source Port" CHARi [0xf0] ð // 0x23f0 = decimal 35240 CHARi [0x0b] _ // 0x0b84 "Destination Port" CHARi [0x84] „ // 0x0b84 = decimal 11132 // up to this it is WDP // WSP starts here CHARi [0x59] Y // WSP Transaction ID (similar to our SMS Msg ID) CHARi [0x06] _ // Push PDU Type CHARi [0x26] & // Header Length (decimal 38) CHARi [0x61] a CHARi [0x70] p CHARi [0x70] p CHARi [0x6c] l CHARi [0x69] i CHARi [0x63] c CHARi [0x61] a CHARi [0x74] t CHARi [0x69] i CHARi [0x6f] o CHARi [0x6e] n CHARi [0x2f] / CHARi [0x76] v CHARi [0x6e] n CHARi [0x64] d CHARi [0x2e] . CHARi [0x77] w CHARi [0x61] a CHARi [0x70] p CHARi [0x2e] . CHARi [0x6d] m CHARi [0x6d] m CHARi [0x73] s CHARi [0x2d] - CHARi [0x6d] m CHARi [0x65] e CHARi [0x73] s CHARi [0x73] s CHARi [0x61] a CHARi [0x67] g CHARi [0x65] e // up to this it is content type = “application/vnd.wap.mms-message” this is for MMS notification CHARi [0x00] // Null terminator CHARi [0x8d] // content length CHARi [0xdc] Ü // content length value CHARi [0xaf] ¯ CHARi [0x84] „ // 0xAF84 WAP-Push-Application-Id: MMS User Agent CHARi [0xb4] ´ // push flag CHARi [0x80] € // push flag value (i.e. 0x00 | 0x80) CHARi [0x8c] Œ // Message Type CHARi [0x82] ‚ // Message Type Value CHARi [0x98] ˜ // Transaction ID CHARi [0x4d] M CHARi [0x32] 2 CHARi [0x30] 0 CHARi [0x30] 0 CHARi [0x36] 6 CHARi [0x30] 0 CHARi [0x32] 2 CHARi [0x31] 1 CHARi [0x37] 7 CHARi [0x30] 0 CHARi [0x30] 0 CHARi [0x33] 3 CHARi [0x34] 4 CHARi [0x33] 3 CHARi [0x38] 8 // up to this it is Transaction ID (i.e. M20060217003438) CHARi [0x00] // Null terminator CHARi [0x8d] // MMS Version CHARi [0x90] // Version 1.0 CHARi [0x89] ‰ // From: CHARi [0x02] _ // from length CHARi [0x80] € // address-present-token CHARi [0x00] // Null terminator CHARi [0x8a] Š // X-Mms-Message-Class CHARi [0x80] € // Personal CHARi [0x8e] Ž // X-Mms-Message-Size CHARi [0x01] _ // one byte CHARi [0x80] € // i.e. 0x80 CHARi [0x88] ˆ // X-Mms-Expiry CHARi [0x05] _ // 5 octets CHARi [0x81] // Relative CHARi [0x03] _ // 3 bytes long integer CHARi [0x01] _ CHARi [0x51] Q CHARi [0x80] € // 015180 = xx days from now CHARi [0x83] ƒ // X-Mms-Content-Location CHARi [0x68] h CHARi [0x74] t CHARi [0x74] t CHARi [0x70] p CHARi [0x3a] : CHARi [0x2f] / CHARi [0x2f] / CHARi [0x31] 1 CHARi [0x30] 0 CHARi [0x2e] . CHARi [0x30] 0 CHARi [0x2e] . CHARi [0x39] 9 CHARi [0x2e] . CHARi [0x32] 2 CHARi [0x35] 5 CHARi [0x2f] / CHARi [0x4d] M CHARi [0x32] 2 CHARi [0x30] 0 CHARi [0x30] 0 CHARi [0x36] 6 CHARi [0x30] 0 CHARi [0x32] 2 CHARi [0x31] 1 CHARi [0x37] 7 CHARi [0x30] 0 CHARi [0x30] 0 CHARi [0x33] 3 CHARi [0x34] 4 CHARi [0x33] 3 CHARi [0x38] 8 // up to this it is content location, and is http://10.0.9.25/M20060217003438 CHARi [0x00] // Null Terminator Thanks Nobin Mathew | ||||
Entire Wap Push
