Sending MMS

Overview

The MX Telecom MMS Gateway allows MMS messages to be sent and received using an HTTP interface. For partners familiar with Nokia's EAIF framework, an EAIF interface is also available.

Using the Bulk Operator MMS Service, MMS messages are sent from the MMS Gateway through MX Telecom's direct connections to the UK mobile operators, before being routed to the end user. Messages will always be routed on-net where possible.

Any MMS messages that are unable to be delivered to the end user straight away (for example, because the handset is switched off or is not within network or GPRS coverage) are stored at the mobile operator's MMS Centre (MMSC), with repeated attempts made to deliver the message to the end user.

Limited delivery reports are currently available for MMS messages sent on- net - i.e. they are only available for messages sent to networks with which MX Telecom has direct connections. If the originator address/field of the MMS message sent is alphanumeric or is not pre-registered as an MSISDN or Short Code, then delivery reports are not available for both on-net and off-net sending of messages.

With the Bulk Operator MMS Service, the end user does not pay for downloading the received MMS. The GPRS fees are covered by the content provider in the overall cost of the service.

The Bulk Operator MMS Service covers all the main UK mobile networks.

Content purposing for Operator MMS messages is done by the mobile operators' MMSCs, ensuring an image that makes up part of an MMS message is the correct size for a particular handset.

Process of sending Operator MMS

Bulk Operator MMS messages can be sent to the MX Telecom MMS Gateway through the use of HTTP requests. They are then routed through several mobile operators' MMSCs before being delivered to end users' handsets.

Technical Setup

MMS messages can be sent through the MX Telecom MMS Gateway by making HTTP GET or Multipart POST requests.

Using the HTTP interface to send MMS, the .zip file contains the .smil file and each of the associated files of the different parts of the MMS, such as .gif and .jpeg files (the actual content of the MMS), along with a manifest file which describes the contents of the file, and parameters such as the mobile phone number and the originator address.

The .smil file controls the layout of the MMS (similar to html) and this is what is used to format the message. It pieces together the MMS files into the order that the end user sees, and combines them into a single stream (so the message display is properly time coordinated and synchronised).

When submitting an HTTP GET or Multipart POST request to send an MMS, it is possible to send the MX Telecom MMS Gateway a URL to the .zip file, instead of submitting the .zip file itself.

The Bulk Operator MMS Service involves a real time Network Lookup to determine the correct network of the end user's handset for each MMS message sent, in order to route the MMS message on-net where possible.

An EAIF interface is also available for sending and receiving MMS messages.

Benefits of Operator MMS

  • The cost to the end user for receiving a Bulk Operator MMS message is zero, as they do not have to pay for downloading received MMS messages (in the same way as peer to peer messaging, where there is no cost to the end user receiving a message)

  • The Bulk Operator MMS Service is available for all of the main UK networks

There are, however, some technical problems associated with MMS. For further details, see Known Issues with MMS.

Pricing

Full details on the Bulk Operator MMS Service Pricing can be seen here.

For more information, please contact us at 0845 666 7778 or via email at sales@uk.openmarket.com.