Multi-Tech Systems Multivoip Model Mvp400/800 Voice/fax Over Ip Networks User Guide

							11 Chapter 1 - Introduction and Description
option.  You can not mix the Proprietary PhoneBook with the Gatekeeper.  If you choose the
Gatekeeper option, interoperability is less of a concern and you can communicate with other third
party endpoints that support H.323 (e.g., Microsoft Netmeeting).  (2) If you choose the Proprietary
PhoneBook, you establish a master-slave relationship in that the master MultiVOIP maintains the
phone directory database.  All of the phone numbers are listed in the data base so that if you want to
communicate with someone in your VOIP network, you can see the phone number in your data base.
Everytime you bring up your MultiVOIP the current phone directory is downloaded to your MultiVOIP.
The Gatekeeper is a separate application that can operate on a network pc and provides all the
controls needed to create, control, and manage an H.323 network zone.  The H.323 network zone is
all the endpoints (terminals and gateways (MultiVOIPs)) that register with the gatekeeper. The
gatekeeper functions are address translation from LAN aliases for terminals and gateways to IP
addresses as defined in the RAS (Registration/Admission/Status) specification.  The RAS Protocol
defines the communication with a gatekeeper and support for RTP/TRCP for sequencing audio
packets. The H.323 Gatekeeper also provides call-authorization for both accepting and placing calls
in its zone, handles hunting (call-rollover), and certain monitoring features (i.e., call permissioning
and address resolution).
So, if you choose the Gatekeeper option, initially you need to communicate with the administrator of
the Gatekeeper to preregister your MultiVOIP.  The information you need from the Gatekeeper
administrator is the IP address of the Gatekeeper and its port number.  Then you need to establish
your alias address which includes phone number, channel number, H323 ID which is a name, e-mail
like address, etc, and your MultiVOIP LAN IP address.  The port number is 1720, but if the
Gatekeeper uses a different port number, you have to ensure that you use the same port number.
The Gatekeeper administrator will then enter your information into the Gatekeeper data base. This
concludes the preregisteration.
Now, you can enter your alias address information into the Add/Edit Phone Entry dialog box.  For
example, if you were setting up the corporate MultiVOIP, you could enter the following information for
Voice Channel 1.  For instance, in our typical application channel 1 of the Corporate MultiVOIP uses
extension 101.  The Description is optional, but can be helpful if it is assigned to a particular individual
or department, or in this case it defines the channel interface.  The H323 ID that was assigned to this
phone number is an e-mail like address which identifies the individual that is using this extension and
the domain name of the Gatekeeper (in this example corporatehd).  The IP Address of the Corporate
MultiVOIP is 201.022.122.118 and the default port number 1720 is used.
So now when you “come alive”, the Gatekeeper will register you with the above alias address.  No
other H323 endpoint can use this alias.  This is like your own telephone number.
Now, if you choose the Proprietary PhoneBook option in the Phone Directory Database dialog box
instead of the Gatekeeper option, the Database Type group would become active and the RAS
Parameters group is inactive (greyed out).   
						

							12 MultiVOIP 400/800 User Guide
Now, lets change the typical application to not have the Gatekeeper control the call session.  When
you elect to use the Proprietary PhoneBook, you set up a master-slave relationship.  This relationship
allows one MultiVOIP to maintain the Phone Directory Database and publish this data base to all
MultiVOIP participants in the network.  This proprietary data base allows you to see all the
participants in your network and provides you with there phone numbers.
Lets again use the corporate MultiVOIP and we will set up the database so that the corporate
MultiVOIP can call the sales, marketing, or regional offices. To do this, the Phone Directory Database
will have four entries for the corporate office, and two entries for the sales office, two for the
marketing office and two for the regional office. Extension 101 at the corporate office is tied to voice
channel 1, 102 is tied to channel 2, etc.  The Description again ties to the type of interface used on
the corporate MultiVOIP (E&M).  The Hunt Group in this situation is set for No Hunt.  But if you
wanted to activate a Hunt Group, i.e., if an extension on the MultiVOIP is busy and you wanted to
look for another extension, you can assign a hunt group to those extensions.  So that, say extension
101 is busy, the corporate MultiVOIP would roll over to extension 102.
Again, the IP Address of the corporate MultiVOIP needs to be added and the port number is 1720.
This adds phone number 101 of the corporate MultiVOIP to the proprietary data base.  Now, to add
extension 102 to the proprietary data base, all you have to do is change the Phone Number and
Description to support channel 2 of the corporate MultiVOIP.  After you have added channel 2, you
need to include the two entries for each office.
The proprietary data base would then appear as in the following dialog box and when the office
MultiVOIP is turned on, the current data base would be down loaded.     
						

							13 Chapter 1 - Introduction and Description
Front Panel Description
The front panel contains three groups of LEDs that provide the status of the Ethernet connection,
Voice/Fax channels, and general status of the MultiVOIP. The front panel is shown in Figure 1-3, and
a description of each LED follows.
Figure 1-3. Front Panel
ETHERNET
RCVReceive Data indicator blinks when packets are being received from the local area
network.
LNKLink indicator lights when the Ethernet link senses voltage from a concentrator or
external device.
XMTTransmit Data indicator blinks when packets are being transmitted to the local area
network.
COLCollision indicator lights when a collision is detected on the Ethernet link.
VOICE/FAX CHANNEL
FXSForeign Exchange Station indicator lights when the voice/fax channel is configured for
FXS operation.
FXOForeign Exchange Office indicator lights when the voice/fax channel is configured for
FXO operation.
E&MEar and Mouth indicator lights when the voice/fax channel is configured for E&M
operation.
FAXFax indicator lights when there is fax traffic on the voice/fax channel.
XMTTransmit indicator blinks when voice packets are being transmitted to the local area
network.
RCVReceive indicator blinks when voice packets are being received from the local area
network.
XSGTransmit Signal indicator lights when the FXS-configured channel is off-hook, the FXO-
configured channel is receiving a ring from the Telco, or the M lead is active on the E&M
configured channel (i.e., the MultiVOIP is receiving a ring from the PBX).
RSGReceive Signal indicator lights when the FXS-configured channel is ringing, the FXO-
configured channel has taken the line off-hook, or the E lead is active on the E&M-
configured channel.
BOOT (BTG)
The BTG indicator lights when the MultiVOIP is booting or downloading setup.
POWER (PWR)
The Power indicator lights when power is applied to the MultiVOIP. 
						

							14 MultiVOIP 400/800 User Guide
Back Panel Description
The cable connections for the MultiVOIP are made at the back panel. Connectors include Power,
Command Port (RS232), Ethernet (10BASE-T), and Voice/Fax Channels (E&M, FXO and FXS). The
cable connectors are shown in Figure 1-4 and defined in the following groups.
 +,	 +, +,	 +,  +,	 +,
-	*
.
+,

/
0
-	*
.
+,

/

-	*
.
+,

/
(
-	*
.
+,

/

-	*
.
+,

/
%
-	*
.
+,

/

-	*
.
+,

/
#
-	*
.
+,

/



/


/1

/0

/(

/%

/#

/

/

/.-2#)

/
.-2#)
3
/
	45	
,2
	5	**.-2#)5	6
*
	74 
48	*	
,
- *

	5	*
*
 +,	 +,
Figure 1-4. Back Panel
Power Connector
The Power connector is used to connect the external power supply to the MultiVOIP. The Power
connector is a 7-pin circular DIN connector. A separate power cord is connected to the power supply
and the live AC grounded outlet.
Command Port Connector
The Command Port connector is used to configure the MultiVOIP using a PC with a serial port and
running Windows® software. The Command Port connector is a DB-25 female connector.
10Base-T (Ethernet) Connector
The Ethernet 10Base-T connector is used to connect the MultiVOIP to a LAN using unshielded
twisted cable. This connector is a keyed RJ-45 jack.
Voice/Fax Channel
The Voice/Fax channel connectors include three options per channel: E&M, FXO and FXS.
E&M - This connector is used if you are connecting VOICE/FAX CHANNEL _ to the E&M trunk on a
PBX. This connector is an RJ-45 jack.
FXO - This connector is used if you are connecting VOICE/FAX CHANNEL _ to the station side of a
PBX. This connector is an RJ-11 jack.
FXS - This connector is used if you are connecting VOICE/FAX CHANNEL _ to a station device, etc.,
an analog telephone, KTS telephone system, or fax machine. This connector is an RJ-11 jack. 
						

							15 Chapter 1 - Introduction and Description
Specifications
 One 1 Meg by 32 byte at 70 nanosecond SIMM is 4 Mb DRAM
Caution: SIMM speed and size cannot be mixed
 Two Meg of flash memory
Ethernet Port
 Single Ethernet Interface - 10Base-T (twisted pair) keyed RJ-45 connector.
Command Port
 Single 19.2 Kbps asynchronous Command Port with a DB-25 female connector
Voice/Fax Channel
 Two RJ-11 jacks (FXO and FXS)
 One RJ-45 jack (E&M)
Electrical/Physical
 Voltage - 115 VAC (Standard), 240 Volts AC (Optional)
 Frequency - 47 to 63 Hz
 Power Consumption - 18 Watts
 Dimensions - 3.75 high x 17.4 wide x 8 deep
8.9cm high x 44.2cm wide x 20.3cm deep
 Weight - 7.4 pounds (3.4 kg) 
						

							16 MultiVOIP 400/800 User Guide 
						

							Chapter 2 - Installation 
						

							18 MultiVOIP 400/800 User Guide
Installing Your MultiVOIP
The basic steps of installing your MultiVOIP 400/800 network involve unpacking the units, connecting
the cables, and configuring the units using management software (MultiVOIP Configuration). This
process results in a fully functional Voice Over IP network. A general description is provided below
and detailed instructions are provided in Chapter 3, Software Loading and Configuration.
Installing and Configuring Your MultiVOIP
The VOIP administrator must first install the MultiVOIP 400/800 software and then configure each
MultiVOIP 400/800 for its specific function. During the configuration process, it’s important to note
that the Phone Directory Database is configured differently depending on whether or not you have
Gatekeeper support on your VOIP network.
If your VOIP network supports Gatekeeper software, you must pre-register or remotely register all
H.323 endpoints with the Gatekeeper.  The procedure for doing this is explained in the section
“Registering with a Gatekeeper Phone Directory.”
If your VOIP network does not have Gatekeeper software or the Gatekeeper software is not enabled,
then you must build a proprietary phonebook with a “Master” MultiVOIP and “Slave” MultiVOIPs. The
“Master” unit includes the assignment of a unique LAN IP address, subnet mask, and Gateway IP
address; as well as the selection of appropriate channel interface type for each of the Voice/Fax
channels. Once all connections have been made, the VOIP administrator configures the unit and
builds the Phone Directory Database that will reside with the Master unit.
Once configuration of the “Master” MultiVOIP has been completed, the administrator moves on to
configure the MultiVOIP(s) designated as “Slave” units.  Again, unique LAN IP addresses, subnet
masks, and Gateway IP addresses are assigned, and each Voice/Fax channel is configured for the
appropriate channel interface type. When this is done, the Phone Directory Database option is set to
Slave, and the IP address of the Master MultiVOIP is entered. Once all Slave units are configured,
the process moves on to the “Deploying the VOIP Network” section.
Deploying the VOIP Network
The final phase of the installation is deployment of the network. When the remote MultiVOIPs are
sent to their remote sites, the remote site administrators need only to connect the units to their LAN
and telephone equipment. A full Phone Directory Database (supplied by the Master MultiVOIP
Proprietary Phonebook will be loaded into their units within minutes of being connected and powered
up. For remote VOIPs that were configured with the Gatekeeper option enabled, each MultiVOIP will
be remotely or pre-registered with the Gatekeeper (i.e., the Gatekeeper phonebook directory is NOT
downloaded to the remote units). The final task of the VOIP administrator or the Gatekeeper
administrator is to develop the VOIP Dialing Directory based on the appropriate phone directory
database (i.e., the Proprietary phonebook database or the Gatekeeper phonebook database).
Safety Warning Telecom
1. Never install telephone wiring during a lighting storm.
2. Never install telephone jacks in wet locations unless the jack is specifically designed for wet
locations.
3. This product is to be used with UL and cUL 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 rist of electrical shock from lighting.
7. Do not use the telephone to report a gas leak in the vicinity of the leak.
8. To reduct the risk of fire, use only No. 26 AWG or larger telecommunications line cord. 
						

							19 Chapter 2 - Installation
Unpacking Your MultiVOIP
Remove all items from the box.
9992:;2:Voice/Fax over IP Networks
Figure 2-1. Unpacking
Safety Warnings
Caution: Danger of explosion if battery is incorrectly replaced.
A lithium battery on the voice/fax channel board provides backup power for the time keeping
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 Sytems for battery replacement.
The E&M, FXS, and Ethernet ports are not designed to be connected to a Public Telecommunication
Network.
Valid VOIP Network Connections
The following VOIP network interface connections (calls) can be made.
  FXS to FXS
  FXS to E&M
  FXS to FXO
  FXO to FXO
  FXO to FXS
  FXO to E&M
  E&M to E&M
  E&M to FXS
  E&M to FXO 
						

							20 MultiVOIP 400/800 User Guide
Cabling Procedure
 Cabling involves connecting the master MultiVOIP to your LAN and telephone equipment.
1. If you are connecting any Voice/Fax Channel to an E&M trunk other than type 2, perform the
E&M Jumper Block Positioning procedure before connecting power to the unit.
2. Connect one end of the power supply to a live AC outlet and connect the other end to the
MultiVOIP as shown in Figure 2-2. The power connector is a 7-pin circular DIN connector.
 +,	 +, +,	 +,  +,	 +,-	*
.
+,

/
0-	*
.
+,

/
-	*
.
+,

/
(-	*
.
+,

/
-	*
.
+,

/
%-	*
.
+,

/
-	*
.
+,

/
#-	*
.
+,

/



/

/1
/0
/(
/%
/#
/
/
/.-2#)
/
.-2#)
3
/
	45	
,2
	5	**.-2#)5	6
*
	74 
48	*	
,
- *

	5	*
*
 +,	 +,
Ethernet Connection
Command Port Connection
Power ConnectionFXS
FXO E&M
FXSE&M
FXO
PSTN
Voice/Fax Channel 1 - 8
          Connections
Figure 2-2.  Cable Connections
3. Connect the MultiVOIP to a PC by using a DB-25 (male) to DB-9 (female) cable. Plug the DB-25
end of the cable into the Command port of the MultiVOIP and the other end into the PC serial
port. See Figure 2-2.
4. Connect a network cable to the ETHERNET 10BASET connector on the back of the MultiVOIP.
Connect the other end of the cable to your network.
5. If you are connecting a station device (e.g., analog telephone, fax machine, or Key Telephone
System (KTS) to your MultiVOIP, connect one end of an RJ11 phone cord to the Voice/Fax
Channel 1 FXS connector on the back of the MultiVOIP and the other end to the station device.
If you are connecting the station side of a telephone switch (PBX) to your MultiVOIP, connect one
end of an RJ11 phone cord to the Voice/Fax Channel 1 FXO connector on the back of the
MultiVOIP and the other end to the phone jack.
If you are connecting an E&M trunk from a telephone switch to your MultiVOIP, connect one end
of an RJ45 phone cord to the Voice/Fax Channel 1 E&M connector on the back of the MultiVOIP
and the other end to the trunk. Refer to Appendix B for E&M cabling pinout.
If you are connecting to an E&M trunk, you need ensure that the E&M trunk jumper is in the
correct position for the E&M type trunk.  The default E&M jumper position is E&M type 2.  To
change the E&M jumper position, perform the E&M jumper block positioning procedure.
6. Repeat the above step to connect the remaining telephone equipment to each Voice/Fax
Channel on your MultiVOIP.
7. Turn on power to the MultiVOIP by placing the ON/OFF switch on the back panel to the ON
position. Wait for the BTG LED on the MultiVOIP to go OFF before proceeding. This may take a
couple of minutes to go OFF.
Proceed to the next section to load the MultiVOIP software.