Send an OMA OTA setting to a PC WAP client.

Send an OMA OTA setting to a PC WAP client. SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 02, 2006 » Send an OMA OTA setting to a PC WAP client. « Previous || Next »
Author Message
Joe Pojun
New member
Username: Pjjoe

Post Number: 1
Registered: 05-2006
Posted on Monday, May 08, 2006 - 08:51 am:   

Dear all,
Using NowSMS I have sent some WAP pushes to my Obigo simulator on PC. But I failed to send any OMA OTA settings to the simualtor. I try to monitor all the sending transations on my PC. Any one knows that NowSMS able to send OTA to my Obigo Simulator? And how?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5899
Registered: 10-2002
Posted on Monday, May 08, 2006 - 06:22 pm:   

We don't support sending OMA OTA settings via the web interface an IP address. The web interface can only support sending MMS messages and WAP push SI and SL messages to an IP address.

However, you could send OMA OTA settings to an IP address if you posted them via the PAP (Push Access Protocol) interface. You would need to perform an HTTP POST like this to the web port of NowSMS:

POST /pap?user=username&password=password HTTP/1.0
Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type="application/xml"
Content-Length: xxxxx

--asdlfkjiurwghasf
Content-Type: application/xml

<?xml version="1.0"?>
<pap>
<push-message push-id="9fjeo39jf084@pi.com">
<address address-value="wappush=1.2.3.4/TYPE=IPv4"></address>
</push-message>
</pap>
--asdlfkjiurwghasf
Content-Type: text/vnd.wap.connectivity-xml

<wap-provisioningdoc>

...

</wap-provisioningdoc>
--asdlfkjiurwghasf--


The only real trick in submitting this type of post is that the "Content-Length:" header is very important, as it tells the server how much content to expect. It needs to specify the number of bytes of data following the HTTP header.

-bn}
Joe Pojun
New member
Username: Pjjoe

Post Number: 2
Registered: 05-2006
Posted on Thursday, May 11, 2006 - 08:13 am:   

Thank you Bryce,

I have made some tests both on Push and Provisioning messages by the instructions you gave me. I use "telnet localhost 8800" to perform HTTP POST at my PC. I can send Push in this way and NowSMS gives me good responses by "HTTP/1.0 202 Accepted". But I received no response from NowSMS in sending the following Provisioning msg. Can You help to check the msg content is good?

POST /pap?user=username&password=password HTTP/1.0
Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type="application/xml"
Content-Length: 1356
--asdlfkjiurwghasf
Content-Type: application/xml
<?xml version="1.0"?>
<pap>
<push-message push-id="9fjeo39jf084@pi.com">
<address address-value="wappush=127.0.0.1/TYPE=IPv4"></address>
</push-message>
</pap>
--asdlfkjiurwghasf
Content-Type: text/vnd.wap.connectivity-xml
<?xml version="1.0"?>
<!DOCTYPE wap-provisioningdoc PUBLIC "-//WAPFORUM//DTD PROV 1.0//EN"
"http://www.wapforum.org/DTD/prov.dtd">

<wap-provisioningdoc>

<characteristic type="PXLOGICAL">
<parm name="PROXY-ID" value="123.123.123.123"/>
<parm name="NAME" value="Logical"/>
<parm name="STARTPAGE" value="http://www.me.com"/>

<characteristic type="PORT">
<parm name="PORTNBR" value="9201"/>
</characteristic>

<characteristic type="PXPHYSICAL">
<parm name="PHYSICAL-PROXY-ID" value="PH"/>
<parm name="PXADDR" value="123.123.123.123"/>
<parm name="TO-NAPID" value="NAP"/>
</characteristic>

</characteristic>

<characteristic type="NAPDEF">
<parm name="NAPID" value="NAP"/>
<parm name="BEARER" value="GSM-CSD"/>
<parm name="NAME" value="My NAP"/>
<parm name="NAP-ADDRESS" value="+888888888"/>
</characteristic>

<characteristic type="BOOTSTRAP">
<parm name="NAME" value="Doc 1"/>
</characteristic>

</wap-provisioningdoc>

--asdlfkjiurwghasf--
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5922
Registered: 10-2002
Posted on Thursday, May 11, 2006 - 01:46 pm:   

Hi Joe,

Unfortunately, there's not much that can be done to troubleshoot this type of push.

I suppose the first thing that should be confirmed is that your simulator can actually receive push messages over IP.

If you send a WAP Push from the web interface, and specify an IP address as the phone number, does the simulator receive the push message?

The simulator needs to listen for push messages on UDP port 2948 ... you can use NETSTAT -a from a command window to determine if any programs are listening on this port.

Most simulators that I have seen do not listen for pushes over IP.

Aside from that, make sure that you have a blank line after "Content-length:" header in your text ... and after the "Content-type:" headers within the content.

And verify that the simulator should be able to accept these types of push messages over UDP/IP. (It would be unusual for a simulator to accept these messages, but I assumed maybe you were a developer of the simulator that you mentioned, as I am not familiar with it.)

-bn
Joe Pojun
New member
Username: Pjjoe

Post Number: 3
Registered: 05-2006
Posted on Monday, May 15, 2006 - 07:38 am:   

Hi Bryce,
My simulator works fine on receiving pushes and provisionings over IP. I guess the NowSMS's PAP can not afford a big push msg. I always failed in POSTing a provisioing to NowSMS via PAP if the content length is 2KB around. After I reduce the msg size to 1500B I can send every provisioing msg successfully. Dose NowSMS limit the size for a push msg? Can I expand it?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5937
Registered: 10-2002
Posted on Tuesday, May 16, 2006 - 08:22 pm:   

Hi Joe,

It does appear that via the PAP interface, we will truncate an IP push message at 2000 bytes.

Send an e-mail message to nowsms@now.co.uk with "Attention: Bryce" in the subject line, and I'll e-mail you back a patch that should address this limit.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics