Instruction manual

System Features
INTER-TEL
®
5000 ADMINISTRATOR GUIDE – Issue 2.3, September 2007
Maintenance of Node-Spanning Hunt Groups
Page 135
The ACD Wrap-Up functions apply the following prioritization method for hunt groups with
remote members:
• The first criterion is priority level. The hunt group with the highest priority gets the
available agent first.
• In the event of a tie in priority, hunt groups located locally take priority over those
located on remote nodes.
• In cases where ties in priority occur within the local node, the hunt group with the long-
est camped on call will receive the available agent.
• Given off-node ties in priority, the first hunt group to camp on will receive the available
agent.
Maintenance of Node-Spanning Hunt Groups
• Deletion of an ACD agent from a hunt group is done from the node on which the hunt
group resides or from a remote node.
– If an agent is deleted on the node containing hunt group(s) of which he is a member,
then the agent is removed from all hunt group(s) on that node and is logged out.
– If the agent is deleted from a remote node, the agent is logged off from that node,
but remains a member of any hunt group(s) located on other nodes.
• If the hunt group is deleted, all remotely logged-in endpoints will be logged out.
• If the extension number of an ACD Hunt Group is changed, any local or remote end-
points that are logged in will reflect the change. If links are down at the time of the
change, remote nodes will not receive the change and an import/export process will be
necessary to update the information on the affected nodes.
• Removing an Agent ID from a hunt group agent list logs out any endpoint, local or
remote, that is logged in to that hunt group using that Agent ID.
• With the node-spanning features of ACD hunt groups, changing Agent IDs can be done
from two possible locations: on the node where the group resides or on a node where
the logged-in endpoint resides.
– When changing an Agent ID on the node where the hunt group resides, the remotely
logged-in endpoint using that Agent ID will be logged out even though the Agent
ID still exists on the remote node. The hunt group will then contain the new Agent
ID in its removed list, making the new Agent ID available for log-in use.
– When changing an Agent ID on the node on which the logged-in endpoint resides (a
node remote from the hunt group), the remote member will be logged out and the
old Agent ID will no longer exist on that node. The hunt group on the original node
will contain the old Agent ID in its removed list, because this ID still exists on that
node.
• During a database restore on a node containing ACD hunt groups that use Agents IDs,
all Agents IDs are placed into each hunt group’s removed list. All endpoints will be
logged out during the restore.
• When the extension number of a logged-in endpoint is changed, the new extension will
be logged in with the same Agent ID and will not be disconnected. This applies to end-
points logged in both remotely and locally.