Possible WAPPushFlag problem

Possible WAPPushFlag problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 02, 2006 » Possible WAPPushFlag problem « Previous || Next »
Author Message
New member
Username: Dcw

Post Number: 1
Registered: 01-2006
Posted on Wednesday, February 01, 2006 - 11:48 am:   

I was trying to decode the WSP layer when I add the WAPPushFlag to the smsgw.INI file. Below is what I believe is the WSP layer and how I think it is decoded.

A2 - transaction ID
06 - PDU Type (0x06 = push)
46 - Headers length (0x46 = 70)
1F2D - length quote (length is 0x2D = 45)
B6 - WSP Content type (0x80 | 0x36 = application/vnd.wap.connectivity-wbxml)
91 - 0x80 | 0x11 = SEC ????
80924530444235373641383831393937373730333946333537434133413539394137343239384532 333100?????
B1 - 0x80 | 0x31 = X-Wap-Initiator-URI
687474703A2F2F7777772E746573742E636F6D00 - http://www.test.com
B3 - 0x80 | 0x33 = Bearer-Indication ????
82 - The value I have in the smsgw.INI file for WAPPushFlag or'd with 0x80

When I remove WAPPushFlag from my ini file, these last two bytes don't show up when I send messages so I am pretty sure these are for that flag. Plus when I change the value that WAPPushFlag is equal to (either 1, 2, or 3) the last byte changes from 0x81, 0x82, 0x83. But according to WAP-230-WSP-20010705-a page 107, Bearer-Indication is header field 0x33 and Push-Flag is 0x34 thus I would expect the second to last byte to be 0xB4 not 0xB3.

Can anyone tell me if my decode is correct and if NowSMS has a bug when using the WAPPushFlag? Or am I doing something wrong with my decode.

Bonus question: How do I decode the 43 bytes in the content type after SEC?

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5494
Registered: 10-2002
Posted on Wednesday, February 01, 2006 - 03:40 pm:   

Hi Dan,

That's definitely a bug.

We've been primarily working on the new NowSMS 2006 release over the past few months. But we've also been prepping a minor patch release for the current product. So I'm going to make sure that this fix goes into the patch. (Either later this week, or early next.)

Regarding the other question:

92 ...= MAC=....

The MAC is essentially a checksum (HMAC, if memory serves me correctly) of the content signed with a shared secret (in this case the NETWPIN). More details can be found in the OMA Provisioning Content specifications.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics