Nortel VoIP Gateway Quick start guide

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 1
Document Addendum V2.1
Norstar VoIP
Gateway Configuration Guide
This addendum describes corrections to the Norstar VoIP Gateway Configuration
Guide.
About Norstar VoIP Gateway
p18 Figure 2 Typical VoIP Gateway Installation
This diagram indicates that the internet is the IP network connecting the gateways
(via routers). The public internet should not be used for this connection. Rather,
the network should be a secure corporate intranet, ideally engineered for voice
quality of service, which could include VPN connections through the public
internet.
Configuring the VoIP Gateway
Configuring the Protocol Definition
p30 Step 4 refers to Table 4 which describes various protocol definition parameters.
The description of the following parameters should be changed as shown below:
p30 Parameter Description
Connection Mode Select Normal if you want the VoIP Gateway to use the Normal
connection mode.
Select Tunneling to have H.245 messages added to H.225
messages during call setup.
Select Fast Start if you want the VoIP Gateway to use the Fast
Start connection mode.
Select Fast Start+Tunneling to combine the two options.
The default value is Fast Start.
The Fast Start connection mode allows a media path to be
established using H.225 without having to start the full H.245
protocol session. In some situations, you need to use fast start
in order to control call progress tones.
Tunneling allows full H.245 session establishment at the same
time that H.225 call setup occurs which can be more efficient
and facilitate interworking with some third party products.

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 2
p30 Parameter Description
Source Number
Encoding Type Select the source number encoding type. This defines the encoding type of the calling phone number in H.225 messages.
You can select E.164, H.323-ID, E.164 & H.323-ID, NPI/TON
from table, or NPI/TON & H.323-ID.
Select NPI/TON from table or NPI/TON & H.323-ID if you want
the gateway to use the values configured in the Tel -> IP
Source Number Manipulation table.
Select H.323-ID or E.164 & H.323-ID or NPI/TON & H.323-ID if
you want the VoIP Gateway to add the H323-ID to the source
information.
Select E.164 if you want the VoIP Gateway to use E.164 source
encoding and not use the encoding type defined in the Tel -> IP
Source Number Manipulation table.
The default value is e.164.
Note: If you select an option that includes “H.323-ID”, you
must enter a string in the H.323-ID box.
Destination Number
Encoding Type Select the destination number encoding type. This defines the encoding type of the called phone number in H.225 setup
messages.
You can select E.164, H.323-ID, E.164 & H.323-ID, NPI/TON
from table.
Select NPI/TON from table if you want the VoIP Gateway to
use the values configured in the Tel -> IP Dest Number
manipulation table.
Select H.323-ID or E.164 & H.323-ID if you want the VoIP
Gateway to add the H323-ID to the destination information.
Select E.164 if you want the VoIP Gateway to use E.164
destination encoding and not use the encoding type defined in
the Tel->IP Dest Number manipulation table.
The default value is E.164.
Note: If you select an option that includes H.323-ID, the H.323-
ID is generated from the string of digits that are dialed and is
added to the destination number as an H.323-ID text string.

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 3
p32 Parameter Description
Gateway Registration
Type Select the registration type you want to use. This defines the encoding type of the Gateway’s phone numbers that is used
when the VoIP Gateway registers these numbers with a
Gatekeeper.
You can select E.164, H.323-ID, E.164 & H.323-ID, NPI/TON
from table, or NPI/TON & H.323-ID.
Select NPI/TON from table or NPI/TON & H.323-ID if you want
the VoIP Gateway to use the values configured in the Gateway
Registration Prefixes Table.
Select H.323-ID or NPI/TON & H.323-IDif you want the VoIP
Gateway to add the H323-ID to the destination information.
Select E.164 if you want the VoIP Gateway to use E.164
encoding and not use the encoding type defined in the table.
The default value is E.164.
Note: If you have entered a string in the H.323 ID box, this
string is added to the gateway registration when you select
H.323-ID, E.164 & H.323-ID, or NPI/TON & H.323-ID.
p40 Step 7 refers to the Save Configuration button. If a reset has been performed, all
changes will be saved to non-volatile memory. The only time that you must click
the Save Configuration button is when changes are made without performing a
reset. Similarly, the Note that follows step 7 should be ignored. When a reset is
performed, all new values are stored in non-volatile memory and are not restored
after a power cycle.

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 4
Configuring the Number Manipulation tables
Configuring number manipulation for Digit Delivery
p51 Parameter Description
Prefix to add Enter the number you want to add to the front of the stripped
destination number.
For example, if you enter 9 and the stripped destination phone
number is 1234, the new destination phone number is 91234.
The prefix can include digits and the following:
• D = wait for dial tone.
You may use D as the first prefix digit so that the VoIP
Gateway will wait for a Norstar dial tone before dialing out
the digits. Dial tone detection can only be used as the first
digit.
• P = pause
Pause inserts a 1.5 second wait period before proceeding
with the remaining digits. It can be used instead of D as the
first digit and may improve call setup time in that case. It
may also be used to wait for any secondary dial tone, such
as might be required for dialing out through the Norstar to
the PSTN. Longer periods may be achieved by using more
than one P character. For example, PP will insert a pause
of 3.0 seconds.
Note: Either D or P should be used at the beginning of the digit
string in order to ensure that the Norstar has enough time to be
ready to receive the digits. Without D or P, the first few digits
may not be reliably dialed.
Configuring number manipulation for Source Phone Numbers
for IP to Norstar calls
p54 Parameter Description
Prefix to add Enter the number you want to add to the front of the stripped
source number.
For example, if you enter 9 and the stripped destination phone
number is 1234, the new source phone number is 91234.

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 5
Configuring number manipulation for Source Phone Numbers
for Norstar to IP calls
p54 Add the following parameter and description to table 9.
Parameter Description
Prefix to add Enter the number you want to add to the front of the stripped
source number.
For example, if you enter 9 and the stripped destination phone
number is 1234, the new source phone number is 91234.
Configuring the Channels to Hunt Group Parameters
p59 Step 7 refers to the Save Configuration button. If a reset has been performed, all
changes will be saved to non-volatile memory. The only time that you must click
the Save Configuration button is when changes are made without performing a
reset. Similarly, the Note that follows step 7 should be ignored. When a reset is
performed, all new values are stored in non-volatile memory and are not restored
after a power cycle.
Configuring the Network Settings
p75 Step 7 refers to the Save Configuration button. If a reset has been performed, all
changes will be saved to non-volatile memory. The only time that you must click
the Save Configuration button is when changes are made without performing a
reset. Similarly, the Note that follows step 7 should be ignored. When a reset is
performed, all new values are stored in non-volatile memory and are not restored
after a power cycle.
Configuring the Channel Settings
p81 Step 7 refers to the Save Configuration button. If a reset has been performed, all
changes will be saved to non-volatile memory. The only time that you must click
the Save Configuration button is when changes are made without performing a
reset. Similarly, the Note that follows step 7 should be ignored. When a reset is
performed, all new values are stored in non-volatile memory and are not restored
after a power cycle.
Configuring the VoIP Gateway time and date
p82 Step 11 refers to the Save Configuration button. If a reset has been performed,
all changes will be saved to non-volatile memory. The only time that you must
click the Save Configuration button is when changes are made without

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 6
performing a reset. Similarly, the Note that follows step 7 should be ignored.
When a reset is performed, all new values are stored in non-volatile memory and
are not restored after a power cycle.
Configuring the VoIP Gateway using the INI file
Retrieving the INI file from the VoIP Gateway
p85 The INI file that is retrieved from the gateway will only include parameters that
have been changed from the default settings.
Contents of the INI File – H.323 Parameters
Table 16 describes various INI file parameters for setting H.323 elements. The
description of the following parameters should be changed as shown below:

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 7
p93 INI File Field Name Valid Range and Description
GWRegistrType The Gateway Registration Type defines the encoding type of
the VoIP Gateway’s phone numbers that are used when the
VoIP Gateway registers these numbers with a Gatekeeper.
0 – E.164 (default)
1 – H.323 ID
2 – E.164 and H.323-ID
3 – NPI/TON from table
4 – NPI/TON & H.323 ID
Select 0 (E.164) if you want the VoIP Gateway to use e164
encoding and not use the encoding in the Gateway Registration
Table.
Select 1, 2 or 4 (H.323-ID) if you want the VoIP Gateway to add
the H323-ID to the destination information.
Select 3 (NPI/TON from table) if you want the VoIP Gateway to
use the values configured in the Gateway Registration Table.
If GWRegistrType = 1, 2 or 4, you must also configure the
H323IDString.
p94 INI File Field Name Valid Range and Description
SourceEncodeMode The Source Number Encoding Type defines the encoding type
of the calling phone number in H.225 setup messages.
0 – E.164 (default)
1 – H.323 ID
2 – E.164 and H.323-ID
3 – NPI/TON from table
4 – NPI/TON & H.323 ID
Select 0 (E.164) if you want the VoIP Gateway to use e164
encoding for the source number and not use the encoding type
defined in the Tel -> IP Source Number manipulation table.
Select 1, 2 or 4 (H.323-ID) is you want the VoIP Gateway to
add the H323-ID to the source information.
Select 3 (NPI/TON from table) if you want the VoIP Gateway to
use the values configured in the Tel -> IP Source Number
manipulation table.
If SourceEncodeMode = 1, 2 or 4, you must also configure the
H323IDString.

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 8
p94 INI File Field Name Valid Range and Description
DestEncodeMode The Destination Number Encoding Type defines the encoding
type of the called phone number in H.225 setup messages.
0 – E.164 (default)
1 – H.323 ID
2 – E.164 and H.323-ID
3 – NPI/TON from table
Select 0 (E.164) if you want the VoIP Gateway to use e164
encoding for the destination number and not use the encoding
type defined in the Tel -> IP Dest Number manipulation table.
Select 1 or 2 (H.323-ID) if you want the VoIP Gateway to add
the H323-ID to the destination information.
Select 3 (NPI/TON from table) if you want the VoIP Gateway to
use the values configured in the Tel -> IP Dest Number
manipulation table.
If DestEncodeMode = 1 or 2 the H.323-ID is generated from
the string of digits that are dialed and is added to the
destination number as an H.323-ID text string.
Configuring the Norstar System
Configuring your Norstar KSU / Required Norstar Hardware
p111 In addition to the hardware requirements indicated in this section, the Norstar
KSU must also have DTMF tone receivers installed in order to use “target line
capability”. Target Lines is the mode used to automatically dial through to the
target set or other line at the destination KSU. In this mode, the Norstar
automatically answers the ringing trunk and presents dial tone to the gateway.
The gateway either detects this dial tone (when using the “D’ parameter in the
Digit Delivery Table) or waits for 1.5 seconds (when using the “P” parameter in
the Digit Delivery Table) and then dials the destination digits into the trunk.
Norstar detects these digits and connects the call through to the required
destination. In order to do this, the Norstar must have DTMF tone receivers
available.
DTMF tone receivers are provided when using any of the following:
1. Services card
2. Combo card
3. E&M trunk card

Norstar VoIP Gateway Configuration Guide Addendum – Version 2.1 9
Configuring a simple Norstar Network
p118 Figure 28 Simple Norstar and VoIP Gateway network
This diagram indicates that the internet is the IP network connecting the gateways
(via routers). The public internet should not be used for this connection. Rather,
the network should be a secure corporate intranet, ideally engineered for voice
quality of service, which could include VPN connections through the public
internet.
Setting up the VoIP Gateway to use a RAD over VoIP trunks
p126 Figure 35 Using a RAD over the VoIP Gateway
This diagram indicates that the internet is the IP network connecting the gateways
(via routers). The public internet should not be used for this connection. Rather,
the network should be a secure corporate intranet, ideally engineered for voice
quality of service, which could include VPN connections through the public
internet.
Setting up the VoIP Gateway for T.38 fax relay
p127 Figure 36 VoIP Gateway with T.38 fax relay
This diagram indicates that the internet is the IP network connecting the gateways
(via routers). The public internet should not be used for this connection. Rather,
the network should be a secure corporate intranet, ideally engineered for voice
quality of service, which could include VPN connections through the public
internet.
Setting up the VoIP Gateway to use a Radvision Gatekeeper
p129 Figure 37 VoIP Gateway with a Gatekeeper
This diagram indicates that the internet is the IP network connecting the gateways
(via routers). The public internet should not be used for this connection. Rather,
the network should be a secure corporate intranet, ideally engineered for voice
quality of service, which could include VPN connections through the public
internet.