370
Chapter 43 VoIP trunk gateways
Local gateway settings include:
•
fallback to circuit switched availability and scope
•
type of call signaling, either directly to the far end system or through a network gatekeeper
•
if there is a gatekeeper, the relevant IP information is noted
•
a KeepAlive signal timer
•
the protocol the system will use for the gateway (must be compatible with remote system or
gatekeeper)
•
allowing/disallowing VoIP gateway tunnel H.245 messages within H.225
•
being able to identify unique call signaling and RAS ports
Notes about NPI-TON aliases for H.323 trunks
NPI-TON aliases store dialed number prefixes as well as information about the type of number. A
dialed number can be qualified according to its TON (type of number), as well as its NPI
(numbering plan identification). Nortel recommends this format over the E.164 format, for
encoding dialed numbers and aliases registered with a gatekeeper.
When using a gatekeeper, and attempting to place an outgoing VoIP trunk call, ensure that the
route and dialing plan configuration matches the NPI-TON aliases registered, by the destination,
with the gatekeeper. These requirements are summarized in
Table 79 Route and Dialing Plan configurations for NPI-TON
Route (DN
type)
Public
Private
Routing Table
Since VoIP trunks are point-to-point channels, besides the local gateway information on your
system, you need to tell your system about the gateway at the remote end.
However, if the network has a gatekeeper or a SIP Proxy Server, it handles call traffic, so a routing
table is not required.
To configure a remote gateway, you need to define the following information:
•
a name that identifies the destination system
NN40020-603
NN40020-603
Dialing Plan used by calling
gateway
Public
Private (Type = None)
Private (Type = CDP)
Private (Type = UDP)
Table
79.
Alias configured for calling gateway
("alias name" in Element Manager)
PUB:<dialedDigitsPrefix>
PRI:<dialedDigitsPrefix>
CDP:<dialedDigitsPrefix>
UDP:<dialedDigitsPrefix>