User's Manual

Avaya Branch Gateway Manager 10.0 Page 310
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
5.8.1 Hunt Group
This tab is used to define the name, extension number and basic operation of the hunt group. It is also used to select the
hunt group members.
Usability
· Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
· Name: Range = Up to 15 characters
The name to identify this hunt group. This field is case sensitive and must be unique.
· Names should not start with a space. Do not use punctuation characters such as #, ?, /, ^, > and ,.
· Voicemail uses the name to match a group and its mailbox. Changing a group's name will route its voicemail calls to
a new mailbox. Note however that Standalone Voice Mail will treat names such as "Sales", "sales" and "SALES" as
being the same.
· Extension: Range = 2 to 15 digits.
This sets the directory number for calls to the hunt group.
· Ring Mode: Default = Sequential
Sets how the system determines which hunt group member to ring first and the next hunt group member to ring if
unanswered. This is used in conjunction with the User List which list the order of group membership.
· Collective
All available phones in the User List ring simultaneously.
· Collective Call Waiting
This is a Collective hunt group as above but with hunt group call waiting also enabled (previous versions of Branch
Gateway Manager used a separate Call Waiting On control to select this option for a Collective group). When an
additional call to the hunt group call is waiting to be answered, users in the group who are already on a call will
receive call waiting indication. On phones with call appearance buttons, the call waiting indication takes the form of
an alert on the next available call appearance button. On other phones, call waiting indication is given by a tone in
the speech path (the tone is locale specific).
· The user's own Call Waiting On setting is overridden when they are using a phone with call appearances.
Otherwise the user's Call Waiting On setting is used in conjunction with the hunt group setting.
· Sequential
Each extension is rung in order, one after the other, starting from the first extension in the list each time.
· Rotary
Each extension is rung in order, one after the other. However, the last extension used is remembered. The next call
received rings the next extension in the list.
· Longest Waiting
The extension that has been unused for the longest period rings first, then the extension that has been idle second
longest rings, etc. For extensions with equal idle time, 'sequential' mode is used.
· Where hunt group calls are being presented to a twinned extension, the longest waiting status of the user can be
reset by calls answered at either their master or twinned extension.
· No Answer Time (secs): Default = System Default. Range = System Default or 6 to 99999 seconds.
The number of seconds an extension rings before the call is passed to another extension in the list. This applies to all
telephones in this group and also any Overflow Groups it uses. For collective hunt groups, the idea of moving to
the next member when the No Answer Time expires does not apply, instead calls will continue ringing unless
overflow or voicemail is applied.
· Hunt Group Mode: Default = Local.
· Select Local for hunt groups that should always be handled by the Avaya Branch Gateway. Calls arriving to the
local hunt group number are processed by the Avaya Branch Gateway and targeted to the hunt group members as
configured on the Avaya Branch Gateway.
· Select Centralized for extensions that are normally handled by the core feature server (Avaya Aura
Communication Manager) and are handled by the Avaya Branch Gateway only when in survival mode due to loss
of connection to the Avaya Aura® Session Manager. Calls arriving to a centralized hunt group number when the
Avaya Aura Session Manager line is in-service are sent by the Avaya Branch Gateway to Avaya Aura Session
Manager and are then processed by the core feature server according to the core feature server hunt group
configuration. Calls arriving to a centralized hunt group number when the Avaya Aura Session Manager line is
out-of-service are processed by the Avaya Branch Gateway and targeted to the hunt group members as
configured on the Avaya Branch Gateway.
· To provide consistent operation when the Avaya Aura Session Manager line is in-service or out-of-service, the
following is recommended:
316