Nortel BCM 3.7, Руководство пользователя, Страница: 510 / 1004

510 Private network programming parameters
N0008589 3.3
Private networking protocols
These are the protocols that the Business Communications Manager supports for private
networking:
• PRI: ETSI QSIG, MCDN
• DPNSS
• BRI: ETSI QSIG
• T1: E&M
• VoIP trunks (Refer to the IP Telephony Configuration Guide for details)
Business Communications Manager 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 “Configuring the public and
private dialing plans” on page 312 and “System numbering plans” on page 524 .
Keycode requirements
Keycodes are required to activate the protocols that are used to create private networking,
including:
• PRI keycodes, if you are using PRI lines for your network
• IP trunks, if you want additional IP trunks
• an MCDN keycode, if you want to use the MCDN protocol between the systems
You must purchase and install these keycode s before you can create any of the networks described
in this chapter. Consult with your Nortel Networks distributor to ensure you order the correct
keycodes for the type of network you want to create.
Remote access to the network
Authorized users can access tie lines, central office lines, and Business Communications Manager
features from outside the system. Remote users accessing a private network configured over a
large geographical area, can potentially also place long-distance calls through the network and
avoid toll charges.
Note: You cannot program a Private DISA DN or Private Auto DN to a VoIP trunk, as they act as
auto-answer trunks from one private network to the next. However, you can configure VoIP line
pools with remote access packages so that callers can access telephones or the local PSTN on
remote nodes on a tandemed network that use VoIP trunks between systems.