Server User Manual

232 Install and configure IP Trunk 3.01 (and later) node
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.
When an IP Trunk 3.01 (or later) node is configured as an ESN5 node and a
call is received from a remote node that cannot send ESN5 data and does
not provide the ESN5 data, the configured ESN5 prefix is inserted in front of
the called number by the destination. (The remote node can be an IP Trunk
3.01 (or later) or other gateway using the interoperability format. It can also
be "H.323 only".) When the IP Trunk 3.01 (or later) node is configured to
use standard signaling and the dialing plan entry indicates ESN5 capability,
the ESN5 prefix is inserted in front of the called number by the originator.
For more information see "Non-Gatekeeper-resolved (local) dialing plan"
(page 319).
Special dial 0 ESN translations
Special dial 0 ESN translations are not supported on IP Trunk 3.01 (and
later) trunks because they are not leftwise-unique.
Use IP Trunk 3.01 (and later) route as first choice for Group 3 fax
The IP Trunk 3.01 (and later) gateway supports Group 3 fax modems by
means of T.38 protocol.
Nortel Communication Server 1000
IP Trunk Fundamentals
NN43001-563 02.01 Standard
Release 5.5 21 December 2007
Copyright © 2007, Nortel Networks
.