Server User Manual

Configure dialing plans within the corporate network 231
The time schedule is a 24-hour clock which is divided up the same way
for all 7 days. Basic steps to program Time of Day for IP Trunk 3.01 (and
later) routes are as follows:
1. Go to LD 86 ESN data block to configure the Time of Day Schedule
(TODS) for the required IP Tr unk 3.01 (and later) control periods.
2. Go to LD 86 RLB and apply the TODS on/off toggle for that route list
entry associated with an IP Trunk 3.01 (and later) trunk route.
ESN5 network signaling
The original ITG-T ISDN application had two major categories of endpoints:
• ISDN-capable endpoints
•
Non-ISDN endpoints
ESN5 information transmission is a mechanism allowing the transmission
of NCOS information. ESN5 digit transmission was added when the ISDN
capability was added to ITG Trunks. ITG Trunk ISDN endpoints were
able to insert the ESN5 prefix in an outgoing message if necessary, and
did so based on the information in the dialing plan tables. This was the
only possible alternative, since the flag indicating the type of ESN5 prefix
and the two prefix digits were also legitimate dialed digits. Non-ISDN
endpoints were, by definition, unable to handle ISDN, and therefore were
not ESN5-capable.
IP Trunk 3.01 (or later) and ITG Trunk 2.x support a mixed network of remote
nodes with ESN5 and standard (non-NCOS broadcasting) signaling.
ESN5 inserts the NCOS prefix ahead of the dialed numbers. If ESN5
signaling is to be used, it must be provisioned on both the IP Trunk cards
and the Meridian 1/CS 1000 M Route Data Block (RDB) for that node.
However, this does not guarantee a satisfactory NCOS value. For example,
the network may contain some ITG Trunk 1.0 basic trunk signaling nodes
or other IP telephony gateways that use H.323 V2 instead of SL-1 (MCDN)
signaling, and therefore do not support ESN5. An ESN5 node that
interworks with one of these non-ESN5, non-ISDN IP telephony gateways
and can receive an H.323 SETUP from them must have the default ESN
prefix correctly provisioned.
The application defaults to an NCOS of "0". If this is unsatisfactory, you
must configure an ESN5 prefix for the non-ESN5 IP telephony gateways by
using the CLI command esn5PrefixSet at the ITG shell on all IP Trunk
cards in the ESN5 node. To verify the default ESN5 value that will be added
for all incoming calls from non-ESN5 IP telephony gateways, use the CLI
command esn5PrefixShow at the ITG shell.
Nortel Communication Server 1000
IP Trunk Fundamentals
NN43001-563 02.01 Standard
Release 5.5 21 December 2007
Copyright © 2007, Nortel Networks
.