Push MMS MO message to Http Post Service

Our service will push All Message Received via the Telstra Message Service to an http POST service hosted by the Customer. This includes both SMS and MMS.

If requires a Default forwardto record/keyword type of URL and with the customer's service URL to be setup by Support. URL should be the full service address with no parameters included.

message structure is application/json and the raw body contains a JSON string of the following structure:

Body Content in Json String

Field Name	Type	Example/Notes
status	string	Will alway be "ACCEPTD"
to	string	international format of the MSISDN the message was sent to eg your virtual mobile number
from	string	international format of the MSISDN the message was sent from - mobile handset number.
subject	string	max 61 characters - message subject as written by the handset owner. this value is empty for SMS messages
body	string	body text of the MMS message
MMSContent	List<MMSContent>	List of message file content. Will either of an array of zero or one. We only record and store one message file content per message.

MMSContent

Field Name	Type	Example/Notes
Type	string	MIME content type of the file eg "image/jpeg"
Filename	string	filename for the image
Payload	string	file payload is base64encoded image byte[] data expressed in string format.

JSON Example

{
	"status":"ACCEPTD",
	"to":"61400001001",
	"from":"61419001001",
	"subject":"This is my subject",
	"body":"MMS message body",
	"Payload":
		[
			{
				"Type":"image/jpeg",
				"Filename":"NewImage.jpeg",
				"Payload":"/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwkHBgoJCAkLCwoMDxkQDw4ODx4WFxIZJCAmJSMgIyIoLTkwKCo2KyIjMkQy....."
			}
		]
}

for SMS messages Payload will be "Payload":[]