11-21-2008 01:35 PM - edited 03-15-2019 02:41 PM
guys
was just wondering how you guys handle this. More from a CME prospective though. the scenario is you have a hunt group that has say six of the operator lines in it. all calls going to the operator hits that hunt group. now if for some reason the operator needs to forward all calls to a different extension that is not in the hunt group, how would you configure this to operate.
11-28-2008 06:15 AM
Hi Arvind, have considered the option 'final' within the ephone-hunt? If a number in the list is busy or does not answer, the call is redirected to the next number in the list. The last number tried is the final number, which is defined using the final command.
Taken from the CME Command Reference:-
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_e1ht.html#wp1024368
You can tune or decrease the timeout value so that if a call that is not answered it is redirected to the next number in the hunt-group list quicker.
Hope this helps.
Allan.
11-28-2008 06:33 AM
Hi Arvind,
Hope all is well!
Because the Call Forward is ignored on the Hunt Group most people have to take a different approach. An excellent way to deal with this "coverage" scenario is to set up any backup person with the ability to Dynamically join the Hunt Group when necessary. Here is the method;
Dynamic Hunt Group Membership
Hunt groups allow you to set up pools of extension numbers to answer incoming calls. Up to 20 wildcard slots can be entered in the list of hunt group extension numbers to allow dynamic group membership, in which authorized phone users can join a hunt group whenever a vacant wildcard slot is available and they can leave when they like. Each phone user who joins a group occupies one slot. If no slots are available, a user who tries to join a group hears a busy signal.
Allowing dynamic membership in a hunt group is a three-step process:
1. Use the list command in ephone-hunt configuration mode to specify up to 20 wildcard slots in the hunt group.
2. Use the ephone-hunt login command under each directory number that should be allowed to dynamically join and leave hunt groups. Directory numbers are disallowed from joining hunt groups by default, so you have to explicitly allow this behavior for each directory number that you want to be able to log in to hunt groups.
3. Use the fac standard command to enable standard FACs or the fac custom command to define custom FACs. FACs must be enabled so that agents can use them to join and leave hunt groups.
From this good doc;
Hope this helps!
Rob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide