9-16 Smart Switch 1800 4. 0 User Guide , Rev 0 1
Syste mat i c Re di re ct io n
will redirect (if Y) all calls to the alternate subscribers specified by the Redirection
Addresses. Consecutive attempts at ca ll 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-
scribe r device is busy .
Redirect on Out of Order
will redirects calls (if Y) according to the Redirection Addresses if the primary sub-
scribe r device is out of order .
Connection Priori ty
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).
Redire cti o n Addres s 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
Hunt gr oups are de s cri b e d on page 8-22. The function has some special requirements
for SNA routin g:
●Each SNA port in a routing path mus t have a unique netwo rk 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 R ob i n s pec i f ie d a nd one or more ro ut i n g pa ths conf i gu re d , a nd th e ot her
port (HPAD2) with any routing algorithm but only one routing path.
●The Port parameters for each port specified in the Routin g 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.