NotePage, Inc. Forum Index

Notepager Pro to Verizon TAP

 
Post new topic   Reply to topic    NotePage, Inc. Forum Index -> NotePager Pro Support
View previous topic :: View next topic  
Author Message
ShuMO



Joined: 01 Dec 2004
Posts: 4
PostPosted: Wed Dec 01, 2004 8:36 pm    Post subject: Notepager Pro to Verizon TAP Reply with quote
I've seen a couple similar posts regarding Verizon via TAP and tried all the clues and options I could surmise. None succeeded.
I've a Conexant Modem thats very new, and did a myriad of tests today. I want to monitor a Windows 2003 server and use the SMS Message feature. To do so, I programmed the notifier tool and got no msgs during tests.
I dropped into Hyperterminal and had a number of problems. One thing I noticed is that Verizon states 300-19200 at 7e1. In truth, Verizon purchase a few years ago GTE. If you look at the phone list on this site (amazingly nice btw) you find that GTE has the same phone number but its set to 8n1. My hyperterminal when set to autodetect kept going to 8n1 and functions. I speculate that indeed 8n1 is the best setting.

Regardless, I get a <esc>PG1<cr> that repeats twice, then a disconnect.
I've tried changing settings of the bitrate, tried dialing a different 800 number for Verizon and attempted to fiddle with the ascii bit settings. all to no avail. I reached all the way to the 4th level (engineering) section at verizon and stumped them too. I took a copy of your product so as to prove to Verizon that it wasn't my equipment or settings. (And it will be purchased, what a stumbled over find of a product!) I suspect that if I can get the Notepager to work, I can resolve the issue with the M$ software as well.
Here is a snippet of my log:
12/1/2004 4:08:24 PM Start connection to carrier: Verizon
12/1/2004 4:08:24 PM Connect using TAP protocol
12/1/2004 4:08:24 PM Setting communication parameters
12/1/2004 4:08:24 PM Sent:AT<CR><LF>
12/1/2004 4:08:25 PM Attempting to reset modem
12/1/2004 4:08:27 PM Sent:AT<CR>
12/1/2004 4:08:27 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:08:28 PM modem reset
12/1/2004 4:08:28 PM Attempting to send carrier init string
12/1/2004 4:08:28 PM Sent:AT&FQ0V1X4&D2N0+MS=V22,0<CR>
12/1/2004 4:08:29 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:08:29 PM Carrier init string sent
12/1/2004 4:08:29 PM Dialing carrier
12/1/2004 4:08:29 PM Sent:ATDT18668230501<CR>
12/1/2004 4:08:37 PM Waiting for connection
12/1/2004 4:08:45 PM Received:<CR><LF>CONNECT 1200<CR><LF>
12/1/2004 4:08:45 PM Connected to carrier
12/1/2004 4:08:46 PM Waiting for protocol initialization
12/1/2004 4:08:50 PM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/1/2004 4:08:50 PM Sent:<CR>
12/1/2004 4:08:53 PM Sent:<CR>
12/1/2004 4:08:55 PM Received:ID=<LF>
12/1/2004 4:08:55 PM TAP protocol detected
12/1/2004 4:08:56 PM Sent:<ESC>PG1<CR>
12/1/2004 4:09:06 PM Sent:<ESC>PG1<CR>
12/1/2004 4:09:16 PM Received:ID=<LF>
12/1/2004 4:09:16 PM Sent:<ESC>PG1<CR>
12/1/2004 4:09:26 PM Attempting to hang up modem
12/1/2004 4:09:28 PM Sent:AT<CR>
12/1/2004 4:09:29 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:09:29 PM modem hung up
12/1/2004 4:09:29 PM Carrier retry limit reached. Marking pending messages as bad
12/1/2004 4:09:29 PM FAILED To:jim Frm:jshimota Msg:HI
12/1/2004 4:09:29 PM FAILED To:jim Frm:jshimota Msg:HI
12/1/2004 4:09:41 PM ====================================
12/1/2004 4:09:41 PM Start connection to carrier: Verizon
12/1/2004 4:09:41 PM Connect using TAP protocol
12/1/2004 4:09:41 PM Setting communication parameters
12/1/2004 4:09:41 PM Sent:AT<CR><LF>
12/1/2004 4:09:42 PM Attempting to reset modem
12/1/2004 4:09:44 PM Sent:AT<CR>
12/1/2004 4:09:44 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:09:45 PM modem reset
12/1/2004 4:09:45 PM Attempting to send carrier init string
12/1/2004 4:09:45 PM Sent:AT&FQ0V1X4&D2N0+MS=V22,0<CR>
12/1/2004 4:09:45 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:09:46 PM Carrier init string sent
12/1/2004 4:09:46 PM Dialing carrier
12/1/2004 4:09:46 PM Sent:ATDT18668230501<CR>
12/1/2004 4:09:54 PM Waiting for connection
12/1/2004 4:10:03 PM Received:<CR><LF>CONNECT 1200<CR><LF>
12/1/2004 4:10:03 PM Connected to carrier
12/1/2004 4:10:03 PM Waiting for protocol initialization
12/1/2004 4:10:07 PM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/1/2004 4:10:07 PM Sent:<CR>
12/1/2004 4:10:10 PM Sent:<CR>
12/1/2004 4:10:12 PM Received:ID=<LF>
12/1/2004 4:10:12 PM TAP protocol detected
12/1/2004 4:10:13 PM Sent:<ESC>PG1<CR>
12/1/2004 4:10:23 PM Sent:<ESC>PG1<CR>
12/1/2004 4:10:33 PM Received:ID=<LF>
12/1/2004 4:10:33 PM Sent:<ESC>PG1<CR>
12/1/2004 4:10:43 PM Attempting to hang up modem
12/1/2004 4:10:45 PM Sent:AT<CR>
12/1/2004 4:10:46 PM Received:<CR><LF>OK<CR><LF>
12/1/2004 4:10:46 PM modem hung up

As you can see, its darn close to working, just no reply to the ESc sequence. Any new ideas that I didn't stumble over while searching this Forum for 'Verizon'?



_________________
Shu
Back to top
View user's profile
Tech Support



Joined: 25 Aug 2003
Posts: 4391
PostPosted: Thu Dec 02, 2004 8:53 am    Post subject: Reply with quote
We (and most customers) connect to Verizon using 1200,7,E,1.

You may want to try the following Init Strings while using 1200,7,E,1.

AT&FQ0V1X4&D2N0+MS=V22
AT&FQ0V1X4&D2+MS=V22
AT&FQ0V1X4&D2+MS=V22,0

Generally when the software detects your current string (AT&FQ0V1X4&D2N0+MS=V22,0) but cannot fully connect to the terminal, removing the ",0" and/or the "N0" from the string helps the modem get over that last hurdle.
Back to top
View user's profile
ShuMO



Joined: 01 Dec 2004
Posts: 4
PostPosted: Fri Dec 03, 2004 2:09 am    Post subject: Reply with quote
no joy my friend.

12/2/2004 11:00:12 PM Dialer Started
12/2/2004 11:01:51 PM ====================================
12/2/2004 11:01:51 PM Start connection to carrier: Verizon
12/2/2004 11:01:51 PM Connect using TAP protocol
12/2/2004 11:01:51 PM Setting communication parameters
12/2/2004 11:01:52 PM Sent:AT<CR><LF>
12/2/2004 11:01:52 PM Attempting to reset modem
12/2/2004 11:01:54 PM Sent:AT<CR>
12/2/2004 11:01:55 PM Received:K<CR><LF>
12/2/2004 11:01:55 PM modem reset
12/2/2004 11:01:55 PM Attempting to send carrier init string
12/2/2004 11:01:57 PM Sent:AT&FQ0V1X4&D2N0+MS=V22B,0&n3<CR>
12/2/2004 11:02:07 PM Received:<CR><LF>ERROR<CR><LF>
12/2/2004 11:02:07 PM Unable to send carrier init string
12/2/2004 11:02:07 PM Dialing carrier
12/2/2004 11:02:07 PM Sent:ATDT1866-823-0501<CR>
12/2/2004 11:02:16 PM Waiting for connection
12/2/2004 11:02:26 PM Received:<CR><LF>CONNECT 2400<CR><LF>
12/2/2004 11:02:26 PM Connected to carrier
12/2/2004 11:02:26 PM Waiting for protocol initialization
12/2/2004 11:02:30 PM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/2/2004 11:02:30 PM Sent:<CR>
12/2/2004 11:02:33 PM Sent:<CR>
12/2/2004 11:02:35 PM Received:ID=<LF>
12/2/2004 11:02:35 PM TAP protocol detected
12/2/2004 11:02:36 PM Sent:<ESC>PG1<CR>
12/2/2004 11:02:46 PM Sent:<ESC>PG1<CR>
12/2/2004 11:02:56 PM Received:ID=<LF>
12/2/2004 11:02:56 PM Sent:<ESC>PG1<CR>
12/2/2004 11:03:06 PM Attempting to hang up modem
12/2/2004 11:03:08 PM Sent:AT<CR>
12/2/2004 11:03:09 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:03:09 PM modem hung up
12/2/2004 11:03:15 PM ====================================
12/2/2004 11:03:15 PM Start connection to carrier: Verizon
12/2/2004 11:03:15 PM Connect using TAP protocol
12/2/2004 11:03:15 PM Setting communication parameters
12/2/2004 11:03:15 PM Sent:AT<CR><LF>
12/2/2004 11:03:16 PM Attempting to reset modem
12/2/2004 11:03:18 PM Sent:AT<CR>
12/2/2004 11:03:18 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:03:19 PM modem reset
12/2/2004 11:03:19 PM Attempting to send carrier init string
12/2/2004 11:03:19 PM Sent:AT&FQ0V1X4&D2N0+MS=V22<CR>
12/2/2004 11:03:20 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:03:20 PM Carrier init string sent
12/2/2004 11:03:20 PM Dialing carrier
12/2/2004 11:03:20 PM Sent:ATDT1866-823-0501<CR>
12/2/2004 11:03:28 PM Waiting for connection
12/2/2004 11:03:36 PM Received:<CR><LF>CONNECT 1200<CR><LF>
12/2/2004 11:03:36 PM Connected to carrier
12/2/2004 11:03:36 PM Waiting for protocol initialization
12/2/2004 11:03:40 PM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/2/2004 11:03:40 PM Sent:<CR>
12/2/2004 11:03:43 PM Sent:<CR>
12/2/2004 11:03:46 PM Received:ID=<LF>
12/2/2004 11:03:46 PM TAP protocol detected
12/2/2004 11:03:46 PM Sent:<ESC>PG1<CR>
12/2/2004 11:03:57 PM Sent:<ESC>PG1<CR>
12/2/2004 11:04:07 PM Received:ID=<LF>
12/2/2004 11:04:07 PM Sent:<ESC>PG1<CR>
12/2/2004 11:04:17 PM Attempting to hang up modem
12/2/2004 11:04:19 PM Sent:AT<CR>
12/2/2004 11:04:20 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:04:20 PM modem hung up
12/2/2004 11:05:05 PM ====================================
12/2/2004 11:05:05 PM Start connection to carrier: Verizon
12/2/2004 11:05:05 PM Connect using TAP protocol
12/2/2004 11:05:05 PM Setting communication parameters
12/2/2004 11:05:05 PM Sent:AT<CR><LF>
12/2/2004 11:05:05 PM Attempting to reset modem
12/2/2004 11:05:07 PM Sent:AT<CR>
12/2/2004 11:05:08 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:05:08 PM modem reset
12/2/2004 11:05:08 PM Attempting to send carrier init string
12/2/2004 11:05:09 PM Sent:AT&FQ0V1X4&D2+MS=V22<CR>
12/2/2004 11:05:09 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:05:10 PM Carrier init string sent
12/2/2004 11:05:10 PM Dialing carrier
12/2/2004 11:05:10 PM Sent:ATDT1866-823-0501<CR>
12/2/2004 11:05:18 PM Waiting for connection
12/2/2004 11:05:26 PM Received:<CR><LF>CONNECT 1200<CR><LF>
12/2/2004 11:05:26 PM Connected to carrier
12/2/2004 11:05:26 PM Waiting for protocol initialization
12/2/2004 11:05:30 PM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/2/2004 11:05:30 PM Sent:<CR>
12/2/2004 11:05:33 PM Sent:<CR>
12/2/2004 11:05:36 PM Received:ID=<LF>
12/2/2004 11:05:36 PM TAP protocol detected
12/2/2004 11:05:36 PM Sent:<ESC>PG1<CR>
12/2/2004 11:05:46 PM Sent:<ESC>PG1<CR>
12/2/2004 11:05:56 PM Received:ID=<LF>
12/2/2004 11:05:56 PM Sent:<ESC>PG1<CR>
12/2/2004 11:06:06 PM Attempting to hang up modem
12/2/2004 11:06:09 PM Sent:AT<CR>
12/2/2004 11:06:09 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:06:09 PM modem hung up
12/2/2004 11:06:42 PM ====================================
12/2/2004 11:06:42 PM Start connection to carrier: Verizon
12/2/2004 11:06:42 PM Connect using TAP protocol
12/2/2004 11:06:42 PM Setting communication parameters
12/2/2004 11:06:43 PM Sent:AT<CR><LF>
12/2/2004 11:06:43 PM Attempting to reset modem
12/2/2004 11:06:45 PM Sent:AT<CR>
12/2/2004 11:06:46 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:06:46 PM modem reset
12/2/2004 11:06:46 PM Attempting to send carrier init string
12/2/2004 11:06:46 PM Sent:AT&FQ0V1X4&D2+MS=V22,0<CR>
12/2/2004 11:06:47 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:06:47 PM Carrier init string sent
12/2/2004 11:06:47 PM Dialing carrier
12/2/2004 11:06:48 PM Sent:ATDT1866-823-0501<CR>
12/2/2004 11:06:56 PM Waiting for connection
12/2/2004 11:07:04 PM Received:<CR><LF>CONNECT 1200<CR><LF>
12/2/2004 11:07:04 PM Connected to carrier
12/2/2004 11:07:04 PM Waiting for protocol initialization
12/2/2004 11:07:08 PM Received:<CR><LF>Translating "tap.css.vtext.com"...domain server (66.174.76.4) [OK]<CR><LF>Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/2/2004 11:07:08 PM Sent:<CR>
12/2/2004 11:07:11 PM Sent:<CR>
12/2/2004 11:07:13 PM Received:ID=<LF>
12/2/2004 11:07:13 PM TAP protocol detected
12/2/2004 11:07:14 PM Sent:<ESC>PG1<CR>
12/2/2004 11:07:24 PM Sent:<ESC>PG1<CR>
12/2/2004 11:07:34 PM Received:ID=<LF>
12/2/2004 11:07:34 PM Sent:<ESC>PG1<CR>
12/2/2004 11:07:44 PM Attempting to hang up modem
12/2/2004 11:07:46 PM Sent:AT<CR>
12/2/2004 11:07:47 PM Received:<CR><LF>OK<CR><LF>
12/2/2004 11:07:47 PM modem hung up

Tried all 3 settings to no avail.

Shu



_________________
Shu
Back to top
View user's profile
Tech Support



Joined: 25 Aug 2003
Posts: 4391
PostPosted: Fri Dec 03, 2004 9:48 am    Post subject: Last suggestions Reply with quote
Try 1200 Baud, but use this init string

AT&FQ0V1X4&D2+MS=B103

If that does not work, try a different modem.

Some "winmodems" just cannot handle low Baud Rates. They (and their drivers) are designed with 33.6K - 56K in mind.
Back to top
View user's profile
ShuMO



Joined: 01 Dec 2004
Posts: 4
PostPosted: Fri Dec 03, 2004 1:18 pm    Post subject: Reply with quote
I did read one of your customers getting resolved with a modem fix, so I give credence to your thought about it.

No luck on that 4th string.
12/3/2004 10:13:47 AM Dialer Started
12/3/2004 10:14:08 AM ====================================
12/3/2004 10:14:08 AM Start connection to carrier: Verizon
12/3/2004 10:14:08 AM Connect using TAP protocol
12/3/2004 10:14:08 AM Setting communication parameters
12/3/2004 10:14:08 AM Sent:AT<CR><LF>
12/3/2004 10:14:09 AM Attempting to reset modem
12/3/2004 10:14:11 AM Sent:AT<CR>
12/3/2004 10:14:11 AM Received:K<CR><LF>
12/3/2004 10:14:12 AM modem reset
12/3/2004 10:14:12 AM Attempting to send carrier init string
12/3/2004 10:14:14 AM Sent:AT&FQ0V1X4&D2+MS=B103<CR>
12/3/2004 10:14:14 AM Received:<CR><LF>OK<CR><LF>
12/3/2004 10:14:15 AM Carrier init string sent
12/3/2004 10:14:15 AM Dialing carrier
12/3/2004 10:14:15 AM Sent:ATDT1866-823-0501<CR>
12/3/2004 10:14:23 AM Waiting for connection
12/3/2004 10:14:25 AM Received:<CR><LF>CONNECT<CR><LF>
12/3/2004 10:14:25 AM Connected to carrier
12/3/2004 10:14:25 AM Waiting for protocol initialization
12/3/2004 10:14:29 AM Sent:<CR>
12/3/2004 10:14:32 AM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/3/2004 10:14:32 AM Sent:<CR>
12/3/2004 10:14:36 AM Sent:<CR>
12/3/2004 10:14:38 AM Received:ID=<LF>
12/3/2004 10:14:38 AM TAP protocol detected
12/3/2004 10:14:39 AM Sent:<ESC>PG1<CR>
12/3/2004 10:14:49 AM Sent:<ESC>PG1<CR>
12/3/2004 10:14:59 AM Received:ID=<LF>
12/3/2004 10:14:59 AM Sent:<ESC>PG1<CR>
12/3/2004 10:15:09 AM Attempting to hang up modem
12/3/2004 10:15:12 AM Sent:AT<CR>
12/3/2004 10:15:12 AM Received:<CR><LF>OK<CR><LF>
12/3/2004 10:15:12 AM modem hung up
12/3/2004 10:15:30 AM ====================================
12/3/2004 10:15:30 AM Start connection to carrier: Verizon
12/3/2004 10:15:30 AM Connect using TAP protocol
12/3/2004 10:15:30 AM Setting communication parameters
12/3/2004 10:15:30 AM Sent:AT<CR><LF>
12/3/2004 10:15:31 AM Attempting to reset modem
12/3/2004 10:15:33 AM Sent:AT<CR>
12/3/2004 10:15:34 AM Received:<CR><LF>OK<CR><LF>
12/3/2004 10:15:34 AM modem reset
12/3/2004 10:15:34 AM Attempting to send carrier init string
12/3/2004 10:15:34 AM Sent:AT&FQ0V1X4&D2+MS=B103<CR>
12/3/2004 10:15:35 AM Received:<CR><LF>OK<CR><LF>
12/3/2004 10:15:35 AM Carrier init string sent
12/3/2004 10:15:35 AM Dialing carrier
12/3/2004 10:15:36 AM Sent:ATDT1866-823-0501<CR>
12/3/2004 10:15:44 AM Waiting for connection
12/3/2004 10:15:46 AM Received:<CR><LF>CONNECT<CR><LF>
12/3/2004 10:15:46 AM Connected to carrier
12/3/2004 10:15:46 AM Waiting for protocol initialization
12/3/2004 10:15:50 AM Sent:<CR>
12/3/2004 10:15:53 AM Received:Trying tap.css.vtext.com (66.174.76.10, 1500)... Open<CR><LF>
12/3/2004 10:15:53 AM Sent:<CR>
12/3/2004 10:15:57 AM Sent:<CR>
12/3/2004 10:15:59 AM Received:ID=<LF>
12/3/2004 10:15:59 AM TAP protocol detected
12/3/2004 10:16:00 AM Sent:<ESC>PG1<CR>
12/3/2004 10:16:10 AM Sent:<ESC>PG1<CR>
12/3/2004 10:16:20 AM Received:ID=<LF>
12/3/2004 10:16:20 AM Sent:<ESC>PG1<CR>
12/3/2004 10:16:30 AM Attempting to hang up modem
12/3/2004 10:16:32 AM Sent:AT<CR>
12/3/2004 10:16:33 AM Received:<CR><LF>OK<CR><LF>
12/3/2004 10:16:33 AM modem hung up

When I get the time, I'll try the another modem. I think I've an old USR around here somewhere.
Jim



_________________
Shu
Back to top
View user's profile
ShuMO



Joined: 01 Dec 2004
Posts: 4
PostPosted: Mon Dec 13, 2004 12:53 pm    Post subject: Problem worked around Reply with quote
I've finally had a chance to take the server down and install a true US Robotics Internal modem. Not an easy thing to do on a 24/7 server.

The results are not dramatic. Simply. Everything worked fine. The wizard choices were all done at defaults (speed - default, 7e1). No customization of the string was needed. Surprisingly, I didn't even need to tell Notepage anything at all about the modem. The auto detect worked flawlessly.

The modem that caused all this trouble was a 'Conexant HSF V92 56K Data Fax Modem'. For anyone reading this thread, this device worked perfectly doing fax x-mission, hyperterm and other basic functions but failed for use as a TAP msg handler for event notification under windows 2003 server.

I can't say enough about the efforts of Notepage's support. After trying hard to help solve this problem, it was their suggestion that the modem could be at fault, and they were correct. Many thanks for the hard work.

ShuMO



_________________
Shu
Back to top
View user's profile
Tech Support



Joined: 25 Aug 2003
Posts: 4391
PostPosted: Mon Dec 13, 2004 12:57 pm    Post subject: Reply with quote
Thanks for the kind words.

We are glad that the change to a different modem worked!
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    NotePage, Inc. Forum Index -> NotePager Pro Support All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2002 phpBB Group
Theme created by Vjacheslav Trushkin