Search found 4 matches

Um, yes. I also updated the driver and still got the same result.

Thanks, I tried that. Same result. The stuff that comes back is exactly the same making me think that it is not baud, parity, stop bits, or error-related. It's a brand-new US Robotics modem. Obviously, it connects and communicates to some degree. Any other ideas? Here are log fragments from the 1200 and 300 test:

====================================
5/19/2011 2:14:04 PM Start connection to carrier: VERIZON-TAP
5/19/2011 2:14:04 PM Connect using TAP protocol
5/19/2011 2:14:04 PM Setting communication parameters
5/19/2011 2:14:04 PM Sent:AT<CR><LF>
5/19/2011 2:14:05 PM Attempting to reset modem
5/19/2011 2:14:07 PM Sent:AT<CR>
5/19/2011 2:14:07 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:14:08 PM modem reset
5/19/2011 2:14:08 PM Attempting to send carrier init string
5/19/2011 2:14:08 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2<CR>
5/19/2011 2:14:09 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:14:09 PM Carrier init string sent
5/19/2011 2:14:09 PM Dialing carrier
5/19/2011 2:14:09 PM Sent:ATDT918668230501<CR>
5/19/2011 2:14:17 PM Waiting for connection
5/19/2011 2:14:20 PM Received:<CR><LF>CONNECT 1200/NONE<CR><LF>
5/19/2011 2:14:20 PM Connected to carrier
5/19/2011 2:14:20 PM Waiting for protocol initialization
5/19/2011 2:14:25 PM Received:Trei9g t<5>p.<CR>Ms.Yt<NAK>aQ9<SUB>k+<15>4<20>6eri<ESC>n.Y:si&N, 15A<STX>JMII<9>4<14>>Yn<CR><LF>
5/19/2011 2:14:25 PM Sent:<CR>
5/19/2011 2:14:28 PM Received:IDuSx
5/19/2011 2:14:28 PM Sent:<CR>
5/19/2011 2:14:33 PM Received:IDuSx
5/19/2011 2:14:33 PM Sent:<CR>
5/19/2011 2:14:39 PM Received:IDuSx
5/19/2011 2:14:39 PM Sent:<CR>
5/19/2011 2:14:45 PM Received:IDuSx
5/19/2011 2:14:45 PM Attempting to hang up modem
5/19/2011 2:14:48 PM Sent:AT<CR>
5 ...

I'm trying to use Verizon with TAP. Below is the log. Everything appears fine until timestamp 9:33:07. Any idea what might be wrong? I'm using the recommended 2400,e,7,1.

5/19/2011 9:32:46 AM Start connection to carrier: VERIZON-TAP
5/19/2011 9:32:46 AM Connect using TAP protocol
5/19/2011 9:32:46 AM Setting communication parameters
5/19/2011 9:32:46 AM Sent:AT<CR><LF>
5/19/2011 9:32:46 AM Attempting to reset modem
5/19/2011 9:32:48 AM Sent:AT<CR>
5/19/2011 9:32:49 AM Received:<CR><LF>OK<CR><LF>
5/19/2011 9:32:49 AM modem reset
5/19/2011 9:32:49 AM Attempting to send carrier init string
5/19/2011 9:32:50 AM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N3<CR>
5/19/2011 9:32:50 AM Received:<CR><LF>OK<CR><LF>
5/19/2011 9:32:51 AM Carrier init string sent
5/19/2011 9:32:51 AM Dialing carrier
5/19/2011 9:32:51 AM Sent:ATDT918668230501<CR>
5/19/2011 9:32:59 AM Waiting for connection
5/19/2011 9:33:02 AM Received:<CR><LF>CONNECT 2400/NONE<CR><LF>
5/19/2011 9:33:02 AM Connected to carrier
5/19/2011 9:33:02 AM Waiting for protocol initialization
5/19/2011 9:33:07 AM Received:Trei9g t<5>p.<CR>Ms.Yt<NAK>aQ9<SUB>k+<15>4<20>6eri<ESC>n.Y:si&N, 15A<STX>JMII<9>4<14>>Yn<CR><LF>
5/19/2011 9:33:07 AM Sent:<CR>
5/19/2011 9:33:10 AM Received:IDuSx
5/19/2011 9:33:10 AM Sent:<CR>
5/19/2011 9:33:15 AM Received:IDuSx
5/19/2011 9:33:15 AM Sent:<CR>
5/19/2011 9:33:20 AM Received:IDuSx
5/19/2011 9:33:20 AM Sent:<CR>
5/19/2011 9:33:27 AM Received:IDuSx
5/19/2011 9:33:27 AM Attempting to hang up modem
5/19/2011 9:33:29 AM Sent:AT<CR>
5/19/2011 9:33:30 AM Received:<CR><LF>OK<CR><LF>
5/19/2011 9:33:30 AM modem hung up
5/19/2011 9:33:30 AM Carrier retry limit reached. Marking pending messag ...

Yes, we have exactly that modem on exactly that platform, only it's not working yet. From tech support on another post:

Unfortunately, the US Robotics 5637 modem can't speak with the Verizon terminal. I don't know why, I don't know what the root cause is but I've never, ever ever under any operating system gotten that specific modem to communicate with the Verizon TAP system reliably or properly.

Author	Message
Topic: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	Forum: General Questions and Announcements Posted: Fri May 20, 2011 11:00 am Subject: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	Um, yes. I also updated the driver and still got the same result.
Topic: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	Forum: General Questions and Announcements Posted: Thu May 19, 2011 4:34 pm Subject: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	Thanks, I tried that. Same result. The stuff that comes back is exactly the same making me think that it is not baud, parity, stop bits, or error-related. It's a brand-new US Robotics modem. Obviously, it connects and communicates to some degree. Any other ideas? Here are log fragments from the 1200 and 300 test: ==================================== 5/19/2011 2:14:04 PM Start connection to carrier: VERIZON-TAP 5/19/2011 2:14:04 PM Connect using TAP protocol 5/19/2011 2:14:04 PM Setting communication parameters 5/19/2011 2:14:04 PM Sent:AT<CR><LF> 5/19/2011 2:14:05 PM Attempting to reset modem 5/19/2011 2:14:07 PM Sent:AT<CR> 5/19/2011 2:14:07 PM Received:<CR><LF>OK<CR><LF> 5/19/2011 2:14:08 PM modem reset 5/19/2011 2:14:08 PM Attempting to send carrier init string 5/19/2011 2:14:08 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2<CR> 5/19/2011 2:14:09 PM Received:<CR><LF>OK<CR><LF> 5/19/2011 2:14:09 PM Carrier init string sent 5/19/2011 2:14:09 PM Dialing carrier 5/19/2011 2:14:09 PM Sent:ATDT918668230501<CR> 5/19/2011 2:14:17 PM Waiting for connection 5/19/2011 2:14:20 PM Received:<CR><LF>CONNECT 1200/NONE<CR><LF> 5/19/2011 2:14:20 PM Connected to carrier 5/19/2011 2:14:20 PM Waiting for protocol initialization 5/19/2011 2:14:25 PM Received:Trei9g t<5>p.<CR>Ms.Yt<NAK>aQ9<SUB>k+<15>4<20>6eri<ESC>n.Y:si&N, 15A<STX>JMII<9>4<14>>Yn<CR><LF> 5/19/2011 2:14:25 PM Sent:<CR> 5/19/2011 2:14:28 PM Received:IDuSx 5/19/2011 2:14:28 PM Sent:<CR> 5/19/2011 2:14:33 PM Received:IDuSx 5/19/2011 2:14:33 PM Sent:<CR> 5/19/2011 2:14:39 PM Received:IDuSx 5/19/2011 2:14:39 PM Sent:<CR> 5/19/2011 2:14:45 PM Received:IDuSx 5/19/2011 2:14:45 PM Attempting to hang up modem 5/19/2011 2:14:48 PM Sent:AT<CR> 5 ...
Topic: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	Forum: General Questions and Announcements Posted: Thu May 19, 2011 1:54 pm Subject: Getting jibberish when connecting to Verizon's TAP
rob Replies: 13 Views: 33574	I'm trying to use Verizon with TAP. Below is the log. Everything appears fine until timestamp 9:33:07. Any idea what might be wrong? I'm using the recommended 2400,e,7,1. 5/19/2011 9:32:46 AM Start connection to carrier: VERIZON-TAP 5/19/2011 9:32:46 AM Connect using TAP protocol 5/19/2011 9:32:46 AM Setting communication parameters 5/19/2011 9:32:46 AM Sent:AT<CR><LF> 5/19/2011 9:32:46 AM Attempting to reset modem 5/19/2011 9:32:48 AM Sent:AT<CR> 5/19/2011 9:32:49 AM Received:<CR><LF>OK<CR><LF> 5/19/2011 9:32:49 AM modem reset 5/19/2011 9:32:49 AM Attempting to send carrier init string 5/19/2011 9:32:50 AM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N3<CR> 5/19/2011 9:32:50 AM Received:<CR><LF>OK<CR><LF> 5/19/2011 9:32:51 AM Carrier init string sent 5/19/2011 9:32:51 AM Dialing carrier 5/19/2011 9:32:51 AM Sent:ATDT918668230501<CR> 5/19/2011 9:32:59 AM Waiting for connection 5/19/2011 9:33:02 AM Received:<CR><LF>CONNECT 2400/NONE<CR><LF> 5/19/2011 9:33:02 AM Connected to carrier 5/19/2011 9:33:02 AM Waiting for protocol initialization 5/19/2011 9:33:07 AM Received:Trei9g t<5>p.<CR>Ms.Yt<NAK>aQ9<SUB>k+<15>4<20>6eri<ESC>n.Y:si&N, 15A<STX>JMII<9>4<14>>Yn<CR><LF> 5/19/2011 9:33:07 AM Sent:<CR> 5/19/2011 9:33:10 AM Received:IDuSx 5/19/2011 9:33:10 AM Sent:<CR> 5/19/2011 9:33:15 AM Received:IDuSx 5/19/2011 9:33:15 AM Sent:<CR> 5/19/2011 9:33:20 AM Received:IDuSx 5/19/2011 9:33:20 AM Sent:<CR> 5/19/2011 9:33:27 AM Received:IDuSx 5/19/2011 9:33:27 AM Attempting to hang up modem 5/19/2011 9:33:29 AM Sent:AT<CR> 5/19/2011 9:33:30 AM Received:<CR><LF>OK<CR><LF> 5/19/2011 9:33:30 AM modem hung up 5/19/2011 9:33:30 AM Carrier retry limit reached. Marking pending messag ...
Topic: USB modem and Windows 2008 R2 64bit.
rob Replies: 3 Views: 10378	Forum: PageGate Support Posted: Thu May 19, 2011 10:32 am Subject: USB modem and Windows 2008 R2 64bit.
rob Replies: 3 Views: 10378	Yes, we have exactly that modem on exactly that platform, only it's not working yet. From tech support on another post: Unfortunately, the US Robotics 5637 modem can't speak with the Verizon terminal. I don't know why, I don't know what the root cause is but I've never, ever ever under any operating system gotten that specific modem to communicate with the Verizon TAP system reliably or properly.