Résumé du contenu de la page N° 1
®
MultiVOIP
Voice/Fax over IP Gateways
Configuration Guide for
MultiVOIP Units deployed with
TM
Avaya Communication Manager
Models:
MVP-130/210/410/810-AV
Résumé du contenu de la page N° 2
Configuration Guide S000299G TM Analog MultiVOIP Units Models MVP-130/210/410/810-AV for use with Avaya Communication Manager This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi- Tech 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 merc
Résumé du contenu de la page N° 3
CONTENTS VOICE/FAX OVER IP GATEWAYS ................................................................................................. 1 CHAPTER 1 - INTRODUCTION ....................................................................................................... 4 About This Manual .................................................................................................................................................................. 4 MultiVOIPs in Avaya Communication Manager Sy
Résumé du contenu de la page N° 4
Chapter 1 - Introduction Chapter 1 - Introduction About This Manual MultiVOIP models (MVP130-AV, MVP130-AV-FXS, MVP210-AV, MVP410-AV, & MVP810-AV) being used TM in systems containing Avaya PBX units and controlled by Avaya Communication Manager software 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 Mult
Résumé du contenu de la page N° 5
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
Résumé du contenu de la page N° 6
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 screen within the MultiVOIP program. If “Register with Communication Manager 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,
Résumé du contenu de la page N° 7
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 follo
Résumé du contenu de la page N° 8
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
Résumé du contenu de la page N° 9
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 MultiV
Résumé du contenu de la page N° 10
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
Résumé du contenu de la page N° 11
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
Résumé du contenu de la page N° 12
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, s
Résumé du contenu de la page N° 13
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 t
Résumé du contenu de la page N° 14
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
Résumé du contenu de la page N° 15
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
Résumé du contenu de la page N° 16
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 MVP
Résumé du contenu de la page N° 17
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
Résumé du contenu de la page N° 18
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 Commu
Résumé du contenu de la page N° 19
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 M
Résumé du contenu de la page N° 20
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
