Multi-Tech Systems Multivoip 200 Model Mvp200 Voice/fax Over Ip Networks User Guide

							71 Chapter 6 - Warranty, Service and Tech Support
The Multi-Tech BBS
For customers who do not have Internet access, Multi-Tech maintains a bulletin board system (BBS).
Information available from the BBS includes new product information, product upgrade files, and
problem-solving tips. The phone number for the Multi-Tech BBS is (800) 392-2432 (USA and
Canada) or (612) 785-3702 (international and local).
The BBS can be accessed by any asynchronous modem operating at 1200 bps to 56K bps at a
setting of 8 bits, no parity, and 1 stop bit (8-N-1).
To Log on to the Multi-Tech BBS
1. Set your communications program to 8-N-1.
2. Dial our BBS at (800) 392-2432 (USA and Canada) or (612) 785-3702 (international and
local).
3. At the prompts, type your first name, last name, and password; then press ENTER. If you are
a first time caller, the BBS asks if your name is spelled correctly. If you answer yes, a
questionnaire appears. You must complete the questionnaire to use the BBS on your first
call.
4. Press ENTER until the Main Menu appears. From the Main Menu you have access to two
areas: the Files Menu and News. For help on menu commands, type ?.
To Download a File
If you know the file name
1. From the Main Menu, type F to access the Files Menu, then type D.
2. Enter the name of the file you wish to download from the BBS.
3. If a password is required, enter the password.
4. Answer Y or N to the automatic logoff question.
5. Select a file transfer protocol by typing the indicated letter, such as Z for Zmodem (the
recommended protocol).
6. If you select Zmodem, the transfer will begin automatically. If you select another protocol, you
may have to initiate the transfer yourself. (In most data communications programs, the PAGE
DOWN key initiates the download.)
7. When the download is complete, press ENTER to return to the File Menu.
8. To exit the BBS, type G and press ENTER.
If you don’t know the file name
1. From the Main Menu, type F to access the Files Menu. For a list of file areas, type L, press
ENTER, then type L and press ENTER again. (If you do not type the second 
L, you will list all
of the files on the BBS.)
2. Mark each file area you would like to examine by typing its list number and pressing ENTER.
3. Enter L to list all the files in the selected file areas. Enter C to go forward in the file list and P
to go back.
4. To mark one or more files for download, type M, press ENTER, type the list numbers of the
files, and press ENTER again.
5. Enter D. You will see a list of the files you have marked. Enter E if you would like to edit the 
						

							72 MultiVOIP 200 User Guide
list; otherwise enter D again to start the download process.
6. Select a file transfer protocol by typing the indicated letter, such as Z for Zmodem (the
recommended protocol).
7. If you select Zmodem, the file will transfer automatically. If you select another protocol, you
may have to initiate the transfer yourself. (In most data communications programs, the PAGE
DOWN key initiates the download.)
About the Internet
If you prefer to receive technical support via the Internet, you can contact Tech Support via e-mail at
the following address:
http://www.multitech.com\_forms\email_tech_support.htm
Multi-Tech’s presence includes a Web site at:
http://www.multitech.com
and an ftp site at:
ftp://ftp.multitech.com
The ftp server mirrors the Multi-Tech BBS. 
						

							Voice / Fax over IP Networks
Appendixes 
						

							74 MultiVOIP 200 User Guide
Appendix A - TCP/IP (Transmission Control Protocol/Inter-
net Protocol) Description
TCP/IP is a protocol suite and related applications developed for the U.S. Department of Defense in
the 1970s and 1980s specifically to permit different types of computers to communicate and
exchange information with one another. TCP/IP is currently mandated as an official U.S. Department
of Defense protocol and is also widely used in the UNIX community.
Before you install TCP/IP on your network, you need to establish your Internet addressing strategy.
First, choose a domain name for your company. A domain name is the unique Internet name, usually
the name of your business, that identifies your company. For example, Multi-Tech’s domain name is
multitech.com ( .com indicates this is a commercial organization; .edu denotes educational
organizations, .gov denotes government organizations). Next, determine how many IP addresses
you’ll need. This depends on how many individual network segments you have, and how many
systems on each segment need to be connected to the Internet. You’ll need an IP address for each
network interface on each computer and hardware device.
IP addresses are 32 bits long and come in two types: network and host. Network addresses come in
five classes: A, B, C, D, and E. Each class of network address is allocated a certain number of host
addresses. For example, a class B network can have a maximum of 65,534 hosts, while a class C
network can have only 254. The class A and B addresses have been exhausted, and the class D and
E addresses are reserved for special use. Consequently, companies now seeking an Internet
connection are limited to class C addresses.
Early IP implementations ran on hosts commonly interconnected by Ethernet local area networks
(LAN). Every transmission on the LAN contains the local network, or medium access control (MAC),
address of the source and destination nodes. The MAC address is 48-bits in length and is non-
hierarchical; MAC addresses are never the same as IP addresses.
When a host needs to send a datagram to another host on the same network, the sending application
must know both the IP and MAC addresses of the intended receiver. Unfortunately, the IP process
may not know the MAC address of the receiver. The Address Resolution Protocol (ARP), described
in RFC 826 (located at ftp://ds.internic.net/rfc/rfc826.txt) provides a mechanism for a host to
determine a receiver’s MAC address from the IP address. In the process, the host sends an ARP
packet in a frame containing the MAC broadcast address; and then the ARP request advertises the
destination IP address and asks for the associated MAC address. The station on the LAN that
recognizes its own IP address will send an ARP response with its own MAC address. An ARP
message is carried directly in an IP datagram.
Other address resolution procedures have also been defined, including those which allow a diskless
processor to determine its IP address from its MAC address (Reverse ARP, or RARP), provides a
mapping between an IP address and a frame relay virtual circuit identifier (Inverse ARP, or InARP),
and provides a mapping between an IP address and ATM virtual path/channel identifiers (ATMARP).
The TCP/IP protocol suite comprises two protocols that correspond roughly to the OSI Transport and
Session Layers; these protocols are called the Transmission Control Protocol and the User Datagram
Protocol (UDP). Individual applications are referred to by a port identifier in TCP/UDP messages. The
port identifier and IP address together form a “socket”. Well-known port numbers on the server side
of a connection include 20 (FTP data transfer), 21 (FTP control), 23 (Telnet), 25 (SMTP), 43 (whois),
70 (Gopher), 79 (finger), and 80 (HTTP).
TCP, described in RFC 793 ( ftp://ds.internic.net/rfc/rfc793.txt) provides a virtual circuit (connection-
oriented) communication service across the network. TCP includes rules for formatting messages,
establishing and terminating virtual circuits, sequencing, flow control, and error correction. Most of
the applications in the TCP/IP suite operate over the “reliable” transport service provided by TCP.
UDP, described in RFC 768 (ftp://ds.internic.net/rfc/rfc768.txt) provides an end-to-end datagram
(connectionless) service. Some applications, such as those that involve a simple query and 
						

							75 Appendix A - TCP/IP Description
response, are better suited to the datagram service of UDP because there is no time lost to virtual
circuit establishment and termination. UDP’s primary function is to add a port number to the IP
address to provide a socket for the application.
The Application Layer protocols are examples of common TCP/IP applications and utilities, which
include:
• Telnet (Telecommunication Network): a virtual terminal protocol allowing a user logged on to
one TCP/IP host to access other hosts on the network, described in RFC 854 ( ftp://
ds.internic.net/rfc/rfc854.txt).
• FTP: the File Transfer Protocol allows a user to transfer files between local and remote host
computers per IETF RFC 959 ( ftp://ds.internic.net/rfc/rfc959.txt).
• Archie: a utility that allows a user to search all registered anonymous FTP sites for files on a
specified topic.
• Gopher: a tool that allows users to search through data repositories using a menu-driven,
hierarchical interface, with links to other sites, per RFC 1436 ( ftp://ds.internic.net/rfc/
rfc1436.txt).
• SMTP: the Simple Mail Transfer Protocol is the standard protocol for the exchange of
electronic mail over the Internet, per IETF RFC 821 ( ftp://ds.internic.net/rfc/rfc821.txt).
• HTTP: the Hypertext Transfer Protocol is the basis for exchange of information over the
World Wide Web (WWW). Various versions of HTTP are in use over the Internet, with HTTP
version 1.0 (per RFC 1945) ( ftp://ds.internic.net/rfc/rfc1945.txt) being the most current.
• HTML: WWW pages are written in the Hypertext Markup Language (HTML), an ASCII-based,
platform-independent formatting language, per IETF RFC 1866 ( ftp://ds.internic.net/rfc/
rfc1866.txt).
• Finger: used to determine the status of other hosts and/or users, per IETF RFC 1288 ( ftp://
ds.internic.net/rfc/rfc1288.txt).
• POP: the Post Office Protocol defines a simple interface between a user’s mail reader
software and an electronic mail server; the current version is POP3, described in IETF RFC
1460 ( ftp://ds.internic.net/rfc/rfc1460.txt).
• DNS: the Domain Name System defines the structure of Internet names and their association
with IP addresses, as well as the association of mail, name, and other servers with domains.
• SNMP: the Simple Network Management Protocol defines procedures and management
information databases for managing TCP/IP-based network devices. SNMP, defined by RFC
1157 ( ftp://ds.internic.net/rfc/rfc1157.txt) is widely deployed in local and wide area network.
SNMP Version 2 (SNMPv2), per RFC 1441< ftp://ds.internic.net/rfc/rfc1441.txt) adds security
mechanisms that are missing in SNMP, but is also more complex.
• Ping: a utility that allows a user at one system to determine the status of other hosts and the
latency in getting a message to that host. Ping uses ICMP Echo messages.
• Whois/NICNAME: Utilities that search databases for information about Internet domain and
domain contact information, per RFC 954 ( ftp://ds.internic.net/rfc/rfc954.txt).
• Traceroute: a tool that displays the route that packets will take when traveling to a remote
host. 
						

							76 MultiVOIP 200 User Guide
Internet Protocol (IP)
IP is the Internet standard protocol that tracks Internetwork node addresses, routes outgoing
messages and recognizes incoming messages, allowing a message to cross multiple networks on
the way to its final destination. The IPv6 Control Protocol (IPV6CP) is responsible for configuring,
enabling, and disabling the IPv6 protocol modules on both ends of the point-to-point link. IPV6CP
uses the same packet exchange mechanism as the Link Control Protocol (LCP). IPV6CP packets are
not exchanged until PPP has reached the Network-Layer Protocol phase. IPV6CP packets received
before this phase is reached are silently discarded. (See also TCP/IP.)
Before you install TCP/IP on your network, you need to establish your Internet addressing strategy.
You first choose a domain name for your company. A domain name is the unique Internet name,
usually the name of your business, that identifies your company. For example, Multi-Tech’s domain
name is multitech.com (where .com indicates this is a commercial organization; .edu denotes
educational organizations, .gov denotes government organizations). Next, you determine how many
IP addresses you’ll need. This depends on how many individual network segments you have, and
how many systems on each segment need to be connected to the Internet. You need an IP address
for each network interface on each computer and hardware device.
IP addresses are 32 bits long and come in two types: network and host. Network addresses come in
five classes: A, B, C, D, and E. Each class of network address is allocated a certain number of host
addresses. For example, a class B network can have a maximum of 65,534 hosts, while a class C
network can have only 254. The class A and B addresses have been exhausted, and the class D and
E addresses are reserved for special use. Consequently, companies now seeking an Internet
connection are limited to class C addresses. The current demand for Internet connections will
exhaust the current stock of 32-bit IP addresses. In response, Internet architects have proposed the
next generation of IP addresses, Ipng (IP Next Generation). It features 16-byte addressing,
surpassing the capacities of 32-bit IP.
An IP address can serve only a single physical network. Therefore, if your organization has multiple
physical networks, you must make them appear as one to external users. This is done via
“subnetting”, a complex procedure best left to ISPs and others experienced in IP addressing. Since
IP addresses and domain names have no inherent connection, they are mapped together in
databases stored on Domain Name Servers (DNS). If you decide to let an Internet Service Provider
(ISP) administer your DNS server, the ISP can assist you with the domain name and IP address
assignment necessary to configure your company’s site-specific system information. Domain names
and IP addresses are granted by the InterNIC. To check the availability of a specific name or to obtain
more information, call the InterNIC at (703)742-4777. 
						

							77 Appendix B - Cabling Diagrams
Appendix B - Cabling Diagrams
Command Port Cable
1  2  3  4  5  6  7  8
PIN NO.
4
7
8
3
2
6
1
51
2
3
4
5
6
7
8
To DTE
Device
(e.g., PC)
CLEAR TO SEND
TRANSMIT DATA
RECEIVE DATA
SIGNAL GROUND
PIN NO.
To Command
Port ConnectorDB9F RJ-45
LAN Cable
1  2  3  4  5  6  7  8
Pin Circuit Signal Name
1 TD+ Data Transmit Positive
2 TD- Data Transmit Negative
3 RD+ Data Receive Positive
6 RD- Data Receive Negative
Voice/Fax Channel Connectors
1  2  3  4  5  6  7  81  2  3  41  2  3  4
Pin Connections
E&M Description FXO Description FXS Description
1M
2 E 1 N/C 1 N/C
3 T1 2 Ring 2 Tip
4 R 3 Tip 3 Ring
5 T 4 N/C 4 N/C
6R1
7SG
8SB 
						

							78 MultiVOIP 200 User Guide
Remote Configuration Cable
Receive Data (RX)
Transmit Data (TX)
Signal Ground
Clear to Send (CTS)
9-Pin Male
2
3
5
8
25-Pin Male
2
3
7
4
To Command port
adapter cableTo DCE Device
(e.g., modem) 
						

							79 Appendix C - Regulatory Information
Appendix C - Regulatory Information
Class A Statement
FCC Part 15
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference when the equipment is operated in a commercial environment. This equipment generates, uses and
can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may
cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to
cause harmful interference, in which case the user will be required to correct the interference at his own expense.
This device complies with Part 15 of the FCC rules.
Operation is subject to the following two conditions:
(1) This device may not cause harmful interference.
(2) This device must accept any interference that may cause undesired operation.
Warning: Changes or modifications to this unit not expressly approved by the party responsible for compliance
could void the user’s authority to operate the equipment.
Industry Canada
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment
Regulations.
Cet appareil numerique de la classe A respecte toutes les exigences du Reglement sur le materiel brouilleur du
Canada.
Fax Branding Statement
The Telephone Consumer Protection Act of 1991 makes it unlawful for any person to use a computer or other electronic
device, including fax machines, to send any message unless such message clearly contains the following information:
• Date and time the message is sent
• Identification of the business or other entity, or other individual sending the message
• Phone number of the sending machine or such business, other entity, or individual
This information is to appear in a margin at the top or bottom of each transmitted page or on the first page of the transmission.
(Adding this information in the margin is referred to as 
fax branding.)
Since any number of Fax software packages can be used with this product, the user must refer to the Fax software manual for
setup details. Typically, the Fax branding information must be entered via the configuration menu of the software.
FCC Part 68 Telecom
1. This equipment complies with Part 68 of the Federal Communications Commission (FCC) rules. On the outside
surface of this equipment is a label that contains, among other information, the FCC registration number. This
information must be provided to the telephone company.
2. As indicated below, the suitable jack (Universal Service Order Code connecting arrangement) for this
equipment is shown. If applicable, the facility interface codes (FIC) and service order codes (SOC) are shown.
3. An FCC-compliant telephone cord with modular plug is provided with this equipment. This equipment is
designed to be connected to the phone network or premises wiring using a compatible modular jack which is Part
68 compliant. See installation instructions for details. 
						

							80 MultiVOIP 200 User Guide
4. If this equipment causes harm to the phone network, the phone company will notify you in advance that
temporary discontinuance of service may be required. But if advance notice is not practical, the phone company
will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint with the
FCC if you believe it is necessary.
5. The phone company may make changes in its facilities, equipment, operations, or procedures that could affect
the operation of the equipment. If this happens, the phone company will provide advance notice in order for you
to make necessary modifications in order to maintain uninterrupted service.
6. If trouble is experienced with this equipment (the model of which is indicated below) please contact Multi-Tech
Systems, Inc., at the address shown below for details of how to have repairs made. If the equipment is causing
harm to the network, the phone company may request that you remove the equipment from the network until the
problem is resolved.
7. No repairs are to be made by you. Repairs are to be made only by Multi-Tech Systems or its licensees.
Unauthorized repairs void registration and warranty.
8. Manufacturer: Multi-Tech Systems, Inc.
Trade name: MultiVOIP
Model Numbers: MVP200
FCC Registration Number: AU7USA-25715-DF-N
Modular Jack (USOC): RJ-11C or RJ-11W
Service Center in U.S.A.: Multi-Tech Systems Inc.
2205 Woodale Drive
Mounds View, MN 55112
(612) 785-3500 Fax (612) 785-9874
Canadian Limitations Notice
Ringer Equivalence Number
Notice: The ringer equivalence number (REN) assigned to each terminal device provides an indication of the maximum
number of terminals allowed to be connected to a phone interface. The termination on an interface may consist of any
combination of devices subject only to the requirement that the sum of the ringer equivalence numbers of all the devices does
not exceed 5.
Notice: The Industry Canada label identifies certified equipment. This certification means that the equipment meets certain
telecommunications network protective, operational and safety requirements. The Department does not guarantee the
equipment will operate to the user’s satisfaction.
Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local tele-
communications company. The equipment must also be installed using an acceptable method of connection. The customer
should be aware that compliance with the above conditions may not prevent degradation of service in some situations.
Repairs to certified equipment should be made by an authorized Canadian maintenance facility designated by the supplier.
Any repairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommunications
company cause to request the user to disconnect the equipment.
Users should ensure for their own protection that the electrical ground connections of the power utility, phone lines and
internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural
areas.
Caution: Users should not attempt to make such connections themselves, but should contact the appropriate electric inspec-
tion authority, or electrician, as appropriate.