230 Install and configure IP Trunk 3.01 (and later) nodeinterface MAC address; for example: 00:60:38:01:06:C6. To find the ELANnetwork interface MAC address, refer to the IP Trunk 3.01 (and later)Installation Summary Sheet. The ELAN network interface MAC addressis labeled on the IP trunk card faceplate as the "motherboard Ethernetaddress." Alternatively, use the ITG shell command "ifShow" to display theEthernet address for lnIsa (unit number 0).Configure dialing plans within the corporate networkConfigure the dialing plan by programming LDs 86, 87, and 90 as required.Configure the Meridian 1/CS 1000M ESN by creating or modifying datablocks in LDs 86, 87, and 90, as required. The Meridian 1/CS 1000M andTM 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 inthe Route List BlockWhen 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 ESNtranslations 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 alternateroutes for circuit-switched facilities, which are therefore shifted to the nexthigher entry number. Increment the ISET (initial set) if Call-Back Queueingor Expensive Route Warning tone are being used.Turn on Step Back on Congestion for the IP Trunk 3.0 (and later) trunkrouteFor 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. Thisenables fallback to alternate circuit-switched trunk routes in the followingsituations:• due to network QoS falling below the defined threshold for the IP Trunk3.01 (and later) node• when there are no ports available at the destination IP Trunk 3.01 (andlater) nodeTurn off IP Trunk 3.01 (and later) route during peak traffic periods onthe IP data networkBased on site data, if fallback routing occurs frequently and consistentlyfor a data network during specific busy hours (for example, every Monday10-11am, Tuesday 2-3pm), these hours should be excluded from the RLBto maintain a high QoS for voice services. By not offering voice traffic to adata network during known peak traffic hours, the incidence of conversationwith marginal QoS can be minimized.Nortel Communication Server 1000IP Trunk FundamentalsNN43001-563 02.01 StandardRelease 5.5 21 December 2007Copyright © 2007, Nortel Networks.
