First of all I want to say thanks to those of you that replied! Secondly I 
wanted to follow-up to the list on this as I seem to have it working pretty 
well now, and this may help someone else out down the road. 

After sending my first email I put a newer, non-Win modem on the laptop that 
runs SA and tried my SMS messaging again at a variety of speeds. I still had 
marginal results and a success rate of about 1 in 6 pages. In doing some 
further research on google I ran across someone who had posted a config that 
they claimed worked well (not with SA, but another alpha-numeric paging app of 
some sort). That configuration info showed that their modem was set to connect 
at 300 bps, which is the minimum that Verizon supports.  

I vaguely recall sub-2400 baud modem rates from the glory days of my Commodore 
64 and first IBM 8088 system, but at this point I was ready to try anything. 
Low and behold once I throttled the modem back that far I was able to crank out 
5 test SMS alerts in a row with 100% of them being received. I then tried to 
switch back to the old onboard modem, but found that even at 300 bps I was 
unable to get reliable messaging. I have switched back to the non-Win modem and 
over the last two days have had numerous tests and real world alert triggers, 
all of which have been 100% successful in getting delivered to multiple cell 
phones! Huzzah! 

So in summary, it appears to be a combination of ditching the Lucent Win-Modem, 
and setting the connection speed back to 300 bps. Now I have gone from my boss 
riding me about getting this working, to asking me to throttle back the alert 
levels (our Internet connection is very flaky) so he doesn't get as much text 
message spam. :>~ 

Cheers! 

Chad 

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Chad 
Stiller
Sent: Monday, February 26, 2007 4:15 PM
To: Servers Alive Discussion List
Subject: [SA-list] Unreliable SMS - any ideas? 

Hello all, I am a recent user of the Servers Alive program and have been 
listening in on the discussion list for a few weeks now. We are currently 
running v6.0.0.2056 of the program and have it working well with basic SMTP 
alerting. I have been working on setting up the SMS paging today to allow 
alerting directly to our Verizon cell phones in case of an Internet trunk or 
email server outage. The Servers Alive program dials out and connects 
consistently on a test, but I only receive one out of every 6 or so text 
messages. I have reviewed the information on the mailing list archive here: 
http://archive.serversalive.com/ (http://archive.serversalive.com/) and tried a 
few of the ideas (such as lowering modem speed, etc.) to no avail. I have also 
seen numerous complaints from Verizon users about this setup, but my boss 
swears he had it working great with a sim! ilar implementation at his old job, 
so I am stuck trying to find an answer! 

 


The information I have from Verizon's website to setup SMS paging is: 


Protocol: Standard TAP 
Toll-Free TAP Access Number: 1-866-823-0501 
Baud Rate Range: 300-19,200 bps 
Data Settings: 7 data bits, even parity 1 stop bit 
Message Length: 160 characters 
Wait to Connect: 60 seconds or longer 


 


Servers Alive Paging registry keys: 


[HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers Alive\Paging]
"Waittime"="60"
"Enabled"=dword:00000001
"CommSettings"=" 1"
"DelayedDelivery"=dword:00000000
"LegitimisationCode"=""
"AuthenticationCode"=""
"Operation"=" 0"
"Receiptformat"=" 100"
"Format"=" 3"
"SMSC"="18668230501"
"Sender"=""
"ActiveDevice"=" 0"
"ActiveDeviceName"="Lucent Win Modem"
"Protocol"=" 1"
"Baudrate"=" 2400"
"RequestReceipt"=dword:00000000
"MultiMessageSending"=dword:00000000
"MaxMessagePerCall"=" 10"
"DefaultPagerPhoneNumber"=""
"MaxRedials"="10"
"DoubleMessage"=dword:00000000 


 


There are no errors showing up in the SA logs, and I have tried using modem 
speeds of 2400,9600, and 19200 without any real change in the issue. I have 
also played with the wait time setting - tried it at 10 seconds, 30, and 60 - 
again with no change, and tried entering the phone number with spaces, dashes, 
and no gaps. I also played with the double message setting, but it didn't seem 
to make a difference either.  I am out of bright ideas, although I have had 
issues with Win modems in the past, so will try to scrounge up an old USR 
external to use as an additional test. Again, the SA program seems to be 
dialing out and connecting on each test attempt, but I only see about 1/6 of 
the messages come through on my phone. 


 


Sorry for the length of the post here but wanted to get all the data out for 
review. If anyone has any ideas, please let me know! Thanks in advance!! 


 


 


 

Chad D. Stiller, MCSE|MCP
Windows System Administrator
City of Flagstaff
(928)779-7685 ext. 7323

To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure 
that they are not send to the list nor to the individual members of the list 
that send a message. Doing this will get you removed from the list.

Reply via email to