Multi-Tech Systems MVPFXS-24, MVPFXS-8, MVPFXS-16 User Manual

Download

MultiVOIP FX

FXS-Only SIP Gateways

Models: MVPFXS-8

User Guide for Voice/IP Gateways

MVPFXS-16 MVPFXS-24

User Guide

S000415A

MultiVOIP FX Analog FXS-Only Gateways

(Models MVPFXS-8, MVPFXS-16 & MVPFXS-24)

This publication may not be reproduced, in whole or in part, without prior expressed written permission from Multi-Tech Systems,

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. Check Multi-Tech’s web site for current versions of our product

documentation.

Record of Revisions

Revision Description

A 07/26/06. Initial release. Describes 13.01 software release.

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 is a registered trademarks of Microsoft.

GENERAL CONTACT

Multi-Tech

Systems, Inc. 2205 Woodale Drive Mounds View,

Minnesota 55112, USA (763) 785-3500 (800) 328-9717 Fax: 763-785-9874

www.multitech.com

TECHNICAL SUPPORT

Country By E-mail By Phone

U.S. & Canada tsupport@multitech.com (800) 972-2439

France support@multitech.fr (+33) 1-64 61 09 81

India support@multitechindia.com (+91) 124-340778

U.K. support@multitech.co.uk (+44) 118 959 7774

Rest of World support@multitech.com (763) 785-3500

CONTENTS

CHAPTER 1: OVERVIEW ......................................................................................................................................................5

ABOUT THIS MANUAL ..............................................................................................................................................................6

INTRODUCTION TO ANALOG MULTIVOIP FX SIP FXS-ONLY GATEWAY VOICE-OVER-IP UNITS (MVPFXS-8/16/24) ..........7

MultiVOIP Front Panel LEDs...........................................................................................................................................10

COMPUTER REQUIREMENTS ...................................................................................................................................................11

SPECIFICATIONS .....................................................................................................................................................................11

INSTALLATION AT A GLANCE .................................................................................................................................................12

RELATED DOCUMENTATION ...................................................................................................................................................12

CHAPTER 2: QUICK START GUIDE.................................................................................................................................13

MULTIVOIP STARTUP TASKS ................................................................................................................................................14

Phone/IP Details *Absolutely Needed* Before Starting the Installation...........................................................................15

Gather IP Information........................................................................................................................................................................ 15

Gather Telephone Information ..........................................................................................................................................................15

Config Info CheckList.......................................................................................................................................................................16

Identify Remote VOIP Site to Call.................................................................................................................................................... 16

Command/Control Computer Setup (Specs & Settings) ....................................................................................................17

Placement ..........................................................................................................................................................................17

Quick Hookup for MVPFXS-8/16/24.................................................................................................................................18

Ensure that Java & Browser Versions will Support Web-Ba sed GUI...............................................................................19

Changing the IP Address through the Console Connection..............................................................................................19

Phone/IP Starter Configuration.........................................................................................................................................26

Phonebook Starter Configuration (with remote voip)........................................................................................................27

Outbound Phonebook ........................................................................................................................................................................ 27

Inbound Phonebook........................................................................................................................................................................... 30

Phonebook Tips .................................................................................................................................................................32

Phonebook Example: An MTU/MDU Application............................................................................................................34

Connectivity Test ...............................................................................................................................................................38

Troubleshooting.................................................................................................................................................................40

CHAPTER 3: MECHANICAL INSTALLATION AND CABLI NG..................................................................................41

INTRODUCTION .......................................................................................................................................................................42

SAFETY WARNINGS ................................................................................................................................................................42

General Safety ...................................................................................................................................................................42

Lithium Battery Caution ....................................................................................................................................................42

Ethernet (WAN) Ports Caution..........................................................................................................................................42

Safety Warnings Telecom...................................................................................................................................................42

UNPACKING YOUR MULTIVOIP.............................................................................................................................................43

Unpacking the MVPFXS-8/16/24 ......................................................................................................................................43

Rack Mounting Instructions for MVPFXS-8/16/24............................................................................................................44

Safety Recommendations for Rack Installations of MVPFXS-8/16/24..............................................................................45

19-Inch Rack Enclosure Mounting Procedure...................................................................................................................46

CABLING PROCEDURE FOR MVPFXS-8/16/24 .......................................................................................................................47

CHAPTER 4: MULTIVOIP & AUXILIARY SOFTWARE...............................................................................................51

INTRODUCTION .......................................................................................................................................................................52

SUMMARY ..............................................................................................................................................................................52

CHAPTER 5: TECHNICAL CONFIGURATION...............................................................................................................53

CONFIGURING THE MULTIVOIP.............................................................................................................................................54

CONFIGURATION BY WEB GUI...............................................................................................................................................55

Pre-Requisites....................................................................................................................................................................55

IP Parameters..................................................................................................................................................................................... 55

Telephony Interface Parameters ........................................................................................................................................................ 56

Config Info CheckList.......................................................................................................................................................................56

Procedure for Configuration by Web GUI (Summary)......................................................................................................57

Local Configuration Procedure (Detailed)........................................................................................................................57

Contents MultiVOIP FXS User Guide

CHAPTER 6: PHONEBOOK CONFIGURATION.............................................................................................................84

CONFIGURING MULTIVOIP PHONEBOOKS .............................................................................................................................85

PHONEBOOK EXAMPLES .........................................................................................................................................................93

2 Site Example ...................................................................................................................................................................93

Configuring Mixed Digital/Analog VOIP Systems ............................................................................................................98

Call Completion Summaries............................................................................................................................................103

Variations in PBX Characteristics...................................................................................................................................105

CHAPTER 7: OPERATION AND MAINTENANCE.......................................................................................................106

OPERATION AND MAINTENANCE SUMMARY ........................................................................................................................107

System Information screen...............................................................................................................................................108

Statistics Screens .............................................................................................................................................................111

About Call Progress.........................................................................................................................................................111

About IP Statistics............................................................................................................................................................114

GENERAL OPERATION FUNCTIONS .......................................................................................................................................117

Change Username/Password...........................................................................................................................................117

Establishing a Username and Password........................................................................................................................................... 117

About Passwords & Login/Logout from Specific Computers ......................................................................................................... 118

Logout..............................................................................................................................................................................119

Save & Apply...................................................................................................................................................................119

Reboot Voip .....................................................................................................................................................................120

Restore Factory Defaults.................................................................................................................................................120

UPGRADING MULTIVOIP FIRMWARE................................................................................................................................... 121

Introduction .....................................................................................................................................................................121

Identifying Current Firmware Version............................................................................................................................121

Obtaining Updated Firmware..........................................................................................................................................122

UPGRADING MULTIVOIP FIRMWARE VIA FTP CLIENT AND VOIP’S BUILT-IN FTP SERVER FUNCTION...............................124

SYSLOG SERVER FUNCTIONS ...............................................................................................................................................144

CHAPTER 8 WARRANTY, SERVICE, AND TECH SUPPORT....................................................................................146

LIMITED WARRANTY............................................................................................................................................................147

REPAIR PROCEDURES FOR U.S. AND CANADIAN CUSTOMERS ..............................................................................................147

TECHNICAL SUPPORT ........................................................................................................................................................... 148

Contacting Technical Support.........................................................................................................................................148

CHAPTER 9: REGULATORY INFORMATION.............................................................................................................149

EMC, Safety, and R&TTE Directive Compliance............................................................................................................150

FCC DECLARATION.............................................................................................................................................................. 150

Industry Canada ..............................................................................................................................................................150

FCC Part 68 Telecom......................................................................................................................................................150

Canadian Limitations Notice...........................................................................................................................................151

WEEE Statement..............................................................................................................................................................152

APPENDIX A: CABLE PINOUTS.....................................................................................................................................153

APPENDIX A: CABLE PINOUTS .............................................................................................................................................154

Command Cable ..............................................................................................................................................................154

Ethernet Connector..........................................................................................................................................................154

RJ-21 Connector..............................................................................................................................................................155

APPENDIX B: TCP/UDP PORT ASSIGNMENTS...........................................................................................................156

WELL KNOWN PORT NUMBERS ............................................................................................................................................157

PORT NUMBER ASSIGNMENT LIST ........................................................................................................................................157

INDEX....................................................................................................................................................................................158

Chapter 1: Overview

Overview MultiVOIP FXS User Guide

About This Manual

This manual is about Voice-over-IP products made by Multi-Tech Systems, Inc. It describes three analog MultiVOIP

FX units that operate with the SIP transmission protocol only and use the FXS telephony interface only, namely, models MVPFXS-24, MVPFXS-16, and MVPFXS-8. At this writing, only the MVPFXS-24 model has been released; the MVPFXS-16 and MVPFXS-8 will be forthcoming.

These MultiVOIP units can inter-operate with other contemporary analog MultiVOIP units (MVP130, MVP130FXS, MVP210, MVP410, and MVP810), with contemporary SIP-Survivability MultiVOIP units (MVP210-SS, MVP410-SS, and MVP810-SS), with contemporary BRI MultiVOIP units (MVP410ST & MVP810ST), with contemporary FXO/FXS SIP MultiVOIPs (MVPFX2-2/4/8), with contemporary digital T1/E1/ISDN-PRI MultiVOIP units (MVP2410 and MVP3010), and with the earlier generation of MultiVOIP products (MVP200, MVP400, MVP800, MVP120, etc.)

The table below describes the vital characteristics of the various models described in this manual.

Analog MultiVOIP SIP FXS-Only Gateways

Description

Model

Function analog voip gateway, SIP only,

MVPFXS-24 MVPFXS-16 MVPFXS-8

analog voip gateway, SIP only, FXS interface only, web GUI only (no Windows GUI)

FXS interface only, web GUI

only (no Windows GUI)

Capacity 24 channels 16 channels 8 channels Chassis/

19” 1U rack mount 19” 1U rack mount 19” 1U rack mount

Mounting

analog voip gateway, SIP only, FXS interface only, web GUI only (no Windows GUI)

How to Use This Manual. In short, use the index and the examples. When our readers crack open this large manual, they generally need one of two things: information on a very specific software setting or technical parameter (about telephony or IP) or they need help when setting up phonebooks for their voip systems. The index gives quick access to voip settings and parameters. It’s detailed. Use it. The best way to learn about phonebooks is to wade through examples like those in our Phonebook Configuration chapter. Finally, this manual is meant to be comprehensive. If you notice that something important is lacking, please let us know.

Additional Resources. The MultiTech web site (www.multitech.com) offers both a list of Frequently Asked Questions (the MultiVOIP FAQ) and a collection of resolutions of issues that MultiVOIP users have encountered (these are Troubleshooting Resolutions in the searchable Knowledge Base).

MultiVOIP FXS User Guide Overview

Introduction to Analog MultiVOIP FX SIP FXS-only Gateway Voice-over-IP Units (MVPFXS-8/16/24)

VOIP: The Free Ride. We proudly present Multi-Tech's MVPFXS-8/16/24 MultiVOIPTM FXS SIP Gateways. These three models allow voice/fax communication to be transmitted at no additional expense over your existing IP network, which has ordinarily been data only. To access this free voice and fax communication, you simply connect the MultiVOIP to your telephone equipment and your existing Internet connection. These analog MultiVOIPs inter-operate readily with T1 or E1 MultiVOIP units.

910

Power Boot

LNK FDX SPD COL

12345678

WAN

Figure 1-1: MVPFXS-8/16/24 Chassis

Capacity. The MultiVOIP FX model MVPFXS-24 is a twenty-four channel unit, the model MVPFXS-16 is a sixteen-channel unit, and the MVPFXS-8 is an eight-channel unit. The front panel (Figure 1-1) is the same for all three units. However, for the MVPFXS-8, only the first eight of the channel LEDs will be functional; for the MVPFXS-16, only the first sixteen of the channel LEDs will be functional. All three of these MultiVOIP units have a 10/100Mbps Ethernet interface for its full-featured web-based configuration GUI and a console port for local access to basic startup configuration parameters (like the gateway’s IP address and password).

11 12 13 14 15

16 17 19242322212018

Mounting. Mechanically, the MVPFXS-8/16/24 MultiVOIP FX units are designed for a one-high industrystandard EIA 19-inch rack enclosure. The product must be installed by qualified service personnel in a restricted-access area, in accordance with Articles 110-16, 10-17, and 110-18 of the National Electrical Code, ANSI/NFPA 70.

Overview MultiVOIP FXS User Guide

Phone System Transparency. These MultiVOIPs inter-operate with a telephone switch or PBX, acting as a switching device that directs voice and fax calls over an IP network. The MultiVOIPs have “phonebooks,” directories that determine to who calls may be made and the sequences that must be used to complete calls through the MultiVOIP. The phonebooks allow the phone user to interact with the VOIP system just as they would with an ordinary PBX or telco switch. When the phonebooks are set, special dialing sequences are minimized or eliminated altogether. Once the call destination is determined, the phonebook settings determine whether the destination VOIP unit must strip off or add dialing digits to make the call appear at its destination to be a local call.

Voip Protocol. The MVPFXS units use the SIP protocol only. (“SIP” means Session Initiation Protocol.)

Telephony Interface. The MVPFXS units use the FXS telephony interface only.

Data Compression & Quality of Service. The analog MultiVOIP

FX unit comes equipped with a variety of data compression capabilities, including G.723, G.729, and G.711 and features DiffServ quality-of-service (QoS) capabilities.

Management. Configuration and system management for the MVPFXS units is done primarily through a web interface. Once you know the IP address of an MVPFXS unit, you can contact that unit with a web browser and set the unit’s operating parameters, which are grouped into several separate screens.

Figure 1-2: The Presentation of the MultiVOIP Web-Based GUI (IP Parameters screen shown)

Certain base-level parameters (like the IP address and password of the unit) can be set by connecting the MVPFXS unit’s “Console” receptacle to a serial connector on a PC (using aRJ45-to-DB9 connector).

MultiVOIP FXS User Guide Overview

The primary advantage of the web GUI (over a GUI that requires a local connection) is remote access for control and configuration. The controller PC and the MultiVOIP unit itself must both be connected to the same IP network and their IP addresses must be known.

Logging of System Events. MultiTech has built SysLog Server functionality into the software of the MultiVOIP units. SysLog is a de facto standard for logging events in network communication systems.

Figure 1-3: Logging with SysLog

The SysLog Server resides in the MultiVOIP unit itself. To implement this functionality, you will need a SysLog client program (sometimes referred to as a “daemon”). SysLog client programs, both paid and freeware, can be obtained from Kiwi Enterprises, among other firms. See www.kiwisyslog.com

. SysLog client programs essentially give you a means of structuring console messages for convenience and ease of use.

MultiTech Systems does not endorse any particular SysLog client program. SysLog client programs by any qualified provider should suffice for use with MultiVOIP units. Kiwi’s brief description of their SysLog program indicates the typical scope of such programs. “Kiwi Syslog Daemon is a freeware Syslog Daemon for the Windows platform. It receives, logs, displays and forwards Syslog messages from hosts such as routers, switches, Unix hosts and any other syslog enabled device. There are many customizable options available.”

Overview MultiVOIP FXS User Guide

MultiVOIP Front Panel LEDs

LED Types. The MultiVOIPs have two types of LEDs on their front panels:

(1) general operation LED indicators (for power, booting, and

ethernet functions), and

(2) channel operation LED indicators that describe the data traffic and performance in each VOIP data

channel. Active LEDs. On the MVPFXS units, there are four WAN LEDs and twenty-four channel-operation LEDs. However, on the MVPFXS-8, only the left eight sets of channel-operation LEDs are functional. On the MVPFXS-16, only the left sixteen sets of channel-operation LEDs are functional. All of the channeloperation LEDs are functional on the MVPFXS-24 unit.

Power Boot

WAN

LNK FDX SPD COL

Figure 1-4. MVPFXS-8/16/24 LEDs

LED Descriptions for MultiVOIP MVPFXS Units

Front Panel LED Definitions

LED NAME DESCRIPTION

General Operation LEDs (one set on each MultiVOIP model)

Power Indicates presence of power.

Boot

Ethernet

After power up, the Boot LED will be on briefly while the MultiVOIP is booting. It lights whenever the MultiVOIP is booting or downloading a setup configuration data set.

FDX. LED indicates whether Ethernet connection is half-duplex or full-duplex (FDX) and, in half-duplex mode, indicates occurrence of data collisions. LED is on constantly for full-duplex mode; LED is off constantly for half-duplex mode. When operating in half-duplex mode, the LED will flash during data collisions.

LNK. Link/Activity LED. This LED is lit if Ethernet connection has been made. It is off when the link is down (i.e., when no Ethernet connection exists). While link is up, this LED will flash off to indicate data activity.

123456789101112131415161718

SPD. Data speed indicator. When lit, data rate is 100 Mbps. When not lit, data rate is 10 Mbps.

COL. Collision indicator. Lit when data collision is detected on Ethernet network.

Channel-Operation LEDs

1, 2, 3, ... 24

There is one LED for each voip channel (channels 1-8 for MVPFXS-8; channels 1-16 for MVPFXS-16; channels 1-24 for MVPFXS-24). The indicator for any channel is lit when there is call activity on that voip channel. The LED is ON when the device attached to the channel is off hook.

MultiVOIP FXS User Guide Overview

Computer Requirements

The command computer used in conjunction with the MultiVOIP must meet these requirements:

(a) any reasonably modern PC, (b) must have an up-to-date version of Java installed (v. 1.5 or higher), (c) must have an up-to-date web browser installed (at this writing, up-to-date browsers would include Internet Explorer 6.0(+), Netscape 6.0(+), or Mozilla FireFox 1.0(+).), (d) must have IP access to the MultiVOIP, and (e) optionally, have an available serial COM port for a console connection to the MultiVOIP.

This PC will generally be in contact with the MVPFXS unit via the web. The Console connection, which requires a cable directly between the PC and the MultiVOIP is, essentially, a backup method of connecting to the voip. This direct connection can be used to reset the MultiVOIP’s IP address and to upgrade firmware. The direct connection is not involved in the general operation of the MultiVOIP unit.

Specifications

Parameter

Operating Voltage/ Current Mains Frequencies Power Consumption Mechanical Dimensions

Weight 7.15 lbs.

Operating Temperature

Storage Temperature

/Model

MVPFXS-24

100-240 VAC,

1.2 - 0.6 A

50/60 Hz 50/60 Hz 50/60 Hz

51 watts TBD TBD

1.75” H x

17.4” W x

8.5” D

4.5cm H x

44.2 cm W x

21.6 cm D

(3.5 kg) includes power supply 0° to +60°C (32° to +120°F); humidity range 20-90% (noncondensing)

-10°C to +85°C -10°C to +85°C -10°C to +85°C

MVPFXS-16 MVPFXS-8

100-240 VAC

1.2 - 0.6 A

1.75” H x

17.4” W x

8.5” D

4.5cm H x

44.2 cm W x

21.6 cm D

7.15 lbs. (3.5 kg) includes power supply 0° to +60°C (32° to +120°F); humidity range 20-90% (non-condensing)

100-240 VAC

1.2 - 0.6 A

1.75” H x

17.4” W x

8.5” D

4.5cm H x

44.2 cm W x

21.6 cm D

7.15 lbs. (3.5 kg) includes power supply 0° to +60°C (32° to +120°F); humidity range 20-90% (non-condensing)

Overview MultiVOIP FXS User Guide

Installation at a Glance

The basic steps of installing your MultiVOIP network involve unpacking the units, connecting the cables, and configuring the units using the MultiVOIP web-based graphic user interface (GUI), and confirming connectivity with another voip site. This process results in a fully functional Voice-Over-IP network.

Related Documentation

The MultiVOIP User Guide (the document you are now reading) comes in electronic form and is included on your system CD. It presents in-depth information on the features and functionality of Multi-Tech’s MultiVOIP Product Family. The MultiVOIP Cabling Guide, a printed document, is shipped with each MVPFXS-8/16/24 unit.

The CD media is produced using Adobe Acrobat print your copy of a user guide, load Acrobat Reader the MultiVOIP CD and is also a free download from Adobe’s Web Site:

for viewing and printing the user guide. To view or

on your system. The Acrobat Reader is included on

www.adobe.com/prodindex/acrobat/readstep.html

This MultiVOIP User Guide is also available on Multi-Tech’s Web site at:

http://www.multitech.com

Viewing and printing a user guide from the Web also requires that you have the Acrobat Reader loaded on your sy stem . To select the MultiVOIP User Guide from the Multi-Tech Systems home page, click Documents and then click MultiVOIP Fam ily in the product list drop-down window. All documents for this MultiVOIP Product Family will be displayed. You can then choose User Guide (MultiVOIP Product Family) to view or download the .pdf file.

Entries (organized by model number) in the “knowledge base” and ‘troubleshooting resolutions’ sections of the MultiTech web site (found under “Support”) constitute another source of help for problems encountered in the field.

Chapter 2: Quick Start Guide

Preliminaries & Info Gathering MultiVOIP FXS Quick Start Guide

This chapter contains streamlined instructions to get the MultiVOIP up and running quickly. These startup instructions include assistance on setting up the MultiVOIP’s Inbound and Outbound Phonebooks. These sections of the Quick Start Guide may be particularly useful for phonebook configuration:

Phonebook Starter Configuration Phonebook Tips Phonebook Example (One Common Situation)

The Quick Start Guide also contains a “Phonebook Worksheet” section. You may want to print out several worksheet copies. Paper copies can be very helpful in comparing phonebooks at multiple sites at a glance. This will assist you in making the phonebooks clear and consistent and will reduce ‘surfing’ between screens on the configuration program.

A printed Cabling Guide is shipped with the MultiVOIP and an electronic copy is included on the Product CD.

MultiVOIP Startup Tasks

Task Summary

 Collecting Phone/IP

Details ( vital! )

 Command/Control

Computer Setup:

The MultiVOIP must be configured to interface with your particular phone system and IP network. To do so, certain details must be known about those phone and IP systems.

Some modest minimum specifications must be met. A COM port must be set up.

Specs & Settings

 Placement

Decide where you’ll mount the voip.

 Hookup Connect power, phone, and data cables per the Quick

Hookup diagram in this chapter.

 Software Installation Check that an up-to-date version of Java (version 1.5) is

on your computer. If not, install it from the MultiVOIP CD or the Java website.

 Phone/IP Starter

Configuration

 Phonebook Starter

Configuration

You will enter phone numbers and IP addresses. You’ll use default parameter values where possible to get the system running quickly. Use “Config Info CheckList” (page 17).

The phonebook is where you specify how calls will be routed. To get the system running quickly, you’ll make phonebooks for just two voip sites.

 Connectivity Test You’ll find out if your voip system can carry phone calls

between two sites. That means you’re up and running!

 Troubleshooting Detect and remedy any problems that might have

prevented connectivity.

MultiVOIP FXS Quick Start Guide Preliminaries & Info Gathering

Phone/IP Details *Absolutely Needed* Before Starting the Installation

The MultiVOIP will interface with both the IP network and the phone system. You must gather information about the IP network and about the phone system so that the MultiVOIP can be configured to operate with them properly. A summary of this configuration information appears on page 16 (“Config Info CheckList”).

Gather IP Information

Ask your computer network



administrator.

• IP Address

• IP Mask

• Gateway

• Domain Name Server (DNS) Info (optional)

IP Network Parameters: Record for each VOIP Site in System

Info needed to operate:

all MultiVOIP models.

Phone/IP Details *Absolutely Needed*

Gather Telephone Information

Analog Phone Parameters



Ask phone company or telecom manager.

• Which interface type is used?

FXS Loop Start only

• Determine whether the channel will be used for a phone, fax, or KTS (key telephone system), or perhaps serve a station card on a PBX.

Analog Telephony Interface Parameters:

Record for this VOIP Site

Needed for:

MVPFXS-24 MVPFXS-16 MVPFXS-8

Preliminaries & Info Gathering MultiVOIP FXS Quick Start Guide

Config Info CheckList

Type of Config Info Gathered

MultiVOIP Configuration screen on which to enter Config

√

Info

IP info for voip unit

● IP address

● Gateway

● DNS IP (if used)

Interface Type (FXS only*)

Country Code Regional Parameters

Network Locations of SIP Proxy units, if used (IP Address or Domain Name)

Reminder: Be sure to Save & Apply after entering configuration values.

IP Parameters

Interface Parameters

*In FXO/FXS systems, channels used for phone, fax, or key system are FXS; channels used for analog PBX extensions or analog telco lines are FXO.

SIP Call Signaling

Identify Remote VOIP Site to Call

When you’re done installing the MultiVOIP, you’ll want to confirm that it is configured and operating properly. To do so, it’s good to have another voip that you can call for testing purposes. You’ll want to confirm end-to-end connectivity. You’ll need IP and telephone information about that remote site.

If this is the very first voip in the system, you’ll want to coordinate the installation of this MultiVOIP with an installation of another unit at a remote site.

MultiVOIP FXS Quick Start Guide Command PC & Voip Hookups

Command/Control Computer Setup (Specs & Settings)

The computer used for command and control of the MultiVOIP

The configuration tasks and control tasks the PC will have to do with the MultiVOIP are not especially demanding. Still, we recommend using a reasonably new computer. The computer that you use to configure your MultiVOIP need not be dedicated to the MultiVOIP after installation is complete.

COM port on controller PC. If you choose to use the MultiVOIP’s Console connection, you will need an available COM port on the controller PC. You’ll need to know which COM port is available for use with the MultiVOIP (COM1, COM2, etc.).

Placement

Mount your MultiVOIP in a safe and convenient location where cables for your network and phone system are accessible. Rack-mounting instructions are in Chapter 3: Mechanical Installation & Cabling.

Command PC & Voip Hookups MultiVOIP FXS Quick Start Guide

Quick Hookup for MVPFXS-8/16/24

Auxiliary Software Issues MultiVOIP FXS Quick Start Guide

Ensure that Java & Browser Versions will Support Web-Based GUI

For more details, see Chapter 4: Software Installation in User Guide.

1. MultiVOIP must be properly cabled. Power must be turned on.

2. Is Java Runtime program at level 1.5 or greater? If not, load up-to-date Java version from MultiVOIP CD or from Java web site.

3. Is web browser of a sufficiently recent version to support MultiVOIP web GUI? (The browser must be Internet Explorer 6.0(+), Netscape 6.0(+), or FireFox 1.0(+).) If not, download a browser version that is new enough to support the web GUI.

4. Browse to IP address of MultiVOIP unit (default is 192.168.2.1).

5. If username and password have been established, enter them when prompted by voip.

6. Use web browser GUI to continue with configuration and operation of voip.

Changing the IP Address through the Console Connection

At its initial bootup, the default IP address of the MultiVOIP is 192.168.2.1. If you are not able to access the web GUI through this IP address (192.168.2.1), then use the procedure below to set a valid IP for operation of the MultiVOIP on your network.

This procedure also works if the IP address is forgotten.

1. Connect a cable between the MultiVOIP’s “Console” connector and a serial cable on the computer.

2. Launch HyperTerminal or a similar communications program.

Phone/IP Starter Config. MultiVOIP FX Quick Start Guide

3. Establish a ‘connection’ in HyperTerminal.

4. Check that HyperTerminal is addressing the correct COM port.

MultiVOIP FXS Quick Start Guide Phone/IP Starter Config.

5. Check that HyperTerminal’s data rate is set to 115200bps.

6. To begin, HyperTerminal must be connected and ready.

Phone/IP Starter Config. MultiVOIP FX Quick Start Guide

7. Reboot the MultiVOIP by turning off its power and turning it back on again. The ARMBoot prompt will appear on the HyperTerminal screen.

When this screen appears, you must quickly press any key to stop the regular boot-up process (the manual boot process).

8. Type setenv ipaddr a.b.c.d where a, b, c, & d are the octet values for the desired IP address of the voip.

Press Enter.

Note: When using the setenv command, be careful in your spelling. If you mis-spell ipaddr as “ipadde” for

example, the ARMBoot program will create a new and useless variable entitled ipadde and will not change the value of the ipaddr variable.

MultiVOIP FXS Quick Start Guide Phone/IP Starter Config.

9. To confirm that the ipaddr (voip IP address) was indeed changed to the value you want, type printenv at the mvp-boot> prompt and then press Enter.

10. Type saveenv and press Enter.

11. Turn the voip off and then on again to reboot it.

Phone/IP Starter Config. MultiVOIP FX Quick Start Guide

12. Allow the voip to boot up again normally (this will take a few minutes) with the console connection still

active. When the rebooting process is complete (when the boot light is no longer lit), type 1 and press Enter.

NOTE: This change of IP address is only temporary. You must complete this procedure to make the

change of IP address permanent.

13. Use a web browser to browse to the voip using the IP address that you have just assigned.

14. In the web browser, click on IP Parameters in the sidebar list.

MultiVOIP FXS Quick Start Guide Phone/IP Starter Config.

In each field, enter the values that fit your particular network.

Click OK.

15. In the sidebar menu, click Save & Apply. Allow the voip to Reboot.

Phone/IP Starter Config. MultiVOIP FX Quick Start Guide

Phone/IP Starter Configuration

Full details here:

MVPFXS-24 MVPFXS-16 MVPFXS-8

1. Open a browser and go to the IP Address of the MVPFXS unit (default IP is 192.168.2.1). In the sidebar

menu, click Configuration.

2. Go to Configuration | IP. Enter or alter any IP Parameters, as needed. Click OK.

3. Go to Configuration | Voice/Fax. Select Coder | “Automatic.” At the right-hand side of the dialog box, click OK. If you know any specific parameter values that will apply to your system, enter them. Click Copy Channel. Select Copy to All. Click Copy. At main Voice/Fax Parameters screen, click OK to exit from the dialog box.

4. Enter telephone system information. Go to Configuration | Interface. Enter parameters obtained from phone company or PBX administrator. Click OK.

5. Go to Configuration | Regional Parameters. Select the Country/Region that fits your situation. Click

OK and confirm. Click OK to exit from the dialog box.

6. Go to Configuration | Logs/Traces. Select “Enable Console Messages.” Click OK.

To do logging with a SysLog client program, click on “SysLog Server – Enable” in the Logs/Traces screen. To implement this function, you must install a SysLog client program. For more info, see the “SysLog Server Functions” section of the “Operation & Maintenance” chapter of the

Technical Configuration chapter

in User Guide

User Guide.

7. Go to Save &Apply. Click OK. This will save the parameter values that you have just entered.

The MultiVOIP’s “BOOT” LED will light up while the configuration file is being saved and loaded into the MultiVOIP. Don’t do anything to the MultiVOIP until the “BOOT “LED is off (a loss of power at this point could cause the MultiVOIP unit to lose the configuration settings you have made).

END OF PROCEDURE.

MultiVOIP FXS Quick Start Guide Phonebook Starter Config.

Phonebook Starter Configuration (with remote voip)

If the topic of voip phone books is new to you, it may be helpful to read the PhoneBook Tips section (page

32) before starting this procedure.

To do this part of the quick setup, you need to know of another voip that you can call to conduct a test. Ideally, a test of two voips at the same physical location connected back-to-back should be done first. A secondary test should be done between two voips at different locations, typically with one voip located somewhere outside of your building. You must know the phone number and IP address for that site. We are generally assuming here that the MultiVOIP will operate in conjunction with a PBX. Note, however, that MVPFXS voips could easily be connected simply to a terminal block and require very simple phone book entries.

You must configure both the Outbound Phonebook and the Inbound Phonebook. A starter configuration only means that two voip locations will be set up to begin the system and establish voip communication.

Outbound Phonebook

1. Open the browser and go to the IP address of the MultiVOIP unit. In the sidebar menu, select Phone Book

2. Go to Outbound Phonebook | Add Entry.

3. On a sheet of paper, write down the calling code of the remote voip (area code, country code, city code, etc.) that you’ll be calling.

Follow the example that best fits your situation.

North America,

Long-Distance Example

Technician in Seattle (area

206) must set up one voip there, another in Chicago (area 312, downtown).

Answer: Write down 312.

Euro, National Call

Example

Technician in central

London (area 0207) to set up voip there, another in Birmingham (area 0121).

Answer: write down 0121.

Euro, International Call Example Technician in Rotterdam (country 31; city 010) to

set up one voip there, another in Bordeaux (country 33; area 05).

Answer: write down 3305.

Phonebook Starter Config. MultiVOIP FXS Quick Start Guide

4. Suppose you want to call a phone number outside of your building using a phone station that is an

extension from your PBX system (if present). What digits must you dial? Often a “9” or “8” must be dialed to “get an outside line” through the PBX (i.e., to connect to the PSTN). Generally, “1 “or “11” or “0” must be dialed as a prefix for calls outside of the calling code area (long-distance calls, national calls, or international calls).

On a sheet of paper, write down the digits you must dial before you can dial a remote area code.

North America,

Long-Distance Example

Seattle-Chicago system.

Seattle voip works with PBX that uses “8” for all voip calls. “1” must immediately precede area code of dialed number.

Answer: write down 81.

Euro, National Call

Example

London/Birming. system.

London voip works with PBX that uses “9” for all out-of-building calls whether by voip or by PSTN. “0” must immediately precede area code of dialed number.

Answer: write down 90.

Euro, International Call Example Rotterdam/Bordeaux system.

Rotterdam voip works with PBX where “9” is used for all out-of-building calls. “0” must precede all international calls.

Answer: write down 90.

5. In the “Destination Pattern” field of the Outbound Phone Book Add Entry screen, enter the digits from

step 4 followed by the digits from step 3.

North America,

Long-Distance Example

Seattle-Chicago system.

Answer: enter 81312 as

Destination Pattern in Outbound Phone-book of Seattle voip.

Euro, National Call

Example

London/Birming. system.

Leading zero of Birmingham area code is dropped when combined with national-dialing access code. (Such practices vary by country.)

Answer: enter 90121 as

Destination Pattern in Outbound Phonebook of London voip. Not 900121.

Euro, International Call Example Rotterdam/Bordeaux system.

Answer: enter 903305 as Destination Pattern in

Outbound Phonebook of Rotterdam voip.

MultiVOIP FXS Quick Start Guide Phonebook Starter Config.

6. In the “Remove Prefix” field, enter the initial PBX access digit (“8” or “9”).

North America,

Long-Distance Example

Seattle-Chicago system.

Answer: enter 8 in “Remove

Prefix” field of Seattle Outbound Phonebook.

Euro, National Call

Example

London/Birming. system.

Answer: enter 9 in “Remove

Prefix” field of London Outbound Phonebook.

Euro, International Call Example Rotterdam/Bordeaux system.

Answer: enter 9 in “Remove Prefix” field of Outbound

Phonebook for Rotterdam voip.

Some PBXs will not ‘hand off’ the “8” or “9” to the voip. But for those PBX units that do, it’s important to enter the

“8” or “9” in the “Remove Prefix” field in the Outbound Phonebook. This precludes the problem of having to make two inbound phonebook entries at remote voips, one to account for situations where “8” is used as the PBX access digit, and another for when “9” is used.

7. If you intend to use a SIP Proxy, enter the relevant information in the Call Signaling screen.

8. Enter the IP address of the MultiVOIP that you want to call.

9. Click OK to exit from the Outbound Phonebook Add Entry screen.

Phonebook Starter Config. MultiVOIP FXS Quick Start Guide

Inbound Phonebook

1. Open the browser and go to the IP address of the MultiVOIP unit.

2. Go to Phone Book | Inbound Phonebook | Add Entry.

3. In the “Remove Prefix” field, enter your local calling code (area code, country code, city code, etc.) preceded by any other “access digits” that are required to reach your local site from the remote voip location (think of it as though the call were being made through the PSTN – even though it will not be).

North America,

Long-Distance Example

Seattle-Chicago system.

Seattle is area 206. Chicago employees must dial 81 before dialing any Seattle number on the voip system.

Answer: 1206 is prefix to be

removed by local (Seattle) voip.

Euro, National Call

Example

London/Birming. system.

Inner London is 0207 area. Birmingham employees must dial 9 before dialing any London number on the voip system.

Answer: 0207 is prefix to be

removed by local (London) voip.

Euro, International Call Example Rotterdam/Bordeaux system.

Rotterdam is country code 31, city code 010. Bordeaux employees must dial 903110 before dialing any Rotterdam number on the voip system.

Answer: 03110 is prefix to be removed by local

(Rotterdam) voip.

MultiVOIP FXS Quick Start Guide Phonebook Starter Config.

4. In the “Add Prefix” field, enter any digits that must be dialed from your local voip to gain access to the

PSTN.

North America,

Long-Distance Example

Seattle-Chicago system.

On Seattle PBX, “9” is used to get an outside line.

Answer: 9 is prefix to be

added by local (Seattle) voip.

Euro, National Call

Example

London/Birming. system.

On London PBX, “9” is used to get an outside line.

Answer: 9 is prefix to be

added by local (London) voip.

Euro, International Call Example Rotterdam/Bordeaux system.

On Rotterdam PBX, “9” is used to get an outside line.

Answer: 9 is prefix to be added by local (Rotterdam)

voip.

5. In the “Channel Number” field, enter “Hunting.” A “hunting” value means the voip unit will assign the call to the first available channel. If desired, specific channels can be assigned to specific incoming calls (i.e., to any set of calls received with a particular incoming dialing pattern).

6. In the “Description” field, it is useful to describe the ultimate destination of the calls. For example, in a

New York City voip system, “incoming calls to Manhattan office,” might describe a phonebook entry, as might the descriptor “incoming calls to NYC local calling area.” The description should make the routing of calls easy to understand. (40 characters max.)

North America,

Long-Distance Example

Seattle-Chicago system.

Possible Description:.

Free Seattle access, all employees

Euro, National Call

Example

London/Birming. system.

Possible Description:.

Local-rate London access, all empl.

Euro, International Call Example Rotterdam/Bordeaux system.

Possible Description:. Local-rate Rotterdam access, all

empl.

7. Repeat steps 2-6 for each inbound phonebook entry. When all entries are complete, go to step 8.

8. Click OK to exit the inbound phonebook screen.

9. Click on Save & Apply. Click OK. Then click Reboot Voip.

Your starter inbound phonebook configuration is complete.

Phonebook Tips MultiVOIP FXS Quick Start Guide

Phonebook Tips

Preparing the phonebook for your voip system is a complex task that, at first, seems quite daunting. These tips may make the task easier.

Use Dialing Patterns, Not Complete Phone Numbers. You will not generally enter complete phone numbers

in the voip phonebook. Instead, you’ll enter “destination patterns” that involve area codes and other digits. If the destination pattern is a whole area code, you’ll be assigning all calls to that area code to go to a particular voip which has a unique IP address. If your destination pattern includes an area code plus a particular local phone exchange number, then the scope of calls sent through your voip system will be narrowed (only calls within that local exchange will be handled by the designated voip, not all calls in that whole area code). In general, when there are fewer digits in your destination pattern, you are asking the voip to handle calls to more destinations.

The Four Types of Phonebook Digits Used. Important!

“Destination patterns” to be entered in your phonebook will generally consist of:

(a) calling area codes, (b) access codes, (c) local exchange numbers, and (d) specialized codes.

Although voip phonebook entries may look confusing at first, it’s useful to remember that all the digits in any phonebook entry must be of one of these four types.

(a)

calling area codes. There are different names for these around the world: “area codes,” “city codes,”

“country codes,” etc. These codes, are used when making non-local calls. They always precede the phone number that would be dialed when making a local call.

(b)

access codes. There are digits (PSTN access codes) that must be dialed to gain access to an operator, to

access the publicly switched ‘long-distance’ calling system(North America), to access the publicly switched ‘national’ calling system (Europe and elsewhere), or to access the publicly switched ‘international’ calling system (worldwide).

There are digits (PBX access codes) that must be dialed by phones connected to PBX systems or key systems. Often a “9” must be dialed on a PBX phone to gain access to the PSTN (‘to get an outside line’). Sometimes “8” must be dialed on a PBX phone to divert calls onto a leased line or to a voip system. However, sometimes PBX systems are ‘smart’ enough to route calls to a voip system without a special access code (so that “9” might still be used for all calls outside of the building).

There are also digits (special access codes) that must be dialed to gain access to a particular discount longdistance carrier or to some other closed or proprietary telephone system.

(c)

local exchange numbers. Within any calling area there will be many local exchange numbers. A single

exchange may be used for an entire small town. In cities, an exchange may be used for a particular neighborhood (although exchanges in cities do not always cover easily discernible areas). Organizations like businesses, governments, schools, and universities are also commonly assigned exchange numbers for their exclusive use. In some cases, these organizational-assigned exchanges can become non-localized because the exchange is assigned to one facility and linked, by the organization’s private network, to other sometimes distant locations.

(d)

specialized codes. Some proprietary voip units assign, to sites and phone stations, numbers that are not

compatible with PSTN numbering. This can also occur in PBX or key systems. These specialized numbers must be handled on a case-by-case basis.

MultiVOIP FXS Quick Start Guide Phonebook Tips

Knowing When to Drop Digits. Example

When calling area codes and access codes are used in combination, a leading “1” or “0” must sometimes be dropped.

Phonebook Entry 

Using a Comma. Detail

Commas are used in telephone dialing strings to indicate a pause to allow a dial tone to appear (common on PBX and key systems). Commas may be used only in the “Add Prefix” field of the Inbound Phonebook.

Area code for Inner London is listed as “0207.” However, in international calls the leading “0” is dropped.

International Access Code

, = 1-second pause

in many PBX systems

(not needed in all)

U.K.

Country

Code

Leading Zero Dropped from Area Code

Ease of Use. The phonebook setup determines how easy the voip system is to use. Generally, you’ll

want to make it so dialing a voip call is very similar to dialing any other number (on the PSTN or through the PBX).

Avoid Unintentional Calls to Official/Emergency Numbers. Dialing a voip call will typically be somewhat

different than ordinary dialing. Because of this, it’s possible to set up situations, quite unwittingly, where phone users may be predisposed to call official numbers without intending to do so. Conversely, a voip/PBX system might also make it difficult to place an official/emergency call when one intends to do so. Study your phonebook setup and do some test-dialing on the system to avoid these pitfalls.

Inbound/Outbound Pattern Matching. In general, the Inbound Phonebook entries of the local voip unit will

match the Outbound Phonebook entries of the remote voip unit. Similarly, the Outbound Phonebook entries of the local voip unit will match the Inbound Phonebook entries of the remote voip unit. There will often be non-matching entries, but it’s nonetheless useful to notice the matching between the phonebooks.

Simulating Network in-lab/on-benchtop. One common method of configuring a voip network is to set up a

local IP network in a lab, connect voip units to it, and perhaps have phones connected on channel banks to make test calls.

Phonebook Example MultiVOIP FXS Quick Start Guide

Phonebook Example: An MTU/MDU Application

In the next example, a small, alternative telco uses an MVPFXS-24 to serve an apartment building with voip-based phone service. This is a common application of the MVPFXS-24 in facilities known as MTU/MDU (multi-tenant units or multi-dwelling units).

Phone Books for Telco CO and Voip Customer Apartment Building

Hilzenvalies, WV

Telco Office of

WVIP-Comm, Inc.

Area: 304

PBX/

Switch

24.98.62.4

24-Channel Digital VoIP (MVP2410)

SIP

Server

WVIP-Comm Voip WVIP-Comm Voip

Inbound Phonebook Outbound Phonebook

Prefix

Prefix to Remove

none none

to Add

Description of Incoming Calls

Lets Bluebird residents call any number.

Destination

Pattern

130455524 1304355 none

155524 1555 none

Prefix to Remove

Prefix to AddIPAddr

Must check the “Accept Any Number” checkbox.

55524 555 none

24.98.

62.3

24.98.

62.3

24.98.

62.3

Description of Outgoing Calls

Out of area-code calls to Bluebird Apt residents.

Intra area-code non-local calls to Bluebird Apt residents.

Local calls to Bluebird Apt residents.

PSTN

Network

Bluebird Apartments

Bluebird Apts Voip Bluebird Apts Voip

Inbound Phonebook Outbound Phonebook

Prefix

Prefix to Remove

2401 none

2402 none

2403 none

2424 none

to Add

Description of Incoming Calls

to Apt #1

to Apt #2

to Apt #3

to Apt #24

Destination

Pattern

none none none

Prefix to Remove

Prefix to AddIPAddr

Must check the “Accept Any Number” checkbox.

24.98.

62.4

Description of Outgoing Calls

Allows Bluebird Apt residents to call any number through WVIPComm Voip system.

(MVPFXS-24)

555-2401

Exchange: 555

24.98.62.3

24-Channel

SIP-FXS

VoI P

555-2402

555-2424

555-2423

555-2422

555-2403

24 apartments 24 extensions

MultiVOIP FXS Quick Start Guide Phonebook Example

Sample Phonebooks Enlarged

WVIP-Comm Voip WVIP-Comm Voip

Inbound Phonebook Outbound Phonebook

Prefix to Remove

none none

Prefix to Add

Must check the “Accept Any Number” checkbox.

Bluebird Apts Voip Bluebird Apts Voip

Inbound Phonebook Outbound Phonebook

Prefix to Remove

2401 none

Prefix to Add

Description of Incoming Calls

to Apt #1

Description of Incoming Calls

Lets Bluebird residents call any number.

Destination

Pattern

none none none

Destination

Pattern

130455524 1304355 none

155524 1555 none

55524 555 none

Prefix to Remove

Prefix to AddIPAddr

24.98.

62.4

Prefix to AddIPAddr

24.98.

62.3

24.98.

62.3

24.98.

62.3

Description of Outgoing Calls

Out of area-code calls to Bluebird Apt residents.

Intra area-code non-local calls to Bluebird Apt residents.

Local calls to Bluebird Apt residents.

2402 none

2403 none

2424 none

to Apt #2

to Apt #3

to Apt #24

Must check the “Accept Any Number” checkbox.

Allows Bluebird Apt residents to call any number through WVIPComm Voip system.

Phonebook Example MultiVOIP FXS Quick Start Guide

Phonebook Worksheet

Voip Location/ID:____________________________

Inbound Phonebook Outbound Phonebook

Prefix

Prefix to Remove

to Add

Other Details:

Inbound Phonebook Outbound Phonebook

Prefix to Remove

Description Incoming Calls

Destin. Pattern

Voip Location/ID:____________________________

Prefix

Description

to Add

Incoming Calls

Tot al Digits

Destin. Pattern

Prefix to Remove

Tot al Digits

Prefix to AddIPAddr

Prefix to Remove

Description Outgoing Calls

Prefix to AddIPAddr

Description Outgoing Calls

Other Details:

Voip Location/ID:____________________________

Inbound Phonebook Outbound Phonebook

Prefix

Prefix to Remove

to Add

Description Incoming Calls

Destin. Pattern

Tot al Digits

Prefix to Remove

Prefix to AddIPAddr

Description Outgoing Calls

Other Details:

MultiVOIP FXS Quick Start Guide Phonebook Example

Enlarged Phonebook Worksheet

Connectivity Test MultiVOIP FXS Quick Start Guide

Connectivity Test

The procedures “Phone/IP Starter Configuration” and “Phonebook Starter Configuration” must be completed before you can do this procedure.

1. These connections must be made:

 MultiVOIP to local phone station

–OR-- MultiVOIP to extension of key phone system

 MultiVOIP to command PC

 MultiVOIP to Internet

2. Inbound Phonebook and Outbound Phonebook must both be set up with at least one entry in each. These entries must allow for connection between two voip units.

3. Console messages must be enabled. (If this has not been done already, go, in the MultiVOIP GUI, to Configuration | Logs and select the “Console Messages” checkbox.

4. Make sure that the COM port connection is free so that the HyperTerminal program can use it.

5. Open the HyperTerminal program.

6. Use HyperTerminal to receive and record console messages from the MultiVOIP unit. To do so, set up HyperTerminal as follows (setup shown is for Windows NT4; details will differ slightly in other MS operating systems):

 In the upper toolbar of the HyperTerminal screen, click on the Properties button.

 In the “Connect To” tab of the Connection Properties dialog box, click on the Configure

button.

 In the next dialog box, on the “General” tab, set “Maximum Speed” to 115200 bps.

 On the “Connection” tab, set connection preferences to:

Data bits: 8

Parity: none

Stop bits: 1

 Click OK twice to exit settings dialog boxes.

7. Make VOIP call on a local phone line accessing PSTN directly or through key system..

MultiVOIP FXS Quick Start Guide Connectivity Test

8. Read console messages recorded on HyperTerminal.

Console Messages from Originating VOIP. The voip unit that originates the call will send back messages like that shown below.

[00026975] CAS[0] : RX : ABCD = 1, 1, 1, 1,Pstn State[1] TimeStamp : 26975 [00027190] CAS[0] : TX : ABCD = 1, 1, 1, 1 [00027190] PSTN: cas seizure detected on 0 [00027440] CAS[0] : TX : ABCD = 0, 0, 0, 0 [00033290] PSTN:call detected on 0 num=17637175662* [00033290] SIP[0]:destAddr = TA:200.2.10.5:1720,NAME:Mounds

View,TEL:17637175662,17637175662 [00033290] SIP[0]:srcAddr = NAME:New York,TA:200.2.9.20 [00033440] SIP [0]:cmCallStateProceeding [00033500] SIP[0]: Remote Information (Q931): MultiVOIP - T1 [00033565] CAS[0] : TX : ABCD = 1, 1, 1, 1 [00033675] SIP [0]: MasterSlaveStatus=Slave [00033675] SIP[0]:FastStart Setup Not Used [00033690] CAS[0] : TX : ABCD = 1, 1, 1, 1 [00033755] SIP[0]: Coder used 'g7231' [00033810] PSTN:pstn call connected on 0

Console Messages from Terminating VOIP. The voip unit connected to the phone where the call is answered will send back messages like that shown below.

[00170860] SIP[0]: New incoming call [00170860] PSTNIF : Placing call on channel 0 Outbound digit 7175662 [00170885] CAS[0] : TX : ABCD = 1, 1, 1, 1 [00171095] SIP [0]: MasterSlaveStatus=Master [00171105] CAS[0] : RX : ABCD = 1, 1, 1, 1,Pstn State[7] TimeStamp : 171105 [00171105] SIP[0]: Coder used 'g7231' [00171110] SIP[0]:FastStart Setup Not Used [00171110] SIP[0]: Already opened the outgoing logical channel [00171110] SIP[0]: Coder used 'g7231' [00171315] CAS[0] : RX : ABCD = 0, 0, 0, 0,Pstn State[9] TimeStamp : 171315 [00172275] PSTN: dialing digit ended on 0 [00172285] PSTN: pstn proceeding indication on 0 [00172995] CAS[0] : RX : ABCD = 1, 1, 1, 1,Pstn State[12] TimeStamp : 172995 [00173660] CAS[0] : TX : ABCD = 1, 1, 1, 1 [00173760] PSTN:pstn call connected on 0

9. When you see the following message, end-to-end voip connectivity has been achieved.

PSTN: pstn call connected on X”

“

where x is the number of the voip channel carrying the call

10. If the HyperTerminal messages do not confirm connectivity, go to the Troubleshooting procedure

below.

Quick Start Instructions MultiVOIP FXS User Guide

Troubleshooting

If you cannot establish connectivity between two voips in the system, follow the steps below to determine the problem.

1. Ping both MultiVOIP units to confirm connectivity to the network.

2. Verify the telephone connections.

 Check cabling. Are connections well seated? To correct receptacle?  Are telephone Interface Parameter settings correct?

Remember that each voip channel is separately configurable.

3. Verify phonebook configuration.

Observe console messages while placing a call. Look for error messages indi-cating phonebook problems, network

problems, voice-coder mismatches, etc.

Chapter 3: Mechanical Installation

and Cabling

Mechanical Installation & Cabling MultiVOIP FXS User Guide

Introduction

When an MVPFXS-8/16/24 unit is to be installed into a rack, two able-bodied persons should participate.

Please read the safety notices before beginning installation.

Safety Warnings

General Safety

This product must be disconnected from its power source and from the telephone network interface when servicing.

Lithium Battery Caution

A lithium battery on the voice/fax channel board provides backup power for the timekeeping capability. The battery has an estimated life expectancy of ten years.

When the battery starts to weaken, the date and time may be incorrect. If the battery fails, the board must be sent back to Multi-Tech Systems for battery replacement.

Warning: There is danger of explosion if the battery is incorrectly replaced.

Ethernet (WAN) Ports Caution

Caution: The Ethernet ports (often labeled “WAN”) are not designed to be connected to a Public Telecommunication Network.

Safety Warnings Telecom

1. Never install telephone wiring during a lightning storm.

2. Never install a telephone jack in wet locations unless the jack is specifically designed for wet locations.

3. This product is to be used with UL and UL listed computers.

4. Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.

5. Use caution when installing or modifying telephone lines.

6. Avoid using a telephone (other than a cordless type) during an electrical storm. There may be a remote risk of electrical shock from lightning.

7. Do not use a telephone in the vicinity of a gas leak.

8. To reduce the risk of fire, use only a UL-listed 26 AWG or larger telecommunication line cord.

MultiVOIP FXS User Guide Mechanical Installation & Cabling

Unpacking Your MultiVOIP

When unpacking your MultiVOIP, check to see that all of the items shown are included in the box. If any box contents are missing, contact MultiTech Tech Support at 1-800-972-2439.

Unpacking the MVPFXS-8/16/24

Cabling

Guide

LNK FDX SPD COL

910

12345678

WAN

11 1 2 13 14 15

16 17 19242322212018

MultiVOIP

Power Boot

Figure 3-1: Unpacking the MVPFXS-8/16/24

Mechanical Installation & Cabling MultiVOIP FXS User Guide

Rack Mounting Instructions for MVPFXS-8/16/24

The MultiVOIPs can be mounted in an industry-standard EIA 19-inch rack enclosure, as shown in Figure 3-2.

Figure 3-2: Rack-Mounting (MVPFXS-8/16/24)

MultiVOIP FXS User Guide Mechanical Installation & Cabling

Safety Recommendations for Rack Installations of MVPFXS-8/16/24

Mounting: Mechanically, this unit is designed for a one-high industry standard EIA 19-inch rack enclosure. The product must be installed by qualified service personnel in a restricted-access area, in accordance with articles 110-16, 10-17, and 110-18 of the National Electrical Code, ANSI/NFPA 70.

• Ensure proper installation of the unit in a closed or multi-unit enclosure by following the recommended installation as defined by the enclosure manufacturer. Do not place the unit directly on top of other equipment or place other equipment directly on top of the unit.

• If installing the unit in a closed or multi-unit enclosure, ensure adequate airflow within the rack so that the maximum recommended ambient temperature is not exceeded.

• Ensure that the unit is properly connected to earth ground by verifying that it is reliably grounded when mounted within a rack. If a power strip is used, ensure that the power strip provides adequate grounding of the attached apparatus.

• When mounting the equipment in the rack, make sure mechanical loading is even to avoid a hazardous condition, such as loading heavy equipment in rack unevenly. The rack used should safely support the combined weight of all the equipment it supports.

• Ensure that the mains supply circuit is capable of handling the load of the equipment. See the power label on the equipment for load requirements (full specifications for MultiVOIP models are presented in chapter 1 of this manual).

• Maximum ambient temperature for the unit is 60 degrees Celsius (140 degrees Fahrenheit) at 20-90% noncondensing relative humidity.

• This equipment should only be installed by properly qualified service personnel.

• Only connect like circuits. In other words, connect SELV (Secondary Extra Low Voltage) circuits to SELV circuits and TN (Telecommunications Network) circuits to TN circuits.

• To reduce the risk of shock, all access doors should be closed during normal operation of the equipment.

Mechanical Installation & Cabling MultiVOIP FXS User Guide

19-Inch Rack Enclosure Mounting Procedure

Attaching the MultiVOIP to a rack-rail of an EIA 19-inch rack enclosure will certainly require two persons. Essentially, the technicians must attach the brackets to the MultiVOIP chassis with the screws provided, as shown in Figure 3-3, and then secure unit to rack rails by the brackets, as shown in Figure 3-4. Because equipment racks vary, screws for rack-rail mounting are not provided. Follow the instructions of the rack manufacturer and use screws that fit.

1. Position the right rack-mounting bracket on the MultiVOIP using the two vertical mounting screw holes.

2. Secure the bracket to the MultiVOIP using the two screws provided.

3. Position the left rack-mounting bracket on the MultiVOIP using the two vertical mounting screw holes.

4. Secure the bracket to the MultiVOIP using the two screws provided.

5. Remove feet (4) from the MultiVOIP unit.

6. Mount the MultiVOIP in the rack enclosure per the rack manufacture’s mounting procedure.

Figure 3-3: Bracket Attachment for Rack Mounting

(MVPFXS-8/16/24)

Figure 3-4: Attaching MultiVOIP to Rack Rail

(MVPFXS-8/16/24)

MultiVOIP FXS User Guide Mechanical Installation & Cabling

Cabling Procedure for MVPFXS-8/16/24

Prerequisites: To complete the MultiVOIP cabling procedure, you must have:

• One RJ-21 Cable. That cable must have a male end to fit the MultiVOIP. The other end must fit your telephony equipment.

• Two common network cables (RJ45-to-RJ45).

Cabling entails connecting:

- the MultiVOIP to ground ,

- the MultiVOIP to power,

- the MultiVOIP to your LAN/WAN network,

- the control computer to your LAN/WAN network,

- the MultiVOIP to your telephone equipment, and

- connecting, optionally, the MultiVOIP Console port to the control computer’s serial port (needed for initial setup only if your system cannot use the voip’s default IP address).

1. Ground Connection. Ensure that the unit is properly connected to an earth ground.

To do this, connect a grounding wire between the chassis grounding screw (see Figure 3-5) and a metallic object that will provide an electrical ground. In some cases, mounting racks will can serve as an adequate earth ground.

Cable hold-down device i s included.

TELECOM251

25 1

RJ-21

The RJ21 50-pin connector can terminate i n either a terminal block, a key system, or a PBX station c ard. In each case, it offers FXS service to phones or fax machines.

CONS OLE WAN

Voip’s Default IP

RJ-45

Connectors

DB-9 Connector to

Computer Serial Port

for Console Functions

Console Port Connection

Grounding

Scr ew

= 192.168.2.1

Grounding

Cable

WAN/Ethernet Connection

VOI P Cont ro l

through

Web GUI

Control Computer’s IP

= 192.168. 2. x

If network configuration makes it

No te :

difficult or impossible to assign the control computer to 192 .168.2.x, then the voip’s IP must be reset using the voip’s Console connection. See

User Guide

for details.

Figure 3-5: Cabling for the MVPFXS-8/16/24

Mechanical Installation & Cabling MultiVOIP FXS User Guide

2. Power Connection. Connect the power cord supplied with your MultiVOIP to a live AC outlet and to the power connector on the back of the MultiVOIP. See Figure 3-5 (top right).

3. VOIP-to-Network Connection. Connect a network cable (RJ45-to-RJ45) to the WAN connector on the back of the MultiVOIP. See Figure 3-5. Connect the other end of the cable to your network switch. The MultiVOIP’s default IP address is 192.168.2.1.

4. Computer-to-Network Connection. Connect a network cable (RJ45-to-RJ45) between your LAN/WAN network and the control computer that you will use to configure/control the MultiVOIP. See Figure 3-5. The control computer’s IP address must be set so that the first three octets of the IP address match that of the MultiVOIP (192.168.2.x).

5. Telephony Connection. Connect a 50-conductor cable (RJ21-to-RJ21) between the MultiVOIP’s TELECOM connector and your telephone equipment. The MultiVOIP requires a male RJ-21 connector. Secure the RJ-21 connector to the TELECOM receptacle with a screw (which is typically built into the connector) and use the hold-down device to secure the cable to the back panel of the MultiVOIP unit. See Figure 3-5. The gender of the RJ-21 connector on the other end of the cable must fit your telephony equipment. Figure 3-6 shows some typical ways in which the other end of the RJ-21 cable might be connected.

to MVPFXS-8/16/24

unit

RJ-21

Key

Phone

System

RJ-11

RJ-21

Terminal

Block

RJ-21

RJ-11

RJ-21

PBX

Station

Card

RJ-11

Figure 3-6: RJ-21 Cabling between MVPFXS unit and FXS phone equipment

MultiVOIP FXS User Guide Mechanical Installation & Cabling

The footprint of the RJ-21 connector is shown in Figure 3-7 and its pin-out list is presented in the table that follows.

RJ-21 Connector

Figure 3-7: RJ-21 Connector Footprint

TIP: on Pins 1 – 24

RING: on Pins 26 - 49

Pin-Out List

Wire Pairs for Each Channel

Channel 1 1 26

Channel 2 2 27

Channel 3 3 28

Channel 4 4 29

Channel 5 5 30

Channel 6 6 31

Channel 7 7 32

Channel 8 8 33

Channel 9 9 34

Channel 10 10 35

Channel 11 11 36

Channel 12 12 37

Channel 13 13 38

Channel 14 14 39

Channel 15 15 40

Channel 16 16 41

Channel 17 17 42

Channel 18 18 43

Channel 19 19 44

Channel 20 20 45

Channel 21 21 46

Channel 22 22 47

Channel 23 23 48

Channel 24 24 49

Pin 25 is not

connected.

Pin 50 is not connected.

√ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √ √

6. Console Connection (optional – not usually needed for initial setup). The Console Cable is needed at initial setup only if your system cannot use the voip’s default IP address. In that case, the Console Cable is needed to change the MultiVOIP’s IP address. Also, if, at a later date, you need to update the MultiVOIP’s firmware, you will need to connect the Console Cable because it is required for that process, as well.

If needed, connect the Console Cable (RJ45 male to DB9 female) between the MultiVOIP and the control PC. Plug the RJ-45 end of the cable into the CONSOLE port of the MultiVOIP and the DB-9 end into a serial port on the PC.

Mechanical Installation & Cabling MultiVOIP FXS User Guide

7. Power-Up. Turn on power to the MultiVOIP by placing the ON/OFF switch on the back panel to the ON position. Wait for the Boot LED on the MultiVOIP to go off before proceeding. This may take a few minutes.

With the connections made, you are ready to contact the web GUI and begin configuring the MultiVOIP.

Proceed to the MultiVOIP & Auxiliary Software chapter for considerations about the Java and browser requirements in relation to the MultiVOIP web GUI.

Chapter 4: MultiVOIP & Auxiliary Software

MultiVOIP & Auxiliary Software MultiVOIP FX User Guide

Introduction

The software (firmware) that runs the MVPFXS-8/16/24 unit resides within the unit and is contacted through a web browser. As such, there is no MultiVOIP configuration software to install. However, the PC operating the web browser GUI must be equipped with an up-to-date version of Java. If an up-to-date version is not already present on the PC, it must be installed from the MultiVOIP CD or from the Java website.

The Java software, the other auxiliary software, and the User Guide are contained on the MultiVOIP product CD. Because the CD is auto-detectable, it will start up automatically when you insert it into your CD-ROM drive. When you have finished loading the Java program, you can view and print the User Guide by clicking on the View Manuals icon.

Java is necessary to operate the MultiVOIP GUI. In addition to Java, other optional 3rd-party software packages are necessary to take advantage of certain optional auxiliary MultiVOIP functions. These include programs for SysLog, FTP, and TFTP.

Summary

Configuring software for your MultiVOIP entails three tasks: (1) loading an up-to-date version of Java onto the PC to enable the web-GUI to operate and, if required, loading other auxiliary software, (2) setting values for telephony and IP parameters that will fit your system (this is “Technical Configuration” and it is discussed in Chapter 5), and (3) establishing “phonebooks” that contain the various dialing patterns for VOIP calls made to different locations (this is “Phonebook Configuration” and it is discussed in Chapter 6).

Chapter 5: Technical Configuration

Technical Configuration MultiVOIP FXS User Guide

Configuring the MultiVOIP

There are two ways in which the MultiVOIP must be configured before operation: technical configuration and phonebook configuration.

Technical Configuration. First, the MultiVOIP must be configured to operate with technical parameter settings that will match the equipment with which it interfaces. There are five types of technical parameters that must be set.

These technical parameters pertain to (1) its operation in an IP network, (2) its operation with telephony equipment, (3) its transmission of voice and fax messages, (4) certain telephony attributes that are common to particular nations or regions, (5) selecting the method by which log reports will be made accessible.

The process of specifying values for the various parameters in these seven categories is what we call “technical configuration” and it is described in this chapter.

Phonebook Configuration. The second type of configuration that is required for the MultiVOIP pertains to the phone number dialing sequences that it will receive and transmit when handling calls. Dialing patterns will be affected by both the PBX/telephony equipment and the other VOIP devices that the MultiVOIP unit interacts with. We call this “Phonebook Configuration,” and, for analog MultiVOIP units, it is described in Chapter 6. The Quick Start Guide chapter presents additional information on phonebook setup.

Local/Remote Configuration. The MultiVOIP is configured through a web browser. The MultiVOIP is factory configured to this IP address:

Certain functions (like update/upgrade of firmware version) and changing the MultiVOIP’s IP address can be done locally via a hard-wired connection between a PC serial port and the MultiVOIP’s “Console” port.

192.168.2.1.

MultiVOIP FXS User Guide Technical Configuration

Configuration by Web GUI

This manual primarily describes configuration of the MultiVOIP with the web GUI.

Pre-Requisites

To complete the configuration of the MultiVOIP unit, you must know several things about the overall system.

Before configuring your MultiVOIP Gateway unit, you must know the values for several IP and telephone parameters that describe the IP network system and telephony system (PBX or telco central office equipment) with which the digital MultiVOIP will interact. A summary of this configuration information appears on page 56 (“Config Info CheckList”).

IP Parameters

The following parameters must be known about the network (LAN, WAN, Internet, etc.) to which the MultiVOIP will connect:

Ask your computer network



administrator.

• IP Address

• IP Mask

• Gateway

• Domain Name Server (DNS) Info

Write down the values for these IP parameters. You will need to enter these values in the “IP Parameters” screen in the Configuration section of the MultiVOIP software. You must have this IP information about every VOIP in the system.

IP Network Parameters: Record for each VOIP Site in System

Info needed to operate:

all MultiVOIP models.

Technical Configuration MultiVOIP FXS User Guide

Telephony Interface Parameters

The following parameters must be known about the PBX or telco central office equipment to which the analog MultiVOIP will connect:

Phone Parameters



Ask phone company or telecom manager.

• Which interface type is to be used?

FXS Loop Start only

• If FXS, determine whether the line will be used for a phone, fax, KTS (key telephone system), or perhaps serve a station card on a PBX.

Config Info CheckList

Type of Configuration Info Gathered

IP Info for voip unit

● IP address

Telephony Interface Parameters:

Record for this VOIP Site

MultiVOIP Configuration screen on which to enter the Info

IP Parameters

Info

Obtained

√

Info

Entered

√

● Gateway

● DNS IP (if used)

Interface Type (FXS only * )

*In FXO/FXS systems, channels used for phone, fax, or key system are FXS; channels used for analog PBX extensions or analog telco lines are FXO.

Country Code Regional

Interface Parameters.

Parameters

Reminder: Be sure to Save & Apply after entering configuration values.

MultiVOIP FXS User Guide Technical Configuration

Procedure for Configuration by Web GUI (Summary)

After the MultiVOIP configuration software has been installed in the ‘Command’ PC (which is connected to the MultiVOIP unit), several steps must be taken to configure the MultiVOIP to function in its specific setting. Although the summary below includes all of these steps, some are optional.

1. Check Power and Cabling.

2. Start MultiVOIP web-based Configuration Program.

3. Confirm Connection.

4. Familiarize yourself with configuration parameter screens and how to access them.

5. Set IP Parameters.

6. Set Voice/Fax Parameters.

7. Set Telephony Interface Parameters.

8. Set SIP Call Signaling parameters.

9. Set Regional Parameters (Phone Signaling Tones & Cadences and setup for built-in Remote Configuration/Command Modem).

10. Set Log Reporting Method (GUI, locally in MultiVOIP Configuration program; or SMTP, via email).

11. View System Info screen and set updating interval (optional).

12. Set Packetization Time.

13. Save the MultiVOIP configuration.

When technical configuration is complete, you will need to configure the MultiVOIP’s inbound and outbound phonebooks in the Phonebook Configuration chapter.

Local Configuration Procedure (Detailed)

You can begin the configuration process after assuring that an up-to-date browser and up-to-date Java application are present on your computer. You can establish your configuration or modify it at any time by contacting the web-GUI through a browser.

1. Check Power and Cabling. Be sure the MultiVOIP is turned on and connected to the computer via the WAN/Ethernet connection (this entails RJ-45 cabling between MultiVOIP and the WAN/Ethernet network).

2. Start MultiVOIP Configuration Program. Launch the MultiVOIP program from a web browser. The default IP address assigned to the MultiVOIP is 192.168.2.1. However, this address can be changed by connecting the PC to the MultiVOIP’s Console port and using a communications program

Technical Configuration MultiVOIP FXS User Guide

Operation of MultiVOIP through web GUI requires up-to-date version of Java. If Java has not yet been installed, follow these instructions:

A. Install up-to-date Java program from MultiVOIP product CD (on first use only).

B. Open web browser.

C. Browse to IP address of MultiVOIP unit.

D. If username and password have been established, enter them when when prompted.

E. Set browser to allow pop-ups. The MultiVOIP Web GUI makes extensive use of pop-up windows

to access screens and commands.

3. Confirm Connection. When the PC is in communication with the MultiVOIP through the web browser, you will see an icon for each voip channel in the lower left corner of the screen. The icon is green when the channel is in use and red when idle.

4. Configuration Parameter Groups: Getting Familiar, Learning About Access. The first part of

configuration concerns IP parameters, Voice/FAX parameters, Telephony Interface parameters, Call Signaling parameters, Regional parameters, Logs/Traces, System Information, and Packetization Time. In the MultiVOIP software, these eight types of parameters are grouped together under “Configuration” and each has its own dialog box for entering and viewing values.

To access the dialog box for these parameter groups, click on the name of the parameter group in the sidebar menu of the browser.

MultiVOIP FXS User Guide Technical Configuration

5. Set IP Parameters. Click on IP Parameters in the sidebar list.

In each field, enter the values that fit your particular network.

Technical Configuration MultiVOIP FXS User Guide

The IP Parameters fields are described in the tables and text passages below. Note that both DiffServ parameters (Call Control PHB and VoIP Media PHB) must be set to zero if you enable Packet Prioritization (802.1p). Nonzero DiffServ values negate the prioritization scheme.

IP Parameter Definitions

Field Name Values Description

Ethernet Parameters

Frame Type Type II, SNAP Must be set to match network’s frame type. Default is Type II.

DiffServ Parameter fields

DiffServ PHB (Per Hop Behavior) values pertain to a differential prioritizing system for IP packets as handled by DiffServ-compatible routers.

values, each with an elaborate technical description. These descriptions are found in TCP/IP standards RFC2474, RFC2597, and, for present 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). Before using values other than these default values of 34 and 46, consult these standards documents and/or a qualified IP telecommunications engineer.

To disable DiffServ, configure both fields to 0 decimal.

There are 64

The passage following this table explains DiffServ in the context of the IP datagram.

Call Control PHB

Voip Media PHB

IP Parameter fields

Gateway Name

Enable DHCP Y/N

IP Address 4-places, 0-255 The unique LAN IP address assigned to the MultiVOIP.

IP Mask 4-places, 0-255

Gateway

0 – 63 default = 34 .

0 – 63 default = 46 n

alphanumeric Descriptor of current voip unit to distinguish it from other units in

disabled by default

4-places, 0-255. The IP address of the device that connects your MultiVOIP to the

Value is used to prioritize call setup IP packets.

Value is used to prioritize the RTP/RTCP audio IP packets.

system.

Dynamic Host Configuration Protocol is a method for assigning IP

address and other IP parameters to computers on the IP network in a

single message with great flexibility. IP addresses can be static or

temporary depending on the needs of the computer.

Subnetwork address that allows for sharing of IP addresses within a LAN.

Internet.

MultiVOIP FXS User Guide Technical Configuration

The IP Datagram with Header, Its Type-of-Service field, & DiffServ

bits =>

0 4 8 16 19 24 31 VERS HLEN

IDENTIFICATION

TIME TO LIVE PROTOCOL HEADER CHECKSUM

TYPE OF SERVICE

FLAGS

SOURCE IP ADDRESS

DESTINATION IP ADDRESS

IP OPTIONS (if any) PADDING …

DATA

…

TOTAL LENGTH

FRAGMENT OFFSET

end of header

The TOS field consists of eight bits, of which only the first six are used. These six bits are called the “Differentiated Service Codepoint” or DSCP bits.

The Type of Service or “TOS” field

0 1 2 3 4 5 6 7

PRECEDENCE D T R

unused

three precedence have eight values, 0-7, ranging from “normal” precedence (value of 0) to “network control” (value of 7).

When set, the D bit requests low delay, the T bit requests high throughput, and the R bit requests high reliability.

Routers that support DiffServ can examine the six DSCP bits and prioritize the packet based on the DSCP value. The DiffServ Parameters fields in the MultiVOIP IP Parameters screen allow you to configure the DSCP bits to values supported by the router. Specifically, the Voip Media PHB field relates to the prioritizing of audio packets (RTP and RTCP packets) and the Call Control PHB field relates to the prioritzing of non-audio packets (packets concerning call set-up and tear-down, gatekeeper registration, etc.).

The MultiVOIP Call Control PHB parameter defaults to 34 decimal (22 hex; 100010 binary – consider vis-à-vis TOS field above) for Assured Forwarding behavior. The MultiVOIP Voip Media PHB parameter defaults to the value 46 decimal (2E hex; 101110 binary – consider vis-à-vis TOS field above). To disable DiffServ, configure both fields to 0 decimal.

IP Parameter Definitions (cont’d)

Field Name Values Description

DNS Parameter fields

Enable DNS Y/N

Default = disabled

DNS Server IP Address

FTP Parameter fields

FTP Server Enable

4-places, 0-255. IP address of specific DNS server to be used to resolve Internet

Y/N

Default = enabled

See “FTP Server File Transfers” in

Operation & Maintenance

chapter.

Enables Domain Name Space/System function where computer names are resolved using a worldwide distributed database.

computer names.

MultiVOIP unit has an FTP Server function so that firmware and other important operating software files can be transferred to the voip via the network.

Technical Configuration MultiVOIP FXS User Guide

8. Set Voice/FAX Parameters. Click on Voice/FAX in the sidebar list.

In each field, enter the values that fit your particular network.

MultiVOIP FXS User Guide Technical Configuration

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 other channels by using the Copy Channel button and its dialog box.

The Voice/FAX Parameters fields are described in the tables below.

Voice/Fax Parameter Definitions

Field Name Values Description

Default --

When this button is clicked, all Voice/FAX parameters are set to their default values.

Select Channel

Copy Channel

1-24 1-16 1-8

Channel to be configured is selected here. The “-24” unit has 24 channels, the “-16” unit has 16 channels, and the “-8” unit has 8 channels.

Copies the Voice/FAX attributes of one channel to another channel. Attributes can be copied to multiple channels or all channels at once.

Voice Gain -- Signal amplification (or attenuation) in dB. Input Gain

Output Gain

+31dB to –31dB

+31dB to

Modifies audio level entering voice channel before it is sent over the network to the remote VOIP. The default & recommended value is 0 dB.

Modifies audio level being output to the device attached to the voice channel. The default and recommended value is 0 dB.

–31dB DTMF Parameters Duration

(DTMF) DTMF

In/Out of Band

Out of Band Mode

60 –

3000 ms

Out of

Band, or

Inband

RFC

2833,

SIP Info

When DTMF: Out of Band is selected, this setting determines how long each DTMF digit ‘sounds’ or is held. Default = 100 ms.

When DTMF Out of Band is selected, the MultiVOIP detects DTMF tones at its input and regenerates them at its output. When DTMF Inband is selected, the DTMF digits are passed through the MultiVOIP unit as they are received.

RFC2833 method. Uses an RTP mode defined in RFC 2833 to transmit the DTMF digits.

SIP Info method. Generates dual tone multi frequency (DTMF) tones on the telephony call leg. The SIP INFO message is sent along the signaling path of the call.

You must set this parameter per the capabilities of the remote endpoint with which the voip will communicate. The RFC2833 method is the more common of the two methods.

Technical Configuration MultiVOIP FXS User Guide

Voice/Fax Parameter Definitions (cont’d)

Coder Parameters

Coder Manual or

Auto-

matic

Determines whether selection of coder is manual or automatic. When Automatic is selected, the local and remote voice channels will negotiate the voice coder to be used by selecting the highest bandwidth coder supported by both sides without exceeding the Max Bandwidth setting. G.723, G.729, or G.711 are negotiated.

Selected Coder

G.711 a/u

law 64

kbps;

G.726, @

32 kbps;

G.723.1 @

6.3 kbps;

G.729,

8kbps;

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. Here 64K of digital voice are compressed to 6.3K, allowing several simultaneous conversations over the same bandwidth that would otherwise carry only one.

To make selections from the Selected Coder drop-down list, the Manual option must be enabled.

Max bandwidth (coder)

AutoCall Parameters

11 – 128

kbps

This field lets you specify the maximum bandwidth allowed for this channel.

If coder is to be selected automatically (“Auto” setting), then enter a value for maximum bandwidth.

Auto Call AutoCall The AutoCall option enables the local MultiVOIP to call a remote

MultiVOIP without the user having to dial a Phone Directory Database number. As soon as you access the local MultiVOIP voice/fax channel, the MultiVOIP immediately connects to the remote MultiVOIP identified in the Phone Number box of this option.

This function applies on a channel-by-channel basis. It would not be appropriate for this function to be applied to a channel that serves in a pool of available channels for general phone traffic. This function requires an entry in the Outgoing phonebook of the local MultiVOIP and a matched setting in the Inbound Phonebook of the remote voip.

Phone Number

-- Phone number used for Auto Call function or Offhook Alert Timer

function. This phone number must correspond to an entry in the Outbound Phonebook of the local MultiVOIP and in the Inbound Phonebook of the remote MultiVOIP (unless a gatekeeper unit is used in the voip system).

MultiVOIP FXS User Guide Technical Configuration

Voice/Fax Parameter Definitions (cont’d) )

Field Name Values Description

Dynamic Jitter

Dynamic Jitter Buffer

Dynamic Jitter defines a minimum and a maximum jitter

value for voice communications. When receiving voice packets from a remote

MultiVOIP, varying delays between

packets may occur due to network traffic problems. This is called Jitter. To compensate, the MultiVOIP uses a Dynamic Jitter Buffer. The Jitter Buffer enables the MultiVOIP to wait for delayed voice packets by automatically adjusting the length of the Jitter Buffer between configurable minimum and maximum values. The length of the jitter buffer directly effects the voice delay between

MultiVOIP gateways.

Minimum Jitter Value

20 to 400

The minimum dynamic jitter buffer of 20 milliseconds is the minimum delay that would be acceptable over a low jitter network. Default = 20 msec

Maximum Jitter Value

20 to 200

The maximum dynamic jitter buffer of 200 milliseconds is the maximum delay tolerable over a high jitter network. Default = 200 msec

Initial Jitter Value

20 – 200

default =

20 ms

The starting value (in ms) of the Jitter Buffer. This value will change itself from the starting value depending on the needs of the jitter buffer. For example, if you set the initial value at 100, it may end up scaling itself down to 20 or up to 200 to meet the needs of operating conditions.

Technical Configuration MultiVOIP FXS User Guide

Voice/Fax Parameter Definitions (cont’d) )

Field Name Values Description

Auto Disconnect

Automatic

-- The Automatic Disconnection group provides four options Disconnection

Jitter Value 1-65535

milliseconds

Call Duration

Consecutive

1-65535 seconds

1-65535 Consecutive Packets Lost defines the number of consecutive

Packets Lost

Network Disconnection

1 to 65535 seconds; Default = 300 sec.

which can be used singly or in any combination.

The Jitter Value defines the average inter-arrival packet deviation (in milliseconds) before the call is automatically disconnected. The default is 300 milliseconds. A higher value means voice transmission will be more accepting of jitter. A lower value is less tolerant of jitter. Inactive by default. When active, default = 300 ms. However, value must equal or exceed Dynamic Minimum Jitter Value.

Call Duration defines the maximum length of time (in seconds) that a call remains connected before the call is automatically disconnected. Inactive by default. When active, default = 180 sec. This may be too short for most configurations, requiring upward adjustment.

packets that are lost after which the call is automatically disconnected. Inactive by default. When active, default = 30

Specifies how long to wait before disconnecting the call when IP network connectivity with the remote site has been lost.

Advanced Features

Silence

Compression

Echo Cancellation

Y/N

Y/N Determines whether echo cancellation is enabled (checked) for this

Determines whether silence compression is enabled (checked) for this voice channel.

With Silence Compression enabled, the MultiVOIP will not transmit voice packets when silence is detected, thereby reducing the amount of network bandwidth that is being used by the voice channel. Default = on.

voice channel.

Echo Cancellation removes echo and improves sound quality. Default = on.

MultiVOIP FXS User Guide Technical Configuration

7. Set Telephony Interface Parameters. Click on Interface in the sidebar list.

In each field, enter the values that fit your particular network.

The kinds of parameters for which values must be chosen depend on which type of telephony supervisory signaling or interface is used (only FXS Loop Start is supported in the MVPFXS units). The parameters for the FXO interface are grayed out on the MultiVOIP web GUI screen and are not discussed further in this manual.

Technical Configuration MultiVOIP FXS User Guide

Note that Interface parameters are applied on a channel-by-channel basis. However, once you have established a set of Interface parameters for a particular channel, you can apply this entire set of Interface parameters to other channels by using the Copy Channel button and its dialog box.

MultiVOIP FXS User Guide Technical Configuration

FXS Loop Start Parameters. The parameters applicable to FXS Loop Start are shown in the figure below and described in the table that follows.

FXS Loop Start Interface: Parameter Definitions

Field Name Values Description

Select Channel 1-8 (MVPFXS-8);

1-16 (MVPFXS-16); 1-24 (MVPFXS-24)

Interface Type FXS Loop Start The value of this field determines whether this channel uses the FXS

FXS Options fields

Ring Count , FXS

Current Loss Y/N

Flash Detection Range fields

Min/Max for Min. and Max., 50

1-99

- 1500 milliseconds

Indicates the voip channel to which parameter values will be assigned.

Loop Start interface type or the FXO interface type. We are here discussing the FXS Loop Start option.

Maximum number of rings that the MultiVOIP will issue before giving up the attempted call.

When enabled, the MultiVOIP will interrupt loop current in the FXS circuit to initiate a disconnection. This tells the device connected to the FXS port to hang up. The Multi-VOIP cannot drop the call; the FXS device must go on hook.

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.

Technical Configuration MultiVOIP FXS User Guide

FXS Loop Start Interface: Parameter Definitions (cont’d)

Field Name Values Description

Caller ID fields

Type Bellcore

Enable Y/N

Dialing Options fields

Regeneration Pulse, DTMF Indicates which type of dialing must be regenerated, either pulses or

Inter Digit Timer

Inter Digit Regeneration Timer

1 - 10 seconds This is the length of time that the MultiVOIP will wait between digits.

in milliseconds

The MultiVOIP currently supports only one implementation of Caller ID. That implementation is Bellcore type 1 with Caller ID placed between the first and second rings of the call. Caller ID information is a description of the remote calling party received by the called party. The description has three parts: name of caller, phone number of caller, and time of call. The ‘time-of-call’ portion is always generated by the receiving MultiVOIP unit (on FXS channel) based on its date and time setup.

In general, the forms of the ‘Caller Name’ and ‘Caller Phone Number’ differ depending on the IP transmission protocol used (H.323, SIP, or SPP) and upon entries in the phonebook screens of the remote (CID generating) voip unit. For MVPFXS units, only the SIP-related Caller ID options are available. The CID Name and Number appearing on the phone at the terminating FXS end will come either from a central office switch (showing a PSTN phone number), or the phonebook of the remote (CID sending) voip unit.

DTMF. For MVPFXS units, DTMF is always used.

When the time expires, the MultiVOIP will look in the outbound phonebook for the number entered and place the call accordingly.

Default = 2.

The length of time between the outputting of DTMF digits. Default = 100 ms.

The Caller ID feature has dependencies on both the telco central office and the MultiVOIP phone book. See the diagram series after the FXO Parameters section below.

MultiVOIP FXS User Guide Technical Configuration

The Caller ID feature has dependencies on both the telco central office and the MultiVOIP phone book. See the diagram series below.

Call is received

here.

xxxyyyzzzz J.Q. Public

Display shows:

FXS

CID

Terminating

VoIP

Clock:

5-31,

1:42pm

CID Number: 763-555-8794

CID Flow

Network

SIP

Protocol

CID

Generating

VoIP

FXO

standard telephony

Central Office

with

Caller ID service

Call originates here at 1:42pm, May 31.

xxxyyyzzzz J.Q. Public

phone of:

Melvin Jones 763-555-8794

CID Name: Melvin Jones

Time Stamp: Date: 05/31 Time:1:42pm

Figure 5-1: Voip Caller ID Case #1 – Call, through telco central office with standard CID, enters

voip system

Call is received

here.

xxxyyyzzzz J.Q. Public

Display shows:

FXS

CID

Terminating

VoIP

Clock:

10/03, 4:51pm

CID Flow

Network

CID

Generating

VoIP

Ch2

Ch3

Ch4

Ch1 401

402

403

404

FXS

xxxyyyzzzz J.Q. Public

phone of:

Call originates here

at 4:51pm, Oct 3.

Nigel Thurston 763-555-9401

CID Number: 423 CID Name: Anoka-Whse-VP3 Time Stamp: Date: 10/03

Time: 4:51pm

Phone Book Configuration

Gateway Name:

Q.931 Parameters

Gatekeeper RAS Parameters

Anoka-Whse-VP3

Remove Prefix Add Prefix Forward/Addr

Inbound Phone Book

423

748

{Channel 1}

Figure 5-2: Voip Caller ID Case #2 – Remote FXS call on SIP voip system

Technical Configuration MultiVOIP FXS User Guide

8. Set Call Signaling Parameters. Click on Call Signaling in the sidebar list.

MultiVOIP FXS User Guide Technical Configuration

The table below describes all fields in the Call Signaling screen.

Call Signaling Parameter Definitions

Field Name Values Description

SIP Parameters

Signaling Port numeric Port number on which the MultiVOIP UserAgent software module will

be waiting for any incoming SIP requests. Default = 5060

Use SIP Proxy Y/N Allows the MultiVOIP to work in conjunction with a proxy server.

Proxy Parameters

Proxy Domain Name / IP Address

Append SIP Proxy Domain Name in User ID

Port Number Logical port number for proxy communications.

User Name Values: alphanumeric

Password Values: alphanumeric

ReRegistration Time

n.n.n.n where n=0-255

Y/N When checked, the domain name of the SIP Proxy serving the MultiVOIP

Description: Identifier used when proxy server is used in network. If a proxy server is

used in a SIP voip network, all clients must enter both a User Name and a Password before being allowed to make a call.

Description: Password for proxy server function. See “User Name” description above.

Values: numeric (in seconds)

Description: This is the timeout interval for registration of the MultiVOIP with a SIP

proxy server. The time interval begins the moment the MultiVOIP gateway registers with the SIP proxy server and ends at the time specified by the user in the ReRegistration Time field (this field). When/if registration lapses, call traffic routed to/from the MultiVOIP through the SIP proxy server will cease. However, calls in progress will continue to function until they end.

Network address of the proxy server that the voip is using.

gateway will be included as part of the User ID for that gateway. If unchecked, the SIP Proxy’s IP address will be included as part of the User ID instead of the SIP Proxy’s domain name.

Technical Configuration MultiVOIP FXS User Guide

9. Set Regional Parameters (Phone Signaling Tones & Cadences). Click on Regional in the sidebar list.

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), ring tone, and other, more specialized tones.

In the Country/Region field, select the option that fits your particular system. When you choose a Country, you choose an entire set of tones and those tones cannot be altered. To create a nonstandard set of tones, use the “Custom” option.

MultiVOIP FXS User Guide Technical Configuration

The Regional Parameters fields are described in the table below.

“Regional Parameter” Definitions

Field Name Values Description

Country/ Region

Standard Tones fields

Type column

Frequency 1 freq. in Hertz Lower frequency of pair.

Frequency 2 freq. in Hertz

Cadence (msec) On/Off

Gain 1

Gain 2

Australia, Central America, Chile, Europe, France, Japan, UK, USA, Custom

dial tone, ring tone, busy tone, unobtainable tone (fast busy), survivability tone, re-order tone

n/n/n/n four integer time values in milli-seconds; zero value for dial-tone indicates continuous tone

gain in dB +3dB to –31dB and “mute” setting

Name of a country or region that uses a certain set of tone pairs for

dial tone, ring tone, busy tone, unobtainable tone (fast busy tone), and

re-order tone (a tone pattern indicating the need for the user to hang up the phone).

In some cases, the tone-pair scheme denoted by a country name may also be used outside of that country. The “Custom” option (button) assures that any tone-pairing scheme worldwide can be accommodated.

Type of telephony tone-pair for which frequency, gain, and cadence are being presented.

Higher frequency of pair.

On/off pattern of tone durations used to denote phone ringing, phone busy, connection unobtainable (fast busy), dial tone (“0” indicates continuous tone), survivability, and re-order. Default values differ for different countries/regions. Although most cadences have only two parts (an “on” duration and an “off” duration), some telephony cadences have four parts. Most cadences, then, are expressed as two iterations of a two-part sequence. Although this is redundant, it is necessary to allow for expression of 4-part cadences.

Amplification factor of lower frequency of pair. This applies to the dial, ring, busy and ‘unobtainable’ tones that the MultiVOIP outputs as audio to the FXS or FX0 port. Default: -16dB

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 or FXO port.

Default: -16dB

Technical Configuration MultiVOIP FXS User Guide

After selecting the appropriate Country/Region for your system, click OK. A screen will appear confirming that the configuration has been updated.

You must select Save and Apply in the sidebar menu to make the change permanent.

10. Set Log Reporting Method. The Logs screen lets you choose how the VoIP administrator will receive log reports about the MultiVOIP’s performance and the phone call traffic that is passing through it. Log reports can be received in one of two ways:

A. as Console Messages accessible through a telecommunications program like HyperTerminal,

B. through a SysLog Server program.

Click Logs/Traces on the sidebar menu to access the Logs/Traces screen.

MultiVOIP FXS User Guide Technical Configuration

The Logs/Traces screen will appear.

If you enable console messages, you can customize the types of messages to be included/excluded in log reports by clicking on the “Filters” button and using the Console Messages Filter Settings screen (see subsequent page). If you use the logging function, select the logging option that applies to your VoIP system design. If you intend to use a SysLog Server program for logging, click in that Enable check box. The common SysLog logical port number is 514.

“Logs” Screen Definitions

Field Name Values Description

Enable Console Messages

Filters (button) Click to access secondary screen on where console messages can be included/excluded by

SysLog Server Enable

IP Address n.n.n.n

Port 514 Logical port for SysLog Server. 514 is commonly used.

Online Statistics

Update Interval

Y/N

for n= 0-255

integer Set the interval (in seconds) at which logging information will be updated.

Allows MultiVOIP debugging messages to be read via a basic terminal program like

HyperTerminal ™ or equivalent. Normally, this should be disabled because it uses

MultiVOIP processing resources. Console messages are meant for tech support personnel.

category and on a per-channel basis. (See the Console Messages Filter Settings screen on

subsequent page.)

This box must be checked if logging is to be done in conjunction with a SysLog Server

program. For more on SysLog Server, see Operation & Maintenance chapter.

IP address of computer, connected to voip network, on which SysLog Server program is

running.

Technical Configuration MultiVOIP FXS User Guide

To customize console messages by category and/or by channel, click on “Filters” and use the Console Messages Filters Settings screen.

MultiVOIP FXS User Guide Technical Configuration

11. View System Information screen and set updating interval (optional).

To reach this dialog box, click System Information in the sidebar menu.

This screen presents vital system information at a glance. Its primary use is in troubleshooting.

System Information Parameter Definitions

Field Name Values Description

Boot Version

nn.nn Indicates the version of the code that is used at the startup (booting)

of the voip. The boot code version is independent of the software version.

Firmware Version

alphanumeric

Indicates version of MultiVOIP firmware.

Technical Configuration MultiVOIP FXS User Guide

System Information Parameter Definitions (cont’d)

Field Name Values Description

Configuration Version

Phone Book Version

MSP Version

Kernel Version

Mac Address

Up Time days:

nn.nn.nn. nn alphanumeric

numeric Indicates the version of the inbound and outbound phonebook

Indicates version of MultiVOIP Configuration software (which includes screens for IP Parameters, SMTP Parameters, Regional Parameters, etc.).

portion of the MultiVOIP software.

nn.nn alphanumeric

Vn_nn_ n.n

alphanumeric

Version of DSP (digital signal processor) software used in MultiVOIP.

Linux kernel version used in MultiVOIP.

Denotes the number assigned as the voip unit’s unique Ethernet address.

Indicates how long the voip has been running since its last booting.

hours: mm:ss

The frequency with which several administrative screens are updated (the System Information, Call Progress, and IP Statistics screens) is determined by a setting in the Logs/Traces screen.

MultiVOIP FXS User Guide Technical Configuration

12. About Packetization Time.

You can use the Packetization Time screen to specify definite packetization rates for coders selected in the Voice/FAX Parameters screen (in the “Coder” group of fields). The Packetization Time screen is accessible in the sidebar list of the main voip software screen. In dealing with RTP parameters, the Packetization Time screen is closely related to both Voice/FAX Parameters and to IP Statistics.

Packetization Time Screen

Technical Configuration MultiVOIP FXS User Guide

Packetization rates can be set separately for each channel.

The table below presents the ranges and increments for packetization rates.

Packetization Ranges and Increments

Coder Types Range (in ms);

{default value}

Increments (in ms)

G711 A-law 5-30 {30} 5 G711 u-law 5-60 {60} 10 G723 30-60 {60} 10 G726 5-60 {60} 10 G729 10-80 {80} 20

Once the packetization rate has been set for one channel, it can be copied into other channels by using the Copy Channel screen.

MultiVOIP FXS User Guide Technical Configuration

13. Saving the MultiVOIP Configuration. When values have been set for all of the MultiVOIP’s various operating parameters, click on Save & Apply in the sidebar.

NOTE: It is possible to return all parameters to their factory default values by using the Restore Factory

Defaults command. By restoring factory-default values, this command will negate all configuration work that has been done.

Chapter 6: Phonebook Configuration

Phone Book Configuration MultiVOIP FXS User Guide

Configuring MultiVOIP Phonebooks

When a VoIP serves a PBX system, it’s important that the operation of the VoIP be transparent to the telephone end user. That is, the VoIP should not entail the dialing of extra digits to reach users elsewhere on the network that the VoIP serves. On the contrary, VOIP service more commonly reduces dialed digits by allowing users (served by PBXs in facilities in distant cities) to dial their co-workers with 3-, 4-, or 5-digit extensions as if they were in the same facility.

Furthermore, the setup of the VoIP generally should allow users to make calls on a non-toll basis to any numbers accessible without toll by users at all other locations on the VoIP system. Consider, for example, a company with VOIP-equipped offices in New York, Miami, and Los Angeles, each served by its own PBX. When the VOIP phone books are set correctly, personnel in the Miami office should be able to make calls without toll not only to the company’s offices in New York and Los Angeles, but also to any number that’s local in those two cities.

To achieve transparency of the VoIP telephony system and to give full access to all types of non-toll calls made possible by the VOIP system, the VoIP administrator must properly configure the “Outbound” and “Inbound” phone-books of each VoIP in the system.

The “Outbound” phonebook for a particular VoIP unit describes the dialing sequences required for a call to originate locally (typically in a PBX in a particular facility) and reach any of its possible destinations at remote VoIP sites, including non-toll calls completed in the PSTN at the remote site.

The “Inbound” phonebook for a particular VoIP unit describes the dialing sequences required for a call to originate remotely from any other VOIP sites in the system, and to terminate on that particular VOIP.

Briefly stated, the MultiVOIP’s Outbound phonebook lists the phone stations it can call; its Inbound phonebook describes the dialing sequences that can be used to call that MultiVOIP and how those calls will be directed. (Of course, the phone numbers are not literally “listed” individually, but are, instead, described by rule.)

Consider two types of calls in the three-city system described above: (1) calls originating from the Miami office and terminating in the New York (Manhattan) office, and (2) calls originating from the Miami office and terminating in New York City but off the company’s premises in an adjacent area code, an area code different than the company’s office but still a local call from that office (e.g., Staten Island).

The first type of call requires an entry in the Outbound PhoneBook of the Miami VOIP and a coordinated entry in the Inbound phonebook of the New York VOIP. These entries would allow the Miami caller to dial the New York office as if its phones were extensions on the Miami PBX.

The second type of call similarly requires an entry in the Outbound PhoneBook of the Miami VOIP and a coordinated entry in the Inbound Phonebook of the New York VOIP. However, these entries will be longer and more complicated. Any Miami call to New York City local numbers will be sent through the VOIP system rather than through the regular toll public phone system (PSTN). But the phonebook entries can be arranged so that the VOIP system is transparent to the Miami user, such that even though that Miami user dials the New York City local number just as they would through the public phone system, that call will still be completed through the VOIP system.

This PhoneBook Configuration procedure is brief, but it is followed by an example case. For many people, the example case may be easier to grasp than the procedure steps. Configuration is not difficult, but all phone number sequences and other information must be entered exactly; otherwise connections will not be made.

Phone Book Configuration MultiVOIP FXS User Guide

Phonebook configuration screens are accessed using the sidebar menu.

1. Select Outbound Phone Book/List Entries. Fields in the “Details” section describe various SIP parameters.

Click Add.

MultiVOIP FXS User Guide Phone Book Configuration

2. The Outbound Phone Book Add Entry screen appears.

Enter Outbound PhoneBook data for your MultiVOIP unit.

Phone Book Configuration MultiVOIP FXS User Guide

The fields of the Outbound Phone Book Add Entry screen are described in the table below.

Outbound Phone Book Add Entry screen: Field Definitions

Field Name Values Description

Accept Any Number

Destination Pattern

Total Digits as needed This field currently disabled.

Remove Prefix dialed digits Portion of dialed number to be removed before completing call to destination.

Add Prefix dialed digits Digits to be added before completing call to destination.

IP Address n.n.n.n

Description alpha-

Y/N When checked, “Any Number” appears as the value in the Destination Pattern

field.

The Any Number feature works differently depending on whether or not an external SIP Proxy routing device is used.

When no external routing device is used. If Any Number is selected, calls to phone numbers not matching a listed Destination Pattern will be directed to the IP Address in the Outbound Phone Book Add Entry screen. “Any Number” can be used in addition to one or more Destination Patterns.

When external routing device is used. If Any Number is selected, calls to phone numbers not matching a listed Destination Pattern will be directed to the external SIP proxy routing device. The IP Address of the external routing device must be set in the Phone Book Configuration screen.

prefixes, area codes, exchanges, line numbers, extensions

for n = 0-255

numeric

Defines the beginning of dialing sequences for calls that will be connected to another VOIP in the system. Numbers beginning with these sequences are diverted from the PTSN and carried on Internet or other IP network.

Number of digits the phone user must dial to reach specified destination.

The IP address to which the call will be directed if it begins with the destination pattern given.

Describes the facility or geographical location at which the call will be completed.

MultiVOIP FXS User Guide Phone Book Configuration

Outbound Phone Book Add Entry screen: Field Definitions (cont’d)

Field Name Values Description

SIP Fields

Use Proxy Y/N Select if proxy server is used.

Transport Protocol

SIP Port Number

SIP URL sip.userphone

TCP or

UDP

5060 or other

*See RFC 3087

(“Control of

Service

Context using

SIP Request-

URI,” by the

Network

Working

Group).

@ hostserver,

where

“userphone”

is the

telephone

number and

“hostserver”is

the domain

name or an

address on the

network

Voip administrator must choose between UDP and TCP transmission protocols. UDP is a

high-speed, low-overhead connectionless protocol where data is transmitted without

acknowledgment, guaranteed delivery, or guaranteed packet sequence integrity. TCP is

slower connection-oriented protocol with greater overhead, but having acknowledgment

and guarantees delivery and packet sequence integrity.

The SIP Port Number is a UDP logical port number. The voip will “listen” for SIP messages at this logical port. If SIP is used, 5060 is the default, standard, or “well known” port number to be used. If 5060 is not used, then the port number used is that specified in the SIP Request URI (Universal Resource Identifier).

Looking similar to an email address, a SIP URL identifies a user's address.

In SIP communications, each caller or callee is identified by a SIP url: sip:user_name@host_name. The format of a sip url is very similar to an email address, except that the “sip:“ prefix is used.

Phone Book Configuration MultiVOIP FXS User Guide

3. Select Inbound PhoneBook | List Entries.

Click Add.

4. The Inbound Phone Book Add Entry screen appears.

MultiVOIP FXS User Guide Phone Book Configuration

Enter Inbound PhoneBook data for your MultiVOIP. The fields of the Inbound Phone Book Add Entry screen are described in the table below.

Inbound Phone Book Add Entry screen:

Field Definitions

Field Name Values Description

Accept Any Number

Remove Prefix dialed digits portion of dialed number to be removed before completing call to destination

Add Prefix dialed digits digits to be added before completing call to destination

Channel Number

Values: Y/N

Description: When checked, “Any Number” appears as the value in the Remove Prefix field.

The Any Number feature of the Inbound Phone Book does not work when an external routing device is used (Proxy for SIP protocol).

When no external routing device is used. If Any Number is selected, calls received from phone numbers not matching a listed Prefix (shown in the Remove Prefix column of the Inbound Phone Book) will be admitted into the voip on the channel listed in the Channel Number field. “Any Number” can be used in addition to one or more Prefixes.

1-24, or “Hunting” or 1-8 or 1-16 depending on model

Channel number to which the call will be assigned as it enters the local telephony equipment . “Hunting” directs the call to any available channel.

Description -- Describes the facility or geographical location at which the call originated.

Y/N

*Must be enabled in Call Signaling

Configuration

screen.

When checked, the value in the Remove Prefix field will be registered with the external SIP proxy routing device. The IP address of the external routing device must be set in the Phone Book Configuration screen.

In a SIP voip system, gateways can register with the SIP Proxy.

Phone Book Configuration MultiVOIP FXS User Guide

5. When your Outbound and Inbound PhoneBook entries are completed, click on Save and Apply in the sidebar menu to save your configuration.

You can change your configuration at any time as needed for your system.

There are two “Edit Entry” screens for revising outbound and inbound phone book entries.

The “Next Entry” and “Previous Entry” buttons allow you to go from one entry to the next without interruption. You must click OK to confirm the change before moving on to the next entry.

MultiVOIP FXS User Guide Phone Book Configuration

Phonebook Examples

The following example demonstrates how Outbound and Inbound PhoneBook entries work in a situation of multiple area codes (as in the Minneapolis metro area). This example also illustrates that MVPFXS voips allow remote callers access only to specific phone stations connected to the MVPFXS voip and do not allow remote callers access to the local PSTN in which the MVPFXS unit is located. Consider a company with offices in Minneapolis and Baltimore. The system depicted is SIP-only. In the Minneapolis office, an MVPFX2-8 unit is used and it affords both FXS and FXO interfaces. By contrast, in the Baltimore office, an MVPFXS-24 voip is used adn it offers the FXS interface only.

2 Site Example

Notice first the area code situation in those two cities: Minneapolis’s local calling area consists of multiple adjacent area codes; Baltimore’s local calling area consists of a base area code plus an overlay area code area code 443), but, since the voip used in Baltimore is FXS-only, it does not offer access to the local PSTN. That is, Minneapolis voip callers can call phone stations in the Baltimore office only; they cannot call into the 410 or 443 area codes using the voip system.

Company

VOIP/PBX

Site

Suburbs

763

SW Suburbs

952

Mpls

61 2

St. Pau l

& Suburbs

651

...

Company Office

ha s M VP FXS - 2 4 V OI P

with FXS Terminal Block

Baltimore

410

Phone Book Configuration MultiVOIP FXS User Guide

An outline of the equipment setup in both offices is shown below.

Local-Call

Area Codes:

612, 651,

952

Company HQ. Minneapolis North Sub. area 763

-5174

-5173

-5172

PBX

-5171

717-5170

VoIP

MVPFX2-8

200.2.10.3

Network



Baltimore Sales Ofc. area 410

R o u t e r

VoIP

MVPFXS-24

200.2.9.7

FXS

Termina l

Block

325-7001

-7003

-7002

MultiVOIP FXS User Guide Phone Book Configuration

The screen below shows Outbound PhoneBook entries for the VOIP located in the company’s Baltimore facility.

The entries in the Minneapolis VOIP’s Inbound PhoneBook match the Outbound PhoneBook entries of the Baltimore VOIP, as shown below.

Phone Book Configuration MultiVOIP FXS User Guide

To call the Minneapolis/St. Paul area, a Baltimore employee must dial eleven digits.

If a Baltimore employee dials any phone number in the 612 area code, the call will automatically be handled by the company’s voip system. Upon receiving such a call, the Minneapolis voip will remove the digits “1612”. But before the suburban-Minneapolis voip can complete the call to the PSTN of the Minneapolis local calling area, it must dial “9” (to get an outside line from the PBX) and then a comma (which denotes a pause to get a PSTN dial tone) and then the 10-digit phone number which includes the area code (612 for the city of Minneapolis; which is different than the area code of the suburb where the PBX is actually located -- 763).

A similar sequence of events occurs when the Baltimore employee calls number in the 651 and 952 area codes because number in both of these area codes are local calls in the Minneapolis/St. Paul area.

The simplest case is a call from Baltimore to a phone within the Minneapolis/St. Paul area code where the company’s voip and PBX are located, namely 763. In that case, that local voip removes 1763 and dials 9 to direct the call to its local 7-digit PSTN.

Finally, consider the longest entry in the Minneapolis Inbound Phonebook, “17637175. Note that the main phone number of the Minneapolis PBX is 763-717-5170. The destination pattern 17637175 means that all calls to Minneapolis employees will stay within the suburban Minneapolis PBX and will not reach or be carried on the local PSTN.

MultiVOIP FXS User Guide Phone Book Configuration

Similarly, the Inbound PhoneBook for the Baltimore VOIP (shown first below) generally matches the Outbound PhoneBook of the Minneapolis VOIP (shown second below).

Each entry corresponds to a phone station of the Baltimore voip. This phonebook arrangement allows Minneapolis users to contact Baltimore co-workers as though they were in the Minneapolis facility, using numbers in the range 7001 to 7024.

The Outbound PhoneBook for the Minneapolis VOIP is shown below. The destination pattern, “7” lets Minneapolis employees call Baltimore co-workers using only local-appearing extensions.

Because the VOIP in Baltimore is FXS-only, Minneapolis VOIP users cannot call numbers in the local Baltimore PSTN through the VOIP system. Minneapolis VOIP users can only use the VOIP system to call Baltimore phones connected to the FXS terminal block in Baltimore.

Phone Book Configuration MultiVOIP FXS User Guide

Configuring Mixed Digital/Analog VOIP Systems

Analog MultiVOIP units, like the MVPFXS-8/16/24, MVPFX2-2/4/8, and the MVP210/410/810/410SS/810SS units are compatible with digital MultiVOIP units like the MVP2410. In many cases, digital and analog VOIP units will appear in the same telephony/IP system. In addition to MVP210/410/810 MultiVOIP units (Series II units), legacy analog VOIP units (Series I units made by MultiTech) may be included in the system, as well. When legacy VOIP units are included, the VOIP administrator must handle two styles of phonebooks in the same VOIP network. The diagram below shows a small-scale system of this kind: one digital VOIP (the MVP2410) operates with a Series II analog VOIP (an MVP410), and two Series I legacy VOIPs (two MVP200 units) and an MVPFXS-24.

Digital & Analog VOIPs

EXAMPLE:

in Same System

Site D:

Pierre, SD

Area Code 615

PSTN

Cheyenne, WY

Area Code 307

444

CH24

CH2

FXS

422

FXO

Series #2 Analog MultiVOIP

Port #4

FXS Port

CO Port

Site E:

200.2.9.6

Analog MultiVOIP

MVPFXS-24

CH1

421

Site F:

Lincoln, NE

Area Code 402

200.2.9.5

MVP410

FXS Ports

CO Ports

Key System

200.2.9.9

Digital

VoIP

MVP2410

Router

Network

PBX

615-492-3100

Series #1 Analog MultiVOIP

(Server/Client Phonebook)

Unit

#200

Series #1 Analog MultiVOIP

(Server/Client Phonebook)

Unit

#100

(Holds phonebook for both

Series #1 analog VOIPs.)

Other extensions

x3101 - x3199

Bismarck, ND

Area Code 701

MVP200

200.2.9.7 Client

MVP200

200.2.9.8 Host

Site A:

CH1

Site B:

Rochester, MN Area Code 507

CH2

CH1

FXS

FXO

FXS

201

102

717-5000

Other extensions

x7401 - x7429

402-263-7400

PSTN

507-717-5792

Suburban Rochester

The Series I analog VOIP phone book resides in the “Host” VOIP unit at Site B. It applies to both of the Series I analog VOIP units.

The Series II analog MultiVOIP (the MVP410) requires its own inbound and outbound phonebooks. The MVP2410 digital MultiVOIP requires its own inbound and outbound phonebooks, also, as does the MVPFXS-24 unit.

Site C:

MultiVOIP FXS User Guide Phone Book Configuration

These seven phone books are shown below.

Phone Book for Series I Analog VOIP Host Unit (Site B)

VOIP Dir #

IP Address Channel Comments

-ORDestination Pattern

102 200.2.9.8 2 Site B, FXS channel.

101 200.2.9.8 1 Site B, FXO channel.

4xx 200.2.9.6 1 Site E FXS channel.

201 200.2.9.7 1 Site A, FXS channel.

1615 xxx

200.2.9.9 0 (Note 2.)

Gives remote voip users access to local PSTN of Site D (Pierre, SD, area code 615).

xxxx

3xxx

(Note 1.)

1402 xxx

200.2.9.9 0 Allows remote voip users to call all PBX

extensions at Site D (Pierre, SD) using only four digits.

200.2.9.5 0 Gives remote voip users access to local PSTN

of Site F (Lincoln, NE; area code 402). xxxx (Note 1.)

140226374xx

(Note 1)

200.2.9.5 0 Gives remote voip users access to key phone system extensions at Site F (Lincoln).

(Note 3)

Note 1. The “x” is a wildcard character.

Note 2. By specifying “Channel 0,” we instruct the MVP2400/2410 to choose any

available data channel to carry the call.

Note 3. Note that Site F key system has only 30 extensions (x7400-7429). This

destination pattern (140226374xx) actually directs calls to 402-263-7430 through 402-263-7499 into the key system, as well. This means that such calls, which belong on the PSTN, cannot be completed. In some cases, this might be inconsequential because an entire exchange (fully used or not) might have been reserved for the company or it might be unnecessary to reach those numbers. However, to specify only the 30 lines actually used by the key system, the destination pattern 140226374xx would have to be replaced by three other destination patterns, namely 1402263740xx, 1402263741xx, and 1402263742xx. In this way, calls to 402-263-7430 through 402-263-7499 would be properly directed to the PSTN. In the Site D outbound phonebook, the 30 lines are defined exactly, that is, without making any adjacent phone numbers unreachable through the voip system.

Phone Book Configuration MultiVOIP FXS User Guide

Outbound Phone Book for MVP2410 Digital VOIP

Destin. Pattern

Remove Prefix

Add Prefix

(Site D)

IP Address

Comment

201 200.2.9.7 To originate calls to Site A (Bismarck). 1507 1507 101#

Note 3.

200.2.9.8 To originate calls to Rochester local PSTN using the FXO channel (channel #1) of the Site B VOIP.

102 200.2.9.8 To originate calls to phone connected to

FXS port (channel #2) of the Site B VOIP.

4 200.2.9.6 Calls to Site E (Cheyenne). 1402 200.2.9.5 Calls to Lincoln area local PSTN (via

FXO channel, CH4, of the Site F VOIP).

1402 263 740 1402

200.2.9.5

Calls to extensions (thirty) of key system at Site F (Lincoln). Human operator or auto-attendant is needed to complete

200.2.9.5

these calls.

263 741 1402

200.2.9.5 263 742 Note 3. The pound sign (“#”) is a delimiter separating the VOIP number from the standard telephony phone number.

Remove Prefix

Add Prefix

1615 9,

Note 4. Note 5.

1615

31 0,

49231

Inbound Phonebook for MVP2410 Digital VOIP (Site D)

Channel Number

(hunting)

Comment

Allows phone users at remote voip sites to call non-toll numbers within the Site D area code (615; Pierre, SD) over the VOIP network. Allows voip calls directly to employees at Site D (at extensions x3101 to x3199).

Note 4. “9” gives PBX station users access to outside line.

Note 5. The comma represents a one-second pause, the time required for the user

to receive a dial tone on the outside line (PSTN). The comma is only allowed in the Inbound phonebook.

100

Multi-Tech Systems MVPFXS-24, MVPFXS-8, MVPFXS-16 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual