564
Business Communications Manager as host
N0008589 3.3
Business Communications Manager as host
A Business Communications Manager that acts as a central voice mail location must be running at
least BCM version 3.5 or newer software. Other systems on the network can be running older
software, as long as that software supports MCDN. In the case of another Business
Communications Manager system, this would require BCM version 2.5 or newer software. You
can add up to 1000 mailboxes on Business Communications Manager voice mail, providing you
have entered adequate keycode
s
.
CallPilot constraints:
•
To allow use of the auto attendant feature, you must ensure that the
Allow Network Transfers
check box is selected in the CallPilot Manager.
•
To allow use of voice mail, you must ensure that the
Enabled Redirected DN
check box is
selected in the CallPilot Manager.
For details about setting up the CallPilot parameters and features, refer to the
CallPilot Manager
Set Up and Operation Guide
and the other CallPilot supporting documentation.
Meridian system as host
If you are using a voice mail system connected to a Meridian 1 as a host system, ensure that the
systems are set up to be compatible with each other:
CallPilot compatibility
If you are planning to use M-1 based CallPilot software for the voice mail system, there are no
compatibility issues.
Meridian Mail compatibility issues
If you are using Meridian Mail as the host system, ensure that the Meridian has the following:
•
Meridian Mail rel. 7 (MM7) or above
•
the appropriate number of PRI cards and D-channel handlers to support the PRI links to all the
Business Communications Managers using the system.
Special requirements:
•
Over a PRI SL-1 line: Meridian 1 must be on Release 19 or greater.
•
Over VoIP: Meridian one must be installed with an IPT card version 3.0 or newer
•
Meridian 1 requires the network ID of the Business Communications Manager, which is
defined under
Dialing Plan, Private Network
in the Unified Manager. This is a number
between 1 and 27, and is defined by the Meridian system administrator.
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...