Cisco Unity Documentation Addendum, Release 4.1
Cisco Unity Bridge Networking Guide

Table Of Contents

Cisco Unity Bridge Networking Guide

Private List Considerations

Pushing Mailbox Information from the Avaya Interchange to Cisco Unity

Upgrading from Cisco Unity 4.0(5) with Bridge 3.x (Cisco Unity with IBM Lotus Domino Only)

Upgrading the Cisco Unity Bridgehead Server

Redesignating the Bridgehead Server

Upgrading Non-Bridgehead Cisco Unity Servers

Upgrading Cisco Unity Bridge 3.x to a Newer Version (Optional)

Installing the Cisco Unity Bridge Analog Network And Node Analyzer (BANANA)

Errors

Configuring the Interop Gateway (Cisco Unity with IBM Lotus Domino Only)


Cisco Unity Bridge Networking Guide


This chapter should be used in conjunction with the Cisco Unity Bridge Networking Guide, Release 3.0. New features are described in individual sections. Information that has changed in the Cisco Unity Bridge Networking Guide, Release 3.0—either because Cisco Unity or Cisco Unity Bridge functionality changed, or because the information is incorrect—is described in the "Errors" section at the end of the chapter.

This chapter contains the following sections:

Private List Considerations

Pushing Mailbox Information from the Avaya Interchange to Cisco Unity

Upgrading from Cisco Unity 4.0(5) with Bridge 3.x (Cisco Unity with IBM Lotus Domino Only)

Errors

Private List Considerations

Consider notifying subscribers in the event that the following members are inadvertently removed from their lists:

When you delete a delivery location, blind addressees are removed from all private list.

When an external subscriber becomes a regular subscriber, the external subscriber is removed from all private lists.

Pushing Mailbox Information from the Avaya Interchange to Cisco Unity

When the Cisco Unity Bridge represents more than one node on the Octel analog network—in other words, the Interchange has multiple location profiles with different serial numbers configured for the same Cisco Unity network—the configuration of the directory view for update pushes of mailbox information should be performed for only one of the Cisco Unity location profiles. Otherwise, the Bridge will receive redundant pushes when changes occur.

Depending on how many location profiles are set up for Cisco Unity on the Interchange and how many changes are occurring, sending duplicate pushes could generate unnecessary use of Bridge ports for administrative calls. It could also generate unnecessary processing of duplicate modifications by Cisco Unity and other servers, such as a Microsoft Exchange server hosting the Voice Connector, or an IBM Lotus Domino server involved in routing the push messages.

Upgrading from Cisco Unity 4.0(5) with Bridge 3.x (Cisco Unity with IBM Lotus Domino Only)

If you currently have Cisco Unity 4.0(5) servers configured for networking with a Bridge 3.x server (or servers), use the task list and procedures in this section to upgrade Cisco Unity. Networking with the Octel servers is not disrupted after upgrading Cisco Unity. Therefore, in installations with multiple Cisco Unity servers, you can upgrade the Cisco Unity servers as your schedule permits.

Upgrade the Cisco Unity Bridgehead Server

1. Upgrade the Cisco Unity bridgehead server. For systems using failover, upgrade the secondary server as well. Refer to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter of the Cisco Unity Reconfiguration and Upgrade Guide (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm.

2. Run ConfigMgr.exe on the Cisco Unity bridgehead server to redesignate it as the bridgehead server. See the "Redesignating the Bridgehead Server" section.

Upgrade Non-Bridgehead Cisco Unity Servers

3. Upgrade all non-bridgehead Cisco Unity servers in the network. For systems using failover, upgrade the secondary servers as well. Refer to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter of the Cisco Unity Reconfiguration and Upgrade Guide (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm.

Optionally, Upgrade the Bridge Server(s)

If a newer version of the Bridge 3.x software is available, we recommend that you upgrade the Bridge software to the latest version.

4. Upgrade the Bridge server. See the "Upgrading Cisco Unity Bridge 3.x to a Newer Version (Optional)" section.

5. Install the Cisco Unity Bridge Analog Network and Node Analyzer (BANANA). See the "Installing the Cisco Unity Bridge Analog Network And Node Analyzer (BANANA)" section.

Enable Optional Features

6. Optionally, if the Bridge is at version 3.0(6) or later, enable the Bridge server to accept requests to push remote mailbox information. Refer to the "Enabling the Bridge to Accept Requests to Push Mailbox Information (Bridge 3.0(6) and Later)" section of the "Setting Up Cisco Unity and the Bridge for Networking" chapter in the Cisco Unity Bridge Networking Guide, Release 3.0 (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/dom/index.htm.

Upgrading the Cisco Unity Bridgehead Server

Upgrade the Cisco Unity bridgehead server. For systems using failover, upgrade the secondary server as well. Refer to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter of the Cisco Unity Reconfiguration and Upgrade Guide (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm.

Redesignating the Bridgehead Server

Run the ConfigMgr.exe utility with the Create Bridge Account option to redesignate the server as the bridgehead. (The CsBridgeConnector service will not start, and the Cisco Unity Administrator will not display Bridge-related pages until ConfigMgr.exe has been run.)

To Designate the Bridgehead Server


Step 1 On the Cisco Unity server, browse to the directory in which Cisco Unity is installed (the default location is CommServer).

Step 2 Double-click ConfigMgr.exe. The ConfigMgr dialog box appears.

Step 3 Click Create Bridge Account.

Step 4 Click OK in the dialog box that displays after the configuration has completed.

Step 5 Close the ConfigMgr dialog box.


Upgrading Non-Bridgehead Cisco Unity Servers

Upgrade all non-bridgehead Cisco Unity servers in the network. For systems using failover, upgrade the secondary servers as well. Networking with the Octel servers is not disrupted after upgrading Cisco Unity. Therefore, in installations with multiple Cisco Unity servers, you can upgrade the Cisco Unity servers as your schedule permits. Refer to the "Upgrading Cisco Unity 4.x Software to the Shipping Version" chapter of the Cisco Unity Reconfiguration and Upgrade Guide (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/rug/dom/index.htm.

Upgrading Cisco Unity Bridge 3.x to a Newer Version (Optional)

Optionally, upgrade the Bridge server (or servers) to the latest 3.x version.

We recommend that you upgrade when Bridge message traffic is light. To upgrade to the latest Bridge version from Bridge 3.0(x):

1. Disable and stop virus-scanning and Cisco Security Agent services.

2. Upgrade the Bridge software.

3. Re-enable and start virus-scanning and Cisco Security Agent services.

To Disable and Stop Virus-Scanning and Cisco Security Agent Services


Step 1 Refer to the virus-scanning software documentation to determine the names of the virus-scanning services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Disable and stop each virus-scanning service and the Cisco Security Agent service:

a. In the right pane, double-click the service.

b. On the General tab, in the Startup Type list, click Disabled. This prevents the service from starting when you restart the server.

c. Click Stop to stop the service immediately.

d. Click OK to close the Properties dialog box.

Step 4 When the services have been disabled, close the Services MMC.


To Upgrade Cisco Unity Bridge 3.x to a Newer Version


Step 1 Log on to the Bridge server by using the Windows 2000 Server Administrator account.

Step 2 Verify that the account has permission to access the Bridge Administrator.

a. Open the Bridge Administrator.

b. If you are allowed access and can view the Bridge Administrator pages, exit the Bridge Administrator and continue with Step 3.


Caution If you are denied access to the Bridge Administrator, do not continue, because the Bridge setup program will fail. You must log off and log back on using another account that is allowed access to the Bridge Administrator. It is possible that the account was denied access to the Bridge Administrator because it is not in the Access Control List of the <Bridge>\Starfish\Asp directory or does not have Full Control permissions to that directory. Access to the <Bridge>\Starfish\Asp directory may have been restricted when password protection was added to the Bridge Administrator as described in the "To Add Password Protection to the Bridge Administrator" procedure in the "Setting Up Cisco Unity and the Bridge for Networking" chapter of the Cisco Unity Bridge Networking Guide (With IBM Lotus Domino) at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/bridge30/bnet/dom/index.htm.

Step 3 On the Windows Start menu, click Programs > Administrative Tools > Services, and stop the following two services:

Digital Networking

Unity Bridge

The Bridge services will complete the shutdown process when the last in-process message transmission or reception, rather than call, is complete. No additional message transmissions will begin on the in-process calls—either outbound or inbound—after shutdown has been initiated.

Step 4 If you downloaded the Bridge software from the Software Center website, browse to the directory in which the files were extracted.

If you are using the Cisco Unity Bridge CD, insert the disc in the CD-ROM drive, and browse to the Install directory.

Step 5 Double-click Setup.exe.

Step 6 Click Next.

Step 7 In the Choose Destination Location dialog box, change the installation directory, if applicable, and click Next.

Step 8 If a device driver service was previously installed for the Brooktrout voice-fax card, a message asks if you want to overwrite the existing service. Click Yes twice.

Step 9 In the Select Country dialog box, select the country for which the voice-fax cards will be configured, and click Next.

Step 10 Verify the installation settings, and click Next.

Step 11 When prompted, remove the disc from the CD-ROM drive.

Step 12 Click OK to restart the server.


To Re-Enable and Start Virus Scanning and Cisco Security Agent Services


Step 1 Refer to the virus-scanning software documentation to determine the names of the virus-scanning services.

Step 2 On the Windows Start menu, click Programs > Administrative Tools > Services.

Step 3 Re-enable and start each virus-scanning service and the Cisco Security Agent service:

a. In the right pane, double-click the service.

b. On the General tab, in the Startup Type list, click Automatic to re-enable the service.

c. Click Start to start the service.

d. Click OK to close the Properties dialog box.

Step 4 When the services have been re-enabled, close the Services MMC.


Installing the Cisco Unity Bridge Analog Network And Node Analyzer (BANANA)

BANANA is a stand-alone application that runs on the Bridge server. It is designed to assist with monitoring and troubleshooting analog communication between the Bridge and the Octel nodes in the analog network. It also provides detail and summary information of call activity.

The drive on which BANANA will be installed requires at least 1 GB of free disk space.

The following procedures provide details for installing and initiating test calls. Refer to the BANANA Help file for information about other functionality provided by BANANA.

To Install BANANA


Step 1 Disable virus scanning services and the Cisco Security Agent service, if applicable.

Step 2 Insert the Cisco Unity Bridge compact disc in the CD-ROM drive, and browse to the BANANA directory.

Step 3 Double-click setup.exe.

Step 4 Click OK at the welcome screen.

Step 5 If applicable, change the directory where BANANA will be installed.

Step 6 Click the Installation button.

Step 7 If applicable, change the program group where BANANA will appear.

Step 8 Click Continue.

Step 9 If a Version Conflict message box is displayed warning that a file being copied is not newer than the file on your system, click Yes to keep the existing file.

Step 10 When the installation is done, click OK.

Step 11 Enable virus-scanning and the Cisco Security Agent services, if applicable


Note The most up-to-date version of BANANA is available at http://www.CiscoUnityTools.com. When you start BANANA, it checks the CiscoUnityTools website to see if a newer version is available, and if so, prompts you about upgrading.



To Adjust the Message Delivery Window Settings


Step 1 In the Bridge Administrator, click Octel Nodes.

Step 2 In the Node list, click an Octel node that you want to be tested, and click Edit.

Step 3 On the Octel Node page in the Message Delivery Windows section, adjust the schedule according to following illustration, so that the Bridge will not wait to initiate calls to the Octels to deliver normal, urgent, and administrative messages.

Note that BANANA makes only administrative calls when testing the Octel analog network. However, if you adjust the normal and urgent schedules as shown, you do not have to remember to adjust the schedule if you also send test messages from Cisco Unity subscribers to Octel subscribers.

Step 4 Click Save.

Step 5 Repeat Step 2 through Step 4 for each Octel node that you want to test.


To Initiate Test Calls to the Octel Nodes


Step 1 On the Bridge server on the Windows Start menu, click Programs > BANANA > BANANA admin. The BANANA admin main window displays.

Step 2 Configure the log and output folder locations.

Step 3 Specify the Octel nodes to be included when placing test calls.

Step 4 Place the test calls.

Step 5 Process the call data, and view the results.

Refer to the BANANA Help for details.


Errors

Configuring the Interop Gateway (Cisco Unity with IBM Lotus Domino Only)

In the Cisco Unity Bridge Networking Guide, Release 3.0 (With IBM Lotus Domino), the procedures for setting up Cisco Unity and the Bridge for networking omit an additional step for configuring permissions for the interop gateway that is required when Cisco Unity is integrated with IBM Lotus Domino release 7.0. The step must be done prior to performing the procedure to configure the interop gateway.

In Domino release 7.0, the default permissions set for the -Default- account on the access control list of the mailbox.ntf template do not include permission to replicate or copy documents. This permission is required when setting up the interop gateway. It can be granted either by adding the permission for the -Default- account, or by adding the UnityServers group that was created during Cisco Unity installation to the access control list, and granting permission to replicate or copy documents to the group. Refer to the applicable IBM Lotus documentation for information on adding this permission.