User's Manual

Avaya Branch Gateway Manager 10.0 Page 311
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Configuration Settings: Hunt Group
· The Avaya Branch Gateway hunt group should be configured consistently with the hunt group administration
at the core feature server that serves the survivable branch endpoints in normal mode.
· Members included in the Avaya Branch Gateway hunt group should be only those members that are in the
local branch, even if the core feature server hunt group includes additional members from other branches
(that is, centralized users).
· DDI Numbers: Default = Blank.
This field is optional for systems where there is a clear mapping of DID numbers to hunt group number, for example
DID 01555364123 and extension 884123.
· Hold Music Source: Default = No Change.
The system can support up to 4 music on hold sources; the System Source (either an internal file or the external
source port or tones) plus up to 3 additional internal wav files, see System | Telephony | Tones & Music . Before
reaching a hunt group, the source used is set by the system wide setting or by the Incoming Call Route that
routed the call. If the system has several hold music sources available, this field allows selection of the source to
associate with calls presented to this hunt group or to leave it unchanged. The new source selection will then apply
even if the call is forwarded or transferred out of the hunt group unless changed again by another hunt group.
· Calls overflowing from a hunt group will use the hold music source setting of the original hunt group and ignore
the setting of the overflow group.
· Calls going to night service or out of service fallback group use the hold music source setting of the original hunt
group and then, if different, the setting of the fallback group. The setting of further fallback groups from the first
are ignored.
· Agent's Status on No-Answer Applies To: Default = None (No status change).
For call center agents, that is hunt group members with a log in code and set to forced log in, the system can change
the agent's status if they do not answer a hunt group call presented to them before being automatically presented to
the next available agent.
· This setting defines what type of hunt group calls should trigger use of the agent's Status on No Answer setting.
The options are None, Any Call and External Inbound Calls Only.
· The new status is set by the agent's Status on No Answer (User | Telephony | Supervisor Settings ) setting.
· This action is only applied if the call is unanswered at the agent for the hunt group's No Answer Time or longer. It
does not apply if the call is presented and, before the No Answer Time expires, is answered elsewhere or the caller
disconnects.
· This option is not used for calls ringing the agent because the agent is in another group's overflow group.
·
· User List
This is an ordered list of the users who are members of the hunt group. For Sequential and Rotary groups it also sets
the order in which group members are used for call presentation.
· Repeated numbers can be used, for example 201, 202, 201, 203, etc. Each extension will ring for the number of
seconds defined by the No Answer Time before moving to the next extension in the list, dependent on the Hunt
Type chosen.
· The check box next to each member indicates the status of their membership. Group calls are not presented to
members who have their membership currently disabled. However, those users are still able to perform group
functions such as group call pickup.
· The order of the users can be changed by dragging the existing records to the required position.
· To add records select Edit. A new menu is displayed that shows available users on the left and current group
members of the right. The lists can be sorted and filtered.
163
350
283 283