View previous topic :: View next topic |
Author |
Message |
djws
Joined: 31 May 2016 Posts: 3 Location: Canada
|
Posted: Tue May 31, 2016 5:59 pm Post subject: Waiting For Protocol Inititialization |
|
|
I've inherited this environment....
Everything seemed to be working until our server for whatever reason decided to change the com port numbers on some of our ports. I've managed to go into Pagegate and verifify the ports it's looking for. In this case, the connector is looking for com 1 and get tap is com4. However it says sent, sent,sent, then retries, then fails...
========================================
5/31/2016 6:39:20 PM Start connection to carrier: Name
5/31/2016 6:39:20 PM Connect using TAP protocol
5/31/2016 6:39:20 PM Setting communication parameters (1200,e,7,1)
5/31/2016 6:39:20 PM Connected to carrier
5/31/2016 6:39:20 PM Waiting for protocol initialization
5/31/2016 6:39:20 PM Sent:<CR>
5/31/2016 6:39:23 PM Sent:<CR>
5/31/2016 6:39:28 PM Sent:<CR>
5/31/2016 6:39:33 PM Sent:<CR>
5/31/2016 6:39:39 PM Carrier retry limit reached. Marking pending messages as bad
5/31/2016 6:39:39 PM FAILED Stn:10 To:156 Frm:Nerds Msg:test
5/31/2016 6:39:39 PM FAILED Stn:10 To:156 Frm:Nerds Msg:test
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1121 Location: US
|
Posted: Wed Jun 01, 2016 7:54 am Post subject: |
|
|
Is this the CONNECTOR log or the getTAP log? the getTAP module allows PageGate to RECEIVE message traffic via the TAP protocol - the connector sends messages OUT to carriers for delivery to the device_________________ 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 |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4355
|
Posted: Wed Jun 01, 2016 8:19 am Post subject: |
|
|
Hm... based on what I can see in the log, it looks like the other end of things isn't responding. With the TAP protocol, the sending system initiates the sequence by sending a carriage return and the receiving system is then supposed to respond with "ID=".
The fact that you're not seeing that indicates that while PageGate is referencing an extant COM port, whatever is on the other end of the serial line isn't responding. |
|
Back to top |
|
djws
Joined: 31 May 2016 Posts: 3 Location: Canada
|
Posted: Wed Jun 01, 2016 8:47 am Post subject: |
|
|
Ok, thanks. I will look at the Carriers device which is attached to the other end of the connection.
|
|
Back to top |
|
OzCom
Joined: 22 Oct 2003 Posts: 1121 Location: US
|
Posted: Wed Jun 01, 2016 8:56 am Post subject: |
|
|
"Carrier's device attached to the other end of the connection" ???
Is it a paging terminal using a NULL modem serial cable or is it a cellular modem? If it is a cellular modem, you do NOT want to use the TAP protocol_________________ 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 |
|
djws
Joined: 31 May 2016 Posts: 3 Location: Canada
|
Posted: Wed Jun 01, 2016 9:42 am Post subject: |
|
|
It is a paging terminal.
This has all worked for years, until windows decided to change the com port numbers. Which I changed back according to the previous config..
|
|
Back to top |
|
|