Busi

ness

Com

mun

icat

ions

Man

ager

Business Communications Manager 3.5 Documentation Update

Welcome to Business Communications Manager 3.5, the unified communications solution that gives you an edge on your competition.

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

To view the documentation:

1 Insert the Business Communications Manager 3.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 3.5 documentation.

Programming and Operations Guide

Page 76, Browser requirementsIf you are using Sun Java JRE, the Unified Manager Help system does not display properly. The frame containing the help information displays correctly, however the frame for the Contents, Index and Search tabs contains no information.

Page 83, Accessing the Unified Manager programming interfaceIn Step 2, the default login name is incorrect.

The default login name is ee_admin.

Page 130, Setting password policyPassword complexity changes

If you change the complexity setting or password length for passwords, ensure that you update any existing passwords that do not meet the complexity setting. (Password Policy tab under Management, User Manager)

If your system was upgraded to Business Communications Manager 3.5 software, the password complexity settings were maintained at the level supported by the previous version of software. If you require increased password security, change the complexity setting and user passwords after the upgrade.

Note: On new 3.5 systems, the default complexity setting is 3 (the highest level), and the password length is set to 8.

If the passwords and complexity settings do not match, you risk losing user accounts when the system is reinitialized after hardware replacement or after a BRU restore.

Page 372, CAP/KIM notesThe key indicator modules (KIMs) that attach to the T7316E to form central answer positions (CAPs) cannot support hunt group DNs as autodial numbers in memory button programming.

2

Page 557, Universal T1 WAN (UTWAN)The UTWAN functionality, along with RTP Header Compression, PPP Fragmentation and Frame Relay Fragmentation, are being made available through a controlled release process. This means that although the UTWAN functionality is installed on the Business Communications Manager, the UTWAN headings and menu items are not visible on Unified Manager by default.

To make the UTWAN headings and menu items visible on Unified Manager, you need to use a utility available from Nortel Networks. To obtain this utility, call the Nortel Networks Technical Support line.

1-800-4NORTEL (1-800-466-7835)If you already have a PIN Code, you can enter Express Routing Code (ERC) 196#.If you do not yet have a PIN Code, or for general questions and first line support, you can enter ERC 338#.

After you use the utility to display the UTWAN heading, you can program the UTWAN features as described in the UTWAN section of the Business Communications Manager Programming Operations Guide.

Page 755, Creating a tunnel between a Business Communications Manager and a Contivity Extranet Switch v02_61

An additional step is required when configuring the Contivity Extranet Switch. Replace the existing configuration procedure with the following.

Configuring the Contivity Extranet Switch

1 Go to Profiles->Network and create a Network with the IP address 14.14.14.0 with mask 255.255.255.0. You will use this for the Local Accessible Networks for your Branch Office Connection.

2 Under Profiles->Branch Office, create a Group based on the Base class.

3 In the IPSec section of this new Group, change the Vendor ID to Disabled and change Compression to Disabled. Business Communications Manager does not support Vendor ID or Compression.

4 In the Connectivity section of this new group, change the Nailed Up setting to Disabled. Business Communications Manager does not support the Nailed Up functionality.

5 Select Define Branch Office Connection.

6 Set the routing type to be Static.

7 Set the Local Endpoint to 47.82.30.60 and the Remote Endpoint to 47.82.20.50.

8 Under Local Accessible Networks, select the Network that was created earlier.

9 Set the Remote Accessible Networks to 10.10.11.0 with mask 255.255.255.0.

10 For the Preshared Key, select the Text button and set the key to '123'. This must match the BCM key.

11 Mark the box for Enable Branch Office Connection.

Page 803, Core software and regionsIn Table 290, the Core Software specified for Brazil is incorrect. Brazil uses the E1 CALA Core Software.

Back Up and Restore Utility (BRU) HelpClicking the Help link for BRU displays a Page cannot be found error, not the BRU help. To access the help you must change the filename in the Address field on your web browser from:

https://<ip_address>/Docs/Help/bcmmug/BCMMAN_SERV_35_Ch10_BRU.html

to:

https://<ip_address>/Docs/Help/bcmmug/BCMMAN_SERV_35_Ch8_BRU.html

where: <ip_address> is the IP address or domain name of your Business Communications Manager system.

3

IP Telephony Configuration Guide

PEC IIIs required for IP Telephony and T.38 Fax• To use IP Telephony, you must have PEC IIIs installed in the MSC card. IP trunks and IP sets are not supported

when 4 PEC 1s are installed.

• To use T.38 Fax, you must have PEC IIIs installed in the MSC card. T.38 trunks are not supported when 4 PEC 1s are installed.

Page 59, Notes about Hot DeskingUsing headsets with hot desking

If you use the headset feature on your IP telephone, and you want to hot desk your telephone to another IP telephone, ensure that the target telephone also a headset installed before you enter the hot desking feature.

If the target telephone does not have a headset, the headset feature from the first telephone does not transfer during hot desking. Adding a headset to the target telephone after hot desking is enabled does not correct the situation. To enable headset function in this situation, you need to cancel hot desking, plug a headset into the target telephone, and then re-establish hot desking.

If the target telephone has a headset, but the originating telephone does not, once hot desking is activated the headset on the target telephone will no longer work. To correct this situation, you need to cancel hot desking, plug a headset into the originating telephone, then re-establish hot desking at the target telephone.

Voice over IP trunks using MCDN protocolContrary to what it says in the IP Telephony Configuration Guide, Meridian 1 IPT does support CSE. CSE, in fact, is the MCDN protocol for VoIP trunks for systems running BCM 3.0, 3.0.1, or 3.5 software and for Meridian 1 systems running IPT (IP trunk) software. If the local gateway for H.323 VoIP trunks on your system has been set to SL-1, after the upgrade, change this to CSE.

Originating telephone Target telephoneHead set feature active on target set after hot desking?

Yes

No

No

4

Page 73, Monitoring H.323 service statusReplace Table 19 with the following table.

Page 87, Setting up the local gatewayIn Table 20, replace the Gateway Protocol row with the row in the following table.

Table 19 H.323 terminals Summary fields

Field Value Description

Name VoIP gateway This is the type of gateway that the H.323 handsets will be using. (read-only)

Status UpEnabled

Disabled

UP: H.323 handsets can be administered on this systemEnabled: This service is enabled.

Disabled: This service is disabled.

Version <digits> Current version of the server software. (read-only)

Description H.323 Voice Over IP Gateway

The type of gateway available to H.323 terminals. (read-only)

Table 20 Local Gateway IP interface fields

Field Value Description

Fields that appear for both types of trunks

Fallback to Circuit-Switched

Fields that appear only for H.323 trunks

*Call Signaling

*Gatekeeper IP

*Alias Names

**Registration TTL

**Gateway Protocol NoneSL1

CSE

Both these protocols require a keycode.SL1: use this protocol only for BCM 2.5 systems

CSE: Use this protocol for BCM 3.0, 3.0.1 and 3.5 systems. This protocol supports Meridian 1 IPT.Otherwise, use None.

** These fields are optional when you use Radvision ECS 2.1.0.1.

5

Page 97, Configuring a remote gateway (H.323 trunks)In Table 21, replace the Transmit Threshold, Receive Threshold and Gateway Protocol rows with the rows in the following table.

Page 134, Faxing over VoIP linesSome fax machines will be unable to successfully send faxes over VoIP (T.38) trunks to the following destinations:

• CallPilot mailboxes

• CallPilot mailboxes (accessed through auto-attendant)

• Fax Transfer (calls transferred to a system fax device through the auto-attendant)

Use the following tips to avoid this problem:

• Avoid the use of manual dial on the originating fax machine. In some fax machines, manually dialing introduces a much shorter call time-out.

• If manual dial must be used, then the user should wait until the call is answered before starting the fax session.

• If manual dial must be used, then the user should enter the digit 8 before initiating the fax session. This ensures that the fax session is initiated by CallPilot before the fax machine's timer is started.

• The call duration can be increased by adding a timed pause to the end of dialing string (for example: 758-5428,,,,). This allows the call to ring at the destination before the fax machine's call duration timer starts.

• Since the problem is related to the delay in initiating the fax session, the number of rings for fax mailboxes Call Forward No Answer (CFNA) should be minimized.

Page 139, Setting up MCDN over VoIP with fallback

paragraph 2 The one difference between MCDN over PRI and MCDN over VoIP is that the VoIP trunks require specific Remote Gateway settings. 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.

Table 25 Remote gateway record

Field Value Description

Name

Destination IP

QoS Monitor

Transmit Threshold 0.0 (bad) to 5.0 (excellent)

Enter the Mean Opinion Score (MOS) that the system uses to determine when a call needs to fallback to a PSTN line. If the MOS on the transmit channel falls below this value for all of the available codecs, the BCM will fallback to a PSTN line.For more information about MOS, refer to Appendix E, Quality of Service in this guide and the QoS Monitor chapter of the Programming Operations Guide.

Receive Threshold 0.0 (bad) to 5.0 (excellent)

Enter the Mean Opinion Score (MOS) that the system uses to determine when a call needs to fallback to a PSTN line. If the MOS on the receive channel falls below this value for all of the available codecs, the BCM will fallback to a PSTN line.For more information about MOS, refer to Appendix E, Quality of Service in this guide and the QoS Monitor chapter of the Programming Operations Guide.

Gateway Type

Gateway Protocol NoneSL-1CSE

Select the gateway protocol that the trunk expects to use.None: No special featuresSL-1: Use for BCM 2.5 systems only that require MCDN over VoIP trunks

CSE: MCDN protocol for gateways that provide VoIP service through IPT or CSE 1000 gateways (BCM 3.0, 3.01, and 3.5 and newer software).

Destination Digits

6

Page 146, Network engineeringReplace Table 38 with the following table.

Page 148, Bandwidth requirements on half duplex linksReplace Table 39 with the following table.

Table 38 VoIP Transmission Characteristics for unidirectional continuous media stream

Codec Type Payload Size IP Packet Ethernet B/W2 PPP B/W FR B/W

ms Bytes Bytes kbit/s kbit/s kbit/s

G.711(64 kb/s)

30 240 280 81.6 75.2 77.1

G.729(8 kb/s)

30 30 70 25.6 19.2 21.1

G.723.1(6.3 kb/s)

30* 24* 64* 24.0* 17.6* 19.5*

G.723.1 (5.3 kb/s) 30* 20* 60* 22.9* 16.5* 18.4*

Notes:

1) * indicates payload sizes used by Business Communications Manager 3.5 for transmission. Other values listed indicate payload sizes that the Business Communications Manager 3.5 can receive.

2) Ethernet bandwidth includes the 14 byte Ethernet frame overhead plus a 12-byte inter-frame gap.

Table 39 Bandwidth Requirements per Gateway port for half-duplex links

Codec TypePayload Size

Ethernet B/W2 PPP B/W FR B/W

No SPSilence Suppression

No SPSilence Suppression

No SPSilence Suppression

ms peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

G.711(64 kb/s)

30 163.2 163.23 163.23 150.4 150.43 150.43 154.2 154.23 154.23

G.729(8 kb/s)

30 51.2 25.6 25.6 38.4 19.2 19.2 42.2 21.1 21.1

G.723.1(6.3 kb/s)

30* 48.0* 24.0* 24.0* 35.2* 17.6* 17.6* 39.0* 19.5* 19.5*

G.723.1 (5.3 kb/s)

30* 45.8* 22.9* 22.9* 33.0* 16.5* 16.5* 36.8* 18.4* 18.4*

Notes:

1) * indicates payload sizes used by Business Communications Manager 2.5 for transmission. Other values listed indicate payload sizes that BCM can receive.

2) Ethernet bandwidth includes the 14 byte Ethernet frame overhead plus a 12 byte inter-frame gap.

3) G.711 does not support silence suppression.

7

Page 149, Bandwidth requirements on full duplex linksReplace Table 40 with the following table.

Page 150, LAN engineering examplesReplace Figure 54 with the following.

Figure 54 LAN engineering peak transmission

Page 151, WAN engineeringReplace Figure 55 with the following.

Figure 55 Peak traffic, WAN link

Table 40 Bandwidth Requirements per Gateway port for Full-duplex links

Codec Type

Payload Size

Ethernet B/W2 PPP B/W FR B/W

No SP Silence Suppression No SP Silence Suppression No SP Silence Suppression

ms peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

G.711(64 kb/s)

30 81.6 81.6 81.63 75.2 75.2 75.23 77.1 77.1 77.13

G.729(8 kb/s)

30 25.6 25.6 12.8 19.2 19.2 9.6 21.1 21.1 10.6

G.723.1(6.3 kb/s)

30* 24.0* 24.0* 12.0* 17.6* 17.6* 8.8* 19.5* 19.5* 9.8*

G.723.1 (5.3 kb/s)

30* 22.9* 22.9* 11.5* 16.5* 16.5* 8.3* 18.4* 18.4* 9.2*

Notes:

1) * indicates payload sizes used by Business Communications Manager 3.5 for transmission. Other values listed indicate payload sizes that Business Communications Manager can receive.

2) Ethernet bandwidth includes the 14 byte Ethernet frame overhead plus a 12 byte inter-frame gap.

3) G.711 does not support silence suppression. Therefore the average bandwidth is the same as the peak bandwidth.

4) Bandwidths stated per channel (Rx or Tx).

Ethernet B/W2

No SPSilence Suppression

peak(kbit/s)

peak(kbit/s)

Avg(kbit/s)

G.729(8 kb/s)

30 34.4 34.4

PPP B/W

No SPSilence Suppression

peak(kbit/s)

peak(kbit/s)

Avg(kbit/s)

G.729(8 kb/s)

30 24.8 12.4

8

Page 154 Determining network loading caused by IP telephony trafficReplace Figure 57 with the following.

Figure 57 Network loading bandwidth

Page 170, InteroperabilityReplace Table 44 with the following table.

CallPilot Set Up and Operation Guide

Page 26, Target AttendantThe description for Target Attendant should be:

"Lets subscribers set up a Personal Target Attendant. If not, callers are directed to the Attendant Extension that is specified in the Greeting Table."

Chapter 15For how to set up Centralized Voice Mail on a Business Communications Manager system, refer to Chapter 15 of the Business Communications Manager Programming Operations Guide.

Fax Set Up and Operation Guide

Page 42Change the following sentence:

"If you answer a call from a caller who is leaving a fax message in your mailbox"

to:

"If a you answer a call from a caller who wants to leave a fax message in your mailbox"

CallPilot Unified Messaging Installation and Maintenance Guide

Page 8, Supported Integrated clientsAdd the following note:

"To install desktop messaging for Lotus Notes, you must have Manager or Designer control of the user's mail database. This control is set on the server by the Lotus Notes administrator."

Codec Type

Payload Size

PPP B/W FR B/W

No SPSilence Suppression No SP

Silence Suppression

ms peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

peak

(kbit/s)

peak

(kbit/s)

Avg

(kbit/s)

G.729(8 kb/s)

30 19.2 9.6 21.1 10.6

Table 44 Supported voice payload sizes

Codec Receive/transmit

G.711 30 ms

G.723.1 30 ms

G.729 30 ms

9

Message Networking Set Up and Operation Guide

Page 45, Creating a network siteThe information for "Mailbox prefix" should say:

"The mailbox prefix can be the same as the remote site prefix."

CallPilot Manager Help

About Digital Networking site parameters page"Mailbox Prefix" should say:

"Type the remote site prefix.

The mailbox prefix is a prefix added to the beginning of the remote mailbox number to make it unique network-wide.

Make the mailbox prefix the same as the remote site prefix."

Multimedia Call Center Set Up and Operation Guide, Multimedia Call Center Web Developer Guide, Call Center Set Up and Operation Guide, Agent Guide, Supervisor Guide, CallPilot Manager Help

Any references to "Voice Button" should be "Multimedia Call Center".

Multimedia Call Center Set Up and Operation Guide

Page 15, Allowing web access for Multimedia Call Center callsDo not perform this procedure. Instead, make sure that any links to Multimedia Call Center from your website use https: rather than http:

Interactive Voice Response Installation and Configuration Guide

Page 11, To enable a software authorization codeStep 3 should be: "The default user ID is ee_admin."

Step 4 should be: "The default password is PlsChgMe!"

Business Series Terminal Doorphone Installation and Configuration GuideWhen you install a doorphone, you need to perform one of the following:

• In the Unified Manager, click on System. Go to the top menu and click on View, then select Refresh. The Unified Manager refreshes and allows the doorphones to be recognized by the system.

or

• In the Unified Manager, click on System. Go to the top menu and click on Logoff, then select Reboot. The system reboots and brings the doorphones on line. Note: If you do a reboot, telephony services are temporarily unavailable.

Page 11, Table 3 Capabilities fieldsThe description for the Handsfree attribute is incorrect. The correct description is:

• Set Handsfree value to Auto for the BST Doorphone.

10

i2050 Software Phone Installation GuideThe most recent version of the i2050 Software Phone is available on the Business Communications Manager 3.5 Install Client page. If you have a previous version of the i2050 Software Phone, uninstall the previous version and then install the new version from the Install Client page.

Business Communications Manager MSC fru replacement processThe Business Communications Manager 3.5 software has a couple of differences in the text-only menus, than is described in the MSC fru replacement process (P0607273), which was written based on Business Communications Manager 3.0/3.01 software.

Page 8, D. Performing service configuration commands

5 Type 7 (Command line).

6 After the [<systemname>]C:\TEMP> prompt, type the following, then press <ENTER>:f:

Note: If the display does not go to f:\, which is the root directory of the f: drive, then type the following and press <ENTER>cd\

7 After the f: prompt, type the following, then press <ENTER>:cd f:\program files\nortel networks\voice platform

8 Type the following, then press <ENTER>:mscoff.batA number of ChangeServiceConfig actions occur.

9 When the Voice Platform prompt reappears, type the following, then press <ENTER>:sc config voicemscservice start= autoThe system will indicate that the ChangeServiceConfig was successful and return to the Voice Platform prompt.

10 Type Exit, then press <ENTER>.Your system will return to the Main Menu screen.

11 Type 8 (Restart the system).

11

Page 13, G. Uploading the MSC softwareNote that there is an additional step for Business Communications Manager 3.5 software, as the MSC upload prompts are on a separate screen (steps 7 and 8).

7 Type 2 (MSC Upload Menu).

The MSC Initialization menu displays.

8 Enter the number for the core software option appropriate to your region.

The system executes the upload process, which takes approximately five minutes.

9 When the upload completes, type 7 (Platform Initialization Menu).

WarningIf you are unsure of which core load to install, do not proceed. Refer to Before you start on page 3 of the MSC Addendum or contact technical assistance.

12

You are returned to the Platform Initialization Menu screen.

10 Type 1 (Initialize menu).

The Initialize Menu displays.

11 Type 2 (Set service startup to Auto).

12 When the change is complete, type M.You return to the Main Menu.

13 Type 8 (Restart the system).

14 At the restart [A,R] prompt, type R.You will receive an indication that the system is shutting down.

1-800-4 NORTELwww.nortelnetworks.com

P0608409 Issue 02Printed in Canada