Have you encounter a problem where your WAP Push or OTA configuration message displays “Unknown Sender”?
While this occurrence does not result in a loss of functionality, it does appear less that professional. (If you have yet to experience this, send a WAP push message to a SonyEricsson P900, or some of the newer Nokia Series 60 devices.)
NowSMS v5.51 now includes the ability to specify the initiator URI, which some phones will display as the sender of WAP push or OTA configuration messages.
Under the [SMSGW] section header of SMSGW.INI, the setting “WAPPushInitiatorURI=” can be used to set the “X-WAP-Initiator-URI:” header, and “WAPPushFlag=” can be used to the set the “Push-Flag:” header.
In most instances, you will want to set the WAPPushInitiatorURI value to a web URL, including the “http://” prefix, and if only a host name is specified in the URL, include a trailing backslash to avoid problems with some devices (e.g., use “http://www.nowsms.com/”).
The WAPPushFlag can generally be omitted. When specified, values of 1, 2 or 3 are expected. According to the WAP Push protocol, a value of 1 indicates that the initiator URI has been authenticated by the Push Proxy Gateway. A value of 2 indicates that the content of the push is trusted by the Push Proxy Gateway. A value of 3 combines both of these settings.
“WAPPushInitiatorURI=” and “WAPPushFlag=” parameters can also be used in HTTP requests when submitting WAP Push or OMA OTA messages.
Related pages:
- Routing MMS Notifications via a WAP Push Proxy Gateway By default, the NowSMS MMSC expects to be able to send MMS Notification via its built-in WAP Push Proxy Gateway...
- Sending WAP Push Messages Sending WAP Push Messages over HTTP To send a WAP Push message via a menu driven interface, please see the...
- Delivering MMS Notifications with WAP Push over IP The delivery of an MMS message to a mobile device is initially triggered by an MMS Notification message sent from...
- MMS Notifications via WAP PPG By default, the NowSMS MMSC expects to be able to send MMS Notification via its built-in WAP Push Proxy Gateway...
- NowSMS as a WAP Push Proxy Gateway NowSMS v5.50 and later support the WAP Push Access Protocol (PAP) to provide the ability to generate more specialised types...
- NowSMS as a WAP Push Proxy Gateway NowSMS v5.50 and later support the WAP Push Access Protocol (PAP) to provide the ability to generate more specialised types...
- NowSMS Update – Interim Release 2010.05.07 An interim update release of NowSMS is available for download at http://www.nowsms.com/download/nowsmsupdate.zip. The most interesting updated features/capabilities include: Major SMS...
- Using NowSMS as a WAP Push Proxy Gateway (PPG) NowSMS supports the Open Mobile Alliance (OMA) Push Access Protocol (PAP), which allows other applications to use NowSMS as a...
- Send WAP Push from Java (or JSP) The previously posted examples for sending SMS and MMS messages from a Java application with NowSMS can also be used...
- SMPP Connection Types – Sender, Receiver, Transceiver When making a connection to an SMPP server, there are three different types of connections that can be supported. A...
Topic Category: WAP Push
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...

Click here to download a free trial version of NowSMS & MMS Gateway, NowSMS Lite or NowWAP Gateway.
Learn more about NowSMS Lite.