Search found 6 matches

So, I did bump it down to 300 bps. And it seems to have done the trick. Doesn't seem like an ideal solution, but it works.

Here's an example timeout segment where the mesage ends up being accepted by the TAP service, however, PageGate assumes it didn't. Resulting in another attempt. Again, I think it's the dual message where it throws a Timeout Error AND Message Accepted (as shown in the following segment):

12/20/2012 11:17:29 AM ========================================
12/20/2012 11:17:31 AM Start connection to carrier: TAP_Gateway
12/20/2012 11:17:31 AM Connect using TAP protocol
12/20/2012 11:17:33 AM Setting communication parameters (1200,e,7,1)
12/20/2012 11:17:34 AM Attempting to reset modem
12/20/2012 11:17:38 AM Sent:AT<CR>
12/20/2012 11:17:38 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 11:17:41 AM Modem reset
12/20/2012 11:17:41 AM Attempting to send dialer init string
12/20/2012 11:17:44 AM Sent:AT&F<CR>
12/20/2012 11:17:44 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 11:17:47 AM Dialer init string sent
12/20/2012 11:17:47 AM Attempting to send carrier init string
12/20/2012 11:17:49 AM Sent:ATS7=120S30=1200S29=0<CR>
12/20/2012 11:17:50 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 11:17:53 AM Carrier init string sent
12/20/2012 11:17:53 AM Dialing carrier
12/20/2012 11:17:55 AM Sent:ATDTXXXXXXXXXXX<CR>
12/20/2012 11:18:03 AM Waiting for connection
12/20/2012 11:18:17 AM Received:<CR><LF>CONNECT 1200<CR><LF>
12/20/2012 11:18:17 AM Connected to carrier
12/20/2012 11:18:20 AM Waiting for protocol initialization
12/20/2012 11:18:20 AM Received:ID=
12/20/2012 11:18:22 AM TAP protocol detected
12/20/2012 11:18:23 AM Sent:<ESC>PG1<CR>
12/20/2012 11:18:35 AM Received:ID=V<11>`t<15>,!"vID=
12/20/2012 11:18:35 AM Sent:<ESC>PG1<CR>
12/20/2012 11:18:39 AM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/20/201 ...

Oh, and FYI, if anyone is searching this forum and has a Cisco MICA modems, here's the reference I used:

http://www.cisco.com/en/US/docs/routers/access/modem/AT/Command/reference/atcmnds.html#wp50153

It would seem that changing the speed did help quite a bit. In fact most messages get through now. However, sometimes PageGate thinks the message fails and will repeatedly try to send it three times, when in fact the TAP service did recieve it. I think it has to do with the error message below where it gives a timeout error AND a message accepted. In the below example the message worked indicated by the "SUCCESSFUL" message. However, why would there be a timeout and an accepted message? Any ideas? Assuming this may be a question for the TAP gateway folks but wondering if you've seen it before...

12/20/2012 10:25:19 AM ========================================
12/20/2012 10:25:19 AM Start connection to carrier: TAP_Gateway
12/20/2012 10:25:21 AM Connect using TAP protocol
12/20/2012 10:25:21 AM Setting communication parameters (1200,e,7,1)
12/20/2012 10:25:24 AM Attempting to reset modem
12/20/2012 10:25:26 AM Sent:AT<CR>
12/20/2012 10:25:29 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 10:25:29 AM Modem reset
12/20/2012 10:25:32 AM Attempting to send dialer init string
12/20/2012 10:25:32 AM Sent:AT&F<CR>
12/20/2012 10:25:34 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 10:25:35 AM Dialer init string sent
12/20/2012 10:25:37 AM Attempting to send carrier init string
12/20/2012 10:25:37 AM Sent:ATS7=120S30=1200S29=0<CR>
12/20/2012 10:25:40 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 10:25:41 AM Carrier init string sent
12/20/2012 10:25:43 AM Dialing carrier
12/20/2012 10:25:43 AM Sent:ATDTXXXXXXXXXXX<CR>
12/20/2012 10:25:53 AM Waiting for connection
12/20/2012 10:26:08 AM Received:<CR><LF>CONNECT 1200<CR><LF>
12/20/2012 10:26:10 AM Connected to carrier
12/20/2012 10:26:10 AM Waiting for protocol initialization
12/20/2012 10:26:13 AM Received:ID=
12/20/2012 10:26:13 AM TAP protocol detected
12/20/2012 10: ...

I had to come up with that init string myself, each of the 'auto' strings threw an error on the modem. I could try a lower baud, I'll let you know if it makes any difference. I'm using a Cisco AS5300 with MICA modems. Here's the ati3 output:

Cisco MICA Hex Modem Module Product Information

Country Code 001
V.92(MOH,QC), V.90, K56FLEX 1.1, V.34+, V.22bis,
V.42, MNP2-4, V.44, V.42bis, MNP5, Fax, V.110, SS7_COT, TRACE

HEX modem index 02
CP code revision 2.9.5.0
CP revision date Sep 09 2003

SP code revision 2.9.5.0
SP revision date 09/09/2003 (MM/DD/YYYY)

Running PageGate version 5.0.95 (registered)

We're using "TAP Gateway" (www.tapgateway.com) as our carrier service. I'm trying to narrow down where the problem lies. There seems to be inconsistent results communicating with the TAP service. It doesn't connect some times, connects and immedately hangs up, fails on a checksum error. I don't seem to have any problem with the TAP Gateway service using qpage on Linux. I was hoping y'all could help. We're a new PageGate customer and I have limited experience with it so far.

This is what I'm seeing in the logs (phone numbers sanitized):

12/19/2012 3:56:24 PM ========================================
12/19/2012 3:56:24 PM Start connection to carrier: TAP_Gateway
12/19/2012 3:56:26 PM Connect using TAP protocol
12/19/2012 3:56:26 PM Setting communication parameters (1200,e,7,1)
12/19/2012 3:56:29 PM Attempting to reset modem
12/19/2012 3:56:31 PM Sent:AT<CR>
12/19/2012 3:56:34 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:56:34 PM Modem reset
12/19/2012 3:56:37 PM Attempting to send dialer init string
12/19/2012 3:56:37 PM Sent:AT&FS7=120<CR>
12/19/2012 3:56:40 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:56:40 PM Dialer init string sent
12/19/2012 3:56:42 PM Attempting to send carrier init string
12/19/2012 3:56:43 PM Sent:at&fS7=120<CR>
12/19/2012 3:56:45 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:56:46 PM Carrier init string sent
12/19/2012 3:56:48 PM Dialing carrier
12/19/2012 3:56:48 PM Sent:ATDTXXXXXXXXXXX<CR>
12/19/2012 3:56:58 PM Waiting for connection
12/19/2012 3:57:20 PM Received:<CR><LF>NO CARRIER<CR><LF>
12/19/2012 3:57:22 PM Attempting to hang up modem
12/19/2012 3:57:24 PM Sent:AT<CR>
12/19/2012 3:57:27 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:57:27 PM Modem hung up
12/19/2012 3:58:06 PM ========== ...

Author	Message
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Fri Jan 11, 2013 11:25 am Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	So, I did bump it down to 300 bps. And it seems to have done the trick. Doesn't seem like an ideal solution, but it works.
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Thu Dec 20, 2012 1:48 pm Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Here's an example timeout segment where the mesage ends up being accepted by the TAP service, however, PageGate assumes it didn't. Resulting in another attempt. Again, I think it's the dual message where it throws a Timeout Error AND Message Accepted (as shown in the following segment): 12/20/2012 11:17:29 AM ======================================== 12/20/2012 11:17:31 AM Start connection to carrier: TAP_Gateway 12/20/2012 11:17:31 AM Connect using TAP protocol 12/20/2012 11:17:33 AM Setting communication parameters (1200,e,7,1) 12/20/2012 11:17:34 AM Attempting to reset modem 12/20/2012 11:17:38 AM Sent:AT<CR> 12/20/2012 11:17:38 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 11:17:41 AM Modem reset 12/20/2012 11:17:41 AM Attempting to send dialer init string 12/20/2012 11:17:44 AM Sent:AT&F<CR> 12/20/2012 11:17:44 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 11:17:47 AM Dialer init string sent 12/20/2012 11:17:47 AM Attempting to send carrier init string 12/20/2012 11:17:49 AM Sent:ATS7=120S30=1200S29=0<CR> 12/20/2012 11:17:50 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 11:17:53 AM Carrier init string sent 12/20/2012 11:17:53 AM Dialing carrier 12/20/2012 11:17:55 AM Sent:ATDTXXXXXXXXXXX<CR> 12/20/2012 11:18:03 AM Waiting for connection 12/20/2012 11:18:17 AM Received:<CR><LF>CONNECT 1200<CR><LF> 12/20/2012 11:18:17 AM Connected to carrier 12/20/2012 11:18:20 AM Waiting for protocol initialization 12/20/2012 11:18:20 AM Received:ID= 12/20/2012 11:18:22 AM TAP protocol detected 12/20/2012 11:18:23 AM Sent:<ESC>PG1<CR> 12/20/2012 11:18:35 AM Received:ID=V<11>`t<15>,!"vID= 12/20/2012 11:18:35 AM Sent:<ESC>PG1<CR> 12/20/2012 11:18:39 AM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR> 12/20/201 ...
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Thu Dec 20, 2012 12:45 pm Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Oh, and FYI, if anyone is searching this forum and has a Cisco MICA modems, here's the reference I used: http://www.cisco.com/en/US/docs/routers/access/modem/AT/Command/reference/atcmnds.html#wp50153
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Thu Dec 20, 2012 12:43 pm Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	It would seem that changing the speed did help quite a bit. In fact most messages get through now. However, sometimes PageGate thinks the message fails and will repeatedly try to send it three times, when in fact the TAP service did recieve it. I think it has to do with the error message below where it gives a timeout error AND a message accepted. In the below example the message worked indicated by the "SUCCESSFUL" message. However, why would there be a timeout and an accepted message? Any ideas? Assuming this may be a question for the TAP gateway folks but wondering if you've seen it before... 12/20/2012 10:25:19 AM ======================================== 12/20/2012 10:25:19 AM Start connection to carrier: TAP_Gateway 12/20/2012 10:25:21 AM Connect using TAP protocol 12/20/2012 10:25:21 AM Setting communication parameters (1200,e,7,1) 12/20/2012 10:25:24 AM Attempting to reset modem 12/20/2012 10:25:26 AM Sent:AT<CR> 12/20/2012 10:25:29 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 10:25:29 AM Modem reset 12/20/2012 10:25:32 AM Attempting to send dialer init string 12/20/2012 10:25:32 AM Sent:AT&F<CR> 12/20/2012 10:25:34 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 10:25:35 AM Dialer init string sent 12/20/2012 10:25:37 AM Attempting to send carrier init string 12/20/2012 10:25:37 AM Sent:ATS7=120S30=1200S29=0<CR> 12/20/2012 10:25:40 AM Received:<CR><LF>OK<CR><LF> 12/20/2012 10:25:41 AM Carrier init string sent 12/20/2012 10:25:43 AM Dialing carrier 12/20/2012 10:25:43 AM Sent:ATDTXXXXXXXXXXX<CR> 12/20/2012 10:25:53 AM Waiting for connection 12/20/2012 10:26:08 AM Received:<CR><LF>CONNECT 1200<CR><LF> 12/20/2012 10:26:10 AM Connected to carrier 12/20/2012 10:26:10 AM Waiting for protocol initialization 12/20/2012 10:26:13 AM Received:ID= 12/20/2012 10:26:13 AM TAP protocol detected 12/20/2012 10: ...
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Thu Dec 20, 2012 11:08 am Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	I had to come up with that init string myself, each of the 'auto' strings threw an error on the modem. I could try a lower baud, I'll let you know if it makes any difference. I'm using a Cisco AS5300 with MICA modems. Here's the ati3 output: Cisco MICA Hex Modem Module Product Information Country Code 001 V.92(MOH,QC), V.90, K56FLEX 1.1, V.34+, V.22bis, V.42, MNP2-4, V.44, V.42bis, MNP5, Fax, V.110, SS7_COT, TRACE HEX modem index 02 CP code revision 2.9.5.0 CP revision date Sep 09 2003 SP code revision 2.9.5.0 SP revision date 09/09/2003 (MM/DD/YYYY)
Topic: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Forum: PageGate Support Posted: Wed Dec 19, 2012 7:22 pm Subject: PageGate and TAP Gateway
spillmantech Replies: 9 Views: 24447	Running PageGate version 5.0.95 (registered) We're using "TAP Gateway" (www.tapgateway.com) as our carrier service. I'm trying to narrow down where the problem lies. There seems to be inconsistent results communicating with the TAP service. It doesn't connect some times, connects and immedately hangs up, fails on a checksum error. I don't seem to have any problem with the TAP Gateway service using qpage on Linux. I was hoping y'all could help. We're a new PageGate customer and I have limited experience with it so far. This is what I'm seeing in the logs (phone numbers sanitized): 12/19/2012 3:56:24 PM ======================================== 12/19/2012 3:56:24 PM Start connection to carrier: TAP_Gateway 12/19/2012 3:56:26 PM Connect using TAP protocol 12/19/2012 3:56:26 PM Setting communication parameters (1200,e,7,1) 12/19/2012 3:56:29 PM Attempting to reset modem 12/19/2012 3:56:31 PM Sent:AT<CR> 12/19/2012 3:56:34 PM Received:<CR><LF>OK<CR><LF> 12/19/2012 3:56:34 PM Modem reset 12/19/2012 3:56:37 PM Attempting to send dialer init string 12/19/2012 3:56:37 PM Sent:AT&FS7=120<CR> 12/19/2012 3:56:40 PM Received:<CR><LF>OK<CR><LF> 12/19/2012 3:56:40 PM Dialer init string sent 12/19/2012 3:56:42 PM Attempting to send carrier init string 12/19/2012 3:56:43 PM Sent:at&fS7=120<CR> 12/19/2012 3:56:45 PM Received:<CR><LF>OK<CR><LF> 12/19/2012 3:56:46 PM Carrier init string sent 12/19/2012 3:56:48 PM Dialing carrier 12/19/2012 3:56:48 PM Sent:ATDTXXXXXXXXXXX<CR> 12/19/2012 3:56:58 PM Waiting for connection 12/19/2012 3:57:20 PM Received:<CR><LF>NO CARRIER<CR><LF> 12/19/2012 3:57:22 PM Attempting to hang up modem 12/19/2012 3:57:24 PM Sent:AT<CR> 12/19/2012 3:57:27 PM Received:<CR><LF>OK<CR><LF> 12/19/2012 3:57:27 PM Modem hung up 12/19/2012 3:58:06 PM ========== ...