| View previous topic :: View next topic |
| Author |
Message |
rob
Joined: 19 May 2011
Posts: 4
|
 Posted: Thu May 19, 2011 1:54 pm Post subject: Getting jibberish when connecting to Verizon's TAP |
 |
|
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 messages as bad
5/19/2011 9:33:30 AM FAILED To:Kevin via modem Frm:Orion NPM Msg:test
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4351
|
| Posted: Thu May 19, 2011 2:04 pm Post subject: |
|
|
| Try using 300 or 1200 baud instead. Also, remember to reset the init string to (auto) each time you change the baud rate. |
|
| Back to top |
|
rob
Joined: 19 May 2011
Posts: 4
|
| Posted: Thu May 19, 2011 4:34 pm Post subject: |
|
|
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/19/2011 2:14:48 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:14:48 PM modem hung up
5/19/2011 2:14:48 PM Carrier retry limit reached. Marking pending messages as bad
5/19/2011 2:14:48 PM FAILED To:Kevin via modem Frm:Orion NPM Msg:test
5/19/2011 2:15:27 PM ====================================
5/19/2011 2:15:27 PM Start connection to carrier: VERIZON-TAP
5/19/2011 2:15:27 PM Connect using TAP protocol
5/19/2011 2:15:27 PM Setting communication parameters
5/19/2011 2:15:27 PM Sent:AT<CR><LF>
5/19/2011 2:15:28 PM Attempting to reset modem
5/19/2011 2:15:30 PM Sent:AT<CR>
5/19/2011 2:15:31 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:15:31 PM modem reset
5/19/2011 2:15:31 PM Auto detecting modem init string
5/19/2011 2:15:31 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N1<CR>
5/19/2011 2:15:32 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:15:32 PM Attempting to send carrier init string
5/19/2011 2:15:32 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N1<CR>
5/19/2011 2:15:33 PM Received:<CR><LF>OK<CR><LF>
5/19/2011 2:15:33 PM Carrier init string sent
5/19/2011 2:15:33 PM Dialing carrier
5/19/2011 2:15:33 PM Sent:ATDT918668230501<CR>
5/19/2011 2:15:41 PM Waiting for connection
5/19/2011 2:15:43 PM Received:<CR><LF>CONNECT 300/NONE<CR><LF>
5/19/2011 2:15:43 PM Connected to carrier
5/19/2011 2:15:43 PM Waiting for protocol initialization
5/19/2011 2:15:48 PM Sent:<CR>
5/19/2011 2:15:51 PM Received:Trei9g t<5>p.<CR>Ms.Yt<NAK>aQ9<SUB>k+<15>4<20>6eri<ESC>n.E<19>Cs)6N91<ETX>-6M0
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4351
|
| Posted: Fri May 20, 2011 9:59 am Post subject: |
|
|
| Is the modem you're using a US Robotics 5637? |
|
| Back to top |
|
rob
Joined: 19 May 2011
Posts: 4
|
| Posted: Fri May 20, 2011 11:00 am Post subject: |
|
|
| Um, yes. I also updated the driver and still got the same result.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4351
|
| Posted: Fri May 20, 2011 11:05 am Post subject: |
|
|
| 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. |
|
| Back to top |
|
OzCom
Joined: 22 Oct 2003
Posts: 1121
Location: US
|
| Posted: Fri May 20, 2011 3:59 pm Post subject: |
|
|
The likely culprit is the fact that Verizon uses a voip link in front of it's TAP modem pool. THat particular USR device (along with several others) has a notoriously hard time negotiating the codec used.
Similar to the reason why VOIP based FAXING is horrendous_________________ Aaron D. Osgood
Streamline Communications, LLC
* Authorized Notepage, Inc. Development Partner and Re-seller
TEL: 207-518-8455
AOsgood@streamline-solutions.net
Creators of AutoPage Spillman CAD interface for PageGate |
|
| Back to top |
|
kent
Joined: 07 Sep 2005
Posts: 44
|
| Posted: Mon Mar 26, 2012 9:30 am Post subject: |
|
|
| Is using a USR 5637 modem with Verizon still an issue? I have been using one for a couple of years on my standby PageGate server and it seems to work just fine.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4351
|
| Posted: Mon Mar 26, 2012 9:33 am Post subject: |
|
|
| If it works for your particular server, there's no reason to switch it out. We've just had a tremendous amount of difficulty getting them to work with nearly every other client system that they've been used on. |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed May 02, 2012 2:59 pm Post subject: |
|
|
The USR 5637 USB is the BEST modem... I use them for everything. You just have to use the right init-string. I'm using 4 of them with Verizon TAP right now.
They work 100% with any computer system I use them in for Verizon TAP. I used it successfully on XP and XP64 and Server 2003 and Vista and 7.
But, it's all in the init string. It will NOT work without this exact string:
If you search the forum, it has been posted here before:
&FS13=7S19=2
The best thing about the 5637 is that, unlike most usb modems, you can use MULTIPLE on the same computer at the same time without conflict!!!
EDIT: AT&FS13=7S19=2 (The AT is required)
Last edited by jandafields on Wed May 02, 2012 3:08 pm; edited 1 time in total |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed May 02, 2012 3:07 pm Post subject: |
|
|
Actually, the exact init string to make this modem work perfectly is:
AT&FS13=7S19=2
(I forgot to add the AT to the previous post, but that is usually assumed)
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4351
|
| Posted: Wed May 02, 2012 3:09 pm Post subject: |
|
|
Just to verify, this:
| jandafields wrote: |
| &FS13=7S19=2 |
should be the part after the AT, right? So, AT&FS13=7S19=2 would be the full init string? |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed May 02, 2012 3:13 pm Post subject: |
|
|
| Tech Support wrote: |
Just to verify, this:
| jandafields wrote: |
| &FS13=7S19=2 |
should be the part after the AT, right? So, AT&FS13=7S19=2 would be the full init string? |
Yes, use that and you will be sending TAP to verizon flawlessly.
I send out literally thousands of messages per day to Verizon TAP with these modems for public safety.
By the way, that was posted in the forum back in 2010. I started that post and someone else posted this solution at the end of it and I have been using these modems exclusivey ever since.
http://www.notepage.net/forum/viewtopic.php?t=7568357&postdays=0&postorder=asc&start=30
|
|
| Back to top |
|
dmmillr1
Joined: 10 May 2012
Posts: 1
Location: Illinois
|
| Posted: Thu May 10, 2012 11:28 am Post subject: |
|
|
| thanks for the post man, huge help
|
|
| Back to top |
|
|
