MMS Not sending from multitech modem/T-Mobile

MMS Not sending from multitech modem/T-Mobile SearchSearch
Author Message
Rob Ristroph
New member
Username: Robristroph

Post Number: 6
Registered: 05-2007
Posted on Thursday, June 28, 2007 - 09:27 pm:   

Attached are logs and .ini files for trying to send an MMS with a single attachment (monkey.jpg) to a cell phone. It is NOT getting to the cell phone. I sent a text message from the now.sms browser - that went to the phone OK. I sent the MMS message from the same browser. Did not arrive - files attached.

Can someone help me fiture out what I'm doing wrong. I'm about ready to give up on this.

Richard
application/x-zip-compressed.ini files used for sending MMS session
MMSC.zip (4.7 k)
application/x-zip-compressedLog files from failed MMS sending
Standard 33600 bps Modem-2007.zip (25.6 k)
Richard Gintz
New member
Username: Robristroph

Post Number: 7
Registered: 05-2007
Posted on Friday, June 29, 2007 - 03:08 pm:   

Really need to get this thing working. Is there anyone at now.sms customer support?
Thanks,
Richard
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7311
Registered: 10-2002
Posted on Friday, June 29, 2007 - 03:40 pm:   

Hi Richard,

You've included a lot of INI and LOG files, which is good.

There's only one problem ... we don't log as much detail in one of the log files when the WAP gateway is configured for HTTP mode.

What I can see is that the T-Mobile MMSC is responding back with an error code indicating that an unspecified error has occurred.

That's not a particularly helpful error response, but it tells us that we are talking to the MMSC, because the error is coming back in proper MMS encoded format.

Unfortunately, because the WAP gateway setting is configured for HTTP mode (http://212.155.165.50:8080 instead of just 212.155.165.50), NowSMS is not putting as much detail in the debug log, which means I can't see the full details of the transaction.

Based upon what I can see, everything looks like it is configured correctly. All the settings seem ok for your mobile operator. (There appears to be a problem with the "MMS Server URL" in the receive MMS settings, where there is a ":8080" in the URL that does not belong. This is not causing the problem that you are currently seeing, but it could cause problems handling received messages in the future if you get past this sending problem.)

So what would I suggest?

In the "MMSC Routing" definition, make sure that "Default Sender Address" is blank, and that "Allow Sender Address Override" is NOT checked. Having other values for those settings can often cause unexpected errors for these types of connections.

Try changing the "WAP Gateway IP Address" setting back to the default for T-Mobile USA ... 216.155.165.50. Try sending again, then post just the MMSWAPDEBUG.LOG file that is generated after the attempt.

Also ... I'm wondering if there's something wrong with how the SIM is provisioned with the operator. Our experience in the past with this particular operator is that you get provisioned by their MMSC automatically the first time that you send an MMS. But maybe that has changed. Do you have a phone that you can move the modem's SIM into ... and then confirm that the phone can actually send/receive MMS properly using the SIM. It just seems like everything is configured ok ... so I can't help but be suspicious that something might be wrong with the account.

-bn
Richard Gintz
New member
Username: Robristroph

Post Number: 8
Registered: 05-2007
Posted on Friday, June 29, 2007 - 05:47 pm:   

OK, I gave up on T-Mobile after failing to make it work in a phone even.

So I put a cingular chip in and I can send!

Receiving is a problem - the CD light stays on - working on that before I have you chase rabbit trails though.

Thanks for getting back to me - will report back on receiving issues shortly.

Thanks again,
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7320
Registered: 10-2002
Posted on Friday, June 29, 2007 - 06:31 pm:   

Hi Richard,

A couple of quick ideas with regard to the CD light staying on.

Make sure that the modem name in the "SMSC" list matches the "Modem Used" setting in the "MMS Settings" for both sending and receiving.

Also, there might be some previously received MMS notification messages that are not valid, or for the previous carrier. (I saw some invalid ones in your earlier log, from when the system was partially configured for direct MMSC delivery.) These could cause NowSMS to keep the CD light on longer than expected, trying to retrieve the messages. Eventually those messages would error out, but you might just want to delete all the files in the MMSINQ directory to clean them out.

-bn
Richard Gintz
New member
Username: Robristroph

Post Number: 9
Registered: 05-2007
Posted on Friday, June 29, 2007 - 08:01 pm:   

bn,
OK, thanks - I deleted the files out of the MMSINQ directory - however, there was a folder in there with the name of the modem and within that folder there was a xxxx.LCK that would not delete. Also within the MMSINQ folder itself, there was another xxxx.LCK file that didn't delete.

I verified the modem as you said. Now the problem I'm getting when I test the modem is this:

RAS Error 777
The connectino attempt failed because the modem (or other connecting device) on the remote computer is out of order.

Any ideas on that? We are now using Cingular-US.

We are almost there and THANK YOU VERY MUCH for getting on this with me. You guys will likely have a sale.
Thanks,
Richard

Richard Gintz
New member
Username: Robristroph

Post Number: 10
Registered: 05-2007
Posted on Monday, July 02, 2007 - 08:41 pm:   

Uh, bn,
I sent a message last Friday - re: 777 - can you help me out on this asap?
------------
After WSPRadDial - failed - RAS Error 777 -- The connection attempt failed because the modem on the remote computer is out of order.
------------
thanks,
richard
Richard Gintz
New member
Username: Robristroph

Post Number: 11
Registered: 05-2007
Posted on Monday, July 02, 2007 - 08:47 pm:   

Here is the log for that last error:

application/octet-streamMMSCDEBUG.log
MMSCDEBUG.LOG (45.4 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7333
Registered: 10-2002
Posted on Tuesday, July 10, 2007 - 10:33 pm:   

Hi Richard,

Sorry, I'm having delays getting caught up on messages after vacation.

The "777" error usually means that the APN connection is being rejected. It could be a username/password issue, wrong APN, or it could be that the provider is not allowing GPRS connectons for some reason.

Is it possible to put the SIM back into a phone, and verify that the phone can send/receive MMS ok?

RAS 777 errors tend to be hard to troubleshoot. If the SIM is working ok in a phone, here are some tests to try with the modem ...

Make sure the NowSMS services are not running, and connect to the modem using HyperTerminal.

Issue the following command:

AT+CGDCONT?

You should see a response something like this:

+CGDCONT: 1,"IP","wap.cingular"

If you don't see this response, try the following commands:

AT+CGDCONT=1,"IP","wap.cingular"

You should get back an OK.

ATD*99***1#

This command tries to initiate a GPRS connection. You should see "CONNECT" followed by some garbage if the connection is ok ... or "NO CARRIER" if the connection fails. If you get "NO CARRIER" then for some reason the modem is not making the connection (maybe it's a signal strength issue?)

While we're talking about AT commands, some times if you have been trying a modem with different carriers, some modems can get confused if there are too many access points configured in the modem.

When you issue the command:

AT+CGDCONT?

And you get a response like this:

+CGDCONT: 1,"IP","wap.cingular"

There might be more than one APN defined ... with the "1" being a different numeric value in each entry returned.

To clear the definitions, enter the following:

AT+CGDCONT=1
AT+CGDCONT=2
...etc...

Clearing those definitions might make a difference (the next time you connect with NowSMS it will add the entry that you need).

Here's an old thread that talked about this issue:

http://support.nowsms.com/discus/messages/485/6383.html

... I don't think that thread offers any resolution for you, but it may give some more things to look at.

-bn