Multitech MVP103, MVP130-AV-FXS, MVP130-AV Configuration Manual
MultiVOIP®
Voice/Fax over IP Gateways
Configuration Guide for
MultiVOIP Units deployed with
Avaya
TM
Communication Manager
Models:
MVP-130/210/410/810-AV
Configuration Guide
S000299H
Analog MultiVOIP Units Models MVP-130/210/410/810-AV for use with Avaya
Manager
This publication may not be reproduced, in whole or in part, without prior expressed written permission from MultiTech Systems, Inc. All rights reserved.
Copyright © 2008, by Multi-Tech Systems, Inc.
Multi-Tech Systems, Inc. makes no representations or warranties with respect to the contents hereof and specifically
disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, Multi-Tech
Systems, Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof
without obligation of Multi-Tech Systems, Inc. to notify any person or organization of such revisions or changes.
Record of Revisions
Revision Date Description
A 04/25/03 Initial Release.
B 06/19/03 Manual revised to include name change to Avaya Communication Manager.
C 08/20/03 Manual revised to include IP Phone Survivability. Software Vs 9.05.28
D 12/26/03 Manual revised to correct IP Phone and FXS port configuration. Software Vs 9.05.28 for
MVP210/410/810-AV and software Vs 2.04.17 for MVP130.
E 05/10/04 Manual revised for software version 9.06.xx. Added support for additional voice coders, DID,
Caller ID remote ping feature, off-hook alerting, and audible message waiting.
F 12/07/04 Manual revised to include editorial comments.
G 06/26/08 Manual revised to include support for 16xx and 96xx IP Phone Modules, in addition to the
46xx series. This update documents VOIP Software Version 9.06.DV or higher.
H 02/23/09 Manual revised to include support for IP phone 4622 and VOIP software version 2.06 for
MVP130-AV
Patents
This Product is covered by one or more of the following U.S. Patent Numbers: 6151333, 5757801, 5682386, 5.301.274;
5.309.562; 5.355.365; 5.355.653; 5.452.289; 5.453.986. Other Patents Pending.
Trademark
Trademark of Multi-Tech Systems, Inc. is the Multi-Tech logo. Windows and NetMeeting are registered trademarks of
Microsoft. Avaya is registered trademark of Avaya Inc.
TM
Communication
World Headquarters
Multi-Tech Systems, Inc.
2205 Woodale Drive
Mounds View, Minnesota 55112
(763) 785-3500 or (800) 328-9717
Fax: 763-785-9874
http://www.multitech.com
Technical Support
Country By Email By Phone
Europe, Middle East, Africa support@multitech.co.uk +(44) 118 959 7774
U.S., Canada, all others support@multitech.com (800) 972-2439 or +(763) 717-5863
CONTENTS
VOICE/FAX OVER IP GATEWAYS ................................................................................................. 1
CHAPTER 1 - INTRODUCTION ....................................................................................................... 4
About This Manual .................................................................................................................................................................. 4
MultiVOIPs in Avaya Communication Manager Systems ...................................................................................................... 4
CHAPTER 2 - CONFIGURATION .................................................................................................... 6
Configuring MultiVOIP for Avaya Communication Manager Use ......................................................................................... 6
Regional Parameters screen .......................................................................................................................... 30
CHAPTER 3 – RELATED MULTIVOIP SETUP PARAMETERS .......................................................... 33
Communication Manager Settings ................................................................................................................ 33
Voice/Fax Parameters ..................................................................................................................................... 36
Interface Parameters ...................................................................................................................................... 42
GK General Settings ....................................................................................................................................... 51
Gatekeeper – Endpoints ................................................................................................................................. 53
Gatekeeper - Calls ........................................................................................................................................... 55
Gatekeeper – Network Parameters................................................................................................................ 59
Gatekeeper - Services .................................................................................................................................... 63
CHAPTER 4 - MISCELLANEOUS .................................................................................................. 65
Gateway Survivability Mode ................................................................................................................................................. 65
Remote Configuration ........................................................................................................................................................... 67
Information ............................................................................................................................................................................ 69
Link Management ............................................................................................................................................ 71
Feature Issues ........................................................................................................................................................................ 72
Chapter 1 - Introduction
About This Manual
Chapter 1 - Introduction
MultiVOIP models (MVP130-AV, MVP130-AV-FXS, MVP210-AV, MVP410-AV, & MVP810-AV) being used
in systems containing Avaya PBX units and controlled by Avaya
differ only slightly from those being used in general voice-over-IP applications. Because this is so,
comprehensive information on the general setup of these MultiVOIP units can be found in the MultiVOIP
User Guide. However, certain MultiVOIP parameters are unique to operation in Communication Manager
systems. This manual describes these parameters.
TM
Communication Manager software
Beyond general setup information (like Mechanical Installation, & Cabling, LED definitions, and other
general info which are presented in the MultiVOIP User Guide & Quick Start Guide), this software guide
presents all the information you need to configure your MultiVOIP for use in a Communication Manager
system. It presents information on the MultiVOIP software screens as well as the related Communication
Manager screens. The MultiVOIP User Guide remains valuable as a reference source.
MultiVOIPs in Avaya Communication Manager Systems
The Communication Manager build of the MultiVOIP software allows for use of MultiVOIP units in
conjunction with IP-equipped Avaya PBX units. These PBXs are equipped with H.323 gatekeeper
functionality and support endpoints such as IP phones and MultiVOIP gateways.
In addition to functioning as a gateway, the MultiVOIP also contains an integrated gatekeeper, except
MVP130 Models. This allows the MultiVOIP to serve as it’s own alternate gatekeeper should
Communication Manager be unavailable. When serving as an alternate gatekeeper, the MultiVOIP
processes registration and call routing for it’s local FXS/FXO/DID ports as well as local Avaya IP phones.
This is the MultiVOIP’s “gatekeeper survivability” mode.
Each MultiVOIP voice channel can be registered with a primary Communication Manager gatekeeper or
one of two optional alternate gatekeepers. The optional gatekeepers can be other Communication Manager
gatekeepers or the integrated MultiVOIP gatekeeper.
The diagram below shows a common function for the MultiVOIP unit within the Communication Manager
network: the MultiVOIP allows selected callers at a site remote from the Avaya PBX units to have access to
the PBX units and all of their extensions without tolls. Voice and fax calls are supported.
4 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 1 - Introduction
Figure 1. MultiVOIP in Avaya Communication Manager System
The MVP810-AV shown in the diagram on the previous page functions as a gateway registered to one of
the Communication Managers in the IP network. The MVP810-AV provides survivable calling between the
IP Phones, stations (FXS) and trunk (FXO/DID) ports at the remote site should the WAN link go down.
The MultiVOIP will not serve as a survivable gatekeeper for IP phones on the other side of the wan link.
If the WAN link goes down, the MultiVOIP will try to register six times with the Primary Communication
Manager Gatekeeper at 3-second intervals. If the Primary gatekeeper does not respond, the MultiVOIP will
try to register with the Alternate #1 Communication Manager Gatekeeper six times at 3-second intervals. If
the alternate #1 gatekeeper does not respond, the MultiVOIP will register with the Alternate #2 gatekeeper,
which is the integrated MultiVOIP gatekeeper. If the MultiVOIP registers to its own gatekeeper, this is
gatekeeper survivability mode where the MultiVOIP will process registration and call routing for its local
FXS/FXO/DID ports as well as local Avaya IP phones.
While in gatekeeper survivability mode, the MultiVOIP checks for the availability of the primary
Communication Manager gatekeeper every 3-minutes. The MultiVOIP will re-register and discontinue its
survivability mode automatically when the primary Communication Manager gatekeeper becomes
available. Any calls that were established during the "survivable mode" which are still active while the
MultiVOIP gateway returns to "subtending mode" to the CM gatekeeper, shall be preserved by the
MultiVOIP gatekeeper. When these calls become inactive (idle), the MultiVOIP gatekeeper shall force these
endpoints to unregister with the MultiVOIP gatekeeper and re-register with the CM gatekeeper.
If the MultiVOIP is not configured as an alternate gatekeeper, and none of the Primary, Alternate #1, or
Alternate #2 CM gatekeepers respond, the MultiVOIP will enter gateway survivable mode (if enabled) and
will process calls according to it’s inbound and outbound phone books. In gateway survivable mode, the
MultiVOIP will check for the availability of the primary Communication Manager gatekeeper according to
the Switching Time Interval programmed into the Communication Manager Parameters screen of the
MultiVOIP configuration. The MultiVOIP will exit gateway survivability mode if it is able to register with
the Primary CM gatekeeper. Gateway survivability mode is enabled by checking the “Enable Survivability
Mode” checkbox in the Communication Manager Parameters screen. If IP phone survivability is required,
you must enable gatekeeper survivability mode instead by configuring the MultiVOIP as one of the
alternate #1 or alternate #2 gatekeepers.
The following Avaya IP Phone models are supported in gatekeeper survivable mode:
4601 4602 4606 4610 4612 4620 4621 4622 4624 4625
9610 9620 9630 9640 9650
1603 1608 1616
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 5
Chapter 2 – Configuration
Chapter 2 - Configuration
Configuring MultiVOIP for Avaya Communication Manager Use
To configure the MultiVOIP unit within such a system (similar to that in Figure 1), use the Communication
Manager Parameters
Gatekeeper” is selected, then many parameters must assume default values and those will be grayed out on
the screen. In setting up the MultiVOIP unit for Communication Manager use, bear in mind that you may
configure the MultiVOIP to operate with any combination of stations (FXS) and/or trunks (FXO/DID).
1. Configure IP Parameters
1a. Configure the IP address, gateway address, and mask used by the MultiVOIP unit in the
Configuration |IP Parameters screen of the MultiVOIP program. The IP address must match that
used in the Communication Manager “Change Node Names IP” form (dialog box).
1b. DiffServ PHB (Per Hop Behavior) values pertain to a differential prioritizing system for IP packets
as handled by DiffServ-compatible routers. There are 64 values, each with an elaborate technical
description.
purposes, in RFC3246, which describes the value 34 (34 decimal; 22 hex) for Assured Forwarding
behavior (default for Call Control PHB) and the value 46 (46 decimal; 2E hexadecimal) for
Expedited Forwarding behavior (default for Voip Media PHB).
If you wish to use just one DiffServ PHB value, Ayaya recommends the value 46 (46 decimal; 2E
hex) for both Call Control and VOIP Media.
screen within the MultiVOIP program. If “Register with Communication Manager
These descriptions are found in TCP/IP standards RFC2474, RFC2597, and, for present
1c. If you require that the MultiVOIP get its IP address from a DHCP server, select the “Enable DHCP”
option. The DHCP server must be located at the same site as the MultiVOIP so it is available in the
event of wan link failure. The DHCP server must issue an IP address that is statically defined on
the DHCP server so that the MultiVOIP gets the same IP address all the time.
1d. TDM Routing Option. Calls placed between ports on the same MultiVOIP voice channel board
will normally be routed over the MultiVOIP’s internal TDM (Time Division Multiplexed) bus. TDM
calls have less delay than calls routed over IP. On MVP410/810-AV models, calls between channels
1-4 or channels 5-8 will be TDM routed. Calls between voice boards (for example, channel 1 calling
channel 5) will be IP routed. If you require all calls to be IP routed, disable the “use TDM Routing
for Intra-Gateway Calls” option. This should not normally be required, so it is recommended that
you leave TDM Routing enabled.
6 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
1e. TCP/UDP port requrements. To ensure proper functioning of the MultiVOIP, the TCP/UDP
network connection must not be blocked on the network connection between the MultiVOIP and
CM.
The UDP ports used by the MultiVOIP are as follows:
Channel RTP Port RTCP Port T38 Port
1 5006 5007 5008
2 5016 5017 5018
3 5026 5027 5028
4 5036 5037 5038
5 5046 5047 5048
6 5056 5057 5058
7 5066 5067 5068
8 5076 5077 5078
The TCP ports used by the MultiVOIP are as follows:
H.225 Listen Port – User configured for each channel in the CM Settings screen (default 1721 –
1728)
H.225 Client Port – Dynamic (16000 – 20000)
H.245 Listen Port – Dynamic (16000 – 20000)
RAS Client Port – Dynamic (16000 – 20000)
1f. Emergency Transfer. Emergency transfer allows local analog telephones to access the local CO and
to answer telephone calls during a power failure.
For the various products the features operate as follows:
MVP210-AV
Port 1 is connected to Port 2
MVP410-AV
Port 1 is connected to Port 2
Port 3 is connected to Port 4
MVP810-AV
Port 1 is connected to Port 2
Port 3 is connected to Port 4
For example, suppose ports 1 and 3 of MVP410-AV are configured as FXS with telephones
attached. Ports 2 and 4 are configured as FXO trunks with CO lines attached. If there is a power
failure, the telephones on ports 1 and 3 would automatically be connected to the CO lines attached
to ports 2 and 4 allowing inbound and/or outbound call to be make.
Note: This feature shall only be available on “AV” models of the gateway that are:
Rev B: For the MVP410 and MVP810 models
Rev B: For the MVP210 model
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 7
Chapter 2 – Configuration
2. Configure Interface Parameters.
2a. Determine which voice channels will be stations (FXS), trunks (FXO/DID), or disabled. Configure
them as such in the
Configuration | Interface screen of the MultiVOIP GUI.
2b. If you are configuring a DID-DPO (Direct Inward Dial – dial-pulse originating) interface for DID
incoming calls, you need to chose DID-DPO from the pull down menu for Interface Type. You also
have to set the DID Options Start Modes; Immediate Start, Wink Start, or Delay Dial.
Immediate Start allows the MultiVOIP to detect the off-hook condition at the originating end of the
call and becomes ready to receive the digits immediately.
Wink Start allows the MultiVOIP to detect the off-hook condition at the originating end of the call.
The MultiVOIP then reverses the battery polarity for a specified time (140-290 ms; a “wink”) and
then becomes ready to receive the dialed digits. You can select the Wink Timer duration (140 to 290
ms).
Delay Dial allows the MultiVOIP to detect the off-hook condition at the originating end of the call.
Then the MultVOIP reverses battery polarity for a specified time (reverse polarity duration has a
wider acceptable range than Wink Start) and then becomes ready to receive dialed digits.
2c. Enable the “Message Waiting Light” feature if you have FXS Interface selected and are using an
Avaya analog telephone with Message Waiting indicator or enable “Stutter Dial Tone” if you are
8 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
using a non-Avaya analog telephone. This station must be properly administered in the Audix
Voice Mail System for the message waiting feature to work.
2d. Activate the “Caller ID” feature if you have FXS Interface selected and are using an analog
telephone with caller ID display. The MultiVOIP will output Caller ID information, if received,
between the first and second rings.
2e. Activate “Caller ID” on FXO interfaces if the attached line supports it. The MultiVOIP will capture
the Caller ID information, if provided, between the first and second rings and will forward the
information to CM.
Note: If the CM customer is operating on CM release 2.0.1 (or newer), remember that for the ‘h323’
specified station, the following CM admin fields must be set appropriately:
a) The ‘Message Waiting’ field must be enabled and set to “led” if this feature is intended to be
supported on the MultiVOIPs analog station port.
b) Similarly, the following features must be enabled as desired:
• Switchhook flash
• Call Waiting Indication
• Attendant Call Waiting Indication
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 9
Chapter 2 – Configuration
3. Configure Voice/Fax Parameters.
3a. In the MultiVOIP’s
Configuration | Voice/Fax Parameters screen, configure the voice channels for a
voice coder that is supported by Communication Manager.
The voice coder selected must match the voice coders listed in the ip-codec-set for the network
region the MultiVOIP resides in. If only G.729 is listed in the ip-codec-set, select G.729 on the
MultiVOIP. If G.711 is listed before G.729 in the ip-codec-set, select G.711, G.729 on the MultiVOIP.
If G729 is listed before G.711 in the ip-codec-set, select G.729, G.711 on the MultiVOIP.
There is one exception, if only G.711 is listed in the ip-codec-set, you must select G.711, G.729 on
the MultiVOIP. This will allow support for G.711 for CM managed calls, and will allow support for
G.729 for survivable mode calls. The MultiVOIP only supports G.729 in survivable mode.
The table below shows the bandwidth required per voice channel based on the codec selected and
the CM “Frames per Packet” setting in the “Change IP-Codec-Set” screen.
Bandwidth per Channel
Voice Frames per IP Packet
Coder 1 2 3 4
G.729 40K bps 24K bps 18K bps 16K bps
G.711 96K bps 80K bps 74.7K bps 72K bps
3b. If the CM customer desires that a particular FXS port is to operate as a “hot extension”, set the
“auto call/off-hook alerting” feature to auto call and enter the desired destination number in the
“phone number” field. Enabling this feature allows an analog phone user to be able to lift his/her
10 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
handset (and without dialing the number) immediately call the far-end party. To prevent toll fraud
on FXO trunk ports, set the “autocall enable” feature and enter the phone number for a receptionist
or auto-attendent.
3c. The MultiVOIP supports off-hook alerting on FXS ports. To enable the feature, set the “auto
call/off-hook alert” feature to “off-hook alert” and enter the destination number in the “phone
number” field. If the user lifts the handset, but does not dial a number, dial tone will be heard for
10 seconds, followed by intercept tone for the number of seconds configured in the “off-hook alert
timer” field. If this timer expires, a call will automatically be placed to the destination number in
the “phone number” field.
4. Configure the station (FXS) channels in the
Communication Manager MultiVOIP: FXS Channels
Communication Manager Parameters screen.
4a. Make sure the “Register with Communication Manager Gatekeeper” option is checked.
4b. Configure Call Signaling Port. This needs to be unique on each registered FXS channel and must
fall within the range of port values supported by Communication Manager. Typically, it is OK to
use the default values 1721-1728 on channels 1-8 respectively.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 11
Chapter 2 – Configuration
4c. Configure Gateway Name (optional). This is the name that gets displayed when viewing Call
Progress statistics for this channel. If used, the MultiVOIP’s Gateway Name must match the
name used in the Communication Manager “Node-Names IP” form.
4d. Configure Phone Number / Extension. This must match the extension configured for this station
in the Communication Manager “station” form. If “ Message Waiting Indicator” is required for this
extension, set this option to “led” in the CM “station” form.
12 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
Note that, in page 2 of the Communication Manager “Station” form, the “Direct IP-IP Audio
Connection” field must be set to “y” and the “IP Audio Hairpinning” field must be set to “n.”
4e. Configure Security Code. This must match the security code configured in the Communication
Manager “Station” form (see first graphic in step 4d).
4f. Configure Primary Gatekeeper IP Address. This must be configured to match the IP address of the
CLAN or PROCR card in the “IP Node Names” form of the primary CM gatekeeper. Do not
change the RAS port from the default 1719 and leave the Gatekeeper Name field blank.
4g. Configure IP addresses for Alternate Gatekeeper 1 and Alternate Gatekeeper 2 (optional). These
must be configured to match the IP address of the respective CLAN or PROCR card in the PBX unit
serving as the Alternate Gatekeeper. This field appears in IP Node Names form of the
Communication Manager software for that PBX. If you are using the MultiVOIP Gatekeeper as an
alternate gatekeeper, enter the IP address of the MultiVOIP. The alternate MultiVOIP gatekeeper
must appear after any Communication Manager alternate gatekeepers.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 13
Chapter 2 – Configuration
5. Configure trunk (FXO) channels in the Communication Manager Parameters screen.
Communication Manager MultiVOIP: FXO Channels
5a. Make sure the “Register with Communication Manager Gatekeeper” option is checked.
14 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
5b. Configure Call Signaling Port. Unlike station (FXS) ports, which require a unique value for each
channel, trunk (FXO) ports require that the same Call Signaling Port value be used on all trunk
(FXO) ports that are registered to the same Communication Manager PBX. Configure this to a
unique value that is not being used by another station (FXS) or trunk (DID) port on this MultiVOIP
unit. This port value must fall within the range of port values supported by Communication
Manager and should match the “Far-end Listen Port” value configured in the Communication
Manager “Signaling Group” (“Display Signaling Group”) form (dialog box). All FXO ports on this
MultiVOIP will use the same Signaling Group for communication with the CM Server.
Note that several other fields in the Communication Manager “Signaling Group” form (dialog box)
must be set to accommodate operation with the MultiVOIP:
Group Type = h.323
Remote Office? = n
RRQ Required? = y
Direct IP-IP Audio Connection? = y
IP Audio Hairpinning? =n
Calls Share IP Sig Connection =y
5c. Configure Delay before Dial value. This is the delay after the MultiVOIP goes off hook before it
dials a number to the attached PSTN line. Some PSTN lines may require more than the default 400
ms value. Configure as appropriate for the PSTN lines you are using. If you are not sure, leave the
default value in place.
5d. Configure Gateway Name. This should match the value configured for this MultiVOIP unit in the
Communication Manager “IP Node Names” and “Signaling Group” forms.
5e. Configure Primary Gatekeeper IP Address. This must be configured to match the IP address of the
CLAN or PROCR card in the “IP Node Names” form of the primary Communication Manager
Gatekeeper unit. Do not change the RAS Port and leave the Gatekeeper name field blank.
5f. Configure IP addresses for Alternate Gatekeeper1 and Alternate Gatekeeper 2 (optional). These
must be configured to match the IP address of the respective CLAN or PROCR card in the PBX unit
serving as the Alternate Gatekeeper. This field appears in IP Node Names form of the
Communication Manager software for that PBX. If you are using the MultiVOIP Gatekeeper as an
alternate gatekeeper, enter the IP address of the MultiVOIP. The alternate MultiVOIP gatekeeper
must appear after any Communication Manager alternate gatekeepers.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 15
Chapter 2 – Configuration
5g. To accommodate the MultiVOIP unit, the following fields in the Communication Manager “Trunk
Group – Page 1” form must be set as shown:
Dial Access? = y
Service Type = tie
Group Type = ISDN
Carrier Medium = IP/H.323
5h. To accommodate the MultiVOIP unit, all of the MultiVOIP’s FXO channels must be listed as trunk-
group members in the Communication Manager Trunk Group form (“Change Trunk-Group” dialog
box).
For example, if four channels of an MVP810-AV are configured as FXO, four trunk group numbers
must be listed, as above.
16 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
6. Configure trunk (DID) channels in the Communication Manager Parameters screen.
Communication Manager MultiVOIP: DID Channels
6a. Make sure the “Register with Communication Manager Gatekeeper” option is checked.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 17
Chapter 2 – Configuration
6b. Configure Call Signaling Port. Unlike station (FXS) ports, which require a unique value for each
channel, trunk DID ports require that the same Call Signaling Port value be used on all DID trunk
ports that are registered to the same Communication Manager PBX. Configure this to a unique
value that is not being used by another station (FXS) or trunk (FXO) port on this MultiVOIP unit.
This port value must fall within the range of port values supported by Communication Manager
and should match the “Far-end Listen Port” value configured in the Communication Manager
“Signaling Group” (“Display Signaling Group”) form (dialog box). All DID trunk ports on this
MultiVOIP will use the same Signaling Group for communication with the CM Server.
Note that several other fields in the Communication Manager “Signaling Group” form (dialog box)
must be set to accommodate operation with the MultiVOIP:
Group Type = h.323
Remote Office? = n
RRQ Required? = y
Direct IP-IP Audio Connection? = y
IP Audio Hairpinning? = n
Calls Share IP Sig Connection =y
6c. Configure Gateway Name. This should match the value configured for this MultiVOIP unit in the
Communication Manager “IP Node Names” and “Signaling Group” forms.
6d. Configure Primary Gatekeeper IP Address. This must be configured to match the IP address of the
CLAN or PROCR card in the “IP Node Names” form of the primary Communication Manager
Gatekeeper unit. Do not change the RAS Port and leave the Gatekeeper name field blank.
6e. Configure IP addresses for Alternate Gatekeeper1 and Alternate Gatekeeper 2 (optional). These
must be configured to match the IP address of the respective CLAN or PROCR card in the PBX unit
serving as the Alternate Gatekeeper. This field appears in IP Node Names form of the
Communication Manager software for that PBX. If you are using the MultiVOIP Gatekeeper as an
alternate gatekeeper, enter the IP address of the MultiVOIP. The alternate MultiVOIP gatekeeper
must appear after any Communication Manager alternate gatekeepers.
18 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
6f. To accommodate the MultiVOIP unit, the following fields in the Communication Manager “Trunk
Group – Page 1” form must be set as shown:
Dial Access? = n
Service Type = tie
Group Type = ISDN
Carrier Medium = IP/H.323
6g. To accommodate the MultiVOIP unit, all of the MultiVOIP’s DID channels must be listed as trunk-
group members in the Communication Manager Trunk Group form (“Change Trunk-Group”
dialog box).
For example, if four channels of an MVP810-AV are configured as DID, four trunk group numbers
must be listed, as above.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 19
Chapter 2 – Configuration
7. Configure MultiVOIP gatekeeper (except for the MVP130 Models) to provide survivability to IP phones
and local FXS/FXO/DID ports.
If you are using Avaya IP phones in addition to the MultiVOIP, you must configure the MultiVOIP
gatekeeper to provide survivability for the IP phones and local FXS/FXO/DID ports in the event of
WAN link failure.
7a. In the MultiVOIP’s Gatekeeper |Endpoints screen, add predefined endpoints to the gatekeeper.
One endpoint entry is required for each FXS port or IP phone. Only one entry is required for one or
more FXO ports per MultiVOIP gateway. Only one entry is required for one or more DID ports per
MultiVOIP gateway.
7b. To add an entry for a MultiVOIP FXS port, configure Endpoint Type, Product ID, Names, Phones,
Registration IP, and Security code fields as indicated below. Configure the Names field with a
unique descriptive identifier. The information contained in the Names and Phones fields will be
used for Caller ID purposes in survivable mode. Configure Phones and Security Code to match the
values configured for this station in Communication Manager. The Registration IP should match
the IP address of the MultiVOIP where the FXS port is located. This could be the IP address of this
very same MultiVOIP or another MultiVOIP. Leave the other fields blank. One entry is required for
each MultiVOIP FXS port that is configured to register with Communication Manager. Click OK to
accept this entry. Repeat the above steps to add additional FXS station port entries.
If the autocall feature is being used to route incoming FXO trunk calls to an extension (1000, etc.,) at
the main site, you can program a second entry in the “Phones” field to 1000 to route incoming FXO
trunk calls to a given FXS station to cover the autocall situation in Gatekeeper Survivable mode.
20 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
7c. To add an entry for MultiVOIP FXO ports, configure Endpoint Type, Product ID, Names,
Registration IP, and Call Signalling Port fields as indicated below. Configure the Names field
with a unique descriptive identifier for the FXO trunk. This same name will be used later to map
Outbound Phone Book entries with specific digit patterns (area codes, etc.) to this FXO trunk, and
for Caller ID purposes in survivable mode. The Registration IP should match the IP address of the
MultiVOIP where the port is located. This could be the IP address of this very same MultiVOIP or
another MultiVOIP. Leave the other fields blank. Only one entry is required for one or more ports
on a given MultiVOIP. For example, if the MultiVOIP has four FXO ports, only one gatekeeper
entry should be added. Click OK to accept this entry.
7d. To add an entry for MultiVOIP DID ports, configure Endpoint Type, Product ID, Names,
Registration IP, and Call Signalling Port fields as indicated below. Configure the Names field
with a unique descriptive identifier for the DID trunk. This name will be used for Caller ID
purposes in survivable mode. The Registration IP should match the IP address of the MultiVOIP
where the DID port is located. This could be the IP address of this very same MultiVOIP or another
MultiVOIP. Leave the other fields blank. Only one entry is required for one or more ports on a
given MultiVOIP. For example, if the MultiVOIP has four DID ports, only one gatekeeper entry
should be added. Click OK to accept this entry.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 21
Chapter 2 – Configuration
7e. To add an entry for an IP phone, configure Endpoint Type, Product ID, Names, Phones, and
Security code fields as indicated below. Configure Phones and Security Code to match the values
configured for this IP phone in Communication Manager. Leave the other fields blank. One entry
is required for each IP phone located at the same site as this MultiVOIP. Do not create entries for IP
phones located at other sites. They will not be able to register with this MultiVOIP in the event of a
wan link failure. Click OK to save this entry. Repeat the above steps to add additional IP phone
entries. The MVP210, MVP410, and MVP810 support 5,10, or 15 IP phones respectively.
The IP phones must be configured to use DHCP and the DHCP server must be located at the same
site as the MultiVOIP and IP phones. This is the only means by which the IP phones are made aware
of alternate gatekeepers, such as the MultiVOIP gatekeeper when the CM is unavailable due to WAN
link failure.
Refer to the following Avaya documents for instructions on how to configure the DHCP server.
● 4600 Series IP Telephone Lan Administrator’s Guide (Avaya document number 555-233-507).
Read the section titled “DHCP” under “Server Administration”.
● Avaya one-x Deskphone Edition for 9600 Series IP Telephones Administrator’s Guide Release
1.5 (Avaya document number 16-300698). Read the section titled “DHCP and File Server”
under “Server Administration”.
● Avaya one-x Deskphone Value Edition 1600 Series IP Telephones Administrator’s Guide
Release 1.0 (Avaya document number 16-601443). Read the section titled “DHCP Server
Administration”.
Your DHCP server must utilize site-specific options (SSON) #176 (46xx models) and/or #242 (16xx,
96xx models) which are IP Telephone-specific DHCP options specifying information such as TFTP
server and Definity CLAN IP address. The MultiVOIP IP address must be listed at the end of the
string. MCIPADD=xxx.xxx.xxx.xxx,yyy.yyy.yyy.yyy where xxx.xxx.xxx.xxx is one or more IP
addresses used for Definity/CM CLAN IP boards and yyy.yyy.yyy.yyy is the MultiVOIP’s IP
address.
22 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Chapter 2 - Configuration
7f. Configure the “Survivable GK Node Name” field with the node name previously given to the
MultiVOIP in the “Node-Names IP” form.
Avaya IP phones running firmware version 2.0 or higher require CM 2.0.1 or higher to work in
survivable mode with the MultiVOIP. When these phones register with the CM, they replace the
list of gatekeepers acquired from the DHCP server (including the MultiVOIP) with a new list of
gatekeepers acquired from CM. This differs from 1.x IP phone firmware where the gatekeeper list
sent to the IP phone from CM was appended to the list of gatekeepers acquired from the DHCP
server. When using CM 2.0.1 or higher, configure the “Survivable GK Node Name” field in the
station form for the IP phone. By doing this, the MultiVOIP will be included in the list of
gatekeepers sent to the IP phone by CM.
Note: IP phone models 4610SW and 4620SW only support 2.0 or higher firmware, therefore these
phones cannot be used with the MultiVOIP unless you are using CM 2.0.1 or higher.
7g. The completed Endpoints screen is shown below:
7h. Click on Save Setup|Save GK Parameters to save the gatekeeper settings.
Multi-Tech Systems, Inc. Avaya Communication Manager Guide 23
Chapter 2 – Configuration
8. Create Outbound Phone Book entries to allow the mapping of digit patterns (area codes, 911 calls, etc)
to FXO trunks during gatekeeper survivable mode.
When a survivable call comes in from the IP network to the MultiVOIP gatekeeper, the MultiVOIP will
search through the Outbound Phone book entries in an attempt to find an entry whose Destination
Pattern matches the first few digits of the destination phone number for the call.
If a match is found, the MultiVOIP will manipulate the digits according to the Remove Prefix and Add
Prefix fields of the Outbound Phone book entry. The call with the manipulated digits will be routed to
the predefined gatekeeper endpoint whose Names entry matches the H.323 ID configured in the
Outbound Phone Book entry. This is the normal sequence for calls to FXO trunks.
If there is no match in the Outbound Phone book, the MultiVOIP gatekeeper will try to find a matching
number in the Phones field of one of the MultiVOIP gatekeeper predefined endpoints. This is the
normal sequence for calls to FXS ports or IP phones.
Suppose the MultiVOIP resides in the 763 exchange of the Minneapolis area with its FXO trunk
connected to PSTN lines. This area has an overlayed area code system where calls to 763, 612, 952, and
651 exchanges are all local calls. In this example, we will add Outbound Phone book entries to allow
calls to phone numbers within these exchanges as well as 911 calling for emergencies.
8a. Go to the MultiVOIP’s Phone Book | Phone Book Modify | Outbound Phone Book | List Entries
screen as seen below.
24 Multi-Tech Systems, Inc. Avaya Communication Manager Guide
Loading...