| View previous topic :: View next topic |
| Author |
Message |
jandafields
Joined: 21 Oct 2008
Posts: 79
|
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
 Posted: Mon Nov 10, 2008 5:11 pm Post subject: |
 |
|
Here is the unsuccessful result from that:
| Code: |
11/10/2008 10:19:37 AM ========================================
11/10/2008 10:19:37 AM Start connection to carrier: VerizonB
11/10/2008 10:19:37 AM Connect using TAP protocol
11/10/2008 10:19:37 AM Setting communication parameters (1200,e,7,1)
11/10/2008 10:19:37 AM Attempting to reset modem
11/10/2008 10:19:40 AM Sent:AT<CR>
11/10/2008 10:19:40 AM Received:<CR><LF>OK<CR><LF>
11/10/2008 10:19:41 AM Modem reset
11/10/2008 10:19:41 AM Attempting to send carrier init string
11/10/2008 10:19:41 AM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2%E0<CR>
11/10/2008 10:19:41 AM Received:<CR><LF>OK<CR><LF>
11/10/2008 10:19:42 AM Carrier init string sent
11/10/2008 10:19:42 AM Dialing carrier
11/10/2008 10:19:42 AM Sent:ATDT18668230501<CR>
11/10/2008 10:19:50 AM Waiting for connection
11/10/2008 10:19:53 AM Received:<CR><LF>CONNECT 1200/NONE<CR><LF>
11/10/2008 10:19:53 AM Connected to carrier
11/10/2008 10:19:53 AM Waiting for protocol initialization
11/10/2008 10:19:57 AM Received:Trying tap.css.vtext.com (69.78.
11/10/2008 10:19:57 AM Sent:<CR>
11/10/2008 10:20:00 AM Received:67.39, 1500)... Open<CR><LF>
11/10/2008 10:20:00 AM Sent:<CR>
11/10/2008 10:20:04 AM Sent:<CR>
11/10/2008 10:20:05 AM Received:ID=<LF>
11/10/2008 10:20:05 AM TAP protocol detected
11/10/2008 10:20:05 AM Sent:<ESC>PG1<CR>
11/10/2008 10:20:15 AM Sent:<ESC>PG1<CR>
11/10/2008 10:20:25 AM Received:ID=<LF>
11/10/2008 10:20:25 AM Sent:<ESC>PG1<CR>
11/10/2008 10:20:35 AM Attempting to hang up modem
11/10/2008 10:20:38 AM Sent:AT<CR>
11/10/2008 10:20:39 AM Received:<CR><LF>OK<CR><LF>
11/10/2008 10:20:39 AM Modem hung up
11/10/2008 10:20:54 AM ========================================
|
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Tue Nov 11, 2008 10:58 am Post subject: |
|
|
Hmmm, still no luck. It seem that the modem on the other end isn't recognizing anything we are sending after the initial connection.
Just for kicks, try setting the carrier to use 8 data bits, and no parity. |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 12, 2008 1:21 pm Post subject: |
|
|
8-N-1
| Code: |
11/12/2008 12:58:18 PM Start connection to carrier: VerizonB
11/12/2008 12:58:18 PM Connect using TAP protocol
11/12/2008 12:58:18 PM Setting communication parameters (1200,n,8,1)
11/12/2008 12:58:19 PM Attempting to reset modem
11/12/2008 12:58:21 PM Sent:AT<CR>
11/12/2008 12:58:22 PM Received:<CR><LF>OK<CR><LF>
11/12/2008 12:58:22 PM Modem reset
11/12/2008 12:58:22 PM Attempting to send carrier init string
11/12/2008 12:58:22 PM Sent:AT&F0Q0V1X4&D2&B1&K0&M0&N2%E0<CR>
11/12/2008 12:58:23 PM Received:<CR><LF>OK<CR><LF>
11/12/2008 12:58:23 PM Carrier init string sent
11/12/2008 12:58:23 PM Dialing carrier
11/12/2008 12:58:24 PM Sent:ATDT18668230501<CR>
11/12/2008 12:58:32 PM Waiting for connection
11/12/2008 12:58:34 PM Received:<CR><LF>CONNECT 1200/NONE<CR><LF>
11/12/2008 12:58:34 PM Connected to carrier
11/12/2008 12:58:34 PM Waiting for protocol initialization
11/12/2008 12:58:38 PM Received:Trying tap.css.v
11/12/2008 12:58:38 PM Sent:<CR>
11/12/2008 12:58:41 PM Received:text.com (69.78.128.199, 1500)... Open<CR><LF>
11/12/2008 12:58:41 PM Sent:<CR>
11/12/2008 12:58:45 PM Sent:<CR>
11/12/2008 12:58:46 PM Received:ID=<LF>
11/12/2008 12:58:46 PM TAP protocol detected
11/12/2008 12:58:47 PM Sent:<ESC>PG1<CR>
11/12/2008 12:58:57 PM Sent:<ESC>PG1<CR>
11/12/2008 12:59:07 PM Received:ID=<LF>
11/12/2008 12:59:07 PM Sent:<ESC>PG1<CR>
11/12/2008 12:59:17 PM Attempting to hang up modem
11/12/2008 12:59:20 PM Sent:AT<CR>
11/12/2008 12:59:20 PM Received:<CR><LF>OK<CR><LF>
11/12/2008 12:59:20 PM Modem hung up
|
I tried using the modem in HyperTerminal. This may or may not be beneficial: 7-e-1-1200.
When I tried using the old working modem in Hyper Terminal, it wouldn't let me type anything so I couldn't see what its working responses look like.
| Code: |
&Fn |Factory0 Setting|Factory1 H/W Flow|Factory2 S/W Flow| |
AT&F0Q0V1X4&D2&B1&K0&M0&N2%E0
OK
ATDT18668230501
CONNECT 1200/NONE
rit.c.text.co(69..6.39500...e
D
D
oectiotot
.c.texgI1<q=HjBb7
x!(U~,-}El͉:8F$ڎ=LT
MT$O +BOeu[ LԭEm!Yr!B=Ԡ1~_͐
2x:Fo4C@ cWk6u40c'6]% XxG!j&zc 6 g^bQ
~EtY$˫{)X5vʺWRswnYռ[3<9NS v6^U?
NO CARRIER
|
I also tried another identical modem. Same results.
|
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 12, 2008 11:26 pm Post subject: |
|
|
Ok, new information: This modem actually works with all other carriers except "verizon us".
I tried the other Verizon numbers, and they worked fine except they rejected the phone number being paged, probably because they are city-specific verizon numbers.
What does this indicate???
|
|
| Back to top |
|
OzCom
Joined: 22 Oct 2003
Posts: 1122
Location: US
|
| Posted: Thu Nov 13, 2008 5:55 am Post subject: |
|
|
Perhaps issue is not your modem (since you can reach other cariers with no problem). While very rare, there are instances where Verizon's terminal will reject a session based on the ANI (caller ID) of the line placing the call. Can you try plugging the modem into a different phone line and letting us know how that worked?_________________ 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 |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Thu Nov 13, 2008 8:12 am Post subject: |
|
|
I tried 2 phone lines and 2 identical modems. My old modem works fine with Verizon on either phone line.
Is there any way to get the city Verizon carriers to work? What are those for with the cities in parenthesis?
|
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 19, 2008 9:38 am Post subject: |
|
|
| Any other suggestions? Any way to use the other Verizon TAP numbers?
|
|
| Back to top |
|
OzCom
Joined: 22 Oct 2003
Posts: 1122
Location: US
|
| Posted: Wed Nov 19, 2008 12:07 pm Post subject: |
|
|
Since your old modem works fine - I suggest that you swap modems._________________ 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 |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 19, 2008 12:50 pm Post subject: |
|
|
I am going to return the USR-5637 USB Modem and exchange it for something else. I would suggest that the PageGate company put into their website FAQ's that USR5637 modem will not work with Verizon US. I have tried multiple of these modems on multiple phone lines.
Please tell me what would be a decent brand and model of USB modem to work with PageGate and Verizon. It must be USB due to our setup.
Thank you.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Nov 19, 2008 3:42 pm Post subject: |
|
|
| ... I should have asked this a while ago. What version of Windows are you using? |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 19, 2008 3:46 pm Post subject: |
|
|
Windows Server 2003 Standard
The same modem works fine to send faxes with the computer.
The modem, and another identical to it, has been tried on other Windows Server 2003 computers, and other phone lines, with the same failed results.
|
|
| Back to top |
|
Tech Support
Joined: 25 Aug 2003
Posts: 4382
|
| Posted: Wed Nov 19, 2008 3:49 pm Post subject: |
|
|
I wish I'd either paid attention or asked which operating system you were using a while ago. Windows 2003 (Server, specifically) is notorious for acting unreliably with non-2003 specific modems. Which is to say, it'll use whatever modem you ask it to use but if it's not a 2003 certified modem, very, very strange and unpredictable things can happen. I've seen this happen more times than I care to remember.
Check to see if your modem is on this list:
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=0&avc=12&ava=0&avq=0&OR=1&PGS=25&ready=0
That's the official supported hardware list. If it isn't on there, I'd almost guarantee that's what's causing the problem. |
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Wed Nov 19, 2008 4:42 pm Post subject: |
|
|
It is not on that list, however on the USR website it states clearly that the modem is 2003 compatible. I checked that before I bought it.
Also, how would it not being 2003 compatible explain why it connects to everything except Verizon-US?
I still think that, for some reason, the USR5637 is not compatible with the modems at Verizon-US. When I get a chance, I will try the modem with Windows XP when I can, just so we will know for sure one way or the other if others should be warned against it.
Regardless... I still need a USB modem that will definitely work with 2003 and Verizon TAP. Any suggestions?
Thank you.
|
|
| Back to top |
|
jandafields
Joined: 21 Oct 2008
Posts: 79
|
| Posted: Fri Nov 21, 2008 9:40 am Post subject: |
|
|
I tried this modem on a standard Windows XP computer, and it had the exact same failure. It would send "Sent:<ESC>PG1<CR>" and never receive a response. I think it is safe to say this modem definitely will not work with Verizon.
Any suggestions on known working USB modems with Verizon?
Thanks.
|
|
| Back to top |
|
|
