How to use PAP with NowSMS

How to use PAP with NowSMS SearchSearch

NowSMS Support Forums » NowSMS Support - SMS Issues » Archive through October 19, 2005 » How to use PAP with NowSMS « Previous || Next »
Author Message
Posted on Monday, August 15, 2005 - 03:10 pm:   


How can I use PAP with NowSMS? Is there a software that I could use for sending the messages to NowSMS (where to put the content of the message)?

In following example is adviced how to use PAP it but I still don't know how to use it or where to copy the content. Should HTTP POST used in it somehow? html

In the same example is said that wbxml content can be used also (when using binary parameter). Should that wbxml content be put in hex-string or in 8-bit binary data? I am trying to send syncml related messages to mobile phone.

What is the maximum content length that can be put to one message?

Thanks, JJ
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4760
Registered: 10-2002
Posted on Tuesday, August 16, 2005 - 02:24 pm:   

Hi JJ,

I don't have any generic examples of software that uses PAP.

But referring to the above thread, the fourth message in the thread has an HTTP POST example for PAP which is quite good.

In that example, it is showing what the HTTP POST looks like. The content for the push is multipart. The first part is XML that is specific to the PAP protocol. And basically, you just have to insert a phone number for the "xxxxxxxxx". (And you can remove the "/" if you want to ... when connecting to other PPGs, this type of syntax might be required, but we just ignore that bit.)

<address address-value="wappush=xxxxxxxxx/"></address>

For putting WBXML content into such a post, you would put in the actual 8-bit binary data. The "Content-Transfer-encoding: binary" header in MIME basically means that the actual 8-bit data follows.

One other note. If you are sending content of the type "application/vnd.syncml.ds.notification", then I would suggest downloading our v5.51d update ( The reason for this is that I understand some phones do not like the long content type header that we were using and expect a short version for DS notifications.

Regarding maximum content length ... if you are sending WBXML, then each byte of your data is going to count as one byte in any SMS messages that are sent out. There will be some overhead, maybe 20 bytes in the first message, and 12 bytes in subsequent message parts. 140 binary bytes can fit in one SMS message. So if the message is longer than 120 bytes, there will be an additional SMS for each additional 128 bytes of your content.

We don't impose a strict limit, but many phones have problems receiving a multipart SMS that spans more than 5 messages. (Although newer phones, which would understand your SyncML commands should support longer multipart messages.)

So your limits are more to do with the number of SMS that will be sent out.

(And my numbers are somewhat rough estimates, not necessarily exact.)


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