Communication with CTIOS Server has failed

Unanswered Question
Sep 4th, 2008
User Badges:

On one PG of side A, following errors in event log were found

-----------------------------------------------

Client:CTIOSServer Object:10.100.36.26 Error Event Report: CTIOS Server "pg1": Communication with CTIOS Server: "10.100.36.26" has failed.


Invalid Enterprise CTI message header (Length:0x5, Type:0x10000000) received from client "CTIOSServer" at 10.100.36.26


Configuration response for Logical Controller 5000 received OPI error code 1 (E_UNKNOWN_INTERFACE_CTRLR_ID)


Configuration response for Logical Controller 5000 received OPI error code 1 (E_UNKNOWN_INTERFACE_CTRLR_ID)

----------------------------------------------------------------------

where 10.100.36.26 is the another PG on side A


What are these error logs? Why are they generated?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
htarra Wed, 09/10/2008 - 13:33
User Badges:
  • Bronze, 100 points or more

The error means: In a duplexed environment, if there are no Computer Telephony Integration (CTI) Clients connected to the CTI Server for more than 60 seconds, the CTI Server process bounces. This forces the non-active CTI Server to become active. In a simplexed environment, the CTI Server simply shuts down and restarts every 60 seconds. This is designed to make the CTI Server fault tolerant. If there are no CTI Clients connected, the CTI Server is unable to identify whether the clients do not connect because of a network issue or whether there are simply no agents online. In order to rule out the possibility of a network problem, the CTI Server process switches sides every minute until the CTI Clients connect. This fixes certain network issues. However, if the absence of connecting clients is intentional, it generates unnecessary error messages.


The client did lose network connectivity to the server, it is not service affecting in the way that the client is self recovering and it will not drop a call in progress, but client/server network connectivity over the LAN/WAN needs to be checked to avoid similar scenarios.


K_require Thu, 09/11/2008 - 03:22
User Badges:

Really many thanks. I will investigate further on this and now I found the direction to work.

Actions

This Discussion