® MultiVOIP Voice/Fax over IP Gateways Configuration Guide for MultiVOIP Units deployed with TM Avaya Communication Manager Models: MVP-130/210/410/810-AV
Configuration Guide S000299G Analog MultiVOIP Units Models MVP-130/210/410/810-AV for use with AvayaTM Communication 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.
CONTENTS VOICE/FAX OVER IP GATEWAYS ................................................................................................. 1 CHAPTER 1 - INTRODUCTION ....................................................................................................... 4 About This Manual .................................................................................................................................................................. 4 MultiVOIPs in Avaya Communication Manager Systems ............
Chapter 1 - Introduction Chapter 1 - Introduction About This Manual MultiVOIP models (MVP130-AV, MVP130-AV-FXS, MVP210-AV, MVP410-AV, & MVP810-AV) being used in systems containing Avaya PBX units and controlled by AvayaTM 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.
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.
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.
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 1 2 3 4 5 6 7 8 RTP Port 5006 5016 5026 5036 5046 5056 5066 5076 RTCP Port 5007 5017 5027 5037 5047 5057 5067 5077 T38 Port 5008 5018 5028 5038 5048 5058 5068 5078 The TCP ports used by the MultiVOIP are as follows: H.
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.
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.
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.
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.
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.
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.
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.
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.
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? Service Type Group Type Carrier Medium =y = tie = ISDN = IP/H.323 5h. To accommodate the MultiVOIP unit, all of the MultiVOIP’s FXO channels must be listed as trunkgroup members in the Communication Manager Trunk Group form (“Change Trunk-Group” dialog box).
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.
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.
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? Service Type Group Type Carrier Medium =n = tie = ISDN = IP/H.323 6g. To accommodate the MultiVOIP unit, all of the MultiVOIP’s DID channels must be listed as trunkgroup members in the Communication Manager Trunk Group form (“Change Trunk-Group” dialog box).
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.
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.
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.
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.
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.
Chapter 2 - Configuration 8b. Click the Add button to add an Outbound Phone Book entry. The Add/Edit Outbound Phone Book screen will be displayed. 8c. Enter the digit pattern 9763 in the Destination Pattern field. Enter the digit 9 in the Remove Prefix field Enter a description in the Description field for information purposes only. Enable the Use Gatekeeper option and enter Minneapolis-FXO in the Gateway H.323 ID field. The Gateway H.
Chapter 2 – Configuration 8d. Go to the MultiVOIP’s Phone Book | Phone Book Modify | Outbound Phone Book | List Entries screen and click the Add button to add another Outbound Phone Book entry for the 612 area code. Enter the digit pattern of 9612 in the Destination Pattern field. Enter the digit 9 in the Remove Prefix field. 8e. Add additional Outbound Phone Book entries for calls to the 651 and 952 exchanges as indicated in the screens below: 26 Multi-Tech Systems, Inc.
Chapter 2 - Configuration 8f. Add an Outbound Phone Book entry to handle the routing of 911 emergency calls to the FXO trunk. Since 911 must be dialed out the FXO trunk, leave the Remove Prefix field blank. Multi-Tech Systems, Inc.
Chapter 2 – Configuration 8g. The completed Outbound Phone book now includes the entries added in the earlier steps. Note: For gatekeeper survivability mode, the Inbound Phone book is not used. 8h. Click on Save Setup | Save and Reboot to save the Outbound Phone Book entries. 9. Dialing examples for gatekeeper survivability mode. 9a. Gatekeeper Survivability dialing example #1: A local station to local IP phone call.
Chapter 2 - Configuration 9c. Gatekeeper Survivability dialing example #3: Incoming Central Office call to station 6011. In this case, the Autocall feature has been enabled in the Voice/Fax screen of the MultiVOIP for the FXO trunk channels. The Autocall Phone Number field has been set to 6011. A call from the Central Office line rings in to the MultiVOIP’s FXO trunk. The MultiVOIP goes off hook on its FXO tip/ring loop-start interface.
Chapter 2 – Configuration Regional Parameters screen The main distinguishing feature of the Regional Parameters screen for Avaya Communication Manager MultiVOIPs is the addition of the survivability dial tone. 1. Set the Survivability Tone in the Configuration|Regional Parameters screen. 2. The Regional Parameters screen will appear. For the country selected, the standard set of frequency pairs will be listed for dial tone, busy tone, ‘unobtainable’ tone (fast busy or trunk busy), and ring tone. 3.
Chapter 2 - Configuration “Regional Parameter” Definitions Continued Description Field Name Values Gain 2 gain in dB +3dB to –31dB and “mute” setting Amplification factor of higher frequency of pair. This applies to the dial, ring, busy, and ‘unobtainable’ (fast busy) tones that the MultiVOIP outputs as audio to the FXS, FXO, or E&M port.
Chapter 2 – Configuration The Custom Tone-Pair Settings fields are described in the table below. Custom Tone-Pair Settings Definitions 32 Field Name Values Description Tone Pair dial tone, busy tone, ring tone, ‘unobtainable’ tone, survivability tone, re-order tone Identifies the type of telephony signaling tone for which frequencies are being specified. TONE PAIR VALUES About Defaults: US telephony values are used as defaults on this screen.
Chapter 3 – Related MultiVOIP Setup Parameters Chapter 3 – Related MultiVOIP Setup Parameters For your convenience, the Communication Manager Settings, MultiVOIP Voice/Fax, Interface, and Gatekeeper parameters are detailed in this section. Communication Manager Settings In the Communication Manager Settings screen, if the “Register with Communication Manager Gatekeeper option is selected, then many of the parameters must assume default values and those will be grayed on the screen.
Chapter 3 – Related MultiVOIP Setup Parameters Communication Manager Parameter Definitions Continued Field Name Values Description Q.931 Parameters Use Fast Start Y/N Enables the H.323 Fast Start procedure. If “Register with Communication Manager Gatekeeper” is enabled, this field defaults to “N” and cannot be changed. Call Signaling Port port number This value must be unique for each of the MultiVOIP’s FXS ports.
Chapter 3 – Related MultiVOIP Setup Parameters Field Name Communication Manager Parameter Definitions (cont’d) Values Description RAS Time to Live Numeric (in seconds) Enable Survivability Mode Y/N Switching Time Interval numeric (in seconds) Q.931 Multiplexing (Mux) Y/N H.245 Tunneling (Tun) Y/N Parallel H.245 (FS + Tun) Y/N Annex –E (AE) Y/N The MultiVOIP sends this value to CM in the Registration Request (RRQ).
Chapter 3 – Related MultiVOIP Setup Parameters Voice/Fax Parameters In each field, enter the values that fit your particular network. 36 Multi-Tech Systems, Inc.
Chapter 3 – Related MultiVOIP Setup Parameters Note that Voice/FAX parameters are applied on a channel-by-channel basis. However, once you have established a set of Voice/FAX parameters for a particular channel, you can apply this entire set of Voice/FAX parameters to another channel by using the Copy Channel button and its dialog box. To copy a set of Voice/FAX parameters to all channels, select “Copy to All” and click Copy. The Voice/FAX Parameters fields are described in the tables below.
Chapter 3 – Related MultiVOIP Setup Parameters Voice/Fax Parameter Definitions Continued Field Name Values DTMF Parameters Description DTMF Gain -- DTMF Gain, High Tones DTMF Gain, Low Tones Duration (DTMF) +3dB to -31dB & “mute” +3dB to -31dB & “mute” 60 – 3000 ms The DTMF Gain (Dual Tone Multi-Frequency) controls the volume level of the DTMF tones sent out for TouchTone dialing. Default value: -4 dB. Not to be changed except under supervision of MultiTech’s Technical Support. Default value: -7 dB.
Chapter 3 – Related MultiVOIP Setup Parameters Voice/Fax Parameter Definitions Continued Field Name Values Coder Parameters (cont’d) Description Selected Coder Select from a range of coders with specific bandwidths. The higher the bps rate, the more bandwidth is used. The channel that you are calling must have the same voice coder selected. Default = G.723.1 @ 6.3 kbps, as required for H.323. Here 64K of digital voice are compressed to 6.
Chapter 3 – Related MultiVOIP Setup Parameters Field Name Values Voice/Fax Parameter Definitions Continued Description AutoCall/Offhook Alert Parameters Auto Call / Offhook Alert AutoCall, Offhook Alert The AutoCall option enables the local MultiVOIP to place a call without the user having to dial a number. As soon as you access the local MultiVOIP voice/fax channel, the MultiVOIP immediately connects to the remote endpoint identified in the Phone Number box of this option.
Chapter 3 – Related MultiVOIP Setup Parameters Voice/Fax Parameter Definitions (cont’d) Field Name Values Description Dynamic Jitter (cont’d) Minimum Jitter Value 60 to 400 ms Maximum Jitter Value 60 to 400 ms Optimization Factor 0 to 12 The minimum dynamic jitter buffer of 60 milliseconds is the minimum delay that would be acceptable over a low jitter network. Default = 150 msec The maximum dynamic jitter buffer of 400 milliseconds is the maximum delay tolerable over a high jitter network.
Chapter 3 – Related MultiVOIP Setup Parameters Interface Parameters In each field, enter the values that fit your particular network. 42 Multi-Tech Systems, Inc.
Chapter 3 – Related MultiVOIP Setup Parameters The kinds of parameters for which values must be chosen depend on the type of telephony supervisory signaling or interface used (FXO, E&M, etc.). We present here the various parameters grouped and organized by interface type. Note that Interface parameters are applied on a channel-by-channel basis.
Chapter 3 – Related MultiVOIP Setup Parameters FXS Loop Start Parameters. The parameters applicable to FXS Loop Start are shown in the figure below and described in the table that follows. Field Name FXS (Loop Start) FXS Loop Start Interface: Parameter Definitions Values Description Y/N Enables FXS Loop Start interface type. Dialing Options fields Inter Digit Timer 1 - 10 seconds This is the length of time that the MultiVOIP will wait between digits.
Chapter 3 – Related MultiVOIP Setup Parameters Field Name FXS Loop Start Interface: Parameter Definitions (cont’d) Values Description Flash Hook Options fields Generation -- not applicable to FXS interface Detection Range for Min. and Max., 50 - 1500 milliseconds For a received flash hook to be regarded as such by the MultiVOIP, its duration must fall between the minimum and maximum values given here.
Chapter 3 – Related MultiVOIP Setup Parameters FXO Parameters. The parameters applicable to the FXO telephony interface type are shown in the figure below and described in the table that follows.
Chapter 3 – Related MultiVOIP Setup Parameters FXO Interface: Parameter Definitions (cont’d) Field Name Values Description FXO Disconnect On (cont’d) Disconnect Tone Sequence 1st tone pair + 2nd tone pair These are DTMF tone pairs. Values for first tone pair are: *, #, 0, 1-9, and A-D. Values for second tone pair are: none, 0, 1-9, A-D, *, and #. The tone pairs 1-9, 0, *, and # are the standard DTMF pairs found on phone sets.
Chapter 3 – Related MultiVOIP Setup Parameters Call is received here. CID Flow CID CID Terminating VoIP FXS IP Network xxxyyyzzzz J.Q. Public Display shows: Generating VoIP Clock: 5-31, 1:42pm FXO Central Office with standard telephony Caller ID service Call originates here at 1:42pm, May 31. xxxyyyzzzz J.Q. Public phone of: H.
Chapter 3 – Related MultiVOIP Setup Parameters CID Flow Call is received here. CID CID FXS Terminating VoIP xxxyyyzzzz J.Q. Public Clock: 10/03, 4:51pm Display shows: Generating Ch1 401 VoIP IP Network Ch2 402 Ch3 403 Ch4 * Call originates here at 4:51pm, Oct 3. FXS xxxyyyzzzz J.Q. Public phone of: Nigel Thurston 763-555-9401 404 H.323 Protocol CID Number: 423 CID Name: Anoka-Whse-VP3 Time Stamp: Date: 10/03 Time: 4:51pm Phone Book Configuration Gateway Name: Anoka-Whse-VP3 Q.
Chapter 3 – Related MultiVOIP Setup Parameters DID Interface Parameter Definitions Field Name Values Description Interface DID-DPO Enables the customer-premises side of DID functionality DID Options Start Modes MultiVOIP’s use of DID applies only for incoming DID calls. The Start Mode used by the MultiVOIP must match that used by the originating telephony equipment, else DID calls cannot be completed.
Chapter 3 – Related MultiVOIP Setup Parameters GK General Settings The fields in the main gatekeeper screen, the GK General Settings screen, must be configured as shown below. Field Name Values Registration Policy GK General Settings Definitions Description No Endpoints Y/N When selected, sets a policy whereby the Gatekeeper accepts no registrations.
Chapter 3 – Related MultiVOIP Setup Parameters Click on the Memory Setting button to access the Memory screen. The configurable fields must be configured as shown below. Field Name Values GK Memory Values GK General Settings Definitions (cont’d) Description Maximum Calls 10, 20, 30 The maximum number of concurrent calls. MVP210AV support 5 calls; MVP410 AV supports 10 calls; MVP810 AV supports 15 calls.
Chapter 3 – Related MultiVOIP Setup Parameters Gatekeeper – Endpoints When an endpoint registers with the gatekeeper, the endpoint is activated. That is, it becomes an acknowledged participant on the network (or on a particular zone of a network). Registration tells the gatekeeper that the endpoint is active and ready to receive calls. An endpoint’s registration can be static (essentially permanent) or dynamic (timed or conditional).
Chapter 3 – Related MultiVOIP Setup Parameters Field Name Type Values Undefined. The endpoint type . When an endpoint attempts to register with the Gatekeeper, the Gatekeeper compares the endpoint type with the predefined value. If the Gatekeeper detects a discrepancy, the registration is not accepted. If you are not sure of the endpoint type, select Undefined, which allows any endpoint of any type to register with the Gatekeeper. (Multipoint Control Units, MCUs, are used to facilitate conference calls.
Chapter 3 – Related MultiVOIP Setup Parameters Gatekeeper - Calls The fields of the Current Calls screen are described in the table below. The Calls window displays a list of all the calls currently taking place and the basic details of the calls: Field Name No Values numeric Current Calls Field Definitions Description Number. A sequential number for identification in the list. ORIG IP n.n.n.n 0-255 Originating IP Address. IP Address of endpoint originating the call.
Chapter 3 – Related MultiVOIP Setup Parameters A Call Details screen for a call in progress can be launched either by clicking on the “Call Details” button for a selected call in the Current Calls screen, or by double-clicking on a selected call listed in the Current Calls screen. The Call Details screen contains general information about the call, as well as details about the call’s source endpoint and destination endpoint.
Chapter 3 – Related MultiVOIP Setup Parameters Field Name Values Call General Info (cont’d) Total BW Conf. Goal State Call Details Field Definitions (Cont’d) Description Reason The total amount of bandwidth used by the call. The type of conference request: create, invite or join. The last reported state of the call. The reason associated with the last state of the call. Field Name Call Details Field Definitions (Cont’d) Description Values Source Info fields Names Phone Numbers The H.
Chapter 3 – Related MultiVOIP Setup Parameters Call Details Field Definitions (Cont’d) Field Name Values Description Destination Info fields 58 Names The H.323 alias name used to make the call. Phone Numbers The e164 alias phone number used to make the call. Other Aliases: Email An e-mail address used to make the call. OtherAliases: Trans. Name A transport name alias used to make the call, consisting of an IP address and port number. Other Aliases: URL A URL alias used to make the call.
Chapter 3 – Related MultiVOIP Setup Parameters Gatekeeper – Network Parameters The fields of the Network Parameters screen must be configured as shown below. Field Name Values Status Information Network Parameter Definitions Description Use Update button to refresh the Status Information fields. Ongoing Calls number The number of current calls with the Gatekeeper. Currently Registered number The number of endpoints registered with the Gatekeeper.
Chapter 3 – Related MultiVOIP Setup Parameters Network Parameter Definitions (cont’d) Field Name Values Pre-Granted ARQ PreGrant Y/N ALL Description Select to cause the Gatekeeper to send a pregrantedARQ permission in the RCF message for each endpoint that wishes to register. The pregranted ARQ permission is given to both makeCall and answerCall with routed mode. When an endpoint receives the permission, it may start the call with a Setup message or directly answer the call with a Connect message.
Chapter 3 – Related MultiVOIP Setup Parameters Network Parameter Definitions (cont’d) Field Name Values Call Mode Description Direct Mode Sets the call mode to direct. In this mode, terminals send ARQ messages to the Gatekeeper, but pass the call signaling and media control signaling directly between them. Routed Mode Sets the call mode to routed. In this mode, terminals pass admission requests and call signaling through the Gatekeeper. Media control information is sent directly between the terminals.
Chapter 3 – Related MultiVOIP Setup Parameters Network Parameter Definitions (cont’d) Field Name Values Configuration Parameters (Cont’d) Description Call IRQ Interval The interval, in seconds, between IRQ messages sent by the Gatekeeper to query the status of calls. IRQ messages are sent to all online endpoints registered as dynamic and having ongoing calls in order to verify that the calls are still ongoing.
Chapter 3 – Related MultiVOIP Setup Parameters Gatekeeper - Services The fields of the Services screen are described in the table below. Field Name Values GK Defined Services Services Screen Definitions Description Prefix A prefix that identifies the service. Description A description of the service that is accessible by dialing the prefix. See “GK Defined Service Types” section on following pages. Default For any GK-defined service being used, the user must select either “Default” or “Public.
Chapter 3 – Related MultiVOIP Setup Parameters Field Name Values V2 GW Prefixes Services Screen Definitions (cont’d) Description H.323 Version 2 enables the gateway to specify prefixes that the user should dial before the WAN number in order to make a call using a certain medium. E.g., the user could dial the prefix 3 for voice calls or 77 for H.320 video calls. The prefixes are defined in the RRQ message at registration. Prefix can be any H.323 alias, including an H.323 ID & mail address.
Chapter 4 - Miscellaneous Chapter 4 - Miscellaneous Gateway Survivability Mode A customer may wish to have some ports on the MultiVOIP gateway not be managed by CM, but rather have them directly routed over a private IP WAN to a second MultiVOIP gateway at the side of the WAN network. An example of this would be to send a T.38 fax call over the private IP WAN network to a fax port on a second MultiVOIP gateway. Create phonebook entries for optional gateway survivable mode (if chosen).
Chapter 4 – Miscellaneous The Inbound Phonebook will be configured as illustrated in the table below. Inbound Destination Pattern: Filter & Remove this Prefix Add Prefix 6001 6002 6003 6004 6005 6006 9303 9303 9720 9720 Channel to direct call toward 303 303 720 720 1 2 3 4 5 6 7 8 7 8 Comm Mgr Dialing Example #1: A local station-to-station call 1. The station at FXS port #1 goes off hook and received the survivable dial tone from the MultiVOIP gateway. The client then proceeds to dial “6002”. 2.
Chapter 4 - Miscellaneous Remote Configuration Remote configuration provides procedures for viewing or changing the configuration of a remote MultiVOIP. Remote configuration requires the MultiVOIP software to be loaded on the local PC. The local PC then controls the remote MultiVOIP. To accomplish this, a MT5634ZBA modem is included with your MultiVOIP, except on models MVP130-AV and MVP130-AV-FXS.
Chapter 4 – Miscellaneous 7. 8. 9. 10. 11. 12. 13. 68 In the Dial String box, enter the AT command for dialing (atdt) plus the phone number of the remote MultiVOIP. Click OK when you are satisfied with your selections. Run the MultiVOIP Configuration program. Click Start|Programs| MultiVOIP 9.06.XX Configuration. The Dialing dialog box displays while software is dialing the remote MultiVOIP. The Reading Setup dialog box displays. The MultiVOIP main menu displays.
Chapter 4 - Miscellaneous Information The System Information screen displays version and addressing information on your MultiVOIP. The System Information screen is a display information screen with such information as Firmware Version level, MAC Address, and Serial Number which can be helpful in identifying your unit when contacting Technical Support. Boot Version: This field displays the version of the boot code running on the MultiVOIP.
Chapter 4 – Miscellaneous Note: It is possible for the hardware revision printed on the packaging label and PCB (printed circuit board) to be higher than what is displayed in the Hardware ID field in the System Information screen. In these cases, the features supported are the same as listed for the displayed Hardware ID above. For example, a MVP810-AV may have Revision C printed on the packaging label and PCB, but display “MVP810-AV Rev B” in System Information.
Chapter 4 - Miscellaneous Link Management The Link Management screen allows you to ping a remote system by entering the IP address of the remote unit in the IP Address to Ping field. The Link Status window displays the results of the ping. Each ping test sends a user configurable number of pings to the remote unit. Configure the Time Interval between Tests field to the number of minutes (0-30) to wait between each ping test. If this field is set to 0, only one ping test is performed.
Chapter 4 – Miscellaneous Feature Issues 72 1. Calling Party Number is not displayed on the Caller ID for FXS ports after receiving a call via CM. This is due to CM not sending the Calling Party Number to the MultiVOIP as part of the Q.931 setup message. 2. “Unknown Name” is displayed on the Caller ID for FXS ports after receiving a call from a MultiVOIP FXO port that was routed by CM. This is due to CM sending “Unknown Name” in the Display field of the Q.
Index Index Accepts Calls option (Gatekeeper General Settings screen) ..... 51 accessing Call Details (gatekeeper) screen ............................... 56 accessing Current Calls (gatekeeper) screen ............................. 55 accessing Endpoints (gatekeeper) screen .................................. 53 accessing Network Parameters (gatekeeper) screen.................. 59 accessing Services (gatekeeper) screen..................................... 63 Add endpoints command (gatekeeper) ...............
Index G.727 .................................................................................... 39 G.729 .................................................................................... 39 Net Coder ............................................................................. 39 Coder field analog ................................................................................... 38 Coder Parameters field group analog ...................................................................................
Index analog ................................................................................... 39 echo, removing analog ................................................................................... 39 Enable Survivability Mode field, Comm Mgr Parameters screen ............................................................................................. 35 endpoint types, gatekeeper........................................................ 54 error correction, forward analog ...........................
Index gatekeeper Call Signalling IP field (Call Details, Destination Info)...................................................................................... 58 gatekeeper Call Signalling IP field (Call Details, Source Info) 57 gatekeeper Cid Sum field (Call Details) ................................... 56 gatekeeper Conf. Goal field (Call Details)................................ 57 gatekeeper Configuration Options field ....................................
Index analog ................................................................................... 38 Input Gain field analog ................................................................................... 37 Inter Digit Regeneration Time (FXO) field .............................. 46 Inter Digit Regeneration Time (FXS Loop Start) field ............. 44 Inter Digit Timer (dialing) field DID-DPO ............................................................................. 50 FXS Loop Start .................
Index Phone Number/ Extension field ................................................ 34 Phone Number/Extension (Comm Mgr Params field) & Extension (Station) field FXS ...................................................................................... 12 Phone Numbers gatekeeper field (Call Details, Destination Info) ............................................................................................. 58 Phone Numbers gatekeeper field (Call Details, Source Info) ... 57 polling, IRQ ...............
Index Unregister button, Comm Mgr Parameters screen .................... 34 Unregister endpoints command Gatekeeper ........................................................................... 54 Update button (gatekeeper Network Parameters) ..................... 62 URQ Unregister Request messages (gatekeeper, H.225) .......... 54 Use Fast Start (Q.931) field ...................................................... 34 V2 GW Prefixes field (gatekeeper, Services) ...........................
