SMS problems
Having some problems getting sms to work, I've used several other sms programs on the same machine/modem running under win2k3 and they send text messages fine (for example currently has a copy of sms-it which works flawlessly).
I've tried using commandline version (output below) but it fails to connect from the look of things, with all the same TAP settings as for the working programs, baud,parity,data and stop bits.
ANy advice on this?
C:PROGRA~1SERVER~1alerts>alert_sms.exe 07921000000 "Just a test" /debug
21/02/2005 11:55:19 License file is valid
21/02/2005 11:55:19 PROFESSIONAL VERSION - Registered to : serverscheck
21/02/2005 11:55:19 Sms Number : 07921000000
21/02/2005 11:55:19 Sms Message : Just a testServersCheck
21/02/2005 11:55:19
21/02/2005 11:55:19 Using the following configuration settings:
21/02/2005 11:55:19 Protocol : TAP
21/02/2005 11:55:19 SmsCenterNumber : 07785499993
21/02/2005 11:55:19 CommSettings : 8,n,1
21/02/2005 11:55:19 BaudRate : 2400
21/02/2005 11:55:19 Port : 1
21/02/2005 11:55:19 ConnectionTimeout : 90
21/02/2005 11:55:19 DialPrefix : 9
21/02/2005 11:55:19
21/02/2005 11:55:19 Initializing modem.
21/02/2005 11:55:19 Dialing sms center (07785499993)
21/02/2005 11:55:19 Sending : ATDT907785499993<CR>
21/02/2005 11:55:19 Comm Event: Sending data
Error: [523] Connection timed out. No response from Modem. Make sure you've selected the right com port.
I've changed my mobile to the 000000 number simply to avoid publishing my mobile number :-)
This is annoying the hell out of me - what am I doing wrong?
I've tried using commandline version (output below) but it fails to connect from the look of things, with all the same TAP settings as for the working programs, baud,parity,data and stop bits.
ANy advice on this?
C:PROGRA~1SERVER~1alerts>alert_sms.exe 07921000000 "Just a test" /debug
21/02/2005 11:55:19 License file is valid
21/02/2005 11:55:19 PROFESSIONAL VERSION - Registered to : serverscheck
21/02/2005 11:55:19 Sms Number : 07921000000
21/02/2005 11:55:19 Sms Message : Just a testServersCheck
21/02/2005 11:55:19
21/02/2005 11:55:19 Using the following configuration settings:
21/02/2005 11:55:19 Protocol : TAP
21/02/2005 11:55:19 SmsCenterNumber : 07785499993
21/02/2005 11:55:19 CommSettings : 8,n,1
21/02/2005 11:55:19 BaudRate : 2400
21/02/2005 11:55:19 Port : 1
21/02/2005 11:55:19 ConnectionTimeout : 90
21/02/2005 11:55:19 DialPrefix : 9
21/02/2005 11:55:19
21/02/2005 11:55:19 Initializing modem.
21/02/2005 11:55:19 Dialing sms center (07785499993)
21/02/2005 11:55:19 Sending : ATDT907785499993<CR>
21/02/2005 11:55:19 Comm Event: Sending data
Error: [523] Connection timed out. No response from Modem. Make sure you've selected the right com port.
I've changed my mobile to the 000000 number simply to avoid publishing my mobile number :-)
This is annoying the hell out of me - what am I doing wrong?
This discussion has been closed.
Comments
Also, I can verify that the modem is dialling the number, as I have initiated a text and then heard the modem dial out.
21/02/2005 12:07:20 License file is valid
21/02/2005 12:07:20 PROFESSIONAL VERSION - Registered to : serverscheck
21/02/2005 12:07:20 Sms Number : 07921000000
21/02/2005 12:07:20 Sms Message : Just a testServersCheck
21/02/2005 12:07:20
21/02/2005 12:07:20 Using the following configuration settings:
21/02/2005 12:07:20 Protocol : TAP
21/02/2005 12:07:20 SmsCenterNumber : 07785499993
21/02/2005 12:07:20 CommSettings : 8,n,1
21/02/2005 12:07:20 BaudRate : 2400
21/02/2005 12:07:20 Port : 1
21/02/2005 12:07:20 ConnectionTimeout : 90
21/02/2005 12:07:20 DialPrefix : 9
21/02/2005 12:07:20
21/02/2005 12:07:20 Initializing modem.
21/02/2005 12:07:20 Dialing sms center (07785499993)
21/02/2005 12:07:20 Sending : ATDT907785499993<CR>
21/02/2005 12:07:20 Comm Event: Receiving data
21/02/2005 12:07:20 Received : ATDT9077
21/02/2005 12:07:20 Comm Event: Sending data
21/02/2005 12:07:20 Comm Event: Receiving data
21/02/2005 12:07:20 Received : 85499993
21/02/2005 12:07:20 Comm Event: Receiving data
21/02/2005 12:07:20 Received : <CR>
21/02/2005 12:07:34 Comm Event: Change in carrier detect line.
21/02/2005 12:07:34 Comm Event: Receiving data
21/02/2005 12:07:34 Received : <CR><LF>CONNEC
21/02/2005 12:07:34 Comm Event: Receiving data
21/02/2005 12:07:34 Received : T 9600 V
21/02/2005 12:07:34 Comm Event: Receiving data
21/02/2005 12:07:34 Received : 42bis<CR><LF>
21/02/2005 12:07:34 Provider successfully connected.
21/02/2005 12:07:34 Starting tap login.
21/02/2005 12:07:39 Sending : <CR>
21/02/2005 12:07:39 Comm Event: Sending data
21/02/2005 12:07:40 Sending : <CR>
21/02/2005 12:07:40 Comm Event: Sending data
21/02/2005 12:07:41 Sending : <CR>
21/02/2005 12:07:41 Comm Event: Sending data
21/02/2005 12:07:42 Sending : <CR>
21/02/2005 12:07:42 Comm Event: Sending data
21/02/2005 12:07:43 Sending : <CR>
21/02/2005 12:07:43 Comm Event: Sending data
21/02/2005 12:07:44 Sending : <CR>
21/02/2005 12:07:44 Comm Event: Sending data
21/02/2005 12:07:45 Sending : <CR>
21/02/2005 12:07:45 Comm Event: Sending data
21/02/2005 12:07:46 Sending : <CR>
21/02/2005 12:07:46 Comm Event: Sending data
21/02/2005 12:07:47 Sending : <CR>
21/02/2005 12:07:47 Comm Event: Sending data
21/02/2005 12:07:48 Sending : <CR>
21/02/2005 12:07:48 Comm Event: Sending data
These settings work fine with sms-it, so I suspect it is sms_alert.exe that has the problem.
The TAP protocol can be implemented in different ways depending on how the provider implemented it and some are good at deviating from protocol specs.
I will ask development to take a look at Vodafone and see what can be done.
We tested it against the number you used and messages arrived just fine.
You can download the update module right here:
http://www.serverscheck.com/files/alert_sms.zip
Regards,
Forum Administrator