Topic Keywords: API, multimedia push, WAP Push
One of the ways that NowSMS can be used for multimedia content delivery is a service that we refer to as Multimedia Content Push (also referred to as Multimedia WAP Push).
When you send a Multimedia WAP Push message with NowSMS, you post all of the message content (e.g., images, video, text, applet) to the NowSMS server. NowSMS packages the content and dynamically generates a URL on the NowSMS server. A WAP Push message is then sent which includes a link to the content.
To send a Multimedia WAP Push message via NowSMS, the same APIs are used as for sending an MMS message, with a special flag set to indicate that the message should be sent out as a Multimedia WAP Push instead of as an MMS message. The subject of the message is used as the text in the WAP Push, and the remainder of the content is packaged into the dynamically generated URL that accompanies the WAP Push message.
NowSMS 2009 also supports a concept of Multimedia Content Push where the push is sent via a text SMS instead of using WAP Push. The concept is similar to Multimedia WAP Push, except that the message that is sent to the recipient is a standard text message.
This alternative is useful in environments where WAP Push is not supported (such as environments where there is a mix of GSM and CDMA technologies), or where binary messaging required by WAP Push is more expensive than standard text messaging. It is also useful for delivering content to devices that do not support WAP Push, such as the Apple iPhone.
The article will explain how the Send MMS APIs for NowSMS are adapted to support Multimedia Content Push.
The APIs for sending MMS messages are described in the following link:
PHP:
Follow the example described at https://nowsms.com/nowsms-php-example-send-mms-message
To send a Multimedia Content Message using WAP Push, add this line before calling MmsSend:
$mmsMessage = MmsAddField ($mmsMessage, “MMSWAPPush”, “Yes”);
To send a Multimedia Content Message using Text SMS, add this line before calling MmsSend:
$mmsMessage = MmsAddField ($mmsMessage, “MMSSMSPush”, “Yes”);
Java:
Follow the example described at https://nowsms.com/nowsms-java-example-send-mms-message, but include the following additional parameter setting when building the MMS message to send the message via WAP Push:
mms.addparameter (“MMSWAPPush”, “Yes”);
Or this parameter setting when building the MMS message to send the message via text SMS:
mms.addparameter (“MMSSMSPush”, “Yes”);
Command Line Interface:
Follow the example described at https://nowsms.com/sending-mms-from-the-command-line, but include the following additional parameter in your command line to send the message via WAP Push:
MMSWAPPush=Yes
Or include this additional parameter to send the message as a URL link via text SMS:
MMSSMSPush=Yes
NowSMS Proprietary URL Submission
Follow the example described at https://nowsms.com/sending-mms-messages-with-nowsms.
Include the following additional variable setting to send the message via WAP Push:
MMSWAPPush=Yes
Or include this additional variable setting to send the message as a URL link via text SMS:
MMSSMSPush=Yes
This additional variable setting can be included in the URL (e.g., &MMSWAPPush=Yes), or it can be included as a variable setting in part of the multipart/form-data.
MM7
Follow the MM7 example described at https://nowsms.com/sending-mms-messages-with-nowsms.
Append “/TYPE=WAPP” to the recipient phone number to send via WAP Push or “/TYPE=SMSP” to send as a URL link via text SMS.
MM4/SMTP
Follow the MM4 example described at https://nowsms.com/sending-mms-messages-with-nowsms.
Append “/TYPE=WAPP” to the recipient phone number to send via WAP Push or “/TYPE=SMSP” to send as a URL link via text SMS.
MM1
Multimedia Content Push is not supported via the MM1 Interface, unless the default outbound route for MMS messages is to use “Multimedia WAP Push” (“WAP Push with Web Link”) or “SMS with Web Link (Direct)”. In this case, MMS messages will be automatically converted to the format specified by the outbound route.
EAIF
Multimedia Content Push is not supported via the EAIF Interface, unless the default outbound route for MMS messages is to use “Multimedia WAP Push” (“WAP Push with Web Link”) or “SMS with Web Link (Direct)”. In this case, MMS messages will be automatically converted to the format specified by the outbound route.
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...