| Why is the WAP push wrong |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through August 01, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| danfel New member Username: Danfel Post Number: 1 Registered: 06-2006 |
I have test a WAP PUSH issue. MS received a PUSH content by SMS, however it can not be parsed rightly. So the PUSH content is discard. I want to know why. the push content is as follow: 08 91 68 31 08 20 01 05 F0 44 04 A1 09 20 00 04 60 60 03 01 35 41 23 4A 06 05 04 0B 84 23 F0 1E 06 1A AE B4 87 AF 82 45 6E 63 6F 64 69 6E 67 2D 56 65 72 73 69 6F 6E 00 31 2E 32 00 01 05 6A 00 45 C6 0C 03 6E 65 77 2E 63 6F 6D 00 07 01 03 68 74 74 70 3A 2F 2F 6E 65 77 2E 63 6F 6D 20 00 01 01 00 20 00 01 01 00 E5 CC 6D ED A0 00 E0 20 6D 0E 8E 8E 07 45 E5 ED CC AE E5 CC 6D ED A4 00 00 20 20 00 99 EC 10 4D 4D 11 10 39 3F 2A 11 B1 4D 11 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 01 00 0C 43 85 I need your help! thank you | |||
| danfel New member Username: Danfel Post Number: 2 Registered: 06-2006 |
I had checked the PUSH content, it is some wrong above. The factual data is as follow: 06 05 04 0B 84 23 F0 1E 06 1A AE B4 87 AF 82 45 6E 63 6F 64 69 6E 67 2D 56 65 72 73 69 6F 6E 00 31 2E 32 00 01 05 6A 00 45 C6 0C 03 6E 65 77 2E 63 6F 6D 00 07 01 03 68 74 74 70 3A 2F 2F 6E 65 77 2E 63 6F 6D 20 00 01 01 00 01 should be end char in WBXML, but this push content is end as 00. Is it fatal wrong when not ending as 01. I wait for your response. | |||
