| Userpin for wap push messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| davide New member Username: Unidavide Post Number: 1 Registered: 05-2010 |
Hi, I'm, tring to send an wap push sms using a user pin, I use the web interface in "Send WAP Push Message" -> "Advanced" with these values: phone number: my number Content-Type: text/vnd.wap.si content: test content-encoding: text OTA pin: 1234 OTA PIN type: USER PIN but no sms arrive, if I send a standard SMS all works fine. What I have to do to send a WAP PUSH SMS using the OTA pin? I need that my user have to insert the PIN (for message integrity) when I send an SMS, what can I do? regards Davide | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2092 Registered: 08-2008 |
Hi Davide, The WAP Push client on the mobile phone is likely throwing this message away because it is corrupt. You are indicating that the content is WAP Push Service Indication (text/vnd.wap.si) ... however the content is plain text, which the WAP Push receiver would consider corrupt and unreadable. If you want to try sending a WAP Push SI message with a user pin, you would need to enter SI XML content. Here's a simple SI push document: <si> <indication href="http://myurl"/> </si> Content-Type: text/vnd.wap.si content-encoding: XML -- Des NowSMS Support | |||
| davide New member Username: Unidavide Post Number: 2 Registered: 05-2010 |
Hi, thanks for the response, I have done: Send WAP Push Message -> Advanced -> Content-Type: text/vnd.wap.si content: <si> <indication href="http://www.test.com"/> </si> content-encoding: XML ota pin: 1234 ota pin type: user pin the sms arrive but no pin is asked, the sms is normally show, what can I try? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2118 Registered: 08-2008 |
Hi Davide, I've consulted the relevant specifications. Originally the SEC and MAC content-type parameters that are used for PIN authentication were only defined for OMA Provisioning Content. They were not part of the core "Push" specifications. The June 2009 OMA Push version 2.2 candidate release extended the definition of the SEC and MAC parameters to be used for any type of push. This specification also includes an example where a PIN is used to sign a Service Indication (SI) message, similar to what you are trying to send. Eventually terminals might support this. However, my experience is the same as yours ... if a PIN is present on an SI push message ... the terminal just ignores it and treats the message as if it were not signed. So, unfortunately, I don't see any easy way to accomplish what you want. The only idea that I would have is that when the user clicks on your URL, a script behind your URL could prompt for a PIN for authentication. -- Des NowSMS Support | |||
| davide New member Username: Unidavide Post Number: 3 Registered: 05-2010 |
Ok, thank you very much for your reply | |||
