SMS Gateway
MMS Gateway
Zip file contents
MX Telecom uses zip files to send and receive the multimedia files for MMS messages. Bundled in the zip file should be:
- the files that make up the MMS message (image, audio, video, animation, Java, polyphonic and text files)
- an optional SMIL file used to format the MMS
- a manifest file named
manifest
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 that the message display is properly time coordinated and synchronised.
The manifest file contains the mapping from Content-Id
to Mime-Type for each file in the MMS. For example,
if the following files are in the zip file:
demo.sml
demo.mid
demo.gif
demo.txt
then the following mapping must be in the manifest file:
demo.sml=application/smil
demo.mid=audio/midi
demo.gif=image/gif
demo.txt=text/plain
The manifest file also sets the order that the files are sent to the end user. If you are using a SMIL file to describe how the MMS should flow, then the order does not matter. If you are not using a SMIL file, then the end user receives each item in the MMS in the same order as within the manifest.
The manifest file must use Java properties format. For example, commented lines should begin with a # while other non-whitespace lines will be of the form key=value.
An example zip file containing a manifest, a SMIL file and multimedia files can be found here.
Note that text files in the MMS message must use UTF-8 character encoding. If text is not encoded correctly, then it may fail to display correctly or the MMS message may not be delivered.
