Table of contents
TOC
Collapse the table of content
Expand the table of content

Customizations for SMS and MMS

Last Updated: 12/12/2016

Contains settings that you can configure for SMS and MMS.

In this section

TopicDescription

Add encoding extension tables for SMS

Partners can extend the set of supported SMS encodings.

Automatic send retry and resize settings for MMS messages

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.

Automatically retry downloading MMS messages

Partners can configure the messaging app to automatically retry downloading an MMS message if the initial download attempt fails.

Content location in the multimedia message service center (MMSC)

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.

Delay for resend attempts

If an SMS message fails to send correctly, partners can specify the number of additional attempts and the minimum delay between them in seconds.

Disable the EMS long messages feature

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.

Expiration time for SMS messages

Partners can set the expiration time before the device deletes the received parts of a long SMS message.

Full error messages for SMS and MMS

Partners can choose to display additional content in the conversation view when an SMS or MMS message fails to send.

IMS retry

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.

IMSI authentication

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.

Maximum length for SMS messages

Partners can specify a maximum length for SMS messages.

Maximum number of attachments for MMS messages

Partners can specify the maximum number of attachments for MMS messages, from 1 to 20.

Maximum number of recipients for SMS and MMS

Partners can set the maximum number of recipients to which a single SMS or MMS message can be sent.

Permanent SMS message failures

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.

Ports that accept cellular broadcast messages

Partners can specify one or more ports from which the device will accept cellular broadcast messages.

Proxy authorization for MMS

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.

Select multiple recipients for SMS and MMS messages

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.

Sending SMS messages to SMTP addresses

Partners can configure SMS messages to be sent to email addresses as well as phone numbers.

Server for MMS acknowledgement messages

By default, the MMS transport sends an acknowledgement to the MMS application server (MMSC) provisioned by following the instructions in MMS application configuration.

SMS encoding

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.

SMS intercept deny list

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.

SMS intercept ports

OEMs can configure ports on which a Wireless Application Protocol (WAP)-formatted message can be intercepted by the mobile operator app.

Support HTTP cache-control no-transform for MMS

For networks that require it, OEMs can add support for the HTTP header Cache-Control No-Transform directive for MMS messages.

Supported protocols for service indication messages

Partners can add additional supported protocols for service indication messages.

Switch from SMS to MMS for long 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.

Truncated content handling for WAP push notification

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.

Use insert-address-token or local raw address

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.

Use UTF-8 for MMS messages with unspecified character encoding

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.

User agent profile for MMS messages

Partners can specify a user agent profile to use on the device for MMS messages.

User agent string for MMS messages

Partners can replace the entire user agent string for MMS.

User alert for service indication messages

Partners can hide the user prompts for signal-medium messages.

Video attachments in MMS

Partners can specify the transcoding to use for video files sent as attachments in MMS messages.

Send comments about this topic to Microsoft

© 2017 Microsoft