but what is contained in the debug file? Just the header text? Nothing related to the CSCA value?
In order to make sure that I fully understand your configuration and setup, could you please do following?
Can you please just run the s-alerts.exe from the command prompt and then send all output (including header text) as a reply (so not sending it to a debug file).
It fails in the code where it actually tries to open the COM port, so not even sending the SMS. Nothing else is using that COM5 port?
trevorw
Here we go !
C:>cd program filesserverscheck_monitoring
C:Program FilesServersCheck_Monitoring>s-alerts
#
#
# ServersCheck Alerting & Notification Component
# version 6.9.0
#
#
# (c) Copyright 2003-2006 - ServersCheck BVBA
# www.serverscheck.com
#
# IP address: 10.51.17.157
#
#
# Tue Dec 12 18:17:27 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Tue Dec 12 18:17:27 2006 processing alert ID
# Tue Dec 12 18:17:33 2006 CSCA set to +447973100973
# Tue Dec 12 18:17:33 2006 Serial port set to COM5
# Tue Dec 12 18:17:33 2006 Pin code set to 0000 - Pin code has to be desactivate
d
invalid COMMPROP block length= 66 at s-alerts.pl line 1219
Access is denied.
can't open device: COM5
at s-alerts.pl line 1219
Access is denied.
can't open device: COM5
at s-alerts.pl line 1219
# Tue Dec 12 18:17:48 2006 could not connect on port COM5 - skipping alert
Administrator
As I suspected, the issue is linked to the fact that ServersCheck can not use the COM5 port. The port is in use and not available to ServersCheck for sending out the SMS.
It first tries to open the COM port and then only it sends out the SMS.
Probably another application is still using the COM 5 port.
trevorw
I have restarted the box and the same.
Hyper Terminal opens and connects to the modem no problem.
I have also installed another GSM modem (my mobile) and the same result.
SO not sure what if anything is using the modem.
Administrator
Can you download and install the trial version of ServersCheck on your laptop / desktop and try the GSM (K750i) on that machine?
We have contacted some customers (whom we build this feature for) and none is reporting the issue. We can't even replicate it on several fresh installs we did: Windows XP Professional and Windows 2003 Server editions.
trevorw
HI,
I have just installed the trial on laptop complete with an Optifusion GSM modem and it works.
Although on running in Debug mode to see what error messages if any get reported I get a Warning: could not delete Spoolfile (Then a series of numbers)
After sending about 6 test messages the s-alerts.exe freezes and sends no more ?????? Also on trying to kill the s-alerts in task manager it fails to end !!
On restarting the Laptop it then sends the text that failed? I am then able to send text again for about 6 or 7 then does exactly the same.
Thanks
Trevor
Administrator
OK that moved us a step further. The spool file error can be ignored.
Allow me to explain how alerts are being sent: they are saved in a queue by the components using the alerting module. The alert module then takes each alert and handles it. That is why it was sent after restart.
Now let's tackle the freeze. When looking at the output to the console, what was the last output?
trevorw
Typical, when you want it to fail it does not.
When it did the last instruction to console was :-
# Wed Dec 13 10:33:43 2006 SMS alert was succesfully sent
# Wed Dec 13 10:34:04 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Wed Dec 13 10:34:04 2006 processing alert ID
Just sent 17 test messages no problem so not sure what is happening. Will run some more test's and let you know if it occurs again. Also will test the GSM modem from work latter in the week to see what is happenign there.
Many Thanks for you help on this.
Trevor
Administrator
No problem. Look forward on your further input.
I am very happy that at least you have seen it sending out SMS alerts.
trevorw
HI,
Well, found some time this morning to run some tests.
The OptiFusion GSM card in my laptop works. The External GSM Modem appears not to. See below :--- as you can see the error message is identical, any ideas ?
#
#
# ServersCheck Alerting & Notification Component
# version 6.9.0
#
#
# (c) Copyright 2003-2006 - ServersCheck BVBA
# www.serverscheck.com
#
# IP address: 10.x.x.x
#
#
# Fri Dec 15 12:10:25 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:10:25 2006 processing alert ID
WARNING: Could not delete spoolfile (07721399450_6521166184632285603C564BA184C37
8B816430980D04).
# Fri Dec 15 12:10:39 2006 SMS alert was succesfully sent
# Fri Dec 15 12:11:20 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:11:20 2006 processing alert ID
invalid COMMPROP block length= 66 at s-alerts.pl line 1214
Access is denied.
can't open device: COM7
at s-alerts.pl line 1214
Access is denied.
can't open device: COM7
at s-alerts.pl line 1214
# Fri Dec 15 12:11:41 2006 could not connect on port COM7 - skipping alert
# Fri Dec 15 12:12:03 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:12:03 2006 processing alert ID
WARNING: Could not delete spoolfile (07721399450_6521166184730285603C564BA984C07
CB816430980D04).
# Fri Dec 15 12:12:17 2006 SMS alert was succesfully sent
Administrator
Like said earlier, this error indicates that it is unable to open the COM7 (or previously the COM5) port. It is not possible for us to tell from here what is blocking the port.
trevorw
Just tried another piece of SMS software and it works no problem. I have contact the supplier and this is what is said:----
Communications between a PC at the low level (USB and COMx) is all we provide and this works
fine with the basic driver.
Using that basic connection it is possible to make CSD (low speed data) calls, GPRS depending on your
service & PC fax using built in PC software.
Regarding any other capabilities, it is up to third party software to be compatible. This would apply to SMS.
Siemens do not provide a driver for the MC55 as it does not require one since it is ETSI compliant. That is that it supports all the relevant ETSI command for GSM devices for data, voice, fax, SMS etc.
Administrator
"it is up to third party software to be compatible"
We have never claimed to be compatible with your specific equipment. Saying that we have to be compatible is not how we see it.
Our piece of software is not even trying to send the SMS, it fails when trying to open the COM port.
During the testing you confirmed that alternatives worked and next to that there are other options available like stated earlier in this thread.
Administrator
A developer has made a new special build for you that bypasses the COM port availability check (causing the failure on your Siemens device).
# Mon Dec 18 14:54:48 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Mon Dec 18 14:54:48 2006 processing alert ID
# Mon Dec 18 14:54:54 2006 CSCA set to +447973100973
# Mon Dec 18 14:54:54 2006 Serial port set to COM2
# Mon Dec 18 14:54:54 2006 Pin code set to 0000 - Pin code has to be desactivate
d
# Mon Dec 18 14:54:54 2006 could not connect on port COM2 - skipping alert
invalid COMMPROP block length= 66 at /PerlApp/GSM/SMS/Support/SerialPort.pm line
76
Can't call method "baudrate" on an undefined value at /PerlApp/GSM/SMS/Transport
/Serial.pm line 202.
C:Program FilesServersCheck_Monitoring>
Administrator
A developer has gone through all the lines of code for that part step by step.
It fails on opening the serial port. Can you confirm that this modem is attached via the serial port of the PC running our software?
trevorw
Hi,
Thanks for you time on trying to resolve this issue.
It is connected to a USB port, not a serial port.
Administrator
The COM port driver for the GSM modem is the issue as we use for our protocol serial port based communications.
USB enabled devices come with their own drivers to create virtual serial COM ports. Although it works with most (like for example the Sony Ericsson mobile phone) in your case it does not recognize the COM port of your GSM modem as being a serial port and basically fails when trying to open it using your driver.
Unfortunately we do not have a solution for this at the short term.
trevorw
Thanks,
I can open in hyperterminal and send AT commands to it including AT commands to send SMS. I guess you are doing somthing a little more complex.
Administrator
A developer has worked hard lately on addressing the GSM modem issue included in release 6.9.4
I need the content of the gsm.conf ? Do you have that file? If not then, then in General Settings, select SMS & Pager Alert Settings.
In that screen select GSM modem and then select your COM port and SMSC and then click on save settings. Once that is done, please click on Test Settings
trevorw
Hi
The only GSM related file is the GSMmodem.conf which I pasted above ?
Dones as requested and get the same message as before. Sound slike I have a file missing ?
Administrator
My mistake. It is the content of the file called sms.conf that I need
Comments
In order to make sure that I fully understand your configuration and setup, could you please do following?
Can you please just run the s-alerts.exe from the command prompt and then send all output (including header text) as a reply (so not sending it to a debug file).
It fails in the code where it actually tries to open the COM port, so not even sending the SMS. Nothing else is using that COM5 port?
C:>cd program filesserverscheck_monitoring
C:Program FilesServersCheck_Monitoring>s-alerts
#
#
# ServersCheck Alerting & Notification Component
# version 6.9.0
#
#
# (c) Copyright 2003-2006 - ServersCheck BVBA
# www.serverscheck.com
#
# IP address: 10.51.17.157
#
#
# Tue Dec 12 18:17:27 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Tue Dec 12 18:17:27 2006 processing alert ID
# Tue Dec 12 18:17:33 2006 CSCA set to +447973100973
# Tue Dec 12 18:17:33 2006 Serial port set to COM5
# Tue Dec 12 18:17:33 2006 Pin code set to 0000 - Pin code has to be desactivate
d
invalid COMMPROP block length= 66 at s-alerts.pl line 1219
Access is denied.
can't open device: COM5
at s-alerts.pl line 1219
Access is denied.
can't open device: COM5
at s-alerts.pl line 1219
# Tue Dec 12 18:17:48 2006 could not connect on port COM5 - skipping alert
It first tries to open the COM port and then only it sends out the SMS.
Probably another application is still using the COM 5 port.
Hyper Terminal opens and connects to the modem no problem.
I have also installed another GSM modem (my mobile) and the same result.
SO not sure what if anything is using the modem.
We have contacted some customers (whom we build this feature for) and none is reporting the issue. We can't even replicate it on several fresh installs we did: Windows XP Professional and Windows 2003 Server editions.
I have just installed the trial on laptop complete with an Optifusion GSM modem and it works.
Although on running in Debug mode to see what error messages if any get reported I get a Warning: could not delete Spoolfile (Then a series of numbers)
After sending about 6 test messages the s-alerts.exe freezes and sends no more ?????? Also on trying to kill the s-alerts in task manager it fails to end !!
On restarting the Laptop it then sends the text that failed? I am then able to send text again for about 6 or 7 then does exactly the same.
Thanks
Trevor
Allow me to explain how alerts are being sent: they are saved in a queue by the components using the alerting module. The alert module then takes each alert and handles it. That is why it was sent after restart.
Now let's tackle the freeze. When looking at the output to the console, what was the last output?
When it did the last instruction to console was :-
# Wed Dec 13 10:33:43 2006 SMS alert was succesfully sent
# Wed Dec 13 10:34:04 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Wed Dec 13 10:34:04 2006 processing alert ID
Just sent 17 test messages no problem so not sure what is happening. Will run some more test's and let you know if it occurs again. Also will test the GSM modem from work latter in the week to see what is happenign there.
Many Thanks for you help on this.
Trevor
I am very happy that at least you have seen it sending out SMS alerts.
Well, found some time this morning to run some tests.
The OptiFusion GSM card in my laptop works. The External GSM Modem appears not to. See below :--- as you can see the error message is identical, any ideas ?
#
#
# ServersCheck Alerting & Notification Component
# version 6.9.0
#
#
# (c) Copyright 2003-2006 - ServersCheck BVBA
# www.serverscheck.com
#
# IP address: 10.x.x.x
#
#
# Fri Dec 15 12:10:25 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:10:25 2006 processing alert ID
WARNING: Could not delete spoolfile (07721399450_6521166184632285603C564BA184C37
8B816430980D04).
# Fri Dec 15 12:10:39 2006 SMS alert was succesfully sent
# Fri Dec 15 12:11:20 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:11:20 2006 processing alert ID
invalid COMMPROP block length= 66 at s-alerts.pl line 1214
Access is denied.
can't open device: COM7
at s-alerts.pl line 1214
Access is denied.
can't open device: COM7
at s-alerts.pl line 1214
# Fri Dec 15 12:11:41 2006 could not connect on port COM7 - skipping alert
# Fri Dec 15 12:12:03 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Fri Dec 15 12:12:03 2006 processing alert ID
WARNING: Could not delete spoolfile (07721399450_6521166184730285603C564BA984C07
CB816430980D04).
# Fri Dec 15 12:12:17 2006 SMS alert was succesfully sent
Communications between a PC at the low level (USB and COMx) is all we provide and this works
fine with the basic driver.
Using that basic connection it is possible to make CSD (low speed data) calls, GPRS depending on your
service & PC fax using built in PC software.
Regarding any other capabilities, it is up to third party software to be compatible. This would apply to SMS.
Siemens do not provide a driver for the MC55 as it does not require one since it is ETSI compliant. That is that it supports all the relevant ETSI command for GSM devices for data, voice, fax, SMS etc.
We have never claimed to be compatible with your specific equipment. Saying that we have to be compatible is not how we see it.
Our piece of software is not even trying to send the SMS, it fails when trying to open the COM port.
During the testing you confirmed that alternatives worked and next to that there are other options available like stated earlier in this thread.
It can be downloaded from following url:
http://www.serverscheck.com/files/s-alerts.zip
C:Program FilesServersCheck_Monitoring>s-alerts
#
#
# ServersCheck Alerting & Notification Component
# version 6.9.2 - Special build for Tycoint.com
#
#
# (c) Copyright 2003-2006 - ServersCheck BVBA
# www.serverscheck.com
#
# IP address: 10.51.17.157
#
#
# Mon Dec 18 14:54:48 2006 debug info: SMS|X|07721399450|X|test message sent fro
m ServersCheck|X||X||X||X|Test|X||X||X||X||X||X||X|
# Mon Dec 18 14:54:48 2006 processing alert ID
# Mon Dec 18 14:54:54 2006 CSCA set to +447973100973
# Mon Dec 18 14:54:54 2006 Serial port set to COM2
# Mon Dec 18 14:54:54 2006 Pin code set to 0000 - Pin code has to be desactivate
d
# Mon Dec 18 14:54:54 2006 could not connect on port COM2 - skipping alert
invalid COMMPROP block length= 66 at /PerlApp/GSM/SMS/Support/SerialPort.pm line
76
Can't call method "baudrate" on an undefined value at /PerlApp/GSM/SMS/Transport
/Serial.pm line 202.
C:Program FilesServersCheck_Monitoring>
It fails on opening the serial port. Can you confirm that this modem is attached via the serial port of the PC running our software?
Thanks for you time on trying to resolve this issue.
It is connected to a USB port, not a serial port.
USB enabled devices come with their own drivers to create virtual serial COM ports. Although it works with most (like for example the Sony Ericsson mobile phone) in your case it does not recognize the COM port of your GSM modem as being a serial port and basically fails when trying to open it using your driver.
Unfortunately we do not have a solution for this at the short term.
I can open in hyperterminal and send AT commands to it including AT commands to send SMS. I guess you are doing somthing a little more complex.
Help file describing the new feature:
http://www.serverscheck.be/help6/definesms_gsmmodem.html
This has been tested with the Falcom Samba 55 USB GSM modem and should work fine with most ones.
It still has not been fully released and I was wondering if you could test it with your hardware and report back.
You will need to perform a manual upgrade as described here:
http://kb.serverscheck.com/index.php?page=index_v2&id=12&c=5
The 6.9.4 download url:
http://www.serverscheck.com/download.asp
done as requested and :--
SMS debugging information:
CSCA set to
COM port set to
Pin code set to 0000 - Pin code has to be desactivated
SMS sending failed Cannot find COM port
It seems that settings where not saved when clicking on "test settings" in the main screen.
Component tabctl32.ocx or one of it's dependancies not correctly registered: a file is missin gor invalid
1/ Download the OCX from here:
http://files.serverscheck.net/fixes/tabctl32.ocx
2/ Copy it to your C:WindowsSystem32 directory
3/ Run following command:
RegSvr32 TABCTL32.OCX
GSMMODEM.conf
spooldir = "C:Program FilesServersCheck_Monitoring/";
router = Simple
log = "C:Program FilesServersCheck_Monitoring/";
[serial01]
pin_code = 0000
memorylimit = 10
serial_port = COM2
name = serial01
csca = +447973100973
baud_rate = 9600
type = Serial
originator = GSM::SMS
match = .*
Then the rest should work too.
I need the content of the gsm.conf ? Do you have that file? If not then, then in General Settings, select SMS & Pager Alert Settings.
In that screen select GSM modem and then select your COM port and SMSC and then click on save settings. Once that is done, please click on Test Settings
The only GSM related file is the GSMmodem.conf which I pasted above ?
Dones as requested and get the same message as before. Sound slike I have a file missing ?
gsmmodem
COM2<X>+447973100973<X>0000