MC35 ERROR - Modem Response (2): ERROR

MC35 ERROR - Modem Response (2): ERROR SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 02, 2006 » MC35 ERROR - Modem Response (2): ERROR « Previous || Next »
Author Message
CiaranB
Unregistered guest
Posted on Friday, August 19, 2005 - 09:44 am:   

Hi I am trying to use the Siemens MC35 external terminal with NowSMS v5.51 (b2004082003) on Windows XP. I have added the modem under Windows as a standard 19,200 modem. NowSms adds the modem as an SMSC and when I click Test it says 'Modem Succesfully Tested'. However when I go to send a text message the messages are not sent.

Whe I look in the SMSDEBUG.log file I see Error: ERROR - Modem Response (2): ERROR


Any ideas what is wrong with my modem or my setup? I have attached log file below.

Thanks,

Ciaran


11:04:41:234 [0] main: Now SMS/MMS Gateway Web server started on port number 8800
11:04:43:921 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem
11:04:43:921 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK
11:04:43:921 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ...
11:04:52:218 [2] ThreadProcessModem: AT+CPMS?
11:04:52:359 [2] ThreadProcessModem:
+CPMS: "MT",0,65,"MT",0,65,"MT",0,65

OK

11:04:52:375 [2] ThreadProcessModem: AT+CNMI?
11:04:52:562 [2] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:04:52:562 [2] ThreadProcessModem: AT+CPMS=?
11:04:52:718 [2] ThreadProcessModem:
+CPMS: ("MT","SM","ME"),("MT","SM","ME"),("MT","SM")

OK

11:04:52:718 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem
11:04:57:250 [2] ThreadProcessModem: Processing 4305AB1B.req...
11:04:57:281 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:04:57:406 [2] ThreadProcessModem: IN:
>
11:04:57:406 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:04:57:593 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:04:57:593 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:05:18:732 [2] ThreadProcessModem: Processing 4305AE26.req...
11:05:18:732 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:05:18:889 [2] ThreadProcessModem: IN:
>
11:05:18:889 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:05:19:045 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:05:19:045 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:05:59:103 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:05:59:103 [5] ThreadProcessConnection: Processing request /
11:05:59:197 [5] ThreadProcessConnection: Request processing complete
11:06:01:652 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:01:652 [6] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:01:652 [6] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm
11:06:01:652 [5] ThreadProcessConnection: Processing request /TOCFrame.htm
11:06:01:933 [5] ThreadProcessConnection: Request processing complete
11:06:01:933 [6] ThreadProcessConnection: Request processing complete
11:06:02:027 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:027 [5] ThreadProcessConnection: Processing request /background.gif
11:06:02:074 [6] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:074 [6] ThreadProcessConnection: Processing request /logo.gif
11:06:02:105 [5] ThreadProcessConnection: Request processing complete
11:06:02:136 [6] ThreadProcessConnection: Request processing complete
11:06:02:543 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:543 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:02:543 [5] ThreadProcessConnection: Request processing complete
11:06:02:574 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:574 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:02:574 [5] ThreadProcessConnection: Request processing complete
11:06:02:590 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:590 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:02:605 [5] ThreadProcessConnection: Request processing complete
11:06:02:605 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:02:605 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:02:621 [5] ThreadProcessConnection: Request processing complete
11:06:12:581 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:12:581 [5] ThreadProcessConnection: Processing request /AddrBook
11:06:12:706 [5] ThreadProcessConnection: Request processing complete
11:06:19:257 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:19:257 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=0868562610&Text=test&InfoCharCounter=&PID =&DCS=&Submit=Submit
11:06:19:257 [5] Debug: 1 recipient entries
11:06:19:257 [5] Debug: 0868562610
11:06:19:304 [5] ThreadProcessConnection: Request processing complete
11:06:19:398 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:19:398 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:19:398 [5] ThreadProcessConnection: Request processing complete
11:06:19:414 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:19:414 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:19:414 [5] ThreadProcessConnection: Request processing complete
11:06:20:477 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:20:477 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:20:477 [5] ThreadProcessConnection: Request processing complete
11:06:20:477 [5] ThreadProcessConnection: Processing connection from 127.0.0.1...

11:06:20:477 [5] ThreadProcessConnection: Processing request /favicon.ico
11:06:20:492 [5] ThreadProcessConnection: Request processing complete
11:06:20:664 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:06:20:664 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:06:20:836 [2] ThreadProcessModem: IN:
>
11:06:20:836 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:06:20:993 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:06:20:993 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:06:22:978 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:06:22:978 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:06:23:088 [2] ThreadProcessModem: IN:
>
11:06:23:088 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:06:23:276 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:06:23:276 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:06:53:765 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:06:53:765 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:06:53:905 [2] ThreadProcessModem: IN:
>
11:06:53:905 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:06:54:062 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:06:54:062 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:07:19:954 [2] ThreadProcessModem: Processing 4305AE26.req...
11:07:19:954 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:07:20:095 [2] ThreadProcessModem: IN:
>
11:07:20:095 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:07:20:283 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:07:20:283 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:07:26:287 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem
11:07:26:287 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem
11:07:32:291 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem
11:07:32:291 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK
11:07:32:291 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ...
11:07:33:135 [2] ThreadProcessModem: AT+CPMS?
11:07:33:323 [2] ThreadProcessModem:
+CPMS: "MT",0,65,"MT",0,65,"MT",0,65

OK

11:07:33:323 [2] ThreadProcessModem: AT+CNMI?
11:07:33:479 [2] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:07:33:479 [2] ThreadProcessModem: AT+CPMS=?
11:07:33:635 [2] ThreadProcessModem:
+CPMS: ("MT","SM","ME"),("MT","SM","ME"),("MT","SM")

OK

11:07:33:635 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem
11:07:34:480 [2] ThreadProcessModem: Processing 4305AB1B.req...
11:07:34:480 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:07:34:620 [2] ThreadProcessModem: IN:
>
11:07:34:620 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:07:34:808 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:07:34:808 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:07:34:933 [2] ThreadProcessModem: Releasing modem for other activities
11:07:34:933 [2] ThreadProcessModem: Releasing modem for other activities
11:07:40:937 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem
11:07:40:937 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem
11:07:46:941 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem
11:07:46:941 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK
11:07:46:941 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ...
11:07:47:785 [2] ThreadProcessModem: AT+CPMS?
11:07:47:973 [2] ThreadProcessModem:
+CPMS: "MT",0,65,"MT",0,65,"MT",0,65

OK

11:07:47:973 [2] ThreadProcessModem: AT+CNMI?
11:07:48:114 [2] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:07:48:114 [2] ThreadProcessModem: AT+CPMS=?
11:07:48:270 [2] ThreadProcessModem:
+CPMS: ("MT","SM","ME"),("MT","SM","ME"),("MT","SM")

OK

11:07:48:270 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem
11:07:54:571 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:07:54:571 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:07:54:712 [2] ThreadProcessModem: IN:
>
11:07:54:712 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:07:54:900 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:07:54:900 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:09:25:054 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:09:25:054 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:09:25:195 [2] ThreadProcessModem: IN:
>
11:09:25:195 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:09:25:382 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:09:25:382 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:09:50:071 [2] ThreadProcessModem: Processing 4305AE26.req...
11:09:50:071 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:09:50:211 [2] ThreadProcessModem: IN:
>
11:09:50:211 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:09:50:352 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:09:50:352 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:10:35:804 [2] ThreadProcessModem: Processing 4305AB1B.req...
11:10:35:804 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:10:35:945 [2] ThreadProcessModem: IN:
>
11:10:35:945 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:10:36:101 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:10:36:101 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:11:26:832 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:11:26:832 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:11:26:973 [2] ThreadProcessModem: IN:
>
11:11:26:973 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:11:27:160 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:11:27:160 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:12:51:446 [2] ThreadProcessModem: Processing 4305AE26.req...
11:12:51:446 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:12:51:587 [2] ThreadProcessModem: IN:
>
11:12:51:587 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:12:51:775 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:12:51:775 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:12:57:776 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem
11:12:57:776 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem
11:13:03:777 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem
11:13:03:777 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK
11:13:03:777 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ...
11:13:04:606 [2] ThreadProcessModem: AT+CPMS?
11:13:04:793 [2] ThreadProcessModem:
+CPMS: "MT",0,65,"MT",0,65,"MT",0,65

OK

11:13:04:793 [2] ThreadProcessModem: AT+CNMI?
11:13:04:950 [2] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:13:04:950 [2] ThreadProcessModem: AT+CPMS=?
11:13:05:106 [2] ThreadProcessModem:
+CPMS: ("MT","SM","ME"),("MT","SM","ME"),("MT","SM")

OK

11:13:05:106 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem
11:13:58:275 [2] ThreadProcessModem: Processing 4305AF1B.req...
11:13:58:275 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:13:58:416 [2] ThreadProcessModem: IN:
>
11:13:58:416 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:13:58:572 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:13:58:572 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:14:06:074 [2] ThreadProcessModem: Processing 4305AB1B.req...
11:14:06:074 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:14:06:230 [2] ThreadProcessModem: IN:
>
11:14:06:230 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:14:06:386 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:14:06:386 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
11:15:34:480 [2] ThreadProcessModem: Releasing modem for other activities
11:15:34:480 [2] ThreadProcessModem: Releasing modem for other activities
11:15:40:481 [2] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem
11:15:40:481 [2] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem
11:15:46:482 [2] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem
11:15:46:482 [2] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK
11:15:46:482 [2] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ...
11:15:47:357 [2] ThreadProcessModem: AT+CPMS?
11:15:47:513 [2] ThreadProcessModem:
+CPMS: "MT",0,65,"MT",0,65,"MT",0,65

OK

11:15:47:513 [2] ThreadProcessModem: AT+CNMI?
11:15:47:685 [2] ThreadProcessModem:
+CNMI: 0,0,0,0,1

OK

11:15:47:685 [2] ThreadProcessModem: AT+CPMS=?
11:15:47:841 [2] ThreadProcessModem:
+CPMS: ("MT","SM","ME"),("MT","SM","ME"),("MT","SM")

OK

11:15:47:841 [2] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem
11:16:22:625 [2] ThreadProcessModem: Processing 4305AE26.req...
11:16:22:625 [2] ThreadProcessModem: OUT: AT+CMGS=16

11:16:22:750 [2] ThreadProcessModem: IN:
>
11:16:22:750 [2] ThreadProcessModem: OUT: 0001000A818086656201000004F4F29C0E
11:16:22:907 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR
11:16:22:907 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4839
Registered: 10-2002
Posted on Thursday, September 01, 2005 - 04:48 pm:   

Hi Ciaran,

Try putting the SIM card into a phone, and verify that you can send SMS with that SIM from a phone.

Assuming that you can, the next thing I would try would be to set "SMS Access" to "GSM" under the "Properties" for the modem in NowSMS. (I believe that is the default mode for the MC35, but try setting it explicitly.)

Another possibility ... does the SIM card have a PIN associated with it? If unsure, you'd find that out when putting the SIM into a phone for testing. If so, you should be able to configure the PIN in NowSMS, but it is also worth using the phone interface to remove the PIN to make sure that this is not the problem.

Unfortunately, the error code coming back from the modem is very generic. The modem is simply saying "ERROR". This could also mean that the modem is not getting a signal to connect to the mobile operator.

-bn
Kokoloko Erukusolala
Unregistered guest
Posted on Monday, October 24, 2005 - 02:06 pm:   

I am having a problem receiving an ems ringtone on a T610 (Sony Ericson) handset from nowsms gateway.These are the steps I followed;
1. Converted the ringtone from MIDI to SP-MIDI and later to EMS format using RINGTONE CREATOR.

2.I sent the ringtone with the parameters below;
UDH=
4F0C4D00424547494E3A494D454C4F44590D0A56455253494F4E3A312E320D0A464F524D41543A43 4C415353312E300D0A424541543A36340D0A4D454C4F44593A0D0A454E443A494D454C4F44590D0A

BINARY DATA=00
PID=0
DCS=0

The log was as below;

2005-10-20 13:31:15,43578E0E.req,127.0.0.1,2348033299305,OK -- COM1:,Binary=1;UDH=4F0C4D00424547494E3A494D454C4F44590D0A56455253494F4E3A312E320 D0A464F524D41543A434C415353312E300D0A424541543A36340D0A4D454C4F44593A0D0A454E443 A494D454C4F44590D0A;Data=00

and the output on the phone was this;


The text message (output) on the mobile phone was as below.

0^M^BEGIN:MELODY
VERSION:1.2
FORMAT:CLASS 1.0
BEAT:64
MELODY:
END:IMELODY.

Is there anything I am doing wrong?

-Kokoloko-
Kokoloko Erukusolala
Unregistered guest
Posted on Monday, October 24, 2005 - 02:08 pm:   

I am having a problem receiving an ems ringtone on a T610 (Sony Ericson) handset from nowsms gateway.These are the steps I followed;
1. Converted the ringtone from MIDI to SP-MIDI and later to EMS format using RINGTONE CREATOR.

2.I sent the ringtone with the parameters below;
UDH=
4F0C4D00424547494E3A494D454C4F44590D0A56455253494F4E3A312E320D0A464F524D41543A43 4C415353312E300D0A424541543A36340D0A4D454C4F44593A0D0A454E443A494D454C4F44590D0A

BINARY DATA=00
PID=0
DCS=0

The log was as below;

2005-10-20 13:31:15,43578E0E.req,127.0.0.1,2348033299305,OK -- COM1:,Binary=1;UDH=4F0C4D00424547494E3A494D454C4F44590D0A56455253494F4E3A312E320 D0A464F524D41543A434C415353312E300D0A424541543A36340D0A4D454C4F44593A0D0A454E443 A494D454C4F44590D0A;Data=00

and the output on the phone was this;


The text message (output) on the mobile phone was as below.

0^M^BEGIN:MELODY
VERSION:1.2
FORMAT:CLASS 1.0
BEAT:64
MELODY:
END:IMELODY.

In the setup I have a TC35 GSM modem attached to my PC.

Is there anything I am doing wrong?

-Kokoloko-
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5181
Registered: 10-2002
Posted on Tuesday, October 25, 2005 - 02:06 pm:   

Hi Kokoloko,

I believe you also sent me this, and some additional information, via e-mail.

I asked you to send the EMS message to the modem itself. In the received message, the UDH indicator is lost, and this is causing the UDH to be treated as part of the message text.

So unfortunately, I don't know what to suggest. You appear to be doing everything correctly. However, the operator SMSC seems to be losing the UDHI (User Data Header Indicator) flag when it processes the message.

This might be a problem with your mobile operator, or it could be a problem with the GSM modem.

I've only seen an issue similar to this once before, on a Canadian network. And in that instance, putting a different SIM in the modem resolved the problem. But I do not understand why that would make a difference ... so I'm not optimistic that this would resolve your problem.

What happens if the T610 sends an EMS message to your modem (include an EMS animation in the message). Does the modem receive a message with any UDH? If so, what if you swap SIMs between the T610 and the modem?

-bn

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