Avaya Communication Manager Administrator's Manual page 1571

Hide thumbs Also See for Communication Manager:
Table of Contents

Advertisement

Send All Calls
If a station activates Send All Calls with the Send All Calls button, then calls to the hunt group extension
go in queue if there is a queue, otherwise callers get a busy treatment if all the agents have their Send All
Calls pushed.
NOTE:
If an extension is an ACD split agent as well as a hunt-group member, the split agent
normally has an AUX-work button that also activates/deactivates Hunt Group Busy. If an
agent presses the Send All Calls button, the agent becomes unavailable for hunt-group
calls. The agent then can become available for calls again by pressing the Send All Calls
button again.
Call Forwarding All Calls
With Call Forwarding All Calls active, an extension within a hunt group is unavailable for hunt-group
calls. Callers hear the hunt group's forced first announcement, if administered, before the system
forwards the call.
Considerations
Members assigned to multiple hunt groups
An extension can be a member of more than one hunt-group. However, a phone, even a
multiappearance phone, can receive only one hunt group call at a time. On a multiappearance
phone, all appearances must be idle to receive a hunt-group call.
You can assign a Coverage Incoming Call Indicator (ICI) button to a multiappearance phone or
attendant console. When a member receives a call for the hunt group associated with the ICI
button, the button's status lamp lights.
ACD agents as hunt group members
Do not include ACD split agents in non-ACD hunt groups if they also receive ACD split calls.
The system distributes all ACD calls to split agents before it distributes hunt-group calls.
When you change an ACD split to a non-ACD hunt group, each split agent must enter the Hunt
Group Busy deactivation code in order to receive calls in that hunt group. If the agent has an
AUX-work button, the button lamp lights when you make the change. The agent can then press
the button to become available for hunt-group calls.
Hunt group for communications devices
Members of a hunt group used for shared data communications must be of the same type. Thus,
you can put data modules or analog modems in a hunt group, but not both. Option settings must
be the same for all group members.
A caller can still use the Data Extension button to access the associated data module, even if the
module is in a hunt group. Individual data modules or modems can originate and receive calls.
Access restrictions
You can restrict, via the Class of Restrictions (COR), any extension in a hunt group from
receiving calls other than those to its assigned hunt group. You can also restrict extensions on
Communication Manager from calling the hunt group's extension.
System limits
The size of your system determines how many hunt groups you can set up and how many
extensions you can assign to each group.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Hunt groups
1571

Advertisement

Table of Contents
loading

Table of Contents