Search found 4 matches

Hi Aaron,

Thanks for the tip.
I was able to find a second TAP terminal number for our area code and it works fine.

-Khalil

It's a landline.
However, I finally figured out the problem.
It was just the TAP terminal being busy.
And perhaps the modem init strings were not correct.
I've deleted all the modems, rebooted the system, let it recognize and re-install the modems again, and then set all the init strings to auto.
Finally, I can connect and send TAP/SMS using my three modems: MultiTech, USR Courrier, and USR Sportster. No luck with the Hayes Optima.

New problem: I can send TAP to Bell Mobility successfully.
I try to send to Rogers AT&T Wireless, and it connects to the TAP terminal, establishes a TAP session, then I get 'Bad ID or message content.... message will not be retried....'.

I think I've seen that somewhere on this forum.

Thanks for the reply.
I don't have a 1 in the phone number because it's local. In area code 613, we have to use 10 digit numbers. The 8, is for line access.
If I plug a standard phone set in the same line and dial the TAP terminal, it answers. But the modem always gets a BUSY or NO CARRIER. I've set the 'Carrier' to use TAP/1200/even/7/1 with hardware control.
I don't know what else to test.

Our PageGate setup has one Multitech modem.
It looks like PageGate can recognize the modem and find the correct setup strings, but it always fails to connect. It always gets busy or no carrier.
When I try to call the same TAP terminal from my desk phone, I always get through.
I suspect that I must have configured something wrong.
Part of the log follows.
Any help will be much appreciated.
4/15/2008 11:21:09 AM ========================================
4/15/2008 11:21:09 AM Start connection to carrier: RogersWireless
4/15/2008 11:21:09 AM Connect using TAP protocol
4/15/2008 11:21:09 AM Setting communication parameters (300,e,7,1)
4/15/2008 11:21:09 AM Attempting to reset modem
4/15/2008 11:21:12 AM Sent:AT<CR>
4/15/2008 11:21:12 AM Received:<CR><LF>OK<CR><LF>
4/15/2008 11:21:13 AM Modem reset
4/15/2008 11:21:13 AM Attempting to send dialer init string
4/15/2008 11:21:14 AM Sent:AT&FQ0V1X4&D2N0+MS=2,0<CR>
4/15/2008 11:21:14 AM Received:<CR><LF>OK<CR><LF>
4/15/2008 11:21:15 AM Dialer init string sent
4/15/2008 11:21:15 AM Dialing carrier
4/15/2008 11:21:16 AM Sent:ATDT8,,6138515208<CR>
4/15/2008 11:21:24 AM Waiting for connection
4/15/2008 11:21:33 AM Received:<CR><LF>BUSY<CR><LF>
4/15/2008 11:21:33 AM Attempting to hang up modem
4/15/2008 11:21:35 AM Sent:AT<CR>
4/15/2008 11:21:36 AM Received:<CR><LF>OK<CR><LF>
4/15/2008 11:21:36 AM Modem hung up
4/15/2008 11:21:36 AM Carrier retry limit reached. Marking pending messages as
bad

Author	Message
Topic: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Forum: PageGate Support Posted: Tue Apr 15, 2008 2:45 pm Subject: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Hi Aaron, Thanks for the tip. I was able to find a second TAP terminal number for our area code and it works fine. -Khalil
Topic: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Forum: PageGate Support Posted: Tue Apr 15, 2008 1:31 pm Subject: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	It's a landline. However, I finally figured out the problem. It was just the TAP terminal being busy. And perhaps the modem init strings were not correct. I've deleted all the modems, rebooted the system, let it recognize and re-install the modems again, and then set all the init strings to auto. Finally, I can connect and send TAP/SMS using my three modems: MultiTech, USR Courrier, and USR Sportster. No luck with the Hayes Optima. New problem: I can send TAP to Bell Mobility successfully. I try to send to Rogers AT&T Wireless, and it connects to the TAP terminal, establishes a TAP session, then I get 'Bad ID or message content.... message will not be retried....'. I think I've seen that somewhere on this forum.
Topic: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Forum: PageGate Support Posted: Tue Apr 15, 2008 11:13 am Subject: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Thanks for the reply. I don't have a 1 in the phone number because it's local. In area code 613, we have to use 10 digit numbers. The 8, is for line access. If I plug a standard phone set in the same line and dial the TAP terminal, it answers. But the modem always gets a BUSY or NO CARRIER. I've set the 'Carrier' to use TAP/1200/even/7/1 with hardware control. I don't know what else to test.
Topic: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Forum: PageGate Support Posted: Tue Apr 15, 2008 10:26 am Subject: Not completing connection to TAP terminal
khalilhayek Replies: 6 Views: 17832	Our PageGate setup has one Multitech modem. It looks like PageGate can recognize the modem and find the correct setup strings, but it always fails to connect. It always gets busy or no carrier. When I try to call the same TAP terminal from my desk phone, I always get through. I suspect that I must have configured something wrong. Part of the log follows. Any help will be much appreciated. 4/15/2008 11:21:09 AM ======================================== 4/15/2008 11:21:09 AM Start connection to carrier: RogersWireless 4/15/2008 11:21:09 AM Connect using TAP protocol 4/15/2008 11:21:09 AM Setting communication parameters (300,e,7,1) 4/15/2008 11:21:09 AM Attempting to reset modem 4/15/2008 11:21:12 AM Sent:AT<CR> 4/15/2008 11:21:12 AM Received:<CR><LF>OK<CR><LF> 4/15/2008 11:21:13 AM Modem reset 4/15/2008 11:21:13 AM Attempting to send dialer init string 4/15/2008 11:21:14 AM Sent:AT&FQ0V1X4&D2N0+MS=2,0<CR> 4/15/2008 11:21:14 AM Received:<CR><LF>OK<CR><LF> 4/15/2008 11:21:15 AM Dialer init string sent 4/15/2008 11:21:15 AM Dialing carrier 4/15/2008 11:21:16 AM Sent:ATDT8,,6138515208<CR> 4/15/2008 11:21:24 AM Waiting for connection 4/15/2008 11:21:33 AM Received:<CR><LF>BUSY<CR><LF> 4/15/2008 11:21:33 AM Attempting to hang up modem 4/15/2008 11:21:35 AM Sent:AT<CR> 4/15/2008 11:21:36 AM Received:<CR><LF>OK<CR><LF> 4/15/2008 11:21:36 AM Modem hung up 4/15/2008 11:21:36 AM Carrier retry limit reached. Marking pending messages as bad