rajender pasricha
New member
Username: Rajender
Post Number: 3
Registered: 03-2007
| | Posted on Thursday, July 05, 2007 - 07:49 am: | |
We need a WAP Push Msg with the MIME type - application/vnd.wap.connectivity-wbxml (Content Type code - 0x36)
If we use the OMA CP option for sending a WAP push Msg using NowSMS we get the MIME type: application/vnd.wap.wbxml (Content Type code - 0x29)
So basically what can we do to get the Msg with the desired Msg (application/vnd.wap.connectivity-wbxml).
Early response will be highly appriciated.
Thanks in advance,
Rajender |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 7335
Registered: 10-2002
| | Posted on Tuesday, July 10, 2007 - 11:05 pm: | |
Hi Rajender,
This section of the forum is for the NowWAP proxy, which is a separate product from NowSMS ... but it is confusing because NowSMS acts as a WAP Push Proxy Gateway.
I sent you some more information via e-mail ... but basically I am not aware of any situation where NowSMS would use MIME type: application/vnd.wap.wbxml (Content Type code - 0x29) for encoding an XML settings document.
If you are sending OMA Provisioning content (<wap-provisioningdoc>), then we use application/vnd.wap.connectivity-wbxml (Content Type code - 0x36).
As I mentioned in my e-mail ... I am suspcious of how you are extracting the WBXML from the WAP Push message that NowSMS sends for the OMA Provisioning Content.
NowSMS does not generate a WBXML document directly as output. It generates a complete WAP push message which includes the WBXML content as part of the WAP Push message.
Let's take the Provisioning Content document that you sent us via e-mail ...
<wap-provisioningdoc>
<characteristic type="BOOTSTRAP">
<parm name="NAME" value="gprsnew" />
</characteristic>
<characteristic type="NAPDEF">
<parm name="NAME" value="gprsnew" />
<parm name="NAPID" value="gprsnew_NAPID" />
<parm name="BEARER" value="GSM-GPRS" />
<parm name="NAP-ADDRESS" value="symbian" />
<parm name="NAP-ADDRTYPE" value="APN" />
<parm name="INTERNET" />
<characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP" />
<parm name="AUTHNAME" value="synbian" />
<parm name="AUTHSECRET" value="sdfj" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
If I send the above document using the NowSMS "Send XML Settings" web form, the following SMS message is generated (I extracted this data from the SMSOUT-yyyymmdd.LOG file):
DCS=F5;UDH=0605040B8423F0;Data=0A0601B6030B6A08677072736E65770045C65601870706830 00101C6550187070683000187110603677072736E65775F4E415049440001871006AB01870806037 3796D6269616E00018709068901871401C65A01870C069A01870D060373796E6269616E0001870E0 6037364666A0001010101
Basically, this is a WSP Connection-less push PDU.
The UDH contains source/destination port addressing to identify the message as a WAP push.
The "data" of the message is the WSP connection-less push PDU.
0A - This is an ID field for the push, this simply increments each time we send a push.
06 - This is the WSP PDU type field, 06 for connection-less push.
01 - This is the headers length
B6 - This is the content type ... B6 is the short encoding for "application/vnd.wap.connectivity-wbxml"
The rest of the data is the actual WBXML content.
If you include a PIN to sign the push, then the content type field becomes considerably more complex.
But anyway ... this is the data that I see NowSMS generate when it sends the provisioning content document that you sent us previously. And as you will see, the MIME content-type is encoded correctly.
If you are seeing a different content type in the push that you receive, then this suggests that something else has performed some processing against the data.
I would suggest that you look more closely at the raw data that comes out of NowSMS ... and follow the path of that data as it is routed to your application, because something appears to be interfering with it.
-bn |
Search
Last
