UCCX 11.0 - How do I show CSQ info on the handset instead of the CTI Port?
I'm currently running UCCX 126.96.36.19900-75 (ES07-38) and CUCM 188.8.131.5200-2. I am using UCCX scripts to route and place calls into CSQ's using the select resources step.
The Call Center I administer has Agents who answer many different CSQ's at once. They need to know which CSQ the call they are answering came from, so they know how to greet the caller.
For example: CSQ A would be for calls pertaining to Company A and CSQ B would be for calls pertaining to Company B. My agents need to know to answer "Thank you for calling Company A" when they receive a call from the Company A CSQ.
I am currently using the "Set Enterprise Data" step, which allows me to use Finesse to show which Queue a call is coming from, however; I need the handset itself to be able to do this. My Agents login to Finesse and basically never interact with it again (and the don't partically like having to depend on a webpage for this info). We work in a situation where our Agents do a lot of web research, and it's not very practical l to have Finesse be the front Window at all times, since they often have tens of windows or tabs open at all times.
There has to be a way to show queue info on our 7962 handsets themselves. Instead of showing the CTI port on the handset (which is basically useless info), I want to show the CSQ that the call is originating from.
Chris is correct in saying that it is not possible to use CSQ information on the phone if agents are using Finesse Desktop. If you want this to be displayed on phone then the only way is to configure Finesse IPPA and let the agents use that for handling Contact Center calls.
I wonder if there isn't a way to do this. It wouldn't be scalable and it would require multiple scripts. If you create two different Call Control Groups, you should be able to configure the Display name for each group. If the two CSQs are assigned today by different scripts, then just associate the application for each side with a different Call Control Group. If, however, they are both in one script, then you will need to split at least one of them off into a new script, which is called by the first and is assigned to an application that is configured with the other CCG.
Please note: I have not tested this and this is a hack. It's just a hack that *should* work.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...