RE: A problem with CTIOS Toolkit http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id= 2013-06-20T01:33:35Z 2013-06-20T01:33:35Z Jean-Marc Lacoste http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=4840101 2011-12-04T08:39:07Z 2011-12-04T08:39:07Z

We have found the solution for this issue. The clientID that identifies the CTIOS connection is built on the machine name, the process ID and the thread name. The issue is that the thread name is not initialized by default, so we have to do it in the code. We have overrided the connect() method to set the thread name to a unique value before calling the CTIOS connect method and it works. Our understanding is that, before CTIOS 7.5, CTIOS server was not checking that the clientID was unique. Best regards, jmlacoste & dostvald

Jean-Marc Lacoste 2011-12-04T08:39:07Z Jean-Marc Lacoste http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=4803599 2011-11-26T16:18:56Z 2011-11-26T16:18:56Z

Hello, We are facing the same issue. We have developped two years ago a third party server application for CTIOS that provides an IP Phone XML interface to manage multiple agents, based on Net CIL 7.0.2. The application handles multiple agents. This application has run on production for two years on CTIOS 7.1.5. However, on CTIOS 7.5 with the previous CIL client or after recompiling with CIL 7.5.9 client, we have found that when login another agent from the application the first one does not receive event but can still control by sending commands. CTIOS Server is mixing the two CTIOS connections. The CtiOsSession is different but the ClientID is the same, it is actually the Windows Process ID First CTIOS connection CTIOS Client : 17:59:28.2942 CtiOsSession(11203942).MakeRequest, (ClientPassword:(null) CILClientID:.1504) CTIOS Server : 17:59:27 CTIOS1-ctios Trace: ClientMgr[1]::IdentifyClientRequest, Client[00226]: Changing ClientID ["00226"->".1504"]. Second CTIOS connection CTIOS Client : 18:01:36.2005 CtiOsSession(28068188).MakeRequest, (ClientPassword:(null) CILClientID:.1504) CTIOS Server : 18:01:35 CTIOS1-ctios Trace: ClientMgr[1]::IdentifyClientRequest, Client[00227]: Changing ClientID ["00227"->".1504"]. 18:01:35 CTIOS1-ctios Trace: CServiceBroker::OnEvent(). 18:01:35 CTIOS1-ctios Trace: ClientMgr[1]::AddToClientIDMap[2112], Found Duplicate Client ID: .1504, PreviousClient[226, 0x42f2008], NewClient[227, 0x4172800] Afterward, when login the second agent the first one (902420) is logged out. 18:01:35 CTIOS1-ctios Trace: [agent.5006.902420]::HandleOnLastSessionClosedEvent(): state [eAvailable] forcing logout. 18:01:35 CTIOS1-ctios Trace: [agent.5006.902420] SET_AGENT_STATE_REQ ( eLogout ) : (PeripheralID:5006 AgentState:eLogout NumSkillGroups:0 EventReasonCode:255 AgentWorkMode:0 AgentID:902420 AgentInstrument:81110) How could we force the server to consider the second CTIOS Connection as a new one ? Is it fixed on more recent CTIOS version ? jmlacoste

Jean-Marc Lacoste 2011-11-26T16:18:56Z