The transactionID associated with the message. Making this unique per request should help with the request tracking within the system.
\@mustUnderstand should be set to 1.
\@actor and \@encodingStyle should not be set.
|No||Not used. Authentication is based on the Authorization header value.|
|VASID||No||Not used. Authentication is based on the Authorization header value.|
|Yes||The shortcode that is sending the MT MMS message. This value is required by the Vibes MMSC (even though the specification says it is optional).|
The shortcode should be wrapped in a <ShortCode> element.
The MDN to deliver the MMS to.
The MDN can be formatted as 10 digit, 11 digit, or e.164 format.
The MDN should be wrapped in a <Number> element.
The Number element should be wrapped in a <To> element.
Multiple MDNs are not supported.
The <Cc> and <Bcc> elements are not supported.
The displayOnly flag will not be used because the Vibes MMSC only allows one recipient per message.
|ServiceCode||No||Not supported, do not set.|
Not supported, do not set.
The type of message. The allowed values are:
Informational is the default.
|Timestamp||No||Not supported, do not set.|
|ReplyCharging||No||Not supported, do not set.|
|EarliestDeliveryTime||No||Not supported, do not set.|
|ExpiryDate||No||Not supported, do not set.|
Flag to request delivery reports for this MT MMS message.
If true, at least one DeliveryReportReq request callback requests will be posted to the client-specified URL sometime after the request has been received for any Delivery Receipts received from the carrier. It It defaults to to false.
If this flag is set to true, then the X-Vibes-DlrCallbackUrl custom header should have the URL to which Delivery Reports should be sent, or else the request will be rejected.
|No||Flag to request read replies. If true, at least one ReadReplyReq request will be posted to the client-specified URL sometime after the request has been received. It defaults to false.|
|No||The importance of the message: Normal, High, or Low.|
|No||Free-text to be displayed as the title of the message on the handset.|
|ChargedParty||No||Not supported, do not set.|
|ChargedPartyID||No||Not supported, do not set.|
|No||The flag on whether to allow message forwarding from the phone. Defaults to false.|
|DeliveryCondition||No||Not supported, do not set.|
|ApplicID||No||Identification information for the destination application on the handset. If set, this information will be passed through to the carrier.|
|ReplyApplicID||No||Identification information for the application which will handle delivery reports, read-reply reports and reply-MMS. If set, this information will be passed through to the carrier.|
|AuxApplicInfo||No||Additional application/implementation specific control information. If set, this information will be passed through to the carrier.|
Classification information for the message content. If set, this information will be passed through to the carrier.
The possible values are: text, image-basic, image-rich, video-basic, video-rich, megapixel, content-basic, content-rich.
|DRMContent||No||The Boolean flag indicating if the content of the message is DRM protected.|
|Content||No||This value is required by the Vibes MMSC (even though the spec says its optional).|
A String reference to the content contained within the message.
|allowAdaptations||No||Allow the content to be adapted for the phone by the carrier MMSC. This is set to true by default.|