01-13-201104:03 PM - last edited on 03-25-201910:55 PM by ciscomoderator
Where can I locate a BACD implementation guide for CCA 3.0 and the UC560?
I need to know specifics about how many BACD groups or pilots you can build, what the maximum number the system can have in the hold queue at a time, what happens to the last caller if the queue is maxed out, and if there have been any improvements to the visibility of the queues from the handsets?
From what I am reading on other posts I would like to know what bugs we may encounter...
I would not use the AA as a front end for all calls to BACD, since the max number of simultaneous connections to CUE is finite (6 for UC540; 12 for UC560).
We support 10 Bacd groups, each with 30 call capacity in queue, so no problem there.
We do not support voice hunt group types (Blast) in Bacd. Just the three ephone hunt algorithms (sequential, longest idle, or peer (circular)).
You can use DIDs mapped to the BACDs and I suppose if the members of the BACD were also in a blast group, and you used the blast group as a front end to get them all to ring, and the HLog may still work for both, but I would suggest this be tried first since I am not sure and not near a lab. But front end call handling won't be captured in BACD measurements (maybe bit a big deal) and calls in queue will not use blast subsequently so kinda half cooked?
Perhaps just tweak the CCA parameters for BACD to allow for shorter duration on each agent phone to ring through all of them a bit faster?
I would avoid CLI for this. You can find threads back in 2009 on this community, when partners pulled their hair out trying to make it work manually (and I don't think blast is supported that way anyway). If you do feel up for that challenge, I would look at ISR CUCME and perhaps contact center.