Instruction manual

Page 1686 of 3156 Hunting
553-3001-306 Standard 10.00 January 2002
When Linear Hunting is implemented, the system searches for an available
trunk in descending order. A station originating an outgoing call is connected
to the last available trunk (highest available trunk route member number) of
the trunk route accessed. The last trunk route member is always the first
choice for outgoing calls and the first trunk route member is always the last
choice.
Round Robin Trunk Hunting
Outgoing calls are evenly distributed among the members of a trunk route.
When a station originates an outgoing call, the system searches for an
available trunk route member in descending order, starting with the next
lower member number from the last trunk seized for an outgoing call on the
trunk route. If a trunk with a lower member number is not available, the
system searches for a trunk starting with the highest member number of the
route.
Note for multiple group machines using Round Robin Trunk
Hunting:
To minimize system resource usage, the Meridian 1 will attempt to hunt to an
available trunk within the same group as the originating TN. For example, if
a call is placed from a telephone whose TN is in group 1, the system will first
attempt to locate an available trunk within group 1. If there are no available
trunks in group 1, the system selects an available trunk from another group.
Each time hunting occurs, the round robin index value, which points to the
next route member to be examined, is updated. Because the proximity of a
trunk loop to the originating TN loop takes precedence over the order of the
trunk route members, the system may be forced to hunt through many route
members to locate an available trunk within a given group. This can cause the
round robin index to change dramatically, yielding inconsistent trunk usage
patterns.
If uniform trunk usage is a prime concern, configure route members with
alternating groups. For example, if a given route contains trunk members
from different groups, alternate the groups so that route member 1 is a trunk
member from group 1, route member 2 is a trunk member from group 2, and
so on. This configuration will produce more uniform trunk usage than would
occur if trunks of the same group were bunched together within a route.