Chapter 33
Private networking: Basic parameters
The following provides an overview of the values in the system that affect private networking,
including:
•
"Private networking protocols" on page 315
•
"Keycode requirements" on page 315
•
"Remote access to the network" on page 316
•
"Other programming that affects private networking" on page 316
•
"Types of private networks" on page 316
Private networking protocols
The BCM supports the following protocols for private networking:
•
PRI: ETSI QSIG, MCDN, DPNSS
•
BRI: ETSI QSIG
•
T1: E&M
•
VoIP: MCDN
BCM systems can be networked together using TIE lines or E&M connections. Larger networks,
or networks that are geographically spread out, can be chained together through faster PRI SL-1
connections or with voice over IP (VoIP) trunk lines. SL-1 lines and VoIP trunks also offer the
opportunity to use the MCDN protocol, which provides enhanced trunking features and end-to-end
user identification. If a Meridian 1 is part of the MCDN network, the network can also provide
centralized voice mail and auto attendant off the Meridian.
MCDN note: MCDN networking requires all nodes on the network to use a common Universal
Dialing plan (UDP) or a Coordinated Dialing Plan (CDP). Refer to
network," on page 275
Keycode requirements
Keycodes are required to activate the protocols that are used to create private networking,
including:
•
IP trunks, if you want additional IP trunks
•
an MCDN keycode, if you want to use the MCDN protocol between the systems
and
"Dialing plan: Private network settings," on page
"Dialing plan: Public
281.
Networking Configuration Guide
315