CINGULAR - USA - Aircard 860 - Can not SEND MMS - All else works

CINGULAR - USA - Aircard 860 - Can not SEND MMS - All else works SearchSearch
Author Message
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 1
Registered: 08-2006
Posted on Wednesday, August 02, 2006 - 09:35 pm:   

I have recently installed the latest version of the SMS Gateway. We have also installed a CINGULAR Aircard 860 here in the US.

SMS Send - Works fine
SMS Receive - Works fine
MMS - Receive - Works fine
MMS - Send - Does not work

I have read thru various posts in setting up, and have setup default routing Profile called Cingular in the MMSC Routing. Had to use NETWORK: Modem - Sierra Air Card, Modem - Sierra Card - All other settings do NOT pass Test Connection.

When sending a MMS message to a known phone which receives MMS, i get nothing, but I also see nothing in the Q folder.

Can someone help me out here, 1 step away from actually buying this and using it :-)

Thanks a lot

sml
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6298
Registered: 10-2002
Posted on Thursday, August 03, 2006 - 01:14 am:   

Hi,

Can you enable the SMSDEBUG.LOG and MMSWAPDEBUG.LOG on the "Serial #" page of the NowSMS config. Then send another MMS in to the modem,and let's take a closer look at those log files.

Actually, before you do that...go into Properties for the modem in the SMSC page. Change the SMS message storage option to be 'Direct to Modem'. That setting is often required for this to work with PC card modems.

-bn
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 3
Registered: 08-2006
Posted on Friday, August 04, 2006 - 12:36 am:   

Tried the direct to Modem, no help their.

I dont have a MMSWAPDEBUG.LOG i Have a MMSCDEBUG.LOG so I am attaching the SMSDEBUG.LOG and MMSCDEBUG.LOG which were generated.

Please let me know,

thanks
application/octet-streamMMSC
MMSCDEBUG_Copy.LOG (1.5 k)
application/octet-streamSMSLOG
SMSDEBUG_COPY.LOG (3.7 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6304
Registered: 10-2002
Posted on Friday, August 04, 2006 - 03:15 am:   

Shawn,

Could you collect a longer log...I'd like to see these logs showing you sending and reeceiving SMS...sending MMS...and attempting to receive MMS.

-bn
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 5
Registered: 08-2006
Posted on Friday, August 04, 2006 - 03:51 am:   

Got it to at least gen the WAPDEBUG. Seems Cingular int he US does not allow connectivity via GPRS for MMS connections, or the WAP Gateay IP is different on the GPRS network, as I ran Ethereal and did Test Connections while on that network, and would never receive a response packet back. So it is set to use the MODEM Connection and Sierra Modem in the MMSC Routing. With this configuration TEST CONNECTION WORKS, and a get a WAPDEBUG, but still no receipt of the MMS.

Here are the 3 log files.

application/octet-streamMMSC
MMSCDEBUG.LOG (1.5 k)
application/octet-streamMMSWAP
MMSWAPDEBUG.LOG (6.1 k)
application/octet-streamSMS
SMSDEBUG.LOG (4.1 k)
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 6
Registered: 08-2006
Posted on Friday, August 04, 2006 - 03:58 am:   

Ok, here are the same logs, but sent myself a MMS message, also had Ethereal running. Point of notice here. (1) TEST CONNECTION - generates packets over Dialup Modem Interface and see good connection (2) SEND MMS - No Packets seen in Ethereal (3) RECV MMS - I saw the PPP Connection Establish and DATA come in

So it looks as though the modem connection is not being opened on SEND ??????

Anyway here is the (3) files. I can also provide you with Remote Desktop Access to the box and you can trace all you like :-)

application/octet-streamMMSC
MMSCDEBUG.LOG (1.5 k)
application/octet-streamMMSWAP
MMSWAPDEBUG.LOG (25.3 k)
application/octet-streamSMS
SMSDEBUG.LOG (18.7 k)
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 7
Registered: 08-2006
Posted on Friday, August 04, 2006 - 11:22 pm:   

I see this issue as being the NOWSMS Gateway does NOT initiate a MODEM connection to Sierra Card. It does for TEST CONNECTION, and it does on RECEIPT of as MMS message, but when sending, no CONNECTION is made.
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 8
Registered: 08-2006
Posted on Wednesday, August 09, 2006 - 07:04 am:   

Any update guys??
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6313
Registered: 10-2002
Posted on Monday, August 14, 2006 - 06:00 pm:   

Hi Shawn,

I think I replied to you via e-mail.

I assumed that the problem was that you did not have the configuration defined for NowSMS to route the message externally via the operator MMSC. (No "MMSC Routing" defined.)

But I can see from your log files that the problem is different from this.

There is an internal error occurring.

The NowSMS web interface is performing an HTTP post to the MMSC (local TCP/IP connection on the same machine), and the MMSC is not receiving the complete HTTP POST.

I have never seen anything like this before.

Basically, the two NowSMS services are not able to properly talk to each other locally over TCP/IP ... so we're not getting as far as even attempting to route the message externally.

It's hard to imagine what could cause such a problem ... like perhaps there is some sort of packet filter/capture program that is getting in the way. (That said, I've used Ethereal and WinPCap many times ... and recommended its use many times ... and never seen anything remotely similar to this.)

In reviewing this with our engineering team, one thing that we noticed was that in this particular section of the code we use a Windows API that we don't use anywhere else in the product. It would appear that this API call must be failing.

Rather than try to troubleshoot what is going wrong with that API call, we're just going to avoid it, and use other APIs widely used throughout the rest of the NowSMS product.

There is an update posted at http://www.nowsms.com/download/shawn.zip.

Give that a try, and let me know if that resolves the problem. I expect it will, although I cannot explain why ...
Shawn Lewis
New member
Username: Smlcaerus

Post Number: 9
Registered: 08-2006
Posted on Wednesday, August 16, 2006 - 03:26 am:   

FIXED !!!!

Thank you.

Shawn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6354
Registered: 10-2002
Posted on Wednesday, August 16, 2006 - 06:22 pm:   

Thanks Shawn,

We will make this change permanent so that it will be applied to future releases.

The underlying problem still does puzzle me. (But not enough to lose sleep over. <g>)

-bn
Christopher Baker
New member
Username: Xchris725

Post Number: 1
Registered: 10-2006
Posted on Friday, October 06, 2006 - 09:43 pm:   

I just tried to use my NowSMS test copy with a Cingular 860 and was told that it does not support SMS. Why is that?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6651
Registered: 10-2002
Posted on Thursday, October 12, 2006 - 10:34 pm:   


quote:

I just tried to use my NowSMS test copy with a Cingular 860 and was told that it does not support SMS. Why is that?




Are you talking about an Aircard 860?

If so, I don't know why it would report this ... a few basic ideas:

1.) There was no SIM card in the device

2.) The wrong COM port was selected and you're talking to an internal modem instead of the Aircard 860

Basically, the device is responding to basic modem commands ... but it is returning an error when we try to issue SMS specific commands.

You could try opening up HyperTerminal (under Programs/Accessories/Communications in the Windows start menu), and connect to the COM port for the Aircard 860 ... then type the following commands (press Enter after typing each command):

AT+CSMS=0
AT+CMGF=0
AT+CMGF=1

Each of those commands should return an OK response ... if you are seeing an error, I would be curious to see if there is any more detail in the error response.