SMS Issue with Multitech MTCBA-C CDMA Modem

SMS Issue with Multitech MTCBA-C CDMA Modem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 16, 2008 » SMS Issue with Multitech MTCBA-C CDMA Modem « Previous || Next »
Author Message
Johny
New member
Username: Stefanus

Post Number: 2
Registered: 07-2008
Posted on Tuesday, August 19, 2008 - 08:42 pm:   

Hi Bryce,

I'm trying to use NowSMS to send/receive SMS with Multitech MTCBA-C CDMA modem.

I've successfully done SMS and data using Multitech's mobilePhone tools, so the device config is fine.

In NowSMS, I can add the modem in SMSC tab without problem, the "Test and Add" was successful and says modem only support text messages, as expected.

However when I try to send SMS using the web interface, I have SMSC Status Error message: MultiTech CDMA Modem: Modem Failure - Unable to access modem, ensure that it is powered on and passes diagnostics tests.

Before starting NowSMS, diagnostic tests are successful.
But afterward it fails and you have to power cycle the modem to fix it.

So it appears NowSMS cause hardware failure on the modem.

Do you know how to fix this issue?
Thanks.
Johny
New member
Username: Stefanus

Post Number: 3
Registered: 07-2008
Posted on Wednesday, August 20, 2008 - 02:02 pm:   

Debug log shows that the modem is working fine until NowSMS sends AT+CMGS command to it.

10:43:16:291 [3] ThreadProcessModem: MultiTech - CDMA Modem
10:43:16:306 [3] ThreadProcessModem: Before ModemAllocate - MultiTech - CDMA Modem
10:43:16:306 [3] ThreadProcessModem: After ModemAllocate - MultiTech - CDMA Modem - OK
10:43:16:306 [3] ThreadProcessModem: Re-initializing modem: MultiTech - CDMA Modem ...
10:43:17:197 [3] ThreadProcessModem: ATI0
10:43:17:197 [3] ThreadProcessModem:
WAVECOM MODEM
800 1900

OK

10:43:17:744 [3] ThreadProcessModem: AT+CPMS?
10:43:17:822 [3] ThreadProcessModem:
+CPMS:"MT",2,30,"MO",0,30

OK

10:43:17:822 [3] ThreadProcessModem: AT+CNMI=,,,1
10:43:17:916 [3] ThreadProcessModem:
OK

10:43:17:916 [3] ThreadProcessModem: AT+CNMI?
10:43:17:994 [3] ThreadProcessModem:
+CNMI:2,1,1,1,0

OK

10:43:17:994 [3] ThreadProcessModem: AT+CPMS=?
10:43:18:072 [3] ThreadProcessModem:
+CPMS: ("MT","BC","SR"),("MO")

OK

10:43:18:150 [3] ThreadProcessModem: Modem initialization complete: MultiTech - CDMA Modem
10:43:40:165 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:40:165 [11] ThreadProcessConnection: Processing request /
10:43:40:228 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:40:228 [11] ThreadProcessConnection: Request processing complete
10:43:40:243 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:40:243 [11] ThreadProcessConnection: Processing request /TOCFrame.htm
10:43:40:275 [12] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:40:275 [12] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm
10:43:40:306 [12] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:40:306 [12] ThreadProcessConnection: Request processing complete
10:43:40:321 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:40:321 [11] ThreadProcessConnection: Request processing complete
10:43:40:384 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:40:384 [11] ThreadProcessConnection: Processing request /background.gif
10:43:40:384 [12] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:40:384 [12] ThreadProcessConnection: Processing request /logo.gif
10:43:40:400 [12] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:40:415 [12] ThreadProcessConnection: Request processing complete
10:43:40:415 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:40:415 [11] ThreadProcessConnection: Request processing complete
10:43:43:306 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:43:43:306 [11] ThreadProcessConnection: Processing request /favicon.ico
10:43:43:306 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
10:43:43:306 [11] ThreadProcessConnection: Request processing complete
10:44:16:696 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:44:16:696 [11] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=xxxyyyzzzz&Text=foo+bar+baz&InfoCharCount er=&PID=&DCS=&DestPort=&DelayUntil=&Submit=Submit
10:44:16:711 [11] Debug: 1 recipient entries
10:44:16:727 [11] ThreadProcessConnection: Before message loop
10:44:16:727 [11] ThreadProcessConnection: Before message loop
10:44:16:727 [11] ThreadProcessConnection: Begin message loop
10:44:16:758 [11] ThreadProcessConnection: End message loop
10:44:16:758 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
10:44:16:774 [11] ThreadProcessConnection: Request processing complete
10:44:16:867 [3] ThreadProcessModem: Processing 48934DA0.req...
10:44:16:867 [3] ThreadProcessModem: OUT: AT+CMGS="xxxyyyzzzz"

10:44:32:133 [3] ThreadProcessModem: ERROR - Error waiting for response from modem (1)
10:44:32:133 [3] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (1)
10:45:05:132 [3] ThreadProcessModem: modem test failed
10:45:11:132 [3] ThreadProcessModem: Before ModemRelease - MultiTech - CDMA Modem
10:45:11:132 [3] ThreadProcessModem: After ModemRelease - MultiTech - CDMA Modem
10:45:17:132 [3] ThreadProcessModem: Before ModemAllocate - MultiTech - CDMA Modem
10:45:17:132 [3] ThreadProcessModem: After ModemAllocate - MultiTech - CDMA Modem - OK
10:45:17:132 [3] ThreadProcessModem: Re-initializing modem: MultiTech - CDMA Modem ...
10:45:35:288 [3] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID
10:45:35:288 [3] HammerNonResponsiveModem: Begin
10:45:35:288 [3] HammerNonResponsiveModem: Unable to access modem at COM1: -- Error 5 -- Access is denied.

10:45:35:288 [3] HammerNonResponsiveModem: Another application is already using this device.
10:45:35:288 [3] HammerNonResponsiveModem: FAILED
10:45:35:288 [3] ThreadProcessModem: Before ModemRelease - MultiTech - CDMA Modem
10:45:35:288 [3] ThreadProcessModem: After ModemRelease - MultiTech - CDMA Modem
10:45:55:287 [3] ThreadProcessModem: Before ModemAllocate - MultiTech - CDMA Modem
10:45:55:287 [3] ThreadProcessModem: After ModemAllocate - MultiTech - CDMA Modem - OK
10:45:55:287 [3] ThreadProcessModem: Re-initializing modem: MultiTech - CDMA Modem ...
10:46:13:443 [3] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID
10:46:13:443 [3] HammerNonResponsiveModem: Begin
10:46:13:443 [3] HammerNonResponsiveModem: Unable to access modem at COM1: -- Error 5 -- Access is denied.

10:46:13:443 [3] HammerNonResponsiveModem: Another application is already using this device.
10:46:13:443 [3] HammerNonResponsiveModem: FAILED
10:46:13:443 [3] ThreadProcessModem: Before ModemRelease - MultiTech - CDMA Modem
10:46:13:443 [3] ThreadProcessModem: After ModemRelease - MultiTech - CDMA Modem
10:46:53:443 [3] ThreadProcessModem: Before ModemAllocate - MultiTech - CDMA Modem
10:46:53:443 [3] ThreadProcessModem: After ModemAllocate - MultiTech - CDMA Modem - OK
10:46:53:443 [3] ThreadProcessModem: Re-initializing modem: MultiTech - CDMA Modem ...
10:47:11:536 [3] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID
10:47:11:536 [3] HammerNonResponsiveModem: Begin
10:47:31:551 [3] ReceiveModemCommand: Error - 3E4 -
10:47:31:551 [3] ReceiveModemCommand: CancelIo
10:48:41:563 [3] HammerNonResponsiveModem: FAILED
10:48:41:563 [3] ThreadProcessModem: Before ModemRelease - MultiTech - CDMA Modem
10:48:41:563 [3] ThreadProcessModem: After ModemRelease - MultiTech - CDMA Modem

Any idea?

Thanks.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 31
Registered: 08-2008
Posted on Wednesday, August 20, 2008 - 03:39 pm:   

That's messed up. (Quite a profound technical insight, I know.)

Is this a USB modem? I am assuming not because there are references to COM1:, so I'm assuming it's serial. If so, that's good, because it is easier to troubleshoot.

It looks like the sending of that AT+CGMS command is putting the modem into a confused state from which we are unable to awaken it.

The best way to troubleshoot this would be to try accessing the modem with HyperTerminal. (You'll likely have to power off the modem and power it back on before you do can do this.)

HyperTerminal can be found under Programs/Accessories/Communciations. Unfortunately, it's a little more difficult with Vista ... HyperTeriminal used to be a free download from Hilgraeve for personal use, but not any more.

Connect to the modem and issue the following commands, pressing Enter after each command:

ATE1V1

The modem should respond to the above with OK ... this is just turning on modem echo if it is not already on.

AT+CSMS?

The modem should respond with +CSMS: and some other info, followed by OK.

AT+CGMS="phonenumber"

Put in an actual phone number between the "quote" characters.

The modem should respond on a new line with just ">". If it does not, then give it about 30 seconds ... type in some text to send as an SMS, and press CTRL-Z.

Do you get an OK response back?

Can you issue a command of just AT and get an OK back?

The initial error that you are getting suggests that the modem is not sending the ">" character back. So I am curious as to whether or not you see this same behaviour from within HyperTerminal. And if you do see that behaviour, can you send anyway?

--
Des
NowSMS Support
Johny
New member
Username: Stefanus

Post Number: 4
Registered: 07-2008
Posted on Wednesday, August 20, 2008 - 04:55 pm:   

Des,

I'm able to send SMS by direct AT command over Hyperterminal.

and you are right about ">" character. After typing at+cmgs="xyz" there's no ">" character in the next line. But anything you type will be SMSed after pressing CTRL-Z.

So do you know how to fix this?

Thanks.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 47
Registered: 08-2008
Posted on Thursday, August 21, 2008 - 05:35 pm:   

Hi Johny,

I did some digging and found a setting that should help you.

Edit SMSGW.INI, and under the [Modem - MultiTech - CDMA Modem] header, add:

ModemSendWorkaround=Yes

It looks like this setting was added to troubleshoot a similar problem.

The only catch is that even with this setting in place, NowSMS is going to wait 15 seconds for that ">" before it continues the sending process, which will slow things down.

If that does resolve the issue, I'll see if I can get engineering to allow the timeout to be changed in conjunction with this setting.

That said ... I wonder if there is a firmware update for the modem to resolve this issue, as it is not implementing the command correctly. (And I know we didn't see this behaviour with that modem when we last tested it.)

--
Des
NowSMS Support
Johny
New member
Username: Stefanus

Post Number: 5
Registered: 07-2008
Posted on Thursday, August 21, 2008 - 06:48 pm:   

Des,

tried your suggestion but still doesn't work.

Here's my SMSGW.ini
[SMSGW]
Debug=Yes
WebAuth=No
WebMenu=Yes
WebPort=8800
ReceiveSMS=No
ReceiveMMS=No
ReceiveSMSCharset=utf-8
ConfigurationUpdateTriggerRestart=20080821154037
Modem1=MultiTech Systems CDMA Wireless Modem
[Modem - MultiTech Systems CDMA Wireless Modem]
PhoneNumber=xxxyyyzzzz
ReceiveSMS=Yes
ReceiveMMS=No
ModemSendWorkaround=Yes


Debuglog:

15:40:53:290 [0] main: Now SMS/MMS Gateway v2008.06.03 Web server started on port number 8800
15:40:55:289 [0] main: preferred sender = xxxyyyzzzz,MultiTech Systems CDMA Wireless Modem
15:40:55:305 [0] main: 42 Days remaining in trial version
15:40:55:305 [7] ThreadProcessModem: MultiTech Systems CDMA Wireless Modem
15:40:55:321 [7] ThreadProcessModem: Before ModemAllocate - MultiTech Systems CDMA Wireless Modem
15:40:55:321 [7] ThreadProcessModem: After ModemAllocate - MultiTech Systems CDMA Wireless Modem - OK
15:40:55:321 [7] ThreadProcessModem: Re-initializing modem: MultiTech Systems CDMA Wireless Modem ...
15:40:56:243 [7] ThreadProcessModem: ATI0
15:40:56:243 [7] ThreadProcessModem:
WAVECOM MODEM

800 1900

OK

15:40:56:789 [7] ThreadProcessModem: AT+CPMS?
15:40:56:867 [7] ThreadProcessModem:
+CPMS:"MT",2,30,"MO",0,30

OK

15:40:56:867 [7] ThreadProcessModem: AT+CNMI=,,,1
15:40:56:961 [7] ThreadProcessModem:
OK

15:40:56:961 [7] ThreadProcessModem: AT+CNMI?
15:40:57:039 [7] ThreadProcessModem:
+CNMI:2,1,1,1,0

OK

15:40:57:039 [7] ThreadProcessModem: AT+CPMS=?
15:40:57:117 [7] ThreadProcessModem:
+CPMS: ("MT","BC","SR"),("MO")

OK

15:40:57:196 [7] ThreadProcessModem: Modem initialization complete: MultiTech Systems CDMA Wireless Modem
15:41:39:709 [11] ThreadProcessConnection: Processing connection from 127.0.0.1...

15:41:39:709 [11] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=aaabbbcccc&Text=foo+bar+baz&InfoCharCount er=&PID=&DCS=&DestPort=&DelayUntil=&Submit=Submit
15:41:39:725 [11] Debug: 1 recipient entries
15:41:39:725 [11] ThreadProcessConnection: Before message loop
15:41:39:725 [11] ThreadProcessConnection: Before message loop
15:41:39:725 [11] ThreadProcessConnection: Begin message loop
15:41:39:725 [11] ThreadProcessConnection: End message loop
15:41:39:740 [11] WaitForSocketClose: WinSock reported ioctlsocket complete
15:41:39:740 [11] ThreadProcessConnection: Request processing complete
15:41:40:287 [7] ThreadProcessModem: Processing 48934DA6.req...
15:41:40:287 [7] ThreadProcessModem: OUT: AT+CMGS="aaabbbcccc"

15:41:56:036 [7] ThreadProcessModem: ERROR - Error waiting for response from modem (1)
15:41:56:036 [7] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (1)
15:42:29:035 [7] ThreadProcessModem: modem test failed
15:42:35:034 [7] ThreadProcessModem: Before ModemRelease - MultiTech Systems CDMA Wireless Modem
15:42:35:034 [7] ThreadProcessModem: After ModemRelease - MultiTech Systems CDMA Wireless Modem
15:42:41:034 [7] ThreadProcessModem: Before ModemAllocate - MultiTech Systems CDMA Wireless Modem
15:42:41:034 [7] ThreadProcessModem: After ModemAllocate - MultiTech Systems CDMA Wireless Modem - OK
15:42:41:034 [7] ThreadProcessModem: Re-initializing modem: MultiTech Systems CDMA Wireless Modem ...
15:42:59:189 [7] OpenDevice: Unable to initialize modem: Error 80000018 from lineGetID
15:42:59:189 [7] HammerNonResponsiveModem: Begin
15:42:59:189 [7] HammerNonResponsiveModem: Unable to access modem at COM1: -- Error 5 -- Access is denied.

15:42:59:189 [7] HammerNonResponsiveModem: Another application is already using this device.
15:42:59:189 [7] HammerNonResponsiveModem: FAILED
15:42:59:189 [7] ThreadProcessModem: Before ModemRelease - MultiTech Systems CDMA Wireless Modem
15:42:59:189 [7] ThreadProcessModem: After ModemRelease - MultiTech Systems CDMA Wireless Modem
15:43:19:187 [7] ThreadProcessModem: Before ModemAllocate - MultiTech Systems CDMA Wireless Modem
15:43:19:187 [7] ThreadProcessModem: After ModemAllocate - MultiTech Systems CDMA Wireless Modem - OK
15:43:19:187 [7] ThreadProcessModem: Re-initializing modem: MultiTech Systems CDMA Wireless Modem ...
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 7655
Registered: 10-2002
Posted on Thursday, August 21, 2008 - 08:33 pm:   

Hmm ... it seems that setting was added since the 2008.06.03 release.

I remember that we added the setting to try to troubleshoot a similar problem, and I suggested it to Des.

But it appears that the setting only exists in more recent interim release versions.

I'm uploading an update to http://www.nowsms.com/download/nowsms20080822.zip. If ModemSendWorkaround=Yes is present in the [Modem - Driver name] section of SMSGW.INI, NowSMS will ignore the fact that the modem does not return the ">" response ... and it will only wait a couple of seconds, instead of the normal 15 second delay ... like Des suggested we should do in his earlier posting.

-bn
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 48
Registered: 08-2008
Posted on Friday, August 22, 2008 - 04:10 pm:   

Hi Johnny,

I'm suspicious about the "AT+CNMA" entries in the log file. A CDMA modem might not understand that command.

Change "SMS Message Storage" to be "Direct to Modem" (I think right now you have it set to "Direct to Modem (Phase 2+)".

I believe Phase 2+ is very GSM specific, and NowSMS attempting to use this mode may trigger some unexpected behaviour on the modem.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 96
Registered: 08-2008
Posted on Thursday, September 11, 2008 - 07:33 pm:   

Hi Johny,

This is all a bit beyond me at this point.

I talked this over with Bryce and forwarded him the information from your debug log, and his suggestion was that you two open a dialog to discuss this directly via e-mail.

Send an e-mail to nowsms@nowsms.com with Attention Bryce in the subject line, and this will get routed through our tech system to his attention.

Depending on timing, he might get in touch with you first, because he has been looking at your log today trying to figure it out.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 97
Registered: 08-2008
Posted on Thursday, September 11, 2008 - 08:20 pm:   

Bizarre ... your debug log disappeared from the thread when I posted this message.

I think a couple of other messages on this thread were swallowed as well.

Johny
New member
Username: Stefanus

Post Number: 8
Registered: 07-2008
Posted on Monday, September 15, 2008 - 12:55 pm:   

Thanks Des.
I've connect up with Bryce.

Yeah it's odd my prev post is not here anymore. Do you want me to put it up again?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 99
Registered: 08-2008
Posted on Tuesday, September 16, 2008 - 06:50 pm:   

Don't worry about reposting.

I'm not sure what happenned to the post. It happened to someone else recently.

This web server is getting a little old and is in need of upgrading. One of my tasks over the coming weeks is to upgrade the server and the discussion board software.

Was Bryce able to resolve the issue?

--
Des
NowSMS Support

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