Message Received via MM4 shows SMIL corruption on phone.

Message Received via MM4 shows SMIL corruption on phone. SearchSearch
Author Message
Joseph Smith
New member
Username: Falangjoe

Post Number: 15
Registered: 08-2006
Posted on Monday, April 19, 2010 - 04:29 pm:   

Union Telephone v2009.07.09

When we receive MMS messages via MM4 from some Verizon phones, they will not display on a subset of our handsets. The handsets that they do not display on include sonys and the pantech duo. The pantech duo shows SMIL corruption. On the pantech duo, if you do some tricks, you are able to view the picture in the message. I was wondering if you could see what if anything is wrong with these messages. I have include the message and a trace of the message as it comes in.

Thanks,
Joseph
application/octet-streamMessage
6B631F4B.MMS (62.9 k)
application/octet-streamTrace
MMSCDEBUG.LOG (92.1 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2022
Registered: 08-2008
Posted on Monday, April 19, 2010 - 06:08 pm:   

Hi Joseph,

The problem is that the "Content-Location:" header is not valid.

Specifically:

Content-location: No Name_2.smil

and:

Content-Location: No Name_1.txt

Our interpretation of the relevant MIME specification (RFC2557?) is that a space character is not valid here.

I don't think the sending phones themselves are the problem ... instead it looks like some sort of message parser/reformatter in the MMSC message path that is deciding to insert this "No Name" nonsense.

That said, we hate finger pointing about problems like this. We'd rather be tolerant of problem situations, so we are preparing an update that will be tolerant of this.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2038
Registered: 08-2008
Posted on Wednesday, April 21, 2010 - 06:11 pm:   

Hi Joseph,

An updated build of NowSMS is available at the following link:

http://www.nowsms.com/download/nowsmsrc.zip

This update will accept "Content-Location:" headers that include a space character.

--
Des
NowSMS Support
Joseph Smith
New member
Username: Falangjoe

Post Number: 16
Registered: 08-2006
Posted on Thursday, April 22, 2010 - 10:19 pm:   

Desi,

This update did not fix the problem. The pantech still can't display new messages from the Verizon phone. It still shows SMIL corruption.

I submitted a ticket a ticket with our intercarrier MMS provider to see if they can get rid of this "No Name" stuff.

Thanks,
Joseph
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2041
Registered: 08-2008
Posted on Friday, April 23, 2010 - 01:48 pm:   

Hi Joseph,

Did it fix the problem with one of the handsets that was having problems before?

Previously, the confusion was causing us to lose the SMIL, and point to the text as the SMIL .... which would definitely be SMIL corruption.

I've rechecked the binary MMS message that gets created as a result of the MM4 content, and I don't see any structure problems.

The only thing that seems like a potential problem is the spaces in the "Content-Location:" header. The SMIL includes the following reference:

<text src="No Name_1.txt" region="Text" >

I'm guessing that maybe the MMS client in this device is having problems resolving "No Name_1.txt".

I'd like to try to confirm this, however.

Here are two MMS messages based upon your original test. I'd like you to try sending these messages via the "Send MMS Message" page in the NowSMS web interface. Include them as a single content file for two separate messages.

application/x-zip-compressedmms_test.zip
mms_test.zip (125.9 k)


test1.mms includes space characters in content-location headers.

In test2.mms, I've replaced the spaces in content-location headers (and referencing SMIL) with "_" characters.

If a space character is causing a problem for the receiving client, this should tell us.

--
Des
NowSMS Support
Joseph Smith
New member
Username: Falangjoe

Post Number: 17
Registered: 08-2006
Posted on Friday, April 23, 2010 - 04:04 pm:   

Desi,

The patch did not fix it for the Sony phones or the pantech duo.

Both Test1 and Test2 were ok on the Pantech. I could view the picture and did not get the SMIL corruption on either. I sent them seperately to the phone.

I attached a message that was received with the updated version of nowsms. When I send it via the web interface it show the SMIL corruption problem on the pantech and sony's.

Thanks,
Joseph
application/octet-streamMessageAfterPatch
8D90850F.MMS (48.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2044
Registered: 08-2008
Posted on Friday, April 23, 2010 - 04:29 pm:   

Hi Joseph,

You're seeing different results than I am. The content-location headers with space characters are being truncated at the space in your sample message.

I'm going to do some more testing and investigation, but can you please double check that your version has been updated to 2010.04.19.

--
Des
NowSMS Support
Joseph Smith
New member
Username: Falangjoe

Post Number: 18
Registered: 08-2006
Posted on Friday, April 23, 2010 - 04:36 pm:   

The updated version shows v2009.06.11. I was confused because this is older that the one we were currently using.

Thanks,
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2045
Registered: 08-2008
Posted on Friday, April 23, 2010 - 04:48 pm:   

If you manually retyped the link, you might have missed the "rc" in the filename:

http://www.nowsms.com/download/nowsmsrc.zip
Joseph Smith
New member
Username: Falangjoe

Post Number: 19
Registered: 08-2006
Posted on Friday, April 23, 2010 - 04:54 pm:   

I download the correct one, but installed the old one. I will try this again and get back to you.

Thanks,
Joseph
Joseph Smith
New member
Username: Falangjoe

Post Number: 20
Registered: 08-2006
Posted on Monday, April 26, 2010 - 06:14 pm:   

Desi,

The update fixed the problem.

Thanks,
Joseph