Slow/No MMS Message Tranmission Between Cingular Phones

Slow/No MMS Message Tranmission Between Cingular Phones SearchSearch
Author Message
Claeton
New member
Username: Claeton

Post Number: 2
Registered: 09-2005
Posted on Sunday, September 18, 2005 - 05:56 pm:   

I have two phones configured exactly the same for Cingular: a Nokia 6800 and a Ericsson t68i. The t68i is acting as a GPRS modem for NOWSMS. Sending MMS messages between them takes more than 10 minutes, if the messages are delivered at all. What is the cause of the delay?

MMS messages sent from the Nokia, to the Nokia, arrive in seconds. Same goes for the t68i. SMS between them arrive in seconds.

I plan to use the t68i as a GPRS modem with NOWSMS, but this performance problem is a non-starter. I am wondering if the MMS traffic is actually going across two different Cingular networks (given the recent merger with AT&T) and there is a delay in routing the MMS message between the networks on the backend.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4938
Registered: 10-2002
Posted on Monday, September 19, 2005 - 06:34 pm:   

Hi Claeton,

I have no idea why there would be such a delay.

I would probably have to see a debug log in order to understand. On the "Serial #" page, enable the SMSDEBUG.LOG and MMSWAPDEBUG.LOG.

The first thing that I would recommend is to make sure that in your "MMSC Routing" definition, the "VASP Sender Address" field is blank, and "Allow Sender Address Override" is UNchecked.

(I wouldn't expect those settings to be responsible for a delay, but it can cause issues with messages not being delivered.)

I'm also curious about something. Do you see this same behaviour sending directly from the T68i (not using NowSMS) to the Nokia? If it is indeed a problem on the backend at Cingular, I'm not sure that there is anything that we could do. (I'm hoping that the problem is NowSMS specific, as that suggests a better possibility of being able to resolve the issue.)

-bn
Claeton
New member
Username: Claeton

Post Number: 3
Registered: 09-2005
Posted on Tuesday, September 20, 2005 - 01:56 am:   

I ran the test you suggested. Going phone to phone (both directions) w/o NOWSMS in the loop, there is a long delivery delay. My knowledge of the network layers is limited, but it seems to me that one phone uses a different "data account" than the other. Any thoughts? If I shift to a different pair of phones, should I go with a pair of Nokia 6800's or a pair of t68i's? One consideration is that I want to send/recv SMS and send MMS via NOWSMS. Thanks.
Claeton
New member
Username: Claeton

Post Number: 4
Registered: 09-2005
Posted on Tuesday, September 20, 2005 - 08:01 am:   

Querying both phone's GSM modems with AT+COPS? proved that they were binding to the same network, so the problem was not inter-network store-and-forward delay. I noticed that the Nokia would start to animate that it was receiving an MMS message and then just stop w/o further progress. So, somewhere in that stream of underlying SMS and WAP traffic, something was falling over. Further, if I waited long enough, the carrier woul try to redeliver the message and successfully deliver it on the second try. I tried power cycling the phone after the first failure and found that the network would immediately try (and succeed) to deliver the MMS message too. Looking closely at the two phones settings, I (finally) noticed that the Nokia had Secure Authentication on the GPRS bearer enabled; disabling it solved the problem. The messages come through in a few seconds now. I don't know why this fix worked, but it did.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4988
Registered: 10-2002
Posted on Tuesday, September 20, 2005 - 11:05 pm:   

Hi Claeton,

Wow ... that is bizarre. I can't imagine why that would make a difference. I can only figure that when the phone went to make its data connection, sometimes the secure authentication would fail.

But to the best of my knowledge, that "secure authentication" only refers to the PPP login over GPRS, when it sends the username and password configured for connecting to the GPRS APN.

Very weird, but I'm glad you were able to resolve it.

-bn