Configuring a hunt group for sna subscribers, Configuring a hunt group for sna subscriber, Systematic redirection – Cabletron Systems 1800 User Manual
Page 142: Redirect on busy, Redirect on out of o rder, Connecti on priori ty, 1st, 2nd,etc. path configured, Port, Redirection address 0, 1,etc
9-16
SmartSwitch 1800 4. 0 User G uide, Rev 01
Systematic Redirection
will redirect (if
Y
) all calls to the alternate subscribers specified by the Redirection
Addresses. Consecutive attempts at call redirection will be made to each alternate sub-
scriber in the list, until the call is completed.
Redirect on Busy
will redirect calls (if
Y
) according to the Redirection Addresses if the primary sub-
scriber device is busy.
Redirect on Out of Order
will redirects calls (if
Y
) according to the Redirection Addresses if the primary sub-
scriber device is out of order.
Connection Priority
prioritizes intra-nodal traffic; the higher the number, the higher the priority. (This pri-
ority has no effect on traffic exiting a node.)
Priorities are configured on all logical interfaces that use a physical frame relay port.
The device processor in the node uses these priorities to help determine the order in
which it will process protocols.
When configuring priorities, be careful to consider the types of
traffic being routed on other connections in the node.
1st, 2nd,etc. Path Configured
includes or excludes the associated port as a routing path to the subscriber device. At
least one path must be specified.
Port
identify the port(s) that make up the routing path(s).
Redirection Address 0,1,etc.
are up to five subscribers that will be called according to the specified redirection
option.
Configuring a Hunt Group for SNA Subscribers
. The function has some special requirements
for SNA routing:
●
Each SNA port in a routing path must have a unique network address, even if it
will not be used explicitly by the routing table.
●
Configure two ports as SNA HPADs, one (called HPAD1 for this list) with
Round Robin specified and one or more routing paths configured, and the other
port (HPAD2) with any routing algorithm but only one routing path.
●
The Port parameters for each port specified in the Routing Paths of each HPAD
must contain a Remote Subscriber ID for any TPAD that might call either
HPAD. (The Remote Subscriber ID in the HPAD's Port configuration is the
Local Subscriber ID in the TPAD's Port configuration.)
●
Include HPAD2 in HPAD1's routing path.