| Sending binary message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Rafael Pacheco New member Username: Rpachecoh Post Number: 2 Registered: 05-2007 |
I am trying to provision a Windows Mobile 5, but I found some problems using NowSMS. As far as I can know, I think the problem is how NowSMS encode some specific Microsoft parameters, such as <nocharacteristic>. I can get the correct Microsoft encoded wbxml provisioning message, so I want to try to send it using the binary option in NowSMS, but I do not know how to get the MAC of the message. Could any one help me? What I do is: UDH: 06:05:04:0b:84:23:f0 DCS: F5 Data: WSPHeader+wbxml ---------------------------- The WSPHeader is: f9 Transaction ID 06 PDU Type ---- SECURITY REQUIRED 2f Header Length 1f2d Length-quote length b6 Content type (UTF-8) 91 Security header 81 Security value (User PIN) 92 MAC header MAC VALUE (40 bytes) 00 (indicates end of MAC Value) ---------------------------------- The wbxml (included Microsoft header) is: 03A20E6A0045C600020501A2000050034D6963726F736F 66740001C65003476F6F676C6500018700020600000603 687474703A2F2F7777772E676F6F676C652E636F6D0001 010101 | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7171 Registered: 10-2002 |
Hi Rafael, Any MS-specific parameters would be encoded as text tags in the WBXML. It is my understanding that MS does support them. However, it is further my understanding that the default configuration for MS mobiles is that they will only accept provisioning content that is signed by the USERNETWPIN method. USERNETWPIN is similar to NETWPIN in that it requires the IMSI number to send out a configuration message. NowSMS 2006 supports USERNETWPIN encoding, but in the web interface, you check "NETWPIN", and then the format of the PIN should be IMSI:USERPIN, where IMSI is the actual IMSI, and USERPIN is the USERPIN value. (If NowSMS gets a NETWPIN request, and it sees a ":" in the PIN value, it converts it to USERNETWPIN.) That said, I'm not sure how any of this discussion helps you, as either way you need an easy way to sign your pre-generated WBXML with either USERPIN or USERNETWPIN MAC. But there is a new feature in NowSMS 2007 that I think would do the trick. When you go to the web interface in the new version, under "Send WAP Push" there is a new "Advanced" option. Using that form, put in "application/vnd.wap.connectivity-wbxml" for the "Content Type". In the "Content" field, put in the hex of your WBXML. For "Content Encoding", specify "Hex String (convert to binary)". Then fill in the "OTA PIN" fields ... if you want to try a USERNETWPIN, then use the instructions that I offered above. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7172 Registered: 10-2002 |
Doh! I should have also mentioned that the formal NowSMS 2007 release is not out yet. But there is a pre-release available for download at http://www.nowsms.com/download/nowsms2007.zip. -bn | |||
