MM4 and Transcoding

MM4 and Transcoding SearchSearch
Author Message
Joseph Smith
New member
Username: Falangjoe

Post Number: 7
Registered: 08-2006
Posted on Monday, September 11, 2006 - 06:33 pm:   

I was testing sending MM4 between two instances of the Now SMS/MMS gateway. Several phones had a problem receiving by MM4 with trancoding turned on. They were the LG1440i, LG2000, SONY w300i, and Samsung SGH-x496. I did not have problems with the Nokia and Motorola phones that I tested.

When the messages are not sent by MM4, all the phones work with trancoding.

I saw a previous post on this problem, and there was a patch for it. I am currently using version v2006.03.09.
Joseph Smith
New member
Username: Falangjoe

Post Number: 8
Registered: 08-2006
Posted on Monday, September 11, 2006 - 06:37 pm:   

Sorry, I tested the LG1400i not the LG1440i.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6483
Registered: 10-2002
Posted on Monday, September 11, 2006 - 08:03 pm:   

Hi,

I'd probably have to see a debug log.

Typically, if there is a problem related to transcoding, it is because there is a problem either retrieving or parsing the UAProf file for the device.

The first time a device connects to retrieve a message, we will try to download its UAProf file and cache it locally for subsequent connections.

This UAProf retrieval is only done if the transcoding is enabled.

If there is a problem retrieving the UAProf file ... for example, if the MMSC does not have a direct internet connection ... or if the host pointed to by the UAProf is having problems ... then, the NowSMS timeout to try to retrieve the UAProf file may be longer than the timeout for the client attempting to retrieve the message.

What doesn't make sense is why this would be effecting so many phones, or why it would only seem to be effecting messages submitted via MM4.

That's why I'd like to see a debug log, specifically the MMSCDEBUG.LOG. I'd suggest enabling that debug log (via the "Serial #" page of the configuration dialog) ... and repeat these problematic message retrievals. It would help to also see some working retrievals so that we could compare what is different.

Either post this MMSCDEBUG.LOG in reply here, or send it to nowsms@now.co.uk with "Attention: Bryce" in the subject line, and a link to this thread in the text of the message.

-bn
Joseph Smith
New member
Username: Falangjoe

Post Number: 10
Registered: 08-2006
Posted on Monday, September 11, 2006 - 10:02 pm:   

Bryce,

I conducted these test with the LG1400i and Sony w300i, and I include the MMSC Debug logs for each test. I also have logs for the sending MMSC, but I did not include them.

Thanks,
Joseph

1.MM4 Receiving LG1400i with transcoding.
Phone cannot display picture.
2.MM4 Receiving LG1400i no transcoding.
Phone displays picture.
3.MM$ Receiving Sony W300i with transcoding.
Phone cannot display picture.
4. MM4 Receiving Sony W300i no transcoding.
Phone can display picture.
5. Locally by MM1 Receiving Sony W300i with transcoding.
Phone can display picture.
6. Locally by MM1 Receiving Lg1400i with transcoding.
Phone can display picture.



application/octet-streamLG1400 Receiving MM4 with trancoding.
TestAReceivingTrancodingLG1400i.LOG (184.2 k)
application/octet-streamLG1400i recieving MM4 without transcoding.
TestBReceivingNoTranscodingLG1400i.LOG (25.6 k)
application/octet-streamSony W300i receiving MM4 with transcoding.
TestCReceivingTranscodingSonyW300i.LOG (172.2 k)
application/octet-streamSony W300i receiving MM4 without transcoding.
TestDReceiveingNoTranscodingSonyW300i.LOG (12.0 k)
application/octet-streamSony W300i Receiving Message locally with transcoding.
TestETranscodingSonyW300i.LOG (178.1 k)
application/octet-streamLG1400i receiving MMS locally with transcoding.
TestFTranscodigLG1400i.LOG (190.0 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6491
Registered: 10-2002
Posted on Tuesday, September 12, 2006 - 12:44 pm:   

Hi Joseph,

Thanks. I see exactly what is going wrong.

The probability is that this would only be a problem with two NowSMS systems connecting via MM4 ... and whether or not the problem occurs is more dependent on the sending phone than the receiving phone.

Unfortunately, I am out of the office again this week, and I don't have an opportunity to test this configuration myself to confirm that I am correct about the problem scenario and that the fix is simple.

One of my colleagues is producing a patch based upon my observations, but he doesn't have access to upload to the web site.

If you send an e-mail to nowsms@now.co.uk with "Attention: Bryce" in the subject line, then I will route the patch to you. Otherwise, I should be back on-line late Friday where I could post it here.

-bn