The aql® mms gateway allows developers to send pre-encoded MMS URLs to compatible handsets. Not all functionality may be supported by the destination handset, and functionality is typically limited to Text, Image and Audio files. Most MMS messages require 1-2 SMS Credits, depending on their size, and may incur charges for the receiver depending on their network plan.
In order to send a message using the gateway, you will need to send a request to one of the following:
The URI-Encoded variables that you will need to pass are:
Obligatory
Optional
Response Codes
GW-NO_AUTH_DETAILS - No username or password were provided
GW-AUTH_ERROR - The username and password you provided could not be validated
GW-NO_EXPIRY - You did not provide an Expire time in days
GW-NO_MMSURL - You did not provide a MMS URL (location of .mms file)
GW-NO_SUBJECT - You did not provide a Subject for the notification
GW-NO_CLASS - You did not provide a Message Class for the notification
GW-NO_CREDIT - Your account does not have sufficient credit
GW-NO_DESTINATION - You did not provide a destination number
GW-INVALID_DESTINATION - The destination number you provided was invalid
GW-INVALID_ORIGINATOR - The originator you provided was invalid
GW-INVALID_CLASS - The message class you provided was invalid (must be either
80,81,82 or 83)
GW-INVALID_EXPIRY - The expiry you provided was invalid (must be a number
without decimal points)
GW-INVALID_FILESIZE - The filesize you provided was invalid (must be size
of mms binary in bytes)
GW-OK:?? - The message was queued successfully, and ?? is the number of messages
used, ie. 2
GW-ERROR:?? - The message failed. ?? is the number of messages that failed,
ie. 1
GW-MSGERROR - There was an error encoding the push message. Please check the
wap url / wap name
GW-QUEUE_ERROR - There was a queue error, please contact support with the
details of the message you attempted to send
