Deploying Avaya Call Management

System

Release 21.0
Issue 3
November 2024
© 2015-2024, Avaya LLC TERMS OF USE. IF YOU DO NOT HAVE SUCH AUTHORITY,
All Rights Reserved. OR IF YOU DO NOT WISH TO ACCEPT THESE TERMS OF
USE, YOU MUST NOT ACCESS OR USE THE HOSTED SERVICE
Notice OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED
While reasonable efforts have been made to ensure that the SERVICE.
information in this document is complete and accurate at the time Licenses
of printing, Avaya assumes no liability for any errors. Avaya reserves
the right to make changes and corrections to the information in this The Global Software License Terms (“Software License Terms”)
document without the obligation to notify any person or organization are available on the following website https://www.avaya.com/en/
of such changes. legal-license-terms/ or any successor site as designated by Avaya.
These Software License Terms are applicable to anyone who
Documentation disclaimer installs, downloads, and/or uses Software and/or Documentation. By
“Documentation” means information published in varying media installing, downloading or using the Software, or authorizing others to
which may include product information, subscription or service do so, the end user agrees that the Software License Terms create
descriptions, operating instructions and performance specifications a binding contract between them and Avaya. In case the end user is
that are generally made available to users of products. accepting these Software License Terms on behalf of a company or
Documentation does not include marketing materials. Avaya shall other legal entity, the end user represents that it has the authority to
not be responsible for any modifications, additions, or deletions bind such entity to these Software License Terms.
to the original published version of Documentation unless such Copyright
modifications, additions, or deletions were performed by or on the
express behalf of Avaya. End user agrees to indemnify and hold Except where expressly stated otherwise, no use should be made
harmless Avaya, Avaya's agents, servants and employees against of materials on this site, the Documentation, Software, Hosted
all claims, lawsuits, demands and judgments arising out of, or in Service, or hardware provided by Avaya. All content on this site, the
connection with, subsequent modifications, additions or deletions to documentation, Hosted Service, and the product provided by Avaya
this documentation, to the extent made by End user. including the selection, arrangement and design of the content is
owned either by Avaya or its licensors and is protected by copyright
Link disclaimer and other intellectual property laws including the sui generis rights
Avaya is not responsible for the contents or reliability of any linked relating to the protection of databases. You may not modify, copy,
websites referenced within this site or Documentation provided by reproduce, republish, upload, post, transmit or distribute in any way
Avaya. Avaya is not responsible for the accuracy of any information, any content, in whole or in part, including any code and software
statement or content provided on these sites and does not unless expressly authorized by Avaya. Unauthorized reproduction,
necessarily endorse the products, services, or information described transmission, dissemination, storage, or use without the express
or offered within them. Avaya does not guarantee that these links will written consent of Avaya can be a criminal, as well as a civil offense
work all the time and has no control over the availability of the linked under the applicable law.
pages. Virtualization
Warranty The following applies if the product is deployed on a virtual machine.
Avaya provides a limited warranty on Avaya hardware and software. Each product has its own ordering code and license types. Unless
Please refer to your agreement with Avaya to establish the terms of otherwise stated, each Instance of a product must be separately
the limited warranty. In addition, Avaya’s standard warranty language licensed and ordered. For example, if the end user customer or
as well as information regarding support for this product while under Avaya Channel Partner would like to install two Instances of the
warranty is available to Avaya customers and other parties through same type of products, then two products of that type must be
the Avaya Support website: https://support.avaya.com/helpcenter/ ordered.
getGenericDetails?detailId=C20091120112456651010 under the link Third Party Components
“Warranty & Product Lifecycle” or such successor site as designated
by Avaya. Please note that if the product(s) was purchased from an The following applies only if the H.264 (AVC) codec is distributed
authorized Avaya channel partner outside of the United States and with the product. THIS PRODUCT IS LICENSED UNDER THE AVC
Canada, the warranty is provided by said Avaya Channel Partner and PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
not by Avaya. CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE
REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH
“Hosted Service” means an Avaya hosted service subscription that THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
You acquire from either Avaya or an authorized Avaya Channel VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
Partner (as applicable) and which is described further in Hosted SAS PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
or other service description documentation regarding the applicable PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE
hosted service. If You purchase a Hosted Service subscription, IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
the foregoing limited warranty may not apply but You may be ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA,
entitled to support services in connection with the Hosted Service L.L.C. SEE HTTP://WWW.MPEGLA.COM.
as described further in your service description documents for the
applicable Hosted Service. Contact Avaya or Avaya Channel Partner Service Provider
(as applicable) for more information. WITH RESPECT TO CODECS, IF THE AVAYA CHANNEL
Hosted Service PARTNER IS HOSTING ANY PRODUCTS THAT USE OR
EMBED THE H.264 CODEC OR H.265 CODEC, THE AVAYA
THE FOLLOWING APPLIES ONLY IF YOU PURCHASE AN CHANNEL PARTNER ACKNOWLEDGES AND AGREES THE
AVAYA HOSTED SERVICE SUBSCRIPTION FROM AVAYA OR AVAYA CHANNEL PARTNER IS RESPONSIBLE FOR ANY AND
AN AVAYA CHANNEL PARTNER (AS APPLICABLE), THE TERMS ALL RELATED FEES AND/OR ROYALTIES. THE H.264 (AVC)
OF USE FOR HOSTED SERVICES ARE AVAILABLE ON THE CODEC IS LICENSED UNDER THE AVC PATENT PORTFOLIO
AVAYA WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO LICENSE FOR THE PERSONAL USE OF A CONSUMER
UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR OTHER USES IN WHICH IT DOES NOT RECEIVE
OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND REMUNERATION TO: (i) ENCODE VIDEO IN COMPLIANCE WITH
ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES THE THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC
HOSTED SERVICE. BY ACCESSING OR USING THE HOSTED VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A
SERVICE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO
BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE
DOING SO (HEREINAFTER REFERRED TO INTERCHANGEABLY IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.
AS “YOU” AND “END USER”), AGREE TO THE TERMS OF USE. ADDITIONAL INFORMATION FOR H.264 (AVC) AND H.265 (HEVC)
IF YOU ARE ACCEPTING THE TERMS OF USE ON BEHALF A CODECS MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://
COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT WWW.MPEGLA.COM.
YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE
Compliance with Laws
You acknowledge and agree that it is Your responsibility to comply
with any applicable laws and regulations, including, but not limited
to laws and regulations related to call recording, data privacy,
intellectual property, trade secret, fraud, and music performance
rights, in the country or territory where the Avaya product is used.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your
company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If You suspect that You are being victimized by Toll Fraud and You
need technical assistance or support, please contact your Avaya
Sales Representative.
Security Vulnerabilities
Information about Avaya’s security support policies can be
found in the Security Policies and Support section of https://
support.avaya.com/security.
Suspected Avaya product security vulnerabilities are handled
per the Avaya Product Security Support Flow (https://
support.avaya.com/css/P8/documents/100161515).
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation, Hosted Service(s), and product(s) provided
by Avaya are the registered or unregistered Marks of Avaya, its
affiliates, its licensors, its suppliers, or other third parties. Users
are not permitted to use such Marks without prior written consent
from Avaya or such third party which may own the Mark. Nothing
contained in this site, the Documentation, Hosted Service(s) and
product(s) should be construed as granting, by implication, estoppel,
or otherwise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya LLC.
All non-Avaya trademarks are the property of their respective owners.
Linux® is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support website: https://support.avaya.com, or such successor site
as designated by Avaya.
Contact Avaya Support
See the Avaya Support website: https://support.avaya.com for
Product or Cloud Service notices and articles, or to report a
problem with your Avaya Product or Cloud Service. For a list of
support telephone numbers and contact addresses, go to the Avaya
Support website: https://support.avaya.com (or such successor site
as designated by Avaya), scroll to the bottom of the page, and select
Contact Avaya Support.
 Contents

Chapter 1: Purpose................................................................................................................... 7
Change history........................................................................................................................ 7
Chapter 2: Deployment planning............................................................................................. 9
Planning checklist.................................................................................................................... 9
Deployment guidelines........................................................................................................... 10
Functional differences when installing CMS in a virtualized environment.................................... 11
High Availability for customer-provided VMware....................................................................... 12
Virtual machine resource requirements and average utilization ................................................ 12
Capacities............................................................................................................................. 14
Customer configuration data worksheets................................................................................. 15
Chapter 3: Deploying CMS software using an OVA file...................................................... 17
Deploying CMS software checklist.......................................................................................... 17
Cloned and copied OVAs are not supported............................................................................ 17
Activating the license for a CMS server................................................................................... 18
Installing a license file on a WebLM server.............................................................................. 19
Downloading software from PLDS.......................................................................................... 20
Deploying the OVA................................................................................................................ 21
Deploying the OVA on a customer-provided VMware server............................................... 21
Deploying the OVA on an Avaya Solutions Platform server................................................. 23
Configuring the virtual machine automatic startup settings on VMware...................................... 25
Configuring the virtual machine for different configuration sizes................................................. 26
Configuring the virtual machine as a small configuration..................................................... 26
Configuring the virtual machine as a medium configuration................................................. 27
Configuring the virtual machine as a large configuration..................................................... 28
Chapter 4: Deploying the CMS KVM..................................................................................... 31
Planning checklist for CMS KVM deployment.......................................................................... 31
Activating the license for a CMS server................................................................................... 32
Installing a license file on a WebLM server.............................................................................. 34
Downloading software from PLDS.......................................................................................... 35
Preparing the CMS KVM file................................................................................................... 36
Importing the CMS virtual machine......................................................................................... 37
Chapter 5: Configuring system features.............................................................................. 39
Configuring system features checklist..................................................................................... 39
Verifying that CMS is installed................................................................................................ 40
Initializing the CMS database................................................................................................. 40
Setting the root password....................................................................................................... 41
Configuring the system network.............................................................................................. 42
Disk encryption..................................................................................................................... 45
Configuring WebLM, EASG, and the encryption passphrase..................................................... 45

November 2024 Deploying Avaya Call Management System 4

Comments on this document?
 Installing CMS patches ......................................................................................................... 47
Updating Linux RPMs............................................................................................................ 47
Running the CMS security script............................................................................................. 48
Turning on IDS and adding disk space for medium and large configurations............................... 48
Verifying system startup and remote access............................................................................ 49
Chapter 6: Configuring CMS features................................................................................... 51
Configuring CMS features checklist........................................................................................ 51
Assigning passwords to the default CMS login IDs................................................................... 51
Viewing CMS authorizations................................................................................................... 52
Activating the CMS Supervisor Web Client software................................................................. 52
Managing certificates for Web Client software.................................................................... 53
Installing the root certificate and any intermediate certificate for the Web Client software...... 54
Installing the root certificate and any intermediate certificate for the Web Client software...... 55
Starting the Web Client software....................................................................................... 56
Storage requirements for CMS backups.................................................................................. 56
Calculating data space requirements for CMSADM backups............................................... 56
Calculating data space requirements for CMS full maintenance backups............................. 57
Setting up the Alarm Origination Manager .............................................................................. 58
Configuring an Alarm Destination ..................................................................................... 59
Configuring an SNMP User.............................................................................................. 62
Configuring an Alarm ID................................................................................................... 65
Configuring a Customer ID .............................................................................................. 65
Sending an AOM Test Alarm............................................................................................ 66
Clearing SNMP Alarms ................................................................................................... 66
CMS SNMP alarm information.......................................................................................... 67
Locating and installing the CMS-MIB.txt file ...................................................................... 71
Setting up AOM configuration for alarming using Socket/SAL.............................................. 71
Chapter 7: Setting up CMS..................................................................................................... 75
About configuring the CMS software....................................................................................... 75
Setting up CMS interactively................................................................................................... 75
Editing a flat file..................................................................................................................... 78
Setting up CMS using the flat file............................................................................................ 79
Chapter 8: Performing the customer handover................................................................... 82
CMS customer handover checklist.......................................................................................... 82
Verifying the system date and time ......................................................................................... 83
Forwarding CMS warning messages....................................................................................... 83
Checking free space allocation .............................................................................................. 83
Testing the ACD link.............................................................................................................. 84
Assigning customer passwords .............................................................................................. 85
Testing the CMS software...................................................................................................... 86
Finalizing the on-site installation ............................................................................................ 89
Appendix A: Flat file example................................................................................................ 90
Example of a flat file.............................................................................................................. 90

November 2024 Deploying Avaya Call Management System 5

Comments on this document?
Appendix B: Resources....................................................................................................... 100
Documentation.................................................................................................................... 100
Finding documents on the Avaya Support website........................................................... 102
Avaya Documentation Center navigation......................................................................... 102
Viewing Avaya Mentor videos............................................................................................... 104
Support.............................................................................................................................. 104
Using the Avaya InSite Knowledge Base......................................................................... 104
Glossary................................................................................................................................. 106

November 2024 Deploying Avaya Call Management System 6

Comments on this document?
Chapter 1: Purpose

This document is for implementation engineers and other personnel who deploy CMS. They can use
this document to install a Avaya Call Management System (CMS) server as a virtual machine on an
Avaya supplied hypervisor server.
The supported options are:

Avaya Solutions Platform CMS R19.2.x CMSR20.x CMS R21.x

Platform Hypervisor
ASP 130 R6 RHEL 8.10 – – ✓
ASP 130 R5 VMware ✓ ✓ ✓

Alternate hypervisor deployment options

• You can deploy CMS as a virtual machine on Amazon Web Services (AWS) or Google
Cloud Platform (GCP). Refer to the separate Deploying Avaya Call Management System in
an Infrastructure as a Service Environment manual.
• When deploying CMS on a customer-provided hypervisor, you can use VMware. This is
supported on:
- VMware vSphere ESXi 7.0
- VMware vCenter Server 7.0
- VMware vSphere ESXi 8.0
- VMware vCenter Server 8.0

Change history
The following table outlines the key changes in this document for Release 21.x:

November 2024 Deploying Avaya Call Management System 7

Comments on this document?
Purpose

Issue Date Summary of changes

3 November 2024 • Added Red Hat KVM information and rewrote Avaya Solutions
Platform information throughout the document.
• Cleaned up outdated information.
• Revised and restructured information throughout the document.
For example, the relevant content in the Architecture overview
chapter has been merged with the Planning chapter.
2 August 2024 • Removed outdated information about configuring the encryption
passphrase.
• Removed outdated information in "Running the CMS security
script".
• Revised a command output example in "Calculating data space
requirements for CMSADM backups".
• Revised old information in Setting up CMS interactively.
1 June 2024 • Updated VMware versions.
• Revised outdated IBM references.
• Revised encryption information and removed outdated procedures.
• Updated various examples.

November 2024 Deploying Avaya Call Management System 8

Comments on this document?
Chapter 2: Deployment planning

This chapter provides planning information and other deployment guidelines. You can deploy CMS
on an Avaya Solutions Platform ASP 130 R6 server or in a customer-provided virtual environment.
As of CMS R21.x, the VMware information in this document only applies to customer-provided
systems. New CMS deployments on an Avaya Solutions Platform server use Red Hat KVM on the
ASP 130 R6.
Note:
• The profile of the Avaya Solutions Platform hardware server you install depends on the
sizing tool specification. You must determine the configuration size before starting the
deployment because the configuration is based on whether the system is small, medium,
or large.
Related links
Planning checklist on page 9
Deployment guidelines on page 10
Functional differences when installing CMS in a virtualized environment on page 11
High Availability for customer-provided VMware on page 12
Virtual machine resource requirements and average utilization on page 12
Capacities on page 14
Customer configuration data worksheets on page 15

Planning checklist
Ensure that the following activities are complete before deploying the virtual appliance:

November 2024 Deploying Avaya Call Management System 9

Comments on this document?
Deployment planning

No Task Notes

1. Assess the infrastructure resource Key factors are:

requirements for your deployment.
• CPU usage
• Memory usage
• Storage requirements
• Network usage
• Supported capacity
2. Plan and resource all staging and This includes IP addressing, naming conventions, and
verification activities. application-specific configuration.
3. Purchase the appropriate order For customer-provided deployments: You must
codes and licenses. separately license each CMS instance, that is, each
installation of an OVA. Ensure that all OVA files are
accessible.
For Avaya Solutions Platform deployments: You no
longer need a license key, but you must have a record
in the Avaya Product Licensing and Delivery System
(PLDS) of each instance of the server hypervisor.
4. Get the WebLM license server Use Avaya WebLM to manage product licenses
details and install the CMS license. obtained from PLDS. For more information, see
Installing a license file on a WebLM server on
page 19.
5. Ensure that you have the CMS A CMS R21.x VMware OVA is available on the Avaya
software image for deployment. Support website. You can use this to deploy CMS on
your own customer-provided server.
For deployments on Avaya Solutions Platform,
download the OVA with the CMS KVM images
from the Avaya Support website. The KVM OVA
is only intended for Avaya Solutions Platform
deployments and cannot be used for a customer-
provided deployment.

Note:
You can deploy a configuration that consists of a mixture of CMS servers hosted on VMware
platforms and CMS servers hosted on non-VMware platforms.

Deployment guidelines
• Deploy the virtualized environment on the same cluster if the cluster goes beyond the host
boundary.

November 2024 Deploying Avaya Call Management System 10

Comments on this document?
 Functional differences when installing CMS in a virtualized environment

• Segment redundant elements on a different cluster, or ensure that the redundant elements
are not on the same host.
• Create a tiered or segmented cluster infrastructure that isolates critical applications, such as
CMS, from other virtual machines.
• Plan for rainy day scenarios. Do not configure resources only for traffic or performance on an
average day.
• Do not oversubscribe resources because this affects performance.
• Monitor the server, host, and virtualized environment performance.

Important:
The values for performance, occupancy, and usage can vary. A virtual machine might
run at 50% occupancy. If the CPU occupancy exceeds 60% or the CMS real-time report
mismatches the refresh rates, you could experience performance issues.

Functional differences when installing CMS in a virtualized

environment
When deploying CMS in an virtualized environment, it operates almost identically to a CMS
deployment on a hardware server using the Linux operating system. This section describes a few
of the functional areas that are different when deploying CMS in a virtualized environment.
Hardware
CMS deployment on VMware supports both customer-provided servers or Avaya-provided
Avaya Solutions Platform 130 R5 servers. For more information about Avaya Solutions
Platform hardware, refer to the Avaya Solutions Platform 130/S8300 Overview and Specification
documentation.
For VMware-certified compatibility guides and product interoperability matrices, see https://
www.vmware.com/guides.html.
Software media for Avaya Solutions Platform deployments
As of CMS Release 21.x, Avaya Solutions Platform deployments use Red Hat KVM on the Avaya
Solutions Platform R6 deployments only. You cannot use the KVM OVA for a customer-provided
deployment.
Related links
Deployment planning on page 9

November 2024 Deploying Avaya Call Management System 11

Comments on this document?
Deployment planning

High Availability for customer-provided VMware

CMS HA is different from VMware vSphere HA. VMware vSphere HA is a specific approach to
VMware deployment.
CMS HA
CMS HA provides redundancy to reduce the potential loss of call center data. You can configure
HA if you have two CMS servers. The CMS servers connect to an ACD system. With HA, one
CMS server is designated as a primary server and the other is designated as a secondary server.
When the primary server goes down, the secondary server takes over.
• You can optionally configure a dual-IP CMS server, where two IP addresses are
administered. One connects to the main ACD system and the other connects to an Enterprise
Survivability Server (ESS).
• For detailed information about CMS HA, see Avaya Call Management System High
Availability Connectivity, Upgrade and Administration.
VMware vSphere HA
VMware vSphere HA provides automatic detection of hardware failures, server failures, and
operating system failures. If a physical server fails, affected virtual machines restart automatically
on another production server that has spare capacity. If an operating system fails, vSphere HA
restarts the affected virtual machine on the same server. The restart takes several minutes, but
the system does recover.
VMware HA ensures that capacity is always available to restart all virtual machines affected
by a server failure. HA continuously and intelligently monitors capacity use and reserves spare
capacity to restart virtual machines. VMware HA helps VMware vSphere users identify abnormal
configuration settings detected within HA clusters. The VMware vSphere client interface reports
relevant operating status and potential error conditions with suggested steps for correction.

Virtual machine resource requirements and average

utilization
Before deploying a CMS virtual machine, ensure that the host can support the configuration you
want. After deployment and during normal operation, monitor the resource usage to ensure that
the proper level of resources remains available.
Important:
• If deploying on a customer provided virtual host platform, you can start with the minimum
memory, minimum memory reservation, and minimum disk space allocations. However,
Avaya will require you to increase the memory allocations if Avaya finds that reported
CMS problems relate to memory usage.
Minimum required resources for virtual machine configurations
The following table outlines the virtual machine resource requirements for different CMS profiles.

November 2024 Deploying Avaya Call Management System 12

Comments on this document?
 Virtual machine resource requirements and average utilization

VM resource Small Medium Large Extended Notes

vCPU Cores (CPU) 2 8 16 32 The number of single core virtual
CPUs.
Cores per Socket 2 8 16 32 The number of CPUs per socket. All
cores are assigned to one socket.
Therefore, the number of vCPU
cores are the number of logical
CPUs.
vCPU reservation 1200 MHz 4800 MHz 9600 MHz 9600 MHz Guaranteed CPU allocation: 25% of
vCPU capacity.
Calculation: vCPUs x processor
clock speed (2400Mhz)/4.
Memory 8 GB 32 GB 64 GB 64 GB The memory size represents the
" minimum for 4 GB 16 GB 32 GB – maximum that a CMS deployment
customer-provided might consume.
VM The medium and large
configuration memory sizes match
real hardware machines. The real
hardware memory configuration
considers future memory growth.
Memory reservation 8 GB 32 G 64 GB 64 GB If the memory is not reserved and
there is contention with other VM
applications for additional memory
resources, sufficient memory might
not be available, resulting in CMS
failures.
" minimum for 4 GB 16 GB 32 GB –
customer-provided
VM
Storage 800 GB 1200 GB 1800 GB 6000 GB If the recommended storage
value on the medium and large
configurations is not administered,
sufficient storage might not be
available resulting in CMS failure.

Note:
For medium and large
configurations, you will
configure two disks.
IOPS 200 300 600 600 The IOPS data is based on real
CMS hardware machines with 50%
read and 50% write data.
Shared NICs Two @ Two @ Two @ Two @ A typical CMS deployment only
1000 1000 1000 1000 requires two Ethernet ports, but
Mbps Mbps Mbps Mbps many hardware options provide a
four-port NIC.

November 2024 Deploying Avaya Call Management System 13

Comments on this document?
Deployment planning

The OVA contains many of the virtual machine resource requirements, such as vCPU reservation
and memory reservation. The target virtual machine confirms that the required resources in the
OVA are available before deploying the OVA.
Average resource and network utilization for standard configurations
Average resource usage Small Medium Large Notes
CPU consumed 600 MHz 2 GHz 8 GHz
Memory consumed 500 MB 2 GB 4 GB
Network consumed 0.252 Mbps 0.512 Mbps 1.696 Mbps
IOPS 12 18 28 IOPS is higher during nightly
summarization.

Requirements for expanding large configurations on customer-provided virtual

machines
To accommodate CMS deployments that require larger databases, you must increase the amount
of disk space on the virtual machine. Use the following table to determine the amount of disk
space required by the database to support a larger number of agent skill pairs at interval lengths
of 15 or 30 minutes.
The values in the table assume 62 days of interval storage and five years of daily storage (1825
days) when you have a one time zone. You can configure data storage allocation and view
free space allocation information from CMS Supervisor as described in Administering Avaya Call
Management System.
Agent skill pairs 200000 400000 600000 800000 1000000 1500000
Interval length 15 30 15 30 15 30 15 30 15 30 15 30
(minutes)
Minimum virtual 1.8 2.2 2.2 1.9 2.9 2.6 3.8 3.3 4.0 2.5 5.9 3.7
machine disk size
(TB)

Capacities
Use this table to determine the configuration to use for your deployment.
• Select the size that provides the capacities you require.
• If any capacity requires a larger configuration, use the larger configuration option.
- For example: If you need 100000 agent skill pairs but your peak busy-hour call volume is
200000, you must select the medium configuration.
• The Extended capacity option is only applicable for the AXP Private – Extended Scale ACD.
• Deployments on Avaya Solutions Platform support the small, medium, and large
configuration options only.

November 2024 Deploying Avaya Call Management System 14

Comments on this document?
 Customer configuration data worksheets

Parameter Small Medium Large Extended

Peak busy-hour call volume 30000 200000 400000 500000
Concurrent CMS Supervisor sessions1 50 200 2999 2999
Concurrent agents 500 5000 10000 30000
Third-party software 3 3 3 3
Agent skill pairs 100000 200000 800000 2 15000002
Reports per CMS Supervisor session 3 5 10 3 153
Report elements 4 5 5 12 12
Percentage of supervisors that can run 10% 50% 100% 100%
reports with a three-second refresh rate
Active agent traces 250 1000 5000 5000
Internal Call History (ICH) records - per 20 4000 4000 4000 4000
minutes
External Call History (ECH) records - per 20 10000 60000 300000 300000
minutes

1. This value is the total number of active CMS Supervisor PC Client and Web Client
sessions.
2. For actual capacity details, see Avaya Call Management System Overview and
Specification.
3. For actual capacity details, see Avaya Call Management System Overview and
Specification.
4. For a definition of Report elements, see Avaya Call Management System Overview and
Specification.
Related links
Deployment planning on page 9

Customer configuration data worksheets

The following worksheet identifies the key customer configuration information that you must enter
when deploying the OVA file. Plan your configuration data before you begin the deployment.
Parameter Your value
Location of OVA template file on your
computer
Virtual machine template name
Virtual machine location
Table continues…

November 2024 Deploying Avaya Call Management System 15

Comments on this document?
Deployment planning

Parameter Your value

Destination storage location for
virtual machine files
Disk format to store the virtual disks Thick Provision

The following worksheet identifies the key customer networking information that you must enter
when you run the /cms/toolsbin/netconfig command.
Parameter Example Your value
Network interface name eth0
Hostname for the CMS server vm_cms1
Use only the short hostname, not the
FQDN. The hostname cannot have
upper-case letters.

Important:
The CMS backup process
automatically assigns time-stamped
file names that truncate the CMS
server hostname if it is longer than
15 characters. To avoid confusion
between the backup files for
multiple CMS servers, do not use
the same first 15 characters for a
hostname when you have multiple
CMS servers in your deployment.
Domain name example.com
IP address 123.45.67.89
Netmask 255.255.255.0
Default gateway IP address 123.45.67.254
DNS IP addresses 123.1.0.1 123.1.0.2
123.1.0.3
Uup to 3 addresses separated with a
space
DNS search domains AltCompanyName.com
OtherCompanyName.co
Separated with a space
m

November 2024 Deploying Avaya Call Management System 16

Comments on this document?
Chapter 3: Deploying CMS software using
an OVA file

Deploying CMS software checklist

No Task Notes

1. Activate the license for the CMS Activating the license for a CMS server on page 18
server.
2. Install the license file on the Installing a license file on a WebLM server on
WebLM server. page 19
3. Download the OVA software. Download the software from the Avaya PLDS website
at https://plds.avaya.com. For more information, see
Downloading software from PLDS on page 20.
4. Deploy the OVA software. For more information, see Deploying the OVA on
page 21.
5. Configure the virtual machine for Configuring the virtual machine automatic startup
automatic startup. settings on VMware on page 25
6. Configure the virtual machine Configuring the virtual machine as a small
configuration. configuration on page 26
Configuring the virtual machine as a medium
configuration on page 27
Configuring the virtual machine as a large
configuration on page 28
7. Power up the virtual machine for For more information, see Initializing the CMS
the first time. database on page 40.

Cloned and copied OVAs are not supported

To redeploy a virtual machine, do not create a copy of the virtual machine or clone the virtual
machine. These processes have subtle technical details that require a thorough understanding of
the effects of these approaches. To avoid any complexities and unexpected behavior, deploy a
new OVA. At this time, Avaya only supports the deployment of new OVAs.

November 2024 Deploying Avaya Call Management System 17

Comments on this document?
Deploying CMS software using an OVA file

Activating the license for a CMS server

About this task
Important:
Each CMS deployment must have its own license file on a WebLM Release 8.0 or later server
and must use Centralized Licensing. Enterprise licensing is not supported for CMS. That is,
multiple CMS deployments cannot share one license file.
Before you begin
Get the following information:
• SAP order number
• WebLM server host ID
Note:
The SAP order number and the WebLM server host ID must be listed under the same
Company ID.
Procedure
1. In a browser window, navigate to the PLDS site:
https://plds.avaya.com
2. Log on to PLDS using your customer ID and password.
3. Navigate to Assets > View Entitlements.
PLDS displays the Search Entitlements screen.
4. Search for your license entitlement using one of the following criteria:
• SAP order number
• Sold to number
• License activation code
You can also use Advanced Search to find a license entitlement.
5. Click Search Entitlements.
PLDS displays the known license entitlements based on the search criteria.
6. For the customer’s entitlement record, click Options > Activate.
PLDS displays a list of possible entitlements.
7. Select the entitlement for CMS release for which you are installing or upgrading.
8. Click Activate.
PLDS displays the Search License Hosts screen. The available license hosts for the
Company ID are displayed on this screen.

November 2024 Deploying Avaya Call Management System 18

Comments on this document?
 Installing a license file on a WebLM server

Note:
You can also download a license file and install the file manually. For more information,
see Installing a license file on a WebLM server on page 19.
9. Select one of the displayed license hosts or create a new host by clicking Add a License
Host.
10. Click Next.
PLDS displays a registration summary screen.
11. Click Next.
PLDS displays the Activate Entitlements screen.
12. Select the quantity of each entitlement you want to activate.
13. Click Next.
14. Add notes for the activation, if needed.
15. Click Finish.
Related links
Deploying the CMS KVM on page 31

Installing a license file on a WebLM server

About this task
Avaya products use WebLM Release 8.0 or later to manage product licenses obtained through
PLDS. For CMS licensing, use either a standalone WebLM server or install the WebLM server on
a coresident Avaya Aura® System Manager. Licenses installed for WebLM must support SHA256
digital signatures and a 14-character host ID.
Important:
Use Centralized licensing for CMS. Enterprise licensing is not supported. This means that
multiple CMS deployments cannot share one license file. After enabling Centralized licensing,
you must assign every license file to the license ID in WebLM.
For more information about installing license files, see the following documents:
• Administering Avaya Aura® System Manager
• Administering standalone Avaya WebLM
Before you begin
Ensure that the XML license file is present in the computer.
Use the uninstall functionality of WebLM to remove any existing license file from the WebLM
server before you install a new license file. The system displays an error message if an older
license file is still available. For a centralized license file, the system automatically overwrites the

November 2024 Deploying Avaya Call Management System 19

Comments on this document?
Deploying CMS software using an OVA file

older license file during installation. If you experience problems while installing the license file, see
the information about license file installation errors in Administering standalone Avaya WebLM.
Procedure
1. Log in to the standalone WebLM web console or the System Manager console with
administrator privilege credentials.
2. In the navigation pane, click Install license.
3. On the Install license page, click Choose File and browse to the directory of the XML
license file that you saved on your computer.
4. Read the terms and conditions and click Accept the License Terms & Conditions.
5. Click Install.
WebLM displays a message on successful installation of the license file. The installation
of the license file might fail for various reasons. For example, the digital signature on the
license file is invalid. If you get such an error, request PLDS to redeliver the license file.
An error can also occur if the current capacity use exceeds the capacity in the installed
license.
6. Enable Centralized licensing as described in WebLM documentation.
With Centralized licensing, you must assign every license file to the license ID in WebLM.
7. Click New.
8. Enter a name to assign to the CMS.
9. Select the license file to associate with the CMS.
Related links
Deploying the CMS KVM on page 31

Downloading software from PLDS

Procedure
1. On your web browser, type http://plds.avaya.com to access the Avaya PLDS website.
2. Enter your login ID and password.
3. On the PLDS Home page, select Assets.
4. Click View Downloads.

5. Click the search icon for Company Name.

6. In the Search Companies dialog box, do the following:
a. In the %Name field, type Avaya or the Partner company name.
b. Click Search Companies.

November 2024 Deploying Avaya Call Management System 20

Comments on this document?
 Deploying the OVA

c. Locate the correct entry and click the Select link.

7. Search for the available downloads by using one of the following:
• In Download Pub ID, type the download pub ID.
• In the Application field, click the application name.
8. Click Search Downloads.
9. In the Download Manager box, click the appropriate Download link.

Note:
The first link, Click to download your file now, uses the Download Manager to
download the file. The Download Manager provides features to manage the download
(stop, resume, auto checksum). The click here link uses your standard browser
download and does not provide the download integrity features.
10. If you use the Download Manager, click Details to view the download progress.
11. Select a location where you want to save the file, and click Save.
12. (Optional) When the system displays the security warning, click Install.
When the installation is complete, PLDS displays the downloads again with a check mark
next to the downloads that have completed successfully.
Related links
Deploying the CMS KVM on page 31

Deploying the OVA

CMS supports the following VMware deployment options:
• Deploying the OVA on customer-provided VMware servers using vSphere.
• Deploying the OVA on Avaya Solutions Platform 130 Appliance VMware servers using ESXi.
Related links
Deploying the OVA on a customer-provided VMware server on page 21
Deploying the OVA on an Avaya Solutions Platform server on page 23

Deploying the OVA on a customer-provided VMware server

About this task
Note:
Based on the vSphere version, you might observe minor differences in the interface.
Before you begin
Download the OVA from PLDS and deploy the OVA on the VMware server. Note down the folder
and file name.

November 2024 Deploying Avaya Call Management System 21

Comments on this document?
Deploying CMS software using an OVA file

Determine the web browser. VMware recommends using Google Chrome or Mozilla Firefox.
Important:
Customers that deploy an OVA on their own VMware systems can initially choose to start with
the minimum memory allocation, minimum memory reservation allocation, and minimum disk
space. However, to maintain support from Avaya, Avaya might require you to later increase
the memory allocations (to no more than the recommended maximum value) if Avaya finds
that problems related to memory usage occur and cause failures on the CMS.
Important:
You must separately license each CMS instance, that is, each installation of OVA. To install
multiple instances of CMS, customers or business partners must order a separate CMS
license for each instance.
Procedure
1. To start the vSphere client software, do one of the following:

• In your web browser, enter https://<hostname>.company.com/vsphere-

client/?csp.
• In your web browser, enter https://<hostname>/ui/#/login.
2. In the User Name field, enter the vCenter Single Sign On user name that has permissions
on vCenter Server.
3. In the Password field, enter the password.
4. Click Login.
5. If you see a warning message on untrusted SSL certificate, select the appropriate action
based on your security policy based on the following security policy:
• To ignore the security for this login session only, click Ignore.
• To ignore the security warning for this login session and install the default certificate,
select Install this certificate and do not display any security warnings for this
server, and click Ignore.
Select this option only if you do experience any security problem in the default certificate
in your environment.
• To install a signed certificate before proceeding, click Cancel and ensure that the signed
certificate is installed on the vCenter Server system before you attempt to connect
again.
6. In the Home navigation pane, click Hosts and Clusters.
7. In the Host and Clusters tree, select an ESXi host where you want to deploy the OVA.
8. Select Actions, and then click Deploy OVF Template.
9. In the Deploy OVF Template window, do the following steps:
a. Select Local File, and then click Browse.

November 2024 Deploying Avaya Call Management System 22

Comments on this document?
 Deploying the OVA

b. Browse to the location of the CMS OVA file, select the OVA file, and then click Open.
c. Click Next.
d. In the Select a name and folder window, enter the virtual machine name and click
Next.
e. Select the destination compute resource and click Next.
f. In the Review Details window, verify the details of the OVA file, including the CMS
version number, and then click Next.
10. In the End User License Agreement window, review the license agreement.
11. In the End User License Agreement window, click Accept and click Next.
12. From the Select virtual disk format drop-down list, select Thick Provision.

Important:
Customers that deploy an OVA on their own VMware systems can initially choose to
start with the minimum memory allocation, minimum memory reservation allocation,
and minimum disk space. However, to maintain support from Avaya, Avaya might
require you to later increase the memory allocations (to no more than the
recommended maximum value) if Avaya finds that problems related to memory usage
occur and cause failures on the CMS.
13. From the VM Storage Policy drop-down list, select Datastore Default.
14. From the Datastore table, select Datastore and click Next.

Important:
The data store type that you select must use the VMFS5 or VMFS6 format.
15. In the Select networks window, choose a network from the Destination Network drop-
down, and then click Next.
16. In the Ready to Complete window verify the deployment settings and click Finish.
The Deploy OVF window closes and installation begins, the Recent Tasks pane displays
information for tasks Deploy OVF template and Import OVF package, the Status column
shows the percentage complete, and the installation should last 10-20 minutes depending
on the processing power of the server.

Deploying the OVA on an Avaya Solutions Platform server

About this task
Interfaces on different VMware ESXi versions might differ.
Before you begin
Download the file to the computer where you execute the vSphere client. Note down the folder
and the file name for the download.
Decide on the browser to use for gaining access to the vSphere client. VMware recommends
using Google Chrome or Mozilla Firefox.

November 2024 Deploying Avaya Call Management System 23

Comments on this document?
Deploying CMS software using an OVA file

Note:
For an Avaya Solutions Platform server, Avaya or Business Partner personnel downloads the
OVA from PLDS and deploy the OVA on the Avaya Solutions Platform server.
Procedure
1. On your web browser, type the VMware ESXi URL.
2. In the User name field, type your user name.
3. In the Password field, type your password.
4. Click Login.
5. (Optional) If the VMware ESXi client browser displays a warning message about an
untrusted SSL certificate, select the appropriate action based on your security policy
below:
• To ignore the security for this login session only, click Ignore.
• To ignore the security warning for this login session, and install the default certificate
so that the warning does not appear again, select Install this certificate and do not
display any security warnings for this server and click Ignore.
Select this option only if the default certificate does not present a security problem in
your environment.
• To install a signed certificate before proceeding, click Cancel and ensure that a signed
certificate is installed on the vCenter Server system before you attempt to connect
again.
6. In the Home navigation pane, click Host.
7. In the Host window, select Create/Register VM.
8. In the Select creation type window, select Deploy a virtual machine from an OVF or
OVA file and then click Next.
9. In the Select OVF and VMDK files window, do the following:
a. Enter the name of the virtual machine.
b. Select the Click to select files or drag/drop check box.
c. Browse to the location of the CMS OVA file, select the OVA file, click Open.
d. Click Next.
10. In the Select storage window, click the storage resource and then click Next.
11. In the End User License Agreement window, review the license agreement. If you agree to
the terms, click I agree and then click Next.
12. In the Deployment options window, implement the following settings.
a. From the Network Mapping drop-down list, select a subnetwork.
b. From the Disk Provisioning drop-down list, select Thick.

November 2024 Deploying Avaya Call Management System 24

Comments on this document?
 Configuring the virtual machine automatic startup settings on VMware

c. Select the Power on automatically check box.

d. Click Next.
13. In the Additional settings window, click Next.
14. In the Ready to Complete window, verify the deployment settings and then click Finish.
The Deploy OVF window closes and installation begins, the Recent Tasks pane displays
information for tasks Upload disk (Target VM name) and Import VApp package, the
Completed column shows the percentage complete, and the installation should last 10-15
minutes depending on the processing power of the server.

Configuring the virtual machine automatic startup settings

on VMware
About this task
When a vSphere ESXi host restarts after a power failure, the virtual machines that are
deployed on the host do not start automatically. You must configure the virtual machines to start
automatically.
In high availability (HA) clusters, the VMware HA software does not use the startup selections.
Before you begin
Verify with the ESXi system administrator that you have the permissions to configure the
automatic startup settings.
Procedure
1. In the web browser, type the vSphere vCenter host URL.
2. Click one of the following icons: Hosts and Clusters or VMs and Templates icon.
3. In the navigation pane, click the host where the virtual machine is located.
4. Click Manage.
5. In Virtual Machines, click VM Startup/Shutdown, and then click Edit.
The software displays the Edit VM Startup and Shutdown window.
6. Click Automatically start and stop the virtual machines with the system.
7. Click OK.

November 2024 Deploying Avaya Call Management System 25

Comments on this document?
Deploying CMS software using an OVA file

Configuring the virtual machine for different configuration

sizes
Configuring the virtual machine as a small configuration
About this task
Note:
Interfaces on different vSphere versions might differ.
Caution:
Do not change the resource settings, because any changes in the allocated resources can
impact the performance, capacity, and stability of the CMS virtual machine. To run at full
capacity, you must meet these resource size requirements. Removing or downsizing the
reserved space can put this requirement at risk. Any deviation in the requirements is at
customer’s own risk.
Before you begin
Turn off the virtual machine.
Procedure
1. On your web browser, type the vSphere vCenter URL and press Enter.
2. In the User name field, type your user name.
3. In the Password field, type your password.
4. Click Login.
5. On the vSphere Web Client home page, select one of the following icons:
• Hosts and Clusters
• VMs and Templates
6. In the navigation pane, click CMS Virtual Machine.
7. Click Actions > Edit Settings.
8. In the Edit Settings dialog box, do the following:
a. In the navigation pane, select CPU and click 2.
b. In the content pane, select Cores per Socket and then click 2.
c. In the navigation pane, select Reservation and then click 1200 MHz.
d. In the content pane, select Memory and then click 8 GB.
For a customer-provided OVA deployment, the minimum value allowed is 4 GB.
e. In the navigation pane, select, select Reservation and then click 8192 MB.
For a customer-provided OVA deployment, the minimum value allowed is 4,096 MB.

November 2024 Deploying Avaya Call Management System 26

Comments on this document?
 Configuring the virtual machine for different configuration sizes

f. Click OK.

Configuring the virtual machine as a medium configuration

About this task
Note:
Interfaces on different vSphere versions might differ.
Caution:
Do not change the resource settings, because any changes in the allocated resources can
impact the performance, capacity, and stability of the CMS virtual machine. To run at full
capacity, you must meet these resource size requirements. Removing or downsizing the
reserved space can put this requirement at risk. Any deviation in the requirements is at
customer’s own risk.
Important:
Avaya recommends that customers increase this storage space by 400 GB to provide 1,200
GB total disk space. Deviating from this recommendation is at the customer’s own risk.
Before you begin
Turn off the virtual machine.
Procedure
1. On your web browser, type the vSphere vCenter URL and press Enter.
2. In the User name field, enter your user name.
3. In the Password field, enter your password.
4. Click Login.
5. On the vSphere Web Client home page, select one of the following icons:
• Hosts and Clusters
• VMs and Templates
6. In the navigation pane, click CMS Virtual Machine.
7. Click Actions > Edit Settings.
8. In the Edit Settings dialog box, do the following:
a. In the navigation pane, select CPU and then click 8.
b. In the content pane, select Cores per Socket and then click 8.
c. In the navigation pane, select Reservation and then click 4800 MHz.
d. In the content pane, select Memory and then click 32 GB.
For a customer-provided OVA deployment, the minimum value allowed is 16 GB.
e. Select Reservation and then click 32,768 MB.
For a customer-provided OVA deployment, the minimum value allowed is 16,384 MB.

November 2024 Deploying Avaya Call Management System 27

Comments on this document?
Deploying CMS software using an OVA file

f. Click OK.
9. In the vSphere Web Client left pane, select the CMS virtual machine.
10. On the vSphere Client browser, click Actions and select Edit Settings.
The system displays the Edit Settings window.
11. In the Edit Settings window, click ADD NEW DEVICE.
The system displays a drop-down list.
12. From the drop-down list, select Hard Disk.
13. Select New Hard disk and click to expand.
14. Enter 400 in the Size field.
15. Click Disk Provisioning and select Thick Provision.

Important:
Customers that deploy an OVA on their own VMware systems can initially choose to
start with the minimum memory allocation, minimum memory reservation allocation,
and minimum disk space. However, to maintain support from Avaya, Avaya might
require you to later increase the memory allocations (to no more than the
recommended maximum value) if Avaya finds that problems related to memory usage
occur and cause failures on the CMS.
16. Select OK.

Configuring the virtual machine as a large configuration

About this task
Note:
Interfaces on different vSphere versions might differ.
Caution:
Do not change the resource settings, because any changes in the allocated resources can
impact the performance, capacity, and stability of the CMS virtual machine. To run at full
capacity, you must meet these resource size requirements. Removing or downsizing the
reserved space can put this requirement at risk. Any deviation in the requirements is at
customer’s own risk.
Important:
Avaya recommends that customers increase this storage space by 1,000 GB to provide 1,800
GB total disk space. Deviating from this recommendation is at the customer’s own risk.
Before you begin
Turn off the virtual machine.

November 2024 Deploying Avaya Call Management System 28

Comments on this document?
 Configuring the virtual machine for different configuration sizes

Procedure
1. On your web browser, type the vSphere vCenter URL and press Enter.
2. In the User name field, type your user name.
3. In the Password field, type your password.
4. Click Login.
5. On the vSphere Web Client home page, select one of the following icons:
• Hosts and Clusters
• VMs and Templates
6. In the navigation pane, click CMS Virtual Machine.
7. Click Actions > Edit Settings.
8. In the Edit Settings dialog box, do the following:
a. In the navigation pane, select CPU and then click 16.
b. In the content pane, select Cores per Socket that then click 16.
c. In the navigation pane, select Reservation and then click 9600 MHz.
d. In the content pane, select Memory and then click 64 GB.
For a customer-provided OVA deployment, the minimum value allowed is 16 GB.
e. Select Reservation and then click 65,536 MB.
For a customer-provided OVA deployment, the minimum value allowed is 16,384 MB.
f. Click OK.
9. In the vSphere Web Client left pane, select the CMS virtual machine.
10. On the vSphere Client browser, click Actions and select Edit Settings.
The system displays the Edit Settings window.
11. In the Edit Settings window, click ADD NEW DEVICE.
The system displays a drop-down list.
12. From the drop-down list, select Hard Disk.
13. Select New Hard disk and click to expand.
14. Enter 1000 in the Size field.
15. Click Disk Provisioning and select Thick Provision.

Important:
Customers that deploy an OVA on their own VMware systems can initially choose to
start with the minimum memory allocation, minimum memory reservation allocation,
and minimum disk space. However, to maintain support from Avaya, Avaya might
require you to later increase the memory allocations (to no more than the

November 2024 Deploying Avaya Call Management System 29

Comments on this document?
Deploying CMS software using an OVA file

recommended maximum value) if Avaya finds that problems related to memory usage
occur and cause failures on the CMS.
16. Select OK.

November 2024 Deploying Avaya Call Management System 30

Comments on this document?
Chapter 4: Deploying the CMS KVM

This section of the document covers the processes for deploying the CMS server as a new KVM
virtual machine on an Avaya ASP 130 R6 server.
Note:
• For the ASP 130 R6 you cannot use Solution Deployment Manager for the installation of
CMS KVM images, Feature Packs, Service Packs, Patches, and Hot fixes. You must follow
the CLI instructions for installation of those artifacts.
Related links
Planning checklist for CMS KVM deployment on page 31
Activating the license for a CMS server on page 18
Installing a license file on a WebLM server on page 19
Downloading software from PLDS on page 20
Preparing the CMS KVM file on page 36
Importing the CMS virtual machine on page 37

Planning checklist for CMS KVM deployment

Ensure that the customer completes the following before deploying the Avaya application KVM
images on Avaya-supplied ASP 130 R6.
No. Task Notes

1. Check the hardware platform For ASP 130 R6, A1SC configurator output should
be utilized to determine which applications are to be
deployed on which server/host.
2. Activate the license for the CMS –
server.
3. Install the license file on the –
WebLM server.
4. Download the latest CMS The deployment process for Feature Packs, Service
software Packs, patches, and hot-fixes is the same regardless
of the underlying hypervisor.
Table continues…

November 2024 Deploying Avaya Call Management System 31

Comments on this document?
Deploying the CMS KVM

No. Task Notes

5. Plan the staging and verification This must include network topology, IP addressing,
activities and assign the naming conventions, and application specific
resources configuration and administration.
6. Purchase the appropriate order Reach out to the Avaya account team for detailed
codes information on ordering ASP 130 R6.
Note that with the introduction of ASP 130 R6, there
is no longer a license key present on the server.
However, it is imperative that customers have a record
in PLDS for each instance of the ASP 130 R6 server
as customers and Avaya are subject to audits to
ensure right to use royalties have been paid.
7. Read the Avaya server Navigate to https://support.avaya.com and search for
documentation Avaya Solutions Platform, Release ASP 130 R6.
8. Download the latest CMS Reference the CMS R21 Release Notes, Product
software Correction Notices, and software downloads for
specific PLDS IDs links to the CMS KVM images.
The deployment process for Feature Packs, Service
Packs, patches, and hot-fixes is the same regardless
of the underlying hypervisor.

Related links
Deploying the CMS KVM on page 31

Activating the license for a CMS server

About this task
Important:
Each CMS deployment must have its own license file on a WebLM Release 8.0 or later server
and must use Centralized Licensing. Enterprise licensing is not supported for CMS. That is,
multiple CMS deployments cannot share one license file.
Before you begin
Get the following information:
• SAP order number
• WebLM server host ID
Note:
The SAP order number and the WebLM server host ID must be listed under the same
Company ID.

November 2024 Deploying Avaya Call Management System 32

Comments on this document?
 Activating the license for a CMS server

Procedure
1. In a browser window, navigate to the PLDS site:
https://plds.avaya.com
2. Log on to PLDS using your customer ID and password.
3. Navigate to Assets > View Entitlements.
PLDS displays the Search Entitlements screen.
4. Search for your license entitlement using one of the following criteria:
• SAP order number
• Sold to number
• License activation code
You can also use Advanced Search to find a license entitlement.
5. Click Search Entitlements.
PLDS displays the known license entitlements based on the search criteria.
6. For the customer’s entitlement record, click Options > Activate.
PLDS displays a list of possible entitlements.
7. Select the entitlement for CMS release for which you are installing or upgrading.
8. Click Activate.
PLDS displays the Search License Hosts screen. The available license hosts for the
Company ID are displayed on this screen.

Note:
You can also download a license file and install the file manually. For more information,
see Installing a license file on a WebLM server on page 19.
9. Select one of the displayed license hosts or create a new host by clicking Add a License
Host.
10. Click Next.
PLDS displays a registration summary screen.
11. Click Next.
PLDS displays the Activate Entitlements screen.
12. Select the quantity of each entitlement you want to activate.
13. Click Next.
14. Add notes for the activation, if needed.
15. Click Finish.

November 2024 Deploying Avaya Call Management System 33

Comments on this document?
Deploying the CMS KVM

Related links
Deploying the CMS KVM on page 31

Installing a license file on a WebLM server

About this task
Avaya products use WebLM Release 8.0 or later to manage product licenses obtained through
PLDS. For CMS licensing, use either a standalone WebLM server or install the WebLM server on
a coresident Avaya Aura® System Manager. Licenses installed for WebLM must support SHA256
digital signatures and a 14-character host ID.
Important:
Use Centralized licensing for CMS. Enterprise licensing is not supported. This means that
multiple CMS deployments cannot share one license file. After enabling Centralized licensing,
you must assign every license file to the license ID in WebLM.
For more information about installing license files, see the following documents:
• Administering Avaya Aura® System Manager
• Administering standalone Avaya WebLM
Before you begin
Ensure that the XML license file is present in the computer.
Use the uninstall functionality of WebLM to remove any existing license file from the WebLM
server before you install a new license file. The system displays an error message if an older
license file is still available. For a centralized license file, the system automatically overwrites the
older license file during installation. If you experience problems while installing the license file, see
the information about license file installation errors in Administering standalone Avaya WebLM.
Procedure
1. Log in to the standalone WebLM web console or the System Manager console with
administrator privilege credentials.
2. In the navigation pane, click Install license.
3. On the Install license page, click Choose File and browse to the directory of the XML
license file that you saved on your computer.
4. Read the terms and conditions and click Accept the License Terms & Conditions.
5. Click Install.
WebLM displays a message on successful installation of the license file. The installation
of the license file might fail for various reasons. For example, the digital signature on the
license file is invalid. If you get such an error, request PLDS to redeliver the license file.
An error can also occur if the current capacity use exceeds the capacity in the installed
license.

November 2024 Deploying Avaya Call Management System 34

Comments on this document?
 Downloading software from PLDS

6. Enable Centralized licensing as described in WebLM documentation.

With Centralized licensing, you must assign every license file to the license ID in WebLM.
7. Click New.
8. Enter a name to assign to the CMS.
9. Select the license file to associate with the CMS.
Related links
Deploying the CMS KVM on page 31

Downloading software from PLDS

Procedure
1. On your web browser, type http://plds.avaya.com to access the Avaya PLDS website.
2. Enter your login ID and password.
3. On the PLDS Home page, select Assets.
4. Click View Downloads.

5. Click the search icon for Company Name.

6. In the Search Companies dialog box, do the following:
a. In the %Name field, type Avaya or the Partner company name.
b. Click Search Companies.
c. Locate the correct entry and click the Select link.
7. Search for the available downloads by using one of the following:
• In Download Pub ID, type the download pub ID.
• In the Application field, click the application name.
8. Click Search Downloads.
9. In the Download Manager box, click the appropriate Download link.

Note:
The first link, Click to download your file now, uses the Download Manager to
download the file. The Download Manager provides features to manage the download
(stop, resume, auto checksum). The click here link uses your standard browser
download and does not provide the download integrity features.
10. If you use the Download Manager, click Details to view the download progress.
11. Select a location where you want to save the file, and click Save.
12. (Optional) When the system displays the security warning, click Install.

November 2024 Deploying Avaya Call Management System 35

Comments on this document?
Deploying the CMS KVM

When the installation is complete, PLDS displays the downloads again with a check mark
next to the downloads that have completed successfully.
Related links
Deploying the CMS KVM on page 31

Preparing the CMS KVM file

About this task
Avaya supplies the KVM files as an KVM OVA file. That file contains a .qcow2 file you can use to
create a CMS virtual machine.
Before you begin
• Download the CMS KVM OVA file from Avaya PLDS. For example, CMS-R21.0.0.1.ab.b-
kvm-e810-00-1.ova.
Procedure
1. Login to KVM CLI as the custadm user.
2. Run sudo ls -ld /var/lib/libvirt/staging.
3. Check that the directory /var/lib/libvirt/staging is listed.
• If the directory does not exist, create it by running the following commands:
sudo mkdir /var/lib/libvirt/staging
sudo chown custadm:wheel /var/lib/libvirt/staging

4. Check that the directory permissions shown as match drwxr-x---.

• If the permissions do not match, change them using the following command. This allows
custadm to write into the directory folder using sudo commands.
• sudo chown custadm:wheel /var/lib/libvirt/staging
5. Verify there is sufficient free-space to copy the size of the KVM image. There needs to be a
minimum of 800 GB free space.
6. Copy the downloaded CMS-R21.0.0.1.ab.b-kvm-e810-00-1.ova file into
the /var/lib/libvirt/staging directory.
7. Extract the contents of the ova using the command:
tar -xvf CMS-R21.0.0.1.ab.b-kvm-e810-00-1.ova
This extracts the following files
• CMS-R21.0.0.1.ab.b-kvm.ovf
• CMS-R21.0.0.1.ab.b-kvm.mf
• CMS-R21.0.0.1.ab.b-kvm-1.qcow2

November 2024 Deploying Avaya Call Management System 36

Comments on this document?
 Importing the CMS virtual machine

8. The .qcow2 file is in thin provisioning format. To create a copy that is thick provisioned file,
run the command:
sudo qemu-img convert -O qcow2 -o preallocation=full CMS-
R21.0.0.1.ab.b-kvm-1.qcow2 CMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2
9. Verify that the thick provision copy is 800 GB by running the command:
sudo qemu-img info CMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2
10. Move the thick provisioned file image to the virtual machine images directory:
sudo mv -i CMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2 /var/lib/libvirt/
images
11. Change the file owner and file permission by running following commands:
sudo chown qemu:qemu /var/lib/libvirt/imagesCMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2
sudo chmod 640 /var/lib/libvirt/images/CMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2

12. You can now delete the downloaded CMS-R21.0.0.1.ab.b-kvm-e810-00-1.ova file

and extracted files from the /var/lib/libvirt/staging folder.
Next steps
• You can now use the KVM image file to create a CMS virtual machine. See Importing the
CMS virtual machine on page 37.
Related links
Deploying the CMS KVM on page 31

Importing the CMS virtual machine

About this task
Use this process to use the .qcow2 file as the virtual drive for a new CMS virtual machine.
Before you begin
• Prepare the CMS .qcow2 disk image. See Preparing the CMS KVM file on page 36.
Procedure
1. Login to the KVM web console in the following format: https://<IP address or FQDN
of KVM host>:9090
• Use the same credentials that you used to access the KVM host by SSH.
• If your web console session shows “Limited Access”, click Turn on administrative
access. This is equivalent to using sudo and web console may prompt you for your
credentials.
2. Navigate to System > Virtual machines > Import VM.
3. In the Name field, enter a name for the CMS virtual machine.

November 2024 Deploying Avaya Call Management System 37

Comments on this document?
Deploying the CMS KVM

4. In the Disk Image field, enter /var/lib/libvirt/images and select the CMS-
R21.0.0.1.ab.b-kvm-1-THICK.qcow2 image.
5. In the Operating system field, select RHEL 8.10.
6. In the Memory field, select the required memory in MB format.
• For more information on footprints, see Virtual machine resource requirements and
average utilization on page 12.
7. Click Import and edit.
8. Under the Disks section:,
a. Check that the CMS-R21.0.0.1.ab.b-kvm-1-THICK.qcow2 image disk image
size is correctly displayed in the Capacity field.
b. Click Edit.
c. In the Bus field select scsi.
d. In the Cache field select directsync.
e. Click Save.
9. In the Firmware field, select BIOS and click Save.
10. In the CPU field, click edit.
a. Increase the values in the vCPU Maximum and vCPU Count fields to match
the footprint requirement (see Virtual machine resource requirements and average
utilization on page 12). Set the same value in each field.
b. Click Apply.
11. In the Networking section:
a. Click on Edit.
b. Select the required Network Bridge and click Save.
12. On the virtual machine, click Run to start the CMS virtual machine.
Related links
Deploying the CMS KVM on page 31

November 2024 Deploying Avaya Call Management System 38

Comments on this document?
Chapter 5: Configuring system features

Following deployment of a new CMS virtual machine, use the processes in this section of the
documentation to start and initially configure CMS.
Related links
Configuring system features checklist on page 39
Verifying that CMS is installed on page 40
Initializing the CMS database on page 40
Setting the root password on page 41
Configuring the system network on page 42
Configuring WebLM, EASG, and the encryption passphrase on page 45
Installing CMS patches on page 47
Updating Linux RPMs on page 47
Running the CMS security script on page 48
Turning on IDS and adding disk space for medium and large configurations on page 48
Verifying system startup and remote access on page 49

Configuring system features checklist

No Task Procedure reference

1. Verify that CMS is installed by Verifying that CMS is installed on page 40

checking the version
2 Initialize the CMS database See Initializing the CMS database on page 40.
3. Set the root password. Setting the root password on page 41
4. Configure the system network. Configuring the system network on page 42
5. Configure WebLM, EASG, and Configuring WebLM, EASG, and the encryption
initial encryption passphrase rules. passphrase on page 45
6. Install any CMS patches that apply Installing CMS patches on page 47
to the CMS release.
7. Update the Linux RPMs for your Updating Linux RPMs on page 47
CMS release, if required.
Table continues…

November 2024 Deploying Avaya Call Management System 39

Comments on this document?
Configuring system features

No Task Procedure reference

8. Turn on IDS and initialize Informix. Turning on IDS and adding disk space for medium and
large configurations on page 48
9. Verify that the CMS system starts Verifying system startup and remote access on
up properly and that you can page 49
access it remotely.
10. Proceed to configuring CMS See Configuring CMS features checklist on page 51.
features.

Related links
Configuring system features on page 39

Verifying that CMS is installed

About this task
Use this process to check the installed CMS version.
Procedure
1. Using the hypervisor console for the CMS virtual machine, log in as root. At this point, no
password has been set.
2. Enter the following command:
rpm -qa cms
3. Confirm that the displayed version matches the expected CMS version.
Related links
Configuring system features on page 39

Initializing the CMS database

About this task
After installing the CMS virtual machine, you need to use this procedure to initialize the CMS
database.
Procedure
1. Login to the administrator interface for the hypervisor platform.
2. If not already active, open the vSphere client software.
3. Log on to the vSphere client.

November 2024 Deploying Avaya Call Management System 40

Comments on this document?
 Setting the root password

4. Locate the CMS virtual machine and select the Console.

5. The system displays the Red Hat Linux login window. Click your cursor in the console
window and press Enter.
6. Log on as root. Initially, no password exists. The system displays the Linux desktop.
7. Right-click your cursor on the Linux desktop.
8. Select Konsole. The system displays a console terminal window.
9. Perform the following to initialize the CMS database:
a. To set the Informix environment, enter . /opt/informix/bin/setenv
b. To initialize the CMS database, enter /opt/informix/bin/dbinit.sh
c. When prompted to confirm, enter y
10. Access the CMS Services Menu by entering cmssvc.
• The system displays the CMS Services Menu, which verifies that the Red Hat Linux and
CMS software is successfully deployed. You do not have to run any other CMS Services
commands.
11. Exit bye CMS Services Menu by entering q.
Related links
Configuring system features on page 39

Setting the root password

About this task
You must create a password for the root user ID. Record this password for when you turn the
system over to the customer.
Security alert:
Remind the customer to change and record the root password after the system is turned over
to them.
Procedure
1. Log on as root. You are not prompted for a password.
2. Enter the following command to assign a password to the root user ID:
passwd root
The system displays the following message:
Changing password for user root.
New password:

3. Enter the new password for the root user ID.

November 2024 Deploying Avaya Call Management System 41

Comments on this document?
Configuring system features

The system displays the following message:

Retype new password:

4. Enter the new password for the root user ID a second time.
The system displays the following message:
passwd: all authentication tokens updated successfully.

Related links
Configuring system features on page 39

Configuring the system network

About this task
This procedure shows example default entries and variables as <variable>. The actual
information you enter must match your network setup.
Note:
This procedure describes how to configure the system network using IPv4. To configure IPv6
support, see the chapter “Installing and configuring optional software” in Maintaining and
Troubleshooting Avaya Call Management System.
Procedure
1. Log on to Linux as a root user.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
2. Enter the following command:
/cms/toolsbin/netconfig
The system displays the following prompt:

WARNING: This tool only supports IPv4

Enter the network interface name from following name(s): eth0 eth1 eth2 eth3
(default <ethX>)

ENTER>

3. Accept the default value eth0 and press Enter.

The system displays the following prompt:
You have entered [ eth0 ]. Is this correct? (y|n)

4. Enter y, then press Enter.

November 2024 Deploying Avaya Call Management System 42

Comments on this document?
 Configuring the system network

The system displays the following prompt:

Enter the host name of the CMS system (default <cms_hostname>)

ENTER>

5. Enter the host name of the CMS server and press Enter.
Hostname for the CMS server

Important:
The CMS backup process automatically assigns time-stamped file names that truncate
the CMS server hostname if it is longer than 15 characters. To avoid confusion
between the backup files for multiple CMS servers, do not use the same first 15
characters for a hostname when you have multiple CMS servers in your deployment.
The system displays the following prompt:
You have entered [ <cms_hostname> ]. Is this correct? (y|n)

6. If you have entered the correct host name, enter y, then press Enter.
The system displays the following prompt:
Enter the domain name of the CMS system (default <cms.domain.com>)

ENTER>

7. Enter the domain name of the CMS server and press Enter.
The system displays the following prompt:
You have entered [ <cms.domain.com> ]. Is this correct? (y|n)

8. If you have entered the correct domain name, enter y, then press Enter.
The system displays the following prompt:
Enter the IP address of the network interface (default <IP_address>)

ENTER>

9. Enter the IP address of the CMS server network interface and press Enter.
The system displays the following prompt:
You have entered [ <IP_address> ]. Is this correct? (y|n)

10. If you entered the correct IP address, enter y, then press Enter.
The system displays the following prompt:
Enter the netmask for the subnet of the network interface (default <netmask_IP>)

ENTER>

11. Enter the netmask for the subnet of the CMS server network interface and press Enter.
The system displays the following prompt:
You have entered [ <netmask_IP> ]. Is this correct? (y|n)

12. If you entered the correct IP address, enter y, then press Enter.

November 2024 Deploying Avaya Call Management System 43

Comments on this document?
Configuring system features

The system displays the following prompt:

Enter the gateway of the CMS system (default <Gateway_IP>)

ENTER>

13. Enter the gateway for the CMS server network interface and press Enter.
The system displays the following prompt:
You have entered [ <Gateway_IP> ]. Is this correct? (y|n)

14. If you entered the correct default gateway, enter y, then press Enter.
The system displays the following prompt:
Enter the DNS server(s) seperated by space (up to three servers) (default
<Maximum_Three_DNS_Servers_IP>)

ENTER>

15. Enter the DNS servers of the CMS server and press Enter.
The system displays the following prompt:
You have entered [ <Maximum_Three_DNS_Servers_IP> ]. Is this correct? (y|n)

16. If you entered the correct DNS server(s), enter y, then press Enter.
The system displays the following prompt:
Enter the search domains separated by space (default <Search_Domains>, "" for
none)

ENTER>

17. Enter the search domain(s) of the CMS server and press Enter.
The system displays the following prompt:
You have entered [ <Search_Domains> ]. Is this correct? (y|n)

18. If you entered the correct search domains, enter y, then press Enter.
The system displays the network configuration options you have entered, for example:
Interface: eth0
CMS Hostname: cmshostname
Domainname: tmp.domain.com
CMS IP address: 10.10.10.10
Netmask: 255.255.255.0
Gateway: 10.20.30.40
DNS Server1: 40.30.20.10
DNS Server2: 100.200.300.400
DNS Server3:
Search domains: tmp.domain1.com tmp.domain2.com

Are the above inputs correct? (y|n)

19. Perform one of the following actions:

• If any of the network configuration entries are not correct, enter n, then press Enter.
The network configuration process returns to step 3.
• If the network configuration entries are correct, enter y, then press Enter.

November 2024 Deploying Avaya Call Management System 44

Comments on this document?
 Disk encryption

The system attempts to bring up the network and if successful, displays a successfully
finished message.
Bring the network up. Please wait...

<timestamp> /cms/toolsbin/netconfig successfully finished

20. If the network configuration was not successful, troubleshoot the network for outages and
repeat this procedure. If the network configuration fails again, escalate through normal
channels. Test your network settings to ensure that the network settings are working
properly using the following commands:
ifconfig <ethX> (use your actual Ethernet port)
ping <system on your local network>
Press Control+C to exit the ping command.

Note:
If the network does not respond, enter ifup <ethX>. If the network still does not
respond, repeat this procedure and verify that the values entered are correct.

Disk encryption
By default, CMS no longer encrypts disks and partitions with CMS data using LUKS encryption.
This encryption is generally redundant because supported cloud providers encrypt by default and
VMware supports disk encryption natively.

Configuring WebLM, EASG, and the encryption

passphrase
About this task
When you run the cmssvc command for the first time after deploying CMS, you are prompted to
provide licensing information and set up other key functionality.
WebLM licensing: You must provide a valid hostname to the WebLM server where the CMS
license is installed. You can use a standalone WebLM server or a System Manager server for
licensing. For information about WebLM licensing modes, see Avaya Call Management System
Overview and Specification.
Enhanced Access Security Gateway (EASG): You can enable or disable EASG. When
enabled, EASG enables service engineers to access CMS for troubleshooting purposes. EASG
supports permission levels such as init, inads, and craft.
Encryption: Disk encryption is implemented on all CMS data partitions. Decide whether to
require an encryption passphrase after each shutdown or reboot. This includes shutdowns for

November 2024 Deploying Avaya Call Management System 45

Comments on this document?
Configuring system features

administrative or maintenance procedures such as turning FIPS on and off, CMSADM restore,
LAN restore, RPM update, software upgrades, and regular maintenance reboots. It also includes
unplanned shutdowns such as a system crash.
Before you begin
• After deploying CMS, set up the root password.
• Log in to the CMS server with root privileges.
Procedure
1. Run the cmssvc command for the first time after deploying CMS.
When you run this command for the first time, a message such as the following is
displayed:
cmssvc: Warning IDS off-line. It will take approx 45 seconds to
start cmssvc. IDS can be turned on with the run_ids command on
the cmssvc menu.
You are required to set the WebLM server before proceeding.

Please enter the hostname for the WebLM license server.

If you do not have a WebLM license server, enter <CR>:

2. Enter the hostname or IP address of the WebLM server where the CMS license is installed.
3. Press Enter.
If the information you entered is incorrect, you are prompted to enter another hostname.
After entering a valid hostname or IP address, proceed to the next step.
4. When prompted, enter the CMS server license ID.
This is an ID created when the license is installed on the WebLM server.
5. Press Enter.
A message such as the following is displayed:
Web hostname is now authorized as https://<Host_Name or IP_Address>:<Port_Number>/
WebLM/LicenseServer.

EASG User Access

By enabling Avaya Logins you are granting Avaya access to

your system. This is necessary to maximize the performance
and value of your Avaya support entitlements, allowing Avaya
to resolve product issues in a timely manner.

In addition to enabling the Avaya Logins, this product should

be registered with Avaya and technically onboarded for remote
connectivity and alarming. Please see the Avaya support site
(support.avaya.com/registration) for additional information for
registering products and establishing remote access and alarming.

Would you like to enable Avaya EASG? (Recommended)

[yes/no]:

6. Do one of the following:

• Enter yes to enable EASG. This is the recommended setting.

November 2024 Deploying Avaya Call Management System 46

Comments on this document?
 Installing CMS patches

• Enter no to keep EASG in the disabled state.

Tip:
If you do not enable EASG now, you can use the cmssvc command to enable it
later.
The message displayed confirms whether EASG is enabled and it indicates that disk
encryption is implemented. You are prompted to choose an option for the encryption
passphrase.
7. Choose one of the following options for the encryption passphrase:
• Enter 1 to require users to manually enter the encryption passphrase on the system
console after every shutdown or reboot.
• Enter 2 to enable auto-unlocking through a CMS-generated local key file. If you select
this option, CMS starts up without an encryption passphrase.
Related links
Configuring system features on page 39

Installing CMS patches

About this task
After installing CMS for the first time, download the latest CMS patches and install them on the
system. For procedure on installing CMS patches, see Maintaining and Troubleshooting Avaya
Call Management System.

Updating Linux RPMs

Avaya provides updated Linux RPMs with new CMS releases, be it a major, minor, feature pack,
or service pack release. When you install or upgrade to the new release, you follow a procedure to
manually update the Linux RPMs.
It is important to update the Linux RPM packages because the updates might contain new Linux
operating system updates for security and system operation. Avaya provides the Linux RPM
updates on the CMS ISO image used for upgrades.
Avaya also releases RPM updates outside of normal CMS releases. In this case, a PSN describes
how to update a CMS release with a new set of Linux RPMs. This PSN will contain specific update
instructions for specific CMS releases. Check the Avaya Support site to see if there are any new
Linux RPM updates for your release of CMS.
Related links
Configuring system features on page 39

November 2024 Deploying Avaya Call Management System 47

Comments on this document?
Configuring system features

Running the CMS security script

About this task
As part of installing or upgrading CMS software, you must install the CMS security options
using the cms_sec security script. The security script must be run after you have updated the
RHEL RPMs. You can run the security script at any time, but any customer customizations are
overwritten.
Procedure
1. Ensure that you are logged in to CMS with root privileges.
2. Run the following security script command to configure your security settings:
/storage/cms_dvd/security/cms_sec

Related links
Configuring system features on page 39

Turning on IDS and adding disk space for medium and

large configurations
Procedure
1. Log on as root.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
2. Enter:
cmssvc
The system displays the following menu:
Avaya(TM) Call Management System Services Menu

Select a command from the list below.

1) auth_display Display feature authorizations
2) weblm_set Set up the connection to the WebLM
3) run_ids Turn Informix Database on or off
4) run_cms Turn Avaya CMS on or off
5) setup Set up the initial configuration
6) swinfo Display switch information
7) swsetup Change switch information
8) uninstall Remove the CMS rpm from the machine
9) patch_rmv Backout an installed CMS patch
10) back_all Backout all installed CMS patches from machine
11) security Administer CMS security features
Enter choice (1-11) or q to quit:

3. Choose the run_ids option to turn on the Informix Database Server.

November 2024 Deploying Avaya Call Management System 48

Comments on this document?
 Verifying system startup and remote access

The system displays the following menu:

Select one of the following
1) Turn on IDS
2) Turn off IDS
Enter choice (1-2):

4. Choose the Turn on IDS option.

5. For a medium or large configuration, type the following command to add disk space:
/opt/informix/bin/dbinit.sh add_disks

Important:
Do not run this command on a small configuration.
Verify that the disk space was added successfully. If the procedure fails, contact Avaya
support.
Related links
Configuring system features on page 39

Verifying system startup and remote access

About this task
After you configure the system features, use this task to verify that the system starts up properly
and that you can access the system remotely.
Before you begin
If the default passphrases have been changed, get those new passphrases.
Procedure
1. Reboot the system using the following command:
shutdown –r now
The remote console displays the reboot sequence. If you did not configure encryption
auto-unlocking, the system displays the following message:
Please enter passphrase for disk Virtual_disk (/cms)!:

2. Enter a default or new encryption passphrase.

You can choose from either of the following default encryption passphrases:
• cmsdefault
• cmssvcdefault
The system displays the Linux login prompt.
3. Log on to Linux as root.

November 2024 Deploying Avaya Call Management System 49

Comments on this document?
Configuring system features

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
4. From another system, verify that you can access the new system using tools such as
puTTY or SSH.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
Related links
Configuring system features on page 39

November 2024 Deploying Avaya Call Management System 50

Comments on this document?
Chapter 6: Configuring CMS features

Configuring CMS features checklist

No. Task Notes

1. Assign passwords for the CMS Assigning passwords to the default CMS login IDs on
login IDs. page 51
2. View the CMS authorizations to Viewing CMS authorizations on page 52
confirm that your licensed features
are authorized.
3. Activate the Supervisor web client. Activating the CMS Supervisor Web Client software on
page 52
4. Calculate storage requirements for Calculating data space requirements for CMSADM
backups. backups on page 56
Calculating data space requirements for CMS full
maintenance backups on page 57
5. Set up the Alarm Origination Setting up the Alarm Origination Manager on
Manager to report alarms to Avaya page 58
support or customer management
systems.

Assigning passwords to the default CMS login IDs

Procedure
1. To assign a password for the cms login ID, enter: passwd cms
The system displays the following message:
New password:

2. Enter the password for the cms login ID.

The system displays the following message:
Re-enter new password:

3. Enter the password for the cms login ID a second time.

November 2024 Deploying Avaya Call Management System 51

Comments on this document?
Configuring CMS features

The system displays the following message:

passwd: password successfully changed for cms

4. To assign a password for the cmssvc login ID, enter: passwd cmssvc
The system displays the following message:
New password

5. Enter the password for the cmssvc login ID.

The system displays the following message:
Re-enter new password

6. Enter the password for the cmssvc login ID a second time.

The system displays the following message:
passwd: password successfully changed for cmssvc

Viewing CMS authorizations

About this task
This section describes how to view CMS capacities authorized based on the license file and the
status of CMS optional feature packages and security settings.
Procedure
1. Enter: cmssvc
The system then displays the Avaya Call Management System Services menu.
2. Enter the number associated with the auth_display option.

Activating the CMS Supervisor Web Client software

The CMS Supervisor Web Client software is installed on the same server as the CMS software.
The Web Client is browser-based and enables customers to access CMS administration and
reports without install client software on your PC. For more information, see Avaya Call
Management System Overview and Specification and Avaya CMS Supervisor Clients Installation
and Getting Started.
Related links
Managing certificates for Web Client software on page 53
Installing the root certificate and any intermediate certificate for the Web Client software on
page 54

November 2024 Deploying Avaya Call Management System 52

Comments on this document?
 Activating the CMS Supervisor Web Client software

Installing the root certificate and any intermediate certificate for the Web Client software on
page 55
Starting the Web Client software on page 56

Managing certificates for Web Client software

About this task
To encrypt communication between browsers and the Web client CMS server you must install a
security certificate. Use the following procedure to obtain a signed security certificate.
Procedure
1. Log on as root on the CMS server.

Important:
• You cannot directly log on as root from a remote connection. You must log on using
an administered CMS user ID, then use su - root to log on with root privileges.
2. To create and move to a temporary work directory, use the following commands:
mkdir /opt/cmsweb/cert/custom
cd /opt/cmsweb/cert/custom
3. To generate a private key, use the following command:
keytool -genkey -alias cmsweb1
-keyalg RSA -keysize 2048
-keystore cmsweb.p12
-dname "CN=[fqdn],OU=CMS,O=Avaya,L=Thornton,ST=Colorado,C=US"
-ext "SAN=IP:[ip],DNS:[fqdn]"

• In the -dname part, replace the [fqdn] with the FQDN for CMS.
• In the -ext part, replace the [fqdn] and [ip] with the values for CMS.
• The -alias value must be cmsweb1 as shown.
• The -keystore value must be cmsweb.p12 as show.
• All other values (-keyalg, -kesize) must be as shown.
4. Enter the keystore password: cmsweb.
5. To generate a Certificate Signing Request (CSR), enter:
keytool -certreq -keyalg RSA -alias cmsweb1 -file cmsweb.csr
-keystore cmsweb.p12
6. To obtain a signed certificate, submit the CSR to the Certificate Authority (CA) using your
organization's regular certificate signing procedure.
• You can use the Avaya System Manager CA function to sign the certificate.
7. Obtain a copy of the root certificate of the CA used in the previous step. For example,
<CARootCert>.pem.

November 2024 Deploying Avaya Call Management System 53

Comments on this document?
Configuring CMS features

8. If the CA also uses intermediate certificates, obtain copies of those certificates.

9. Copy the signed certificate to /opt/cmsweb/cert/custom directory.
10. To import the signed certificate, enter:
keytool -import -alias cmsweb1 -keystore cmsweb.p12 -file
<SignedCert>.pem
11. To copy the keystore containing the certificate to the CMS Web location, enter:
cp cmsweb.p12 /opt/cmsweb/cert/cmsweb.p12
12. To restart the Web client on the CMS server, enter:
cmsweb stop
cmsweb start
Next steps
• You need to install the CA root certificate, and any intermediate certificates. See Installing the
root certificate and any intermediate certificate for the Web Client software on page 54.
Related links
Activating the CMS Supervisor Web Client software on page 52

Installing the root certificate and any intermediate certificate for

the Web Client software
About this task
You can use this process to install a copy of the root certificate obtained from the Certificate
Authority (CA) that you used to sign the CMS security certificate.
If the CA issued any intermediate certificate, you must also import those intermediate CA
certificates.
Procedure
1. Copy and paste the root certificate into a file. For example, <CARootCert>.pem.
2. To import the certificate: , enter:
a. Enter:
keytool -import -alias root -keystore cmsweb.p12 -trustcacerts
-file <CARootCert>.pem
b. For the password, enter cmsweb.
3. If the CA also requires intermediate certificates:
a. Copy and paste the intermediate certificate into a file, for example,
intermediate.cert.
b. To import the certificate, enter:

November 2024 Deploying Avaya Call Management System 54

Comments on this document?
 Activating the CMS Supervisor Web Client software

keytool -import -alias intermediate -keystore cmsweb.p12

-trustcacerts -file intermediate.cert
c. For the password, enter cmsweb.
4. Copy and paste the new certificate into a file, for example, cmsweb.cert.
5. To import the certificate, enter:
keytool -import -alias cmsweb -keystore cmsweb.p12 -trustcacerts
-file cmsweb.cert
6. For the password, enter cmsweb.
7. To stop the Web Client software, enter:
cmsweb stop
8. Copy the keystore to the correct location, for example:
cp /opt/cmsweb/cert/custom/cmsweb.p12 /opt/cmsweb/cert
9. To restart the Web Client software, enter:
cmsweb start
Next steps
• Configure the browser to trust the CA. See Installing the root certificate and any intermediate
certificate for the Web Client software on page 55.

Installing the root certificate and any intermediate certificate for

the Web Client software
About this task
Ensure that your browser is configured to trust the CA. If your organization does not automatically
configure this setting, you can manually configure the settings for your browser. You can use the
process below for

Procedure
1. If using Google Chrome or Microsoft Edge:
a. Open the browser.
b. Navigate to Settings > Privacy and security > Security > Manage device
certificates.
c. On the Certificates window, click the Trusted Root Certification Authorities tab.
d. In the list of certificates, select the CA root certificate and click Import.
2. For Mozilla Firefox:
a. Import the CA to the Firefox certificate store. If you use Windows, you can open the
command line cmd.exe using the Run as Administrator option.

November 2024 Deploying Avaya Call Management System 55

Comments on this document?
Configuring CMS features

b. At the command line, you can use the following command:

certutil -addstore -enterprise -f "Root" <CARootCert>.pem
Related links
Activating the CMS Supervisor Web Client software on page 52

Starting the Web Client software

Procedure
1. Log on as root on the CMS server.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
2. Enter the following command to start the Web Client software:
cmsweb start
The system displays the following message:
starting cmsweb...

3. Enter the following command to verify that the correct version of the Web Client software is
installed:
rpm –q cmsweb
The system displays a message similar to the following example:
cmsweb-R{XX}-web{XX}xx.x.x

The {XX} in this message is the release version.

Storage requirements for CMS backups

Calculating data space requirements for CMSADM backups
About this task
The command described in this procedure provides a snapshot of the current CMS disk space
usage. Run additional checks periodically to see if your storage needs have changed to ensure
you have enough backup space.
Procedure
1. Log in to the CMS command line interface with root privileges.
2. Run df -Th to get a snapshot of the current disk space usage on the CMS server.

November 2024 Deploying Avaya Call Management System 56

Comments on this document?
 Storage requirements for CMS backups

Information such as the following is displayed:

Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs tmpfs 7.7G 4.0K 7.7G 1% /dev/shm
tmpfs tmpfs 7.7G 105M 7.6G 2% /run
tmpfs tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/sda2 ext4 9.8G 2.4G 6.9G 26% /
/dev/sda12 ext4 16G 540M 15G 4% /tmp
/dev/sda8 ext4 2.9G 268M 2.5G 10% /var
/dev/sda1 ext4 545M 187M 319M 37% /boot
/dev/sda13 ext4 12G 1.1G 11G 10% /opt
/dev/sda3 ext4 9.8G 971M 8.3G 11% /cms
/dev/sda7 ext4 32G 96K 30G 1% /export/home
/dev/sda9 ext4 2.0G 36K 1.9G 1% /var/tmp
/dev/sda10 ext4 2.0G 22M 1.8G 2% /var/log
/dev/sda6 ext4 86G 5.5G 77G 7% /storage
/dev/sda11 ext4 9.8G 4.5M 9.3G 1% /var/log/audit
tmpfs tmpfs 1.6G 0 1.6G 0% /run/user/0

3. Add the disk space from the Used column for all ext4 file systems, except for the /
storage and /tmp directories.
4. Calculate the space you need.
The example in the following table shows the used space for the relevant ext4 file system
directories:

Directory Used space

/ 1.6 GB
/boot 106 MB
/var 240 MB
/export/home 49 MB
/opt 1.8 GB
/cms 354 MB
Total: 4.15 GB

Calculating data space requirements for CMS full maintenance

backups
Procedure
1. Log on to Linux as root.

Important:
• If using a remote connection, you cannot directly log on as root. Instead, log on
using an administered CMS user ID and then then use su - root to log on with
root privileges.
2. Run the following command to set the Informix environment: ./opt/informix/bin/
setenv

November 2024 Deploying Avaya Call Management System 57

Comments on this document?
Configuring CMS features

3. Run onstat -d
4. Use the output generated from running this command to estimate how much database
space is required for a CMS full maintenance backup. The data in this table is dynamic and
changes as database space is used.

Note:
• Bytes to GB conversion factor = 1,073,741,824.
• Full Maintenance Backup compression ratio = 30 (approximation). The onstat -d
command gives a current snapshot of disk space usage of the CMS server.
• You must run additional checks periodically to see if your storage needs have
changed to ensure that you have enough backup space.

Setting up the Alarm Origination Manager

Use this section to set up the Alarm Origination Manager (AOM) on the CMS server. The aom_tool
is used to configure AOM. You can use the AOM feature to enable alarming to Avaya and this
capability is available only for CMS servers with a current maintenance agreement in effect.
You can optionally use AOM to send SNMP alarms to customer provided Network Management
Systems (NMS). You can enable SNMP alarms to a customer provided NMS even if a current
Avaya maintenance agreement is not in effect.
Note:
CMS supports only SNMP v3 in this release
Important:
There are multiple phases to completing the AOM configuration. You must configure an Alarm
ID, and you must configure an Alarm ID and a Customer ID if SNMP alarming to SAL is
intended. To use SNMP, you must configure an SNMP user. Finally, you must configure an
Alarm Destination.
Prerequisites
Before you set up AOM, perform the following tasks:
• Obtain an Alarm ID number and Sold To Functional Location (FL) number. You can obtain
an Alarm ID by registering the CMS server. You can register a CMS server using the Avaya
Global Registration Tool (GRT) tool at https://support.avaya.com/grt. If you cannot register
the system using the GRT tool, call 1800-242-2121, extension 15265, for assistance. If the
system does not have an Avaya maintenance agreement in effect and you are going to
configure optional SNMP alarming in a customer NMS, accept the default values that are
pre-populated.

Note:
During AOM configuration, use the Alarm ID referred to here as the Alarm ID and use the
Sold To Functional Location (FL) number as the Customer ID.

November 2024 Deploying Avaya Call Management System 58

Comments on this document?
 Setting up the Alarm Origination Manager

• Log on as root.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
Related links
Configuring an Alarm Destination on page 59
Configuring an SNMP User on page 62
Configuring an Alarm ID on page 65
Configuring a Customer ID on page 65
Sending an AOM Test Alarm on page 66
Clearing SNMP Alarms on page 66
CMS SNMP alarm information on page 67
Locating and installing the CMS-MIB.txt file on page 71
Setting up AOM configuration for alarming using Socket/SAL on page 71

Configuring an Alarm Destination

About this task
Use this procedure to configure an alarm destination.
Procedure
1. Start the AOM tool by running the command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Configure the Alarm Destination option, and press
Enter.
The system displays the following message:
Welcome to Avaya CMS Alarm Origination main menu.
1) SNMP/SAL
2) Socket/SAL
q) Quit
Enter choice (1-2, q):

Note:
Avaya recommends using SNMP/SAL for alarming.
3. Enter the number associated with the SNMP/SAL option, and press Enter.

November 2024 Deploying Avaya Call Management System 59

Comments on this document?
Configuring CMS features

The system displays a list of SNMP configuration options:

Do you want to
1) Add an SNMP Connection
2) Delete an SNMP Connection
3) Modify an SNMP Connection
4) Add an SNMP User
5) Delete an SNMP User
6) Modify an SNMP User
7) Clear SNMP Alarms
q) Quit
Enter choice (1-7, q):

4. Enter the number associated with the Add an SNMP connection option, and press Enter.
The system displays the Adding an SNMP connection option followed by an input prompt
for destination type:
Adding an SNMP connection
Select a destination type:
1) SAL
2) NMS
Enter choice (1-2):

5. Enter the number associated with SAL or NMS, and press Enter.
The system displays the input prompt for the destination IP address:
What is the destination IP address?

6. Enter the destination IP address, for example, 192.168.123.256, and press Enter.
The system displays the input prompt for the port number:
What is the destination port number?

7. Enter the destination port number, for example, 162, and press Enter.
The system displays the input prompt for the SNMP user:
Select an SNMP user:
1) cmssnmp
Enter choice (1-1):

8. Enter The system displays a list of defined users. Select an SNMP user, and press Enter.
The system displays the input prompt for Alarm ID along with the default Alarm ID value:
What is the Alarm ID (10 digit alarm ID)? (default:3000004043)

9. Enter the Alarm ID or accept the default value, and press Enter.
The system displays the input prompt for Customer ID along with the default Customer ID
value:
What is the Customer ID (10 digit customer code)? (default:0004558769)

10. Enter the Customer ID value or accept the default value, and press Enter.
The system displays the input prompt for Customer Name along with the default Customer
Name value:
What is the Customer Name? (default:Avaya)

11. Enter the Customer Name or accept the default value, and press Enter.

November 2024 Deploying Avaya Call Management System 60

Comments on this document?
 Setting up the Alarm Origination Manager

The system displays the input prompt for running a test alarm:
Run a test alarm when done?(y/n)

12. Enter y or n, and press Enter.

The system displays the following messages:
You have selected to configure AOM using SNMP.

Add an SNMP Connection

Destination Type: SAL

Destination IP: 198.1.1.2
Destination port: 162
Notification Type: inform
User Name: salcmsuser
Alarm ID: 3000004043
Customer ID: 0004558769
Customer NAME: Avaya

A test alarm will be sent at the end.

Press [Enter] to continue or [q] to quit

Note:
The SAL SNMP option requires a Notification Type of inform and notify in the
dest.cfg file.
13. Press Enter.
The system displays the following messages:
Configuring dest.cfg
[started]
done
reset AOM
[started]
done
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
done
Do you want to
1) Add an SNMP Connection
2) Delete an SNMP Connection
3) Modify an SNMP Connection
4) Add an SNMP User
5) Delete an SNMP User
6) Modify an SNMP User
7) Clear SNMP Alarms
q) Quit
Enter choice (1-7, q): q

14. Enter q to quit, and press Enter.

The system displays the following message:
Quitting

November 2024 Deploying Avaya Call Management System 61

Comments on this document?
Configuring CMS features

Configuring an SNMP User

Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Configure the Alarm Destination option, and press
Enter.
The system displays the Welcome to Avaya CMS Alarm Origination main menu options:
Welcome to Avaya CMS Alarm Origination main menu.
1) SNMP/SAL
2) Socket/SAL
q) Quit
Enter choice (1-2, q):

Note:
Avaya recommends using SNMP/SAL for alarming.
3. Enter the number associated with the SNMP/SAL option, and press Enter.
The system displays the list of SNMP configuration options:
Do you want to
1) Add an SNMP Connection
2) Delete an SNMP Connection
3) Modify an SNMP Connection
4) Add an SNMP User
5) Delete an SNMP User
6) Modify an SNMP User
7) Clear SNMP Alarms
q) Quit
Enter choice (1-7, q):

4. Enter the number associated with the Add an SNMP User option, and press Enter.
The system displays the input prompt for SNMP user name:
Adding an SNMP user
What is the SNMP user name?

5. Enter the SNMP user name, and press Enter.

The system displays the Select the SNMP version option:
Select the SNMP version:
1) v3
Enter choice (1-1):

6. Enter the number associated with the v3 option, and press Enter.

November 2024 Deploying Avaya Call Management System 62

Comments on this document?
 Setting up the Alarm Origination Manager

The system displays the Select the access level option:

Select the access level:
1) rouser: Read Only
2) rwuser: Read/Write
Enter choice (1-2):

7. Enter the number associated with the level of access to assign to the user, and press
Enter.
The system displays the Select the security level option based on the FIPS status:
• If the FIPS mode is off:
Select the security level:
1) noAuthNoPriv: Unauthenticated/Unencrypted (not allowed in FIPS mode)
2) authNoPriv: Authenticated/Unencrypted (not allowed in FIPS mode)
3) authPriv: Authenticated/Encrypted
Enter choice (1-3):
• If the FIPS mode is on:
Select the security level:
3) authPriv: Authenticated/Encrypted
Enter choice (1-1):

8. Enter the number associated with the level of security to assign to the user, and press
Enter. .
The system displays the Select the authentication protocol option based on the FIPS
status:
• If the FIPS mode is off:
Select the authentication protocol:
1) MD5 ( not allowed in FIPS mode)
2) SHA
Enter choice (1-2):
• If the FIPS mode is on:
Select the authentication protocol:
1) SHA
Enter choice (1-1):

9. Enter the number associated with the authentication protocol to assign to the user, and
press Enter.

Note:
Authentication utilizes the defined authentication password to sign the messages that
are sent during authentication. The encryption protocol for this can be either MD5 or
SHA.
The system displays the authentication password prompt:
Enter authentication password (min 8 chars):

10. Enter the authentication password to assign to the user, and press Enter.
The system displays the Select the encryption protocol option:
Select the encryption protocol:
1) AES

November 2024 Deploying Avaya Call Management System 63

Comments on this document?
Configuring CMS features

2) DES
Enter choice (1-2):

11. Enter the number associated with the encryption protocol to assign to the user, and press
Enter.

Note:
Authentication utilizes the defined encryption password to encrypt the data portion of
the SNMP messages. The encryption protocol for this may be either AES or DES.
The system displays the encryption password prompt:
Enter encryption password (min 8 chars):

12. Enter the encryption password to assign to the user, and press Enter.
The system displays information about the choices entered:
CMS was last rebooted 11 day(s) ago.
You have selected to configure AOM using SNMP.
Add an SNMP User
User Name: TestSNMP
SNMP version: v3
SNMP Access Level: rouser
SNMP Security Level: authPriv
SNMP authentication protocol: MD5
SNMP authentication password: ******
SNMP encryption protocol: AES
SNMP encryption password: ******
Press [Enter] to continue or [q] to quit

13. Press Enter to save the choices displayed, or press q to quit. .

14. If you press Enter, the system saves the choices and displays the following messages: .
Configuring /cms/aom/data/admin/user.cfg
[started]
Done
Do you want to
1) Add an SNMP Connection
2) Delete an SNMP Connection
3) Modify an SNMP Connection
4) Add an SNMP User
5) Delete an SNMP User
6) Modify an SNMP User
7) Clear SNMP Alarms
q) Quit
Enter choice (1-7, q):

• To add another user, repeat Steps 3-13.

• To modify a user, enter the number associated with the Modify an SNMP User option,
and press Enter. Make any desired changes to the configuration of the user.
15. Enter q to quit, and press Enter.
The system displays the following message:
Quitting

November 2024 Deploying Avaya Call Management System 64

Comments on this document?
 Setting up the Alarm Origination Manager

Configuring an Alarm ID
Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Set a Test Alarm option, and press Enter .
The system clears the current alarms and then sends the test alarm. The system displays
the following messages, and the tool returns to the command line prompt.
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
#

Configuring a Customer ID
Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Customer ID option, and press Enter
The system displays the Customer ID prompt:
What is the Customer ID (10 digit customer code)? (default:0004558769)

3. Enter the Customer ID value, and press Enter.

The default Customer ID is normally the last value entered. CMS servers have a pre-
defined default value that must be changed if the customer has an Avaya maintenance
agreement.
The system displays the Customer Name prompt:
What is the Customer Name? (default:Avaya)

4. Enter the Customer Name, and press Enter.

November 2024 Deploying Avaya Call Management System 65

Comments on this document?
Configuring CMS features

After you have configured the Customer name, the system displays the following
messages, and the tool returns to the command line prompt:
reset AOM
[started]
Done
#

Sending an AOM Test Alarm

Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Send a Test Alarm option, and press Enter .
The system clears the current alarms and then sends the test alarm. The system displays
the following messages, and the tool returns to the command line prompt.
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
#

Clearing SNMP Alarms

Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Configure the Alarm Destination option, and press
Enter .
The system displays the Welcome to Avaya CMS Alarm Origination main menu options
Configure the Alarm DestinationWelcome to Avaya CMS Alarm Origination main menu.
1) SNMP/SAL
2) Socket/SAL

November 2024 Deploying Avaya Call Management System 66

Comments on this document?
 Setting up the Alarm Origination Manager

q) Quit
Enter choice (1-2, q):

Note:
Avaya recommends using SNMP/SAL for alarming.
3. Enter the number associated with the SNMP/SAL option, and press Enter.
The system displays the list of SNMP configuration options:
Do you want to
1) Add an SNMP Connection
2) Delete an SNMP Connection
3) Modify an SNMP Connection
4) Add an SNMP User
5) Delete an SNMP User
6) Modify an SNMP User
7) Clear SNMP Alarms
q) Quit
Enter choice (1-7, q): 7

4. Enter the number associated with the Clear SNMP Alarms option, and press Enter
The system displays active alarms.
5. To close an open alarm, enter y at the prompt.

CMS SNMP alarm information

Alarm type Alarm name SNMP object identifier Description
Test Alarm TEST_ALARM .1.3.6.1.4.1.6889.2.72.0.1 This Test alarm is generated
to verify that CMS alarming is
functional. Since this is a test
alarm, this alarm does not cause
a new alarm ticket to be created
with Avaya.
Test Alarm Clear TEST_ALARM_CLR .1.3.6.1.4.1.6889.2.72.0.2 This Test alarm clear is generated
to verify that CMS alarming is
functional. Since this is a test
alarm clear, this alarm does not
close all alarm tickets with Avaya.
Expert System ES_ALARM .1.3.6.1.4.1.6889.2.72.0.3 Avaya Expert System alarm.
Alarm
Expert System ES_ALARM_CLR .1.3.6.1.4.1.6889.2.72.0.4 Avaya Expert System alarm clear.
Alarm Clear
ACD Link Alarm ACDLINK[1-8] .1.3.6.1.4.1.6889.2.72.0.5 This ACD Link Alarm is generated
if any CMS ACD link experiences
trouble.
ACD Link Alarm ACDLINK[1-8]_CLR .1.3.6.1.4.1.6889.2.72.0.6 This ACD Link Alarm Clear is
Clear generated when an existing ACD
Link alarm is cleared.
Table continues…

November 2024 Deploying Avaya Call Management System 67

Comments on this document?
Configuring CMS features

Alarm type Alarm name SNMP object identifier Description

Archiving Alarm [H]*ARCH .1.3.6.1.4.1.6889.2.72.0.7 This Archiving Alarm is generated
when the CMS interval, daily,
weekly, or monthly data archiver
experiences trouble.
Archiving Alarm [H]*ARCH_CLR .1.3.6.1.4.1.6889.2.72.0.8 This Archiving Alarm Clear is
Clear generated when an existing data
archiver alarm is cleared.
Disk Error DISK _ERR .1.3.6.1.4.1.6889.2.72.0.9 This disk error alarm is generated
when a disk failure occurs.
Disk Error Clear DISK_ERR_CLR .1.3.6.1.4.1.6889.2.72.0.10 This disk error clear alarm is
generated when an existing DISK
_ERR alarm is cleared.
ECH Warning ECH_WARNING .1.3.6.1.4.1.6889.2.72.0.11 This ECH Warning Alarm is
Alarm generated when External Call
History experiences a warning.
ECH Warning ECH_WARNING_CLR .1.3.6.1.4.1.6889.2.72.0.12 This ECH Warning Alarm Clear is
Alarm Clear generated when an existing ECH
Warning alarm is cleared.
ECH Failure ECH_FAILURE .1.3.6.1.4.1.6889.2.72.0.13 This ECH Failure Alarm is
Alarm generated when External Call
History experiences a failure.
ECH Failure ECH_FAILURE_CLR .1.3.6.1.4.1.6889.2.72.0.14 This ECH Failure Alarm Clear is
Alarm Clear generated when an existing ECH
Failure alarm is cleared.
Surviving Alarm SURVIVING .1.3.6.1.4.1.6889.2.72.0.15 This Surviving Alarm is generated
when a survivable CMS in
standby mode becomes active.
Surviving Alarm SURVIVING_CLR .1.3.6.1.4.1.6889.2.72.0.16 This Surviving Alarm Clear is
Clear generated when an existing
Surviving Alarm is cleared.
Disk Warning DISK_WRN .1.3.6.1.4.1.6889.2.72.0.17 This disk warning alarm is
generated when a disk warning
occurs. A disk warning indicates a
disk failure condition that can exist
in the near future.
Disk Warning DISK_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.18 This disk warning clear alarm
Clear is generated when an existing
DISK_WRN alarm is cleared.
Battery Error BATTERY_ERR .1.3.6.1.4.1.6889.2.72.0.19 This battery error alarm is
generated when a RAID battery
failure occurs.
Table continues…

November 2024 Deploying Avaya Call Management System 68

Comments on this document?
 Setting up the Alarm Origination Manager

Alarm type Alarm name SNMP object identifier Description

Battery Error BATTERY_ERR_CLR .1.3.6.1.4.1.6889.2.72.0.20 This battery error clear alarm
Clear is generated when an existing
BATTERY_ERR alarm is cleared.
Battery warning BATTERY_WRN .1.3.6.1.4.1.6889.2.72.0.21 This battery warning alarm is
generated when a RAID battery
warning occurs. A battery warning
indicates a RAID battery failure
condition that can exist in the near
future.
Battery Warning BATTERY_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.22 This battery warning clear alarm
Clear is generated when an existing
BATTERY_WRN alarm is cleared.
RAID Error RAID_ERR .1.3.6.1.4.1.6889.2.72.0.23 This RAID error alarm is
generated when a RAID enclosure
failure occurs.
RAID Error Clear RAID_ERR_CLR .1.3.6.1.4.1.6889.2.72.0.24 This RAID error clear alarm
is generated when an existing
RAID_ERR alarm is cleared.
RAID Warning RAID_WRN .1.3.6.1.4.1.6889.2.72.0.25 This RAID warning alarm is
generated when a RAID enclosure
warning occurs. A RAID warning
indicates a RAID enclosure failure
condition that can exist soon.
RAID Warning RAID_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.26 This RAID warning clear alarm
Clear is generated when an existing
RAID_WRN alarm is cleared.
Backup Warning BACKUP_WRN .1.3.6.1.4.1.6889.2.72.0.27 This backup warning alarm
is generated when a CMS
maintenance backup warning
occurs. A backup warning
indicates that a CMS maintenance
backup was not successful.
Backup Warning BACKUP_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.28 This backup warning clear alarm
Clear is generated when an existing
BACKUP_WRN alarm is cleared.
Elog Warning ELOG_WRN .1.3.6.1.4.1.6889.2.72.0.29 Warning that the CMS error
Alarm logging process may be
overloaded.
Elog Warning ELOG_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.30 CMS ELOG_WRN clear.
Alarm Clear
ACD Secondary ACDSECUP[1-8] .1.3.6.1.4.1.6889.2.72.0.31 The secondary ACD IP address is
Link Up being used.
Table continues…

November 2024 Deploying Avaya Call Management System 69

Comments on this document?
Configuring CMS features

Alarm type Alarm name SNMP object identifier Description

ACD Secondary ACDSECUP[1-8]_CLR .1.3.6.1.4.1.6889.2.72.0.32 The Clear is generated when the
Link Up Clear ACD Secondary Link Up Alarm is
cleared.
Disk Full Warning DISKFULLINF .1.3.6.1.4.1.6889.2.72.0.33 This Disk Full Alarm is generated
when the disks are 95% full.
Disk Full Warning DISKFULLINF_CLR .1.3.6.1.4.1.6889.2.72.0.34 This Disk Full Warning Clear is
Clear generated when the Disk Full
Warning is cleared.
Disk Full Alarm DISKFULLWRN .1.3.6.1.4.1.6889.2.72.0.35 This Disk Full Alarm is generated
when the disks are 95% full.
Disk Full Alarm DISKFULLWRN_CLR .1.3.6.1.4.1.6889.2.72.0.36 The Disk Full Alarm is cleared.
Firewall Warning FIREWALLWRN .1.3.6.1.4.1.6889.2.72.0.37 This firewall warning is generated
Alarm when the firewall is disabled.
Firewall Warning FIREWALLWRN_CLR .1.3.6.1.4.1.6889.2.72.0.38 The firewall warning is cleared.
Alarm Clear
FIPS Warning FIPS_WRN .1.3.6.1.4.1.6889.2.72.0.39 This FIPS warning is generated
Alarm when FIPS is disabled.
FIPS Warning FIPS_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.40 The FIPS Warning Alarm is
Alarm Clear cleared.
WebLM Warning LIC_ERR .1.3.6.1.4.1.6889.2.72.0.41 This License error is generated
Alarm when CMS is in license error
mode.
WebLM Warning LIC_ERR_CLR .1.3.6.1.4.1.6889.2.72.0.42 The license error mode is cleared.
Alarm Clear
WebLM Warning LIC_RESTRICTED .1.3.6.1.4.1.6889.2.72.0.43 This License Restricted is
Alarm generated when CMS is in license
restricted mode.
WebLM Warning LIC_RESTRICTED_CL .1.3.6.1.4.1.6889.2.72.0.44 The license restricted mode is
Alarm Clear R cleared.
Web Client WEBCRT_WRN .1.3.6.1.4.1.6889.2.72.0.45 This Web Client certificate
Warning Alarm warning alarm is generated when
the Web Client certificate is about
to expire.
Web Client WEBCRT_WRN_CLR .1.3.6.1.4.1.6889.2.72.0.46 The Web Client certificate warning
Warning Alarm alarm is cleared.
Clear
Web Client Error WEBCRT_ERR .1.3.6.1.4.1.6889.2.72.0.47 This Web Client certificate error
Alarm alarm is generated when the Web
Client certificate has expired.
Web Client Error WEBCRT_ERR_CLR .1.3.6.1.4.1.6889.2.72.0.48 The Web Client certificate expired
Alarm Clear error alarm is cleared.
Table continues…

November 2024 Deploying Avaya Call Management System 70

Comments on this document?
 Setting up the Alarm Origination Manager

Alarm type Alarm name SNMP object identifier Description

EASG Warning EASGCRT365_WRN .1.3.6.1.4.1.6889.2.72.0.49 This EASG certificate warning
Alarm alarm is generated when the
EASG certificate is expiring within
365 days.
EASG Warning EASGCRT365_WRN_ .1.3.6.1.4.1.6889.2.72.0.50 The EASG certificate 365 day
Alarm Cleared CLR warning alarm is cleared.
EASG Warning EASGCRT180_WRN .1.3.6.1.4.1.6889.2.72.0.51 This EASG certificate warning
Alarm alarm is generated when the
EASG certificate is expiring within
180 days.
EASG Warning EASGCRT180_WRN_ .1.3.6.1.4.1.6889.2.72.0.52 The EASG certificate 180 day
Alarm Cleared CLR warning alarm is cleared.
EASG Warning EASGCRT30_WRN .1.3.6.1.4.1.6889.2.72.0.53 This EASG certificate warning
Alarm alarm is generated when the
EASG certificate is expiring within
30 days.
EASG Warning EASGCRT30_WRN_C .1.3.6.1.4.1.6889.2.72.0.54 The EASG certificate 30 day
Alarm Cleared LR warning alarm is cleared.
EASG Error EASGCRT30_ERR .1.3.6.1.4.1.6889.2.72.0.55 This EASG certificate error alarm
Alarm is generated when the EASG
certificate has expired.
EASG Error EASGCRT30_ERR_C .1.3.6.1.4.1.6889.2.72.0.56 The EASG certificate expired error
Alarm Cleared LR alarm is cleared.

Locating and installing the CMS-MIB.txt file

Procedure
1. Download the CMS-MIB.txt file from http://support.avaya.com.
2. Install the MIBS file with NMS.

Setting up AOM configuration for alarming using Socket/SAL

The aom_tool is used to configure AOM.
• To set up AOM configuration, continue with Configuring AOM.
• To send a test alarm, continue with Sending an AOM Test Alarm.

Configuring AOM
Configuring AOM for alarming using a modem includes the following:
• Configuring an Alarm Destination
• Configuring an Alarm ID
• Sending an AOM Test Alarm

November 2024 Deploying Avaya Call Management System 71

Comments on this document?
Configuring CMS features

Configuring an Alarm Destination

Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Configure the Alarm Destination option, and press
Enter.
The system displays the following message:
Welcome to Avaya CMS Alarm Origination main menu.
1) SNMP/SAL
2) Socket/SAL
q) Quit
Enter choice (1-2, q):

Note:
Avaya recommends using SNMP/SAL for alarming.
3. Enter the number associated with the Socket/SAL option, and press Enter.

Note:
If the system has been previously configured with an alarming method, the system can
prompt for the removal of the configuration.
The system displays the input prompt for the SAL IP address:
What is the SAL ip address?

4. Enter the SAL IP Address and press Enter.

Do not use any leading zeros in the IP address as this can lead the system to interpret the
numbers in the address as octal.
The system displays the input prompt for the SAL network port and the default network
port value:
What is the SAL network port? (default:5108)

5. Enter the SAL network port value or accept the default value and press Enter.
The system displays the input prompt for the Alarm ID and the default Alarm ID:
What is the Alarm ID (10 digit product code)?

6. Enter the Alarm ID or accept the default value, and press Enter.
The system displays the input prompt for running a test alarm:
Run a test alarm when done?(y/n)

November 2024 Deploying Avaya Call Management System 72

Comments on this document?
 Setting up the Alarm Origination Manager

7. Enter y or n, and press Enter.

The system displays the following messages:
CMS was last rebooted 1 day(s) ago.
You have selected to configure AOM using SAL via Socket/Virtual NIU.
Removing existing socket configuration
SAL IP Address:
SAL network port number: 5108
Alarm ID: 3000004043
A test alarm will be sent at the end.
Press [Enter] to continue or [q] to quit

8. Press Enter.
The system displays the following messages, and the tool returns to the command line
prompt:
Configuring dest.cfg
[started]
done
reset AOM
[started]
done
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
done#

Configuring an Alarm ID
Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Set a Test Alarm option, and press Enter .
The system clears the current alarms and then sends the test alarm. The system displays
the following messages, and the tool returns to the command line prompt.
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
#

November 2024 Deploying Avaya Call Management System 73

Comments on this document?
Configuring CMS features

Sending an AOM Test Alarm

Procedure
1. Start the AOM tool by running the following command: /cms/aom/bin/aom_tool
The system displays the following messages:
Welcome to Avaya CMS Alarm Configuration Main Menu.
1) Set Alarm ID
2) Set Customer ID
3) Configure Alarm Destination
4) Send a Test Alarm
q) Quit
Enter choice (1-4, q):

2. Enter the number associated with the Send a Test Alarm option, and press Enter .
The system clears the current alarms and then sends the test alarm. The system displays
the following messages, and the tool returns to the command line prompt.
Clearing all current alarms.
[started]
done
Sending test alarm.
[started]
done
#

Setting the Informix configuration parameters for CMS

The IDS configuration parameters for CMS are automatically optimized for system performance
during the installation of Informix.

November 2024 Deploying Avaya Call Management System 74

Comments on this document?
Chapter 7: Setting up CMS

About configuring the CMS software

You can choose either of the following ways to configure the CMS software:
• Interactive configuration. If you use the interactive option, the program automatically prompts
you for the necessary information to configure the CMS software.
• Flat file configuration. If you use what is called the “flat file” option, you edit a file that contains
the necessary configuration data to set up the CMS software. When you execute the install
program, the program runs in the background and uses the flat file to configure CMS.
Prerequisites
Before you configure the CMS software, perform the following tasks:
• Verify that you are logged in as root.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
• Verify that if TCP/IP is being used to connect to an ACD, the switch/LAN setup is done.
• Verify that all file systems are mounted.

Setting up CMS interactively

About this task
When you run cmssvc and select the setup option for setting up CMS, all previous setup
information is erased. Before running this command option, ensure that you have any old setup
information on record.
Before you begin
Ensure that CMS is turned off and that IDS is running.
Procedure
1. Ensure that you are logged in to the CMS server with root privileges.
2. Run the cmssvc command.

November 2024 Deploying Avaya Call Management System 75

Comments on this document?
Setting up CMS

The Call Management System Services menu is displayed:

Avaya(TM) Call Management System Services Menu

Select a command from the list below.

1) auth_display Display feature authorizations
2) weblm_set Set up the connection to the WebLM
3) run_ids Turn Informix Database on or off
4) run_cms Turn Avaya CMS on or off
5) setup Set up the initial configuration
6) swinfo Display switch information
7) swsetup Change switch information
8) uninstall Remove the CMS rpm from the machine
9) patch_rmv Backout an installed CMS patch
10) back_all Backout all installed CMS patches from machine
11) security Administer CMS security features
Enter choice (1-11) or q to quit:

Note:
If you are running cmssvc for the first time, the Services menu is not displayed.
Instead, you are prompted to set up your system as described in Configuring WebLM,
EASG, and the encryption passphrase on page 45.
3. At the command prompt, enter 4 to select the run_cms option.
4. At the command prompt, enter 2 to turn CMS off and keep the Informix Database Server
running.
5. To create a new contact center connection, run the cmssvc command again.
6. At the command prompt, enter 5 to select the setup option.
7. At the command prompt, enter y to add a new configuration to CMS.
The system displays the following message:
Select the language for this server:

All languages are ISO Latin except Japanese. Selection of the

server language assumes that existing customer data is compatible. (Upgrade from
any ISO Latin language to any ISO Latin language or from Japanese to Japanese is
supported).

1) English
2) Dutch
3) French
4) German
5) Italian
6) Portuguese
7) Spanish
8) Japanese
Enter choice (1-8): (default: 1)

8. Enter the number corresponding to your language.

For example, you can enter 1 to select English.
When CMS is ready for adding a new configuration, a message such as the following is
displayed: Customer CMS data successfully initialized.

November 2024 Deploying Avaya Call Management System 76

Comments on this document?
 Setting up CMS interactively

9. At the Enter a name for this UNIX system prompt, enter the name of the new
system.
You can enter a maximum of 64 alphanumeric characters.
10. At the Select the type of backup device you are using prompt, select the
backup device type.
Note that tape backups are no longer supported.
11. Enter the backup device path when prompted.
12. At the Enter the number of Automatic Call Distribution systems (ACDs)
being administered prompt, enter 1.
13. At the Enter switch name prompt, enter the name of the new contact center.
You can enter a maximum of 20 alphanumeric characters.
14. Enter the number corresponding to the switch model you want to select.
15. At the Enter the local port assigned to switch prompt, enter the local port
number.
The port number must be in the range of 1 through 64 and match the corresponding value
defined for the Routing Core Server during the contact center installation.
16. At the Enter the remote port assigned to switch prompt, enter the remote port
number.
The port number must be in the range of 1 through 64 and match the corresponding value
defined for the Routing Core Server.
17. At the Enter switch host name or IP Address prompt, enter the Routing Core
Server IP address.
For the Simplex deployment, specify the static IP address of the Routing Core Server.
For the local HA and geo-redundant HA deployments, specify the virtual IP address
of the Routing Core Server. You define the Routing Core Server IP addresses in the
megaconfig.yml file.
18. At the Enter switch TCP port number prompt, enter the TCP port number.
The port number range is 5001 through 5020.
19. At the Number of splits/skills prompt, enter the number of skills in your contact
center.
The value range is 0 through 15,000.
20. At the Total split/skill members summed over all splits/skills prompt,
enter the number of agents in your contact center.
The value range is 0 through 1,000,000.
21. At the Number of trunk groups prompt, enter the number of trunk groups.

November 2024 Deploying Avaya Call Management System 77

Comments on this document?
Setting up CMS

The value range is 0 through 400.

22. At the Number of trunks prompt, enter the number of trunks in your contact center.
The value range is 0 through 200,000.
23. At the Number of unmeasured facilities prompt, enter the number of facilities in
your contact center.
The value range is 0 through 100,000.
24. At the Number of call work codes prompt, enter the number of call work codes in
your contact center.
The value range is 0 through 1,999.
25. At the Number of vectors prompt, enter the number of vectors in your contact center.
The value range is 0 through 32,000.
26. At the Number of VDNs prompt, enter the number of VDNs in your contact center.
The value range is 0 through 30,000.
You see the message Setup completed successfully displayed in the command
output.
27. (Optional) If you need to install additional CMS-related feature packages, see Maintaining
and Troubleshooting Avaya Call Management System.
28. If you are not installing any other feature packages, perform the following steps:
a. Run the cmssvc command.
b. Enter the number associated with the run_cms option.
c. Enter the number associated with the Turn on CMS option.

Editing a flat file

About this task
To configure CMS using a flat file, you must edit a copy of the cms.inst.skl installation file and
start the setup option of the cmssvc command.
Important:
This procedure is not necessary if you already configured CMS interactively.
Procedure
1. Use the following command to change to the CMS installation directory:
cd /cms/install/cms_install
2. Use the following command to make a copy of the CMS installation file:

November 2024 Deploying Avaya Call Management System 78

Comments on this document?
 Setting up CMS using the flat file

cp cms.inst.skl cms.install
3. Use the following command to change permissions on the copied CMS installation file:
chmod 644 cms.install
4. Use the following command to edit the copied CMS installation file:
vi cms.install
The file contains a series of questions and value ranges for each possible ACD (Automatic
Call Distribution system) in your configuration. Enter the appropriate values for your
configuration. The entries must be added on the blank lines after each question.

Caution:
Use the CMS server host name for the Linux system name. The computer’s host name
was assigned during network setup.
5. Press Esc.
6. Enter:
:wq!
The system saves and closes the file.
Example
For an example of a flat file that you will edit to set up CMS, see Example of a flat file on
page 90.
Next steps
Continue with Setting up CMS using the flat file on page 79.

Setting up CMS using the flat file

Before you begin
Verify that you have made all edits in the flat file. For more information, see Editing a flat file on
page 78.
Ensure that CMS is turned off and that IDS is running.
Procedure
1. Enter cmssvc.

Note:
If you are executing the cmssvc command for the first time, the system does not
display the menu. Instead, the system automatically prompts for WebLM setup, EASG
setup, encryption passphrase setup. For more information, see Configuring WebLM,
EASG, and the encryption passphrase on page 45.

November 2024 Deploying Avaya Call Management System 79

Comments on this document?
Setting up CMS

The system displays the “Call Management System Services Menu”:

Avaya(TM) Call Management System Services Menu

Select a command from the list below.

1) auth_display Display feature authorizations
2) weblm_set Set up the connection to the WebLM
3) run_ids Turn Informix Database on or off
4) run_cms Turn Avaya CMS on or off
5) setup Set up the initial configuration
6) swinfo Display switch information
7) swsetup Change switch information
8) uninstall Remove the CMS rpm from the machine
9) patch_rmv Backout an installed CMS patch
10) back_all Backout all installed CMS patches from machine
11) security Administer CMS security features
Enter choice (1-11) or q to quit:

2. Type the option number for the setup command.

The system displays the following message:
Select the language for this server:

All languages are ISO Latin except Japanese. Selection of the

server language assumes that existing customer data is compatible. (Upgrade from
any ISO Latin language to any ISO Latin language or from Japanese to Japanese is
supported).

1) English
2) Dutch
3) French
4) German
5) Italian
6) Portuguese
7) Spanish
8) Japanese
Enter choice (1-8): (default: 1)

Note:
When the cmssvc setup command is running, the system does not allow any other
cmsadm or cmssvc commands. The system rejects any attempt to run other cmsadm
or cmssvc commands and the system displays the following error message
Please try later, setup is active.

Note:
If system setup has already been done, the program responds:
Warning!!! Setup has already been performed.
Running this command will remove all CMS data in the database.
Do you wish to proceed and re-configure CMS? (y/n): (default: n)

If the warning message is displayed, perform one of the following actions:

• Enter n to exit the setup.
• Enter y to continue with the setup.
3. Enter the number associated with the language that is used on the system.

November 2024 Deploying Avaya Call Management System 80

Comments on this document?
 Setting up CMS using the flat file

The system displays the following message if a flat file exists; otherwise, this menu is not
displayed:
The input will be read from
1) the terminal
2) a flat file
Enter choice (1-2):

4. Enter the number associated with the flat file option.

The system displays the following message:
*** The rest of this command is running in the background ***

5. Verify that the installation completed successfully by entering: tail -f /cms/install/

logdir/admin.log
The -f option in the tail command updates the console as messages are written to
the admin.log file. All failure messages are logged in this file. The CMS software is
successfully set up when you see a message similar to the following:
Setup completed successfully <date/time>

You can edit this file and add comments about the packages that were installed or
authorized.
6. Press Delete to exit the tail -f command.
7. Choose one of the following:
• To install additional CMS-related feature packages (such as Forecasting or External Call
History), see Maintaining and Troubleshooting Avaya Call Management System.
• If you are not installing any other feature packages, do the following to turn on the CMS
software:
a. Enter: cmssvc.
The system displays the “Avaya Call Management System Services Menu”.
b. Enter the number associated with the run_cms option.
c. Enter the number associated with the Turn on CMS option.

November 2024 Deploying Avaya Call Management System 81

Comments on this document?
Chapter 8: Performing the customer
handover

This section describes how to test the CMS software to ensure that the application is working
properly before the system is turned over to the customer.
Prerequisites
Before you begin the procedures in this section, the technicians must:
• Locate the backup tapes (the set created by provisioning during installation) and set these
tapes to write-protect mode if using tape drives for backups.
• Connect the CMS server to the switch.
• Translate the switch with the CMS feature enabled.
• Connect the switch to an active link.

CMS customer handover checklist

No. Task Notes

1. Check the system date and time. See Verifying the system date and time on page 83.
2. Configure CMS warning email See Forwarding CMS warning messages on page 83.
forwarding.
3. Check the free-space allocation. See Checking free space allocation on page 83.
4. Test the ACD link. See Testing the ACD link on page 84.
5. Assign customer password. See Assigning customer passwords on page 85.
6. Test the CMS software. See Testing the CMS software on page 86.
7. Finalize the on-site installation. See Finalizing the on-site installation on page 89.

November 2024 Deploying Avaya Call Management System 82

Comments on this document?
 Verifying the system date and time

Verifying the system date and time

Procedure
1. Verify that the RHEL operating system time and the current local time are the same.
2. If the date and times are not correct, see the procedures in “Changing the system date and
time” in Maintaining and Troubleshooting Avaya Call Management System.

Forwarding CMS warning messages

About this task
The CMS server can forward warning messages to specific customer e-mail addresses. If you do
not enable CMS to forward warning messages, the messages will remain in the CMS root e-mail
account.
Important:
To use this feature, you must have Avaya Professional Services install either the Admin
Paging or Supervisor Paging packages. Contact Avaya support for more information.
Use the following steps to forward CMS warning messages:
Procedure
1. Obtain the e-mail addresses of any customer CMS administrators who want to receive the
warning messages.
2. Enter: cd /
3. Create the file for the e-mail addresses by entering: vi /.forward
4. Enter an e-mail address on a single line in the file.
You can enter more than one e-mail address but each e-mail address must be on a single
line as shown in the following example:
[email protected]
[email protected]
[email protected]

5. Save and quit the file by pressing Esc and entering: chmod 600 /.forward

Checking free space allocation

About this task
Note:
The steps in this section are performed using CMS Supervisor.

November 2024 Deploying Avaya Call Management System 83

Comments on this document?
Performing the customer handover

Procedure
1. Log on to CMS Supervisor.
2. Navigate to Administration > System Setup > Free Space Allocation.
3. Enter an ACD number (1-8).
4. Click on the Get Contents icon.
The system displays the Get Contents screen showing the amount of dbspace allocated
for each CMS item for the ACD selected.
For more information about free space allocation, see Administering Avaya Call
Management System.
If the Total Free Space field shows that there is not enough space available, you must
modify data storage allocation.

Testing the ACD link

About this task
After the CMS software has been installed or upgraded, the on-site technician must test the link
from the CMS server to the switch that is using the Automatic Call Distribution (ACD) feature.
Before you begin
Verify that:
• A virtual console window is open
• CMS is turned on.
Procedure
1. In a virtual console window, log into the system by using a CMS administrator’s login ID by
entering: su - cms
Enter the correct password if prompted.
2. Enter: cms
3. Enter the correct terminal type.
The CMS Main Menu is displayed.
The CMS Main Menu has indicators that show whether the link to the ACD is active. The
link indicator consists of the carets (\/ and /\) at the right side of the banner line. There
should be one caret for each ACD, and all should be pointed up (^).
Example:
If you have four ACDs, the link indicator should look like this: ^^^^, which means that all
four ACDs are up and operating.

November 2024 Deploying Avaya Call Management System 84

Comments on this document?
 Assigning customer passwords

4. Select Maintenance from the CMS Main Menu.

The system displays the Maintenance menu.
5. Select Connection Status from the Maintenance menu.
The Connection Status window displays the following information:
• The name of the ACD
• Whether the application is in data transfer
• Whether the session is in data transfer
• Whether the connection is operational
• The date, time, and any errors
6. Press the F5 key to exit the screen.

Assigning customer passwords

About this task
This section describes how the customer assigns passwords to each of its logins on the CMS
server. The customer must assign passwords to each of the following logins:
• root
• cms
• Any other administration logins that have been added for the customer
Procedure
1. Log in as root.

Important:
You cannot directly log on as root from a remote connection. You must log on using an
administered CMS user ID, then use su - root to log on with root privileges.
2. At the system prompt, have the customer enter: passwd login
where login is root, cms, and so on.
The system displays the following message:
New password:

3. Have the customer enter the new password.

The system displays the following message:
Re-enter new password.

4. Have the customer enter the password again.

November 2024 Deploying Avaya Call Management System 85

Comments on this document?
Performing the customer handover

Note:
The technician should not know these passwords
5. Repeat this procedure for each customer login.

Testing the CMS software

About this task
After the CMS software has been installed or upgraded, the on-site technician must test the CMS
software to verify its sanity.
Before you begin
Verify that:
• The virtual console is active
• CMS is turned on.
Procedure
1. Test the Real-Time Reports subsystem.
a. Enter: CMS
The system displays the CMS Main Menu.
b. Select Reports.
c. Select Real-time.
d. Select Split/Skill.
e. Select Split Status or Skill Status.
f. Verify that the Split/Skill Status Report input window is displayed.
g. Enter a valid split number in the Split: or Skill: field.
h. Select the Run action to run the report.
i. Verify that the system displays the Split or Skill Status Report window.
j. If the switch link is not operating, the report fields are blank and the status line reads
Switch link down.
k. Press the F3 key to access the Print window screen.
l. Select Print window to send the report to the printer.
m. Look at the message line near the bottom of the window and verify that there is a
confirmation message about sending the report to the printer.
n. Verify that the report printed by checking the printer for the report.
o. Return to the CMS Main Menu screen by pressing the F5 key twice.

November 2024 Deploying Avaya Call Management System 86

Comments on this document?
 Testing the CMS software

2. Test the Historical Reports subsystem.

a. On the CMS Main Menu, select Reports.
b. Select Historical.
c. Select Split/Skill.
d. Select Status.
e. Verify that the Split/Skill Status Report input window is displayed.
f. Enter a valid split number in the Split/Skill: field.
g. Enter -1 in the Date: field.
h. Select the Run action list item, and run the report.
i. Verify that the report window is displayed and that the information is displayed in the
appropriate fields.

Note:
If no historical data exists, the fields in the report window are blank.
j. Return to the CMS Main Menu by pressing the F5 key twice.
3. Test the Dictionary subsystem by doing the following from the CMS Main Menu.
a. On the CMS Main Menu select Dictionary.
b. Select Login Identifications
c. Enter an asterisk (*) in the Login ID field.
d. Select the List all action list item. The system lists all the login IDs.
e. Verify that the logins are displayed.

Note:
On a new system, the fields are blank.
f. Return to the CMS Main Menu by pressing the F5 key twice.
4. Test the Exceptions subsystem.
a. On the CMS Main Menu screen, select Exceptions.
b. Select Real-time Exception Log.
c. Verify that the window is displayed.

Note:
For a new installation, this window may be blank
d. Return to the CMS Main Menu by pressing the F5 key once.
5. Test the Call Center Administration subsystem.
a. On the CMS Main Menu select Call Center Administration.

November 2024 Deploying Avaya Call Management System 87

Comments on this document?
Performing the customer handover

b. Select the Call Work Codes option.

c. Press Enter.
d. Select the List all action list item, and list all the call work codes currently defined.
e. Verify that the displayed information is correct.

Note:
On a new system, the fields may be blank.
f. Return to the CMS Main Menu by pressing the F5 key twice.
6. Test the Custom Reports subsystem.
a. On the CMS Main Menu select Custom Reports.
b. Select Real-time. The system lists the names of the custom reports.
c. Verify that the names of existing custom reports are listed. If there are no reports, you
receive a message saying the submenu is empty.
d. Return to the CMS Main Menu by pressing the F5 key once.
7. Test the User Permissions subsystem.
a. On the CMS Main Menu select User Permissions.
b. Select User Data.
c. Verify that the User Data Input window is displayed.
d. Return to the CMS Main Menu by pressing the F5 key once.
8. Test the System Setup subsystem
a. On the CMS Main Menu select System Setup.
b. Select CMS state.
c. Verify that CMS is operating in the Multi-user mode.
d. Return to the CMS Main Menu by pressing the F5 key once.
9. Test the Maintenance subsystem.
a. On the CMS Main Menu select Maintenance.
b. Select the Printer Administration option.
c. Enter a valid printer name in the CMS printer name: field.
d. Select the List all action list item. The system lists the printer parameters.
e. Verify that the printer has been administered correctly.
f. Return to the CMS Main Menu by pressing the F5 key twice.
10. If the Graphics feature package has been enabled, test the Graphics subsystem.
a. On the CMS Main Menu select Graphics.

November 2024 Deploying Avaya Call Management System 88

Comments on this document?
 Finalizing the on-site installation

b. Verify that a Real-time Graphics screen can be accessed.

c. Return to the CMS Main Menu by pressing the F5 key once.
d. At each CMS terminal, log in as cms and enter the correct terminal type to verify that
the terminals are working properly. To log off, select the Logout option from the CMS
Main Menu.
If you encounter a problem that you cannot solve, escalate the problem through normal
procedures.

Finalizing the on-site installation

About this task
This section contains the final steps that a technician must perform before turning the system over
to the customer.
Procedure
1. Back up the system using a CMSADM backup.
The CMSADM file system backup saves all local file systems on the computer onto
a backup device, including system files, OS programs, and CMS programs. For more
information about backups, see Maintaining and Troubleshooting Avaya Call Management
System.

Caution:
Use a new set of backup media for this CMSADM file system backup. Do not use the
provisioning backup media. Ensure that the customer has the proper media for the
new backup.
2. Perform a full maintenance backup to back up historical data.
You can perform this backup using the CMS Supervisor maintenance features. For
more information about maintenance backups, see Administering Avaya Call Management
System.
3. Set up alarming. For more information about the AOM tool, see Setting up the Alarm
Origination Manager on page 58.
4. Ensure that customer login information and passwords are recorded.
5. Give the passwords, backup media, and software to the CMS administrator.
For system security and recovery, ensure that the CMS administrator stores passwords,
Informix serial numbers, key license information, encryption passphrases, and backup
media in a secure location.

November 2024 Deploying Avaya Call Management System 89

Comments on this document?
Appendix A: Flat file example

Example of a flat file

The following display shows an example of a flat file used to configure the CMS software for up to
eight ACDs (eight Automatic Call Distribution systems). Enter data for only the required number of
ACDs.
For more information, see About configuring the CMS software on page 75, Editing a flat file on
page 78, and Setting up CMS using the flat file on page 79.
# Enter a name for this UNIX system (up to 64 characters):
localhost
# Select the type of backup device you are using
# 1) Tape
# 2) Other
# Enter choice (1-2):

# Default backup device paths based on device type:

# Device Default backup path
# Tape /dev/st0
# Other 'none'
# Enter the default backup device path:

# Enter number of ACDs being administered (1-8):

# The following information is required per ACD:

# Information for ACD 1:
# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

November 2024 Deploying Avaya Call Management System 90

Comments on this document?
 Example of a flat file

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 2:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

November 2024 Deploying Avaya Call Management System 91

Comments on this document?
Flat file example

# /etc/hosts file or the link to the switch will not work.

# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 3:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x

November 2024 Deploying Avaya Call Management System 92

Comments on this document?
 Example of a flat file

# 2) Communication Mgr 7.x

# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

November 2024 Deploying Avaya Call Management System 93

Comments on this document?
Flat file example

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 4:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999

November 2024 Deploying Avaya Call Management System 94

Comments on this document?
 Example of a flat file

# Communication Mgr 8.x/CM 8.1.2+ Secured 1999

# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 5:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000

November 2024 Deploying Avaya Call Management System 95

Comments on this document?
Flat file example

# Communication Mgr 8.x/CM 8.1.2+ Secured 15000

# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 6:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

November 2024 Deploying Avaya Call Management System 96

Comments on this document?
 Example of a flat file

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 7:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000

November 2024 Deploying Avaya Call Management System 97

Comments on this document?
Flat file example

# CM 8.1.2+ Secured 360000

# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

# Information for ACD 8:

# Enter switch name (up to 20 characters):

# Select the model of switch for this ACD

# 1) Communication Mgr 6.x
# 2) Communication Mgr 7.x
# 3) Communication Mgr 8.x
# 4) CM 8.1.2+ Secured
# Enter choice (1-4):

# Enter the local port assigned to switch (1-64):

# Enter the remote port assigned to switch (1-64):

# If a host name is entered, the host name must be administered in a DNS or

# /etc/hosts file or the link to the switch will not work.
# Enter switch host name or IP Address:

# Enter switch TCP port number (5001-5999):

November 2024 Deploying Avaya Call Management System 98

Comments on this document?
 Example of a flat file

# Maximum number of splits/skills based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Number of splits/skills (0-Maximum):

# Maximum number of split/skill members based on switch type:

# Release(s) Value
# Communication Mgr 6.x 100000
# Communication Mgr 7.x/Communication Mgr 8.x 360000
# CM 8.1.2+ Secured 360000
# Total split/skill members, summed over all splits/skills (0-Maximum):

# Maximum number of trunk groups based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 2000
# Communication Mgr 8.x/CM 8.1.2+ Secured 2000
# Number of trunk groups (0-Maximum):

# Maximum number of trunks based on switch type:

# Release(s) Value
# Communication Mgr 6.x 12000
# Communication Mgr 7.x 24000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Number of trunks (0-Maximum):

# Maximum number of unmeasured trunks:

# Release(s) Value
# Communication Mgr 6.x 6000
# Communication Mgr 7.x 12000
# Communication Mgr 8.x/CM 8.1.2+ Secured 15000
# Number of unmeasured facilities (0-Maximum):

# Minimum number of call work codes based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1
# Communication Mgr 8.x/CM 8.1.2+ Secured 1
# Maximum number of call work codes based on switch type:
# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 1999
# Communication Mgr 8.x/CM 8.1.2+ Secured 1999
# Number of call work codes (Minimum-Maximum):

# Maximum number of vectors based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 8000
# Communication Mgr 8.x/CM 8.1.2+ Secured 8000
# Enter number of vectors (0-Maximum):

# Maximum number of VDNs based on switch type:

# Release(s) Value
# Communication Mgr 6.x/Communication Mgr 7.x 30000
# Communication Mgr 8.x/CM 8.1.2+ Secured 30000
# Enter number of VDNs (0-Maximum):

November 2024 Deploying Avaya Call Management System 99

Comments on this document?
Appendix B: Resources

Documentation
CMS and CMS Supervisor documents
Title Description Audience
Overview
Avaya Call Management System Overview Describes tested product characteristics All users
and Specification and product capabilities including feature
descriptions, interoperability, performance
specifications, security, and licensing
requirements.
Installation and maintenance
Deploying Avaya Call Management System Describes how to install and configure Implementation
CMS in a virtualized VMware or KVM engineers,
environment. administrators
Deploying Avaya Call Management System Describes how to deploy CMS in an Implementation
in an Infrastructure as a Service Amazon Web Services or Google Cloud engineers,
Environment Platform environment. administrators
Maintaining and Troubleshooting Avaya Describes how to configure, maintain, and Administrators,
Call Management System troubleshoot CMS. support personnel
Avaya Call Management System and Describes how to connect and administer Administrators,
Communication Manager Connections, the Automatic Call Distribution (ACD) installation
Administration, and Troubleshooting systems used by CMS. personnel, support
personnel
Avaya Call Management System High Describes how to connect to HA servers Administrators,
Availability Connectivity, Upgrade and and upgrade to HA. installation
Administration personnel, software
specialists involved
with HA
Using Avaya Call Management System Describes how to install and maintain your Administrators,
High Availability and Admin-Sync CMS High Availability (HA) system. support personnel
Upgrading
Table continues…

November 2024 Deploying Avaya Call Management System 100

Comments on this document?
 Documentation

Title Description Audience

Upgrading Avaya Call Management Describes the procedures required to System
System upgrade to a new CMS release. This administrators,
document is focused on full software or implementation
platform upgrades. engineers
Avaya Call Management System Base Describes how to perform a simplified base System
Load Upgrade load upgrade. You can perform a base administrators,
load upgrade within a CMS release or for implementation
other approved scenarios. Not all releases engineers
support base load upgrades.
Administration
Administering Avaya Call Management Provides instructions on administering a Avaya support
System call center using CMS Supervisor. personnel,
Administrators
Avaya Call Management System Call Describes the format of the Call History Administrators,
History Interface data files and how to transfer these files to supervisors
another computer.
Using ODBC and JDBC with Avaya Call Describes how to use Open Database Administrators,
Management System Connectivity (ODBC) and Java Database support personnel
Connectivity (JDBC) with CMS.
Avaya Call Management System Database Describes each database item and Administrators,
Items and Calculations calculation that CMS tracks and how CMS support personnel
calculates the values displayed on CMS
reports and CMS Supervisor reports.
Avaya Call Management System Custom Describes how to design and create Administrators,
Reports custom reports in CMS. report designers
Avaya Call Management System Security Describes how to implement security Administrators,
features in CMS. support personnel
CMS Supervisor
Avaya CMS Supervisor Clients Installation Describes how to install and configure Implementation
and Getting Started CMS Supervisor. engineers, system
administrators
Avaya CMS Supervisor Reports Describes how to use CMS Supervisor Supervisors,
reports. administrators
Avaya CMS Supervisor Report Designer Describes how to create new reports and Supervisors,
to edit existing reports through Report administrators
Designer and Report Wizard.

Avaya Solutions Platform Documents

Title Description Audience
Avaya Solutions Platform Overview and Describes the key features of Avaya All users
Specification Solutions Platform server
Table continues…

November 2024 Deploying Avaya Call Management System 101

Comments on this document?
Resources

Title Description Audience

Installing the Avaya Solutions Platform 130 Describes how to install Avaya Solutions Implementation
Series Platform 130 Series servers. engineers, solution
architects, support
personnel
Maintaining and Troubleshooting Avaya Describes procedures to maintain and Implementation
Solutions Platform 130 Series troubleshoot Avaya Solutions Platform 130 engineers, solution
Series servers. architects, support
personnel

Finding documents on the Avaya Support website

Procedure
1. Go to https://support.avaya.com.
2. To log in, click Sign In at the top of the screen and then enter your login credentials when
prompted.
3. Click Product Support > Documents.
4. In Search Product, start typing the product name and then select the appropriate product
from the list displayed.
5. In Select Release, select the appropriate release number.
This field is not available if there is only one release for the product.
6. (Optional) In Enter Keyword, type keywords for your search.
7. From the Select Content Type list, select one or more content types.
For example, if you only want to see user guides, click User Guides in the Select Content
Type list.

8. Click to display the search results.

Avaya Documentation Center navigation

For many programs, the latest customer documentation is available on the Avaya Documentation
Center website at https://documentation.avaya.com. Some functionality is only available when you
log in to the Avaya Documentation Center. The available functionality depends on your role.
Important:
If the documentation you are looking for is not available on the Avaya Documentation Center,
you can find it on the Avaya Support website.
While navigating through the Documentation Center, you can click the Avaya Documentation
Center logo at the top of the screen to return to the home page anytime. On the Avaya
Documentation Center, you can do the following:
• Click Avaya Links in the top menu bar to access other Avaya websites, including the Avaya
Support website.

November 2024 Deploying Avaya Call Management System 102

Comments on this document?
 Documentation

• Click Languages ( ) in the top menu bar to change the display language and view
localized documents.
• In the Search Documentation field, search for keywords and click Filter to filter by solution
category, product, or user role.
You can select multiple items in each filter category. For example, you can select a product
and multiple user roles.
• Click Library in the top menu bar to access the complete library of documents. Use the
filtering options to refine your results.
• After performing a search or accessing the library, you can sort content on the search results
page. When you find the item you want to view, click it to open it.
• Use the table of contents in a document for navigation. You can also click < or > next to the
document title to navigate to the previous topic or the next topic.

• Click Share ( ) to share a topic by email or copy the URL.

• Download a PDF of the current topic in a document, the topic and its subtopics, or the entire
document.
• Print the section you are viewing.

• Add content to a collection by clicking Add to My Topics ( ). You can add the topic and its
subtopics or add the entire publication.
• View the topics in your collections. To access your collections, click your name in the top
menu bar and then click My Topics.
You can do the following:
- Create, rename, and delete a collection.
- Set a collection as the default or favorite collection.
- Save a PDF of the selected content in a collection and download it to your computer.
- Share content in a collection with others through email.
- Receive collections that others have shared with you.

• Click Watch ( ) to add a topic to your watchlist so you are notified when the content is
updated or removed.
• View and manage your watchlist by clicking Watchlist from the top menu with your name.
You can do the following:
- Enable Email notifications to receive email alerts.
- Unwatch the selected content or all topics.
• Send feedback for a topic.

November 2024 Deploying Avaya Call Management System 103

Comments on this document?
Resources

Viewing Avaya Mentor videos

Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot
Avaya products.
About this task
Videos are available on the Avaya Support website, listed under the video document type, and on
the Avaya-run channel on YouTube.
• To find videos on the Avaya Support website, go to https://support.avaya.com/ and do one of
the following:
- In Search, type Avaya Mentor Videos, click Clear All and select Video in the Select
Content Type.
- In Search, type the product name. On the Search Results page, click Clear All and select
Video in the Select Content Type.
The Video content type is displayed only when videos are available for that product.
In the right pane, the page displays a list of available videos.
• To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and do
one of the following:
- Enter a keyword or keywords in the Search Channel to search for a specific product or
topic.
- Scroll down Playlists, and click a topic name to see the list of videos available. For
example, Contact Centers.

Note:
Videos are not available for all products.

Support
Go to the Avaya Support website at https://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.

Using the Avaya InSite Knowledge Base

The Avaya InSite Knowledge Base is a web-based search engine that provides:
• Up-to-date troubleshooting procedures and technical tips.
• Information about service packs.

November 2024 Deploying Avaya Call Management System 104

Comments on this document?
 Support

• Access to customer and technical documentation.

• Information about training and certification programs.
• Links to other pertinent information.
If you are an authorized Avaya Partner or a current Avaya customer with a support contract, you
can access the Knowledge Base without extra cost. You must have a login account and a valid
Sold-To number.
Use the Avaya InSite Knowledge Base for any potential solutions to problems.
1. Go to https://support.avaya.com.
2. To log in, click Sign In at the top of the screen and then enter your login credentials when
prompted.
3. Click Product Support > Products.
4. In Search Product, start typing the product name and then select the appropriate product
from the list displayed.
5. Select the release number, if applicable.
6. Click the Technical Solutions tab to view articles for resolving technical issues.

November 2024 Deploying Avaya Call Management System 105

Comments on this document?
Glossary

AFS Authentication File System. AFS is an Avaya Web system that allows you
to create Authentication Files for secure Avaya Global Services logins for
supported non-Communication Manager Systems.

Avaya Appliance A physical server sold by Avaya running a VMware hypervisor that
has several virtual machines, each with its virtualized applications. The
servers can be staged with the operating system and application software
already installed. Some of the servers are sold as just the server with
DVD or software downloads.

ESXi A virtualization layer that runs directly on the server hardware. Also
known as a bare-metal hypervisor. Provides processor, memory, storage,
and networking resources on multiple virtual machines.

Hypervisor A hypervisor is also known as a Virtual Machine Manager (VMM). A

hypervisor is a hardware virtualization technique which runs multiple
operating systems on the same shared physical server.

OVA Open Virtualization Appliance. An OVA contains the virtual machine

description, disk images, and a manifest zipped into a single file.
The OVA follows the Distributed Management Task Force (DMTF)
specification.

PLDS Product Licensing and Download System. The Avaya PLDS provides
product licensing and electronic software download distribution.

Reservation A reservation specifies the guaranteed minimum required amounts of

CPU or memory for a virtual machine.

RFA Remote Feature Activation. RFA is an Avaya Web system that you use
to create Avaya License Files. These files are used to activate software
including features, capacities, releases, and offer categories. RFA also
creates Authentication Files for secure Avaya Global Services logins for
Communication Manager Systems.

Snapshot The state of a virtual appliance configuration at a particular point

in time. Creating a snapshot can affect service. Some Avaya virtual
appliances have limitations and others have specific instructions for
creating snapshots.

November 2024 Deploying Avaya Call Management System 106

Comments on this document?
 Storage vMotion

Storage vMotion A VMware feature that migrates virtual machine disk files from one data
storage location to another with limited impact to end users.

vCenter Server An administrative interface from VMware for the entire virtual
infrastructure or data center, including VMs, ESXi hosts, deployment
profiles, distributed virtual networking, and hardware monitoring.

virtual appliance A virtual appliance is a single software application bundled with an

operating system.

VM Virtual Machine. Replica of a physical server from an operational

perspective. A VM is a software implementation of a machine (for
example, a computer) that executes programs similar to a physical
machine.

vMotion A VMware feature that migrates a running virtual machine from one
physical server to another with minimal downtime or impact to end users.
vMotion cannot be used to move virtual machines from one data center to
another.

VMware HA VMware High Availability. A VMware feature for supporting virtual

application failover by migrating the application from one ESXi host to
another. Since the entire host fails over, several applications or virtual
machines can be involved. The failover is a reboot recovery level which
can take several minutes.

vSphere Web Client The vSphere Web Client is an interface for administering vCenter Server
and ESXi. Downloadable versions are VMware 5.5 and 6.0. A browser-
based Web client version is VMware 6.5 and later.

November 2024 Deploying Avaya Call Management System 107

Comments on this document?
Index
A CMS Supervisor Web Client software (continued)
activating ...................................................................... 52
activating certificates .................................................................... 53
CMS Supervisor Web Client software .......................... 52 root certificate ......................................................... 54, 55
license .................................................................... 18, 32 starting ..........................................................................56
adding CMS VM ...............................................................................11
disk space .....................................................................48 CMS-MIB.txt file ...................................................................71
alarm destination ........................................................... 59, 72 collection
alarm ID ......................................................................... 65, 73 delete ..........................................................................102
Alarm Origination Manager edit ..............................................................................102
setting up AOM .............................................................58 generating PDF .......................................................... 102
AOM .....................................................................................66 sharing content ........................................................... 102
AOM configuration ................................. 59, 62, 65, 66, 72–74 configuration
using Socket/SAL ......................................................... 71 customer data ...............................................................15
assigning customer passwords ............................................85 configuration data ................................................................ 15
automatic restart configure
virtual machine ............................................................. 25 CMS features ................................................................51
Avaya InSite Knowledge Base ...........................................104 initial configuration ........................................................39
Avaya support website .......................................................104 system features ............................................................ 39
average resource utilization .................................................12 configuring
EASG ............................................................................45
encryption passphrases ................................................45
C system network .............................................................42
calculating data space virtual machine automatic restart ..................................25
CMSADM backup ......................................................... 56 WebLM ......................................................................... 45
full maintenance backup ...............................................57 configuring a medium configuration .....................................27
capacities .............................................................................14 configuring AOM .................................................................. 71
certificates configuring CMS .................................................................. 90
CMS Supervisor Web Client software .......................... 53 configuring CMS authorizations ...........................................52
changing content
root password ............................................................... 41 publishing PDF output ................................................ 102
checking free space allocation .............................................83 searching .................................................................... 102
checklist sharing ........................................................................102
configure CMS features ................................................51 sort by last updated .................................................... 102
configure system features ............................................ 39 watching for updates .................................................. 102
customer handover .......................................................82 customer handover .............................................................. 82
KVM deployment .......................................................... 31 customer ID ......................................................................... 65
planning .......................................................................... 9
VMware deployment .....................................................17 D
clearing SNMP alarms ......................................................... 66
clones database
deployment ................................................................... 17 initialize .........................................................................40
CMS configuration Dell platforms
through a flat file ........................................................... 78 for Avaya Solutions Platform .........................................11
CMS login passwords .......................................................... 51 deploying copies .................................................................. 17
CMS patches ....................................................................... 47 deploying OVA
CMS setup on Avaya Solutions Platform .........................................23
interactive configuration ................................................75 on customer-provided VMware server ..........................21
using a flat file ...............................................................79 deployment
CMS SNMP KVM ..............................................................................31
alarm information ..........................................................67 verify ............................................................................. 40
CMS software configuration .................................................75 VMware ........................................................................ 17
CMS Supervisor Web Client software deployment guidelines ......................................................... 10

November 2024 Deploying Avaya Call Management System 108

Comments on this document?
deployment overview ............................................................. 9 O
Disk encryption .................................................................... 45
disk space OVA ......................................................................................11
adding ...........................................................................48 OVA deployment .................................................................. 21
document changes ................................................................ 7 OVA deployment options
document purpose ................................................................. 7 customer provided OVA ................................................21
documentation ................................................................... 100
documentation center ........................................................ 102
finding content ............................................................ 102
P
navigation ................................................................... 102 planning
documentation portal ......................................................... 102 checklist ..........................................................................9
downloading software .......................................................... 11 planning for deployment ........................................................ 9
PLDS
E downloading software .............................................20, 35

EASG
configuring .................................................................... 45
Q
encryption passphrases QCOW2 ................................................................................11
configuring .................................................................... 45

R
F
related documentation ....................................................... 100
finalizing the on-site installation ........................................... 89 remote access ..................................................................... 49
finding content on documentation center ...........................102 requirements
flat file example ....................................................................90 virtual machine resources .............................................12
forwarding CMS warning messages .................................... 83 resource requirements .........................................................12
root certificate ................................................................ 54, 55
H root password ...................................................................... 41

handover ..............................................................................82
hardware support ................................................................. 11
S
high availability searching for content ......................................................... 102
VMware ........................................................................ 12 security script .......................................................................48
setting the Informix configuration .........................................74
I sharing content .................................................................. 102
small configuration ...............................................................26
IDS SNMP user .......................................................................... 62
starting ..........................................................................48 software media .....................................................................11
installation sort documents .................................................................. 102
CMS patches ................................................................ 47 starting
installing CMS Supervisor Web Client software .......................... 56
license file ...............................................................19, 34 support ...............................................................................104
system startup ..................................................................... 49
K
T
KB
Support site ................................................................ 104 test alarm ....................................................................... 66, 74
KVM deployment ................................................................. 31 testing the ACD link ............................................................. 84
testing the CMS software .....................................................86
L
U
large configuration ............................................................... 28
license ............................................................................18, 32 update Linux RPMs ............................................................. 47
limitations .............................................................................14
Linux RPMs ......................................................................... 47

November 2024 Deploying Avaya Call Management System 109

Comments on this document?
V
verify
CMS version ................................................................. 40
verifying
remote access .............................................................. 49
system startup .............................................................. 49
verifying the system date and time ...................................... 83
videos ................................................................................ 104
virtual environment ...............................................................11
virtual machine
automatic restart configuration ..................................... 25
virtual machine resource average utilization ........................12
virtual machine resource requirements ................................12

W
watchlist ............................................................................. 102
WebLM
configuring .................................................................... 45
worksheets ...........................................................................15

November 2024 Deploying Avaya Call Management System 110

Comments on this document?