Avaya Feature Pack 1 Maintenance Release User Manual

Business Communications Manager 2.5 Feature Pack 1, Maintenance Release Documentation Update

Welcome to Business Communications Manager 2.5 Feature Pack 1, the unified communications solution that gives you an edge on your competition.

The Business Communications Manager 2.5 documentation is on the Business Communications Manager 2.5 Documentation CD-ROM. This CD-ROM is in your Business Communications Manager 2.5 kit.

To view the documentation:

1. Insert the Business Communications Manager 2.5 Documentation CD-ROM into the CD-ROM drive of your computer.

2. Double click the My Computer icon.

3. Double click the CD-ROM icon.

4. Double click Start.pdf.

This document provides last-minute changes to the Business Communications Manager

2.5 documentation.

Business Communications Manager 2.5 Programming Operations Guide

Page 161 Defining line pool access for remote packages

The note in this section is incorrect . You can use VoIP line pools for remote packages. However, you cannot use VoIP line

pools for Remote Paging.

Centralized voice messaging, MWI

Note: When you attach a third-party voice mail system to the Meridian 1 that you are

using for centralized voice mail for your network, ensure that the voice mail system supports Meridian standard MIK/MCK messaging. Refer to your Meridian documentation for standards and configuration details.

System Wide Access Keys (SWCA)

This feature requires a valid Call Park Prefix (General settings, Access Codes) and valid Park timeout settings (General settings, Feature settings).

If the Call Park Prefix is set to None, the park feature is turned off. In this case, calls cannot be parked on SWCA keys.

The Park timeout timer is used to determine how long a call can remain unanswered on a SWCA key before the key is released and the call is returne d to the original answering telephone.

Business Communications Manager

Enabling the RIP Subnet summary

1. Start a Unified Manager session.

2. Click the Services key and then click the IP Routing key.

3. Click the heading of the network interface you want to modify (LAN1, LAN2, WAN1 or WAN2).

4. Click the Configuration menu and then click Enable Rip Subnet Summ.

The message "Please wait..setting data" appears in the message bar at the bottom of the Unified Manager Window. After the Rip Subnet Summary is successfully enabled, the message "Ready" appears in the message bar.

Disabling the RIP Subnet summary

1. Start a Unified Manager session.

2. Click the Services key and then click the IP Routing key.

3. Click the heading of the network interface you want to modify (LAN1, LAN2, WAN1 or WAN2).

4. Click the Configuration menu and then click Disable Rip Subnet Summ.

The message "Please wait..setting data" appears in the message bar at the bottom of the Unified Manager Window. After the Rip Subnet Summary is successfully disabled, the message "Ready" appears in the message bar.

Page 450 Web Cache

The following sentence is incorrect.

• You can also configure the web caching settings on your computer through your web browser.

This sentence should be:

• To use the Web Cache on the Business Communications Manager, you must configure the client computer to use an Internet Proxy at port 6800, where the internet proxy is the Business Communications Manager.

Page 468 NAT (Network Address Translation)

The following sentence is incorrect.

• On all of the interfaces expected to carry PPTP tunnel traffic, add rules to allow PPTP traffic (bidirectional traffic on TCP port 1723 and IP sub-protocol 47) to and from Business Communications Manager.

The requirements above do not apply to using NAT with PPTP tunnels.

Page 469 Filters

Change the first bullet in this section to the following sentence.

• Allow PPTP protocol under the Protocol field for traffic to and from Business Communications Manager.

Page 484 Adding Remote Accessible Networks to the IPSec tunnel

If you want to send all traffic from the Local Accessible Networks through the IPSec tunnel, add the following eight Remote Accessible Networks to the tunnel.

Network Number IP Address IP Mask

R1 1.0.0.0 255.0.0.0

R2 2.0.0.0 254.0.0.0

R3 4.0.0.0 252.0.0.0

R4 8.0.0.0 248.0.0.0

R5 16.0.0.0 240.0.0.0

R6 32.0.0.0 224.0.0.0

R7 64.0.0.0 192.0.0.0

R8 128.0.0.0 128.0.0.0

Page 540 System Name

After you change the System Name, restart the Business Communications Manager system. If you change the System Name and do not restart the Business Communicat ions Manager system , Scheduled tasks will not run.

Note: The System Name is the Netbios name of Business Communications Manager.

Business Communications Manager 2.5 Installation and Maintenance Guide

Mirrored disk (RAID) hard disk jumper settings

The Business Communications Manager Mirrored disk (RAID) system uses a Master/Master configuration. Hard disk drives purchased from Nortel Networks come with the correct jumper settings.

Business Communications Manager 2.5 IP Telephony Configuration Guide

Page 26 VLAN port number

In Table 3, replace item 3.c with the following.

3.c Does the switch use VLANs? If so, get the 802.1Q VLAN ID.

Page 30 VLAN port number

In Table 7, replace item 7.c with the following.

7.c If DHCP is not being used, or if you want to enter the port manually, has the 802.1Q VLAN ID been supplied, if one is being used on the switch?

Page 37 VLAN

For the VLAN field, you must select 0 (no VLAN) or 1 (Manual VLAN). Option 2 (Automatic) is not available.

Page 60 Configuring codecs

The following note should be added to Step 5. Note: If you choose the None option, there is no preferred codec for this level. This means that any codec

that is supported by Business Communications Manager can be used.

Page 94 MCDN over VoIP M1 ITG configuration updates

Make sure the Meridian 1 ITG meets the following requirements:

• ITG 2.8.24* or 2.24.24*

• Rls 25.30 or higher

• S/W Packages 57, 58, 59, 145, 147, 148, 160

*A maintenance release for ITG 2.X.26 will introduce Media Card support for Meridian 1 to Business Communications Manager.

Page 110 Adjust the jitter buffer size

The following note should be added. Note: Business Communications Manager does not support Fax over IP calls.

Page 128 Decision: does the intranet meet IP telephony QoS needs?

The following note should be added. Note: Business Communications Manager does not support Fax over IP calls.

Page 134 Nortel NetVision Phone Administrator (NVPA)

The NVPA application is not available on Business Communications Manager. To download NVPA, go to the Symbol web site (http://www.symbol.com/services/downloads/nvfirmware2.html).

Remote gateway: Gateway Type and Protocol changes

If you set up IP trunks on your Business Communications Manager 2.5 system, you will need to adjust the Remote Gateway records when you upgrade to Feature Pack 1 and newer versions.

You must now select a Gateway Type and a Gateway Protocol. These fields determine what type of system the gateway connects to, and what protocol you are using to make that connection.

Note: The following information is contained in the Business Communications Manager 2.5 Feature

Pack 1 IP Telephony Configuration Guide.

To update the Remote Gateway:

1. In Unified Manager, open Services, IP Telephony, H.323 Trunks, and click on Remote Gateway. The remote gateway tab appears. The Remote Gateway screen shows all gateway records that have been added to the system.

2. Select the gateway record you want to change.

3. On the top menu, click Configuration, and select Modify entry. The Remote Gateway window appears.

4. Use the information in the table below to choose the appropriate Gateway Type and Gateway protocol.

Table 1 Remote gateway record

Field Value Description

Gateway Type BCM2.5

BCM 2.0 ITG

Gateway Protocol None

SL-1

Choose the type of system that is accessed through the remote gateway: BCM2.5: Business Communications Managers running 2.5 or newer

software BCM 2.0: Business Communications Managers running 2.0 software, or

Enterprise Edge systems running 2.0.x software. ITG: Meridian 1 Internet Telephony Gateway

Select the gateway protocol that the trunk expects to use. None: No special features SL-1: MCDN protocol for gateways that provide MCDN over VoIP service Note: You require a keycode for SL-1 protocol.

5. Click Save.

6. Repeat for all your Remote Gateway records.

Using Radvision ECS 2.1.0.1 as the gatekeeper for VoIP trunks

When you use Radvision ECS 2.1.0.1 as the gatekeeper with the Business Communications Manager VoIP trunks, specifically with the FP1 Maintenance Release, use the configurations described in this section. For detailed information about Radvision, and how to open and use the application, refer to the documentation for the application.

Business Communications Manager requirements

On the Business Communications Manager Local Gateway IP interface screen:

These fields are mandatory:

• Call Signaling

• Gatekeeper IP

• Alias Names

These fields are optional:

• Registration TTL

• Gateway Protocol

Note: Refer to the IP Telephony Guide for details about using the Local Gateway IP interface screen.

Configuring the Radvision application as a Business Communications Manager gatekeeper

To ensure compatibility with the Business Comm unications Manager FP1 Maintenance Release software, the following configurations must be set on the Radvision ECS 2.1.0.1 gatekeeper application, which can be obtained through http://www.radvision.com/.

1. Open the Radvision application.

2. On the viaIP Administrator screen, select the Settings tab, then click on the Basics button.

3. Beside the Who can register field, choose Everyone.

+ 9 hidden pages