| Sms gateway must be restartet - it hangs |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| jfanzott |
the now sms gateway service seems to run in a correct manner BUT after a certain time (certain sms received - maybe) the service has to be restartet - serveral times during the day - when we use it to receive sms messages - because it hangs!!! please finde the errors log find enclosed (we xxx'ed some entries in the log file to hide personal information!) our configuration: now sms trial version: v4.20 (b20030528) we use 4 com interfaces we use http request for the received sms os: windows 2000 professional 21:05:51:958 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 21:05:53:980 [0] main: preferred sender = +436766577050,Standard 9600 bps Modem 21:05:53:980 [0] main: preferred sender = +436641270100,Standard 9600 bps Modem #2 21:05:53:990 [0] main: preferred sender = +436645672777,Standard 9600 bps Modem #3 21:05:53:990 [0] main: preferred sender = +436642737899,Standard 9600 bps Modem #4 21:05:54:000 [2] ThreadProcessModem: Re-initializing modem: Standard 9600 bps Modem ... 21:05:54:000 [3] ThreadProcessModem: Re-initializing modem: Standard 9600 bps Modem #2 ... 21:05:54:000 [4] ThreadProcessModem: Re-initializing modem: Standard 9600 bps Modem #3 ... 21:05:54:041 [5] ThreadProcessModem: Re-initializing modem: Standard 9600 bps Modem #4 ... 21:05:54:211 [0] main: 44 Days remaining in trial version 21:05:55:062 [3] ThreadProcessModem: AT+CPMS? 21:05:55:112 [2] ThreadProcessModem: AT+CPMS? 21:05:55:182 [3] ThreadProcessModem: +CPMS: "SM",0,10,"SM",0,10 OK 21:05:55:182 [3] ThreadProcessModem: Modem initialization complete: Standard 9600 bps Modem #2 21:05:55:202 [4] ThreadProcessModem: AT+CPMS? 21:05:55:212 [5] ThreadProcessModem: AT+CPMS? 21:05:55:232 [2] ThreadProcessModem: +CPMS: "SM",1,20,"SM",1,20 OK 21:05:55:242 [2] ThreadProcessModem: Modem initialization complete: Standard 9600 bps Modem 21:05:55:322 [4] ThreadProcessModem: +CPMS: "SM",12,15,"SM",12,15 OK 21:05:55:322 [4] ThreadProcessModem: Modem initialization complete: Standard 9600 bps Modem #3 21:05:55:372 [5] ThreadProcessModem: +CPMS: "SM",5,15,"SM",5,15 OK 21:05:55:372 [5] ThreadProcessModem: Modem initialization complete: Standard 9600 bps Modem #4 21:05:59:128 [5] ModemReceiveMessages: +CMGL: 1,0,,59 069134660405F1040C913466546712310000300180027583802DD374F9CC4EBBC96516A8E977EBCB 7216E828AFD3E76374D90DA2E158A05C2C366381A47572D9CD02 +CMGL: 2,0,,61 069134660405F1000C91346614198262000030018071041480305474595E9EA7C3A0E9DB6D4FB3D9 6110753E46DFC3727DD90DB28140B99A0D063296D9E4755A3E4697DD +CMGL: 3,0,,20 069134660405F1000C913466649232340000300180716142800142 +CMGL: 4,0,,60 069134660405F1040C913466542633670000300180814082802EC824935864119F556570C92216AB D4A213F934169D53AAD425CBB17230198CB564068F45A7B12AA502 OK 21:05:59:128 [5] ModemReceiveMessages: Decoding received message index 1 from message storage ME 21:05:59:128 [5] ModemReceiveMessages: SMSC address len = 6 21:05:59:128 [5] ModemReceiveMessages: SMSC Address = +436640501 21:05:59:128 [5] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 21:05:59:128 [5] ModemReceiveMessages: Sender address len = 12 21:05:59:128 [5] ModemReceiveMessages: Sender Address = +436645762113 21:05:59:128 [5] ModemReceiveMessages: PID = 00 21:05:59:128 [5] ModemReceiveMessages: DCS = 00 21:05:59:128 [5] ModemReceiveMessages: Anticipated user data length = 45 21:05:59:128 [5] ModemReceiveMessages: Message = xxxxx, xxx, xxxx, 9113, Ruden, 21:05:59:128 [5] ModemReceiveMessages: AT+CMGD=1 21:05:59:228 [6] ThreadProcessInboundSMS: Processing 3F846017.in... 21:05:59:508 [6] ThreadProcessInboundSMS: Executing http://212.xx.xx.xx/inbound/inbound.aspx?SMS_PREFIX=xxxx%2C&SMS_TEXT=M%C3%BCnzer %2C%20Grutschen%2048%2C%209113%2C%20xxxx%2C&SENDER=%2B436645xxxxx&RECIP=%2B43664 27xxxxx&FULL_SMS=xxxxe%2C%20M%C3%BCnzer%2C%20xxxxx%2048%2C%209113%2C%20Ruden%2C 21:05:59:508 [6] RetrieveURL: Retrieving http://212.xxx.xx.165/inbound/inbound.aspx?SMS_PREFIX=xxxxx%2C&SMS_TEXT=M%C3%BCn zer%2C%20Grutxxxx%2048%2C%209113%2C%20Ruden%2C&SENDER=%2B4366xxxx2113&RECIP=%2B4 366xxxx3899&FULL_SMS=xxxnde%2C%20M%C3%BCnzer%2C%20Grxxxn%2048%2C%209113%2C%20Rxx xn%2C 21:05:59:518 [6] RetrieveURL: Retrieving inbound/inbound.aspx?SMS_PREFIX=xxxlinde%2C&SMS_TEXT=M%C3%BCnxxxr%2C%20Grxxxn%20 48%2C%209113%2C%20xxx%2C&SENDER=%2B4366xxxx3&RECIP=%2B436xxxx899&FULL_SMS=xxxnde %2C%20M%C3%BCnzer%2C%20Gxxxxhen%2048%2C%209113%2C%20xxxxn%2C 21:05:59:518 [6] RetrieveURL: GET /inbound/inbound.aspx?SMS_PREFIX=Sxxxx%2C&SMS_TEXT=M%C3%BCnzer%2C%20xxxxxn%2048% 2C%209113%2C%20xxxxn%2C&SENDER=%2B436xxxx&RECIP=%2B436xxxxxx&FULL_SMS=xxxxxxxx%2 C%20M%C3%BCnzer%2C%20Gxxxxn%2048%2C%20xxx3%2C%20xxxxen%2C HTTP/1.0 User-Agent: Now SMS/MMS Gateway v4.20 (b20030528) Accept: */* Connection: Close Host: 212.17.98.165 Accept: */* 21:05:59:669 [6] RetrieveURL: got success response 21:05:59:669 [6] RetrieveURL: text/html; 21:09:28:068 [6] RetrieveURL: text/html; 21:09:28:409 [5] ModemReceiveMessages: AT+CMGD=1 OK 21:09:29:611 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:29:851 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:31:053 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:31:273 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:32:475 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:32:695 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:33:897 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:34:117 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:35:319 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:35:539 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:36:741 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:36:961 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:38:163 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:38:383 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:39:585 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:39:805 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:41:007 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:41:227 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:42:429 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:42:649 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:43:851 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:44:071 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:45:273 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:45:493 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:46:695 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:46:915 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:48:117 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:48:337 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:49:539 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:49:759 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:50:961 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:51:182 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:52:383 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:52:604 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:53:805 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:09:54:026 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:10:42:565 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:10:43:767 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 21:10:43:987 [5] ModemReceiveMessages: AT+CMGL=0 ERROR 22:56:07:080 [0] main: Shutdown: Closing log files | |||
| Bryce Norwood - NowSMS Support |
Hi, It looks like the modem is what is hanging. When we issue a command to check the modem for messages, the modem is reporting back an "ERROR". Are you able to actually get things working again by restarting the NowSMS service? (Without restarting the modems?) If so, then you might want to try updating to the v5.0 release. In this release, if we get an error back from a modem in this particular area, we automatically re-initialise the modem (just as restarting the service would do). We made this change in v5.0 because of another installation that encountered a similar problem. Also in v5.0 ... for each of the modems defined in your "SMSC" list, select "Properties", and under "Receive Messages", I would suggest changing "SMS Message Storage" to "SIM Card" ... based upon the response to the AT+CPMS command that I see in your log. This setting may help prevent the error from occurring on the modem in the first place. | |||
| jfanzott |
Are you able to actually get things working again by restarting the NowSMS service? (Without restarting the modems?) Yes we only restart the service - not the modem we now try the v5.0 question: if i use the option 'sms message storage' to 'SIM Card' - what happens if there are more sms coming in than the sim card memory can save? | |||
| Bryce Norwood - NowSMS Support |
NowSMS is going to pull them off there as quick as it can to free up space. I should mention that you can also use the "receive message to" "device memory" setting, if your modem supports it. When I took a quick look at your log, I made an incorrect assumption that your modem only supported storing the messages on the SIM card. (The v5.0 release includes more queries in the debug log. Your modem might support storing received messages to device memory.) -bn | |||
| jfanzott |
fyi: we use a Fastrack GSM M1200 Series modem | |||
| Bryce Norwood - NowSMS Support |
I think you need to specify receive to SIM card for that device, but you can try both settings. (I think either setting will perform better than the "Default" in this case.) | |||
