I'm having a problem with the way in which 3.1 (2c)handles extensions in hunt groups when they are logged out.
I have a hunt group (7899) containing 3 DN's 7900,7901 and 7902. If 7900 is logged in and 7899 is called, no problem 7900 rings. If 7900 is busy and 7901 logged in the 7901 rings. However if 7900 is logged out the call fails to re-order tone. I thought that the Cisco TCD was supposed to look at the state of the Line before attempting the call and step over unavailable/busy extensions.
Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen
If anyone else in the forum has some advice, please reply to this thread.
I have had a similar problem with hunt groups. The only way I could get around this was to forward the call on no answer for each user back onto the initial hunt group. This worked for longest idle hunt group pilot points.
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...