Actually traditional IQ doesn't have a collate time attached to it, which allows the network time to determine longest available agent at both sites. I don't believe traditional creates a "reserved" state, which, in my situation is triggering the app to pop.
The app is popping on the virtual call. We have a sent connect in the CCT but with NIQ-IP, an agent goes reserved when a "race" scenario is created, thus creating a "ghost pop" when the call is sent to the other agent.
Does the CCEM actually flag when the call starts with an agent? Or does is...
We have NIQ over IP and one of our CTI applications (internally developed) is popping on the virtual call, when the agent goes reserved.
Has anyone dealt with CTI apps over IP-NIQ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.