Customizations for SMS and MMS
Contains settings that you can configure for SMS and MMS.
In this section
Partners can extend the set of supported SMS encodings.
For MMS messages that have photo attachments and that fail to send, partners can choose to automatically resize the photo and attempt to resend the message.
Partners can configure the messaging app to automatically retry downloading an MMS message if the initial download attempt fails.
For networks that require it, partners can specify the default GET path within the MMSC to use when the GET URL is missing from the WAP push MMS notification.
If an SMS message fails to send correctly, partners can specify the number of additional attempts and the minimum delay between them in seconds.
Partners can disable the enhanced messaging service (EMS), which concatenates text messages so that the user can enter more than 160 characters in a single message.
Partners can set the expiration time before the device deletes the received parts of a long SMS message.
Partners can choose to display additional content in the conversation view when an SMS or MMS message fails to send.
For networks that support it, when an outgoing SMS message fails to send due to a transient error, partners can specify the threshold for the number of attempts to resend the SMS over IMS before switching over to 3GPP or 3GPP2.
For networks that require it, MMS messages can include the IMSI in the GET and POST header that the message center uses to authenticate the mobile subscriber.
Partners can specify a maximum length for SMS messages.
Partners can specify the maximum number of attachments for MMS messages, from 1 to 20.
Partners can set the maximum number of recipients to which a single SMS or MMS message can be sent.
Partners can mark SMS message failures as permanent failures so that the user will not be given the option to attempt to resend the SMS.
Partners can specify one or more ports from which the device will accept cellular broadcast messages.
Partners can specify the use of NAI information as a dedicated header for MMS authentication for mobile networks that require this functionality. The string value must be the MMS header used for authentication.
Partners can show the select all contacts/unselect all menu option to allow users to easily select multiple recipients for an SMS or MMS message.
Partners can configure SMS messages to be sent to email addresses as well as phone numbers.
By default, the MMS transport sends an acknowledgement to the MMS application server (MMSC) provisioned by following the instructions in MMS application configuration.
Partners can change the default GSM 7-bit code page decoding and encoding, and can also extend the set of supported SMS encodings by setting an "always-on" GSM 7-bit shift table, adding encoders, and adding decoders.
OEMs can specify one or more filters in order to intercept incoming SMS messages intended for mobile operator partner applications that are not installed on the device.
OEMs can configure ports on which a Wireless Application Protocol (WAP)-formatted message can be intercepted by the mobile operator app.
For networks that require it, OEMs can add support for the HTTP header Cache-Control No-Transform directive for MMS messages.
Partners can add additional supported protocols for service indication messages.
For networks that do support MMS and do not support segmentation of SMS messages, partners can specify an automatic switch from SMS to MMS for long messages.
For networks that require non-standard handling of single-segment incoming MMS WAP Push notifications, partners can specify that MMS messages may have some of their content truncated and that they may require special handling to reconstruct truncated field values.
To meet certain mobile operator requirements, OEMs can customize the OS image to use either the insert-address-token or the local raw address for the From field in MMS messages.
Some incoming MMS messages may not specify a character encoding. To properly decode MMS messages that do not specify a character encoding, OEMs can set UTF-8 to decode the message.
Partners can specify a user agent profile to use on the device for MMS messages.
Partners can replace the entire user agent string for MMS.
Partners can hide the user prompts for signal-medium messages.
Partners can specify the transcoding to use for video files sent as attachments in MMS messages.