|
A hunt group is a collection of users accessible through a single directory number. Calls to that hunt group can be answered by any available member of the group. The order in which calls are presented can be adjusted by selecting different group types and adjusting the order in which group members are listed. For a full overview of hunt groups, see Hunt Groups in the Telephone Features section.
|
|
| • | Call Presentation
The order in which the available members of the hunt group are used for call presentation is selectable. |
| • | Availability
There are a range of factors which control whether hunt group calls are presented to a user in addition to that user being a member of the hunt group. |
| • | Queuing
This optional feature allows calls to be queued when the number of calls to be presented exceeds the number of available hunt group members to which call can be presented. |
| • | Announcements
On systems with a voicemail server (Voicemail Pro, Voicemail Lite (pre-IP Office 5.0) or Embedded Voicemail), announcements can be played to callers waiting to be answered. That includes calls that are ringing and calls that are queued. |
| • | Overflow
This optional feature can be used to redirect calls to an overflow group or groups when not answered within a set time. |
| • | Fallback
A hunt group can be taken out of operation manually or using a time profile. During fallback, calls can be redirected to a fallback group or sent to voicemail or just receive busy tone. Two types of fallback are supported; night service and out of service. |
| • | Voicemail
Calls can be redirected to voicemail. The IP Office allows selection of whether hunt group calls remain in the hunt group mailbox or are copied to the individual mailboxes of the hunt group members. When messages are stored in the hunt group's own mailbox, selection of who receives message waiting indication is possible. |
|
Changing the name of a hunt group has the following effects:
| • | A new empty mailbox is created on voicemail with the new hunt group name. |
| • | Entries in other groups' Overflow lists will be updated. |
| • | Out-of-Service and Night-Service fallback references are updated. |
Modifying the extension number of a hunt group updates the following:
| • | Overflow, Out of Service Fallback and Night Service Fallback group entries. |
| • | Incoming call route entries. |
When a hunt group is deleted, all references to the deleted group will be removed including:
| • | Entry in Incoming call routing table. |
| • | Transfer target in internal auto-attendant. |
| • | Overflow, Night-Service or Fallback-Service on other groups. |
| • | DSS keys monitoring group status. |
Hunt Groups in a Small Community Network (SCN)
In a Small Community network, the extension numbers of users are automatically shared between IP Office systems and become diallable from other systems without any further programming.
For IP Office 4.0+, the following features are available for hunt groups within a Small Community Network. For pre-IP Office 5.0 systems, these features requires the IP Offices to have Advanced Small Community Networking licenses.
| • | Advertised Hunt Groups
Each hunt group can be set as being 'advertised'. The hunt group can then be dialed from other systems within the SCN. The hunt groups extension number and name must be unique within the network. Non-advertised hunt group numbers remain local only to system hosting the hunt group. |
| • | Distributed Hunt Groups
Hunt groups on a system can include users located on other IP Office systems within the SCN network. Distributed hunt groups are automatically advertised to other systems within the SCN. Note that distributed hunt groups can only be edited on the system on which they were created. |
© 2009 AVAYA
15-601011 Issue 23.p.-
07:06, 30 October 2009
(hunt_group_settings.htm)
Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing
by Avaya before they become applicable to any particular order or contract. The company reserves the right to
make alterations or amendments at its own discretion. The publication of information in this document does not
imply freedom from patent or any other protective rights of Avaya or others.
All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other
trademarks are the property of their respective owners.
Last Modified: 09/06/2009
|
Manager: Configuration Settings