Need some help here. I'm getting this error "Too many transfer failures" when i do a reactive debug, it happens at the select resource step. I am sure that it's not the problem with the script as it's working previously. Attached the MIVR logs and a section of the logs which I think its the cause of the problem.
6451: Feb 23 10:03:38.447 SGT %MIVR-SS_TEL-7-UNK:CallID:0 MediaId:4068/1 Task:27000000001, TerminalConnection to Terminal: CTIP_9009 is HELD
6452: Feb 23 10:03:38.449 SGT %MIVR-SS_TEL-7-UNK:OrigCall=CallID:0 MediaId:4068/1 Task:27000000001, ConsultEvent= ConsultCallActive
I can make a pretty good guess on this one having seen the situation occur many times before.
UCCX is not aware of, and doesn't really understand, the partitions and call search spaces on CUCM. When you do a select resource step, and attempt to send the call to the agent, the UCCX server will basically do a switch hook flash type supervised transfer to transfer the call to the agent.
When the transfer attempt is made, the CTI port that the caller is queued on will attempt to outdial to the agent's extension. It assumes that the agent phone is reachable, but has no way to verify this.
If the agent extension cannot be reached as a destination using the calling search space assigned to the CTI port, the transfer will fail. The agent will likely get stuck in a reserved state, or maybe even made not ready by the system. You can validate this by opening the dialed number analyzer in CUCM, and use the analyze function to dial the agent extension using the CSS assigned to your CTI ports.
Every time I've seen this problem over the years, the above issue was the problem. Check it out and see if it doesn't solve your issue.
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.