Nortel Meridian 1 Administration And Maintenance page 329

Hunting
Hunting allows calls that encounter a busy condition at the original call
destination to be automatically routed to a different destination in a hunt
chain. Hunting continues along a predetermined sequence of DNs in a
hunting group until an idle ISDN BRI or non-ISDN terminal DN is found to
answer the call or until the maximum number of hunt steps is exhausted. The
hunting DNs are defined in the DSL by using Service Change Program
LD 27. Refer to the ISDN BRI line and packet data implementation chapter
of this guide in DSL configuration procedures.
Special hunting for BRI supports calls terminating at a ISDN BRI terminal.
This feature is activated when a call terminating at a DSL encounters a busy
condition and if hunting is enabled. You can configure internal and external
hunt DNs when configuring the DSL.
A busy condition occurs when:
— the maximum number of calls on a DSL exceeds the specified limit of
simultaneous calls on a DSL as defined for MCAL in LD 27, or
— if the total number of calls including active, calls held, calls waiting, and
calls in progress exceed the number of channels configured to handle the
incoming call type
If the call limit on a DSL is not exceeded, an incoming call will be presented
to the DSL interface as a call waiting call.
Hunting is enabled or disabled when configuring the TSP for the ISDN BRI
terminal DN by using Service Change BRI Program LD 27. Refer to the
ISDN BRI line and packet data implementation chapter of this guide in TSP
configuration procedures.
To perform a hunting test:
1 Set the FEAT parameter to HTA to enable hunting for two voice
ISDN BRI terminals.
Specify this parameter when configuring the TSP by using Service
Change BRI Program LD 27. Refer to the ISDN BRI line and packet data
implementation chapter of this guide in TSP configuration procedures.
Option 11C
Chapter 7 — Acceptance testing
ISDN BRI Administration and Maintenance
Page 315 of 492