| |
| Search found 4 matches |
| Author | Message |
|---|---|
| ShuMO Replies: 6 Views: 20618 |
|
| 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 |
|
| ShuMO Replies: 6 Views: 20618 |
|
| 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 === ... |
|
| ShuMO Replies: 6 Views: 20618 |
|
| 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 ... |
|
| ShuMO Replies: 6 Views: 20618 |
|
| 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 Receiv ... |
|
All times are GMT - 5 Hours |