A recent tech support incident where users were receiving MMS messages with missing text parts of the MMS content had us rather confused.
The customer was using NowSMS as an MMSC, and encountered two devices, the Motorola RAZR V8 and ROKR Z6, which were unable to receive any text content within an MMS message.
As a first step of troubleshooting, we recommended that the customer disable “content adaptation” by the MMSC to determine if the problem was related to content adaptation. (This setting is labeled “Enable Dynamic Image + Audio Conversion” in the MMSC configuration.)
The problem did go away with content adaptation disabled. However, disabling this support was not considered to be a permanent solution for the customer.
Upon further investigation, it was determined that the content adaptation problem was caused by errors in the User Agent Profiles (UAProf files) published by Motorola for these devices. The NowSMS MMSC consults these profiles to determine what content types are supported by the MMS client in the receiving handset. The profiles for these devices included a list of content types supported by the MMS client, but did not include plain text (text/plain) as one of the supported content types.
The NowSMS MMSC caches UAProf files in the UAPROF subdirectory of the NowSMS installation. The user was able to manually edit the motorazrv8.rdf and motorokrz6.rdf files in this directory to add support for the content typle “text/plain”.
The supported MMS content types are listed in the “MmsCcppAccept” section of the UAProf file. Simply adding <rdf:li>text/plain</rdf:li> within this section of the file is all that is necessary to add support for the “text/plain” content type.
Future versions of the NowSMS MMSC will always assume that “text/plain” is a supported content type within MMS messages, even if there is an error in the UAProf file published by the handset manufacturer.
Related pages:
- Small Image Size in Received MMS A recent posting on our disucssion board got me thinking. The question was asking about how when the customer receives...
- Routing MMS Notifications via a WAP Push Proxy Gateway By default, the NowSMS MMSC expects to be able to send MMS Notification via its built-in WAP Push Proxy Gateway...
- MMS Notifications via WAP PPG By default, the NowSMS MMSC expects to be able to send MMS Notification via its built-in WAP Push Proxy Gateway...
- NowSMS in Fault Tolerant or Redundant Load Balanced Environment For many configurations it is desirable to install NowSMS on multiple servers in order to achieve fault tolerance and/or improved...
- 2-Way MMS Support Support for processing received MMS messages is slightly more complex than received SMS messages, because the content of MMS messages...
- High Availability Environments For many configurations it is desirable to install NowSMS on multiple servers in order to achieve fault tolerance and/or improved...
- NowSMS Features NowSMS supports a wide range of SMS and MMS protocols, and simultaneous connectivity to multiple SMSC and/or MMSC connections. Applications...
- Creating MMS Message Files Creating MMS Message Files – MMSCOMP The over-the-air MMS message file format is a binary file format, and special tools...
- Migrating to a Multiple Server MMSC, WAP Gateway, or NowSMS Gateway The recent postings about multiple server redundant NowSMS or NowWAP configurations have generated a lot of questions from existing customers...
- Send MMS from the Command Line Last time, I posted a Windows JScript file that could be used to enable the sending of OMA Client Provisioning...
Topic Category: content adaptation, operator MMSC
For comments and further discussion, please click here to visit the NowSMS Technical Forums (Discussion Board)...
Click here to download a free trial version of NowSMS & MMS Gateway, NowSMS Lite or NowWAP Gateway.
Learn more about NowSMS Lite.