A Vaya Aurac M Product Description
A Vaya Aurac M Product Description
Product Description
Release 6.3
03-300468
Issue 11
June 2014
© 2014 Avaya Inc. Avaya grants you a license within the scope of the license types
described below, with the exception of Heritage Nortel Software, for
All Rights Reserved. which the scope of the license is detailed below. Where the order
documentation does not expressly identify a license type, the
Notice applicable license will be a Designated System License. The applicable
number of licenses and units of capacity for which the license is granted
While reasonable efforts have been made to ensure that the will be one (1), unless a different number of licenses or units of capacity
information in this document is complete and accurate at the time of is specified in the documentation or other materials available to you.
printing, Avaya assumes no liability for any errors. Avaya reserves the “Software” means Avaya’s computer programs in object code, provided
right to make changes and corrections to the information in this by Avaya or an Avaya Channel Partner, whether as stand-alone
document without the obligation to notify any person or organization of products, pre-installed , or remotely accessed on hardware products,
such changes. and any upgrades, updates, bug fixes, or modified versions thereto.
“Designated Processor” means a single stand-alone computing device.
Documentation disclaimer
“Server” means a Designated Processor that hosts a software
“Documentation” means information published by Avaya in varying application to be accessed by multiple users. “Instance” means a single
mediums which may include product information, operating instructions copy of the Software executing at a particular time: (i) on one physical
and performance specifications that Avaya may generally make machine; or (ii) on one deployed software virtual machine (“VM”) or
available to users of its products and Hosted Services. Documentation similar deployment.
does not include marketing materials. Avaya shall not be responsible
for any modifications, additions, or deletions to the original published License types
version of documentation unless such modifications, additions, or
deletions were performed by Avaya. End User agrees to indemnify and • Designated System(s) License (DS). End User may install and
hold harmless Avaya, Avaya's agents, servants and employees against use each copy or an Instance of the Software only on a number
all claims, lawsuits, demands and judgments arising out of, or in of Designated Processors up to the number indicated in the
connection with, subsequent modifications, additions or deletions to order. Avaya may require the Designated Processor(s) to be
this documentation, to the extent made by End User. identified in the order by type, serial number, feature key,
Instance, location or other specific designation, or to be provided
Link disclaimer by End User to Avaya through electronic means established by
Avaya specifically for this purpose.
Avaya is not responsible for the contents or reliability of any linked
websites referenced within this site or documentation provided by • Concurrent User License (CU). End User may install and use
Avaya. Avaya is not responsible for the accuracy of any information, the Software on multiple Designated Processors or one or more
statement or content provided on these sites and does not necessarily Servers, so long as only the licensed number of Units are
endorse the products, services, or information described or offered accessing and using the Software at any given time. A “Unit”
within them. Avaya does not guarantee that these links will work all the means the unit on which Avaya, at its sole discretion, bases the
time and has no control over the availability of the linked pages. pricing of its licenses and can be, without limitation, an agent,
port or user, an e-mail or voice mail account in the name of a
Warranty person or corporate function (e.g., webmaster or helpdesk), or
Avaya provides a limited warranty on Avaya hardware and software. a directory entry in the administrative database utilized by the
Refer to your sales agreement to establish the terms of the limited Software that permits one user to interface with the Software.
warranty. In addition, Avaya’s standard warranty language, as well as Units may be linked to a specific, identified Server or an Instance
information regarding support for this product while under warranty is of the Software.
available to Avaya customers and other parties through the Avaya • Database License (DL). End User may install and use each copy
Support website: http://support.avaya.com or such successor site as or an Instance of the Software on one Server or on multiple
designated by Avaya. Please note that if you acquired the product(s) Servers provided that each of the Servers on which the Software
from an authorized Avaya Channel Partner outside of the United States is installed communicates with no more than an Instance of the
and Canada, the warranty is provided to you by said Avaya Channel same database.
Partner and not by Avaya.
• CPU License (CP). End User may install and use each copy or
Licenses Instance of the Software on a number of Servers up to the
number indicated in the order provided that the performance
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA capacity of the Server(s) does not exceed the performance
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR capacity specified for the Software. End User may not re-install
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE or operate the Software on Server(s) with a larger performance
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR capacity without Avaya’s prior consent and payment of an
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., upgrade fee.
ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS
APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA • Named User License (NU). You may: (i) install and use the
OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE Software on a single Designated Processor or Server per
AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND authorized Named User (defined below); or (ii) install and use
THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM the Software on a Server so long as only authorized Named
ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN Users access and use the Software. “Named User”, means a
AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO user or device that has been expressly authorized by Avaya to
TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING access and use the Software. At Avaya’s sole discretion, a
OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY “Named User” may be, without limitation, designated by name,
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR corporate function (e.g., webmaster or helpdesk), an e-mail or
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF voice mail account in the name of a person or corporate function,
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, or a directory entry in the administrative database utilized by the
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER Software that permits one user to interface with the Software.
REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A • Shrinkwrap License (SR). You may install and use the Software
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE in accordance with the terms and conditions of the applicable
APPLICABLE AVAYA AFFILIATE (“AVAYA”). license agreements, such as “shrinkwrap” or “clickthrough”
license accompanying or applicable to the Software
(“Shrinkwrap License”).
Virtualization
Each product has its own ordering code and license types. Note that
each Instance of a product must be separately licensed and ordered.
For example, if the end user customer or Avaya Channel Partner would
like to install two Instances of the same type of products, then two
products of that type must be ordered.
Chapter 1: Introduction...................................................................................................... 7
Purpose..................................................................................................................................................... 7
Intended audience.................................................................................................................................... 7
Document changes since last issue.......................................................................................................... 7
Related resources..................................................................................................................................... 8
Documentation................................................................................................................................. 8
Training............................................................................................................................................ 10
Avaya Mentor videos........................................................................................................................ 12
Support...................................................................................................................................................... 12
Warranty.................................................................................................................................................... 12
Chapter 2: Communication Manager overview................................................................ 13
System running Communication Manager................................................................................................ 13
Communication Manager software bundles.............................................................................................. 14
Chapter 3: Communication Manager deployment scenarios......................................... 15
Communication Manager deployment...................................................................................................... 15
System Platform........................................................................................................................................ 15
Evolution server........................................................................................................................................ 16
Feature server........................................................................................................................................... 16
Communication Manager templates overview.......................................................................................... 17
Communication Manager device support................................................................................................. 19
Port network and gateway connectivity..................................................................................................... 20
Trunk connectivity..................................................................................................................................... 20
Communication Manager public networking and connectivity.................................................................. 23
Communication Manager intelligent networking....................................................................................... 24
Communication Manager data interfaces................................................................................................. 26
Chapter 4: Communication Manager functionality.......................................................... 29
Call Center................................................................................................................................................ 29
Avaya Call Center on branch gateways........................................................................................... 29
Computer Telephony Integration.............................................................................................................. 30
Communication Manager Automatic Call Distribution............................................................................... 30
Avaya Basic Call Management System.................................................................................................... 31
Avaya Business Advocate................................................................................................................ 31
Communication Manager mobility............................................................................................................. 32
Collaboration............................................................................................................................................. 34
Communication Manager call routing....................................................................................................... 37
Telecommuting and Remote Office........................................................................................................... 38
Communication Manager telephony......................................................................................................... 39
Call log support......................................................................................................................................... 39
Call notification.......................................................................................................................................... 40
Codec support........................................................................................................................................... 40
Chapter 5: Communication Manager features................................................................. 41
Administration features............................................................................................................................. 41
Communication Manager attendant features............................................................................................ 41
Communication Manager customization features..................................................................................... 45
Purpose
This document describes tested product characteristics and capabilities, including product
overview and feature descriptions, and security and licensing requirements.
Intended audience
This document is intended for anyone who wants to gain a high-level understanding of the
product features and functions.
Related resources
Documentation
The following table lists the documents related to this product. Download the documents from
the Avaya Support website at http://support.avaya.com.
Avaya Aura® Solution Design Describes the Avaya Aura® solution, Sales Engineers,
Considerations and Guidelines IP and SIP telephony product Solution
deployment, and network Architects
requirements for integrating IP and
SIP telephony products with an IP
network.
Avaya Aura® Communication Describes the system capacities for Sales Engineers,
Manager System Capacities Avaya Aura® Communication Solution
Table Manager. Architects
Implementation
Avaya Aura® Communication Describes the reports for Avaya Sales Engineers,
Manager Reports Aura® Communication Manager. Solution
Architects,
Implementation
Engineers,
Avaya Aura® Communication Describes the denial events listed on Sales Engineers,
Manager Denial Events the Events Report form. Solution
Architects,
Implementation
Engineers,
Support
Personnel
Avaya Aura® Toll Fraud and Describes the security risks and Sales Engineers,
Security Handbook measures that can help prevent Solution
external telecommunications fraud Architects,
involving Avaya products. Implementation
Engineers,
Support
Personnel
Administration
Avaya Aura® Communication Describes the features that you can Sales Engineers,
Manager Feature Description administer using Communication Solution
and Implementation Manager. Architects,
Support
Personnel
Avaya Aura® Communication Describes the screens that you can Sales Engineers,
Manager Screen Reference administer using Communication Solution
Manager. Architects,
Support
Personnel
Avaya Aura® Call Center Elite Describes tested product Sales Engineers,
Overview and Specification characteristics and capabilities, Solution
including product overview and Architects,
feature descriptions, interoperability, Support
performance specifications, security, Personnel
and licensing requirements.
What’s New in Avaya Aura® Describes the new features for the Sales Engineers,
Release 6.2 Feature Pack 4 current release of Avaya Aura®. Solution
Architects,
Support
Personnel
Avaya Aura® Communication Describes the special features that Sales Engineers,
Manager Special Application are requested by specific customers Solution
Features for their specific requirement. Architects, Avaya
Business
Partners, Support
Personnel
Training
The following courses are available on https://www.avaya-learning.com. To search for the
course, in the Search field, enter the course code and click Go.
Note:
Videos are not available for all products.
Support
Visit the Avaya Support website at http://support.avaya.com for the most up-to-date
documentation, product notices, and knowledge articles. You can also search for release
notes, downloads, and resolutions to issues. Use the online service request system to create
a service request. Chat with live agents to get answers to questions, or request an agent to
connect you to a support team if an issue requires additional expertise.
Warranty
Avaya provides a 90-day limited warranty on Communication Manager. To understand the
terms of the limited warranty, see the sales agreement or other applicable documentation. In
addition, the standard warranty of Avaya and the details regarding support for Communication
Manager in the warranty period is available on the Avaya Support website at https://
support.avaya.com under Help & Policies> Policies & Legal > Maintenance and Warranty
Information. See also Help & Policies > Policies & Legal > License Terms.
Communication Manager organizes and routes voice, data, image, and video transmissions.
Communication Manager is an extensible, scalable, highly reliable, and secure telephony application that
connect to private and public telephone networks, Ethernet LANs, and the Internet.
Communication Manager is the key component of Avaya Aura®. Communication Manager delivers rich
voice and video capabilities and provides a resilient, distributed network for gateways and analog, digital,
and IP-based communication devices. In addition, Communication Manager delivers robust PBX features,
high reliability and scalability, and multi-protocol support. Communication Manager includes advanced
mobility features, built-in conference calling and contact center applications, and E911 capabilities.
Communication Manager aims to solve business challenges by powering voice communications and
integrating with value-added applications. Communication Manager is an open, scalable, highly reliable
and secure telephony application. Communication Manager provides user and system management
functionality, intelligent call routing, application integration and extensibility, and enterprise
communications networking.
Communication Manager provides the virtual enterprise with:
• Robust voice and video call processing capabilities
• Advanced workforce productivity and mobility features
• Built-in conferencing and contact center applications
• Centralized voice mail and attendant operations across multiple locations
• Connectivity to a wide range of analog, digital, and IP-based communication devices
• Support for SIP, H.323, and many industry-standard communications protocols over a variety of
different networks
• More than 700 powerful features
• High availability, reliability, and survivability
1 Voice
2 Data
3 Image
4 Video
System Platform
System Platform technology delivers simplified deployment of Unified Communications and
Contact Center applications. This framework leverages virtualization technology, predefined
templates, common installation, licensing, and support infrastructure.
Evolution server
An evolution server is similar to the traditional Communication Manager server. The evolution
server provides Communication Manager features to both SIP and non-SIP endpoints. The
evolution server uses the full-call model. The evolution server connects to Session Manager
through a non-IMS Signaling group. Session Manager handles call routing for SIP endpoints
and enables SIP endpoints to communicate with all other endpoints that are connected to the
evolution server.
If you configure Communication Manager as an evolution server:
• H.323, digital, and analog endpoints register with Communication Manager.
• SIP endpoints register with Session Manager.
• All endpoints receive service from Communication Manager.
The evolution server supports a limited form of application sequencing.
Feature server
A feature server provides Communication Manager features to the SIP endpoints registered
with Session Manager. The feature server uses the half-call model of IP Multimedia Subsystem
(IMS). The feature server connects to Session Manager through an IMS-enabled SIP signaling
group and an associated SIP trunk group.
Note:
The Communication Manager installation and administration Web pages refer to Survivable
Core as Enterprise Survivable Server (ESS) and Survivable Remote as Local Survivable
Processor (LSP) respectively.
The Communication Manager templates are available in two categories: Communication
Manager for Main/Survivable Core and Communication Manager for Survivable Remote.
Table 1: Applications and servers supported with Communication Manager Main and
Survivable Core templates
• Dell™ PowerEdge™
R610
• Dell™ PowerEdge™
R620
• S8800
Note:
You can install
Simplex Survivable
Remote on an HP
ProLiant DL360p G8
or Dell™ PowerEdge™
R620 Server. You can
install Simplex
Survivable Remote on
an S8510 Server with
8-Gb memory as an
upgrade only.
• Polycom® VVX
• Polycom® DMA
Note:
Polycom® DMA replaces Polycom® CMA only for the gatekeeper functionality. The
management application is provided by the Polycom® CMA gatekeeper
For a full list of supported devices, see Avaya Aura® Communication Manager Hardware
Description and Reference, 555-245-207.
Trunk connectivity
Communication Manager supports the following trunk connectivity features:
• Circuit switched DS1 trunk service — DS1 can be used for voice or voice-grade data, for
data-transmission protocols, and for T1 and E1 services. For a full list of supported
devices, see Avaya Aura® Communication Manager Screen Reference.
• Separate licensing for TDM stations and TDM trunks.
• Internet Protocol.
- H.323 trunk. A TN802B in MedPro mode or a TN2302AP IP interface enables H.323
trunk service using IP connectivity between two systems running Communication
Manager. The H.323 trunk groups can be configured as system-specific tie trunks,
generic tie trunks, or direct-inward-dial (DID) public trunks. In addition, the H.323
trunks support ISDN features such as QSIG and BSR.
- IP loss groups. A primary reason to accomplish a loss plan for voice communication
systems is the desire to have the received speech and tone loudness at a
comfortable listening level. This should be accomplished so that users can listen to
each other without being concerned who or where the remote party is, or what kind
of telephone equipment each may be using.
- IP trunks. IP trunk groups may be defined as virtual private network tie lines between
systems or ITS-E servers running Communication Manager. The benefits of IP trunk
include a reduction in long distance voice and fax expenses, facilitating global
communications, providing a full function network with data and voice convergence
and optimizing networks by using the available network resources.
- IP trunk fallback to PSTN. The PSTN fallback of IP trunks feature refers to bypassing,
or skipping over, IP trunks when IP network conditions make the voice quality of IP
trunks unacceptable.
- IP trunk link bounce. H.323 trunk link bounce provides customers with fewer call
failures in the event of an IP network failure or disruption. This feature lessens the
impact of IP network failures and disruptions by postponing corrective action after
an H.323 signaling link failure.
- Session Initiation Protocol (SIP) is a signalling protocol used for establishing
sessions in an IP network. For more information on SIP, see the documents from
the Avaya Support website at http://support.avaya.com.
- SIP trunking functionality:
• Provides access to less expensive local and long distance telephone services,
plus other hosted services from SIP service providers
• Provides presence and availability information to members of the enterprise
and authorized consumers outside the enterprise, including other enterprises
and service providers
• Facilitates SIP-enabled converged communications applications within the
enterprise, such as the Seamless Service Experience.
• Auxiliary trunks connect devices in auxiliary cabinets with Communication Manager.
Some of the features that are supported with this type of trunk are recorded
announcements, telephone dictation service, malicious call trace, and loudspeaker
paging.
• Central Office (CO) trunks connect Communication Manager to the local central office for
incoming and outgoing calls.
• The digital multiplexed interface feature supports two signaling techniques: bit-oriented
signaling and message-oriented signaling for direct connection to host computers.
• Direct Inward Dialing. Direct Inward Dialing (DID) trunks connect Communication
Manager to the local central office for incoming calls dialed directly to stations without
attendant assistance.
• Direct Inward/Outward Dialing. Traditionally, Central Office (CO) trunks and Direct Inward
Dialing (DID) trunks interface an attendant console with a central office. A CO trunk
services outgoing calls and accepts incoming calls that are terminated at the attendant.
A Direct Inward/Outward Dialing (DIOD) trunk is used for calls that need to be terminated
without an attendant interaction.
• E&M signaling - E&M trunks are used to provide analog communications links.
Continuous and pulsed Continuous and pulsed E&M signaling is a modification to the
E&M signaling used in the United States. Continuous E&M signaling is intended for use
in Brazil, but can also be used in Hungary. Pulsed E&M signaling is intended for use in
Brazil.
• E911 CAMA trunk group. This provides Caller Emergency Service Identification (CESID)
information to the local enhanced 911 system through the local central office.
• Foreign Exchange. Foreign Exchange (FX) trunks connect Communication Manager to
a Central Office other than to the local office.
• ISDN trunks. These give you access to a variety of public and private network services
and facilities. The ISDN standard consists of layers 1, 2, and 3 of the Open System
Interconnect (OSI) model. Systems running Communication Manager can be connected
to an ISDN using standard frame formats: Basic Rate Interface (BRI) and the Primary
Rate Interface (PRI).
• Personal Central Office Line provides a dedicated trunk circuit between multi-appearance
telephones and a CO or other switch via the network.
• Release Link Trunks (RLT) are used between switch locations to provide centralized
attendant service or automatic call distribution group availability.
• Remote Access provides users with access to the system and system features from the
public network. With Remote Access, users can make business calls from home or use
Recorded Telephone Dictation Access to dictate a letter. An authorized user can also
access system features from any onsite extension.
• Tie trunks carry communications between Communication Manager and other switches
in a private network. Several types of trunks can be used, depending on the type of private
network you establish.
• Timed automatic disconnect for outgoing trunk calls provides the capability to
automatically disconnect an outgoing trunk call after an administrable amount of time.
The amount of time that can elapse before the trunk is dropped can be specified, and can
vary between 2 and 999 minutes.
• Wide Area Telecommunications Service (WATS) trunks allow you to place long-distance
outgoing voice-grade calls to telephones in defined service areas. The calls are priced
according to distance in the service area, length of the call, time of day, and the day of
the week.
• Administrable Test Type 100 Timer. To test voice quality on a trunk set up at Central
Office, you can administer the time length for which the test call must be active. Test Type
100 tests far-end to near-end loss and C-message. After the Test Type 100 line answers
a call, Communication Manager sends a 1004 Hz tone at 0 dBm for 5.5 seconds, and
then transitions to the silent mode until the call is disconnected.
T.30 signaling between a fax machine and a far-end fax receiver, and the far-end
fax receiver does not support T.38, then the call falls back to G.711. You can
administer the feature on the Ip-codec-set form. This feature is only supported on
G430 and G450 Media Gateways and only over Verizon SIP trunks. Communication
Manager supports the transition of an existing audio call to a fax call. receives a
request for establishing a fax call during an audio call. If T.38 is administered,
Communication Manager accepts the fax call and disconnects the audio call. Else,
Communication Manager rejects the fax call. Communication Manager does not
support a fax call and an audio call simultaneously
- V.150.1 Modem-over-IP: Modem devices use the V.150.1 protocol to transmit V-
series modem signals between modems and telephony devices. The V.150.1
protocol is a standard recommended by International Telecommunication Union
(ITU) to use a modem over IP networks that support dialup modem calls. The V.150.1
protocol defines how to transmit modem traffic between modems and telephony
devices over an IP network. With the Modem-over-IP feature, secure terminals
establish a secured connection over SIP and H.323 trunks and the Avaya proprietary
Inter-gateway Connections (IGCs).
• QSIG support: QSIG is a global signaling and control standard for use in private corporate
ISDN networks.
- QSIG Supplementary Service - Advice of Charge. The QSIG Supplementary Service
- Advice of Charge (SS-AOC) provides the capability to extend the public network
charging information, provided by service providers in various countries, into users
in a private network.
- QSIG support for Unicode. The QSIG support for Unicode feature extends the
Unicode support on a single server to multi-node Communication Manager
networks. This feature allows Unicode support across large campus
configurations.
• Uniform Dial Plan: A unique three to 13–digit number assigned to each station on the
network. Uniform numbering gives each station a unique number (location code plus
extension) that can be used at any location in the electronic tandem network to access
that station. Communication Manager enhances the standard UDP with the unrestricted
13-digit Uniform Dial Plan, which allows up to five digits to be parsed for call routing.
UDP provides extension-to-extension dialing between two or more private-switching
systems.
• SIP and H.323 dual registration: With the SIP and H.323 dual registration feature, you
can assign the same extension to H.323 and SIP endpoints. When you use the same
extension to register a SIP endpoint to Session Manager and an H.323 endpoint to
Communication Manager, an incoming call to that extension rings at both the endpoints.
The user can answer the call either at the H.323 endpoint or at the SIP endpoint. You can
create an extension of H.323 type by using System Manager. You can reassign the same
extension as SIP by using the Stations with off-pbx telephone integration screen in
Communication Manager SAT. This feature is supported by the following audio and video
endpoints:
• Data Privacy protects analog data calls from being disturbed by any overriding or ringing
features of the system. Data Privacy is activated when you dial an activation code at the
beginning of the call.
• Data restriction protects analog data calls from being disturbed by any overriding or
ringing features of the system. It is administered at the system level to selected analog
and multi-appearance telephones and trunk groups.
• Default dialing. This feature provides data terminal users who dial a specific number the
majority of the time a very simple method of dialing that number. This feature enhances
Data Terminal (Keyboard) Dialing by allowing a data terminal user to place a data call to
a pre-administered destination in several different ways, depending on the type of data
module.
• IP asynchronous links enable Communication Manager to transfer existing asynchronous
adjunct connectivity to an Ethernet (TCP/IP) environment. IP asynchronous links support
switch server applications, as well as client applications.
• The Multimedia Application Server Interface provides a link between Communication
Manager and one or more Multimedia Communications eXchange nodes. A Multimedia
Communications eXchange is a stand-alone multimedia call processor produced by
Avaya.
• Multimedia calling. Multimedia calls are initiated with voice and video only. Once a call is
established, one of the parties may initiate an associated data conference to include all
of the parties on the call who are capable of supporting data.
• Pass advice of charge information to world-class BRI endpoints provides Advice of
Charge (AOC) information to World Class BRI (WCBRI) endpoints. On a call using a
WCBRI endpoint, AOC information will be displayed on the endpoint after the call has
completed and the far end has hung up.
Call Center
The Avaya Aura® Call Center provides a fully integrated telecommunications platform that
supports a powerful assortment of features, capabilities, and applications designed to meet all
of your customers' Call Center needs.
Call Center applications, such as Avaya Call Management System for real-time reporting and
performance statistics, and Avaya Business Advocate for expert predictive routing based on
incoming calls rather than historical data, are easily integrated.
Communication Manager supports the Agent ID feature using which telephones can retrieve
specific agent greetings and play the greetings when calls are received.
Communication Manager also supports the Restrict Call Joining feature on Avaya Aura®
Contact Center. If enabled, Communication Manager restricts the agents from initiating a
transfer or a conference operation. The restriction is applicable only to outbound calls. With
the Restrict Second Agent Consult feature, agents can use only one consult operation, transfer
or conference, at a time.
For a complete description of Call Center features for Communication Manager, see the
following documents:
• Avaya Aura® Call Center Overview
• Planning an Avaya Aura® Call Center Implementation
• Administering Avaya Aura® Call Center Features
• Avaya Aura® Call Center Feature Reference
• Programming Call Vectoring Features in Avaya Aura® Call Center
R610, or HP ProLiant DL360 G7 Server, and the G650 port network gateway with the S8800,
Dell™ PowerEdge™ R610, or HP ProLiant DL360 G7 Server.
Avaya Call Center “Basic” software is included with Communication Manager capability along
with optional Computer Telephony Integration (CTI). This package provides a low-cost call
center solution for small or branch offices.
More robust call center capabilities are provided with the optional Avaya Call Center “Elite”,
which features Avaya Expert Agent Selection and services as the foundational software for
the optional Avaya Business Advocate and Avaya Dynamic Advocate software.
The call center capabilities found in the Elite Call Center software package allows
Communication Manager Call Center customers to enhance their customer service, help desk,
travel, and other operations by providing powerful, integrated call routing through “call
vectoring” and resources selection.
Note:
Avaya Wireless Telephone Solutions (AWTS) replaces the DEFINITY Wireless
Business System (DWBS).
• The Avaya Extension to Cellular (EC500) feature provides the expansion of mobile
services, including one-number availability, increased user capacities, flexibility across
facilities and hardware, more control over unauthorized usage, enhanced enable/disable
capability, increased serviceability, and support of IP trunk facilities. To define call
treatment options for EC500 calls, you can use up to 99 configuration sets that are defined
in the system. If you set the Cellular voice mail detection field, an EC500 call does not
cover to the cellular voice mail. When the call server detects that the call is covered to
the cellular voice mail, the call server returns the call to the server.
Note:
In the One-X mobile environment, you can edit the values of only the Cellular voice
mail detection field and the Call log notify field. All other fields are read-only.
Communication Manager 6.3.2 introduces additional security for the EC500/One-X
Mobile Lite call (AEFSC) feature. With this feature, when a user makes an FNE call from
a cellular phone, the system authenticates the call with the station security code (SSC).
The call fails without the valid SSC. When a caller wants to make an EC500 call, the caller
must dial the SSC after the FNE number. For example, <FNE> [Dial tone] <SSC> # [Dial
tone or confirmation tone] <Subsequent digit or extension>.
The integration of Microsoft Office Communicator (MOC) with Communication Manager
through ASAI supports bridging, that is, having two user functions simultaneously. For
example, the user can be on an active call on a desk phone and, at the same time, be on
an active call on an off-PBX destination, such as a mobile phone.
• E911 ELIN for IP wired extensions automates the process of assigning an emergency
location information number (ELIN) through an IP subnetwork (“subnet”) during a 911 call.
The ELIN is then sent over either CAMA or ISDN PRI trunks to the emergency services
network when 911 is dialed.
• The Personal Station Access (PSA) feature allows you to transfer your telephone station
preferences and permissions to any other compatible telephone. PSA has several
telecommuting applications. For example, several telecommuting employees can share
the same office on different days of the week. The employees can easily and remotely
make the shared telephone “theirs” for the day.
• The SIP Visiting User (SIP VU) feature enables users with the 9620 or 9630 SIP telephone
to log in to any SIP telephone in the enterprise and receive their own individualized
services, including menus, contacts, and buddy lists.
The SIP Visiting User feature relies on specialized firmware on the telephone, and also
requires SIP VU administration.
• Use the Terminal Translation Initialization (TTI) feature to merge an X-ported extension
to a valid port, or to separate an extension from a port. You usually use TTI to move
telephones. However, you can also use TTI to connect and move attendants and data
modules. Terminal Translation Initialization (TTI) also works with Administration Without
Hardware (AWOH).
• The TransTalk 9000 is a single-zone or dual-zone, in-building wireless system that
provides a mobility solution on Communication Manager-based systems. It delivers the
benefits and accessibility of a wireless telephone with all the power and functionality of a
wired desk telephone.
• X-station mobility allows remote users to access switch features. That is, X-station
mobility allows certain OEM wireless telephones remoted over a PRI trunk interface to
be controlled by Communication Manager as if the telephones were directly connected
to the switch.
• With the Multiple Device Access (MDA) feature, a SIP user can register more than one
SIP device with a single extension. For example, a user has ADVD at his desk, 96X1 in
his lab, and one-X® Communicator on his laptop and all the devices are registered with
the same extension 123456. When a call arrives at extension 123456, all the devices are
alerted. The user can answer the call from any one of the devices. If required, the user
can bridge on to the call from one of the idle devices by using the Simulated Bridge
Appearance (SBA) feature. Therefore, the call can be handed off between devices without
parking the call.
Collaboration
Communication Manager contains a variety of features aimed at providing easy ways to
collaborate with groups of peers, customers, and partners such as executives, sales people,
and professional specialists. These key work groups require a high level of effective interaction,
and Communication Manager delivers.
Conferencing:
• Abort conference. When you press the conference button and for any reason you hang
up before you complete the conference, you will cancel the conference. The original call
that was put on soft-hold is put on hard-hold
• Conference - three party. The conference button allows single-line telephone users to
make up to three-party conference calls without attendant assistance.
• Conference - six party. The conference button allows multi-appearance telephone users
to make up to six-party conference calls without attendant assistance.
• Conference/transfer display prompts are based on the display prompts are based on the
user class of restriction (COR), independent of the select line appearance conferencing
and no-dial-tone conferencing feature.
• The conference/transfer toggle/swap feature allows users to toggle between two parties
in the middle of setting up a conference call prior to connecting all parties together, or to
consult with both parties prior to transferring a call.
• The group listen feature simultaneously activates your speakerphone in listen-only mode,
and your handset or headset in listen-and-speak mode. This allows you to serve as
spokesperson for a group. You can participate in a conversation while everyone else in
the room is listening to what is said.
Note:
This feature is not supported on IP telephones.
• Hold/unhold conference allows a user to use the Hold button to bring the held party back
to the conversation.
Note:
This feature is not available for BRI stations or attendant consoles.
• The Meet-me Conferencing feature allows a person to set up a dial-in conference of up
to six parties. The Meet-me Conferencing feature uses call vectoring to process the setup
of the conference call.
enable you to conduct video conferences, and forward, cover, hold, or park multimedia
calls much as you would a standard voice call.
• Multimedia call redirection to multimedia endpoint. A dual port multimedia station may be
a destination of call redirection features such as call coverage, forwarding, and station
hunting. The station can receive and accept full multimedia calls or data calls converted
to multimedia.
• Multimedia data conferencing (T.120) through an ESM. The data conference is controlled
by an adjunct device called an Expansion Services Module (ESM). For more information
on ESM, see Installation for Adjuncts and Peripherals for Avaya Aura™ Communication
Manager.
• Multimedia hold, conference, transfer, and drop. Station users can activate hold,
conference, transfer, or drop on multimedia calls. Multimedia endpoints and voice-only
stations may participate in the same conference.
• Multimedia queuing with voice announcement. When multimedia callers queue for an
available member of a hunt group, they are able to hear an audio announcement.
Paging and intercom:
• Code calling access allows attendants, users, and tie trunk users to page with coded
chime signals.
• Group paging allows a user to make an announcement to a group of people using
speakerphones. The speakerphones are automatically turned on when the user begins
the announcement.
• Intercom - automatic. With this feature, users who frequently call each other can do so
by pressing one button instead of dialing an extension number.
• Intercom - dial. This feature allows multi-appearance telephone users to easily call others
within an administered group. The calling user lifts the handset, presses the dial intercom
button, and dials the one-digit or two-digit code assigned to the desired party.
• Loudspeaker paging access provides attendants and telephone users dial access to voice
paging equipment. As many as nine paging zones can be provided by the system, and
one zone can be provided that activates all zones at the same time.
• Manual signaling allows one user to signal another user. The receiving user hears a two-
second ring. The signal is sent each time the button is pressed by the signaling user. The
meaning of the signal is prearranged between the sender and the receiver. Manual
signaling is denied if the receiving telephone is already ringing from an incoming call.
• Whisper page allows an assistant or colleague to bridge onto your telephone conversation
and give you a message without being heard by the other party or parties you are talking
to. Whisper page works only on certain types of telephones.
Team button:
The Team button feature is used to monitor members of a team of stations. Monitoring station
is notified about the general redirection state of the monitored station. Starting Release 6.3.6
of Communication Manager, direct transfer, transfer upon hang-up, and override SAC/CFWD/
EC features can be used with the Team button feature.
Session Manager uses the IP address to select the matching trunk or route pattern and
then routes the call to destination stations.
• With the Multiple Call Handling feature, the rerouted or the forwarded-switched calls use
the call coverage path of the diverted-to party. Based on the Communication Manager
configuration, the greeting of the administered party is played to the caller.
• Delayed drop: With Communication Manager Release 6.3.6, you can use the
Interworking of ISDN Clearing with In-Band Tones field on the SIP Trunk form to
communicate the reason of the call drop to the caller. After knowing that the called party
will not answer the call, the caller or the Voice Portal agent can decide whether to wait
for the announcement to complete or drop the call.
• Inter-Gateway Alternate Routing: IGAR provides enhanced Quality of Service (QoS) to
large distributed single-server configurations. You can use IGAR for configurations where
the IP network is not reliable enough to carry bearer traffic. If you have more than one IP
network available, you can use H.323 or SIP trunks for IGAR instead of the PSTN.
Communication Manager Release 6.3.5 and earlier supported IGAR for analog, DCP,
and H.323 endpoints. From Release 6.3.6 onwards, IGAR support is extended to SIP
endpoints.
Call notification
SIP undelivered call notification:
The SIP undelivered call notification feature provides a notification about the undelivered call
to the endpoint. Communication Manager initiates the SIP undelivered call notification feature
when a SIP endpoint receives a call in one of the following situations:
• All call appearances are busy.
• LNCC is activated and the endpoint is busy.
• Call Forward Busy or Call Forward All is enabled.
• Enhanced Call Forward (ECF) unconditional or ECF busy is enabled.
• Cover All Calls is enabled.
Codec support
Communication Manager supports G.722 wideband audio codec between H.323 endpoints
and SIP video and audio endpoints.
Administration features
Communication Manager support several administration interfaces for ease of use. See
Administering Avaya Aura® Communication Manager for more information.
• System Access Terminal (SAT) uses a Command Line Interface (CLI) interface for
telephony administration. SAT is available through the Avaya Site Administration
package. The system-level limit on the number of concurrent SAT sessions is 22. This
limit is only for login profiles 18 to 69 and not for system logins. A user can have up to 5
concurrent SAT sessions.
• System Management interface.
• System Manager.
• System Platform Management Console. The System Platform Web interface is called
System Platform Management Console. After installing System Platform, you can log on
to the System Platform Management Console to view details of System Platform virtual
machines (namely, System Domain (Dom-0) and Console Domain), install the required
solution template, and perform various administrative activities by accessing options from
the navigation pane.
Communication Managerlabels each point-to-point session with a globally unique identifier by
generating a 128-bit identifier and inserting the identifier in the Global Session ID (GSID)
header of the request. To troubleshoot call flows, you can use a tracing tool and filter GSIDs
from the relevant logged messages.
• Attendant backup. The attendant backup feature allows you to access most attendant
console features from one or more specially-administered backup telephones. This allows
you to answer calls more promptly, thus providing better service to your guests and
prospective clients.
• Attendant room status. Communication Manager allows an attendant to see whether a
room is vacant or occupied, and what the housekeeping status of each room is.
Note:
This feature is available only when you have enhanced hospitality enabled for your
system.
• Attendant functions using Distributed Communications System protocol.
- Control of trunk group access allows an attendant at any node in the Distributed
Communications System (DCS) to take control of any outgoing trunk group at an
adjacent node.
- Direct trunk group selection allows the attendant direct access to an idle outgoing
trunk in a local or remote trunk group by pressing the button assigned to that trunk
group.
- Inter-PBX attendant calls allows attendants for multiple branches to be concentrated
at a main location.
• Call handling.
- Attendant Intrusion. Use the Attendant Intrusion feature to allow an attendant to
intrude on an existing call. The Attendant Intrusion feature is also called Call Offer.
- Attendant lockout - privacy. This feature prevents an attendant from re-entering a
multiple-party connection held on the console unless recalled by a telephone user.
- Attendant split swap. The attendant split swap feature allows the attendant to
alternate between active and split calls. This operation may be useful if the attendant
needs to transfer a call but first must talk independently with each party before
completing the transfer.
- Attendant vectoring. Attendant vectoring provides a highly flexible approach for
managing incoming calls to an attendant. For example, with current night service
operation, calls redirected from the attendant console to a night station can ring only
at that station and will not follow any coverage path.
- Automated attendant. Automated attendant allows the calling party to enter the
number of any extension on the system. The call is then routed to the extension.
This allows you to reduce cost by reducing the need for live attendants.
- Backup alerting. The backup alerting feature notifies backup attendants that the
primary attendant cannot pick up a call.
- Call waiting. Call waiting allows an attendant to let a single-line telephone user who
is on the telephone know that a call is waiting. The attendant is then free to answer
other calls. The attendant hears a call waiting ringback tone and the busy telephone
user hears a call waiting tone. This tone is heard only by the called telephone
user.
- Calling of inward restricted stations. A telephone with a class of restriction (COR)
that is inward restricted cannot receive public network, attendant-originated, or
attendant-extended calls. This feature allows you to override this restriction.
- Conference. The conference feature allows an attendant to set up a conference call
for as many as six conferees, including the attendant. Conferences from inside and
outside the system can be added to the conference call.
- Enhanced Return Call to (same) Attendant. Communication Manager provides
individual queuing functions for each attendant supporting a multiplicity of waiting
calls at a given time.
- Listed directory number. Allows outside callers to access your attendant group in
two ways, depending on the type of trunk used for the incoming call.
- Override of diversion features. The override of diversion feature allows an attendant
to bypass diversion features such as send all calls and call coverage by putting a
call through to an extension even when these diversion features are on. This feature,
together with attendant intrusion, can be used to get an emergency or urgent call
through to a telephone user.
- Priority queue. Priority queue places incoming calls to the attendant in an orderly
queue when these calls cannot go immediately to the attendant.
- Release loop operation. Release loop operation allows the attendant to hold a call
at the console if the call cannot immediately go through to the person being called.
A timed reminder begins once the call is on hold.
- Selective conference mute. Selective conference mute allows a conference call
participant, who has a display station, to mute a noisy trunk line. Selective
conference mute is also known as far end mute.
- Serial calling. The serial calling feature enables an attendant to transfer trunk calls
that return to the same attendant after the called party hangs up. The returned call
can then transfer to another station within the switch. This feature is useful if trunks
are scarce and direct inward dialing services are unavailable.
- Timed reminder and attendant timers. Attendant timers automatically alert the
attendant after an administered time interval for the certain types of calls.
• Centralized Attendant Service. Centralized Attendant Service (CAS) enables attendant
services in a private network to be concentrated at a central location. Each branch in a
centralized attendant service has its own listed directory number or other type of access
from the public network. Incoming calls to the branch, as well as calls made by users
directly to the attendants, are routed to the centralized attendants over release link
trunks.
• Display. The display feature shows call-related information that helps the attendant to
operate the console. This feature also shows personal service and message
information.
• Making calls.
- Auto Start and Do Not Split. The Auto Start feature allows the attendant to make a
telephone call without pushing the start button first. If the attendant is on an active
call and presses digits on the keypad, the system automatically splits the call and
begins dialing the second call.
- Auto Manual Splitting. Auto Manual Splitting allows an attendant to announce a call
or consult privately with the called party without being heard by the calling party on
the call. It splits the calling party away so the attendant can confidentially determine
if the called party can accept the call.
• Monitoring calls.
- Attendant control of trunk group access. Use the Attendant Control of Trunk Group
Access feature to allow the attendant to control outgoing and two-way trunk
groups.
- Attendant direct extension selection. This feature allows the attendant to keep track
of extension status - whether the extension is idle or busy - and to place or extend
calls to extension numbers without having to dial the extension number.
- Attendant direct trunk group selection. With this feature, the attendant directs access
to an idle outgoing trunk by pressing the button assigned to the trunk group. This
feature eliminates the need for the attendant to memorize, or look up, and dial the
trunk access codes associated with frequently used trunk groups.
- Crisis alerts to an attendant console. Crisis alert uses both audible and visual alerting
to notify attendant consoles when an emergency call is made. Audible alerting
sounds like an ambulance siren. Visual alerting flashes the CRSS-ALRT button lamp
and displays the caller's name and extension (or room).
- Trunk group busy/warning indicators to attendant. This feature provides the
attendant with a visual indication that the number of busy trunks in a group has
reached an administered level. A visual indication is also provided when all trunks
in a group are busy. This feature is particularly helpful to show the attendant that the
attendant control of trunk group access feature needs to be invoked.
- Trunk identification by attendant. Trunk identification allows an attendant or display-
equipped telephone user to identify a specific trunk being used on a call. This
capability is provided by assigning a trunk ID button to the attendant console or
telephone. This feature is particularly helpful for identifying a faulty trunk. That trunk
can then be removed from service and the problem quickly corrected.
- Visually Impaired Attendant Service. Visually Impaired Attendant Service (VIAS)
provides voice feedback to a visually impaired attendant. Each voice phrase is a
sequence of one or more single-voiced messages. This feature defines six attendant
buttons to aid visually impaired attendants.
Note:
AE Services has its own set of customer documentation, including an overview. This
Overview of Communication Manager does not outline the changes to AE Services.
• Device and media control API. Device and media control API provides a connector to
Communication Manager that allows clients to develop applications that provide first party
call control. Applications can register as IP extensions on Communication Manager and
then monitor and control those extensions.
Device and media control API consists of connector server software and a connector
client API library. The connector server software runs on a hardware server that is
independent from Communication Manager. That is, device and media control API does
not run co-resident with Communication Manager.
Tip:
Ask your Avaya representative for a complete list of device and media control API
documentation.
• Co-resident branch Gateway. In simplest terms, the branch Gateway is an application
that enables communications between TCP/IP clients and Communication Manager call
processing. In more technical terms, the application is software that both routes
internetwork messages from one protocol to another (ISDN to TCP/IP) and bridges all
ASAI message traffic by way of a TCP/IP tunnel protocol.
• Java telephony application programming interface (JTAPI) is an open API supported by
Avaya computer telephony that enables integration to Communication Manager ASAI.
• Telephony Services Application Programming Interface (TSAPI) is an open API
supported by Avaya computer telephony that allows integration to Communication
Manager ASAI. TSAPI is based on international standards for CTI telephony services.
Specifically, the European Computer Manufacturers Association (ECMA) CTI standard
Scalability
System capacities have been expanded for many products and features.
For the entire list of updated capacities, see Avaya Aura® Communication Manager System
Capacities Table, 03-300511.
• Connection preserving upgrades for duplex servers. The connection preserving upgrades
for duplex servers feature provides connection preservation on upgrades of duplex
servers for:
- connections involving IP telephones
- connections involving TDM connections on port networks
- connections on branch gateways
- IP connections between port networks and branch gateways
• Communication Manager Survivable Core provides survivability by allowing backup
servers to be placed in various locations in the customer network. The backup servers
supply service to port networks in the case where the main server or server pair fails, or
connectivity to the main server or server pair is lost.
- Automatic return to primary (main) server. When the Survivable Core is in control
due to a network fragmentation or catastrophic main server failure, the return to the
main server is predicated by the scheduled, manual, and automatic options.
- The Dial Plan Transparency for Survivable Remote and Survivable Core preserves
users’ dialing patterns if a branch gateway registers with Survivable Remote, or
when a port network registers with Survivable Core.
• IP bearer duplication using the TN2602AP circuit pack. The TN2602AP IP Media
Resource 320 circuit pack provides high-capacity voice over Internet protocol (VoIP)
audio access to the switch for local stations and outside trunks.
- Load balancing. Up to two TN2602AP circuit packs may be installed in a single port
network for load balancing. The TN2602AP circuit pack is also compatible with and
can share load balancing with the TN2302 and TN802B IP Media Processor circuit
packs.
- Bearer signal duplication. Two TN2602AP circuit packs may be installed in a single
port network for bearer signal duplication. In this configuration, one TN2602AP is an
active IP media processor and one is a standby IP media processor.
• IP endpoint Time-to-Service The IP endpoint time-to-service (TTS) feature improves a
customer’s IP endpoint time to service, especially in cases where the system has a lot of
IP endpoints trying to register or re-register. With this feature, the system considers that
IP endpoints are in-service immediately after they register.
• A survivable processor is an Internal Call Controller (ICC) with an integral branch
gateway, in which the ICC is administered to behave as a spare processor rather than as
the main processor. The standby Avaya S8300 Server runs in standby mode with the
main server ready to take control in the event of a outage with no loss of
communication.
• Handling of split registrations. Split registrations occur when resources on one network
region are registered to different servers. For example, after an outage activates the
Survivable Remote server (Local Survivable Processors) or Survivable Core server
(Enterprise Survivable Server), telephones in a network region register to the main server,
while the branch gateways in that network region are registered with the Survivable
Remote server. The telephones registered with the main server are isolated from their
See Avaya Aura® Communication Manager Security Design for further information.
Related topics:
NIST support on page 49
NIST support
The National Institute of Standards and Technology (NIST) develops cryptographic standards
for the United States government. NIST recommends that starting in 2014, the digital
signatures of Identity Certificates use SHA2 hashing and 2048–bit encryption keys. NIST
requires at least 2048 bit keys.
With theCommunication Manager Release 6.3.6 security service patch, you can receive and
validate the certificate that uses the SHA-2 signing algorithm and 2048 bit RSA keys. Using
Communication Manager System Management Interface, you can import the third-party
trusted certificate that uses the SHA-2 signing algorithm.
• Busy tone disconnect. In some regions of the world, the CO sends a busy tone for the
disconnect message. With busy tone disconnect, the switch disconnects analog loop-start
CO trunks when a busy tone is sent from the CO.
• Country-specific localization
- Brazil. Block collect call. This feature blocks collect calls on class-of-restriction basis.
This feature is available for any switch that uses the Brazil country code.
- Italy. Distributed Communications Systems protocol Italian DCS adds features to the
existing DCS capabilities and requires the use of Italian TGU/TGE tie trunks.
- Japan.
• National private networking provides support for Japanese private ISDN
networks.
• Katakana character set Communication Manager supports the Katakana
character set .
- Russia
• Central Office support on branch gateways. Communication Manager supports
central office (CO) trunks in Russia using Avaya branch gateways.
• ISDN/DATS network support. This feature supports ISDN/DATS trunk networks
when the tone generated field is set to 15 (Russia) on the system-parameters
tone—generation screen. It modifies the overlap sending delay and ISDN T302
and T304 timers to support the Russian trunk network.
• Multi-Frequency Packet signaling. Multi-Frequency Packet (MFP) address
signaling is provided in Russia on outgoing CO trunks. Calling party number
and dialed number information is sent on outgoing links between local and toll
switches.
• E&M signaling - E&M trunks are used to provide analog communications links.
Continuous and pulsed Continuous and pulsed E&M signaling is a modification to the
E&M signaling used in the United States. Continuous E&M signaling is intended for use
in Brazil, but can also be used in Hungary. Pulsed E&M signaling is intended for use in
Brazil.
• Multinational Locations. For customers who operate in more than one country, the
Multinational Locations feature provides the ability to use a single Enterprise
Communication Server (ECS) across multiple countries.
• Public network call priority provides call retention, forced disconnect, intrusion, mode-of-
release control, and re-ring to switches on public networks. Different countries frequently
refer to these capabilities by different names.
• QSIG support for Unicode. The QSIG support for Unicode feature extends the Unicode
support on a single server to multi-node Communication Manager networks. This feature
allows Unicode support across large campus configurations.
• World class tone detection. World class tone detection enables Communication Manager
to identify and handle different types of call progress tones, depending on the system
administration.
• XOIP Tone Detection Bypass. The X over IP Tone Detection Bypass feature (where X =
modem, fax, TTY-TDD, and so on) serves customers using older or non-standard external
equipment such as modems, fax, TTY devices which are not easily recognized by VoIP
resources within Communication Manager.
A deployment ................................................................. 15
Device Support ........................................................... 19
Administration .............................................................41 document changes ....................................................... 7
Administration features ...............................................41 document purpose ....................................................... 7
Attendant .................................................................... 42
Automatic Call Distribution ......................................... 30 E
Avaya Business Advocate .......................................... 31
Avaya Call Center on gateways ................................. 29 evolution server .......................................................... 16
Avaya courses ............................................................ 10
B F
Basic Call Management System ................................ 31 feature server ............................................................. 16
BCMS ......................................................................... 31
Business Advocate ..................................................... 31
I
C
Intelligent Networking ................................................. 24
Call Center ................................................................. 29 intended audience ........................................................ 7
Call Distribution .......................................................... 30 Interfaces ....................................................................26
Automatic ............................................................. 30 Data ..................................................................... 26
call log support ........................................................... 39
call notification ............................................................ 40
L
call routing .................................................................. 37
Capacities ...................................................................46 legal notice ................................................................... 2
codec support ............................................................. 40 Localization ................................................................ 49
Collaboration .............................................................. 34
Communication Manager .......................... 13, 14, 29, 45
overview ............................................................... 13 M
Software Bundles ................................................. 14
Mobility ....................................................................... 32
Communication Manager evolution server ................. 16
Communication Manager feature server .................... 16
Communication Manager functionality ....................... 39 N
call logs ................................................................ 39
Communication Manager Localization ....................... 49 Networking ............................................................ 23, 24
Communication Manager System .............................. 14 Intelligent ..............................................................24
Communication Manager template ............................ 17 Public ................................................................... 23
Computer Telephony Integration ................................ 30 NIST support .............................................................. 49
connectivity .................................................................20 security enhancement .......................................... 49
gateway ................................................................20
port network ......................................................... 20 O
Connectivity ................................................................ 20
Trunk .................................................................... 20 overview ..................................................................... 13
CTI ..............................................................................30 Communication Manager ..................................... 13
Customization .............................................................45
D P
Data Interfaces ........................................................... 26 Privacy ........................................................................48
S
U
Safety ......................................................................... 48
Scalability ................................................................... 46 User features .............................................................. 42
Security ...................................................................... 48
security enhancement ................................................ 49
NIST support ........................................................ 49
V
support ....................................................................... 12
videos ......................................................................... 12
contact ................................................................. 12
virtualization ............................................................... 15
Supported Devices ..................................................... 19
survivability ................................................................. 46
Survivable Core .......................................................... 46 W
Survivable Remote ..................................................... 46
System Platform ......................................................... 15 warranty ......................................................................12