View previous topic :: View next topic |
Author |
Message |
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
Posted: Wed Dec 19, 2012 7:22 pm Post subject: PageGate and TAP Gateway |
|
|
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 ========================================
12/19/2012 3:58:06 PM Start connection to carrier: TAP_Gateway
12/19/2012 3:58:08 PM Connect using TAP protocol
12/19/2012 3:58:08 PM Setting communication parameters (1200,e,7,1)
12/19/2012 3:58:11 PM Attempting to reset modem
12/19/2012 3:58:13 PM Sent:AT<CR>
12/19/2012 3:58:16 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:58:16 PM Modem reset
12/19/2012 3:58:19 PM Attempting to send dialer init string
12/19/2012 3:58:19 PM Sent:AT&FS7=120<CR>
12/19/2012 3:58:22 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:58:22 PM Dialer init string sent
12/19/2012 3:58:24 PM Attempting to send carrier init string
12/19/2012 3:58:24 PM Sent:at&fS7=120<CR>
12/19/2012 3:58:27 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:58:28 PM Carrier init string sent
12/19/2012 3:58:30 PM Dialing carrier
12/19/2012 3:58:30 PM Sent:ATDTXXXXXXXXXXX<CR>
12/19/2012 3:58:40 PM Waiting for connection
12/19/2012 3:58:55 PM Received:<CR><LF>CONNECT 14400 /V.42/V.42bis<CR><LF>
12/19/2012 3:58:57 PM Connected to carrier
12/19/2012 3:58:57 PM Waiting for protocol initialization
12/19/2012 3:59:03 PM Sent:<CR>
12/19/2012 3:59:06 PM Sent:<CR>
12/19/2012 3:59:12 PM Sent:<CR>
12/19/2012 3:59:17 PM Sent:<CR>
12/19/2012 3:59:26 PM Attempting to hang up modem
12/19/2012 3:59:28 PM Sent:AT<CR>
12/19/2012 3:59:35 PM Received:<CR><LF>NO CARRIER<CR><LF>
12/19/2012 3:59:35 PM Attempting to hang up modem
12/19/2012 3:59:40 PM Sent:AT<CR>
12/19/2012 3:59:40 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 3:59:42 PM Modem hung up
12/19/2012 4:00:19 PM ========================================
12/19/2012 4:00:22 PM Start connection to carrier: TAP_Gateway
12/19/2012 4:00:22 PM Connect using TAP protocol
12/19/2012 4:00:24 PM Setting communication parameters (1200,e,7,1)
12/19/2012 4:00:24 PM Attempting to reset modem
12/19/2012 4:00:29 PM Sent:AT<CR>
12/19/2012 4:00:29 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:00:32 PM Modem reset
12/19/2012 4:00:32 PM Attempting to send dialer init string
12/19/2012 4:00:34 PM Sent:AT&FS7=120<CR>
12/19/2012 4:00:35 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:00:38 PM Dialer init string sent
12/19/2012 4:00:38 PM Attempting to send carrier init string
12/19/2012 4:00:40 PM Sent:at&fS7=120<CR>
12/19/2012 4:00:40 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:00:43 PM Carrier init string sent
12/19/2012 4:00:43 PM Dialing carrier
12/19/2012 4:00:46 PM Sent:ATDTXXXXXXXXXXX<CR>
12/19/2012 4:00:54 PM Waiting for connection
12/19/2012 4:01:10 PM Received:<CR><LF>CONNECT 14400 /V.42/V.42bis<CR><LF>
12/19/2012 4:01:10 PM Connected to carrier
12/19/2012 4:01:12 PM Waiting for protocol initialization
12/19/2012 4:01:16 PM Sent:<CR>
12/19/2012 4:01:21 PM Sent:<CR>
12/19/2012 4:01:25 PM Sent:<CR>
12/19/2012 4:01:28 PM Received:ID=
12/19/2012 4:01:28 PM TAP protocol detected
12/19/2012 4:01:31 PM Sent:<ESC>PG1<CR>
12/19/2012 4:01:31 PM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/19/2012 4:01:34 PM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/19/2012 4:01:34 PM Automatic TAP mode accepted
12/19/2012 4:01:37 PM ----------------------------------------
12/19/2012 4:01:37 PM Working on message to: michael_wilkinson from: Bad Robot
12/19/2012 4:01:39 PM Formatting message
12/19/2012 4:01:39 PM Message contained in single packet
12/19/2012 4:01:41 PM Message contained in single block
12/19/2012 4:01:41 PM Sending block
12/19/2012 4:01:43 PM Sent:<STX>XXXXXXXXXX<CR>Bad Robot:This is a test, actually, yeah, a test.<CR><ETX>2>4<CR>
12/19/2012 4:01:48 PM Received:501 Timeout error<CR><NAK><CR>501 Timeout error<CR><NAK><CR>501 Timeout error<CR><NAK><CR>506 Excessive attempts<CR><NAK><CR>115 Thank you for calling<CR><ESC><EOT><CR>
12/19/2012 4:01:51 PM Checksum error. Retrying block
12/19/2012 4:01:51 PM Sent:<EOT><CR>
12/19/2012 4:01:53 PM Attempting to hang up modem
12/19/2012 4:01:56 PM Sent:AT<CR>
12/19/2012 4:01:58 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:01:58 PM Modem hung up
12/19/2012 4:02:45 PM ========================================
12/19/2012 4:02:45 PM Start connection to carrier: TAP_Gateway
12/19/2012 4:02:47 PM Connect using TAP protocol
12/19/2012 4:02:47 PM Setting communication parameters (1200,e,7,1)
12/19/2012 4:02:50 PM Attempting to reset modem
12/19/2012 4:02:52 PM Sent:AT<CR>
12/19/2012 4:02:55 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:02:55 PM Modem reset
12/19/2012 4:02:58 PM Attempting to send dialer init string
12/19/2012 4:02:58 PM Sent:AT&FS7=120<CR>
12/19/2012 4:03:00 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:03:01 PM Dialer init string sent
12/19/2012 4:03:03 PM Attempting to send carrier init string
12/19/2012 4:03:03 PM Sent:at&fS7=120<CR>
12/19/2012 4:03:06 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:03:07 PM Carrier init string sent
12/19/2012 4:03:09 PM Dialing carrier
12/19/2012 4:03:09 PM Sent:ATDTXXXXXXXXXXX<CR>
12/19/2012 4:03:19 PM Waiting for connection
12/19/2012 4:04:00 PM Received:<CR><LF>CONNECT 14400 /V.42/V.42bis<CR><LF>
12/19/2012 4:04:02 PM Connected to carrier
12/19/2012 4:04:02 PM Waiting for protocol initialization
12/19/2012 4:04:05 PM Received:ID=
12/19/2012 4:04:05 PM TAP protocol detected
12/19/2012 4:04:08 PM Sent:<ESC>PG1<CR>
12/19/2012 4:04:09 PM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/19/2012 4:04:11 PM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/19/2012 4:04:11 PM Automatic TAP mode accepted
12/19/2012 4:04:14 PM ----------------------------------------
12/19/2012 4:04:14 PM Working on message to: michael_wilkinson from: Bad Robot
12/19/2012 4:04:16 PM Formatting message
12/19/2012 4:04:16 PM Message contained in single packet
12/19/2012 4:04:18 PM Message contained in single block
12/19/2012 4:04:18 PM Sending block
12/19/2012 4:04:20 PM Sent:<STX>XXXXXXXXXX<CR>Bad Robot:This is a test, actually, yeah, a test.<CR><ETX>2>4<CR>
12/19/2012 4:04:21 PM Received:501 Timeout error<CR><NAK><CR>501 Timeout error<CR><NAK><CR>501 Timeout error<CR><NAK><CR>
12/19/2012 4:04:24 PM Checksum error. Retrying block
12/19/2012 4:04:24 PM Sent:<EOT><CR>
12/19/2012 4:04:26 PM Attempting to hang up modem
12/19/2012 4:04:29 PM Sent:AT<CR>
12/19/2012 4:04:32 PM Received:<CR><LF>OK<CR><LF>
12/19/2012 4:04:32 PM Modem hung up
12/19/2012 4:04:35 PM Carrier retry limit reached. Marking pending messages as bad
12/19/2012 4:04:37 PM FAILED Stn:0 To:michael_wilkinson Frm:Bad Robot Msg:This is a test, actually, yeah, a test.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Thu Dec 20, 2012 8:15 am Post subject: |
|
|
What make and model of modem are you using? I ask because the init string you're using, AT&FS7=120, is really odd... that and you're connecting to the TAP terminal 14400 baud, which is higher than most TAP terminals can properly support (though, from the connection sequence, I can see that the TAP terminal is responding properly at that baud rate). |
|
Back to top |
|
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
Posted: Thu Dec 20, 2012 11:08 am Post subject: |
|
|
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)
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Thu Dec 20, 2012 11:23 am Post subject: |
|
|
I'd recommend trying a lower baud rate, try 300, 1200 or 9600. The only trouble is that the init string generally controls the baud rate, so you'd have to reconfigure the init string to match the new baud rate. Also, do you have a link to the documentation for your modem? I can't seem to find it on the Cisco site. |
|
Back to top |
|
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
Posted: Thu Dec 20, 2012 12:43 pm Post subject: |
|
|
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:26:15 AM Sent:<ESC>PG1<CR>
12/20/2012 10:26:26 AM Received:ID=ID=u<9>/<ETX>
12/20/2012 10:26:28 AM Sent:<ESC>PG1<CR>
12/20/2012 10:26:28 AM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/20/2012 10:26:31 AM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/20/2012 10:26:31 AM Automatic TAP mode accepted
12/20/2012 10:26:33 AM ----------------------------------------
12/20/2012 10:26:33 AM Working on message to: it_department from: Mike_W
12/20/2012 10:26:36 AM Formatting message
12/20/2012 10:26:36 AM Message contained in single packet
12/20/2012 10:26:38 AM Message contained in single block
12/20/2012 10:26:38 AM Sending block
12/20/2012 10:26:40 AM Sent:<STX>XXXXXXXXXX<CR>Mike_W:This is a 2nd test. Let me know if you receive this one too. Thanks!<CR><ETX><02<CR>
12/20/2012 10:26:41 AM Received:501 Timeout error<CR><NAK><CR>&$<14>G~213 Message Accepted<CR><ACK><CR>
12/20/2012 10:26:43 AM Block sent successfully
12/20/2012 10:26:43 AM Packet sent successfully
12/20/2012 10:26:45 AM SUCCESSFUL Stn:0 To:it_department Frm:Mike_W Msg:This is a 2nd test. Let me know if you receive this one too. Thanks!
12/20/2012 10:26:48 AM Sent:<EOT><CR>
12/20/2012 10:26:50 AM Attempting to hang up modem
12/20/2012 10:26:53 AM Sent:AT<CR>
12/20/2012 10:26:56 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 10:26:56 AM Modem hung up\
|
|
Back to top |
|
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Thu Dec 20, 2012 1:30 pm Post subject: |
|
|
If you would, post a segment of the log that had the timeout. Typically speaking, a timeout occurs if we don't receive a response from the carrier in a timely fashion, we assume that there isn't going to be a response and move on before it can clog the system. |
|
Back to top |
|
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
Posted: Thu Dec 20, 2012 1:48 pm Post subject: |
|
|
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/2012 11:18:40 AM Received:110 1.7<CR>Welcome to TAPGATEWAY.COM (20121212)<CR><ACK><CR><ESC>[p<CR>
12/20/2012 11:18:42 AM Automatic TAP mode accepted
12/20/2012 11:18:42 AM ----------------------------------------
12/20/2012 11:18:44 AM Working on message to: kurt_hathaway from: Orion_NPM
12/20/2012 11:18:44 AM Formatting message
12/20/2012 11:18:46 AM Message contained in single packet
12/20/2012 11:18:46 AM Message contained in single block
12/20/2012 11:18:49 AM Sending block
12/20/2012 11:18:49 AM Sent:<STX>XXXXXXXXXX<CR>Orion_NPM:Node mailgw.spillman.com is Up. This is an Exchange critical system.<CR><ETX>>25<CR>
12/20/2012 11:18:51 AM Received:<29><29><8>501 Timeout error<CR><NAK><CR>iQc'213 Message Accepted<CR><ACK><CR>
12/20/2012 11:18:51 AM Checksum error. Retrying block
12/20/2012 11:18:54 AM Sent:<EOT><CR>
12/20/2012 11:18:54 AM Attempting to hang up modem
12/20/2012 11:18:59 AM Sent:AT<CR>
12/20/2012 11:19:00 AM Received:<CR><LF>OK<CR><LF>
12/20/2012 11:19:02 AM Modem hung up
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4382
|
Posted: Thu Dec 20, 2012 1:57 pm Post subject: |
|
|
Ah, now I see. It isn't that they aren't responding, it's that the response packet it getting garbled in transmission:
12/20/2012 11:18:51 AM Received:<29><29><8>501 Timeout error<CR><NAK><CR>iQc'213 Message Accepted<CR><ACK><CR>
The TAP system is accepting the message but something still isn't quite right in the communication, so it's garbling that response packet and the assumed timeout is happening. Try bumping the baud rate down to 300 and let's see what happens. |
|
Back to top |
|
spillmantech
Joined: 19 Dec 2012 Posts: 6 Location: Salt Lake City, UT
|
Posted: Fri Jan 11, 2013 11:25 am Post subject: |
|
|
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.
|
|
Back to top |
|
|