![]() ![]() The following considerations apply to calls handled by hunt pilots: For example, if the Forward No Coverage field is set to voice mail, the call will be sent to that person's voice-mail box when hunting fails. If the call hunting fails, either because all the hunting options were exhausted or because a timeout period expired, the call can be sent to a destination personalized for the person who was originally called. You can implement the personal preferences option by configuring a user's phone so that the Forward No Answer field redirects the call to a hunt pilot, to search for someone else who can answer the call. The personal preference is configured using the CFNC settings at the phone line. ■ A personal preference, configured at the DN of the originally called number when hunting on behalf of that number fails. ■ A specific destination configured globally at the hunt pilot. This call redirection is configured in the Hunt Forward Settings section of the Hunt Pilot Configuration page, and the destination for this redirect can be either of the following options: ■ The maximum hunt timer has expired (configured at the hunt list level). ■ All hunting options have been exhausted, and the call has not been answered. Hunting may fail for one of the following reasons: The hunt list points to one or more line groups, which include DNs.īeginning with CUCM Release 4.1, calls can be redirected to a final destination when the hunting fails. Hunt pilots are dialable patterns in the call-routing database (similar to route patterns, translation patterns, and DNs). ![]() The line group Operators distributes the call to the operator DNs. If no agent answers, the hunt list sends the call to the second line group, Operators.ĥ. The various calldistribution algorithms are covered later in this chapter.Ĥ. Assuming the top-down calldistribution algorithm was selected, 2001 would ring, then 2002. The line group distributes the call to agent DNs. The first line group of Agents is processed.ģ. The hunt list uses top-down processing of the line groups. The hunt pilot distributes the call to the hunt list HelpDesk.Ģ. The CUCM digit analysis result matches the hunt pilot number of 2222. The line groups are assigned to the hunt list HelpDesk:Ī hunt pilot of HelpDesk with the pattern 2222 is configured to use hunt list HelpDesk for call coverage.įigure 14-4 and the list that follows illustrate the call-coverage components involved in distributing a call from the hunt pilot.ġ. ■ Operators line group: Contains the DNs 21. ■ Agents line group: Contains the DNs 20. ![]() In the following example, two line groups are configured: Calls are distributed among the four DNs at the bottom of the figure. The hunt pilot in this example has been configured as 1 800 555-0111. ![]() If the hunting algorithm is ringing a phone and the call is not answered, the CFNA setting of that phone is ignored, and the hunting algorithm goes on to the next line group member.įigure 14-3 illustrates the call-hunting process and components. While hunting, the forwarding configuration of line group members is not used. A hunt pilot can be called directly or a call may be forwarded to the hunt pilot from an IP phone that received a call and is configured to forward calls to the hunt pilot to provide call coverage. ■ Hunt pilots are the numbers that will match on dialed digits to invoke the hunting process. A hunt list is an ordered list of one or more line groups. ■ Hunt lists are assigned to hunt pilots. Line group hunt options and distribution algorithms can be specified to define how call hunting should be performed for the members of the line group. A hunt list can have one or more line groups. ■ Line groups are assigned to hunt lists. ■ Phone DNs or voice- mail ports are assigned to line groups. CUCM call-hunting implementation is composed of the following components: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |