NowSMS v5.50 and Push Access Protocol (PAP)

NowSMS v5.50 and Push Access Protocol (PAP) SearchSearch

NowSMS Support Forums » NowSMS Support - MMS & Advanced Issues » Archive through July 14, 2004 » NowSMS v5.50 and Push Access Protocol (PAP) « Previous || Next »
Author Message
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2087
Registered: 10-2002
Posted on Friday, March 12, 2004 - 09:54 pm:   

NowSMS v5.50 now supports the WAP Push Access Protocol (PAP) to provide the ability to generate more specialised types of WAP Push messages. PAP is the standard defined by the Open Mobile Alliance for how applications can interface to a Push Proxy Gateway for sending WAP Push messages.

With support for PAP, NowSMS can be used as a push proxy for other vendor's MMSCs. It also becomes possible to send other types of push messages, such as those related to SyncML, Wireless Village, and OMA Digital Rights Management.

An example of using PAP to send an OMA DRM rights message can be found in the following thread:

To post a push message via the PAP interface, perform an HTTP POST to the "web" port configured for the NowSMS web interface (not the MMSC), posting to a URL of "/pap".

A PAP post is a multipart MIME request, with the first MIME part being the PAP control document that specifies message recipient(s). The second MIME part is the data to be pushed.

An example of a service indication push being sent via PAP can be found below:
-----------------BEGIN EXAMPLE-----------------
POST /pap HTTP/1.0
Content-Type: multipart/related; boundary=mime-boundary; type="application/xml"
Content-Length: xxxxx

Content-Type: application/xml

<?xml version="1.0"?>
[<?wap-pap-ver supported-versions="2.0,1.*"?>]>
<push-message push-id="">
<address address-value="wappush=xxxxxxxxx/"></address>
Content-Type: text/

<?xml version="1.0"?>
<indication href=""
si-expires="2004-06-30T00:00:00Z">You have 4 new emails</
-----------------END EXAMPLE-----------------

Note that the "/" included in the WAP Push address specification is optional for NowSMS v5.50, and will be ignored, as only the relevant destination phone number is parsed from the request.

NowSMS v5.50 will perform XML to WBXML conversions for WAP push of the following content types:

  • text/
  • text/
  • application/vnd.oma.drm.rights+xml
  • text/vnd.wap.emn+xml

Other types (including "application/vnd.wap.mms-message") must be submitted via the appropriate binary encoding.

NowSMS supports the following text values for "X-Wap-Application-id":
  • x-wap-application:push.sia
  • x-wap-application:push.syncml

Other "X-Wap-Application-id" header values must be submitted to NowSMS using their assigned decimal value rather than the text name.

Further information on the WAP Push Access Protocol can be found from by downloading the WAP-247-PAP specification from