Considerations for Hunt Groups

Last Updated : Oct 30, 2012 |

This section provides information about how the Hunt Groups feature behaves in certain circumstances. Use this information to ensure that you receive the maximum benefits of the Hunt Groups feature under all conditions.

Members assigned to multiple hunt groups

An extension can be a member of more than one hunt group. However, a telephone, even a multiappearance telephone, can receive only one hunt group call at a time. On a multiappearance telephone, all appearances must be idle to receive a hunt group call.

You can assign a Coverage Incoming Call Indicator (ICI) button to a multiappearance telephone or an attendant console. When a member receives a call for the hunt group that is associated with the ICI button, the status lamp lights.

Automatic Call Distribution (ACD) agents as hunt group members

Do not include agents in an ACD split in non-ACD hunt groups if the agents also receive ACD split calls. The system distributes all ACD calls to agents in a split before the system distributes hunt group calls.

When you change an ACD split to a non-ACD hunt group, each agent in the split must dial the Hunt Group Busy deactivation code to receive calls for that hunt group. If the agent has an AUX-work button, the status 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 that is used for shared data communications must be of the same type. Therefore, you can enter either 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 use Class of Restrictions (COR) to restrict an extension from receiving calls other than those calls to the hunt group to which the extension is assigned. You can also restrict extensions on Communication Manager from calling the extension of the hunt group.

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.

Trunk signaling

A hunt group always has its own extension. Therefore, a caller with a telephone on Communication Manager can dial that extension to call the hunt group. If a trunk group can pass digits from the central office (CO) to Communication Manager, for example, over a DS1 trunk group, a caller can also dial a 7-digit number. The 7-digit number consists of a specified prefix and the extension of the hunt group.

If a trunk group cannot pass digits from the CO to Communication Manager, the system can connect incoming calls to a hunt group only if the trunk group has the hunt group extension as the primary destination. This requirement includes trunk groups for incoming listed directory number (LDN) calls, international exchange calls, 800 service calls, and automatic tie-trunk calls.