| Decode WAP |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ |
◄ ► |
| Author | Message | |||
| Michael Horvath New member Username: Havi Post Number: 1 Registered: 04-2010 |
Hi! Could someone please help me parsing the service center number, the sender number and the date out of this pdu: 730604ae8d01bf02056a81093930343633360057696c6c6b6f6d6d656e207a756d207072616b7469 7363687374656e2047757473636865696e20616c6c6572205a656974656e21204469652041312047 757473636865696e20426f7820697374206b6f7374656e6c6f7320756e6420536965207370617265 6e2062617265732047656c642e204c6f7320676568742773206175660045c60d0361316775747363 6865696e626f782e61742f00081183000ac3072010041307364110c304201009080183070101 i allready decoded the message and the link according to this post http://support.nowsms.com/discus/messages/1/395.html, but im stuck on the header. to me it seems a bit short, could it be malformed? i would appreciate any help. the pdu type is 6, although i dont really know what that means to be honest. can someone give me a link to a paper where these types are descibed? thanks in advance | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7907 Registered: 10-2002 |
Hi Michael, This looks like a WAP Push PDU (WSP). 73 - transaction id 06 - push PDU 04 - headers len AE - content-type: application/vnd.wap.sic 8D 01 FB - Content-length: 251 application/vnd.wap.sic content follows The service centre number and sender number are not part of this PDU. They would be part of an SMS PDU that would carry this message. If a WAP Push is sent in an SMS message, then you have a WSP WAP Push PDU that is packaged inside a WDP PDU for SMS. The WDP PDU then gets packaged inside of an SMS PDU. The WSP and WDP specifications are part of the WAP Protocols, which can be found at http://www.openmobilealliance.org/Technical/wapindex.aspx SMS PDU formats vary based upon what protocol you are using to interface with SMS. For example, if your interface is SMPP, you would refer to the SMPP protocol (and the service centre number is not available via SMPP). If you are using a GSM modem, then ETSI GSM 07.05 and 03.40 would apply (http://www.etsi.org). -bn | |||
| Michael H. New member Username: Havi Post Number: 2 Registered: 04-2010 |
thanks for your reply, that really helped me. you guys rock | |||
| Akanksha New member Username: Akujun24 Post Number: 1 Registered: 09-2012 |
Hi Can someone help me how to Decode the following WAP Push Messages TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211223956B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211223956B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 0000 00FF017D TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211243836B3D0605040B841C6B0106236170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF9400100100004000000046054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211243836B3D0605040B841C6B0106236170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF9400100100004000000046054001180010 TPDU Data= 0000 00FF017D TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 07804180551512F2FF 440B804180551512F27DF53090211213936B440605040B841C6B01062A6170706C69636174696F6E 2F766E642E6F6D616C6F632D7375706C2D696E697400AF7375706C2E756100001001000040000000 46054001180010 TPDU Data= 0000 00FF017D TPDU Data= 0000 00FF017D TPDU Data= 0000 00FF017D | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4110 Registered: 08-2008 |
Hi, The MIME content type is application/vnd.omaloc-supl-init. It appears to be a type defined by the Open Mobile Alliance (http://www.openmobilealliance.org). I assume it is somehow related to SUPL location services. I did find some other info here: http://support.nowsms.com/discus/messages/132/21808.html However, for more detail, I'd suggest checking the SUPL and location related enabler specification at the OMA web site. -- Des NowSMS Support | |||
| Venkatesh Sathyanarayana New member Username: Msvenky Post Number: 1 Registered: 12-2012 |
Have issue in decoding SUPL INIT messasage through SMS and encoded as WAP PUSH. Message : 0901AB010007804180551512F2009F400B804180551512F27DF53090211223432B8C0B0003020201 05040B841C6B01063B6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E69 7400AF782D6F6D612D6170706C69636174696F6E3A756C702E756100005601000040000000C60540 01182017D040A60E00D20E40CA0DC0E80400860DE0DA0DA0EA0DC0D20C60C20E80D20DE0DC0E6010 2983803483903283703A01002183 Can you help me in decoding? I know that SUPL content type is 6170706C69636174696F6E2F766E642E6F6D616C6F632D7375706C2D696E6974 in the above message and application id is 782D6F6D612D6170706C69636174696F6E3A756C702E7561 in the above message. I want decoding info for the fields before this | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4249 Registered: 08-2008 |
0B000302020105040B841C6B is the SMS User Data Header. I'd assume the 8C before that is message length. | |||
| theresa hill New member Username: Tessalou34 Post Number: 1 Registered: 11-2013 |
can anyone decode this text message or tell me the code which is used HeS]WS]OARAFC]iAH_AB]siQS]OABE_kiARiAPSARgAB]ABYG_Q_YSGAXhQSgAnQ_YKAfSikCiS_]ARg AlKesAHSMMSGkYiAL_eAZKAhQKAD_sgAJ]U_sAhQKAhS[KAhQKsAfaK]IAnSiQAhQKSeAHCIA~ ,130720213915,447802000332,1 | |||
| sridhar d New member Username: Sridhard Post Number: 1 Registered: 03-2014 |
Can any one decode following WAP PUSH message? 010606aeb4828d01c701056a0045c60c03776170707573682e3138392e636e2f3f656d3d4d546735 4d5463324d5449354e6a4e384d44677a4d6d4e6c4e7a4e6c596a4a6c5a6a67334d574d345a574a6c 4d5752694e4759344d4749344f4446384d5441774c6a457562335a504e5734754f4468724c6a457a 4f544130004e5463354d6a51754d5467354d5463324d5449354e6a4e414d5467354c6d4e75620011 03313430313233313431383438303736383333380001035b313839e982aee7aeb15de4b8bbe9a298 3a313233343500010100 Please provide the link to specification to decode the WAP psuh message. thanks in advance. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8080 Registered: 10-2002 |
This looks like a WAP Push PDU (WSP) containing a Service Indication (SI). 01 - transaction id 06 - push PDU 06 - headers len AE - content-type: application/vnd.wap.sic B4 82 - push-flag: 2 8D 01 C7 - content-length: 199 SI content follows Service Indication format has its own spec (WAP 167) in the library at http://www.openmobilealliance.org/Technical/wapindex.aspx. WSP header encoding is WAP 203. -bn Bryce Norwood Now SMS/MMS Support | |||
| sridhar d New member Username: Sridhard Post Number: 2 Registered: 03-2014 |
Thanks a lot for your support Bryce. In the above PDU, last byte "00" is acceptable as per WAP specification? The complete PDU: 000310BDF0018E0460001847D6000C2820C0008008FC02E1004181ABAD20A34071C0415A80117183 00DDD85C1C1D5CDA0B8C4E0E4B98DB8BCFD95B4F535519CD535518CC9355124D539A938E135119DE 935B539B139E939B165A929B169A99CCD355D34D1695D29B1355D49A5391D64D1351D24D13D1118E 1355105DD31A915D588CD6941395CD1D53D11A1C931A915E93D5104C0003061401231418480A0140 0E06040D32C8C480 000311061001620300001847D6000AC815C00080539518CD535A945D535519CD535518CC9355124D 539A9390535519CD531B539D58800440CC4D0C0C4C8CCC4D0C4E0D0E0C0DCD8E0CCCCE000040D6CC 4E0E7A60ABB9EBAC57792E2EFA68A60E8C4C8CCD0D4000404003061401231418490A01400E06040D 32C8C480 what is above PDU type? Thanks, Sridhar | |||
| sridhar d New member Username: Sridhard Post Number: 3 Registered: 03-2014 |
Any help on decoding above PDU? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8084 Registered: 10-2002 |
Without spending a lot of time decoding this, I would say the last byte "00" is invalid. But a good decoder would simply stop when it reaches the closing of the last open WBXML tag. "01" is a tag closer. For the other PDUs ... you'd need to give me some clue as to the context in which you are seeing them. -bn Bryce Norwood Now SMS/MMS Support | |||
