We'd like agents to be able to hand off long duration calls to another line, to be able to free up their agent extension for incoming calls from UCCX. However, if we transfer the call to another ext on the same phone, CAD still shows them in a talking state. The thing is, I added extra lines to the agent device profiles a week ago and we were able to do this - the call would go onto a different line, and CAD would go back to ready, but this week, no go. However we can still initiate calls on other non-agent extensions on a phone and CAD stays in a ready state - this is what we want. So, obviously we're puzzled by this inconsistent behavior and are wondering if what we want to do is possible?
Wow. I wonder why it ever worked. You are not supposed to do that, really.
What you might want to do is actually: send the long call back to the UCCX and let it wait there. This way your reporting would be consistent and you don't have to worry about multiple lines on your agents' phones.
I think I know why it worked initially - I had just added extra extensions to the agents device profile and UCCX must have not been aware of them yet (not synched up ?!).
Ok, so I take it by your answer that UCCX is not designed do this at all - correct? If that's the case, then I'd like to know what the "multiple line" support is supposed to do in UCCX. And I'm guessing that when you say send them back to UCCX you are meaning just do a transfer back to the trigger, correct?
Hi, I ran through the UCCX 8.5(1) SRND and there IS multiline support (explained on p. 47) There is a note, though:
ACD calls should only be transferred to the ACD lines controlled by Cisco Unified CCX.
There's no additional info on that, "should" is a bit vague in this case, we don't know what happens if the calls are transferred to a non-ACD lines, does the system blow up? Or it's more or less like a mosquito bite? Or the behaviour is quite unpredictable?
About sending the calls "back", well, yes, it's just sending the call to a DN, triggering an application (not necessarily the same application that had delivered the call the first time).
We are experiencing unpredictable behavior with non-UCCX extensions on our phones. When these lines are used, sometimes the agent stays in a ready state and sometimes they are switched to not ready. It would be nice if it was predictable.
So, it sounds like we shouldn't be doing this at all - is this correct?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.