MMS Image autoconversion issue with SonyEricsson T630

Author

Message

janek shein
Unregistered guest

Posted on Thursday, August 04, 2005 - 04:11 pm:

Hello.

I have stumbled accross very mysterious issue. Namely, if the image resize is on and if the message comes in from MM4 (haven't been able to test MM7), then SonyEricsson's T630 reports it as "damaged" and fails to open the message. It doesn't matter if it resizes to the screen size or max supported size.

There is no issue if the autoconversion is turned off. Also, if the message is delivered locally, the image seems to be converted fine and the handset has no problem receiving it. Other handset models seem to receive this type of image fine, regardless of the message being MM4 or local.
Also, according to the reports i received, various T630 software versions were tested and all of them suffer from this same issue.

Will provide tcp traffic dumps and mmsc debuglogs if needed.

Hoping for a prompt reply.
Thanks in advance,
Janek Shein
Elisa / Estonia

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4731
Registered: 10-2002

Posted on Wednesday, August 10, 2005 - 07:30 pm:

Hi Janek,

Apolgies for the delay in response.

We've had a few similar reports from different customers about this issue.

Oddly enough, they've all just surfaced in the last 2 weeks...which is odd, because the SE T630 has been out for over a year now. (In fact, I used one as my primary phone for several months last year, and never had a problem.)

In the other cases, a Samsung phone was on the sending side, and no external MM4 connections were involved.

We believe the problem is that under certain conditions the reference to the SMIL file gets lost in the MMS header during content conversion. The SMIL content remains in the message after content conversion, but it is not pointed to in the message header. And this seems to cause problems for some clients.

In the other instances, a Samsung phone on the sending end seems to trigger the problem.

But it is possible that a message input via MM4 might have similar characteristics, depending on how the headers are generated by the MM4 partner.

We are currently testing a fix (v5.51d), which we were planning to upload overnight. So it should be up there in a few hours. I'm going to guess that it will also resolve this problem, and I'll post a note here when the update is available for download.

-bn