Networked hunt groups provide hunt group functionality across a network or cluster.
The controller of a network hunt group must be running Release 7.0 or later software.
A remote hunt group member is one that is not either a primary or secondary device on the hunt group host. These remote members must be accessed via trunks that use DPNSS signaling (T1/E1 DPNSS, XNET, or IP trunks). Access via QSIG signaling is not supported.
Only hunt groups with hunt group type "Voice" can be networked.
Uniform Call Distribution (UCD) hunt groups cannot be networked. RADs should not be programmed against voice hunt groups with remote members, and remote members should not be programmed against voice hunt groups with RADs.
Valid members of a network hunt group include:
local stations or broadcast groups
remote directory numbers (RDNs)
system speedcall numbers.
Remote members are programmed in the hunt group as RDNs or system speed call digits. Voice terminals in another vendor's network are valid network hunt group members (programmed as system speed call digits).
If another call arrives to a network hunt group that is already being hunted, the new call proceeds through the member list in parallel with the existing call(s) to the group.
If using terminal hunting for a hunt group, place the local members at the beginning of the member list.
If using circular hunting for a hunt group, alternate local and remote members as much as possible. Avoid long sequences of remote members, one after the other, in a circular group. This configuration can take longer to present a call to an available agent.
The RDN must be the correct device type for the hunt group (station or broadcast group). If an RDN is deleted from the Remote Directory Assignment form, it is also deleted from any hunt groups to which it belongs.
Speedcall members whose ARS routes do not translate to supported trunk types will not be called as Hunt Group candidates. If a system speed call is deleted from the System Speed Call Assignment form, it is also deleted from ay hunt groups to which it belongs.
Campon and Callback are not allowed to network hunt groups.
When a user performs a transfer to a Network Hunt Group, there may be a short delay before the Release softkey appears in the set display. The Release softkey is not presented until a free member is found.
An attendant cannot release a caller to a busy network hunt group (because Campon is not allowed to a hunt group that has one or more remote members).
If a 5550 IP console attendant transfers a call to a Network Hunt Group, the attendant cannot retrieve the call while the system is hunting the group for an idle member. After the call begins ringing an idle member, the attendant can retrieve the call from the Transferred Call queue. If all members in the Network Hunt Group are either busy or do not answer (before the Call Forward - No Answer Timer expires) the attendant console is recalled.
On the local controller, SMDR functions the same for network hunt groups as it does for local hunt groups. If the remote members are hosted on systems with Release 7.0 or later software, SMDR logs are only recorded on the controller that hosts the network hunt group. However, if the network hunt group contains remote members that are hosted on systems with pre-Release 7.0 software, SMDR logs will also be generated on the remote system. In this case, additional logs will be generated for incoming calls that are answered, busy, or unavailable (no answer).
If RDN Synchronization is supported in the cluster, you can add, delete, or change (renumber) directory numbers that are members of cluster call pickup groups from the User Configuration form.
If
OPS Manager is used in your cluster to manage the element telephone directories,
then you must use the OPS Manager Moves, Adds, and Changes (MAC) application
to add, delete, or change (renumber) directory numbers that
are members of network hunt groups. Do not use the User Configuration,
Single-Line Assignment, Multiline Assignment, or Wireless Set Assignment
forms in the System Administration Tool to change a directory number that
is a remote member of a network hunt group if OPS Manager is managing
the cluster telephone directories.
To change the directory number of a device that is a network hunt group
member using OPS Manager:
Delete the member from the network hunt group through OPS MAC, or from the Hunt Group Assignment form of the element's System Administration Tool.
Change (renumber) the directory number from the OPS MAC application.
Perform an OPS Manager synchronization to distribute the change to the cluster elements.
Add the directory number to the network hunt group through OPS MAC or through the Hunt Group Assignment form on the local element.
If you change a directory number without first removing the member from the network hunt group, and then perform an OPS Manager synchronization, the remote elements that host the network hunt group will not be updated with the change by the OPS Manager synchronization. An OPS Manager sync error "delta" is generated on OPS Manager to alert you that the change was not made on the remote element.
To correct:
Log into the element identified in the error log.
Remove the member from the network hunt group.
Perform a synchronization operation from OPS Manager to distribute the remote directory number updates to the cluster element.
Add the renumbered remote member back into the network hunt group of the local element.
SMDR logs are generated at the hunt group controller switch and at the remote member switch after a remote member answers the call. A log is generated at the hunt group controller switch in the following format:
01/25 07:59P 0000:00:04 16130 22216130 16716 A X9999 161 16116130 A1610013 A
A similar log is generated for the incoming call at the remote member switch. For examples of SMDR logs, see Local and Network_Hunt_Group_SMDR_Examples.
Also refer to the Dialed Call Pickup Conditions.
Also refer to the Hunt Group Conditions.
To create a network hunt group, in the Hunt Group Assignment form:
Create a Hunt Group with the proper type (Voice).
Program the COS (Day, Night1, and Night2) for the Hunt Group. You must program the COS fields in the Hunt Group Assignment form before you can add remote members to the Hunt Group.
Add members (local and remote) to the Hunt Group.
Notes:
If two local Hunt Groups (on two different controllers) have the same pilot number, you must adjust the local programming before you merge the members into a single group. The Hunt Group must be deleted from one controller, and the members of that group must be manually added to the Hunt Group on the other controller.
Because Camp-on feature is not available to network hunt groups, ensure that you configure busy call handling for all network hunt groups.
None.