Nortel Networks NN43001-563 - Manual (Page 230)

230 Install and configure IP Trunk 3.01 (and later) node
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.
If ESN5 is provisioned for an IP Trunk 3.01 (or later) node (both in the RDB
and on the node cards), you must configure that node as "SL1 ESN5" in the
dialing plan for all other ITG 2.x and IP Trunk 3.01 (or later) nodes. If these
other nodes are also ESN5-capable, when originating a call they will pass
the ESN5 prefix that they receive in the messages from the Meridian 1 to
the destination node. Otherwise, a default NCOS is inserted by a non-ESN5
node sending the SETUP to the ESN5 destination. Only when the originator
is not ISDN-capable is a default NCOS inserted by the ESN5 node receiving
the call from the non-ESN5 VoIP gateway.
IP Trunk 3.01 (or later) nodes that are to support ESN5 signaling are
configured in TM 3.1 at the ITG Node Properties window, in the Configuration
tab in the Protocol field. Select SL1 ESN5 from the drop-down list.
There are three possible scenarios where ESN5 prefixes are inserted:
1. A non-ESN5-compatible node calling an ITG Trunk 2.x node or calling
an IP Trunk 3.01 (or later) node provisioned in the dialing plan table as
SL1 ESN5. In this case, the originator inserts the ESN5 prefix.
2. Remote nodes calling an ESN5 IP Trunk 3.01 (or later) node using the
Nortel interoperability non-standard data format, if the originating call
does not use ESN5. In this case, the destination (IP Trunk or IP Peer)
inserts the ESN5 prefix.
3. Remote nodes calling an ESN5 IP Trunk 3.01 (or later) node that does
not support the MCDN protocol, since MCDN includes ESN5 capability.
In this case, because the ISDN data is missing, the receiving node can
identify that ESN5 data is required.
Nortel Communication Server 1000
IP Trunk Fundamentals
NN43001-563 01.01 Standard
Release 5.0 30 May 2007
Copyright © 2007, Nortel Networks
.