« Back to CTIOS Toolkit Questions

RE: Monitoring without login

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hello There,
I have connected to a CTI OS Server 8.0.1 using and AgentMode connection to monitor when the current agent receives an event of "OnAgentStateEvent" with the ReasonCode '32767' to popup a message to the agent to warn him that he is not ready beacause of the redirect.
My application works fine and it is working on production environment.
I have just one issue that the supervisor is complaning about the agent to be "twice login". Even when the agent loggout from the CTI OS Toolkit, my application still working (and keep the agent logged in) to receive future events.
 
There is anyway to set an agent mode connection and log in with an agent WITHOUT count the agent as "LOGGED IN"? This is "breaking" the reports...
 
I'd like to develop some "silent monitoring..."
 
Thanks
 
Guilherme

As you have noted, CTIOS allows more than one instance of an agent to be logged in. The only way around this is to set RejectIfAlreadyLoggedIn in the CTIOS registry (see the CTIOS System Administrator Guide, but that would defeat the purpose of your agent mode connection to monitor the agentstateevent. How is the agent logging in? I can think of no way around having your agent mode connection not to be counted as an agent logged in.

This is unrelated to silent monitoring.

Hi David,
Thanks for your fast reply.
My application is installed in a Call Center with 30 people using through CTI OS Toolkit - Agent Desktop 8.0.1.
Every time that the Cti Toolkit opens (we monitors the .exe process) we start to monitor the agent, based on the CTI OS\LastLogin windows registry. After that, the agent log in using cti toolkit and at this moment, this agent is "twice logged in".
When the agent logs out or close de application, we need to keep our monitoring and mantain the agent as "logged in", otherwise how can we listen to the agents events?
We thought to create a bridge service as Monitor Mode (just one) to monitor all agents and call back all clients to do an specific procedure when the agent event turns into "not ready" because of a "redirect on no answer" reason code.
If you have any strategy to help us, we'll appreciate that.
 
Regards
Guilherme

I see no way around having 2 agent mode connections in your scenario. An alternative is to create your own CTIOS Agent desktop based on the code in the toolkit for the CTIOS Agent Desktop and add the check of not ready reason to your own application. Then you wouldn’t need a second application to check.

Regarding a monitor mode application, you certainly can use it to notify your agents that they are not ready due to a redirect on no answer.

David Lender (467)
Shannon McCoy (91)
Arthur Shats (57)
Christopher Nagel (47)
GEOFFREY THOMPSON (38)