Other “X-Wap-Application-id” header values must be submitted to NowSMS using their assigned decimal value rather than the text name.įurther information on the WAP Push Access Protocol can be found from by downloading the WAP-247-PAP specification from NowSMS supports the following text values for “X-Wap-Application-id”: Other types (including “application/-message”) must be submitted via the appropriate binary encoding. NowSMS will perform XML to WBXML conversions for WAP push of the following content types: Note that the included in the WAP Push address specification is optional for NowSMS, and will be ignored, as only the relevant destination phone number is parsed from the request. X-Wap-Application-Id: x-wap-application:wml.ua The second MIME part is the data to be pushed.Īn example of a service indication push being sent via PAP can be found below: -BEGIN EXAMPLE-Ĭontent-Type: multipart/related boundary=mime-boundary type='application/xml' 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”.Ī PAP post is a multipart MIME request, with the first MIME part being the PAP control document that specifies message recipient(s).

It also becomes possible to send other types of push messages, such as those related to SyncML, Wireless Village, and OMA Digital Rights Management.Īn example of using PAP to send an OMA DRM rights message can be found in the following thread: With support for PAP, NowSMS can be used as a push proxy for other vendor’s MMSCs. 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. NowSMS v5.50 and later support the WAP Push Access Protocol (PAP) to provide the ability to generate more specialised types of WAP Push messages.

Wap 2.0 gateway http post