| MIME type Issue |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| rajender pasricha New member Username: Rajender Post Number: 2 Registered: 03-2007 |
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). An early response will be jhighly appriciated. Thanks in advance, Rajender Pasricha | |||
| DevMan New member Username: Devman Post Number: 2 Registered: 07-2007 |
This seems to be a real issue. How does NowSMS send a OMA OTA WAP Push message for Client Provisioning? Is it sent as a application/vnd.wap.connectivity-wbxml msg or is it attached to a SMS? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7339 Registered: 10-2002 |
No, this is not a real issue. When NowSMS sends an OMA Client Provisioning message, the XML content is encoded as WBXML with the content type "application/vnd.wap.connectivity-wbxml". That WBXML content is packaged inside of a WAP WSP Connectionless Push PDU. I posted some more detail in another posting of this same issue here: http://support.nowsms.com/discus/messages/131/21949.html There is no content type problem with NowSMS sending OMA Client Provisioning messages. If you are having a problem with a device not receiving provisioning messages, keep in mind that most devices require that the provisioning content be signed by a PIN. (I do not believe that the original poster is having a PIN related problem ... but it may be a problem that others are experiencing. The original poster appears to be involved in client software development for a mobile device and they are having some decoding issues.) -bn -bn | |||
