GSM Zoom phone not working
Serverscheck ver 10.1.0
Bus 500 version
Zoom modem attached com5 via usb to server
green light on modem, flashing.
cp on win server indicates the modem is on com5 and is working. Sending test message:
SMS debugging information:
COM port set to COM5
SMSC number returned by SIM: +CSCA: "+12063130004",145
SMS message was succesfully sent to 1925437xxxx
DON'T FORGET TO RESTART THE MONITORING SERVICE
Issue is I did not receive any serverscheck sms message?
Bus 500 version
Zoom modem attached com5 via usb to server
green light on modem, flashing.
cp on win server indicates the modem is on com5 and is working. Sending test message:
SMS debugging information:
COM port set to COM5
SMSC number returned by SIM: +CSCA: "+12063130004",145
SMS message was succesfully sent to 1925437xxxx
DON'T FORGET TO RESTART THE MONITORING SERVICE
Issue is I did not receive any serverscheck sms message?
This discussion has been closed.
Comments
You can always run the web server in debug mode, try sending the alert and check out the communication with the modem in the debug log. You are also welcome to post it here so that users and we can have a look
#
# ServersCheck Web Server
# BUSINESS500 Edition
# ServersCheck BUSINESS500 Edition - version 10.1.0
#
# Number of monitors allowed: 500
#
# Installed on - SERVERSCHECK2
#
# Loading language file: EN.lang
# version 10.1.0
#
# ServersCheck MSP license loaded
#
# (c) Copyright 2003-2013 - ServersCheck BVBA
# www.serverscheck.com
#
#
#
#
#
# Start: Thu Aug 22 12:54:54 2013 - End: Thu Aug 22 12:54:54 2013
#
# Configuration server ready, serving on port "1272"...
#
#
# Thu Aug 22 12:55:45 2013 Reading configuration file - last was
# Thu Aug 22 12:55:45 2013 Reading conf file completed
# Thu Aug 22 12:55:46 2013 Importing current status of each monitor
# Thu Aug 22 12:55:46 2013 End importing current status of each monitor
+++
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
ATE0
AT+CSCA?
# Thu Aug 22 12:56:18 2013 Service center number is: +CSCA: "+12063130004",145 (configured: )
AT+CMGF=0
# Thu Aug 22 12:56:18 2013 Sending SMS to 1925437xxxx
AT+CPIN?
ATE1
AT+CMGF=0
AT+CMGS=49
0011000B819152349791F50000A728D4F29C0E9A36A7A01648A180BEEF6579990C12E715D3B2DC5E96CF87E8F278ED1ABFDB
# GSM Thu Aug 22 12:56:22 2013 Send result : 1
# Thu Aug 22 12:56:22 2013 SMS message was succesfully sent to 19254379195
# Thu Aug 22 12:56:38 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 12:56:38 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 12:56:46 2013 Reading configuration file - last was 1377201345
# Thu Aug 22 12:56:46 2013 Reading conf file completed
# Thu Aug 22 12:57:10 2013 Importing current status of each monitor
# Thu Aug 22 12:57:10 2013 End importing current status of each monitor
# Thu Aug 22 12:57:10 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 12:57:10 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 12:57:15 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 12:57:15 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 12:58:14 2013 Reading configuration file - last was 1377201406
# Thu Aug 22 12:58:14 2013 Reading conf file completed
# Thu Aug 22 12:58:14 2013 Importing current status of each monitor
# Thu Aug 22 12:58:14 2013 End importing current status of each monitor
# Thu Aug 22 12:58:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 12:58:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 12:59:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 12:59:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 12:59:15 2013 Reading configuration file - last was 1377201494
# Thu Aug 22 12:59:15 2013 Reading conf file completed
# Thu Aug 22 12:59:16 2013 Importing current status of each monitor
# Thu Aug 22 12:59:16 2013 End importing current status of each monitor
# Thu Aug 22 13:00:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 13:00:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 13:00:16 2013 Reading configuration file - last was 1377201555
# Thu Aug 22 13:00:16 2013 Reading conf file completed
# Thu Aug 22 13:00:46 2013 Importing current status of each monitor
# Thu Aug 22 13:00:46 2013 End importing current status of each monitor
# Thu Aug 22 13:01:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 13:01:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 13:01:46 2013 Reading configuration file - last was 1377201616
# Thu Aug 22 13:01:46 2013 Reading conf file completed
# Thu Aug 22 13:02:14 2013 Importing current status of each monitor
# Thu Aug 22 13:02:14 2013 End importing current status of each monitor
# Thu Aug 22 13:02:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 13:02:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 13:03:14 2013 Reading configuration file - last was 1377201706
# Thu Aug 22 13:03:14 2013 Reading conf file completed
# Thu Aug 22 13:03:14 2013 Logs from 1377154800:Thu Aug 22 00:00:00 2013 to 1377241200:Fri Aug 23 00:00:00 2013
# Thu Aug 22 13:03:14 2013 Scanning log: alerts-2013-8-22
# Thu Aug 22 13:03:16 2013 Importing current status of each monitor
# Thu Aug 22 13:03:16 2013 End importing current status of each monitor
Please verify your modem and if that is ok, then please check with your mobile operator
Here is debug.txt > Now what to try?
# Starting up app
# Fri Aug 23 08:02:17 2013 file modem.log cleaned
#
# ServersCheck Web Server
# BUSINESS500 Edition
# ServersCheck BUSINESS500 Edition - version 10.1.0
#
# Number of monitors allowed: 500
#
# Installed on - SERVERSCHECK2
#
# Loading language file: EN.lang
# version 10.1.0
#
# ServersCheck MSP license loaded
#
# (c) Copyright 2003-2013 - ServersCheck BVBA
# www.serverscheck.com
#
#
#
#
#
# Start: Fri Aug 23 08:02:17 2013 - End: Fri Aug 23 08:02:17 2013
#
# Configuration server ready, serving on port "1272"...
#
#
# Fri Aug 23 08:02:38 2013 Reading configuration file - last was
# Fri Aug 23 08:02:38 2013 Reading conf file completed
# Fri Aug 23 08:02:38 2013 Importing current status of each monitor
# Fri Aug 23 08:02:38 2013 End importing current status of each monitor
+++
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
ATE0
AT+CSCA?
# Fri Aug 23 08:03:07 2013 Service center number is: +CSCA: "+12063130004",145 (configured: )
AT+CMGF=0
# Fri Aug 23 08:03:07 2013 Sending SMS to 1925437xxxx
AT+CPIN?
ATE1
AT+CMGF=0
AT+CMGS=49
0011000B819152349791F50000A728D4F29C0E9A36A7A01648A180BEEF6579990C12E715D3B2DC5E96CF87E8F278ED1ABFDB
# GSM Fri Aug 23 08:03:11 2013 Send result : 1
# Fri Aug 23 08:03:11 2013 SMS message was succesfully sent to 19254379195
# Fri Aug 23 08:03:30 2013 Logs from 1377241200:Fri Aug 23 00:00:00 2013 to 1377327600:Sat Aug 24 00:00:00 2013
# Fri Aug 23 08:03:30 2013 Scanning log: alerts-2013-8-23
# Fri Aug 23 08:04:08 2013 Reading configuration file - last was 1377270158
# Fri Aug 23 08:04:08 2013 Reading conf file completed
# Fri Aug 23 08:04:08 2013 Importing current status of each monitor
# Fri Aug 23 08:04:08 2013 End importing current status of each monitor
2) Did it ever work before? If so, then what has been changed since last time it worked?
C:Program Files (x86)>cd serverscheck_monitoring
C:Program Files (x86)ServersCheck_Monitoring>
s-alerts.exe > alerts.txt
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
C:Program Files (x86)ServersCheck_Monitoring>
# MODEM Fri Aug 23 08:03:06 2013 s-server.exe info sending init string...
# MODEM Fri Aug 23 08:03:06 2013 s-server.exe info sending attention sequence...
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info reached timeout max wait without response
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read []
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read [^MOK^M]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `OK'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info disabling echo
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read [ATE0^MOK^M]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `ATE0^MOK'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info Ok connected
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info requesting service center number
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read [^M+CSCA: "+12063130004",145^M^MOK^M]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `+CSCA: "+12063130004",145^M^MOK'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info service center number is [+CSCA: "+12063130004",145]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info setting mode to [pdu]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read [^MOK^M]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `OK'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info Not yet registered, doing now...
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info PIN status query
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: read [^M+CPIN: READY^M^MOK^M]
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info answer: `+CPIN: READY^M^MOK'
# MODEM Fri Aug 23 08:03:07 2013 s-server.exe info Already registered on network. Ready to send.
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info answer: read [^MOK^M]
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info answer: `OK'
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info encoded dest. address is [0B819152349791F5]
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info encoded 7bit text (w/length) is [28D4F29C0E9A36A7A01648A180BEEF6579990C12E715D3B2DC5E96CF87E8F278ED1ABFDB]
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info due to send PDU [0011000B819152349791F50000A728D4F29C0E9A36A7A01648A180BEEF6579990C12E715D3B2DC5E96CF87E8F278ED1ABFDB]
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info answer: read [AT+CMGF=0^MOK^M]
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info answer: `AT+CMGF=0^MOK'
# MODEM Fri Aug 23 08:03:09 2013 s-server.exe info Selected PDU format for msg sending
# MODEM Fri Aug 23 08:03:10 2013 s-server.exe info reached timeout max wait without response
# MODEM Fri Aug 23 08:03:10 2013 s-server.exe info answer: read [AT+CMGS=49^M> ]
# MODEM Fri Aug 23 08:03:10 2013 s-server.exe info answer: `AT+CMGS=49^M> '
# MODEM Fri Aug 23 08:03:10 2013 s-server.exe info PDU sent [0011000B819152349791F50000A728D4F29C0E9A36A7A01648A180BEEF6579990C12E715D3B2DC5E96CF87E8F278ED1ABFDB + CTRLZ]
# MODEM Fri Aug 23 08:03:11 2013 s-server.exe info answer: read [^M^M+CMGS: 141^M^MOK^M]
# MODEM Fri Aug 23 08:03:11 2013 s-server.exe info answer: `+CMGS: 141^M^MOK'
# MODEM Fri Aug 23 08:03:11 2013 s-server.exe info Sent SMS (pdu mode) to 19254379195!
# MODEM Fri Aug 23 08:03:11 2013 s-server.exe info Disconnected from .COM4
what has changed is I bought (3) gateway sensors from you last month. I configured the gw and connected humidity, temp & power sensors to gw. Now all those work fine but my gsm modem stopped sending out alerts. email alerts are working, but not the sms part.
If sms alerting worked before and does no longer work, then something in the software must have changed:
1) upgrade server
2) upgrade software
3) new install
4) modem moved to a new usb port
etc...
No zoom log was added in previous comments; only ServersCheck logs. Do you have modem log entries from when the setup was running fine?
Knowing what changed allows to see how it can be brought back to a previous known working state.
Name Mobile Connector
Description Mobile Connector
Device ID USBVID_1C9E&PID_9603&MI_026&2730978D&2&0002
Device Type External Modem
Attached To COM5
Answer Mode Not Available
PNP Device ID USBVID_1C9E&PID_9603&MI_026&2730978D&2&0002
Provider Name Mobile Connector
Modem INF Path oem21.inf
Modem INF Section Modem2
Blind Off Not Available
Blind On Not Available
Compression Off Not Available
Compression On Not Available
Error Control Forced Not Available
Error Control Off Not Available
Error Control On Not Available
Flow Control Hard Not Available
Flow Control Off Not Available
Flow Control Soft Not Available
DCB 
Default 
Inactivity Timeout 0
Modulation Bell Not Available
Modulation CCITT Not Available
Prefix AT
Pulse P
Reset AT&F<cr>
Responses Key Name Mobile Connector::Mobile Connector::Mobile Connector
Speaker Mode Dial Not Available
Speaker Mode Off Not Available
Speaker Mode On Not Available
Speaker Mode Setup Not Available
Speaker Volume High Not Available
Speaker Volume Low Not Available
Speaker Volume Med Not Available
String Format Not Available
Terminator <cr>
Tone T
Driver c:windowssystem32driversmodem.sys (6.0.6001.18000, 39.50 KB (40,448 bytes), 1/18/2008 10:38 PM)
"If sms alerting worked before and does no longer work, then something in the software must have changed:
1) upgrade server
2) upgrade software
3) new install
4) modem moved to a new usb port
etc...
No zoom log was added in previous comments; only ServersCheck logs. Do you have modem.log entries from when the setup was running fine?
Knowing what changed allows to see how it can be brought back to a previous known working state."
We want to know what configuration worked previously so that we can return to that configuration. The modem.log generated by ServersCheck might help in that respect.
Thank you
What was changed on the system/configuration between the time it worked and it no longer worked?
I don't think this would have anything to do with the gsm issue but still it should be registering the correct version.
so we don't have a known good state to go back too :-(
let's start all over again from scratch. we know the modem works based on your tests.
let's do it step by step.
what com ports is the modem listed on in Windows in the Device Manager. If your modem has more than one com port for the modem listed, then please provide the descriptions next to the modem.
See below email, they recommending changing the Win com5 > com4. Then serverscheck alerting has to change as well.
To you agree?
Just got email from zoom modem techs:
Joyce P. (SmartFacts Customer Assistant)
Aug 28 05:20 pm (EDT)
The software always default to COM 4 and you cannot change this in the software but the COM can be easily changed in Windows in the properties of the modem from Com 5 to Com 4
If it is on COM5 then it may mean that something else is using COM4.
Set it in our software to COM5 (if that still is the port shown in the Windows Device Manager).
When that is done then make sure that no Zoom software is running and that all ServersCheck services are stopped.
Then run the s-alerts.exe from the command prompt in debug mode and send us the debug output after letting it run for one minute (allows us to check if modem communications works)
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:UsersAdministrator>cd..
C:Users>cd..
C:>cd program files (x86)
C:Program Files (x86)>cd serverscheck_monitoring
C:Program Files (x86)ServersCheck_Monitoring>s-alerts.exe > debug.txt
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
can't open device: .COM4
at /<C:Program Files (x86)ServersCheck_Monitorings-alerts.exe>Device/Modem.p
m line 492
Thank you