T1 Phonebook Configuration
MultiVOIP User Guide
172
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.
Summary of Contents for MULTIVOIP MVP-3010
Page 6: ...6 Chapter 1 Overview ...
Page 28: ...28 Chapter 2 Quick Start Instructions ...
Page 38: ...Technical Configuration T1 E1 MultiVOIP User Guide 38 Chapter 4 Software Installation ...
Page 49: ...49 Chapter 5 Technical Configuration ...
Page 58: ...Technical Configuration MultiVOIP User Guide 58 Config Info CheckList ...
Page 117: ...MultiVOIP User Guide Technical Configuration 117 ...
Page 139: ...MultiVOIP User Guide Technical Configuration 139 ...
Page 170: ...170 Chapter 6 T1 Phonebook Configuration North American Telephony Standards ...
Page 184: ...T1 Phonebook Configuration MultiVOIP User Guide 184 3 Select Inbound PhoneBook List Entries ...
Page 208: ...208 Chapter 7 E1 Phonebook Configuration European Telephony Standards ...
Page 252: ...252 Chapter 8 Operation and Maintenance ...
Page 257: ...MultiVOIP User Guide Operation Maintenance 257 The Call Progress Details Screen ...
Page 265: ...MultiVOIP User Guide Operation Maintenance 265 The Logs Screen ...
Page 277: ...MultiVOIP User Guide Operation Maintenance 277 ...
Page 280: ...Operation and Maintenance MultiVOIP User Guide 280 T1 Statistics Screen ...
Page 288: ...Operation and Maintenance MultiVOIP User Guide 288 ...
Page 343: ...343 Chapter 9 Warranty Service and Tech Support ...
Page 347: ...347 Chapter 10 Regulatory Information ...
Page 352: ...352 Appendix A Cable Pinouts ...
Page 358: ...358 Appendix B TCP UDP Port Assignments ...
Page 360: ...360 Appendix C Installation Instructions for MVP428 Upgrade Card ...
Page 365: ...MultiVOIP User Guide Index 365 Index ...
Page 395: ...395 S000384A ...