That's unfortunate. How do you page if your main pipe to the internet goes down? On the other hand, a POTS line almost NEVER breaks, even during power outages. That's why I use TAP. Once TAP is unavailable, say goodbye to reliable paging during network outages.
-ryan. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, July 11, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMS Alpha paging problem We're currently working on the SMPP protocol because a provider (which I'm not gonna name and no it's not Verizon) had to admin that it's TAP gateway was very unstable. So I wouldn't be surprised if other providers have similar problems with their TAP gateway. Also I was told by somebody within that "paging" world that more and more provider are shifting towards network protocols for paging opposed to modem protocols (like TAP and UCP)...you might wonder why :-) dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ryan White Sent: Fri Jul 11 8:22 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMS Alpha paging problem Hmm...unfortunately I already tried 2400. It's been set that way for about a week, and I'm still loosing 4/5 pages I test. Either something in SA is configured wrong, or Verizon isn't accepting a lot of TAP requests anymore? -ryan. -----Original Message----- From: Luis Rosales [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 11:12 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMS Alpha paging problem I use Verizon, and I too had a similar problem. only about 1 out of every few pages sent, would be delivered. I even went so far as to format and reinstall my SA machine to try and solve the problem. Seemed to have worked perfectly with the older versions of SA. I finally solved my problem by dropping the baud rate to 2400 bps when dialing out to the TAP access number. I remember reading somewhere that Verizon still uses an older version of the TAP protocol on their system. might have something to do with it. Anyway, ever since lowering the baud to 2400, I've had no more problems of not being notified. >>> "Ryan White" <[EMAIL PROTECTED]> 07/11/03 10:40AM >>> Funny, I've been experiencing this *exact* same problem. At my last company I used dialup/TAP to page using Verizon for the last 2 years, worked great. Then, I just implemented SA at my new job, and I started having these problems. I won't send my logs, because they look identical. Logon: failed. I'll get maybe about 1/5 pages SA tries to send. Any ideas? -ryan. -----Original Message----- From: Serge Couture [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 10:35 AM To: [EMAIL PROTECTED] Subject: [SA-list] SMS Alpha paging problem I've been trying to receive alpha paging and tried about everything I could without success. First, I must say that with different software (even one I program myself) I'm able to receive messages with the same parameters than those I entered in ServersAlive, latest build (v4.0.1458). Here's part of the log that concern the paging that can't succeed. It seems to be related to the logon procedure... Anything I'm missing ? Serge ------------------------------------------------------------------------ -------------------------------------------------- 11 juillet 2003 12:56:03 PAGING : Comm 1 11 juillet 2003 12:56:03 PAGING : RECIP 4185640707 11 juillet 2003 12:56:03 PAGING : REQ F 11 juillet 2003 12:56:03 PAGING : TEXT 1234567890 11 juillet 2003 12:56:03 PAGING : SMSC 563-1607 11 juillet 2003 12:56:03 PAGING : PROTO 1 11 juillet 2003 12:56:03 TAP DEBUG: Starting sending thread. ( 26400) 11 juillet 2003 12:56:03 TAP DEBUG: Sending thread starting up. ( 26400) 11 juillet 2003 12:56:03 TAP DEBUG: Logon procedure started. ( 26101) 11 juillet 2003 12:56:32 TAP DEBUG: Protocol retries logon. ( 26102) 11 juillet 2003 12:56:34 TAP DEBUG: Remote party disconnected ( 26012) 11 juillet 2003 12:56:34 TAP DEBUG: Logon: failed. ( 26104) 11 juillet 2003 12:56:34 TAP STATUS: Message sending failed. (ID: 5) ( 26315) 11 juillet 2003 12:56:34 TAP STATUS: The transmission is completed. (ID: -1) ( 26313) 11 juillet 2003 12:56:34 TAP remove #PHONE=4185640707#MESSAGE=1234567890#REDI=0#(#PHONE=4185640707#MESSAGE=1 234567890#REDI=0#) ------------------------------------------------------------------------ -------------------------------------------------- To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
