NORTEL, the globemark design, and the NORTEL corporate logo are trademarks of Nortel
Networks.
Contents
Contents3
New in this release7
Features 7
Other Changes 9
Introduction11
Fundamentals13
Configuration interfaces 13
Scheduled services 15
Call-by-call service selection 15
Dynamic device configuration 15
SNMP management 19
Music source and BcmAmp 20
System configuration23
BCM450 system configuration preparation25
Connecting to the BCM system through the OAM port 26
Accessing the BCM Web page 26
Downloading and installing Element Manager 27
Downloading the Startup Profile template 27
Downloading the factory default programming record 28
Connecting to the BCM system 28
Viewing or modifying the Welcome panel 29
Saving the programming record 31
Basic parameters configuration33
BCM450 configuration with Telset Administration35
Entering the keycode 35
Configuring the IP address 36
Configuring the modem 37
Selecting the region 38
Selecting the telephony startup template and start DN 38
Initializing voice mail 38
Entering the keycode 41
Configuring the IP address 42
Configuring the modem 43
Configuring the startup template for telephony services 43
Initializing voice mail 44
Entering a name for your system 44
Configuring the date and time settings 45
Configuring DHCP server settings 46
Configuring IP Phones 47
Configuring SNMP settings 49
Configuring the SNMP manager list 50
Deleting an SNMP manager 51
Configuring SNMP community strings 51
Deleting SNMP community strings 52
Configuring service access points 52
Deleting service access points 53
Configuring SNMP trap destinations 54
Viewing and modifying SNMP trap destinations 55
Deleting SNMP Trap Destinations 56
Creating user accounts 56
BCM450 configuration with Startup Profile59
Setting the Excel macro security level 59
Customizing a Startup Profile for your system 60
Loading the Startup Profile data onto your BCM system 61
BCM450 internal resources configuration63
Configuring IP trunks 63
Configuring IP sets and applications 64
BCM450 MBM and legacy Norstar configuration67
Configuring main unit MBMs 68
Configuring legacy Norstar modules 69
Configuring expansion unit MBMs 71
Deconfiguring MBMs and Norstar modules 73
BCM450 trunk module configuration75
Configuring the trunk module parameters 75
Configuring call-by-call service selection 76
Provisioning module lines and loops 76
Dial-up resources configuration79
ISDN interface management 79
ISDN interface connection or disconnection 81
Configuring schedule names and timers 101
Configuring scheduled service 102
BCM450 music source configuration105
Selecting the audio jack as a music source 105
Selecting a network device as a music source 106
Accessing the Music Manager administration Web page 107
Loading music onto the BCM450 108
Adding music to the play list 109
Removing music from the play list 109
Deleting music from the BCM450 110
Using the BcmAmp Player 110
Basic configuration testing113
BCM450 main unit testing115
Testing the main unit 115
Troubleshooting the main unit 116
BCM450 expansion unit testing117
Testing the expansion unit 117
Troubleshooting the expansion unit 118
BCM450 media bay modules testing119
Testing a station MBM 119
Testing a trunk MBM 119
Determining why an MBM does not appear in Element Manager 120
BCM450 analog terminal adapter testing121
Correcting a non-functioning ATA2 121
Correcting no dial tone at the ATA2 121
Confirming correct ATA2 wiring 122
Interface availability 137
Tones and cadences 140
Core parameters for market profiles 150
Analog trunk parameters 167
GASM8 parameters 176
GASI parameters 179
ATA2 parameters 181
Voice mail 185
ISDN line services 187
Analog and digital trunk types 188
This is the initial release of the BCM450 platform. This document contains
information about configuring the BCM450 system in Release 1.0
Features
See the following sections for information found in this document.
BCM450 configuration
You configure your BCM450 system to provide the required system
functionality. A BCM450 system cannot function until it is configured.
You can configure basic parameters (initial parameters and startup
parameters) through Element Manager, Telset Administration, or the Startup
Profile template. For more information about configuring your BCM450
system see, BCM450 system configuration preparation (page 25).
Element Manager configuration
To configure your BCM450 system most efficiently, you can download and
install Element Manager on your computer. You can configure all BCM system
parameters through Element Manager. For more information see, Element
Manager (page 13)and BCM450 configuration with Element Manager
(page 41).
Telset Administration configuration
You can use Telset Administration through a digital telephone with a two-line
display to set the BCM configuration parameters.
You cannot set all the basic parameters using Telset Administration.
Therefore, after configuring the initial parameters, you must use Element
Manager to set the startup parameters. For more information see, Tel se t
Administration (page 14) and BCM450 configuration with Telset
Administration (page 35).
An experienced administrator uses the Startup Profile tool to customize a
template with common BCM system parameters. The administrator uses this
template to configure a single system or multiple systems. For more
information see,Startup Profile (page 14) and BCM450 configuration with
Startup Profile (page 59).
Internal resources configuration
You can configure the internal resources on your BCM main unit. The internal
resources include IP trunks, IP sets, and applications resources. For more
information see, IP sets and applications configuration (page 17) and
You can configure media bay modules (MBMs) for the BCM450. Configurimg
main unit media bay modules (MBM) is a two-stage process. First, identify the
type of installed MBMs to the BCM system, and then configure the required
variables. The BCM system suggests default values for your MBM. For more
information see, BCM450 MBM and legacy Norstar configuration (page 67).
Trunk configuration
Configure the trunk module parameters to define the line properties for your
BCM system. For more information see, IP trunk module configuration
(page 16)and BCM450 MBM and legacy Norstar configuration (page 67).
Music source configuration
The Music on Hold and Background Music features provide music to users.
For these features to function properly, you must connect a music source to
the BCM system and configure the music source. For more information see,
BCM450 music source configuration (page 105).
Configuration testing
Perform basic testing and troubleshooting on BCM main unit, expansion units,
media bay modules (MBM), and analog terminal adapter (ATA) For more
information see, Basic configuration testing (page 113), BCM450 main unit
testing (page 115), BCM450 expansion unit testing (page 117), BCM450
media bay modules testing (page 119), and BCM450 analog terminal adapter
testing (page 121).
Dynamic device configuration
With dynamic device configuration, DN and line number allocation and
assignment is dynamically performed by the system, as required, until either
all hardware administered to a system is populated with the necessary DNs
and line numbers, or the system has reached the maximum capacity.
This section provides conceptual information about BCM450 configuration.
Navigation
•Configuration interfaces (page 13)
•Scheduled services (page 15)
•Call-by-call service selection (page 15)
•Dynamic device configuration (page 15)
•SNMP management (page 19)
•Music source and BcmAmp (page 20)
Configuration interfaces
This section describes the methods to configure your BCM450 system.
While Element Manager is the primary management application, BCM450
also supports the programming of telephony and applications areas through
Telset Administration, and through the Startup Profile template.
Element Manager
The primary management application for configuring and administering the
BCM450 system is Element Manager. Element Manager is a client-based
management application that runs on a Windows computer, or on a Citrix
server.
You use Element Manager to connect to the BCM450 devices to be managed
either through an IP network connection, or through the OAM port on a
BCM450 main unit.
You can download Element Manager from the BCM450 web page and install
it on your computer at any time. However, you cannot connect to a BCM450
system with Element Manager until the BCM450 main unit is installed and
running.
Installing Element Manager in a Citrix environment
You can run Element Manager in a Citrix environment, using the following
software:
•Windows 2000 Server SP4 (fully patched)
•Citrix Metaframe XP Feature Release 3
•Citrix Program Neighborhood Version 7.0
When you run Element Manager in a Citrix environment, install Element
Manager on a Citrix server. You can run Citrix Program Neighborhood to
connect to the server and launch the Element Manager.
Element Manager is designed for single-user environments. A single
installation of Element Manager extends the same user preferences to any
Citrix user, including the device list and any saved passwords. Citrix
administrators can ensure a secure environment by using one of the following
approaches:
•install a copy of Element Manager for each user or group of users in
different folders, with Windows permissions set for the folder to control
access.
•in cases where a shared device tree is permitted, ensure that users do not
save passwords, but instead enter a password each time they connect.
Startup Profile
The Startup Profile is a template containing the basic configuration
parameters that you edit using Microsoft Excel. The Startup Profile is used to
accelerate the initial installation programming of system-level parameters. It
helps bring the BCM450 system to a basic operational and ready-tocustomize state without using either Element Manager or Telset
Administration.
The administrator must fill out the Startup Profile template, save it onto a USB
storage device and insert the storage device into the USB port of the BCM450
main unit before the initial start-up. On start-up the BCM450 system reads the
information and starts up with the correct system parameters and feature
licensing already in place.
Telset Administration
Installers who are already familiar with Telset Administration can perform
programming from the keypad of any telephone connected to the BCM450
device. This alleviates the need for access to a computer at the customer site.
For more information about using Telset programming on the BCM450, see
the following documents:
•Intelligent Contact Center Telephone Administration Guide (NN40160-
602)
Scheduled services
Use scheduled services to control how calls are answered in off-hours
(Ringing Groups), how calls are routed at various times of the day, and how
restrictions are applied on lines and telephones at specific times of the day.
With Element Manager, you can perform the following configuration functions
for scheduled services:
•determine which schedules are active on the system for routing,
restriction, and ringing schedules.
•set the time periods within each schedule for each day of the week.
•rename schedules.
Schedules are activated and deactivated through control telephones.
Restriction and Routing services require a service control password before
users can change scheduling on a control telephone. You use the Service
Control Password field to delete a current entry, and add a new password.
Make a note of the password; the panel shows only asterisks.
15
Call-by-call service selection
The PRI Call-by-call Service Selection is region-specific to North America for
a DTM set to a PRI module type.
By default, incoming calls on a PRI are routed based on the Called Party
Number information within the call request. The last number of digits of the
called party number that match the Received Number Length setting are used
as Receive Digits to find a target line.
In North American PRI, the Call-by-Call services provides alternate routing
maps to be defined in various ways, depending on the protocol defined for this
PRI.
Dynamic device configuration
With dynamic device configuration, DN and line number allocation and
assignment is dynamically performed by the system, as required, until either
all hardware administered to a system is populated with the necessary DNs
and line numbers, or the system has reached the maximum capacity.
Dynamic device configuration applies to internal components on the main unit
including IP trunks, IP sets, and applications, as well as media bay modules
(MBM) and legacy Norstar modules on the main unit and expansion unit.
If a set of directory numbers (call the set X) are configured (either IP Sets or
MBM DNs) with the "Assign Target Lines" selected, then these DNs will have
Target Lines assigned to them (assuming there are unused Target Lines
available).
If a number (n) of the DNs in set X are subsequently Deconfigured, then
although n DNs are gone, the state of the originally assigned Target Lines
associated with these n DNs is:
•they remain programmed with the original DNs' Public and Private
Configured numbers
•they remain assigned to the DN positions (that is, position 1-300) just
Deconfigured
The effect of this is that if, after Deconfiguring n DNs from set X above, a new
DN set Y is configured on the same bus on the system (IP Sets, Applications,
MBM devices), then the first n number of the DNs in set Y will still have the
Target Lines assigned to them that were originally assigned as part of
Configured DN set X. This is independant of the ‘Assign Target Line’ option
selection for this new Configured DN set Y.
The net effect to the administrator is that if s/he Configured DNs with Target
Lines and then decides to Deconfigure and Reconfigure as different DNs, then
the original Target Line assignments and Pub/Priv number programming
follows the Reconfigured DNs.
IP trunk module configuration
Although IP trunks are not physical devices and you cannot remove them from
the system, BCM450 supports modification of IP trunk line numbers. The
initial values assigned by the system on the IP trunks are “guaranteed to work”
values.
You can assign a larger range of line numbers than what is actually licensed
for IP trunks. The effect is to reserve the line numbers beyond the current
licensed line count for future additional IP trunk licenses. Lines beyond the
licensed count do not boot until the necessary keycodes are provided to
enable the additional lines.
The list of line numbers for IP trunks must be consecutive. If the available line
numbers are segmented and the necessary number of consecutive line
numbers does not exist, you receive an error. If this occurs, you must remove
other lines in the system and restart line numbering for devices so the lines
numbers are not as segmented and consecutive groups can be obtained for
all devices.
If additional licensing is added later for more IP trunks such that the licensed
number of IP trunks is greater than the currently provisioned number, then the
system will not automatically request additional line numbers for the new
trunks. In this case the administrator must configure the new line numbers to
populate the additional IP trunks. If additional licensed IP trunks are added
and line numbers are reserved such that these additional trunks are covered,
then no additional line numbering configuration operations are necessary.
IP sets and applications configuration
Main unit telephony resources includes a list of IP set DNs and a range of
application DNs. Services assigned to the IP sets or applications device type
are the DNs of these sets or DNs that an application can use respectively.
Application DNs are the DNs assigned to applications such as the CallPilot
DN, the MeetMe DN, or Contact Center skillset DNs.
The ability to assign IP set and application DN services is limited by the
maximum number of DNs for IP sets and applications respectively, and also
by the maximum total number of relocatable DNs on the system.
There may be notes or warnings in the Configuration dialog box to notify the
administrator of the impact of the configuration action. This may include a
recommendation to restart, or that a service may be restarted automatically.
17
Additional configuration options specify whether or not target lines are desired
for the DNs, and if so a starting public DN, and starting private DN can be
assigned to target lines.
An available target line is one that is currently unassigned to any DN (even a
Hunt Group DN) and has no programmed private or public receive digits
assigned to it. Target line numbers may or may not be consecutive.
Conflicts of public or private line DNs, where the DN is used elsewhere, results
in a failure of the public or private DN assignment to the set in question, but
does not cause the entire request to fail. The sets are configured, but not all
are successfully assigned public or private target line numbers if resource
limitations prevent it.
Once a target line is configured with public or private numbers, deconfiguring
DNs that have appearances of those target lines does not remove the public
or private numbers from those target lines.
The DNs assigned to IP sets or applications do not need to be consecutive. If
the relevant pool DNs are renumbered or changed, so the consecutive DNs
do not exist, then the IP sets or applications have non-consecutive DNs. For
this reason the low and high values for IP sets and applications represent the
lowest and highest DN value currently in the respective assigned range. The
total number of DNs assigned is not all the DN values in between the low and
high values.
Configuring IP or Application DNs is a cumulative action. Every new
successful configuration request adds the relevant count of IP or Application
DNs to the existing range. Existing DNs are not affected or changed in any
way. The default number of DNs to add is normally zero. This is a protection
mechanism. You must change the number of DNs in the Number of DNs to
add field to the desired number of additional DNs.
When you configure DNs there is an exception to the number of DNs you can
add. The BCM450 system requires a minimum of three configured application
DNs for applications to function correctly. When you configure application
DNs, if there are fewer than three currently configured application DNs, then
the minimum number possible to configure is set so that the final configured
application DN count is at least three. For example, if through Set-based
administration you complete a DN deconfiguration, and only two configured
application DN remains, then the next time you configure application DNs the
system would permit a minimum of two additional DNs to be configured for a
final total of three.
Finally, you can partially configure IP sets and applications (but not MBMs)
with fewer DNs then the licensed device count. If there are not sufficient DNs
defined in the relevant pools then the number of available DNs are allocated
to the services list.
Main unit and expansion unit MBM configuration
During media bay module (MBM) configuration, the BCM450 system provides
suggested default values for the MBM. These suggestions include DNs or line
numbers. If you change configuring data from the defaults provided and the
configuration fails, then the configuration reverts back to the suggested
values.
When configuring a line device, a starting line number is specified. Based on
the MBM type and region configuration, the appropriate number of line
numbers are allocated and associated with the ports of the MBM. If insufficient
resources are available to complete the requested configuration then the
device configuration fails.
For combination devices, configuration of the individual components is treated
separately. It is possible for one part of a combination device to get configured
while the other part fails because of insufficient resources.
The location of a device is independent of the bus value associated with a
device. For example, an MBM in location “Main MBM 1” can be assigned Bus
10 in one configuration, but subsequent changes to the configuration can
result in “Main MBM 1” assigned to Bus 11 (or any other valid bus value). The
bus assigned to a device is now one of several resources that a device
receives during configuration to become operational.
It is possible for a configuring request of a device to fail if sufficient resources
are not available. This can be a result of insufficient contiguous line numbers,
not enough remaining DNs, or no busses remaining. If sufficient resources are
not available for a configuring request, the system presents a dialog box that
the device configuration request failed.
When a BRI MBM is configured all loops on the MBM are defaulted as T-loops
and the administrator must provide a starting line number for a BRI MBM upon
configuration. It is important to note that a BRI MBM uses eight consecutive
line numbers. This is to ensure a consecutive series of line numbers across a
BRI MBM regardless of the loop type setting.
You configure the R2MFC MBM as a DTI-PRI MBM with additional
configuration to set the attributes of the PRI protocol such that the device
operates as an R2MFC.
DNs are dynamic and changing a loop on a BRI-ST device from S to T type
completely removes those DNs from the system.
DSMn16+/32+ MBMs are capable of double density. If you want to maximize
TDM sets on a system using an expansion unit, you need to set the dip
settings on the DSM32+ MBMs in the chassis to double density mode.
SNMP management
SNMP (Simple Network Management Protocol) is a set of protocols for
managing complex networks. SNMP-compliant devices, called agents, store
meta-data in Management Information Bases (MIBs) and provide this data to
SNMP requesters.
You can configure general SNMP settings, including enabling and disabling
the SNMP agent, enabling and disabling versions of the SNMP agent, defining
access permissions, and adding and deleting SNMP management stations.
You can create a list of SNMP managers who are permitted to query the
BCM450 system by specifying their IP addresses. If you have specified SNMP
managers, the BCM450 SNMP agent will respond only to SNMP requests
from those IP devices.
You can use external SNMP clients, such as HP OpenView, to monitor
theBCM450 system by means of read-only SNMP requests.
The BCM450 main unit supports the following versions of SNMP:
•SNMP v1 — the first implementation of SNMP; this version supports such
protocols as IP
•SNMP v2C — provides improved efficiency and error handling
•SNMP v3 — provides improvements in security and privacy
Using the Element Manager, you can select which versions of SNMP you want
the BCM450 agent to support. For more information, see Configuring SNMP
settings (page 49).
Management Information Bases provide access to the managed objects of a
system and specify the format of traps. BCM450 supports the following MIBs:
•RFC 1213 — MIB II
•RFC 2863 — Interface MIB
•RFC 2737 — Entity MIB
•RFC 2790 — Host MIB
•RFC 2261 — SNMP framework
•SmallSiteEvent MIB for traps
Music source and BcmAmp
This section describes the music source for your BCM450 system.
Music source
The Music on Hold and Background Music features provide music to users.
For these features to function properly, a music source must be connected to
the BCM.
There are three ways you can connect the music source to the BCM system:
•You can connect an external music source through an analog input to the
BCM.
•You can use the IP Music feature to connect to Music Manager. Music
Manager is an audio player application that resides on the BCM system
and provides a streaming audio signal to the BCM system.
•You can use the IP Music feature to connect to an external music source
on the data network.
You must connect the external music source to your network and it must be
accessible to the BCM system. The external music source must also produce
a streaming audio signal that is compatible with the BCM system.
Select Music Manager if you are using the IP Music feature to connect to the
music source available on the BCM. If you select Music Manager, you must
configure the BcmAmp application before you can use it.
Select Streaming Server if you are using the IP Music feature to connect to a
music source on the data network. If you select Streaming Server, you must
configure the Network Device before you can use it.
For information about connecting an external music through and analog input,
see Installation—System (NN40160-301).
BcmAmp application
The audio files loaded onto the BCM system are loaded into the same disk
space that is used for CallPilot messages. Therefore, every minute of audio
file loaded onto the BCM system reduces the amount of message storage
space available to CallPilot by one minute. To ensure the proper operation of
both Music Manager and CallPilot, the following restrictions are applied to
uploading audio files.
•The maximum size of any single sound file you load onto the BCM system
is 150 MB.
21
•The maximum amount of disk space available for Music Manager audio
files is 1 GB.
•To ensure there is sufficient disk space for CallPilot, Music Manager
Administration prevents you from uploading files if there is less than 1 GB
of free disk space on the BCM system.
To minimize the time required to upload audio files, record the audio files as a
single channel (mono) using 8-bit samples at a rate of 8 kHz.
To configure your BCM450 system most efficiently, you can download and
install Element Manager on your computer. You can download the Startup
Profile template, if you want to use it to set the basic parameters for your
BCM450 system. A programming record template that provides the default
parameters is also available for download.
Prerequisites to BCM450 system configuration preparation
•You can use the latest Element Manager version to manage all previous
BCM systems that require Element Manager. You need only one instance
of Element Manager on your computer.
•Element Manager has the following system requirements:
— Windows: Windows 2000 Pro, Windows XP, or Windows Vista
(Business, Ultimate, and Enterprise versions)
— RAM: minimum 256 MB, recommended 512 MB
— free space: 150 MB
— A Citrix server supports access to Element Manager
BCM450 system configuration preparation navigation
•Connecting to the BCM system through the OAM port (page 26)
•Accessing the BCM Web page (page 26)
•Downloading and installing Element Manager (page 27)
•Downloading the Startup Profile template (page 27)
•Downloading the factory default programming record (page 28)
If you must change the IP address (due to a conflict with your network), you
can connect to the BCM system through the OAM port.
Prerequisites
•Before using the default address on your network, check with your system
administrator. If this address conflicts with the LAN settings, you can
cause network damage if you connect to the network without changing the
IP address.
•Obtain a standard Ethernet cable.
Procedure steps
StepAction
1Connect one end of the Ethernet cable to the OAM port on the main unit.
2Connect the other end of the Ethernet cable to the Ethernet port on your
computer.
The DHCP-enabled computer is assigned IP address 10.10.11.2.
(255.255.255.252).
Accessing the BCM Web page
After you connect your computer to the BCM system, you can download
Element Manager from the Administrator Applications area of the BCM Web
page.
Prerequisites
•Ensure you connect your computer to the BCM system, either through the
OAM port or through a LAN connection.
Procedure steps
StepAction
1Open a Web browser and enter the BCM system IP address:
•If your BCM450 is installed on a network, type the address on the
network in the form, http://xxx.xxx.xxx.xxx.
• If your BCM450 is installed but not yet configured, connect directly to
the BCM450 through the OAM port and type, http://10.10.11.1
•Download and install Element Manager. For more information, see
Downloading and installing Element Manager (page 27).
Procedure steps
StepAction
1Launch Element Manager.
2From the Network menu, click New Network Element > Business
Communications Manager.
3In the IP Address box, type the BCM system IP address.
4In the User ID and Password boxes, type the following information:
•User ID: nnadmin
•Password: PlsChgMe!
5Click OK.
6From the Network Elements list, select your BCM system IP address.
29
7Ensure that the user name and password are entered.
8Click Connect.
You are now connected to the BCM system.
--End--
Viewing or modifying the Welcome panel
The Welcome panel displays information for the current account logged on the
system. The administrator is prompted to change the password before any
programming menus are accessible.
The initial Welcome panel displays:
•on the first login to the BCM by nnadmin
•when the administrator has selected the forced password change option
on an account