Error parsing SMIL header

Error parsing SMIL header SearchSearch
Author Message
Jon Berres
New member
Username: Jberres

Post Number: 5
Registered: 04-2009
Posted on Tuesday, March 02, 2010 - 09:34 pm:   

Hi

We are having problems with MMS sent over our outgoing VASP route to another carrier. They are unable to parse the SMIL header portion of the MMS. At this time it seems to only effect LG phone which are on the receiving end. Below is an example of the problem, as you can see "3D" is getting added to the fields in the header:

Original SMIL header...


<smil><head><layout><root-layout width=3D"502" height=3D"288"/><region id=3D"Image" w=

idth=3D"366" height=3D"275" top=3D"7" left=3D"68" fit=3D"meet"/></layout></head><body><pa=
r dur=3D"5000ms"><img region=3D"Image" src=3D"02112010.jpg"/></par></body></smil>


Is this a bad library that is causing this? I'm not sure the purpose of the "3D" characters, if they are even valid. But LG phone specifically do not like this.

Attached is a document with some additional information. If you have any ideas on what causes this I would appreciate it.

Thanks again,
Jon

text/plain
Results.txt (4.3 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1897
Registered: 08-2008
Posted on Tuesday, March 02, 2010 - 09:57 pm:   

Hi Jon,

That is quoted printable encoding. Because MM4 uses SMTP as a transport, it needs to follow some SMTP rules, especially with regard to file content that doesn't include line breaks. (Some SMIL clients generate SMIL that doesn't include any line breaks.)

We have seen that this can cause problems for MM4 interoperability, particularly in the US. (We should probably consider making the configuration parameter that I describe below a default setting.)

There is a configuration setting that exists in version 2009.06.11 and later (latest at http://www.nowsms.com/download/nowsmsupdate.zip) to disable the use of quoted-printable transfer encoding.

Edit the MMSC.INI file, and under the [MMSC] header, add MM4QuotedPrintableOK=No

It is necessary to restart the MMSC service after applying this setting in order for the setting to take effect.

--
Des
NowSMS Support
Jon Berres
New member
Username: Jberres

Post Number: 6
Registered: 04-2009
Posted on Tuesday, March 02, 2010 - 10:30 pm:   

Thanks Des, I'll give that a try.
Jon Berres
New member
Username: Jberres

Post Number: 7
Registered: 04-2009
Posted on Wednesday, March 03, 2010 - 07:20 pm:   

Hi Des,

I did the upgrade and everything is running fine. I was just wondering if this is according to the MM4 spec? Are some phones not following the spec correctly and thats why we need to set the MM4QuotedPrintableOK setting?

I just want to understand better why some phones have problems with this, and if by setting "MM4QuotedPrintableOK = no" we will break something in the future.

Thanks again,
Jon
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1902
Registered: 08-2008
Posted on Wednesday, March 03, 2010 - 08:44 pm:   

Hi Jon,

It's not really a phone issue, it's an MMSC issue.

It has to do with the content encoding and decoding that occurs when the message is transferred via MM4.

In this case, the message is not being properly decoded.

It has nothing to do, at least directly, with the mobile phone MMS clients.

Slightly unusual behaviour in the sending phone triggers the NowSMS MMSC to use a standard Content-Transfer-Encoding (quoted-printable) that the receiving MMSC appears to not understand. As a result, the message is mangled.

This configuration setting enables some additional logic to reformat the SMIL so that quoted-printable encoding can be avoided.

I don't expect any concerns with your using this setting. In fact, I'm recommending to our engineering team that this setting be enabled by default in future versions.

Initially, this setting was implemented as a quick fix for a user experiencing a specific problem. In case there was a problem with the fix, we wanted to be cautious about it, until it saw more real world testing.

I've had enough customers implement this setting that I'm confident in recommending it.

All this setting does is insert line breaks into SMIL content when transferring it across MM4, if the client didn't use line breaks. There is no requirement that SMIL client use or not use line breaks, so it is an inconsequential transformation.

--
Des
NowSMS Support