I've installed CUAC v9 Premium (Non HA). The calls get through to the operators, but I cannot hold or park the calls from the operator consoles. There are 4 sites configured, each with their own CTI route point (DDI), own Gateway ports, own Service ports and Park ports. Each site got it's own Device Pool, Location and Calling Search spaces configured in CUCM v9.1. I can answer the calls with the operator console, but have to transfer or hold the calls with the Cisco IP handset that belongs to the operator. The moment I try to transfer or hold the call with the operator console, it drops the call.
Usually this is caused by the original calling party (i.e. the gateway/trunk) not being able to see the CUxAC CTI Ports or transfer destination. CUxAC uses an older CTI behavior which doesn't use the CTI Port's own CSS when performing a transfer/redirect operation. Instead, CUCM ends up using the original calling party's CSS. This is the same behavior CCX used to have before they added the Redirecting CSS choice on the Triggers.
In CUAC 9.1 it now uses the CTI Ports own CSS and not the originating device CSS.
However, a CSS issue is not likely to cut the call off, it just stops a number being dialed. With calls being cut off it sounds like there maybe a codec mismatch, are you using the TAPI Wave Driver on the CUAC Server or the Cisco Media Driver?
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4