
147
IP Telephony Configuration Guide
Chapter 8
Typical network applications using MCDN
This section explains several common installation scenarios and provides examples about how to
use VoIP trunks and IP telephony to enhance your network.
Information in this section includes:
• “Setting up MCDN over VoIP with fallback” on page 147
• “Networking multiple Business Communications Managers” on page 149
• “Multi-location chain with call center” on page 151
• “Business Communications Manager to remote IP telephones” on page 152
Setting up MCDN over VoIP with fallback
The MCDN networking protocol between a Meridian 1 and one or more Business
Communications Managers works the same way as it does over PRI lines. You still require the
MCDN and IP telephony software keys and compatible dialing plans on all networked systems.
The one difference between MCDN over PRI and MCDN over VoIP is that the VoIP trunks
require specific Remote Gateway settings, unless there is a Gatekeeper configured to route traffic
on the IP network. Under Services, IP Telephony, H.323 Trunks, Remote Gateway, ensure that
Gateway Protocol is set to CSE for the VoIP connection to the Meridian 1-IPT system. The
Gateway Type would be set to IPT, as it would for any non-MCDN VoIP connection to a
Meridian system. For details about setting up MCDN networks, refer to the Private Networking
chapter in the Business Communications Manager Programming Operations Guide.
Note: If you use MCDN over VoIP, ensure that your PSTN fallback line is a PRI SL-1 line, to
maintain MCDN features on the network.
One application of this type of network might be for a company, which has an M1 at Head Office,
who want to set up a warehouse in another region. This would allow the warehouse to call Head
Office across VoIP lines, bypassing long-distance tolls. This type of network also provides the
possibility of having common voicemail off the M1. Refer to the following figure for an example.
Komentáře k této Příručce