52.24.3 MMS Send

Sends an MMS.
When composing an MMS script controlling both sender and receiver, it is best to use a Parallel structure. See sections "Parallel Activities" and "Parallel".
If logging in to the MMS Center requires connecting to a different APN than the one used for data services, the MMS Send activity must be preceded by a "Network Connect" activity specifying the MMS APN. Of course, if the device is going to execute data services later on, the device must first switch back to the data service APN by doing Network Disconnect and then another Network Connect.

Configuration property:

Connection and Gateway sections
These are WAP settings, the same as for the WAP Get activity; see section "WAP Get".
MMS Content section

To: The phone number(s) or email address(es) to send the MMS to. Multiple recipients can be specified, separated by semicolons. The receiving device can be identical with the sender.

Text of MMS Message: Free text field containing the text message of the MMS (if any).

File to Attach to the MMS: The file to send. A wide variety of file types, including plain-text files and frequently used image file formats, is supported. A file with an extension unknown to TEMS Investigation will be sent as an attachment to the MMS (content type "application/octet-stream").

Please note that operators generally impose a limit on the MMS file size. If you encounter problems sending MMS messages, try sending very small files to find out whether the size limit is causing the problem.
MMS Message Center section

URL: The URL of the MMS Center (usually beginning with http://).

User, Password: Login credentials for MMS Center, if required.
Proxy section: WAP proxy, optionally used for Connection Mode = WP-HTTP; see the "WAP Get" activity.
Lists of MMS send information elements and events.
Limitations
When an Android device is connected in tethered mode, it cannot send MMS messages unless the data service APN is used for MMS send as well. This is due to a limitation in Android devices.