Server User Manual

230 Install and configure IP Trunk 3.01 (and later) node
interface MAC address; for example: 00:60:38:01:06:C6. To find the ELAN
network interface MAC address, refer to the IP Trunk 3.01 (and later)
Installation Summary Sheet. The ELAN network interface MAC address
is labeled on the IP trunk card faceplate as the "motherboard Ethernet
address." Alternatively, use the ITG shell command "ifShow" to display the
Ethernet address for lnIsa (unit number 0).
Configure dialing plans within the corporate network
Configure the dialing plan by programming LDs 86, 87, and 90 as required.
Configure the Meridian 1/CS 1000M ESN by creating or modifying data
blocks in LDs 86, 87, and 90, as required. The Meridian 1/CS 1000M and
TM 3.1 IP Trunk 3.01 (and later) dialing plan information must correspond.
Make the IP Trunk 3.01 (and later) the first-choice, least-cost entry in
the Route List Block
When adding IP Trunk 3.01 (and later) TIE trunks to an existing ESN,
a common practice is to create a new Route List Block (RLB) for ESN
translations that are to be routed by the IP Trunk 3.01 (and later) network.
Insert the new IP Trunk 3.01 (and later) route ahead of the existing alternate
routes for circuit-switched facilities, which are therefore shifted to the next
higher entry number. Increment the ISET (initial set) if Call-Back Queueing
or Expensive Route Warning tone are being used.
Turn on Step Back on Congestion for the IP Trunk 3.0 (and later) trunk
route
For the IP Trunk 3.01 (and later) trunk route entry in the Route List Block
(RLB), enter RRA at the Step Back on Congestion (SBOC) prompt. This
enables fallback to alternate circuit-switched trunk routes in the following
situations:
•
due to network QoS falling below the defined threshold for the IP Tr unk
3.01 (and later) node
•
when there are no ports available at the destination IP Trunk 3.01 (and
later) node
Turn off IP Trunk 3.01 (and later) route during peak traffic periods on
the IP data network
Based on site data, if fallback routing occurs frequently and consistently
for a data network during specific busy hours (for example, every Monday
10-11am, Tuesday 2-3pm), these hours should be excluded from the RLB
to maintain a high QoS for voice services. By not offering voice traffic to a
data network during known peak traffic hours, the incidence of conversation
with marginal QoS can be minimized.
Nortel Communication Server 1000
IP Trunk Fundamentals
NN43001-563 02.01 Standard
Release 5.5 21 December 2007
Copyright © 2007, Nortel Networks
.