| Windows Mobile - Identifying WAP Push SMS |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ |
◄ ► |
| Author | Message | |||||
| Isaac New member Username: Isaacw Post Number: 1 Registered: 08-2006 |
Hello, We're trying to test WAP Push provisioning over-the-air (OTA) via SMS by using two Windows Mobile devices - one as a sender, the other as a receiver. When the receiving device receives the provisioning message (the message just adds a new browser Favorite, and the message is unsigned), the following "Confirmation" prompt appears: "From unidentified sender: This changes device settings. Caution: unauthenticated message. Accept?" When hitting 'Yes', the Browser Favourite is created properly. Question 1: what does 'unidentified sender' mean? When sending a regular text SMS message, the receiving phone can decipher the sender's phone number, e.g. +61410022305. When receiving a WAP Push message, shouldn't the receiver know the message comes from a particular phone number? Or does 'unidentified sender' means something else. To send the provisioning message, we're using a modified version of the WDP_SMS sample code to send the message (the original code can be found in the 'Windows CE' SDK, e.g. in 'C:\Program Files\Windows CE Tools\wce500\Windows Mobile 5.0 Smartphone SDK\Samples\CPP\Win32\Cellcore\Wdp_sms') from the sending Windows Mobile device. Now, we've set up the WAP_ADDRESS's for the sender's number, and the receiver's number. Question 2: At present, the receiving device can only receive the provisioning message when the device is completely unlocked (we used 'unlock.xml' as attached here). We're trying to set up a Trusted Provisioning Server (TPS) and a Push Proxy Gateway (PPG) for the receiving device to accept messages from the sending device, as identified by a phone number. We tried doing this via 'WapTrustedGateway.xml' (as attached). However, the receiving device simply drops the incoming message without any prompt or messages. How do we set up the receiving device to only accept unsigned messages coming from the sending device by recognising the sender's phone number? Your help would be much appreciated. Thanks! Regards, Isaac
| |||||
| Frank Henningsen New member Username: Fhx Post Number: 2 Registered: 02-2008 |
Hi Issac, Regarding question 1: If you dont provide a Originating Name within the SMS message, then your device will reckonize the message as unidentified, unless you have provided a value for the X-WAP-Initiator-URI within the WSP header. Regarding question 2: Ive managed to obtain the TPS role by including the following parameters when i encode the provisioning xml: - Content type - Originating address: The OA is the SMSC address. - Push-Flag: The push-flag is defined in [WAPPUSHOTA ch 9.1.3]. If the push-flag is given the value 1, it is possible to obtain the TPS role - X-Wap-Initiator-Uri defines the originating initiator URI address of a WAP message. The X-Wap-Initiator-Uri is defined in [WAPPUSH ch. 5.2.2.3] The following template shows how a WAP push message should be encoded. /** * Create WSP PDU (WAP-230-WSP 8.2.1) */ [01] Transaction ID [06] PDU Type PDU Type (0x06 = push, WAP-230-WSP 8.2.4.1) <wsp-hdr-length> WSP Header length /** * Encode Content type. Content Type are registered at * http://www.wapforum.org/wina/wsp-content-type.htm */ [1f] Length-Quote. Length > 30 and necessary to quote. (WAP-230-WSP 8.4.2.2) [2d] Length: 0x2D = 45 (includes content type and security) [b6] WSP Content type (0x80 | 0x36 = B6) (application/vnd.wap.connectivity-wbxml) /*** * Encode security method (SEC) (WAP-183-PROVCONT 5.3) * 0x00 = NETWPIN * 0x01 = USERPIN * 0x02 = USERNETWPIN * 0x03 = USERPINMAC */ [91] SEC (0x80 | 0x11 = 0x91) (WAP-230-WSP Table 38) <security-method> The security method (NETWPIN, USERPIN, etc) [92] MAC (0x80 | 0x12 = 0x92) (WAP-230-WSP Table 38) <hmac-value> MAC value, always 40 bytes [00] EOF /** * Encode Push-Flag (WAP-189-PushOTA 9.1.3): * 0x01 = Initiator URI is authenticated * 0x02 = Content is trusted * 0x04 = Last push message * other = reserved for future use :-) */ [b4] Push-Flag token (0x80 | 0x34 = 0xB4) [81] Push-Flag value (0x80 | 0x01 = 0x81) : Initiator URI is authenticated /** * Encode X-WAP-Initiator-URI as ASCII/Hex (WAP-230-WSP Table 39) */ [b1] X-WAP-Initiator-URI <initiator-Uri> X-WAP-Initiator-URI value [00] EOF /** * (Optional) Encode X-WAP-APPLICATION-ID. Application-ID's are registered at * http://www.openmobilealliance.org/tech/omna/omna-push-app-id.htm */ [AF] X-WAP-APPLICATION-ID (0x80 | 0x2F = 0xAF) (WAP-230-WSP Table 39) [80] x-wap-application:* (0x80 | 0x00 = 0x80) ANY_APPLICATION <WSP Body> best regards Frank Henningsen (autodidactic WAP push expert) | |||||
| Anupam Mangudkar New member Username: Anupamvm Post Number: 1 Registered: 11-2008 |
Hello...I was not able 2 receive the WAP provisioning message over my Windows Mobile Device. I have used a Nokia phone as a Modem and am sending the WAP Provisioning message using the NOWSMS web interface.I receive the same message successfully when sent on a Nokia phone and it also changed the settings successfully when the receiver is a Nokia phone. Also could we connect a Windows Mobile device as a Modem for NOW SMS ? Any help would be gr8! | |||||
| Anupam Mangudkar New member Username: Anupamvm Post Number: 3 Registered: 11-2008 |
Hello...I was not able 2 receive the WAP provisioning message over my Windows Mobile Device. I have used a Nokia phone as a Modem and am sending the WAP Provisioning message using the NOWSMS web interface.I receive the same message successfully when sent on a Nokia phone and it also changed the settings successfully when the receiver is a Nokia phone. Also could we connect a Windows Mobile device as a Modem for NOW SMS ? Any help would be gr8! | |||||
| Frank Henningsen |
hi anupam, I guess that you need to configure your security policies correctly to receive your message. I recommend you use a remote control tool like http://www.breaksoft.com/Blog/Utilities/2005/1/Mobile_Registry_Editor.aspx to view and edit your policies on your WM device. best regards Frank | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 191 Registered: 08-2008 |
Hi Anupam, As Frank mentions, security policies are a big deal for Windows Mobile devices. By default, the security policy defined by the operator and OEM will not allow provisioning. There's some more info in the following thread: http://support.nowsms.com/discus/messages/1/24272.html Also be forewarned that you cannot send simple provisioning messages using the NowSMS "Send OMA OTA Settings" web form, like you can with many other devices. You need to write your own XML for provisioning Windows Mobile devices, which tends to be a lot more complex. The XML is based upon the same OMA Provisioning Content specification, but Microsoft has added numerous extensions that are specific to Windows Mobile. The other thread may give you some additional pointers. -- Des NowSMS Support | |||||
| Christine LE DREO New member Username: Evitavie Post Number: 1 Registered: 07-2009 |
Hello all! We are trying to federate a group of small retailers (for a temporary city event) to send push SMS (advertising) randomly to people arriving at airport. What open source applications can we use to send such SMS, assuming we do not know the cell phone numbers of passengers arriving at the airport. What are the important parameters for configuring such a system? Can we configure the time for sending PUSH SMS and daily volume per retailer? What are the general prices (price per SMS) for such services for bulk volume (thousands, millions SMS per month)? I just need an approximate idea for North American operators. What minimum set of players (Cellphone operators, SMS gateways, SMS brokers, etc) do we need to work with to reduce the cost of sending these push SMS? Thanks in advance for all your advice and suggestions! Christine | |||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1027 Registered: 08-2008 |
Hi Christine, That's an interesting scenario. But it's pretty tall order to send SMS messages to people when you don't know their phone numbers. I don't know what country you are operating in, but I would also expect that privacy laws would be an issue as well. I expect that the only way that you'd be able to do this would be in partnership with a mobile operator. The mobile operator knows when a subscriber registers with a cell site at the airport. Without them, you don't have access to this information. Maybe someone else will have other ideas for you ... but the way I see it, open source software and SMS pricing are the least of your concerns. The big concern would be getting a mobile operator to partner with you on this, so that they give you the phone numbers of subscribers as they register with the cell site. A secondary concern would be that sending unsolicited text messages can have legal issues associated with it. -- Des NowSMS Support | |||||
| Eugene Kleca New member Username: Berthoudguy Post Number: 1 Registered: 07-2009 |
HI: I'm just trying to get the WDP_SMS sample code found in 'C:\Program Files\Windows CE Tools\wce500\Windows Mobile 5.0 Smartphone SDK\Samples\CPP\Win32\Cellcore\Wdp_sms' to work. I changed the number to my cell phone number. I have a Verizon Windows Mobile Ver 6.1 phone. It loads and runs to the point of sending the data and then I get an error. Is there more than what I can find on the setup? Thanks in advance. | |||||
| vetriselvi New member Username: Leema Post Number: 1 Registered: 08-2010 |
[unrelated spam removed] | |||||
unlock.xml
