This is old gripe I have with CCM 4.X and I want to know what others think about it.
From very early versions CCM has had the AC hunt groups that had the neat feature of being able to specify AC usernames and line #s as hunt group members as well as DNs as hunt group members. You could mix and match for robust scenarios.
Starting with version 4.0 line group/hunt list/hunt pilot was introduced. Also the "busy trigger" for DNs was introduced.
The new LG/HL/HP model introduced a much better feature set for hunting. It also observes the "busy trigger" such that if a person is on a single phone call and his/her DN is configured with a busy trigger of 2, the call will still hunt to that user.
Problem 1: The old AC hunt group does not observe the busy trigger. So if I have a DN with a busy trigger of 6 for a switchboard person, the AC based hunt group will consider that line busy and hunt past it with only 1 call on the line.
Problem 2:The new model of LG/HL/HP DOES observes the busy trigger but does not offer the flexability of adding AC user and line # as a line group member.
Conclusion: Each model has features the other needs. This should be reconciled.
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...