Using SL-1 with MCDN to network with a Meridian system
541
Programming Operations Guide
An example of a private network with Meridian 1
The following figure shows a private network composed of one central Meridian 1, and two sites
with Business Communications Manager systems all connected by SL-1, with MCDN activated on
all sites. This example uses a coordinated dialing plan (CDP). The DNs consist of four digits. The
first digit is a destination code which is specific to each system. The last three digits are unique to
each telephone within that system. Refer to
Chapter 11, “Controlling access into the system,” on
page 293
for a description of the dialing plans available to private networks.
Figure 188
MCDN networking, with a common public network connection
This example could represent a large head office (the Meridian 1) connected to several smaller
branch offices (the two Business Communications Managers). In this network, only the head
office has trunks connected to the public network.
The branch offices access the public network via the PRI to the head office. This configuration
allows for cost savings by consolidating the public access trunks. Users at all three locations
access the public network by dialing 9, followed by the public number. For example, a user in the
West End branch might dial 9-555-1212 (for a local call) or 9-1-613-555-1212 (for a long distance
call). These public calls are routed to the Meridian 1 by the Business Communications Manager
routing table. Routing tables at the Meridian 1 will then select an appropriate public facility for the
call.
Network # 2221
Received # 2221
Internal # 2221
Network # 6221
Received # 6221
Internal # 6221
Business Communications
Manager
West-end branch
PNI= 1
Business Communications
Manager
East-end branch
PNI=2
Central
Office
Meridian M1
PRI (public protocol)
PRI (SL-1)
PRI (SL-1)
DN: 4221
Voice Mail or
Auto Attendant
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...