BCM50 - System Overview
Business Communications Manager 50 3.0 (BCM50 3.0) introduces software enhancements, including Session Initiated Protocol (SIP)
trunking, to the BCM50 Platform.
This release of BCM50 introduces the following enhancements:
Enhancements to the SIP trunk solution
Introduction of new IP sets & accessories: the 1200 series IP sets, the 1110 IP set and the expansion module for the 1120E & 1140E sets.
Introduction of new end user features: Meet-Me Conferencing and Silent Record-a-call
Enhancements to the Intelligent Contact Center solution
Introduction of Activity Reporter
Introduction of operability enhancements
Introduction of NCM4.0 which includes a new NCM feature to support RADIUS for user authentication and authorization.
BCM50 continues to be a complete, converged voice, data, and feature-rich business telephony applications solution for small business and small enterprise branch offices. BCM50 gives you the features and applications of traditional small office PBX and key systems plus the new converged value of IP.
BCM50 hardware
BCM50 (as shown in Figure 1) is available in six configurations.
BCM50: The compact main unit, suitable for networks where you do not require integrated data-routing capability or if your networks already have an IP network.
BCM50a: Includes an ADSL router.
BCM50e: Includes an integrated Ethernet router.
BCM50b: Includes an integrated Dual ISDN S/T BRI.
BCM50be: Includes an Ethernet router and a Dual ISDN S/T BRI.
BCM50ba: Includes ADSL router and a Dual ISDN S/T BRI.
BCM50 main unit
The BCM50 Main Unit (with telephony only) provides call processing and simple data-networking functions. It provides connections for 12 digital telephones, 4 PSTN lines, 4 analog station ports, and 4 connections for auxiliary equipment (auxiliary ringer, page relay, page output, and music source). The BCM50 Main Unit has no router, but it has four LAN ports: one is the OAM port for technicians, and three are for basic LAN connectivity.
A Main Unit contains the following field-replaceable units:
one programmed hard disk
one cooling fan
one router card (BCM50a, BCM50e, BCM50ba and BCM50be only)
Additional BCM50 hardware
The BCM50 expansion unit is a compact unit that accommodates the Media Bay Modules (MBM) used by other BCM platforms. The BCM50 main unit can support a maximum of two expansion units. The wall-mount bracket is an inexpensive bracket for mounting the BCM50 or expansion unit to a wall. An optional wiring card, which provides RJ-45 connectors for all main unit trunk and station interfaces, is also available for use with the wall-mount bracket. The rack-mount shelf is an inexpensive shelf for mounting a maximum of four BCM50 systems into a standard 19-inch rack. An optional patch field that provides RJ-45 connectors for all main unit trunk and station interfaces is also available.
BCM50 supports the complete range of IP telephony capability offered by existing BCM products. These features are enabled through keycodes and require no additional hardware:
VoIP Gateway (H.323 or SIP): up to 12 VoIP trunks
VoIP Telephony Clients: up to 32 VoIP Telephony clients, that support the IP Softphone 2050 client, the Mobile Voice Client 2050 and the complete range of Avaya IP phones
SIP Gateway trunks: up to 12 SIP trunks
BCM50 physical dimensions
BCM50 has a compact plastic enclosure so that you need not add hardware to enable features and applications. The compact size and flexible installation options support fast installations and accommodate the diverse environmental and physical conditions of small businesses. The following table describes the physical dimensions of the BCM50 main unit and expansion unit.
The BCM50 main unit and expansion unit design features include in following components:
external power supply
stackable units
rubber feet that allow unit installation on a desktop or a shelf
optional wall-mount bracket
optional rack-mount shelf
BCM50 physical interfaces
The BCM50 interfaces preclude the need for additional hardware.
Your BCM50 is equipped with these interfaces:
Twelve digital station ports support the complete line of Business Series Telephones. These ports are accessible through the front panel RJ-21 connector and are enabled through keycodes.
Four Analog Loop Supervised Trunks. These ports are accessible through the front panel RJ-21 connector and are enabled through keycodes.
Four Analog Station interfaces with message waiting and CLID support. These ports are accessible through the front panel RJ-21 connector and are enabled through keycodes.
Page and auxiliary relay output on the front panel RJ-21 connector.
Three-port 10/100 Ethernet switch with automatic sensing and automatic polarity. Two of these ports support connecting optional expansion units.
One 10/100 Ethernet port reserved for direct-access management of the system.
Music on hold input supported either through the front panel jack or an RJ-21 connector.
USB port to enhance BCM50 management.
Telephony features
BCM50 provides a full set of telephony features that can respond to the various requirements of your business. BCM50 supports the following features and components:
Full set of base telephony features consistent with the BCM portfolio.
Business Series Telephones including Doorphone
analog station terminals, including phones and fax machines
IP telephony features
BCM50 offers the complete range of IP telephony features currently provided in the BCM50 product line:
G.711 and G.729 codecs
echo cancellation
H.323 IP trunking and MCDN over H.323
SIP and SIP proxy
MCDN SIP trunking
Gatekeeper
T.38 Fax
BCM50e and BCM50a: BCM systems with integrated routers
BCM50 is available with an optional integrated ADSL or Ethernet router. These units suit the needs of small businesses and small enterprise branch offices that require external data networking, such as Internet access or VPN-based networking to other offices. Two variations of the BCM50 have an integrated router, depending on the WAN interface you require: the BCM50e (Ethernet WAN) and, BCM50a (ADSL WAN). Both routers have the following data features:
secure Internet access
multisite VoIP trunking using secure VPN tunnels
wide-area VoIP applications with remote user support
remote IP management and support using VPN clients
Common features and capabilities
BCM50a and BCM50e share the same functionality, which focuses on secure Internet access and VoIP.
Note: Support for desktop clients includes Avaya IP telephone portfolio including IP Phone 1210, IP Phone 1220, IP Phone 1230, IP Phone 2001, IP Phone 2002, IP Phone 2004, IP Phone 2007, IP Phone 1110, IP Phone 1120e, IP Phone 1140e, IP Audio Conference Phone 2033. Support for soft-clients is offered through the IP 2050 software phones that extend voice services to mobile and home-based employees over the Internet.
BCM50e and BCM50a have three additional Ethernet LAN ports for a total of six LAN ports for local premises use. All Ethernet ports are 10/100 Mb/s automatic sensing and support automatic polarity. Therefore, you require no crossover cable to connect data hardware to the unit. An additional port is provided for WAN access for, either Ethernet or ADSL. The following features make BCM50a and BCM50e attractive for small sites that want to become Internet-capable and multisite enterprises with many small sites. Until now, these sites could not be part of the corporate WAN because of the high cost of traditional WAN connectivity and managed service.
VPN
10 IPSec Branch Office Tunnels (peer-to-peer)
IPSEC client termination supported
support for bandwidth management
support for Dynamically addressed peers ABOT
support for Client Tunnel origination (not termination) to simplify the connection to a larger VPN Router network
IKEv1 Main Mode
IKEv1 Quick Mode
Diffie-Hellman Group 1,2
IPSec Tunnel Mode
ESP
NAT Traversal
NAT
many-to-one, static, many-to-many
port forwarding
IPSec pass through
NAT support for tunnel mode IPSec tunnels
Throughput traffic performance - 23.1 Mb/s
IP Services
DHCP client
DHCP server with support for Avaya Internet Telephones
DHCP Relay supported
DNS Proxy
DNS with VPN client
WAN failover supported
PPPoE
PPTP (ethernet router only)
Configurable MAC address
Clear text traffic:
WAN to LAN 33.9 Mb/s
LAN to WAN 30.5 Mb/s
Security Services
cryptographic services
DES and 3DES
data authentication SHA-1
data authentication MD-5
authentication services
preshared secrets
security services
stateful firewall
intrusion detection
AES support
digital certificates supported
RADIUS support
Router
Clear text routing
Static: through tunnel
RIP v1: through tunnel and clear text
RIP v2: through tunnel and clear text
BCM50e
The BCM50e provides call-processing and data-routing features and is suitable for networks that require data-routing capability using an integrated Ethernet router. The WAN interface port provides 10/100 Ethernet with automatic sensing and automatic polarity. If you have existing or alternative WAN access technology, you can still benefit from the VoIP features of the BCM50.
BCM50a
The BCM50a provides call-processing, data-routing features, and an integrated ADSL modem. The BCM50a is a stand-alone set of integrated applications. With the BCM50a, you have complete voice and Internet service with efficiency and convenience.
These features provide a complete, integrated Communications Server/ADSL access package for ease of interconnecting with service-provider ADSL networks:
ITU G.992.1 (G.DMT)
G.992.1 Annex A
ITU G.992.2 (G.Lite)
ANSI T1.413 Issue 2
DSL Forum document TR-042 ATM Transport over ADSL
G.hs 994.1
G.ploam G.997.1
Autonegotiation rate adaptation
RFC 2364 PPP over AAL5
RFC 2684 Multi protocol Encapsulation over ATM, both Bridged and Routed encapsulation
Support for British Telecom SIN 329
Broadband IP Products requirements for End User NTE equipment, where the router and ADSL modem functions are integrated into one device
RFC 1483 Multi-protocol over AAL5
RFC 2365 PPP over AAL5
RFC 2516 PPPoE
Traffic-shaping UBR, CBR
ATM forum UNI 3.1/4.0 PVC (minimum 5 PVCs)
BCM50b, BCM50ba, and BCM50be: BCM systems with integrated BRIs
The BCM50 system provides private network and telephony-management capability to small and medium businesses the EMEA and APAC markets. The BCM50 integrates voice and data capabilities, IP telephony gateway functions, and data-routing features into a single telephony system. The BCM50 is a compact system that you use to create and provide telephony applications for use in a business environment.
Common features and capabilities
BRI Compact Daughter Card (CDC) Performance conforms to ITU I.430, ETSI ETS 300012, ANSI T1.605, and safety standards and lightening protection
Additional CDC connector, for a total of two CDC slots
Xilinx FPGA - XC3S400-4FT256C
Integrated eight-port 10/100 Ethernet switch to support future eDSP CDC (upgraded from five-port)
2.5 in. hard drive and new bracket
Optimized position of fan cable, SATA cable, and hard-drive connector
POL Current Limiting
Introduce BRI and improve pack performance, and customer feature set.
Memory parity
Upgrade DSP and microprocessor
GASI support
BCM50b
The BCM50b Main Unit provides functionality similar to the BCM50 main unit. The difference is that the BCM50b main unit has two integrated BRI ports that replace the four analog lines on the RJ-21 telephony connector.
new CSC with integrated BRI in place of integrated GATI
keycode BRI ports
BCM50ba
The BCM50ba Main Unit provides similar functionality to the BCM50a main unit. The difference is that the BCM50ba main unit has two integrated BRI ports that replace the four analog lines on the RJ-21 telephony connector.
BCM50be
The BCM50be Main Unit provides similar functionality to the BCM50e main unit. The difference is that the BCM50be main unit has two integrated BRI ports that replace the four analog lines on the RJ-21 telephony connector.
BCM50 expansion unit and media bay modules
You can expand BCM50 trunk and station capacity by connecting up to two external BCM50 expansion units. Expansion ports on the BCM50 are enabled through keycodes. The expansion unit fits easily with the BCM50 and is easy to integrate and install using the wall-mount and rack-mount accessories. The expansion unit connects to the BCM50 using an RJ-45 CAT5 cable and uses its own external power supply, both of which are provided with the expansion unit.
Each expansion unit can support one Media Bay Module (MBM) and, the same modules currently supported in the BCM products. BCM50 supports the following Media Bay Modules:
4x16 Combo (4 analog trunks, 16 digital stations) North America only
8x16 combo (8 analog trunks, 16 digital stations)
ADID4 and ADID8 modules North America only
ASM8+ (8-port analog station interface) North America only
CTM4 (4-port CLID trunk module) North America only
CTM8 (8-port CLID trunk module) North America only
DTM (digital trunk module)
BRI (ISDN Basic Rate trunk module)
DSM16+ (16-port digital station module)
DSM32+ (32-port digital station module)
GATM4 (4-port global analog trunk module)
GATM8 (8-port global analog trunk module)
GASM8 (8-port global analog station module)
R2MFC
Mounting kits
Businesses can have a range of physical environments in which the system must be installed. The BCM50 has optional accessories you can use to tailor the installation to the needs of the location.
Small System Wallmount Bracket
You can use this optional bracket to mount the BCM50 and expansion unit on a vertical surface. Attach the bracket to the surface and hang the BCM50 from the bracket. The details on the bracket ensure that the BCM50 securely locks into place. The bottom of the bracket includes a covered cable tray to organize cables. An optional add-in card that mounts into the cable tray is available, to provide RJ-45 connections for the main unit trunk and station interfaces.
Small System Rackmount Shelf
You can install this optional shelf in a standard 19-inch rack and mount the BCM50 and expansion unit on it. The details on the shelf firmly lock the BCM50 in place. The bracket also provides space to store power supplies for the BCM50. An optional patch panel is available to provide RJ-45 connections for the main unit trunk and station interfaces.
Software upgrade
The upgrade impacts all on-box software of a field installed BCM50 1.0 or BCM50 2.0 system to BCM50 3.0 software while preserving customer programmed data. New software introduced as part of the BCM50 3.0 program is installed as part of the upgrade. An upgraded BCM50 3.0 system is functionally equivalent to a factory BCM50 3.0 system. The target time for an upgrade is 45 minutes. The upgrade with BCM50 and Business Element Manager supports remote and scheduled upgrades. This new capacity is significant for partners and administrators to reduce installation costs and business impacts. Systems that operate in SRG mode are upgraded to the new software but remain in SRG mode after the upgrade. Support exists for the following upgrade paths: BCM50 1.0 to BCM50 3.0 BCM50 2.0 to BCM50 3.0 BCM50 1.0 to BCM50 2.0 to BCM50 3.0
BCM50b, BCM50ba, and BCM50be: BCM systems with integrated BRIs
The BCM50 system provides private network and telephony-management capability to small and medium businesses the EMEA and APAC markets. The BCM50 integrates voice and data capabilities, IP telephony gateway functions, and data-routing features into a single telephony system. The BCM50 is a compact system that you use to create and provide telephony applications for use in a business environment.
SIP trunk enhancements
SIP REFER
BCM50 3.0 supports SIP REFER, which is the call transfer mechanism for SIP. BCM50 responds to a REFER request on an existing call by making a second call and transferring the two calls together. BCM also responds to a REPLACE request on an incoming call by replacing the identified incoming SIP call with this new call.
SIP refer supports two types of call transfer:
Blind (or Unattended): The TransferOR puts the primary call on hold, then dials the Transfer Target and completes the transfer without communicating with the Transfer Target. The TransferEE hears ringback on the secondary call and connects when the
Transfer Target answers.
Consult (or Attended): The TransferOR places the primary call on hold and establishes a Consult call (consultation) to another party. After the consultation, the TransferOR completes the transfer, causing the TransferEE to connect to the Transfer Target and replaces the Transfer Target's call with the TransferOR.
SIP proxy failover
A new setting, called Route all calls using proxy, on the SIP Proxy tab in the Business Element Manager, determines whether to ignore the Routing Table for SIP calls. With SIP proxy failover, the SIP Proxy configuration is used. The SIP Proxy Domain is mandatory and is used in SIP message headers. A dedicated SIP Proxy Agent provides outbound proxy failover. The SIP Proxy Agent runs within the SIP Component of the FEPS process on the BCM. To provide an alternative call route to a destination, the SIP Proxy Agent interacts with the Functional Endpoint Proxy Server (FEPS) during outgoing SIP trunk call setup. When proxy failover provides no on-demand SIP proxy information, the SIP Proxy Agent interacts with the SIP facilities within the FEPS to periodically poll each configured SIP proxy server to maintain the up or down status of each server.
RFC 2833
With RFC 2833 the BCM SIP gateway can send and receive Dual-Tone Multi Frequency (DTMF) digits on SIP trunks using RFC 2833. This feature does not apply to H.323. For outgoing digits received, the core software enters the digits as DTMF. The Digital Signal Processor (DSP) intercepts the digits and encodes and them as described in RFC 2833. This is required in both short- and long-tone mode whenever the media path goes through the BCM. When the media path does not go through the BCM, the short tone digits are sent to Functional Endpoint Proxy Server (FEPS) in VDI messages. For incoming digits, the core software handles incoming digit indications from FEPS and provides short-tone functionality. While the digits received can be longer than the short-tone duration, the long duration is not required.
SIP trunk authentication
SIP trunk local users are accounts used to authorize remote SIP entities when they attempt to connect through the SIP trunk interface to place calls through the BCM. SIP trunk accounts are also used for remote connections to the ISP and incoming call requests. The total number of SIP trunk accounts is 240. Configuration of domain and ports for remote SIP trunk endpoints. Configuration and use of domain and port entries for remote endpoints allows more flexible installations, compared to the BCM 4.0 and BCM50 R2 use of IP addresses only. The BCM50 3.0 introduces RFC3263-based DNS support for locating SIP servers. The addition of DNS support means that customers do not need to know the IP addresses of those remote servers. Standards based DNS support using RFC3263 to simplify network deployment.
Optional G.711 based transport of FAX communication
This solution will allow the choice of whether T.38 or G.711 is used to transmit fax calls over SIP trunks, to and from the BCM. The choice is decided during configuration, and applies to all SIP trunk calls If T.38 is not configured, then SuperG3 fax and V.34 modem will be supported over G.711. Previously, they had to use G3/V.17 in case there was a switch to T.38 which cannot encode V.34 successfully.
IP phone 1200
BCM50 3.0 supports new IP Phone 1200 series and associated expansion modules.
IP phone 1110
The BCM50 system provides private network and telephony-management capability to small and medium businesses the EMEA and APAC markets. The BCM50 integrates voice and data capabilities, IP telephony gateway functions, and data-routing features into a single telephony system. The BCM50 is a compact system that you use to create and provide telephony applications for use in a business environment.
Meet-Me Conferencing
Meet-Me Conferencing provides feature-rich, high density conferencing capabilities for BCM users. Designed to provide a more sophisticated feature set for formal conference calls, Meet-Me Conferencing allows parties to establish a teleconference by calling in to a specified bridge number at an agreed on time. One party acts as the chairperson and has additional powers to start, stop, secure and control the conference. Conferences are initiated by calling in to the system on designated lines or to a specified directory number. The service responds by prompting the caller for the conference ID and optional pass-code. The caller then receives music-on-hold until the chairperson starts the conference. At that point, a multi way voice conference is established with all parties in the conference.
Meet-Me Conferencing supports DTMF-based commands and display/softkey based commands, so all users, regardless of phone, have access to participant and chairperson controls. All parties can use DTMF-based commands to control their participation (example: mute on or off). When using DTMF-based commands, the help menu will provide an audible list of existing commands. Additionally, the system will provide voice prompts to assist the user. For example, when a user turns on the mute feature, they will receive a voice prompt saying, muted. When they turn off the mute feature, a voice prompt will say, un-muted. Display set users receive status information by way of the display. Softkey equivalents are offered to softkey-set users.
Status display and softkeys for internal participants include the following:
status shows elapsed time, number of participants
VIEW softkey cycles through list of participants, showing name (internal) or CallerID (external)
command to turn on or off the mute line
Chairperson commands include the following:
turn conference mute on or off. While the conference is muted, only the chairperson can speak
selectively mute or disconnect a participant with VIEW
lock or unlock a conference. While locked, no new participants can join conference.
change continuation or announcement settings
all participant commands (self-mute on or off, participant count, list commands)
The Meet-Me Conferencing feature supports 18 active ports spread over as many conferences sessions as desired. Note that the pool of conference ports is shared between Meet-Me Conferencing and the ad-hoc conference feature. Since the total pool of ports is 18, this means that if 18 ports are in use for Meet-Me Conferencing, there will be no available ports for ad-hoc conferences. Similarly, if 18 ports are being used for ad-hoc conferences, there will be no ports available for Meet-Me Conferences.
Intelligent Contact Center
Intelligent Contact Center API's
Enhanced Intelligent Contact Center API's are included providing more flexibility and functionality enabling 3rd party applications, like CRM adaptors, to more effectively integrate with the BCM50 Intelligent Contact Center. The API's are:
Agent log in,
Agent log out,
Not ready
Not Ready Time Out
Previous to this release, when a call is presented to an agent and is not answered, the call is returned to the skillset queue and the agents set is placed into the not ready mode. The agent receives a visual indication that they are placed into the not ready mode and no further calls are presented to the agent until they manually take themselves out of the not ready mode. This enhancement provides an administrable timer that when the timer has expired the agent will be made active an d receive calls. The agent does not have to manually make themselves available.
Not Ready Audible Notification
When an agents is placed into the Not Ready Mode the agent receives an audible and visual reminder that they are in the not ready mode. This is an enhancement to BCM50 2.0 where only a visual reminder is provided.
Agent Break Time Configurable on Agent Basis
This enhancement allows the Agent Break (wrap time) Time to be configurable on an agent by agent basis. The Agent Break Time, is the time that the agent is automatically taken out of the skillset after completion of a call. Typically, this time is required to complete paper or other activities associated with the call. Currently Agent Break Time is only configurable on a skillset basis. This provides more flexibility to call centre manager enabling individual agents to have different break times based on their experience and or other needs.
Primary and Secondary Alerts Configurable on a Skillset Basis
Primary and Secondary Alerts are now configurable on a skillset by skillset basis. Primary and Secondary Alerts provide visual indication when calls have been waiting beyond specific thresholds to agents and supervisors. In BCM50 2.0 the Primary and Secondary Alerts are configurable on a system wide basis, not on a skillset basis. The enhanced capability provides more flexibility for the Intelligent Contact Center manager as each skillset can have different Primary and Secondary Alerts based the characteristics of the skillsets. For some skillsets it may be acceptable to expect and tolerate longer wait times then others. As such the Primary and Secondary Alerts can be established specifically for each skillset.
.
Reporting for Contact Center
There are many enhancements to the Reporting for Contact Center included in BCM50 3.0. These include additional information to existing reports, more flexibility in how reports are generated and a new Call Audit that provides a complete view of everything that occurs on a call from the moment it arrives in the Contact Center until it leaves. These enhancements include:
Call Audit Report
This is a new 'cradle to grave' report
Answered Call Report
New report that reports CLID and DNIS of answered calls
Agent Audit Report
New ringing and not available fields
Abandon Call Report
Added DNIS and Skillset fields
Agent Activity Report
Added available time, not available time and ringing time fields
Agent Average Report
Added internal transactions, non CC transactions, not ready time, not available time, ringing time and supervisor monitoring time
Agent Capacity Report
More granularity
Breaks down the instances and time based on each time all agents are busy
Agent Profile Report
Can now report on multiple skillsets,
Added not available time, ringing time, supervisor monitoring time, internal transactions and non CC transactions
Real Time reports
Added new agent states; ringing and not available
New Agent selection method
Greater flexibility in what agents reports will be reporting on and allows Agent Reports to be generated by individual agents as well as skillsets.
Activity Reporter
For information about the Activity Reporter and Activity Reporter Basic features, see the Activity Reporter Administration Guide and the Activity Reporter User Guide.
Operability enhancements - Power On Self Test logging
Power On Self Test (POST) is a set of hardware tests occurs early in the system boot cycle. The data from these tests will be captured and published to the standard log system when the boot cycle is complete. When there is failure from POST, alarms and SNMP traps will be raised through existing DiaLogger component. When BCM 50 is powered up, it goes through a number of POST to validate the system. Results from the POST are currently displayed on the serial port in real time. If there are any failures, the results are also captured on Flash. It is desired to capture all POST results, whether they are passed or failed, so that all results can be displayed at a later time for analysis. The solution provided here is a complete solution for making POST results available on the main file system.
IP Music enhancements
The volume normalized enhancement resolves issues where the on hold play back volume is too loud and can not be adjusted.
The multiple files upload feature enhancement allows customers to upload multiple music files in a compressed format. The files preservation over upgrade enhancement resolves issues where music files are not preserved over upgrade, specially important for professional music recordings.
Business Element Manager change tracking logs
Bring back the tracking changes log that was available on BCM 3.x this log was very useful in validating and checking steps that lead up to a failure and also validated the steps the installer took to get in to the configuration problem. This log tracked all changes that had been applied to the system since it was initialized. The log records the entire configuration steps, not just the final result.
System ID field copy
This feature allows you to copy the System ID field from the Element Manager to your PC clip board, and can then paste it directly into the KRS web tool interface. By implementing this simple ease-of-use functionality, you can remove the human error in querying, downloading and applying the wrong keycode file to a system that will impact the installation time. Also, this can help to prevent the case of applying the new authorization code to the wrong system ID and generate the wrong keycode which can only be reset by Avaya support which impacts installation time, potential miss customer delivery of system, and cost of ownership.
Security enhancements
In addition to the enhancements mentioned in SIP trunk authentication on page 22, BCM50 3.0 includes these new security enhancements.
Last failed login time
The last failed login time information is added to the current user panel in BEM and displays the last time the login was attempted and failed.
Web access on Secure Socket Layer Version 3
BCM50 3.0 sets the default Secure Socket Layer (SSL) protocol to SSLv3 for Web access.
Platform accounts
Platform accounts are integrated accounts that allow access to BEM and other functions based on privileges. The maximum number of accounts is increased to 280 active accounts for each BCM.
User ID length
The maximum character length for the user ID is 128 characters.
Microsoft Vista operating system
BCM applications for BCM50 support the following Vista versions: Windows Vista Business, Windows Vista Ultimate, and Windows Vista Enterprise. BCM applications support both 32-bit and 64-bit versions of Windows Vista, except for the following limitations:
The CTE TAPI option is not supported by the 64-bit version of Windows Vista (x64).
Personal Call Manager is not supported by the 64-bit version of Windows Vista (x64).
Reporting for Contact Center is not supported by the 64-bit version of Windows Vista operating systems.
CallPilot Desktop Messaging 4.0 does not support Groupwise 7.x on Windows Vista operating systems.
The IP SoftPhone 2050 is not supported by the 64-bit version of Windows Vista operating systems.
VPN client is not supported by the 64-bit version of Windows Vista operating systems.
WinHlp32.exe help file exception
WinHlp32.exe, previously used to display the help files (.hlp files), is not included in Microsoft Windows Vista. The Windows Help program does not ship as a component of Vista. Also, third-party programs that include .hlp files are prohibited from redistributing the Windows Help program with their products. To view 32-bit .hlp files, you must download the program from the Microsoft Download Center, and then install it on your computers.
VPN exceptions
The Avaya VPN Client for Vista has the following limitations:
The Avaya VPN Client must be run as an administrator. UAC always prompt for elevation when it runs.
The VPN Client installs and runs only as an application. This is due to Vista services hardening and the deprecation of the GINA infrastructure.
Support exists only UDP encapsulation. This is due to changes in the Microsoft stack, which prevents ESP packets from reaching the VPN driver as it is currently implemented. Enable UDP encapsulation in the Contivity switch group profile. For Vista users, the NAT Traversal setting must have any value other than Not Allowed.
Unified Messaging Client exceptions
The Unified Messaging Client requires a new compatible fax driver from ImageMaker. CallPilot Desktop Messaging 4.0 does not support Groupwise 7.x on Vista. You can download Windows Help that is used by CallPilot help from the Microsoft Download Center. The Desktop Messaging installation can appear to be stalled for several minutes when you are completing the installation process. Vista Windows Mail purge messages fails because of Microsoft limitations. To avoid this failure and keep deleted messages in your Inbox, navigate to Tools > Options > Advanced. Deselect the Use the Deleted Items Folders with IMAP accounts check box. To show deleted messages in your Inbox, navigate to View > Current View. Select the Deleted Messages check box.
BCM50 existing features
Core Telephony
Digital Mobility
Doorphone
Ad Hoc Conferencing
New Zealand, Mexico, Poland profile updates
GASM Poland and Australia CLIDGATx (Bahrain, Ireland, Hong Kong, and Peoples Republic of China)
GATI profiles (United Kingdom, Poland, Mexico, Taiwan, Brazil, Australia, and New Zealand)
Modem answer on CLID feature
IP Telephony
WLAN IP Phones
IP Phone 2007
IP Audio Conference Phone 2033
IP Softphone 2050
IP KEM
IP Phone 1120E
IP Phone 1140E
SIP trunk features
H323 Interop (SN08, SN09, SE09)
SIP/H323 Interop (CS1K 4.5/5, MCS5100 3.5 and 4.0)
IP Phone 1110
IP Set Firmware
SIP/H323 Interop (BCM 4.0 and BCM 3.7)
Management
PVQM
Citrix of Element Manager
Remote and Scheduled Upgrade
NCM Support
ISDN Dial-up
Data and Security
Security
WAN Failover
EU routers with Contivity v2.5 and VPN Client Termination
Applications
Intelligent Contact Center
Reporting for Contact Center
IP MOH
MCDN TAT
MMCC
Hospitality
Platform
BRI Versions
BCM50b
BCM50ba
BCM50be
BCM50 Upgrade CD
SRG50 Support
8x16 MBM
ADID MBM (North America only)
BRI version
BCM50 integrates two-port BRI S/T trunks for EMEA and Asia Pacific (APAC) markets for customers who need digital trunking. The analog trunk versions are still available separately for customers who require them.
R2MFC MBM support
BCM50 supports the R2MFC MBM in selected Caribbean and Latin America (CALA) and APAC countries.
EU-compliant routers M222 and M252 firmware
BCM50 routers deliver Removal of Hazardous Substances (RoHS) compliancy for network infrastructure, or 5/6 compliancy. This requires new hardware for both the Ethernet router and the ADSL router. The new hardware is based on a common architecture for both routers and is also common to Contivity EU releases.
These new features apply to the M222/252 routers only. A software upgrade is available for installed M221/251. The following features align to Contivity 2.5 with the addition of VPN client termination support.
VPN Client Termination (new)
Port Restricted Cone NAT
SIP firewall ALG
Nailed Up tunnels
SSH, SSL and Secure FTP
New hardware support for ADSL2+
Client emulation enhancements
Client management privileges
Failover IP assignment for automatic assignment of fail over site IP address
X.509 digital certificates
New DSL version support for ADSL2+
Note: M221/251 refers to the routers shipped with BCM50 1.0 units, and M222/252 refers to the new EU-compliant routers shipped with EU BCM50 2.0 and BCM50 3.0 units.
WAN failover
The router hardware simplifies WAN failover as well as future management integration through the internal serial connector. The router provides support for WAN failover on all BCM50 platforms with M222/252 routers. WAN failover allows calls that experience issues using the WAN link to continue over the soft modem or LAN or ISDN.
Integrated Services Digital Network Basic Rate Interface dial-up support
The BCM50 requires a data layer over the channelized Integrated Services Digital Network (ISDN) for remote management dial-up over Basic Rate Interface (BRI). Support is available for remote management over BRI over the integrated BRI CDC or BRI MBM configured for ISDN support. Support is available for all on-demand and scheduled management tasks, are such as CDR collection, backup and restore, software updates, and log collection.
Network Configuration Manager support for BCM50
Network Configuration Manager (NCM) support for BCM50 is delivered as a new release. The product is branded NCM 4.0 and is delivered to new customers on a new CD.
Global Analog Trunk Interface localization
Global Analog Trunk Interface (GATI) supports EMEA, China, and APAC countries where the MBM is currently sold. See the country matrix in Global markets on page 37. Some profiles require new Disconnect Supervision (DS) or Caller ID (CLID) support.
Analog Direct Inward Dial Media Bay Module
BCM50 adds Analog Direct Inward Dial (ADID) Media Bay Modules (MBM) (ADID4 and ADID8) for North America, Taiwan, and Hong Kong markets. This MBM is backward-compatible to BCM 4.0.
8x16 Media Bay Module
BCM50 has an 8x16 Combo MBM to deliver GATM8 plus DSM16 capability in one MBM. It requires only one expansion chassis and is available in all markets where the GATM8 or DSM16 is sold. This MBM is backward-compatible to BCM4.0.
Next generation IP phones
BCM50 supports Next Generation IP phones from BCM4.0. PVQM, Desktop Assistant, and Business Element Manager button programming includes support for both existing sets and new sets.
SIP and H.323 interoperability
BCM50 and SRG50 match BCM 4.0 SIP and H.323 interoperability.
SIP interoperability includes the following products:
CS1000 4.5 and 5.0
MCS5100 3.5 and 4.0
H.323 interoperability includes the following products:
CS1000 4.5 and 5.0
CS2000 SN08 and SN09/09FF/09U
CS2100 SE08 and SE09
MSC5100 3.0 and 3.5
IPT 3.01
Hardware inventory
As part of the BCM50 management changes, the Business Element Manager hardware inventory panel and the Entity MIB allow you to remotely view detailed information about the CSC, integrated router, and integrated BRI CDC hardware. Additionally, visibility of other FRU components, such as fans, provides a complete hardware inventory view of all BCM50 hardware components to the FRU level.
Proactive Voice Quality Monitoring
With the proactive voice quality monitoring (PVQM) capability, you can set call-quality thresholds for IP sets and receive an alert and if these thresholds are exceeded. You can proactively identify voice quality of experience (QoE) issues for every call. In turn, you can troubleshooting of voice-quality issues within the network. PVQM supports calls from an IP set to any other set or trunk. The measured call-quality metrics includes the following.
packet loss
inter-arrival jitter
listening R-value
RTCP round trip delay
With PVQM, a system-wide summary view of threshold-violation alert occurrences is maintained. Threshold violations can be sent as alarms and used by the central AppManager VoIP performance-monitoring product from NetIQ to generate a system-wide view of the voice quality of the network and to help diagnose voice-quality issues. The alarms include extensive call-quality information in accordance with IETF RTCP-XR RFC 3611.
PVQM on BCM50
provides the ability to monitor the quality and integrity of IP-based voice networking
is a significant differentiator in VoIP convergence network sales with its market-leading, proactive focus on every call.
mitigates customer issues to determine whether the data network or the BCM is at fault when call-quality issues situations occur
provides consistency in the QoE solution across Avaya enterprise call servers to facilitate mixed network deployments
Ad Hoc conferencing
Currently, the BCM supports three-party conferencing. Ad-Hoc Conferencing extends this capability to support multi party conferencing.
provides a user interface model which is similar to the current F3 conference
ensures no impact on the users feature button footprint (that is, no requirement exists for additional IC keys or for an additional feature key)
provides the current three-party conferencing capabilities, allowing users the flexibility to have larger multi-party conferences
supports up to 18 simultaneous participants on multiple conferences
Meridian Customer Defined Network Trunk Anti-Tromboning with integrated applications
The BCM currently uses Meridian customer-defined network (MCDN) signaling to optimize networkresource use to transfer or forward station-to-station calls. With this feature, voice mail and autoattendant applications can use MCDN capabilities to optimize network use.
MCDN trunk anti-tromboning (TAT) on BCM50
provides customers with optimal use of trunk facilities
enables a large number of feasible networking scenarios to serve customers
With MCDN TAT, BCM can determine whether calls routed across a network by the integrated AutoAttendant or Voicemail should invoke TAT or Trunk Route Optimization (TRO) MCDN to optimize the trunking network connection.
Session Initiated Protocol
BCM supports H.323 and SIP VoIP basic call communication for BCM-to-BCM calls. H.323 also supports the same features that the MCDN capability supports.
BCM50 existing SIP features include:
support for the MCDN features with SIP
expanded SIP interoperability to the CS1K and MCS5100
The MCDN supported features include:
Private Name/Number
Network Call Redirection Info (NCRI)
Trunk Anti-Tromboning (TAT)
ISDN Call Connection Limit (ICCL)
Message Waiting Indication (MWI)
Trunk Route Optimization (TRO)
In enterprise network systems, the SIP feature supports private numbering plans, optimizes the use of network traffic (TAT/TRO/ICCL), and supports centralized voice mail applications (NCRI, MWI) using the SIP messaging protocol. By making these capabilities available using the SIP protocol, you can begin to transition your network to the latest standard.
Security
BCM50 3.0 security enhancements are an extension of the BCM50 platform.
User account access management
This feature significantly improves BCM user-account access management by enhancing password, session, account authentication, and access-management. These improvements align the BCM with the security enhancements introduced with BCM50 and add incremental capabilities.
Password Management and Policy Enhancements include:
Minimize the vulnerability of passwords
password characteristics are now more stringent (length, criteria)
password aging, history and change notification added
forced password change on initial login
password storage hashing with Secure Hashing Algorithm 1 (SHA1)
Session Management Enhancements minimizes the vulnerability of logged-on sessions for idle session time outs.
Account Management includes:
Minimize the vulnerability of User IDs
Automatic disabling of unused accounts
Set-based administration requires user ID and password
Account User ID Access Privilege Management includes the logged-on user ID session and access display. These enhancements to user-account access management provide a secure BCM access environment, which makes it difficult for a malicious user to gain access to a BCM. BCM owners can enforce secure account-access controls to the BCM to ensure secure BCM management and to increase protection against potential vulnerabilities.
Secure interface and audit logging
This feature enhances interface security by adding secure access controls, security audit logs (configchange.systemlog), and system activity by User ID, date, and time. Secure Interface Access and Communications Controls provide
support for Secure Copy (SFTP) SSH encrypted file transfers
support for Simple Network Management Protocol (SNMP) v2 and v3, including encryption provided with v3
BCM owner control of Avaya technical support access
use of digital signatures and enhanced tamper detection to ensure trusted sources for software upgrades (patches and software release upgrades)
ability to test the system ability to generate alarms and logs, including system security alarms and logs
Audit log tracks critical changes to the system and the logon attempts, including
last successful login identification and interface
last failed login attempt and total failed logons since last successful logon
configuration change log to track configuration changes to system by User ID
RADIUS Support (Centralized Authentication and Radius Client to authenticate and authorize using a centralized RADIUS server)
In addition to supporting IPsec tunnels for management, the ability to encrypt SNMP and file transfers provides BCM users an expanded capability set for secure interface communications. With audit logging of long attempts, the BCM user can track security violation attempts and determine further action. If you suspect a user ID security breach as a result of system configuration changes, the audit logging of configuration changes provides traceability to user IDs and interfaces.
An overall increase in security you have with effective logging capabilities for Audit Trail logs, Alarm logs and Configuration Change logs. If you require improved interface access and communications security for alarm, log, and file transfers, you can use these security enhancements. As well, you can audit and identify the critical system changes that specific users initiate.
Terminal and mobility support
The BCM50 Terminal and mobility support is equivalent to that of BCM 4.0. BCM50 supports the following phones:
IP Phone 1110
IP Phone 1120e
IP Phone 1140e
IP Phone 1210/1220/1230
T7406E Cordless Handset
IP Audio Conference Phone 2033
IP Key Expansion Module I24
IP 11xx Key Expansion Module
IP 12xx Key Expansion Module
IP 12xx Key Expansion Module with Display
The IP phones incorporate network management and security enhancements. You can upgrade the firmware with a patch or call sever release that provides the following:
enhanced VLAN (configured manually or with DHCP) and PC VLAN (configured manually) tagging
enhanced display for local Network Diagnostic Utilities
Global markets
BCM50 voice prompts, which were introduced in BCM 4.0, include Polish, Finnish, Korean, Turkish, and Czech.
The following additional capabilities are available:
addition of second dial tone for PRI/BRI
In some markets, a PBX must provide a local tone to the originating party (as opposed to the central office).
This feature adds the ability to provide the local tone.
increased public received digit length from 7 to 12 digits
Some markets require more than public received digits to support dial plans.
BCM50 regional bundles for APAC and EMEA are updated to include the GATI or BRI keycodes to replace expansion chassis and BRI MBM where applicable.
Support, security and servicing
BCM50 provides solutions for client support, replacement parts, upgrades, and enhanced servicing.
Client operating system support
BCM50 supports Microsoft Windows 2000 Professional, Microsoft Windows XP Professional, Windows Vista, Citrix Metaframe XP for Element Manager, and Citrix client support equivalent to BCM 4.0. BCM applications for BCM50 support the following Vista versions: Microsoft Vista Business, Microsoft Vista Ultimate and Microsoft Vista Enterprise.
Field replaceable units
Field replaceable units (FRU) strategy is consistent with previous BCM50 systems, including a replacement router and a BRI CDC card. CDCs are not hot-pluggable.
Ease of installation
BCM50 installation easy with innovative hardware and management tools. The simple rack-and-stack nature of BCM50 physical installation, with the multipurpose RJ-45-based connector strategy, provides easy installation. The dedicated RJ-45 port for
management access provides easy access to the unit for on-site PC-based element management tasks. For BCM50 installations that require data networking, IP sets, or VoIP trunking, BCM50 can function as a DHCP client to a network DHCP server for automated IP address assignment. BCM50 can also function as a DHCP server to provide both IP phones and a directly connected Element Manager PC with the IP configuration.
Startup profile
To accelerate the initial installation programming of system-level parameters, you can use the Startup Profile to quickly place the BCM50 in a basic operational state, ready to program, without having to use Element Manager or set-based administration.
The Startup Profile is an easy-to-use template you can datafill using Microsoft Excel. The Startup Profile provides a quick interface to define, for example, the following parameters:
system profile including country, telephony template, and key voice mail attributes
system IP parameters
system-level telephony attributes to automatically create the system DNs
keycode information through automated application of keycodes
users and groups
You fill out the template, save it to a USB storage device, and insert the memory stick into the USB port of the BCM50 during the initial startup of the system. This information is read into the BCM50 and applied during a single restart sequence. The Startup Profile is similar to the Quickstart wizard of the BCM200 and BCM400, but it can be data filled and applied without an IP connection to the unit, a PC, or telephone. The Startup Profile executes quickly, and includes a broad scope of system-level parameters.
Remote management accessibility
BCM50 has an integrated analog modem that can accept an incoming modem call on any BCM50 system line. You can configure the BCM50 system to have the modem automatically answer a specific line with configuration options. You can manage from BRI. Remote users can also initiate a voice call to a person or an autoattendant, who transfers the call to the modem. The analog modem also supports callback for management access to the BCM50, which can be used to support automatic dial-out on SNMP traps and automated sending of Call Detail Records (CDR) to a remote CDR collection point. The modem is also enhanced with CLID. Although Avaya does not recommend that you use the analog modem to transfer large files, the modem provides a flexible method of remote access to remotely perform all programming tasks. The BCM50e and BCM50a provides remote management capability with a high-speed connection. Tasks such as transferring backup files to a remote destination and transferring software update files, CDR records, and log files can occur more efficiently than over the analog modem.
On-box and device manageability features
BCM50 has an SNMPv3 interface that includes support for SNMP v1 and v2 for management by legacy SNMP managers. SNMPv3 delivers improved security features for SNMP device access. The BCM50 main unit supports the following versions of SNMP:
SNMP v1the first implementation of SNMP; this version supports protocols such as IP
SNMP v2Cprovides improved efficiency and error handling
SNMP v3provides improvements in security and privacy
Using the BCM50 Element Manager, you can select which versions of SNMP you want the BCM50 agent to support.
If you have any queries or would like more information about any of the solutions outlined, please contact us or request a call back. Alternately, you can call us on 905 695 2237 or 877 336 7710 for more immediate help and advice.