The hunt groups you find under Service -> Cisco CM Attendant Console are strictly top down - they try the first member, then the second, then the third, etc. Also, the hunt groups stops when it finds an available member (a DN it can ring). The Hunt Lists/Line Groups you find under Route Plan -> Route/Hunt are more complex. You can choose how the line group decides who gets the call (top down, circular, longest idle, broadcast). You can have the line group perform a different action based on the state of the DN (No answer, busy, not available). You can configure multiple line groups for a single hunt list allowing you to forward a call to a different group if a particular member is not available. In short, hunt lists/line groups provide far more options than hunt groups when dealing with the selection process for multiple DNs.
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...