Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways S000249C User Guide

							MultiVOIP User Guide T1 PhoneBook Configuration
251
4. Select PhoneBook Modify and then select Inbound PhoneBook/List Entries. 
						

							E1 Phonebook Configuration MultiVOIP User Guide
252
5. The Add/Edit Inbound PhoneBook screen appears.
Enter Inbound PhoneBook data for your MultiVOIP.  The fields of the
Add/Edit Inbound PhoneBook screen are described in the table below.    
Add/Edit Inbound Phone Book: Field Definitions
Field Name Values Description
Remove Prefix dialed digits portion of dialed number to
be removed before
com
pleting call to destination
(often a local PBX)
Add Prefix dialed digits digits to be added before
com
pleting call to destination
(often a local PBX)
Channel
Number1-24, or
“Hunting”T1 channel number to which
the call will be assigned as it
enters the local telephony
equipment
(often a local PBX).
“Hunting” directs the call to
any available channel. 
						

							MultiVOIP User Guide T1 PhoneBook Configuration
253
   
Add/Edit Inbound Phone Book: Field Definitions
(cont’d)
Field Name Values Description
Description -- Describes the facility or
geographical location at
which the call originated.
Call Forward Parameters
Enable Y/N Click the check-box to enable
the call-forwarding feature.
Forward
ConditionUncondit.;
Busy
No Resp.Unconditional. When
selected, all calls received
will be forwarded.
Busy. When selected, calls
will be forwarded when
station is busy.
No Response. When
selected, calls will be
forwarded if called party
does not answer after a
specified number of rings,
as specified in Ring Count
field.
Forward
Address/
NumberIP addr. or
phone
numberPhone number or IP
address to which calls will
be directed.
Ring CountintegerWhen No Response is
condition for forwarding
calls, this determines how
many unanswered rings
are needed to trigger the
forwarding.
6. When your Outbound and Inbound PhoneBook entries are
completed, click on Save Setup in the sidebar menu to save your
configuration.
You can change your configuration at any time as needed for your
system. 
						

							E1 Phonebook Configuration MultiVOIP User Guide
254
Remember that the initial MVP2400/2410 setup must be done locally
using the MultiVOIP program.  However, after the initial configuration
is complete, all of the MVP2400/2410 units in the VOIP system can be
configured, re-configured, and updated from one location using the
MultiVoipManager software program.
T1 Phonebook Examples
The following example demonstrates how Outbound and Inbound
PhoneBook entries work in a situation of multiple area codes.  Consider
a company with offices in Minneapolis and Baltimore.
3 Sites, All-T1 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.
Mpls
612 NW
Suburbs
763St. Paul
& Suburbs
651
SW Suburbs
952

Company
VOIP/PBX
SIte


Baltimore
410Baltimore/
Outstate MD
Overlay
443
Company
VOIP/PBX
SIte... 
						

							MultiVOIP User Guide T1 PhoneBook Configuration
255
An outline of the equipment setup in both offices is shown below.
IP
Network
Digital
Vo I P
200.2.10.3
T1
717-5170
PBX
-5171-5172
-5173
-5174
Company HQ.
Minneapolis
North Sub.
area 763 Local-Call
Area Codes:
612, 651,
952
325-7001
R
o
u
t
e
r




Digital
Vo IP
200.2.9.7
T1
Baltimore
Sales Ofc.
area 410
PBX
Overlay
Area Code:
443
-7002
-7003 
						

							E1 Phonebook Configuration MultiVOIP User Guide
256
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. 
						

							MultiVOIP User Guide T1 PhoneBook Configuration
257
To call the Minneapolis/St. Paul area, a Baltimore employee must dial
eleven digits. (In this case, we are assuming that the Baltimore PBX
does not require an “8” or “9” to seize an outside phone line.)
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 cal 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. 
						

							E1 Phonebook Configuration MultiVOIP User Guide
258
Similarly, the Inbound PhoneBook for the Baltimore VOIP (shown first
below) generally matches the Outbound PhoneBook of the Minneapolis
VOIP (shown second below).
Notice the extended prefix to be removed: 14103257.  This entry allows
Minneapolis users to contact Baltimore co-workers as though they were
in the Minneapolis facility, using numbers in the range 7000 to 7999.
Note also that a comma (as in the entry 9,443) denotes a delay in
dialing.  A one-second delay is commonly used to allow a second dial-
tone to be generated for calls going outside of the facility’s PBX system. 
						

							MultiVOIP User Guide T1 PhoneBook Configuration
259
The Outbound PhoneBook for the Minneapolis VOIP is shown below.
The third destination pattern, “7” facilitates reception of co-worker calls
using local-appearing-extensions only.  In this case, the “Add Prefix”
field value for this phonebook entry would be “1410325” . 
						

							E1 Phonebook Configuration MultiVOIP User Guide
260
Configuring Mixed Digital/Analog VOIP Systems
The MVP2400/2410 digital MultiVOIP unit is compatible with analog
VOIPs.  In many cases, digital and analog VOIP units will appear in the
same telephony/IP system.  In addition to MVP-210/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 MVP2400) operates with two Series II  analog VOIPs (an
MVP210 and an MVP410), and two Series I legacy VOIPs (two MVP200
units).
IP
NetworkPBX
Digital
Vo IP
MVP2400200.2.9.9T1
PSTN Site D:Pierre, SD
Area Code 615
615-492-3100
EXAMPLE:
Digital & Analog VOIPs
in Same System
Router
Other extensions
x3101 - x3199
Unit
#200
201 FXS
CH1
Series #1 Analog MultiVOIP
(Server/Client Phonebook)
MVP200
200.2.9.7
Client
Site A:Bismarck, ND
Area Code 701
200.2.9.8
Host
(Holds phonebook for both
Series #1 analog VOIPs.)
Site B:Rochester, MN
Area Code 507
CH2
FXS
717-5000FXOUnit
#100 Series #1 Analog MultiVOIP
(Server/Client Phonebook)
MVP200
507-717-5662Site C:Suburban Rochester
CH1
FXS
Site E:Cheyenne, WY
Area Code 307
Key
System
402-263-7400
Other extensions
x7401 - x7429
CO PortFXS Ports
CO Ports FXS Port
PSTN200.2.9.5200.2.9.6FXO
PSTN
102
Site F:Lincoln, NE
Area Code 402
421
Port #4
CH1
Series #2 Analog MultiVOIP
MVP210
Series #2 Analog MultiVOIP
MVP410