| WBXML to SE Xperia |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ |
◄ ► |
| Author | Message | ||||
| Boris Suhodrev New member Username: Barushok Post Number: 1 Registered: 12-2010 |
Hi guys. I would like to know if your service support WBXML extracted or attached file? 1)I tried to paste the extracted file but that was copied partialy. I used "Send XML Settings Document" and in case of the extracted XML file that succeed. 2) How should I use your service in case of sending WBXML push to SE? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2753 Registered: 08-2008 |
Hi Boris, I cannot answer your question without seeing the content in question. Can you post it in reply here? -- Des NowSMS Support | ||||
| Boris Suhodrev New member Username: Barushok Post Number: 2 Registered: 12-2010 |
Here is the file. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2758 Registered: 08-2008 |
Hi Boris, The "Send XML Settings" interface is for submitting XML documents that NowSMS converts to WBXML. (There are different WBXML value tables for different XML schemas, so NowSMS only supports the XML to WBXML encodings described in the documentation at http://www.nowsms.com/doc/web-menu-interface/send-xml-settings) Converting the XML to WBXML is only part of the issue. The appropriate content type needs to be encoded in the WAP Push, and some content types have additional WAP Push header requirements that NowSMS generates depending on the content type. What you have here is mystery binary content. It appears to be a DRM 1.0 rights object. That type of object is supported via the "Send XML Document" interface, but you should input it using XML format, not WBXML. -- Des NowSMS Support | ||||
| Boris Suhodrev New member Username: Barushok Post Number: 3 Registered: 12-2010 |
Thank you. | ||||
| Boris Suhodrev New member Username: Barushok Post Number: 4 Registered: 12-2010 |
Another question: What is the way to send WBXML file? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2771 Registered: 08-2008 |
You can't just send this WBXML file without constructing the necessary WAP Push headers to tell the receiving device what type of WBXML content this is. This is why I suggest using the XML version of this content instead. The WBXML content that you have started off as an XML file that had to be converted to WBXML format. This XML content would have had a root element of <o-ex:rights>. If you submit that XML document (not the WBXML version) using the "Send XML Settings" form, then NowSMS will convert it to WBXML and generate all of the necessary WAP Push headers to send it to the device. If you are using a tool that only generates a WBXML version of the rights object, then I would suggest you find a different tool. That said, the "Send WAP Push Advanced" form (http://www.nowsms.com/doc/web-menu-interface/send-wap-push-message) can be used to send advanced advanced types of WAP Push messages, such as this content. However, in order to do this, you need to convert your content to a hex string instead of binary data. For example, your content that you previously posted would be expressed as: 030E6A00C50585068607870146470331 2E30000101494A4648036369643A6578 616D706C652E6D70330001014B4CC310 2ABF5BF3F7773B966C27B96453946C97 0101014D4E5253033200010101010101 On the "Send WAP Push Advanced" form, you would specify: Content-Type = application/vnd.oma.drm.rights+wbxml Content = hex string of your content, as described above X-WAP-Application-ID = x-wap-application:drm.ua Other settings can be left at their default. Assuming that the WBMXL is correctly encoded, that should work. If you are confused about converting this binary data into a hex string, here is an old link that has a command line utility that can perform this t type of conversion: http://support.nowsms.com/discus/messages/1/71.html -- Des NowSMS Support | ||||
