 |
| |
|
|
| Search found 3 matches |
| Author | Message |
|---|---|
 Topic: Waiting For Protocol Inititialization |
|
| djws Replies: 5 Views: 10100 |
 Forum: PageGate Support Posted: Wed Jun 01, 2016 9:42 am Subject: Waiting For Protocol Inititialization |
| 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.. |
|
| Topic: Waiting For Protocol Inititialization |
|
| djws Replies: 5 Views: 10100 |
Forum: PageGate Support Posted: Wed Jun 01, 2016 8:47 am Subject: Waiting For Protocol Inititialization |
| Ok, thanks. I will look at the Carriers device which is attached to the other end of the connection. | |
| Topic: Waiting For Protocol Inititialization |
|
| djws Replies: 5 Views: 10100 |
Forum: PageGate Support Posted: Tue May 31, 2016 5:59 pm 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 |
|
All times are GMT - 5 Hours |