RE: A problem with CTIOS Toolkit

RE: Error: failure code:14 Number of supported monitor mode connections [2

2013-03-15T10:47:24Z

Hi, I think there is nothing you can do on the client side for this. I can't remember if it requires a reboot, I did this so long time ago. In some cases we have installed a third CTIOS and used that only for monitoring. This is not supported by Cisco but has worked for us and separates monitoring from agent traffic.

RE: Error: failure code:14 Number of supported monitor mode connections [2

2013-03-15T10:11:53Z

Hi, there is a registry setting in CTIOS server, that states how many monitor mode connections are allowed. I think the default is 2, we have used 8 with no problems for 600 agents envinronments. It seems for me that there are some monitor mode applications there and you should change the registry setting from 2 to something bigger.

RE: CTI OS Server Offline on CTI OS Server-Client connection

2013-03-13T14:26:14Z

Hi, typically 42027 is a cti-server port for CG1 and 42028 is for ctios-server. Are you sure you are using the rigth port?

RE: A problem with CTIOS Toolkit

2012-10-10T10:49:35Z

Big Thanks for the code sample. I had to modify it a bit (code below), since the thread name was already set where I called Set_Agent for the first time. I found out that the latest point where current.thread.name was not set in my code was just before connect method. Also I had to create a new property, AgentPeripheralNumber, that I can set later in the code where I know what it is. Is there any (easy) way to see if this fixes the issue other than installing the new client to 600 workstations. public class CtiOsSessionWithAgentID : CtiOsSession { private string _agentID; public string sAgentPeripheralNumber { get { return _agentID; } set { _agentID = value; } } public CtiOsSessionWithAgentID(string pAgentID) { _agentID = pAgentID; } new public CilError SetAgent(Agent NewAgent) { // could not set thread name here, since it was alraedy set return base.SetAgent(NewAgent); } new public CilError Connect(Arguments rArgs) { if (Thread.CurrentThread.Name != null) { // cant't set the thread name since it is set already } else { Thread.CurrentThread.Name = _agentID; } return base.Connect(rArgs); } }

RE: A problem with CTIOS Toolkit

2012-10-09T10:58:15Z

We are hitting this same problem. Is there a way to verify from ctios server logs that the threadname is set correctly, since othervise it is hard to see if this is fixed. Also, would you like to share the new connect method.