Aircard 875U on ATT in California - Can't send or receive SMS

Aircard 875U on ATT in California - Can't send or receive SMS SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 31, 2007 » Aircard 875U on ATT in California - Can't send or receive SMS « Previous || Next »
Author Message
Doug Wightman
New member
Username: Wightman

Post Number: 1
Registered: 09-2007
Posted on Thursday, September 13, 2007 - 09:22 pm:   

The NowSMS gateway detects the modem and indicates that the tests are passed (Aircard 875U (i.e. usb) on the AT&T network in California), but can not send (or receive) sms messages which my mobile phone and the Sierra Wireless "3G Watcher" application can send and receive (i.e. this problem is specific to the NowSMS gateway).

I put the gateway into Debug mode by editing the .ini file, and here's the contents of the debug log. What do I need to do? Thank!

14:53:55:015 [0] main: Now SMS/MMS Gateway v2007.06.27 Web server started on port number 8800
14:53:57:046 [2] ThreadProcessModem: SDKLINK - VirtualSMSC
14:53:57:046 [2] SenderAddressOverride: Yes
14:53:57:046 [3] ThreadProcessModem: Sierra Wireless MC8775 HSDPA Modem #2
14:53:57:046 [0] main: 58 Days remaining in trial version
14:53:57:078 [3] ThreadProcessModem: Before ModemAllocate - Sierra Wireless MC8775 HSDPA Modem #2
14:53:57:093 [3] ThreadProcessModem: After ModemAllocate - Sierra Wireless MC8775 HSDPA Modem #2 - OK
14:53:57:093 [3] ThreadProcessModem: Re-initializing modem: Sierra Wireless MC8775 HSDPA Modem #2 ...
14:53:57:421 [3] ThreadProcessModem: ATI0
14:53:57:421 [3] ThreadProcessModem: Sierra Wireless, Inc.

MC8775

APP2

OK

14:53:57:421 [3] ThreadProcessModem: AT+CPMS?
14:53:57:421 [3] ThreadProcessModem:
OK

14:53:57:421 [3] ThreadProcessModem: AT+CNMI=,,,1
14:53:57:421 [3] ThreadProcessModem:
OK

14:53:57:421 [3] ThreadProcessModem: AT+CNMI?
14:53:57:421 [3] ThreadProcessModem:
OK

14:53:57:421 [3] ThreadProcessModem: AT+CPMS=?
14:53:57:421 [3] ThreadProcessModem:
OK

14:53:57:437 [3] ThreadProcessModem: Modem initialization complete: Sierra Wireless MC8775 HSDPA Modem #2
14:54:23:703 [3] ThreadProcessModem: Processing 46E9A787.req...
14:54:23:703 [3] ThreadProcessModem: OUT: AT+CMGS=27

14:54:39:218 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
14:54:39:218 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
14:56:27:687 [3] ThreadProcessModem: Processing 46E9A789.req...
14:56:27:687 [3] ThreadProcessModem: OUT: AT+CMGS=33

14:56:43:093 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
14:56:43:093 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
14:56:46:359 [3] ThreadProcessModem: Processing 46E9A788.req...
14:56:46:359 [3] ThreadProcessModem: OUT: AT+CMGS=22

14:57:02:046 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
14:57:02:046 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
15:00:00:015 [0] main: 58 Days remaining in trial version
15:01:10:000 [3] ThreadProcessModem: Processing 46E9A787.req...
15:01:10:000 [3] ThreadProcessModem: OUT: AT+CMGS=27

15:01:26:046 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
15:01:26:046 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
15:01:28:250 [3] ThreadProcessModem: Processing 46E9A789.req...
15:01:28:250 [3] ThreadProcessModem: OUT: AT+CMGS=33

15:01:44:171 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
15:01:44:171 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
15:03:32:937 [3] ThreadProcessModem: Processing 46E9A788.req...
15:03:32:937 [3] ThreadProcessModem: OUT: AT+CMGS=22

15:03:48:078 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
15:03:48:078 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
15:06:44:546 [3] ThreadProcessModem: Processing 46E9A789.req...
15:06:44:546 [3] ThreadProcessModem: OUT: AT+CMGS=33

15:07:00:218 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
15:07:00:218 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
15:08:26:750 [3] ThreadProcessModem: Processing 46E9A787.req...
15:08:26:750 [3] ThreadProcessModem: OUT: AT+CMGS=27

15:08:42:093 [3] ThreadProcessModem: ERROR - Modem Response (1): OK
15:08:42:093 [3] ThreadProcessModem: Error: ERROR - Modem Response (1): OK
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7479
Registered: 10-2002
Posted on Friday, September 14, 2007 - 08:21 pm:   

Hi Doug,

Someone else in another thread is reporting the same problem. Here's the reference to it:

http://support.nowsms.com/discus/messages/1/22438.html

My initial reaction would be the same as what I posted in that thread:


quote:

In my experience with other Sierra Wireless devices, the software that comes with the device does not use an AT command interface for sending/receiving SMS, but instead uses a protocol that is proprietary to Sierra Wireless.

Those errors are very bizarre ... NowSMS is sending an AT command to send a message ... AT+CMGS=## (where ## refers to the length of the PDU for the message to be sent).

The modem is supposed to response with a continuation response (">" character) to indicate that it is ready to accept the message.

Instead, the modem is responding "OK", as if the command was complete!

Try editing SMSGW.INI, and under the section header for the modem, add ModemTextMode=Yes ... this setting will configure NowSMS to use the text interface for sending SMS messages instead of the binary PDU interface.

I'm just wondering if that makes a difference.

From the sound of things, Sierra Wireless may have some problems with their AT command implementation in their new USB modem. To troubleshoot further, let's try text mode first.




The documentation on the Sierra Wireless web site certainly seems to suggest that the USB modem supports the required AT commands for SMS support. So if the ModemTextMode=Yes setting that I mentioned above doesn't work ... then I'd like to try to get some more diagnostic information.

Try connecting to the modem with HyperTerminal (under Program/Accessories/Communications). You'll need to go into the Windows Control Panel / Phone & Modem options to figure out which COM port has been assigned to the HSDPA modem in order to know which port to connect to in HyperTerminal.

Try issuing the following commands, and I'd like to see what the responses are:

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


The above will leave the modem in "text" mode, so you can send an SMS using the following format:

AT+CGMS="enterphonenumberhere"

The modem will respond with ">"

Enter the text for a message and press CTRL-Z ... the modem should then send the message.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics