| Problems with SIemens GSM Module M1 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| BooLE New member Username: Boole Post Number: 1 Registered: 06-2004 |
Hi, I have problem sending sms-es with my Siemens M1 module, it is working as I have tested it with other software but now I want to use it with nowsms. Here is a SMSDEBUG.log: 16:21:27:639 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 16:21:29:639 [0] main: preferred routing = +385910401,COM1: 16:21:29:639 [0] main: preferred sender = +38591*******,COM1: 16:21:29:764 [2] ThreadProcessModem: Before ModemAllocate - COM1: 16:21:29:764 [2] ThreadProcessModem: After ModemAllocate - COM1: - OK 16:21:29:764 [2] ThreadProcessModem: Re-initializing modem: COM1: ... 16:21:32:232 [2] TestModemSpeed: Initialised modem at 57600 bps 16:21:32:560 [2] ThreadProcessModem: AT+CGSMS=3 16:21:32:639 [2] ThreadProcessModem: ERROR 16:21:32:639 [2] ThreadProcessModem: Modem initialization complete: COM1: 16:21:35:076 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 16:21:35:076 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B385914691621&Text=testz&InfoCharCounte r=&PID=&DCS=&Submit=Submit 16:21:35:076 [5] Debug: 1 recipient entries 16:21:35:076 [5] Debug: +385914691621 16:21:35:639 [2] ThreadProcessModem: Processing 40D1A8EF.req... 16:21:35:639 [2] ThreadProcessModem: OUT: AT+CMGS=18 16:21:35:717 [2] ThreadProcessModem: IN: > 16:21:35:717 [2] ThreadProcessModem: OUT: 0001000C91839541966112000005F4F29CAE07 16:21:36:529 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 16:21:36:529 [5] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm 16:21:40:967 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 16:21:40:967 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 16:21:42:045 [2] ThreadProcessModem: Processing 40D1A8EF.req... 16:21:42:045 [2] ThreadProcessModem: OUT: AT+CMGS=18 16:21:42:123 [2] ThreadProcessModem: IN: > 16:21:42:123 [2] ThreadProcessModem: OUT: 0001000C91839541966112000005F4F29CAE07 16:21:48:748 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 16:21:48:748 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 16:22:18:826 [2] ThreadProcessModem: Processing 40D1A8EF.req... 16:22:18:826 [2] ThreadProcessModem: OUT: AT+CMGS=18 16:22:18:904 [2] ThreadProcessModem: IN: > 16:22:18:904 [2] ThreadProcessModem: OUT: 0001000C91839541966112000005F4F29CAE07 16:22:24:810 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 16:22:24:810 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 16:22:34:889 [2] ThreadProcessModem: Processing 40D18D63.req... 16:22:34:889 [2] ThreadProcessModem: OUT: AT+CMGS=17 16:22:34:967 [2] ThreadProcessModem: IN: > 16:22:34:967 [2] ThreadProcessModem: OUT: 0001000C91839541966112000004F4F29C0E 16:22:40:873 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 16:22:40:873 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 16:23:24:951 [2] ThreadProcessModem: Processing 40D1A8EF.req... 16:23:24:951 [2] ThreadProcessModem: OUT: AT+CMGS=18 16:23:25:029 [2] ThreadProcessModem: IN: > 16:23:25:029 [2] ThreadProcessModem: OUT: 0001000C91839541966112000005F4F29CAE07 16:23:30:967 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 16:23:30:967 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 16:24:50:639 [2] ThreadProcessModem: Before ModemRelease - COM1: 16:24:50:639 [2] ThreadProcessModem: After ModemRelease - COM1: 16:24:56:920 [0] main: Shutdown: Closing log files Is ther someone that is using nowsms with this module. Thanks in advance | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2896 Registered: 10-2002 |
Hi Boole, That is strange, the modem is coming back from the message sending attempts and reporting the text "ERROR". About the only thing that I can think of is that perhaps that modem requires the SMSC address to be explicitly set when sending a message. Most modems don't require this, and just use the SMSC address configured on the SIM card. But just maybe the M1 requires the address to be set explicitly. This SMSC address varies depending upon what operator you are subscribed to. You can set the SMSC address by manually editing the SMSGW.INI file. Under the section header for the modem configuration (e.g., [Modem - ...], add SMSC=+phonenumber, where "+phonenumber" is the address of the SMSC. Here's a link to a good list of SMSC phone numbers: http://www.cellular.co.za/smsc_lists.htm. A more reliable way of determining the correct SMSC number is to put your SIM into a phone, and go through the SMS configuration menus on the phone to determine the currently configured SMSC number. When you enter the SMSC phone number, always start it with a "+" and don't include any other non-numeric characters (no dashes or dots) in the address. Always restart the gateway service after making a change to the SMSGW.INI file. If you try setting the SMSC value by manually editing SMSGW.INI ... if the setting doesn't make a difference, always go back in and remove it immediately so that it doesn't confuse things down the road. -bn | |||
| BooLE New member Username: Boole Post Number: 2 Registered: 06-2004 |
Hi Bryce, nope this is not the problem, I know that I must set in software SMSC, i think that the problem is in PDU mode, 'cause M1 doesn't support text mode. I know that this module is very old one (over 6 years) but when using it with other softwares it works fine, but with nowsms I get this problem. I've addes the smsgw.ini (I even tried adding presend commands, but nothing): [Modem - COM1:] ReceiveSMS=No ReceiveMMS=No SMSC=+385910401 CommandPreSend1=AT CommandPreSend2=ATE0 CommandPreSend3=ATE0Q0V1 CommandPreSend4=AT&S0 CommandPreSend5=AT&C0 CommandPreSend6=AT+CMGF=0 CommandPreSend7=AT+CPMS="SM" CommandPreSend8=AT+CNMI=2,0,0,0,0 [SMSGW] Modem1=COM1: WebAuth=No WebMenu=Yes WebPort=8800 ReceiveSMS=No ReceiveMMS=No Debug=Yes | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2912 Registered: 10-2002 |
Hi Boole, We only use PDU mode, so that should not be an issue. Since it is such an old module, I was thinking that the SMSC setting might be an issue. I know we had someone else that was trying to use an M1, and experienced similar problems to what you describe, so they gave up and used a different modem. When I look at the debug log above, I think it is very unusual that there is a period of 5 or 6 seconds that elapses between the time that we pass the message to the modem, and the "ERROR" response comes back. This suggests to me that the modem is, in fact, attempting to process the message. If there were a message formatting issue, the modem would return back an "ERROR" more quickly. So, I am not sure what the issue could be here. I've done a little bit of searching, and I found an old document with an example of sending an SMS with the M1. The only thing that jumps out to me (other than the requirement that the SMSC be specified in the PDU, which the INI file parameter should be doing, or set via the AT+CSCA="+xxx" command) ... is that the example includes the optional validity period parameter in the message submission. Try submitting a mesasge to NowSMS using the URL format, but include a "&Valid=" parameter. For example, http://127.0.0.1:8800/?PhoneNumber=%2B385914691621&text=test+message&Valid=7D The "&Valid=" parameter allows the validity period to be set in the outgoing message. Valid values are xxD, xxH or xxM, where "xx" is a number, and the "D", "H", or "M" parameter indicates days, hours or minutes. Does that make a difference? -bn | |||
| BooLE New member Username: Boole Post Number: 3 Registered: 06-2004 |
Hi Bryce, to skip intro, here is debug log: 09:35:22:781 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 09:35:24:796 [5] ThreadProcessConnection: Processing request /?PhoneNumber=%2B385914691621&text=test+message&Valid=7D 09:35:24:796 [5] Debug: 1 recipient entries 09:35:24:796 [5] Debug: +385914691621 09:35:24:890 [2] ThreadProcessModem: Processing 40DFCA3C.req... 09:35:24:890 [2] ThreadProcessModem: OUT: AT+CMGS=24 09:35:24:953 [2] ThreadProcessModem: IN: > 09:35:24:953 [2] ThreadProcessModem: OUT: 069183950104F101000C9183954196611200000CF4F29C0E6A97E7F3F0B90C 09:35:29:062 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 09:35:29:062 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 09:35:30:125 [2] ThreadProcessModem: Processing 40DFCA3C.req... 09:35:30:125 [2] ThreadProcessModem: OUT: AT+CMGS=24 09:35:30:187 [2] ThreadProcessModem: IN: > 09:35:30:187 [2] ThreadProcessModem: OUT: 069183950104F101000C9183954196611200000CF4F29C0E6A97E7F3F0B90C 09:35:35:906 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 09:35:35:906 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 09:36:05:968 [2] ThreadProcessModem: Processing 40DFCA3C.req... 09:36:05:968 [2] ThreadProcessModem: OUT: AT+CMGS=24 09:36:06:031 [2] ThreadProcessModem: IN: > 09:36:06:031 [2] ThreadProcessModem: OUT: 069183950104F101000C9183954196611200000CF4F29C0E6A97E7F3F0B90C 09:36:10:203 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 09:36:10:203 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 09:37:10:343 [2] ThreadProcessModem: Processing 40DFCA3C.req... 09:37:10:343 [2] ThreadProcessModem: OUT: AT+CMGS=24 09:37:10:406 [2] ThreadProcessModem: IN: > 09:37:10:406 [2] ThreadProcessModem: OUT: 069183950104F101000C9183954196611200000CF4F29C0E6A97E7F3F0B90C 09:37:14:281 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 09:37:14:281 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR 09:38:44:390 [2] ThreadProcessModem: Processing 40DFCA3C.req... 09:38:44:390 [2] ThreadProcessModem: OUT: AT+CMGS=24 09:38:44:468 [2] ThreadProcessModem: IN: > 09:38:44:468 [2] ThreadProcessModem: OUT: 069183950104F101000C9183954196611200000CF4F29C0E6A97E7F3F0B90C 09:38:48:203 [2] ThreadProcessModem: ERROR - Modem Response (2): ERROR 09:38:48:203 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): ERROR Maybe I can give you a part of log of working application? Message text is: ----------------------(not part of SMS, just separator) test (Sent using SMS Gateway www.winsms.com) ----------------------(not part of SMS, just separator) SMS Gateway - Communications Log Date/Time :28.06.2004 09:44:37 Operating System :Windows NT 5.0 (Build 2195: Service Pack 2) Memory :523.804 KB SMS Gateway :Version: 11.4.8cp-v - Evaluation [Configuration] Port=1 Speed=19200 Flow Control=NONE Communication Retries=3 Communication Timeout=45 Transmit Pacing=0 Init String=E0 Init String 2= Init String 3= Interface=PDU Mode Enter Block Mode Command= Wait OK=0 PIN Code= Service Centre Address=+385910401 SCA in TPDU=0 Transfer Mode=2 Transfer MT=1 Transfer BM=0 Transfer DS=0 Transfer BFR=0 Mem1=SM Mem2= Mem3= Check RSSI=20 Hardware=Siemens M1 Nokia Segmentation=0 [Startup] Auto Connect=0 Auto Connect wait DSR=0 Auto ReConnect DSR=1 Auto ReConnect CD=1 WorkingDir= Disable Close Button=0 Show Send Message Content=1 Show Receive Message Content=1 Show Send Queue=1 Show Receive Queue=1 Show Interactive Controls=1 Use System Tray Icon=1 Show Receiving Application=1 Show COMMS details in Status Bar=1 Show POP3 details in Status Bar=1 Show SMTP details in Status Bar=1 Strip non pintable characters from logs=1 [Receive Message] Startup Transfer=0 OLE Timeout=60 Purge After Connect Attempts=3 [Test Message] Destination=0914691621 [HTTP] Host=127.0.0.1 Port=8088 Mngt Enabled=1 Mngt UserID= Mngt Password= Mngt IP Allow List= Submit XML Enabled=0 Submit HTML Enabled=0 Submit IP Allow List=* Submit IP Block List= Receive Enabled=0 Receive Timer=5 Receive Timeout=5 Receive URL= Receive UserID= Receive Password= [Database] Pack Time=12:00:00AM [Failure Options] Purge Radio Fail=0 Purge Program Close=0 Purge Send 3 Errors=0 [Debugging] Communications=1 POP3=1 SMTP=1 HTTP=1 Overwrite at startup=1 Max log size=5 Attempting to connect to Mobile Terminal FlowControl is None Signal event - DSR ON Signal event - RLSD ON Port open successful : Connected to COM1 Signal state after open : CTS=ON RLSD=OFF DSR=ON [TX: 09:44:39 00 01] AT [RX: 09:44:39 00 01] OK [TX: 09:44:40 01 02] ATE0 [RX: 09:44:40 01 02] OK [TX: 09:44:40 02 03] AT [RX: 09:44:40 02 03] OK [TX: 09:44:40 03 04] AT [RX: 09:44:40 03 04] OK Signal event - RLSD ON [TX: 09:44:40 04 05] ATE0Q0V1 [RX: 09:44:40 04 05] OK [TX: 09:44:40 05 06] AT&S0 [RX: 09:44:40 05 06] OK [TX: 09:44:41 06 07] AT&C0 [RX: 09:44:41 06 07] OK [TX: 09:44:42 07 08] AT+GMI [RX: 09:44:42 07 08] +CGMI: SIEMENS [RX: 09:44:42 07 09] OK [TX: 09:44:42 08 09] AT+GMM [RX: 09:44:42 09 0A] +CGMM: M1 [RX: 09:44:42 09 0B] OK [TX: 09:44:43 09 0A] AT+GMR [RX: 09:44:43 0B 0C] +CGMR: Ver.04.003 01.04.97 [RX: 09:44:43 0B 0D] OK [TX: 09:44:45 0A 0B] AT+CSMS=? [RX: 09:44:45 0D 0E] +CSMS: 0 [RX: 09:44:45 0D 0F] OK [TX: 09:44:46 0B 0C] AT+CMGF=? [RX: 09:44:46 0F 10] +CMGF: 0 [RX: 09:44:46 0F 11] OK [TX: 09:44:46 0C 0D] AT+CSCS=? [RX: 09:44:46 11 12] ERROR [TX: 09:44:46 0D 0E] AT+CPMS=? [RX: 09:44:46 12 13] +CPMS: "SM", "SM" [RX: 09:44:46 12 14] OK [TX: 09:44:47 0E 0F] AT+CNMI=? [RX: 09:44:47 14 15] +CNMI: 0 1 2, 0 1 2, 0, 0, 0 [RX: 09:44:47 14 16] OK [TX: 09:44:47 0F 10] AT+CMGF=0 [RX: 09:44:47 16 17] OK [TX: 09:44:47 10 11] AT+CPMS="SM" [RX: 09:44:47 17 18] +CPMS: 12 , 25 , 12 , 25 [RX: 09:44:47 17 19] OK [TX: 09:44:47 11 12] AT+CSCA="+385910401" [RX: 09:44:47 19 1A] OK [TX: 09:44:48 12 13] AT+CNMI=2,0,0,0,0 [RX: 09:44:48 1A 1B] OK [TX: 09:44:48 13 14] AT+CNMI=2,0,0,0 [RX: 09:44:48 1B 1C] OK [TX: 09:45:01 14 15] AT+CSQ [RX: 09:45:02 1C 1D] +CSQ: 29 , 99 [RX: 09:45:02 1C 1E] OK [TX: 09:45:21 15 16] AT+CSQ [RX: 09:45:22 1E 1F] +CSQ: 28 , 99 [RX: 09:45:22 1E 20] OK [TX: 09:45:41 16 17] AT+CSQ [RX: 09:45:42 20 21] +CSQ: 29 , 99 [RX: 09:45:42 20 22] OK [TX: 09:46:01 17 18] AT+CSQ [RX: 09:46:02 22 23] +CSQ: 28 , 99 [RX: 09:46:02 22 24] OK [TX: 09:46:21 18 19] AT+CSQ [RX: 09:46:22 24 25] +CSQ: 29 , 99 [RX: 09:46:22 24 26] OK [TX: 09:46:41 19 1A] AT+CSQ [RX: 09:46:42 26 27] +CSQ: 29 , 99 [RX: 09:46:42 26 28] OK [TX: 09:47:01 1A 1B] AT+CSQ [RX: 09:47:02 28 29] +CSQ: 29 , 99 [RX: 09:47:02 28 2A] OK [TX: 09:47:21 1B 1C] AT+CSQ [RX: 09:47:22 2A 2B] +CSQ: 29 , 99 [RX: 09:47:22 2A 2C] OK [TX: 09:47:41 1C 1D] AT+CSQ [RX: 09:47:42 2C 2D] +CSQ: 28 , 99 [RX: 09:47:42 2C 2E] OK [TX: 09:48:01 1D 1E] AT+CSQ [RX: 09:48:02 2E 2F] +CSQ: 29 , 99 [RX: 09:48:02 2E 30] OK [TX: 09:48:21 1E 1F] AT+CSQ [RX: 09:48:22 30 31] +CSQ: 29 , 99 [RX: 09:48:22 30 32] OK [TX: 09:48:41 1F 20] AT+CSQ [RX: 09:48:42 32 33] +CSQ: 29 , 99 [RX: 09:48:42 32 34] OK [TX: 09:49:01 20 21] AT+CSQ [RX: 09:49:02 34 35] +CSQ: 29 , 99 [RX: 09:49:02 34 36] OK [TX: 09:49:21 21 22] AT+CSQ [RX: 09:49:22 36 37] +CSQ: 29 , 99 [RX: 09:49:22 36 38] OK [TX: 09:49:41 22 23] AT+CSQ [RX: 09:49:42 38 39] +CSQ: 29 , 99 [RX: 09:49:42 38 3A] OK [TX: 09:50:01 23 24] AT+CSQ [RX: 09:50:02 3A 3B] +CSQ: 29 , 99 [RX: 09:50:02 3A 3C] OK [TX: 09:50:21 24 25] AT+CSQ [RX: 09:50:22 3C 3D] +CSQ: 29 , 99 [RX: 09:50:22 3C 3E] OK [TX: 09:50:41 25 26] AT+CSQ [RX: 09:50:42 3E 3F] +CSQ: 29 , 99 [RX: 09:50:42 3E 40] OK [TX: 09:50:46 26 28] AT+CMGS=54 [RX: 09:50:46 40 41] > [TX: 09:50:46 27 28] 11000C918395419661120000A72DF4F29CAE50A0A665371D549FA7DD67D0B439051DC3F4F23D9C07 DDEF77D73DED9EB7E7AEF1BB9D02 [RX: 09:50:51 41 42] +CMGS: 1 [RX: 09:50:51 41 43] OK [TX: 09:51:01 28 29] AT+CSQ [RX: 09:51:02 43 44] +CSQ: 29 , 99 [RX: 09:51:02 43 45] OK | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2927 Registered: 10-2002 |
Hi Boole, Ok ... between that log, and some other investigation, I've found that there is a bug in the M1 in PDU mode. The M1 was a very early device, and so I don't know if I'd necessarily call it a bug, or more likely the specifications were not complete at the time. Do me a favour and send an e-mail message to nowsms@now.co.uk referencing this issue, and I will e-mail you a ZIP file with an update. In this update, you can edit the [Modem - driver name] section of the SMSGW.INI file, and add an entry ExcludeSMSC=Yes under that section header. I believe that will provide a work-around for the M1. I believe the other software is identifying that it is connecting to an M1, and is using alternate encoding logic. -bn | |||
| BooLE New member Username: Boole Post Number: 4 Registered: 06-2004 |
Hi Bryce, I've sent you an e-mail, but I wonder, if it will fix the problem, maybe you'll have to adapt the whole encoding for M1, and I hope that you won't say that it is too old module, because I have 5 of kind (like in poker), and I need to use them for alerting. Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2941 Registered: 10-2002 |
I've sent you the update, so let me know how it goes. If it works, all you have to do is edit a configuration file entry for each of the M1 modem definitions. If it doesn't work, I'll have to study the above messages in more detail. -bn | |||
| BooLE New member Username: Boole Post Number: 5 Registered: 06-2004 |
Hi Bryce, yes it worked, here is a copy of smsgw.INI used: [Modem - COM1:] ReceiveSMS=No ReceiveMMS=No ExcludeSMSC=Yes [SMSGW] Modem1=COM1: WebAuth=No WebMenu=Yes WebPort=8800 ReceiveSMS=No ReceiveMMS=No Debug=Yes Big thanks for that update. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2948 Registered: 10-2002 |
That is excellent. Thanks for the follow-up report. | |||
| BooLE New member Username: Boole Post Number: 7 Registered: 06-2004 |
Np. Will you put this as a release on site for others to download? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2980 Registered: 10-2002 |
It is available now, along with a few other updates. There is a patch download to update v5.50 at the following URL: http://www.nowsms.com/download/nowsms550c.zip | |||
