What is 3GPP?
MMS is specified by 3GPP, and allows for submission and reception of multiple content types (e.g. video, audio, images, text) to and from a mobile device. MMS is a store and forward medium that takes advantage of a carrier’s MMSC to store a MMS message for retrieval via a handset, as well as accept messages from handsets for on forwarding to another device. Telstra MMS is a store and forward messaging service that allows mobile subscribers to exchange messages with integrated text, audio & images. MMS allows for a variety of message content types, including moving or still images, sound and text to be originated or terminated using a compatible MMS mobile handset. MMS message are uploaded (via HTTPsPost) or downloaded (via HTTPs-GET) from/to the handset using HTTP/WSP or a WAP connection. The handset is required to be correctly configured for GPRS or 1xRTT for MMS to correctly function Message delivery is accomplished by sending an SMS message to the device (known as a WAP-Push) that will inform the device that it needs to collect a message from a specified URL (which is the MMSC). The handset will then initiate a data session to collect the message and display it on the handset. Part of the role of the MMSC is to convert the message being delivered to the handset upon retrieval so that only valid and supported content types are delivered to the handset.
There are several specific protocols supported by the 3GPP specifications for message submission and reception. For 3rd party VASP access the protocol supported by Telstra is MM7. The MM7 protocol is an open standard protocol designed by 3GPP to provide a flexible data-communications interface for the transfer of MMS messages. It has been specifically designed to enable external applications to communicate with an MMS Centre. Telstra’s MMSC supports MM7 version 5.3.0, although higher versions should function however, the functionality is not guaranteed. For a more comprehensive discussion of the MM7 protocol please refer to the specification at: http://www.3gpp.org/
Supported file formats
In order to reliably deliver a message to the majority of handsets it is recommended that you use the following file formats. In each case the correct MIME type for the format is given in parentheses. The correct MIME type must be used in order to ensure the message is accepted by Telstra.
• JPEG, JPG (image/jpeg): good support
• GIF: GIF87a, GI89a, animated GIF89a (image/gif): good support
• PNG (image/png): good support
• WBMP (Wireless Bitmap) (image/wbmp): this is B&W image format from the old days of
• WAP: good support.
• BMP (Windows Bitmap) (image/bmp): dependent on handset support
• MP3 (audio/mpeg): partial support; some handsets may limit the use of the file due to DRM concerns by the manufacturer
• MID, MIDI (audio/mid or audio/midi): good support
• WAV (audio/wav): good support
• AMR (audio/amr): partial support, GSM handsets only; CDMA handsets will require the B-party MMSC to transcode to EVC format or store on Web site for PC-based retrieval
• IMY, EMY (audio/imelody) : partial support
• EVC: not currently supported
• AAC: not currently supported • Video • MPEG, MPG, MP4 (video/mpeg4): support may vary by handset
• 3GP (video/3gpp): good support
• TXT, TEXT: UTF-8, US-ASCII (not UTF-16) (text/plain): good support.
• X-IMELODY (text/x-imelody) – partial to good
• X-EMELODY (text/e-melody) – partial to good
Note that Telstra’s infrastructure will endeavour to transcode files to a format supported by the end device.
In order to use the product, the source address must be a legitimate MSISDN (e.g. 61499999999), the destination address may be an MSISDN or compatible format.