0% found this document useful (0 votes)

23 views75 pages

CM FeatureDescription70

This document provides system capacity information for Avaya Aura Communication Manager Release 7.0. It includes legal notices and license information for the software. The document contains technical specifications and limitations for the communication manager system.

Uploaded by

mivaleria200

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

23 views75 pages

CM FeatureDescription70

Uploaded by

mivaleria200

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 75

Avaya Aura® Communication

Manager System Capacities Table

Release 7.0
03-300511
Issue 1.0
August, 2015
© THE HOSTED SERVICE. BY ACCESSING OR USING THE
2015 Avaya Inc.
All Rights Reserved. HOSTED SERVICE, OR AUTHORIZING OTHERS TO DO SO,
YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR
Notice WHOM YOU ARE DOING SO (HEREINAFTER REFERRED TO
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
While reasonable efforts have been made to ensure that the THE TERMS OF USE. IF YOU ARE ACCEPTING THE TERMS
information in this document is complete and accurate at the time OF USE ON BEHALF A COMPANY OR OTHER LEGAL ENTITY,
of printing, Avaya assumes no liability for any errors. Avaya YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO
reserves the right to make changes and corrections to the BIND SUCH ENTITY TO THESE TERMS OF USE. IF YOU DO
information in this document without the obligation to notify any NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT WISH TO
person or organization of such changes. ACCEPT THESE TERMS OF USE, YOU MUST NOT ACCESS
OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO
ACCESS OR USE THE HOSTED SERVICE. YOUR USE OF
Documentation disclaimer
THE HOSTED SERVICE SHALL BE LIMITED BY THE NUMBER
AND TYPE OF LICENSES PURCHASED UNDER YOUR
“Documentation” means information published by Avaya in
CONTRACT FOR THE HOSTED SERVICE, PROVIDED,
varying mediums which may include product information,
HOWEVER, THAT FOR CERTAIN HOSTED SERVICES IF
operating instructions and performance specifications that Avaya
APPLICABLE, YOU MAY HAVE THE OPPORTUNITY TO USE
may generally make available to users of its products and Hosted
FLEX LICENSES, WHICH WILL BE INVOICED ACCORDING TO
Services. Documentation does not include marketing materials.
ACTUAL USAGE ABOVE THE CONTRACT LICENSE LEVEL.
Avaya shall not be responsible for any modifications, additions, or
CONTACT AVAYA OR AVAYA’S CHANNEL PARTNER FOR
deletions to the original published version of documentation
MORE INFORMATION ABOUT THE LICENSES FOR THE
unless such modifications, additions, or deletions were performed
APPLICABLE HOSTED SERVICE, THE AVAILABILITY OF ANY
by Avaya. End User agrees to indemnify and hold harmless
FLEX LICENSES (IF APPLICABLE), PRICING AND BILLING
Avaya, Avaya's agents, servants and employees against all
INFORMATION, AND OTHER IMPORTANT INFORMATION
claims, lawsuits, demands and judgments arising out of, or in
REGARDING THE HOSTED SERVICE.
connection with, subsequent modifications, additions or deletions
to this documentation, to the extent made by End User.
Licenses
Link disclaimer
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE
AVAYA WEBSITE,
Avaya is not responsible for the contents or reliability of any linked
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR SUCH
websites referenced within this site or documentation provided by
SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE
Avaya. Avaya is not responsible for the accuracy of any
APPLICABLE TO ANYONE WHO DOWNLOADS, USES
information, statement or content provided on these sites and
AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM
does not necessarily endorse the products, services, or
AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA
information described or offered within them. Avaya does not
CHANNEL PARTNER (AS APPLICABLE) UNDER A
guarantee that these links will work all the time and has no control
COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA
over the availability of the linked pages.
CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY
AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS
Warranty
LICENSE IF THE SOFTWARE WAS OBTAINED FROM
ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
Avaya provides a limited warranty on Avaya hardware and
AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT
software. Refer to your sales agreement to establish the terms of
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE
the limited warranty. In addition, Avaya’s standard warranty
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.
language, as well as information regarding support for this
BY INSTALLING, DOWNLOADING OR USING THE
product while under warranty is available to Avaya customers and
SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU,
other parties through the Avaya Support website:
ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM
http://support.avaya.com or such successor site as designated by
YOU ARE INSTALLING, DOWNLOADING OR USING THE
Avaya. Please note that if You acquired the product(s) from an
OFTWARE (HEREINAFTER REFERRED TO
authorized Avaya Channel Partner outside of the United States
INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO
and Canada, the warranty is provided to You by said Avaya
THESE TERMS AND CONDITIONS AND CREATE A BINDING
Channel Partner and not by Avaya.
CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).
“Hosted Service” means a hosted service subscription that You
acquire from either Avaya or an authorized Avaya Channel
Avaya grants You a license within the scope of the license types
Partner (as applicable) and which is described further in Hosted
described below, with the exception of Heritage Nortel Software,
SAS or other service description documentation regarding the
for which the scope of the license is detailed below. Where the
applicable hosted service. If You purchase a Hosted Service
order documentation does not expressly identify a license type,
subscription, the foregoing limited warranty may not apply but You
the applicable license will be a Designated System License. The
may be entitled to support services in connection with the Hosted
applicable number of licenses and units of capacity for which the
Service as described further in your service description
license is granted will be one (1), unless a different number of
documents for the applicable Hosted Service. Contact Avaya or
licenses or units of capacity is specified in the documentation or
Avaya Channel Partner (as applicable) for more information.
other materials available to You. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel
Hosted Service
Partner, whether as stand-alone products, pre-installed on
THE FOLLOWING APPLIES IF YOU PURCHASE A HOSTED
hardware products, and any upgrades, updates, patches, bug
SERVICE SUBSCRIPTION FROM AVAYA OR AN AVAYA
fixes, or modified versions thereto. “Designated Processor”
CHANNEL PARTNER (AS APPLICABLE), THE TERMS OF USE
means a single stand-alone computing device. “Server” means a
FOR HOSTED SERVICES ARE AVAILABLE ON THE AVAYA
Designated Processor that hosts a software application to be
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO
accessed by multiple users. “Instance” means a single copy of the
UNDER THE LINK “Avaya Terms of Use for Hosted Services” OR
Software executing at a particular time: (i) on one physical
SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, AND
machine; or (ii) on one deployed software virtual machine (“VM”)
ARE APPLICABLE TO ANYONE WHO ACCESSES OR USES
or similar deployment.
on extent of activation or use authorized as specified in an order
License type(s) or invoice.

Designated System(s) License (DS). End User may install and Copyright
use each copy or an Instance of the Software only on a number of
Designated Processors up to the number indicated in the order. Except where expressly stated otherwise, no use should be made
Avaya may require the Designated Processor(s) to be identified in of materials on this site, the Documentation, Software, Hosted
the order by type, serial number, feature key, Instance, location or Service, or hardware provided by Avaya. All content on this site,
other specific designation, or to be provided by End User to the documentation, Hosted Service, and the product provided by
Avaya through electronic means established by Avaya specifically Avaya including the selection, arrangement and design of the
for this purpose. content is owned either by Avaya or its licensors and is protected
by copyright and other intellectual property laws including the sui
Concurrent User License (CU). End User may install and use the generis rights relating to the protection of databases. You may not
Software on multiple Designated Processors or one or more modify, copy, reproduce, republish, upload, post, transmit or
Servers, so long as only the licensed number of Units are distribute in any way any content, in whole or in part, including
accessing and using the Software at any given time. A “Unit” any code and software unless expressly authorized by Avaya.
means the unit on which Avaya, at its sole discretion, bases the Unauthorized reproduction, transmission, dissemination, storage,
pricing of its licenses and can be, without limitation, an agent, port and or use without the express written consent of Avaya can be a
or user, an e-mail or voice mail account in the name of a person criminal, as well as a civil offense under the applicable law.
or corporate function (e.g., webmaster or helpdesk), or a directory
entry in the administrative database utilized by the Software that Virtualization
permits one user to interface with the Software. Units may be
linked to a specific, identified Server or an Instance of the Each product has its own ordering code and license types. Note
Software. that each Instance of a product must be separately licensed and
ordered. For example, if the end user customer or Avaya Channel
Database License (DL). End User may install and use each copy Partner would like to install two Instances of the same type of
or an Instance of the Software on one Server or on multiple products, then two products of that type must be ordered.
Servers provided that each of the Servers on which the Software
is installed communicates with no more than one Instance of the Third Party Components
same database.
“Third Party Components” mean certain software programs or
CPU License (CP). End User may install and use each copy or portions thereof included in the Software or Hosted Service may
Instance of the Software on a number of Servers up to the contain software (including open source software) distributed
number indicated in the order provided that the performance under third party agreements (“Third Party Components”), which
capacity of the Server(s) does not exceed the performance contain terms regarding the rights to use certain portions of the
capacity specified for the Software. End User may not re-install or Software (“Third Party Terms”). As required, information regarding
operate the Software on Server(s) with a larger performance distributed Linux OS source code (for those products that have
capacity without Avaya’s prior consent and payment of an distributed Linux OS source code) and identifying the copyright
upgrade fee. holders of the Third Party Components and the Third Party Terms
that apply is available in the products, Documentation or on
Named User License (NU). You may: (i) install and use the Avaya’s website at: http://support.avaya.com/Copyright or such
Software on a single Designated Processor or Server per successor site as designated by Avaya. You agree to the Third
authorized Named User (defined below); or (ii) install and use the Party Terms for any such Third Party Components.
Software on a Server so long as only authorized Named Users
access and use the Software. “Named User”, means a user or THIS PRODUCT IS LICENSED UNDER THE AVC PATENT
device that has been expressly authorized by Avaya to access PORTFOLIO LICENSE FOR THE PERSONAL USE OF A
and use the Software. At Avaya’s sole discretion, a “Named User” CONSUMER OR OTHER USES IN WHICH IT DOES NOT
may be, without limitation, designated by name, corporate RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN
function (e.g., webmaster or helpdesk), an e-mail or voice mail COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”)
account in the name of a person or corporate function, or a AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A
directory entry in the administrative database utilized by the CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR
Software that permits one user to interface with the Software. WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO
PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL
Shrinkwrap License (SR). You may install and use the Software in BE IMPLIED FOR ANY OTHER USE. ADDITIONAL
accordance with the terms and conditions of the applicable INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C.
license agreements, such as “shrinkwrap” or “clickthrough” SEE HTTP://WWW.MPEGLA.COM.
license accompanying or applicable to the Software (“Shrinkwrap
License”). Preventing Toll Fraud

Heritage Nortel Software “Toll Fraud” is the unauthorized use of your telecommunications
system by an unauthorized party (for example, a person who is
“Heritage Nortel Software” means the software that was acquired not a corporate employee, agent, subcontractor, or is not working
by Avaya as part of its purchase of the Nortel Enterprise Solutions on your company's behalf). Be aware that there can be a risk of
Business in December 2009. The Heritage Nortel Software Toll Fraud associated with your system and that, if Toll Fraud
currently available for license from Avaya is the software occurs, it can result in substantial additional charges for your
contained within the list of Heritage Nortel Products located at telecommunications services.
http://support.avaya.com/LicenseInfo under the link “Heritage
Nortel Products” or such successor site as designated by Avaya. Avaya Toll Fraud intervention
For Heritage Nortel Software, Avaya grants You a license to use
Heritage Nortel Software provided hereunder solely to the extent If You suspect that You are being victimized by Toll Fraud and
of the authorized activation or authorized usage level, solely for You need technical assistance or support, call Technical Service
the purpose specified in the Documentation, and solely as Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the
embedded in, for execution on, or for communication with Avaya United States and Canada. For additional support telephone
equipment. Charges for Heritage Nortel Software may be based numbers, see the Avaya Support website:
http://support.avaya.com or such successor site as designated by
Avaya. Suspected security vulnerabilities with Avaya products
should be reported to Avaya by sending mail to:
[email protected].

Downloading Documentation

For the most current versions of Documentation, see the Avaya

Support website: http://support.avaya.com, or such successor site
as designated by Avaya.

Contact Avaya Support

See the Avaya Support website: http://support.avaya.com for

product or Hosted Service notices and articles, or to report a
problem with your Avaya product or Hosted Service. For a list of
support telephone numbers and contact addresses, go to the
Avaya Support website: http://support.avaya.com (or such
successor site as designated by Avaya), scroll to the bottom of
the page, and select Contact Avaya Support.

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, 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 and Avaya Aura® are registered trademarks of Avaya Inc.

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.
INTRODUCTION

This document contains the Avaya Aura® Communication Manger Release 7.0 system software-defined capacities information for all appliances and
equivalent software only offers of the Avaya Aura® Communication Manager. This document also includes capacity information for ASAI, Messaging, and
Call Center. This document does not contain capacities for Communication Manager Branch Edition, Communication Manager Essential Edition, and
Session Manager.
Both software-defined limits and offer limits are provided in the capacities table of the Avaya Aura® Communication Manger Release 7.0. The offer limits
are highlighted in tan for easy identification. They may be enforced by license files, or they may be enforced by Avaya support policy.
The capacities table in this document is the basis for the offer-based system capacities table posted on the Avaya web site which is frequently accessed
by the Avaya sales people, offer managers, and customers. When the offer limits are less than the corresponding software limits, the web document
shows only the offer limits.
Because the information compiled here is obtained from various sources, the authors appreciate a review of the document by a wider audience. This helps
to reduce errors or inconsistencies and to refine the information contained in these tables. MRs must be written against this document for any changes
related to capacities.
Highlights of Communication Manager Release 7.0
 Avaya Aura® Media Server support on Communication Manger
o 250 Media servers supported
o 40K Voice channels per Communication Manger
 Support for S8300E
o 1000 H.323 and 1000 SIP users for LSP
o 1000 SIP users for Branch Session Manager
 CC Elite 7.0 with CMS R18
o Increase Measured Trunks to 24K from 12K
o Increase Agent-Skill Pair Limit to 360K from 100K
o Increase Locations to 2000
 Increase in TLS sessions
o 500 new TLS sessions for AMS
o 250 new TLS sessions for H.248 gateways
o 2000 new TLS sessions for H.323 stations(for JITC only)
o TLS sessions for SM and AES remain unchanged
 Increase in Domain-controllers per Station Domain from 4 to 8

Highlights of Communication Manager Release 6.3

See the Capacities Table for details. Communication Manager Release 6.3 introduces:
 S8300D
o 1000 H.323 and 700 SIP users for LSP
o 700 SIP users for Branch Session Manager
 S8300E
o 1000 H.323 and 700 SIP users for LSP

Avaya Aura® Communication Manager System Capacities Table August 2015

o 700 SIP users for Branch Session Manager
 Offline call log entries for H.323 endpoints.
 Increase in the network region and locations from 250 to 2000.
 Increase in the number of Coverage answer groups (1000 to 1500), members in a group (8 to 100) and the system max of all members across
groups (22000 to 33000).
 Increase in the number of display-parameters from 25 to 50. Increase the number of location parameters to 50.
 Increase in the number of route patterns from 999 to 2000.
 Increase in the number of AAR and ARS analysis patterns from 999 to 2000.
 Increase in the number of simultaneous VDN Service Observers from 50 to 999.
 Increase in the number of simultaneous classified calls from 600 to 1200.
 SIP CC agents. Max capacity is 5000 agents.
 Increase in messages per second per AES connection from 1000 to 2000.
 Increase in ASAI event notification associations from 10,000 to 30,000.
 Increase in the number of simultaneous admin login sessions from 15 to 20 via GRIP 7364.
 VE offer. See footnote 146.

Highlights of Communication Manager Release 6.2

See the capacities table for details. Communication Manager Release 6.2 introduces:
 Increases in the offer limit for SIP endpoints (stations) from 18,000 to 36,000 for general business configurations.
 Increases in the number of Crisis Alert buttons for special application SA8608 from 250 to 750. Increase the “Max number of Bridges to a
Principal’s Call Appearance from 25 to 63 (a correction) and from 63 to 255 with SA9018 (described in Endnote 15).
 Increase in the number of table entries for the ip-network-map table from 500 to 4000 with SA9115.
 The midsize enterprise limits are preliminary and subject to change.
 Video capacities have been re-stated.
 SIP trunk capacities have been re-stated.
 A new 96x1 SIP agent deskphone – 6.2 SIP for EAS Agent use. This phone will be announced separately when it becomes available.

Highlights of Communication Manager Release 6.1 (6.0.1)

See the Capacities Table for details. Communication Manager Release 6.1 (6.0.1) introduces:
 A new System Platform template:
o Avaya Aura® Midsize Enterprise configuration (Midsize_Ent).
 A new ISDN BRI Media Module (MM_721).

Highlights of Communication Manager Release 6.0

See the Capacities Table for details. Communication Manager Release 6.0 introduces:
 Five new System Platform templates:
o Avaya Aura® Main / Avaya Aura® for Survivable Core Duplex configuration (CM_Duplex)
o Avaya Aura® Main / Avaya Aura® for Survivable Core Simplex configuration (CM_Simplex)
o Avaya Aura® for Survivable Remote Simplex configuration (CM_SurvRemote140)
o Avaya Aura® Main Embedded configuration (CM_onlyEmbed)
o Avaya Aura® for Survivable Remote Embedded configuration (CM_SurvRemoteEmbed140)

Avaya Aura® Communication Manager System Capacities Table August 2015

 Many capacity increases for Call Center including increase of logged in agent capacity to 10,000 agents, vectoring increases and some
general increases that are needed for Call Center applications.
 Not certified or supported: ATM.
 Not certified or supported: Center Stage Switch (CSS) except for federal government use.
 Not certified or supported: G600 gateways.
 Not certified or supported: G150 gateways.
 Not certified or supported: S8300B, S8300C, S8400A, S8400B, S8500B, S8500C, S8730, S8720, and S8710.
 Not certified or supported: MM312, MM314, MM316, and MM340.
 End of Sale but supported in R6 for Avaya Aura® Evolution Server Configurations: G250 gateways and G350 gateways.

Highlights of Communication Manager Release 5.2.1

See the Capacities Table for details. Communication Manager Release 5.2.1 introduces:
 S8800 server.
 The S8300D, with the co-resident SES server enabled, supports a maximum of 450 stations.

Highlights of Communication Manager Release 5.2

See the Capacities Table for details. Communication Manager Release 5.2 introduces:
 Increase in number of IP (H.323 and SIP) endpoint and trunk maximum.
 Increase in the announcement capacity for the G450 media gateway.
 New Communication Manager platform: S8300D (same capacities as the S8300C).

Highlights of Communication Manager Release 5.1

See the Capacities Table for details. Communication Manager Release 5.1 introduces:
 A Communication Manager platform, S8510, with the same capacities as the S8500C/D.

Highlights of Communication Manager Release 5.0

See the Capacities Table for details. Communication Manager Release 5.0 introduces:
 The S8730 server. The capacity limits of the S8730 are the same as those of the S8720XL, but the S8730 does not offer the Standard and XL
versions of the S8720.
 Co-resident Communication Manager and SIP Enabled Server (SES) on the S8300 server.
 The G450 Media Gateway, which has the same capacity limits as the G700 Media Gateway.
 The Avaya Agent Deskphone 16CC, an OPTIM-interfaced SIP Call Center agent phone, along with support in Communications Manager, SES
and other AST components. There are limits on how many Avaya Agent Deskphone 16CCs, added under the OPTIM Applications section, can be
logged in simultaneously.
Communication Manager 5.0 does not support S8700 and S8500A servers.

Highlights of Communication Manager Release 4.0

See the Capacities Table for details. Communication Manager Release 4.0 introduces:
 The S8720XL feature which allows for specific feature capacity increases as noted in a separate column.
 Other system capacity increases.

Avaya Aura® Communication Manager System Capacities Table August 2015

Highlights of Communication Manager Release 3.1
See the Capacities Table CID 106869 for details. Communication Manager Release 3.1 introduces:
 New Communication Manager platforms: S8720 (same capacities as the S8700 and S8710) and S8400.
 Other system capacity increases, such as support for 5,000 SIP trunks.

Highlights of Communication Manager Release 3.0

See the Capacities Table CID 106869 for details. Communication Manager Release 3.0 introduces:
 The G250 Media Gateway for small Branch Office configurations.
 Expanded Meet-Me Conferencing (EMMC), MM720 Line Side BRI and other feature related capacities.
 SIP (SES, SUSHI, and SCCAN) related capacity increases (but not restricted to SIP).
 Increased entries in the Incoming Call Handling Treatment (ICHT) table on the Trunk Group form and public-unknown-numbering form.
 Number of Bridged Appearances to 80,000 system-wide, SIP trunks, maximum SIP users per SES Home node and per System
(S8700/S8500/S8300).
 Call Center support on the VM Blade Server platform.
 The Application Enablement Services interface for ASAI/CTI applications.

Highlights of Communication Manager Release 2.2

See the Capacities Table CID 101553 for details. Communication Manager Release 2.2 introduces:
 The S8710 HP server, which supports IP-Connect and MultiConnect configurations. Capacities and configurations information from earlier
releases applies to the S8710.
 Support for ASAI Switch Classified Calls for trunks on H.248 Gateways and IP-Connected Port Network Gateways.
 The G150 H.323 Remote Office Gateway. It works with S8700, S8710, S8500, S8300, and G3si as the main Communication Manager server.
G150 provides connectivity over the WAN. Models of the G150 are the G150 2T + 4A (3 VOIP); G150 4T + 4A + 8DS (3VOIP); G150 4T + 4A +
8DS (16VOIP).
 The capacities for the RO Gateways are separate and independent from the H.248 media gateway capacity limits.
 G3SI offer End-of-Sale.
o New systems: The last date for sale is end of June 2005.
o Upgrades: The last date for upgrades is December 2005.
o Software Release: The last software release that supports G3SI is Communication Manager R2.2.
o S8500 replaces G3SI.
 The number of BRI trunk boards increases from 60 to 250 on all Communication Manager Linux platforms.

Highlights of Communication Manager Release 2.1

 The S8700 IP-Connect system capacities are the same as for S8700 MultiConnect system. The Capacities Table contains capacities for both 2.0
and 2.1, with separate columns for IP-Connect and Multi-Connect systems.
 The S8100 (Windows/D1/IP600/gaznt) is not offered on Communication Manager Release 2.1 and beyond. Communication Manager Release 2.0
is offered on the S8100.

Avaya Aura® Communication Manager System Capacities Table August 2015

 G350 in Call Center Applications: the G350 can be used in both ICC (S8300/G350) and ECC (as media gateway and survivable remote (formerly
LSP)). See footnotes [1] and [2] on this page, applicable to all H.248 media gateways.
 Blade Server capacities information is not included in this document, as recommended by Jan Leistikow, Scott Horton and others. Blade Server
information is also not included in the System Capacities Table on the web, because the Table is for the Enterprise Customer market and the
Blade solution is for the Service Provider market. The Blade Server is not offered through the CSD business unit; it can only be obtained through
the hosted solutions business unit, and they have a separate marketing organization.

Highlights of Communication Manager R2.0

 The DEFINITY® Server R (G3R) was discontinued on December 8, 2003. The G3R cannot be upgraded to Communication Manager R2.0, but
upgrades to Communication Manager R1.3.x were sold until November 2004. Please consult Upgrades and Additions for Avaya DEFINITY Server
R, 555-233-115, for information about upgrading to Communication Manager R1.3.
 The Category B offer is not offered in Communication Manager R2.0 and beyond.
 G350 in Call Center applications: G350 can be used in ECC configurations with Communication Manger R2.0, but not as a standalone
S8300/G350 (ICC configuration). This applies to G350 Media Gateways used in media server (S8700 or S8500 or S8300/G700) configurations.
See footnotes [1] and [2] on this page, applicable to all H.248 media gateways.

SYMBOL USED IN THE CAPACITIES TABLES:

An asterisk (*) indicates that the software-defined capacity may not be reachable due to hardware and/or processor capacity limits for the offer.

1
Tone Detectors: G700 and G350 have a limit of 15 Tone Detectors, which is sufficient for most call center applications considering the smaller overall capacity; but if many
calls have long tone detector holding time it may not support all the trunk capacity. Configurations have to be traffic engineered. This has always been the case but it is
even more critical with H.248 gateways because resources tend to be dedicated on a per-gateway basis, compared to the multi-connect configuration with port networks
where the resources are pooled across the configuration.
2
ASAI Switch Classified calls (for Predictive Dialing and Communication Manager applications) function for trunks on H.248 gateways starting with Release 2.2.

Avaya Aura® Communication Manager System Capacities Table August 2015

Row CM Capacity Item Avaya Aura® for
Main / Main / Survivable Main Survivable Remote Migrated
Survivable Survivable Core Remote Simplex Embedded137 Embedded 138 Midsize
Core Simplex 136 136
SMALL146, 147 SMALL 146, 147 Enterprise to
Duplex)136 LARGE 146, 147 LARGE 146, 147
Avaya Aura®
LARGE 146, 147 7.0
MEDIUM146, 147
Documentation disclaimer: The capacities specified in this table pertain to general business configurations and may not be valid or recommended for
Contact Center (CC) solutions. Simultaneously achieving the upper bounds for multiple capacities may not be possible for real-world CC systems. Call
rates and other operational aspects of these CC systems may preclude realizing the maximum limits. Contact the Sales Factory Design Center for
assistance with specific Contact Center solutions and capacities.
In general, software capacities of LSPs and ESSes are that of the Main Communication Manager they are associated with. They are not listed separately
in this table. Exceptions to this general rule are noted in the table and in the endnotes. For example, compare row "System-wide Maximum H.248 media
gateways" with row "H.248 media gateways per LSP".
The call handling capacities are based on the platform limits. Some of the capacities are offer specific and are determined by the License File; other
capacities are offer specific but are not limited by the License File. Some Call Center capacity increases require a Call Center Software upgrade to the
release the increase is provided in. This table contains both the software-based capacities and offer-based limits. Offer and license limits are under the
corresponding rows that provide the System Software limits.
Avaya Aura® Contact Center (AACC): See detailed capacities in Aura Contact Center Planning & Engineering Guide, Document 44400-210, available on
support.avaya.com
An asterisk (*) indicates that the software-defined capacity may not be reachable due to hardware and/or processor capacity limits for the platform.
65 ABBREVIATED DIALING and Autodial
70 AD Lists per System 68 20,000 20,000 20,000 2,400 20,000 20,000
75 AD List Entry Size 24 24 24 24 24 24
AD Entries per System
80 69 250,000 250,000 250,000 12000 * 250,000 250,000
85 ABBREVIATED DIALING Lists (See endnote 132 for Autodial Buttons)
Autodial buttons per
90 System endnote 132 endnote 132 endnote 132 endnote 132 endnote 132 endnote 132
Enhanced List (a
95 System List) 70 2 2 2 2 2 2
Max entries across
100 both enhanced lists 20,000 20,000 20,000 10,000 10,000 20,000
105 Group Lists 1,000 1,000 1,000 1,000 1,000 1,000
110 Max entries per list 100 100 100 100 100 100
Group lists /
115 extension 3 3 3 3 3 3
120 System List 1 1 1 1 1 1
125 Max entries 100 100 100 100 100 100
130 Personal Lists 20,000 20,000 20,000 2,400 2,400 20,000
135 Max entries per list 100 100 100 100 100 100

Avaya Aura® Communication Manager System Capacities Table August 2015

Display Formats for

2995 VuStats 50 50 50 50 50 50
System Max
Simultaneous Updating
3000 Displays 118 500 500 500 500 500 500
3005 Reporting Periods
3010 Intervals 25 25 25 25 25 25
3015 Days 1 1 1 1 1 1
3020 Reporting Adjunct Switch Links
3025 CMS R13.1 and earlier 1 or 2 1 or 2 1 or 2 1 or 2 1 or 2 1 or 2
R14 CMS and 4.0
3030 Avaya IQ or later87 2 or 4 2 or 4 2 or 4 2 or 4 2 or 4 2 or 4
3035 CES
System Max CES
3040 Servers151 10/22 10/22 10/22 10/22 10/22 10/22

Avaya Aura® Communication Manager System Capacities Table August 2015

CMS Capacities

The limits in the following table are defined by capacities on CMS R18.0 and not by CM structures. For
information about CMS capacities, see Avaya CMS Overview and Specification.

R18.0 CMS
Row CMS Capacity Item
Total Capacity

CMS - 1 ACD Admin Log Records 30,000

CMS - 2 ACDs (multi-ACD configuration) 8
CMS - 3 Agent login/logout data records 1,500,000
CMS - 4 Agent Login/Logout Records 1,500,000
CMS - 5 Agent Trace Records 5,100,000
CMS - 6 Agent Traces Active 5,000
CMS - 7 ICH Call Records 100,000
CMS - 8 CWC 85 1,999
CMS - 9 Exception Records 2,000
CMS - 10 External Call History Busy Hour Calls (per 20 min interval) 200,000
CMS - 11 External Call History Busy Hour Calls (per hour) 600,000
CMS - 12 ICH Data Base Rows (write rate 4K in 20 min) 100,000
CMS - 13 Locations / Location IDs 2000
CMS - 14 Logged-in Agent-Split/Skill Pairs over 8 ACDs 800,000
CMS - 15 Logged-in Agent-Split/Skill Pairs per ACD 360,000
CMS - 16 Max CWCs collected in the call record 6
CMS - 17 Measured Trunk Groups per ACD 8,000
CMS - 18 Measured Trunks over 8 ACDs (R14 and later) 84 80,000
CMS - 19 Measured Trunks per ACD (R14 and Later) 84 24,000
CMS - 20 Measured VDNs for a single ACD 30,000
CMS - 21 Measured VDNs over 8 ACDs 30,000
CMS - 22 Reason Codes (Aux Work) - 15 minute intervals 100
CMS - 23 Skills/Splits over 8 ACDs 32,000
CMS - 24 Splits/Skills per ACD 8,000
CMS - 25 Supervisor Logins (Simultaneous active client sessions) 86 1,600
CMS - 26 Unmeasured Trunks over 8 ACDs 20,000
CMS - 27 Unmeasured Trunks per ACD 6,000
CMS - 28 Vectors over 8 ACDs 32,000
CMS - 29 Vectors per ACD 8,000

Endnotes
The capacities table for Communication Manager Release 7.0 contains Communication Manager offer limits.
These endnotes explain some of the contents in the Capacities Table and some of the major offer limits. Special
Applications-based capacity differences are highlighted in green.

For information regarding end-of-sale of platforms such as G3R and G3si, see the introduction and the notes in
the beginning of the capacities table.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

* The software-defined capacity may not be reachable due to hardware and/or processor capacity limits
for the platform.

1 Documentation disclaimer: The capacities specified in this table pertain to general business
configurations and may not be valid or recommended for Contact Center (CC) solutions.
Simultaneously achieving the upper bounds for multiple capacities may not be possible for real-world
CC systems. Call rates and other operational aspects of these CC systems may preclude realizing the
maximum limits. Contact the Sales Factory Design Center for assistance with specifying Contact
Center solutions and capacities.

2 System Management sessions are used for system administration and maintenance purposes, and
some of the platforms allow multiple simultaneous sessions. The Simultaneous System Management
Sessions states row the number of simultaneous sessions each offer supports. However, besides
human administrators, the following types of sessions may also be using some of this capacity.
 EPN maintenance ports: 1
 Dial in or dial out requests: 1 for each direction
 Management Information Systems: 1
 CLAN ports: 1

The system also limits the number of simultaneous administration commands such as add and
change, as long as they are not accessing the same data. The Simultaneous Admin Commands row
gives the number of these allowed. For example, two administrators cannot change the same station
simultaneously. Commands such as test, busyout, release, and status are maintenance commands.
The Simultaneous Maintenance Commands row gives the number of simultaneous maintenance
commands that can be issued in addition to the administration commands, as long as they are not
accessing the same data and the command is not designated as a single user command.

3 In previous releases this feature was supported only on Fiber-Connected Port Networks (ATM or
Direct-Connect or the center stage switch (CSS)), but CM 6.0 support for fiber connections is only
using CSS, and then only for federal government use.

3.1 Endnote removed.

4 SA9050 provides 32 routing plans and time of day charts on the Main / Survivable Core Duplex, Main
/ Survivable Core Simplex, Survivable Remote Simplex 140, and Survivable Remote Embedded 140
offer. SA9050 provides 8 routing plans and time of day charts on the Main Embedded offer.

4.1 The TN799 (C-LAN) circuit pack has one Ethernet connection and 16 PPP connections. The sum of
links via PPP and Ethernet ports has to be less than the maximum number of communication-interface
links per switch. IP Routes refers to the size of the IP routing table accessed by the change ip-route
command.

CLAN boards need to be in a port network. Port networks cannot be used with S8300D. PPP links are
not supported via the processor Ethernet interface.

4.2 Endnote removed.

4.3 The system supports 10 QSIG hunt groups, but the number of messaging adjuncts depends on the PRI
signaling groups in the system.

4.4 This shows the number of agent-split combinations supported. Agent-split pairs is the total combination
used by ACD agents, Auto-Available Splits (AAS) ports (for example, VRUs), non-ACD hunt groups
(groups with or without queues, Message Center Service, INTUITY AUDIX®, Remote AUDIX®, etc.).
Each non-ACD hunt group member, AAS split member, and split assigned to an ACD agent is counted
when administered. CMS R18 is required for the increase to 360,000.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

4.5 The number of CMS adjuncts using TN799 circuit packs (C-LAN) for connectivity to the switch counts
toward the maximum capacity of C-LANs. The servers also provide LAN connectivity through their
native NICs and do not use C-LAN boards.
4.6 Administer the links over the TN799 circuit pack (C-LAN) or over the Processor Ethernet (procr).

5 An agent can be assigned more splits during administration but only this number can be simultaneously
logged into.

6 The maximum Members per Group limits limit the number of agents that can log into the same
split/skill. Maximum agent limits are reduced by the number of non-ACD members and AAS ports
administered, and with non-EAS, the additional splits assigned to agents that are not logged into.

7 Queue slots are shared across non-ACD, ACD (splits/skills) and AAS hunt groups.

NOTE: The capacity limits for System and Per Group Queue Slots are not applicable with platforms
that run Communication Manager Release 2.1 or later due to the Dynamic Hunt Group Queue Slot
Allocation feature. Hunt group queue slots are allocated on an as-needed basis allowing all calls that
are possible to be in queue as the default. The previous hunt group Queue Length field became a
Queue Limit field with specified limits carried forward in an upgrade. The common pool of queue slots
is 5,000 for the Main Embedded and Survivable Remote Embedded 140 offer and 15,000 for the
Main/Survivable Core Duplex, Main/Survivable Core Simplex and Survivable Remote Simplex 140
offers.

8 Plus up to 7 Inter-eXchange Carrier (IXC) digits

9 This is the number of available inserted-digit-strings administered on the route-patterns selected by

AAR/ARS analysis.

10 The number of attendant consoles listed is per software limitations.

10.1 Endnote removed.

10.2 Crisis Alert Stations: Crisis Alert buttons can be administered on attendant consoles and 10 additional
digital stations. Prior to 6.2, special application, SA8608, increases this capacity to 250 Crisis Alert
digital stations. With 6.2, special application SA8608 increases the capacity of Crisis Alert digital
stations to 750.

11 The number of release link trunk groups counts towards the total number of trunk groups in the system.

12 This does not include MLPP. With MLPP the limit is 17 for all platforms.

12.1 The BCMS monitor split command shows the status for the first 100 agents logged into the split,
regardless of how many additional agents log into the split.

12.2 BCMS monitoring is a maintenance process and is limited by the active maintenance commands limit,
as shown in row "Simultaneous Maintenance Commands". This should be reduced by 3 to reserve
command slots for INADS and SAT logins.

13 EPNs:
The entries reflect the PNs, and in brackets, the number of stacked cabinets per PN.

In a Mixed PNC environment, scalability increases for Center Stage Switch (CSS) by expanding the
number of total port networks to 64. The CSS is limited to a maximum of 44 PNs, but another 20 (or
more depending on how many PNs are part of the CSS) can be IP Bearer connected, for a maximum of

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

64. CM 6.0 support for fiber connections is only using the center stage switch, and then only for
government use.

14 The total number of trunks in trunk groups that are assigned as measured externally or “both” for CMS
and/or IQ tracking and reporting is limited to 12,000 trunks. Also trunk groups with a signaling group
defined as “IMS” (IP Multimedia Subsystem) for SIP links with Session Manager (SM) cannot be
assigned as measured by BCMS or external reporting adjuncts. The expanded virtual trunk port
number range to T24000 will be supported by the reporting adjuncts.

15 There can be up to 16 Bridged Call Appearances for a primary phone’s extension (not call appearance
button) if ASAI is used. Otherwise, 1250 principal stations can each have up to 63 other stations with
bridged appearances of the principal station. After that, the 1251st principal station through the
principal station that hits the system-wide maximum number of bridged appearances are limited to
having only 25 other stations with bridged appearances of the principal station.

Special Application SA9018 increases the number of Bridged Call Appearances for a primary’s call
appearance to 255.

16 The number of call appearances is the sum of primary and bridged appearances. The Max Call
Appearances per Ext row gives the maximum that can be primary.
A maximum of 54 administrable buttons is supported on the 7434 terminal without display.
A maximum 52 call appearances is supported on the 8434 terminal with display and expansion module.
A maximum 96 administrable buttons is supported on the 9630, 9640, and 9650 IP telephones with 3
button modules.

17 This maximum varies depending on the number of parties already on the call, on the calling and called
parties’ sides. The 7-parties maximum number of parties on a call is the guiding principle.
18 To administer announcements greater than 256, specifically refer to an announcement number greater
than 256. For example, use change announcement 300. The administrator then has access to
another 16 pages and so on.

For hunt group announcements greater than 256, the Call Center Release must be Release 8.1 or
later.

19 Shared extensions must be shared among all attendant groups in the system including Tenant
Partitions.

20 Special Application SA8661 provides 2050 automatic wakeup requests in a 15-min. interval.

20.1 VDNs are counted as part of the miscellaneous extensions capacity which includes VDNs, hunt groups,
announcements, LDNs, TEGs, PCOL groups, access endpoints, administered TSCs, and Code Calling
IDs extensions and common shared extensions.

The total of stations (station extensions including ACD agent physical set extensions, Logical Agent IDs
and AWOH) assigned cannot exceed the platform Station Extensions limit.

The total of all extensions assigned for any purpose cannot exceed the platform Maximum Extensions
limit (See the Dial Plan section for details).

20.5 BSR (Best Service Routing) application numbers are limited to 511, and location numbers are limited to
255.

21 Simultaneous 3-way Conference Calls. For non-IP endpoints on systems using port networks, the limit
equals the number of time slots for voice per port network (484) divided by 3, then rounded down, then
multiplied by the number of Port Networks. See Maximum Port Networks row

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

For non-IP endpoints on systems using H.248 media gateways, the limit equals the number of time
slots for voice per media gateway divided by 3, then rounded down, then multiplied by the number of
media gateways. See endnote 61 and the System-wide Maximum H.248 media gateways row."

If IP endpoints are involved, a VoIP resource is used up. The available number of VOIP resources
limits the number of such calls with IP endpoints.

For the Main Embedded and Survivable Remote Embedded 140 offers, the number of simultaneous 3-
way conference calls depends on the gateway the S8300D is embedded in. The following numbers do
not include subtending media gateways.
 S8300D embedded in a G430 or G350 or G250: 157
 S8300D embedded in a G450 or G700: 137

22 Simultaneous 6-way Conference Calls. For non-IP endpoints on systems using port networks, the limit
equals the number of time slots for voice per port network (484) divided by 6, then rounded down, then
multiplied by the number of Port Networks. See Maximum Port Networks row.

For non-IP endpoints on systems using H.248 media gateways, the limit equals the number of time
slots for voice per media gateway divided by 6, then rounded down, then multiplied by the number of
media gateways. See endnote 61 and the System-wide Maximum H.248 media gateways row.

If IP endpoints are involved, a VoIP resource is used up. The available number of VOIP resources
limits the number of such calls with IP endpoints.

For the Main Embedded, Survivable Remote Embedded 140 offers, the number of simultaneous 6-way
conference calls depends on the gateway the S8300D is embedded in. The following numbers do not
include subtending media gateways.
 S8300D embedded in a G430 or G350 or G250: 78
 S8300D embedded in a G450 or G700: 68

23 In practice, customers with RLT trunks also have DCS trunks, which limit them to 63 RLT nodes and 63
RLT trunk groups at the main server.

24 The Maximum Extensions limit is the total number of defined extensions for any use. Included in this
count are station extensions, miscellaneous extensions, data extensions, PRI endpoint extensions and
terminating extension groups.

24.1 Station extensions consist of attendant extensions, station set assignments (including ACD agent
physical sets), AWOH (administration without hardware) and administered Logical Agent IDs
extensions.

25 Miscellaneous extensions consist of VDNs, hunt groups, announcements, LDNs, PCOL groups,
common shared extensions, access endpoints, administered TSCs, Code Calling IDs, TEGs, Paging
zones, and Phantom ACAs. Access Endpoints are tied to the number of trunks, not the number of trunk
groups.

26 Special Application SA8993 increases Music on Hold Sources to 250 for all offers.

27 Integrated Directory Entries = stations + attendant consoles.

28 Number of Names = number of stations + attendant consoles + trunk groups + digital data endpoints +
miscellaneous extensions.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

28.1 Total of the administered Login ID skill-pair members (for agents and AAS ports).

28.2 Endnote removed.

28.3 Number of agent-skill combinations supported. Agent-skill pairs is the total combination used by ACD
agents, Auto-Available Skills (AAS) ports (for example, VRUs), non-ACD hunt groups (groups with or
without queues, Message Center Service, INTUITY AUDIX®, Remote AUDIX®, etc.). Each non-ACD
hunt group member and AAS skill member is counted when administered. Each skill assigned to an
EAS agent is counted as an ACD member when the EAS agent logs in, not when administered. CMS
R18 is required for the increase to 360,000.

28.4 This limit may not be reachable depending on how many skills are assigned per Login ID due to the
ACD Members Administered (Login ID-skill pair) limits. Login ID limits for different numbers of skills per
Login ID are:
Maximum Login IDs with Main/Survivable Core Main Embedded and
Duplex, Main/Survivable Survivable Remote
Core Simplex and Survivable Embedded 140 templates
Remote Simplex 140 Offer
1 Skill Each 30,000 1,500
20 Skills Each 30,000 300
60 Skills Each 16,666 N.A.
120 Skills Each 8,333 N.A.

Max Administered ACD Members (login ID / Agent-Skill pairs) shows the Login ID-Skill pair limit for
each server.

28.5 Hunt group members include non-ACD (hunting, Message Center Service, INTUITY AUDIX®, Remote
AUDIX®, etc.) and ACD uses (splits or skills including Auto-Available Splits/Skills). Each ACD agent-
split/skill assignment counts as a hunt group member.

28.6 This capacity is supported only with ucd-mia and ead-mia hunt group types and optionally with ucd-
loa and ead-loa using the bucket occupancy algorithm. Otherwise the capacity is 1,500 agents in a
skill. The bucket algorithm changes the occupancy selection to a more granular/coarse approach.
When the option is active and more than 3K agents have assigned to the same skill, the algorithm for
agent selection based on LOA switches over to a bucket algorithm (with 5% increment buckets). Note
that PAD and SLM types are still limited to 1,500.

28.7 SIP Contact Center (SIP EAS agent) is a new functionality introduced in 6.3. The limit of 5,000 SIP
agents is within the system limit of agents (row 1655). SIP agent is treated as a normal agent and is
subjected to existing capacity limitations of the system.
29 Last Number Dialed Entries = stations + digital data endpoints + attendant consoles.

31 INTUITY® supports 20 DCS nodes.

32 These numbers are node number addresses.

33 Special Application SA8927 increases the number of speakerphone paging groups to 999 on the
Main/Survivable Core Duplex, Main/Survivable Core Simplex and Survivable Remote Simplex 140, and
Survivable Remote Embedded 140 offer, and to 256 on the Main Embedded offer.

34 Only port slots are included in this count. For example, there are 100 slots per MCC EPN cabinet with
99 port slots and one slot dedicated for the Tone Clock circuit pack. There may be other service circuits
required that would further reduce the number of port slots available.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

35 Special Application SA9096 increases the members per speakerphone paging group to 127 for all
offers.

36 “Simultaneous calls in CM” is equal to the number of call record data structures allocated for the server
platform. This was traditionally determined using 242 Simultaneous Circuit Switched Calls per port
network. Multimedia calls tend to be multi-party calls.

Calls involving circuit switched endpoints will also be limited by the Total Time Slots in CM row. For
example, the maximum number of calls between two circuit switched endpoints on a Main Embedded
or Survivable Remote Embedded 140 offer running embedded in a G450 would be 512/2 = 256. Calls
involving only IP endpoints would not have this limitation if CM is configured to use IP-IP direct media.

See Communication Manager Hardware and Traffic Guidelines for further details.

37 Special Application SA8911 increases Public/Unknown Numbering entries to 20000 on the

Main/Survivable Core Duplex, Main/Survivable Core Simplex and Survivable Remote Simplex 140, and
Survivable Remote Embedded 140 offer, but leaves it at 240 on the Main Embedded offer.

38 484 time slots for voice and data per port network.

39 The system uses the port network TN744 Call Classifier/Detector for basic TTR use as well as call
prompting/call classification/MFC. With H.248 IP gateways (for example, G450) the embedded
processor circuit pack provides local tone detectors.
The number of TN744 circuit packs is limited by the number of available slots.
There is a single limit on the total number of tone receiver (classifier) ports for the system.
 TN744 has 8 ports for call prompting/call classification/MFC/TTR/GPTD use.
 The IPSIs (TN2312BP IP server interface) have 8 TTR resources embedded within them.
 The G250 TTR limits are in endnote 124 Current Gateway Capacities
 The G350 TTR limits are in endnote 124 Current Gateway Capacities
 The G700 TTR limits are in endnote 124 Current Gateway Capacities
 The G430 TTR limits are in endnote 124 Current Gateway Capacities
 The G450 TTR limits are in endnote 124 Current Gateway Capacities
The TTR capacity of the G700 affects the Busy Hour Call Capacity, especially the Call Center call mix.
In an IP-Connected configuration, TTRs can only be used to serve calls local to the gateway. They
cannot be shared across media gateways /PNGs.

40 Counts towards the total number of DS1 circuit packs.

41 Call Associated Temporary Signaling Connections (CA-TSCs) are associated with DCS and older
AUDIX® integration methods. They are not used by QSIG or SIP. QSIG uses Non Call Associated
TSCs.

42 The TN2185 BRI Trunk circuit pack, the MM720 and MM721 provide 8 ports. The TN556B and TN2198
provide 12 ports. Each port (2B + D) provides 2 BRI trunks.

42.1 Endnote removed

42.2 More information regarding BRI trunks (including TN2185, TN556 (suffix C and later), MM722, MM721,
and MM720 that are administered with the add bri trunk command). CM supports the number of BRI
trunk circuit packs shown in the BRI Trunk Circuit Packs row. This includes TN2185, TN556 (suffix C
and later), MM722, MM 721, and MM720 that are administered with the add bri trunk command. The
TN720 can be either NT or TE mode, but as long as it is administered as a trunk circuit pack it counts
towards that maximum.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

CM limits media gateways to the numbers shown in the System-wide Maximum H.248 media gateways
row. This can be any combination of G700, G450, G430, G350, and G250. BRI board limits are also
based on the types of media gateway and how many Media Modules (MM) they can support.
 G450 supports a maximum of 8 MMs per gateway.
 G430 supports a maximum of 3 MMs per gateway.
 G700 supports a maximum of 4 MMs per gateway.
 G350 supports a maximum of 6 MMs per gateway
 G250-BRI supports no MMs, but has 2 native BRI interfaces (4B + 2D) per gateway.
 CM will likely run into the BRI trunk circuit pack limits before running into the maximum BRI
trunks limits. With a MM720, if you use all 16 ports on each MM you get up to 250 x 16 = 4000
trunks on the Main/Survivable Core Duplex, Main/Survivable Core Simplex, Survivable
Remote Simplex and Survivable Remote Embedded 140 offer, and 50 x 16 = 800 trunks on the
Main Embedded offer. These are less than the limits on the Administered BRI Trunks in CM
row.

42.3 The 6,000 maximum is based on the following. Each TN556 BRI circuit pack supports 12 ports; each
port supports 2 B-Channels per port. 250 x 24 = 6,000.

If BRI trunks are used to connect to the PSTN, TN2185, MM720 or MM721 is more commonly used,
which support 8 ports (16 B-Channel), giving a total of 4000 (250 x 16) trunks.

If MM722 or the MM721 (2-port BRI circuit pack) is used, the capacity is further reduced.

The MM721 capacities per media gateway are as follows:

Gateway G450 G430 G700 G350

Max MM721s 7 4 4 33

43 The following items use extensions, and so can reduce the total number of available extensions on a
switch:
 Analog Music-On-Hold
 Attendants
 Modem Pool Conversion Resources
 TAAS Port
 Stations (Digital, display, BRI, etc.)
 Analog Announcements
 Analog External Alarm Port
 EAS Agent Login Ids
 ACD Agents

44 All BRI stations can be display stations.

MM720 and MM721 support 8 ports (on G450 gateway), and multipoint configuration with 2 B-channels
per port. Thus the MM720 and MM721 can support 16 BRI stations. The multipoint configuration
requires an external data module.

45 Capacities depend upon the version of IP phones.

3
To avoid changing the Channel Block Management (large blocks vs small blocks) strategy, this will be left as 3
slots.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

45.1 The Logged-In IP Softphone Agents field on the System-Parameters Customer-Options form, which
counts the ACD agents (either non-EAS or EAS) logging in with IP softphones for display purposes, is
set to the lesser of the two by the RFA/License File on the Logged-in ACD Agents field or the
Maximum Concurrently Registered IP Stations field.

46 Including extensions administered without associated hardware. See the Dial Plan section of the
Capacities Table for more details.

47 An H.323 Softphone operating in shared control with a H.323 telephone with the same extension will
consume two IP station registrations.

48 Endnote removed. It was replaced by endnote 95.1.

49 Endnote removed.

50 Due to a downlink buffer overflow problem, Group Page with Speakerphone does not work with
TN754A or TN754B. Minimum vintage of TN754C is required. Earlier vintage circuit packs may cause
lost messages, pages not terminating, phantom ringing, invalid displays, etc.

51 There are 2 Polycom SpectraLink® in-building wireless offers: the 900 MHz system and the 24GHz
system called the IP Wireless Telephone System. The 900 MHz phone (3410) is administered on CM
as 8410; the 2.4GHZ phone (3606) is administered as 4606. The Polycom SpectraLink® wireless user
maximum is based on the station user maximum.

52 A SIP station-to-station call counts as one call towards the Simultaneous Calls in CM row. However,
the SIP half-call model means that each SIP station on the call is using two SIP trunks. This limits
simultaneous SIP call capacity. The limits shown already have taken this into account. A SIP to H.323
call would use only half as much SIP resources.

53 Endnote removed.

54 There are two ways to collect CDR records: Legacy CDR and Survivable CDR.

In the Legacy method, the CM switch outputs the CDR data records in a near real time stream via an IP
link to an external CDR collection devices such as a third party CDR adjunct device or a terminal
server. When outputting to the third party adjunct, the data can be transmitted using standard TCP/IP
or via the Avaya propriety Reliable Session Protocol (RSP).

In the Survivable CDR method, the CDR data records are stored in data files on the CM server's hard
drive and then collected by a third party CDR adjunct using Secure File Transfer Protocol (SFTP). The
Survivable CDR method provides encrypted transfers of the CDR data records from the server to the
adjunct.

54.1 CM servers can buffer the number of records shown on the Max Number of CDR Records That Can Be
Buffered in the Switch row. The second number, 1,900 is a watermark number. Assume both primary
and secondary CDR devices are up, then if the buffered records (there is one buffer only) reaches 1900
or higher, the secondary CDR is dropped down for 2 minutes. The primary CDR continues to be up
and sending records. This indicates that secondary CDR device should not be used for sending
records, but for debug, etc. In most cases, only the primary CDR device is used.

55 The Survivable CDR feature allows CDR records to be stored on the hard disk of the server (main,
survivable remote (formerly LSP), or survivable core (formerly ESS) rather than being transmitted to the
CDR adjunct through an IP link. Once the CDR data is stored on the local hard drive the CDR adjunct
must login to the server and retrieve the CDR data files that are saved there.

Each server is capable of saving up to 20 CDR data files, each with up to 20 megabytes per file. When

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

the twenty-first file is created, the oldest CDR data file is automatically deleted thereby maintaining the
twenty file maximum.

Individual CDR record length may vary from 59 characters per record in the LSU formats up to 155
characters per record in the maximum size customized format. Customers select the format that best
meets their needs. The most popular CDR format is the unformatted format which contains 107
characters. A single CDR data file can hold anywhere from a little over 76.5K records per file up to
355.4 records per file depending on the selected format.

56 Special Application SA8993 increases the number of music sources to 250 for all platforms.

56.1 Endnote removed.

57 H.235.5 (Annex H) Stations are limited by offer. They are not limited by CM software nor by CM license
software, other than the Maximum Concurrently Registered H.323 Stations and the Offer Limit:
Maximum Concurrently Registered H.323 Stations row. If you administer more H.235.5 (Annex H)
stations than the H.235.5 (Annex H) offer limit, recovery re-registration delays after an outage can be
significant.

58 Endnote removed.

59 Endnote removed.

60 The signaling connections are shared by ISDN, H.323, and SIP signaling groups.

61 For the Main Embedded and Survivable Remote Embedded 140 offer, the number of time slots depends
on the gateway the S8300D is embedded in. The following numbers do not include subtending media
gateways.

Total Time Slots:

 S8300D embedded in a G430 or G250: 256
 S8300D embedded in a G450, G700, or G350: 512

Total Time Slots for Voice & Data

 S8300D embedded in a G430 or G250: 234
 S8300D embedded in a G450: 412
 S8300D embedded in a G700 or G350: 472

62 If the 12,000 trunk administration limit is ever exceeded for fault tolerance, the configuration
must prevent more than 12,000 trunks from ever being active on calls simultaneously.

For non-Session configurations designed for fault tolerance:

For IP (H.323 or SIP) trunks to continue to work when the far end of the IP trunk switches to a
survivable server, the near end CM server needs to have twice as many IP trunks configured as will be
in service at any one time. Half of those IP trunks go to the far end main server, and the other half of
those IP trunks go to the far end survivable server. This effectively reduces the maximum number of
administered IP trunks on the near end CM server by a factor of two. Here is an example.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

4000 total trunks, normal operation 4000 total trunks, far end in survivable mode
2000 trunks to far end main in use 2000 idle trunks to far end main
2000 idle trunks to far end survivable 2000 trunks to far end survivable in use

Local Far End

Local Far End CM Main CM
CM Main CM

Far End Far End

Survivable CM Survivable CM

For Session Manager configurations designed for fault tolerance:

In order to provide for SIP-only trunk configurations that can provide fault tolerant service, an exception
to the Administered trunk Limit for the CM-ES is allowed for configurations such as the following.
Customer requires N+1 redundancy for all critical components including: PSTN Access, Session
Border Controller (SBC), CM (Main and Survivable). Trunking typically is to one or the other data center
but each data center and subtending components must be able to handle the full load. For a CM-ES
that includes one or more Survivable Servers with co-located Session Managers, the number of
administered SIP trunks is allowed to exceed the nominal 12,000 trunk limit up to the maximum of
24,000 to accommodate the Session Managers at multiple sites.

No more than 12,000 trunks can be active on calls at one time. In the following example each Session
Manager must be able to handle the full load which means that CM must have full load trunking to each
SM. To enforce this limit, call traffic from the SIP Provider cannot exceed 12K active trunks. The
assumption is that the SIP trunks are distributed across the Session Managers in each Data Center in
this configuration. This restriction on traffic must be enforced outside of the SM/CM configuration. For
example, this can be enforced by a Session Border Controller (SBC) feeding traffic into normally active
the Session Managers in Data Center 1 or Data Center 2.

This relaxation of the trunk administration capacity limit for a CM-ES is driven by customers with
multiple data centers with N+1 requirements to provide for the geographic separation of the Main CM
and its Survivable Servers that have co-located Session Managers.

The Following diagram shows a case where there are no more than 6K active trunks but requires 24K
CM trunks to support the N+1 requirement

 6000 total trunks, normal operation  6000 total trunks, in disaster

to Data Center 1 mode to Data Center 2
 SBC load balances traffic between  SBC load balances traffic
SBC1 and SBC 2 (3000 to each) between SBC3 and SBC 4 (3000
 In event of SM failure remaining SM to each)
must take all 6000 calls  In event of SM failure remaining
 CM needs 6000 trunks to each SM in SM must take all 6000 calls
DC1  CM needs 6000 trunks to each
SM in DC2

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

PSTN

DC 1
DC 2

SBC SBC
1 2

SM1 SM2 SM3 SM4

Main Survivabl
CM e CM

Need total of 24K trunks to support this N+1

Survivable Configuration that uses 6K PSTN SIP trunk

63 The overall system limit is not restricted by the type of underlying transport that is used. For example,
either a single Processor Ethernet connection or 10 CLANs will be able to reach 2000 messages per
second on the Main/Survivable Core Duplex, Main/Survivable Core Simplex and Survivable Remote
Simplex 140 offers.

64 Endnote removed.

65 This is for tracking features like send all calls, call forwarding, and station busy status. The limit is 64 if
the buttons doing the tracking are on J24 (SUSHI) DCP sets, and as shown in the Buttons per Tracked
Resource row if the buttons doing the tracking are on other set types. CM can administer more than
these, but call processing won't use more than these.

66 Logged-in Agent capacity is limited by the offer through the Logged-In Agent customer option. See the
respective Product Definitions for details.

67 Endnote removed.

68 Includes personal lists + group lists + system list + enhanced lists.

69 This amount allows users to have 20,000 Enhanced AD entries (implemented as 2 lists), 10,000
personal lists with 20 entries each rather than 100, a System list of 100, and 100 Group lists with 100
entries each. This creates a maximum of 230,100 entries instead of 250,000.

70 Enhanced Abbreviated Dialing consists of 2 lists of 10,000 entries each, rather than one Enhanced AD
list of 20,000 entries. This allows 4-digit dialing via FAC to remain as before. A 20,000 entry list would
have required users to enter 5 digits when dialing via FAC.

71.0 Communication Manager software-based limits may not apply to features because their maximums are
scaled by their associated capacities, set by the License File, or based on the hardware/platform
limitations (boot-time configurations). Some capacities available on the main server may be different
from capacities on a survivable server.

Call Capacities (such as simultaneous 2-way, 3-way or 6-way calls) in the table are for non-IP
endpoints. If IP endpoints are involved, a VoIP resource is used. The available number of VOIP
resources limits the number of such calls with IP endpoints. See endnotes 21 and 22.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

The Main Embedded and Survivable Remote Embedded 140 offers don't use the TN-pack based IP
Media Resources TN2302AP and TN2602AP. This is because TN packs need port networks, but
S8300D does not support port networks. The Main Embedded and Survivable Remote Embedded 140
offers IP Media Resources depend on the gateways that the S8300D is embedded in. The sub-sections
below contain gateway-specific information.

71.0
continued Media Gateways supported by Avaya
Connect  IP- Fiber (CSS) Comments
Gateways Connect Connect 1
G250 Yes No Counts towards H.248 MGs
G350 Yes No Counts towards H.248 MGs
G430 Yes No Counts towards H.248 MGs
G450 Yes No Counts towards H.248 MGs
G650 Yes Yes Counts towards max PNs; see
Maximum Port Networks
G700 Yes No Counts towards H.248 MGs
IG550 Yes No Counts towards H.248 MGs
SCC/MCC Yes Yes Counts towards max PNs; see
Maximum Port Networks

1. Fiber connect is only for federal government use.

71.0
continued VOIP resources
Each IP Phone requires one channel. TN circuit packs can go on G650, MCC and SCC Media
Gateways.
 TN2602AP (IP Media Resource 320, a.k.a. standard IP Media Resource)
o 320 channels for G.711 and G.726A
o 280 channels for G.729A/AB
o It does not support G.723
These capacities are the same with either AEA or AES encryption.
 TN2602AP (a.k.a. Low Density IP Media Resource) supports
o 80 channels for G.711 and G.726A.
o 80 channels for G.729A/AB.
o It does not support G.723.
These capacities are the same with either AEA or AES encryption
 TN2302AP (IP media processor): Capacities impacted if AES encryption algorithm is used.
o 64 G.711 audio channels with AEA (48 with AES).
o 32 G.729A/B and G.723 audio channels with AEA (24 with AES).
 G430 channel capacity is described by endnote 124 Current Gateway Capacities
 G450 channel capacity is described by endnote 124 Current Gateway Capacities.
 G350 channel capacity is described by endnote 124 Current Gateway Capacities.
 G250 channel capacity is described by endnote 124 Current Gateway Capacities.

71.1 G700
The VOIP engine on the G700 support 64 channels for G.711, and 32 channels for G.729 or G.723.
The MM760 media module also supports 64 channels for G.711 and 32 channels for G.729 or G.723.

VOIP Capacity of a Single G700 Media Gateway (MG) with and without Internal Call
Controller

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

Description VOIP Engine and Call Constraining Factor

Capacities
The column with ( ) applies
to Without ICC
Configuration only, which
supports 5 MGs
Number of VOIP Engines 1 2 3 4 (5)
Installed in a Single MG 
Type of call 
IP Phone to Legacy Station, 32 64 96 128 (160 Simultaneous G.711 equivalent
Analog Trunk or E1/T1 Facility ) non-encrypted 2-Way
Conversations limited by the
VoIP Engine
(Note B) Includes call progress
tones
IP Phone to IP Phone 2-Way Dependent on
Conversations (1) Ability of the IP phones to
Shuffle
(2) Performance of the LAN
IP Phone to IP Phone 2-Way 64 128 192 256 (320 (1) Limited by the VoIP Engine
Conversations that require Hair ) (2) Performance of the LAN
Pin capability
IP Phone to IP Phone 3-Way 10 21 32 42 (53) Simultaneous 3-Way
Conference Conversations Limited by VoIP
Engine (Note A)
Transcoding IP to IP phone 32 64 96 128 (160 Simultaneous 2-Way
(from G711, G729 and G723) ) Conversations Limited by the
VoIP Engine
(Note A)

Note A: Calls between IP Phones depend on the ability of IP Phones to shuffle and the performance of
the LAN.
Note B: The maximum cannot be reached simultaneously with all types of calls that require a VOIP
Port.

On each G700 media gateway, 512 Time-Slots are available, out of which 40 time-slots are used for
Call Progress Tones. Each G700 media gateway can support a maximum of 236 simultaneous non-IP
connections (472 total time-slots divided by 2 time-slots per call). Each G700 media gateway supplies
15 Call Classifiers.

G700 supports stacked media gateways, 10 media gateways/stack.

71.2 Endnote removed.

71.3 Endnote removed.

71.4 G350 is targeted at small branch offices of large distributed systems. In a standalone configuration, an
S8300 server on a G350 Media Gateway provides WAN, LAN and PSTN connectivity. Call Center
applications are supported. Embedded AUDIX® (IA770) is supported. G350 has 6 physical slots for
Media Modules.

The following are configuration guidelines, not software-defined capacity limits. See Communication
Manager Hardware and Traffic Guidelines for more details.
o Recommend using 4 slots for voice, 2 for WAN connectivity: 1 slot for High-Density Media
Module (HDMM), 1 slot for Call Controller (S8300), and 4 slots for other media modules. No

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

more than 2 MM710. No more than 3 MM716.

o G350 can support up to 5 other subtending G350/G250 gateways. The G700 gateway
subtending to a G350 is not recommended.
 Stations per G350 gateway
o Up to 72 users in any combination of IP, analog, and DCP stations.
 Trunks per G350 gateway
o Up to 60 trunks total
o 40 analog trunks
o 2 T1/EI for digital trunks
o 32 IP trunks at G711
o Up to a total of 132 TDM stations and trunks
71.5 G860
G860 R1 supports a maximum of 40,000 calls BHCC of medium call center traffic terminating on IP
endpoints, using a CM server with the latest GA version of TN2602AP (IP Media Resource 320, a.k.a.
High Density). G860 R1 supports a minimum 2,688 VoIP channels with a single T3 PSTN interface.
The G860 R1 supports a maximum 4 active TP-6310 modules which serve as many as 4xDS-3
interfaces. This carrier-grade platform supports redundancy to avoid any single point of failure.

G860 R2 increases capacity to 6000 channels and 40,000 BHCC of medium call center traffic
terminating on IP endpoints per CM server with the latest GA version of TN2602AP. When many
G860s are added, the level of availability and scalability is increased, the capacity increases with
multiple Communication Manager servers to provide a solution with G860 to offer more than the 40K
BHC. New solution configurations include a many-to-many mapping of Communication Manager
servers to G860. This multiple mapping is implemented by assigning each T3 circuit pack (TP6310) to
a different Communication Manager server. As many as three active TP6310s may be used in a single
G860 in a 9+3 configuration along with one standby redundant TP6310 (N+1 configuration). Achieve
load balancing by distributing incoming calls based on ANI/DNIS information.

A 9 + 3 configuration refers to nine active T3 interfaces supported by three hot standby TP6310 circuit
packs in which each TP6310 circuit pack supports three x T3 interfaces. The G860 has total of 10 slots.
Four slots are used by primary and redundant shelf controller circuit packs, and Ethernet circuit packs.
Slot 10 is reserved for a redundant standby TP circuit pack, leaving 5 slots for active TP circuit packs.

G860 R2 supports high bandwidth optical interfaces including OC3 (Optical Carrier at 155.52 Mbps)
and STM (Synchronous Transfer Mode) in a 3+1 configuration. This configuration is three T3/OC-
3/STM-1 PSTN interfaces supported by one active TP6310. TP-6310 supports either a single OC-3
interface or 3xDS-3 interfaces. A 3+3 configuration requires one active and one redundant TP-6310
modules. A standby TP6310 may be used in slot 10. This configuration allows G860 R2 to support data
connections in addition to TDM voice calls.

Avaya IG550 Integrated Gateway:

71.6
The IG550 Integrated Gateway is based on the Juniper routers that host an Avaya TGM550 card
functioning as a H.248 gateway, and some TIM cards that provide interfaces for legacy TDM interfaces.
This solution is focused on branches of 2-100 users.

The TGM550 can support 10, 20, or 80 concurrent VoIP calls, depending on which DSP option is
installed. It provides 32 ports of touch tone detection and call classification, 16 announcement ports, 20
minutes of announcements or music, and 256 announcement files. Each gateway provides 120
timeslots.

J2320 J2350 J4350 / J6350

Slots in the platform 3 5 6
Max number of interface TIM (excluding TGM) 2 4 4
Max # of Avaya TIM516 (Analog) 1 2 3

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

Max # of Avaya TIM514 (Analog) 2 4 4

Max # of Avaya TIM508 (Analog) 1 3 3
Max # of Avaya TIM518 (Analog) 1 3 3
Max # of Avaya TIM521 (BRI) 2 4 4
Max # of Avaya TIM510 (E1/T1) 2 4 4
Max # of Juniper BRI cards 1 1 2
Max # of Juniper T1/E1 cards 1 1 2
Max # of analog ports (trunks and lines) 16 16 J4350 - 35
J6350 - 40
71.7 Endnote removed

72 Using multiple subtending gateways allows CM embedded on S8300D to reach the system-wide
capacities. Use the traffic configurator to determine the number of gateways needed per system and
to build a system with the proper configuration.

73 QSIG integrated nodes are not limited by a fixed node capacity. However, the size of a QSIG network
is limited by physical connectivity and the inter-switch dial plan limitations based upon the customer
configuration. With AAR dialing, it is possible to address another user within a QSIG network with up to
a 20-digit number, so it is possible to have large QSIG networks.

74 Endnote removed.

75 The TN799 C-LAN circuit pack supports 300 sockets. This value is configured as default by ASD.

76 Applies to hybrid QSIG/DCS networks. The QSIG portion of the network is unrestricted with respect to
the number of nodes (see note 73). The DCS portion is restricted to the DCS node limitations that
already exist. A switch that acts as a gateway (both DCS and QSIG links) deducts from the overall DCS
node limit.

77 Video calls utilize an internal CM video system resource. Video-enabled stations and trunks whose
signaling groups support video that participate in a video call, each consume units of this internal CM
video system resource for the life of the call. The particular video resource consumption for a call,
depends on the call-flow and is a function of the number of H.323 stations and the number of
H.323/SIP trunks used.

As an example, a video call between two video-capable H.323 stations that use the same CM-ES,
consumes two units of the Video Call Resource, because there are two H.323 stations in use on the
call. The resulting system limit for such calls is described in the row “Number of Simultaneous Video
Calls on a CM-ES”.

As another example, a video call between two video-capable SIP stations that use the same CM-FS,
consumes fours units of the Video Call Resource, because there are four SIP trunks in use on the call.
The resulting system limit for such calls is described in the row “Number of Simultaneous Video Calls
on a CM-FS.”

78 System maximum for all simultaneous in-use IP ports, including stations and trunks. These can be
H.323, SIP, or any combination of H.323 and SIP that does not exceed these limits nor the separate
limits for H.323 and SIP, and the separate limits for stations and trunks.

A system configured to support the maximum numbers of IP ports requires that the signaling groups for
the H.323 trunks be administered to use shared signaling. SIP trunks always use shared signaling.

See Communication Manager Hardware and Traffic Guidelines for further details.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

79 Endnote removed.

80 If the capacity of CMS exceeds the capacity of the DEFINITY® server or Communication Manager
server for a single ACD configuration, the server capacity takes precedence. Additional capacity is
provided to support the optional Multi-ACD CMS configuration. The capacities shown for CMS
represent the total capacity across all ACDs (total of 8) supported in a Multi-ACD configuration. ACD
Member/Agent Login capacities reflect the maximum number of CMS measured agent-split/skill pairs,
including AAS ports that can be logged-in across 8 ACDs. Capacities for R3V11 or later CMS assume
a limit of 100K agent-skill pairs. Increased agent-skill pair capacity on CMS increase CMS platform
requirements.

81 Endnote removed.

81.1 Endnote removed. It was replaced by endnote 78.

82 The CM 6.0 servers and H.248 media gateways do not support the TN750C announcement circuit
pack. Customers must upgrade to the VAL (Voice Announcement on LAN) circuit pack, and/or use the
Embedded VAL announcement sources on the media gateways.

83 AAS ports are included in the ACD Members, Logged-In Agents and Logged-In IDs Staffed counts on
the Communication Manager Server system. Only measured logged-in ACD agent-split/skill pairs
(including AAS ports) are counted towards the CMS limits.

84 CMS requires allocation of trunk data structures called unmeasured trunks for tracking of agent-to-
agent, bridging, conference, and transfer call sequences that use capacity from the total. The maximum
values for measured trunks and unmeasured trunk facilities are specified for each ACD in the CMS
Data Storage Allocation window on CMS.

Prior to CMS Release 14, the unmeasured trunks were counted along with the measured trunks toward
the system and ACD allocated trunk limit of a total of 40,000 across all ACDs. The recommended
assignment per ACD for unmeasured trunks was 25% of the measured trunks.

With CMS Release 14 and later the measured trunks and unmeasured trunks are treated separately.
Unmeasured trunks are not subtracted from the maximum measured trunks. Data Storage Allocation
recommends that unmeasured trunks be set at 50% of the measured trunks allocated. The
unmeasured system limit is 20,000 (50% of the measured trunk system limit over all ACDs which is
40,000) and the unmeasured limit for an ACD is 6,000 (50% of the measured trunk CM limit for a single
ACD).

All trunks supported on the Communication Manager platform can be assigned as externally measured
by CMS.

85 Maximum call work codes is the number that can be stored in the call work code tables on CMS. This is
not the maximum number that can be collected in call records.

86 Each Supervisor client session may include CMS ASCII terminals, Supervisor, Visual Vectors and
Network Reporting clients.

87 With Communication Manager Release 4.0 and later, a second pair of MIS TCP/IP links is provided for
connecting Avaya IQ, a reporting adjunct. The first pair of links connects CMS, and the second pair
connects Avaya IQ. You can connect a Communication Manager system to both CMS and Avaya IQ,
with both running the same SPI language. High Availability (HA) is supported on both pairs of MIS links.
HA operation on the first pair runs on 2 CMS systems and HA operation on the second pair runs on 2
Avaya IQ systems. HA between CMS and Avaya IQ is not supported. All reporting adjunct systems
connected to the same Communication Manager system must be running the same SPI language. CC

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

6.0 provides SA9090 that will allow assigning up to 4 of the MIS links for use as CMS links instead of
IQ links.

88 Endnote removed.

89 Endnote removed.

90 The TN2501AP VAL circuit packs and vVAL media gateway sources do not use compression to store
announcements. All announcement files are recorded as wave files (64 Kbps PCM wave files *.wav,
CCITT u-law/a-law, 8 KHz sampling, 8-bit mono). Announcement file storage requires 8 Kbytes per
second of recording time plus approximately 30 bytes for the header.

91 To save the announcement files to a PC, use LAN connectivity and FTP to backup and restore all
active TN2501 VAL circuit packs and Media Gateway embedded vVAL sources. Transfer the
announcements per file to and from the source and a client PC.

92 BRI Link capacity limited to 8.

93 The system requires a fixed length account code between 1 and 15 unless SA7991 Variable Length
Account Codes is enabled.

94 On the Main/Survivable Core Duplex, Main/Survivable Core Simplex, Survivable Remote Simplex 140,
and Survivable Remote Embedded 140 offers with SA7491 enabled, an additional 166 DS1 interfaces
are supported. Use the additional DS1 interfaces for Line Side DS1 connections and not as trunks.

94.1 Limits on other vital system resources such as VoIP resources and tone detectors can block some
media gateway configurations. Traffic engineering should take this into account. The following are
configuration guidelines, not software-defined capacity limits. See Communication Manager Hardware
and Traffic Guidelines for more details.

Total recommended DS1 Circuit Packs, including DS1s on all subtending gateways, for a S8300D
embedded in a gateway.
o G450, G700, G430: 80
o G350: 10
o G250-DS1: 1

95 Station Busy Indicators (SBI) maximum when SA7994 is enabled: 25,000 SBIs are available for the
Main/Survivable Core Duplex, Main/Survivable Core Simplex, Survivable Remote Simplex 140, and
Survivable Remote Embedded 140 offers.

95.1 The following button features share a common resource in memory:

 Call Forwarding All
 Call Forward Busy Don’t Answer
 Send Extension Calls (SAC with extension)
 Station Busy Indicators
 Trunk Group Status
 Hunt Group Status
 Loudspeaker Paging Zone Status
 PCOL Group Status
 Data Module
 Terminating Extension Group Status
 Announcement Status
 Attendant Group Status/DXS
 Remote Trunk Group Select

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

This resource is called Facility Status tracking buttons (Facility Busy Indicators or FBIs). It includes the
following. Maximum SBIs on stations + Maximum Queue status buttons + total DTGS buttons on
Attendants + SBIs on attendants (2 SBIs per attendant).

For the Main/Survivable Core Duplex, Main/Survivable Core Simplex, Survivable Remote Simplex 140,
and Survivable Remote Embedded 140 offers, the FBI maximums are:
 Standard offer: 32,726 =(10,000 + 12000 + (24 DTGS x 414 attds) + (2 x 414 attds)
 With SA7994: 47,726 = (25,000 + 12000 + (24 DTGS x 414 attds) + (2 x 414 attds)
For the Main Embedded SMALL offer, the FBI maximums are:
 Standard offer: 5,868 = 3600 + 500 + (24 DTGS x 68 attds) + (2 x 68 attds).
 No Special Application for the smaller systems.
Each of these individual maximums cannot be exceeded when arriving at total FBIs on the system. For
example, maximum queue status buttons cannot exceed the system maximum, although the SBI
maximum may not be reached in a system.

96 Endnote removed.

97 Endnote removed.

98 Endnote removed.

99 Prefixed extensions can take any length between 2 and 6 digits. Only regular extensions can be the
length specified in the Maximum Extension Size row. The prefixed extension length refers to the
number of dialed digits, not the true extension length. For prefixed extensions of length 2-6, the
corresponding administered true extension lengths range from 1-5.

100 In the code base, this number is known as MAXDAC, the maximum number of dial access codes that
are commonly referred to as Feature Access Codes.

101 This is also limited by license, but that limit is also 41,000.

102 This is the total number of trunks permitted in the system. IP trunks are part of this overall maximum.
However, the maximum number of circuit switched trunks, H.323 trunks, and SIP trunks differ. See
rows Administered ISDN+IP Trunks (pool of ISDN, IP, and SIP trunk Ports)", “Maximum administered
H.323 trunks" and “Administered SIP Trunks" for details.

103 Endnote removed.

104 Extension to Cellular maximums are based on the limits for the station maximums for the specific
software offers

The number of station records can run out before the limit is reached if EC500 users are configured in a
bridging arrangement that requires 3 station records per EC500 user (1 Principal desk set, and 2
XMOBILE stations as bridges of the 2 Call Appearances of the Principal).

105 EC500 / EC500 OPTIM

Station users administered with EC500 count towards the station user maximums set by the software
offer-specific limits. This limit does not include XMOBILE mappings. XMOBILE mappings are limited by
the software-defined station user capacity. On CM 6.0, the EC500 OPTIM user capacity is the same as
the station user maximum for each of the platforms.

106 Location administration allows:

 Remote Port Networks and Remote Offices and Gateways to have different administration than
the main server
 Different settings for Time of Day Offset, Area Code, and Daylight Savings Rules for different
locations

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

 Specific route selection in AAR/ARS administration

Starting 6.3, Location parameters is no longer a single form, a single set of parameter values, for the
entire system. Now, up to 50 location parameter sets can be configured and assigned to locations.

107 Endnote removed.

108 Endnote removed.

109 Endnote removed.

110 Endnote removed.

111 Endnote removed.

112 In CM 6.0, the Increased Adjunct Route Capacity RTU is automatically enabled in licensing for every
switch that has ASAI enabled. While this RTU is OFF in the fixed feature masks for survivable servers
(formerly LSP/ESS), if the feature is ON for the main server, it will be turned ON for any survivable
server subtending the main server.

113 Endnote removed.

114 The Remote Office Feature group, introduced in Communication Manager Release 9.2, provides
connectivity over the WAN.
The maximum Remote Office Gateways is separate and independent from the H.248 Media Gateway
maximum. A system can be configured with all of the following.
 PNs as stated on Maximum Port Networks.
 H.248 media gateways (mix of G430, G450, etc.) as stated on System-wide Maximum H.248
media gateways.
 Remote Offices (MultiTech gateways) as stated on Remote Office Gateways.
The MultiTech gateway is an H.323 managed gateway. From an engineering calculation point-of-view,
one can start with the capacity limits regarding the number of gateways per platform. There is some
interplay to consider. Check Communication Manager server resources for the allowed limits of H.323
endpoints and H.323 trunks.
 The MultiTech gateway's stations are managed as H.323 stations that count as IP stations.
 The MultiTech gateway's trunks are managed as H.323 trunks.
Communication Manager does not perceive the MultiTech gateway to be a gateway for building tables
and associating stations and trunks together for maintenance, administration, and call processing.
Signaling Groups are supported on the Communication Manager platform. The signaling group
limitation is often encountered as the first hard limit. Customers who add gateways to systems that are
heavily loaded with existing stations and trunks sometimes run into limitations on IP station or trunks.
Each customer is different and Avaya account teams must work with customer engineers on system
configuration.

115 Endnote removed.

116 The VSX Video station usually registers to 3 separate extensions as if it were 3 separate stations.

117 Auto/Remote Message Waiting. A Special Application, SA8558, allows a capacity increased to 11,000.

118 VUSTATS: A Special Application, SA8558, allows a maximum of up to 5,000 VUSTATS buttons on the
large servers and increases the number of simultaneously updating displays limit from 500 to 2,000.

119 Intra-Switch CDR: individually administer the endpoints for intra-switch CDR on the intra-switch CDR
form.
SA8202 (Intra-switch CDR by COS) extends the limit to include all the stations supported on a platform.
All phones with the same COS are included in intra-switch CDR reporting.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

120 SIP Enablement Services is no longer supported in CM 6.0. Instead, CM 6.0 works with Session
Manager. The Session Manager capacities document, to be written, contains Session Manager
capacities.

A Communication Manager server can be connected to multiple Session Manager servers.

 TLS Links on Communication Manager: Communication Manager supports a maximum of 49
TLS sessions of any kind
o 17 max may be allocated to AES 32 max may be used by SIP/Session Manager and other
servers such as Meeting Exchange ®. Theoretically there can be a maximum of 32
Session Manager Servers per Communication Manager server. The actual number is
smaller. A signaling connection between a Communication Manager and a Session
Manager pair requires 2 such TLS sessions (one each for Session Manager-originated and
CM-originated traffic) These 2 TLS sessions together, forming the signaling connection
between Communication Manager and Session Manager is called a TLS link, hence a 16
TLS link maximum because of the max 32 sessions. A network can have at most 6 core
Session Manager servers; the remainder would be local Branch Session Manager servers.
TLS links for SIP are independent of AES TLS sessions
121 An Audio Group defines a list of VAL/vVAL sources (circuit pack locations) from which announcement
files are played. An audio group can be assigned to an announcement extension as the source location
instead of a specific single source circuit pack location. When the announcement is to be played, the
closest working source in the list of sources assigned to the audio group is selected to play the named
file assigned to the announcement extension. The same audio group can be assigned as the location
for many announcement extensions, limited by the number of announcement files that can be stored on
any given source. Each file for the announcement extensions must be duplicated in each of the sources
listed for the audio group.

122 The administered announcement files limit is a count of all the sources assigned to defined
announcement extensions that contain an announcement file. With all single-sourced announcements,
the total equals the total extensions defined. (This is the same as without Locally Sourced Music and
Announcements (LSMA)). With group sourced announcements, each source included in the group
defined for the extension is counted towards the limit (i.e., each source a file is in is counted). In a
system with a combination of single sourced and group sourced extensions, each of the single sourced
extensions and the individual sources in the assigned groups are counted towards the limit. For
example, a configuration with 5 single sourced announcement extensions and 2 audio group sourced
extensions with each group listing 10 sources uses 7 announcement extensions and 25 administered
announcement files. The display capacity screen shows both the announcement extensions and
administered files system limits along with the current Used and Available quantities.

123 For Call Center applications, an increase of extension length beyond 8 digits requires an R16 or later
CMS and CM 5.2.1 or later, or use of Avaya IQ.

124 TDM VoIP

Announcement
Gateway Timeslots1 TTR Channels
(pairs) Ports11 Time Files
G250 (analog,
BRI) 113/117 8 7 15 min. 256 10 10
G250
(DCP, DS1) 113/117 16 7 15 min. 256 16 10
G350 234/238 16 7 15 min. 256 32 2
G430 229/237 32 16 45/240 min8. 256 259
G450 206/238 64 64 45/240 min8 1024 80 to 320 7

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

G700 230/238 15 16 20 min. 256 643,5

IG550 1286 32 16 20 min. ? 10/20/80 2,4
124
NOTES:
continued
1. Available timeslot pairs for voice calls (number of simultaneous 2-party calls); first number is
with announcements enabled on the gateway, requiring reserved TDM timeslots (hence G450
with more announcement ports, ends up with fewer available timeslots for voice calls); second
number is available timeslots with no announcement
2. Same number of channels for all Codec and encryption options
3. Number of G.711 unencrypted; for other Codecs and encryption options, refer to CID 123531
4. Capacity depends on VoIP DSP configuration options
5. VoIP channels expandable via MM760, each with 64 additional G.711 channels
6. 128 timeslot pairs to backplane and separate 128 pairs to media processors.
7. Each MP20 provides 25 channels for G.711 or G.726 but only 20 channels for G.729. Each
MP80 provides 80 channels independent of codec. There are four slots for MP boards. The
maximum of 320 active channels requires 4 MP80s.
8. The announcement capacity of the G430 and G450 is 240 minutes (4 hours) when the system
is equipped with compact flash. The announcement capacity is 45 minutes for systems that
have internal flash.
9. The G430 is equipped with on-board DSP having a maximum capacity of 25 VoIP channels for
G.711 or G.726, 20 VoIP channels for G.729 or any combination of the above. There is an
option to add additional DSP resources by using add on boards:
a. A MP10 to increase the channel allotment by 10 for G.711, G.729 and G.726 codecs.
b. A MP20 to increase the channel allotment by 25 channels for G.711 or G.726 or 20
channels for G.729 codec.
c. A MP80 to increase the channel allotment by 80 for G.711, G.729 and G.726 codecs.
The maximum G430 channel allotment with the 25 channels on the motherboard and 80
channels on the optional MP80 is 105.
10. G250 supports VoIP channels for G729/G723 and G.711 with or without Encryption.
o G250-and G250-BRI support
 10 VoIP channels for G729/G723 and G.711
 10 VoIP channels with AES encryption
 8 VoIP channels with SRTP encryption
o G250-DS1 and G250-DCP support
 16 VoIP channels for G729/G723 and G.711
 12 VoIP channels with AES encryption
 10 VoIP channels with SRTP encryption
11. One port is reserved for recording.

125 When the Allow Two Observers in Same Call field on the Feature-Related System-Parameter form
is set to y, two service observers can be in a merged conference call, where the service observers may
be monitoring an EAS LoginID, station extension, or VDN (1 observing the VDN and 1 another type).
Multiple service observers will be counted as conferees in a conference call, but they will not be
included in the actual number of conferenced parties that is shown for the Conference <n> station
display.

This capability allows automated Agent Quality Recording via switch-adjunct products (for example,
Witness or NICE) that use the Service Observing feature to continue recording EAS agents or stations
after two service-observed agents are merged by a call conference (previously the one doing the
recording was stopped) or to be able to have an observer monitor EAS agents or stations for quality

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

while being observed for recording.

If more than 2 service observers are about to be merged for a call-conference operation and a call-
conference occurs with more than two service observers in both call legs, this feature allows the
conference to take place, but only 2 observers will be left in the merged call with an observer in each
call leg.
In this instance, the highest preference is given to keeping the service observer with a Class of
Restriction (COR) with the Service Observing by Recording Device field set to y.

This feature applies to activation using any of the SO FACs (Listen-Only, Listen/Talk and No-Talk) or
SO buttons towards stations/agents. It can not be applied towards VDNs for VDN service observing so
no more than one VDN observer can be on the same call in vector processing. When the call is
connected to an agent, both the VDN observer and the agent observer (or conferenced agent observer)
can be connected.

126 If the number of parties will exceed 6, an observer or additional observer will not be added and/or the
agents are denied adding another conference party.

Capacities with DMCC/CMAPI call recording:

1. Using Service Observe or Single Step Conference – Each observer (recording or manual
observer) counts towards the 6 party limit per call. Example: Only 2 additional conferenced
parties can be added along with the caller and agent with multiple observers (2 recording ports,
or one recording port plus the manual observer).
2. Using Multiple Registrations – Only one party is considered towards the 6 party limit per call.
Example: up to two recording ports register on the agent’s station as additional endpoints.
Communication Manager will not consider these as additional parties on a call, so up to 4
additional parties can be added to a call. Note: as of January, 2008, none of the recording
vendors have demonstrated the ability to use this method which requires Communication
Manager Release 5.0 and AES Release 4.1 or later.

127 There is no process limit to the number of Service Observing associations that can be active in the
system. What will limit service observing is the number of bridged connections involved with an
observed call, the number of observers of the same call (limited to one observer except when the
Allow Two Observers In The Same Call system option is active) and system resources that include
timeslots, inter-gateway connections/links and VoIP resources.

128 Special Application SA8993 allows a maximum of 250 Multiple Listed Directory Numbers.

129 Endnote removed

130 Special Application SA8993 allows a maximum of 250 Tenant Partitions.

131 Special Application SA9035 allows a maximum of 1024 Intercom Groups on the Main/Survivable Core
Duplex, Main/Survivable Core Simplex, Survivable Remote Simplex 140, and Survivable Remote
Embedded 140 offers. Special Application SA9035 allows a maximum of 128 Intercom Groups on the
Main Embedded offer.

132 There is no limit on the maximum number of auto dial buttons, other than the system limit on button
capacity. See row 'Station Button Capacity' for system button limitations.

133 The CM offer limit on SIP trunks simultaneously in use on the CM_Duplex and CM_Simplex templates
is 12,000 for CM Evolution Server (ES) configurations and is up to 24,000 for CM Feature Server (FS)
configurations.

134 With one exception, Communication Manager Messaging for Federal Markets (CMM-FM) has the same
capacities as CMM on the Avaya Aura® Main / Avaya Aura® for Survivable Core (Simplex

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

configuration) template. That exception is Subscriber Mailboxes. CMM-FM supports 15,000 mailboxes.

135 Survivable remote platforms in CM 6.0 are expected to only support SIP trunking to the SM core.
Service provider PSTN SIP trunks are not yet planned to be supported on survivable remote platforms
in CM 6.0. They are planned to be supported in a future release.

136 The capacities shown in these columns assume a large core survivable server backing up a large main
server. In other words, they assume the following settings on the Server Role page's "Configure
Memory" fields.
 The "This Server's Memory Setting" field is set to Large.
 If the server role field is set to one of the survivable roles (formerly LSP and ESS) then the
server also has the "Main Server's Memory Setting" field set to Large.

137 The capacities shown in this column assume a small main server. In other words, they assume the
following settings on the Server Role page.
 The server's role is set to Main.
 The "This Server's Memory Setting" field under "Configure Memory" is set to Small.

138 The capacities shown in this column assume a small survivable server backing up a remote part of a
large core server. In other words, they assume the following settings on the Server Role page.
 The "This Server's Memory Setting" field under "Configure Memory" is set to Small.
 The server role field is set to one of the survivable roles (formerly LSP or ESS)
 The "Main Server's Memory Setting" field under "Configure Memory" is set to Large.

If you want to know what the capacities would be for a small survivable backing up a small main, read
the (CM_onlyEmbed) column immediately to the left. In other words, if "This Server's Memory Setting"
is Small, and "Main Server's Memory Setting" is also Small, the resulting survivable server's capacities
are the same as those of a small main server.

139 For survivable remote server software capacities, this document uses the term 'administered' as seen
from two different points of view.
1. The way people and marketing offers commonly use the term.
2. The way CM software uses the term.
For example, suppose a CM system has a large main server at headquarters and two small survivable
servers, one at each of two distant remote branches. Person A moves from one phone to another
phone, both within branch A.
1. From a marketing offer point of view, person A's station is only used in branch A. From a
marketing offer point of view, the only survivable server that needs to have this station counted
towards the station limits is the survivable server in branch A.
2. However, from CM software's point of view, CM station translations, including A's phone move,
are updated through the headquarters main server. That main server downloads the complete
set of revised station translations to all survivable remote branches. The survivable server in
branch B receives that complete set of translations. From CM server B's point of view, those
translations include person A's extension information. Server B counts that extension towards
server B's administered station capacity limit.
That is why this document's software capacity limits for some items in the survivable remote server
columns are higher than similar limits in the adjacent marketing Offer Limit rows.

140 Endnote removed.

141 IP Soft Consoles are included in the Maximum Concurrently Registered IP stations limit.

142 When tenant partitioning is enabled for the system, you can administer up to 100 COS groups, each
with 16 Classes of Service. The command line changes from “change cos x” to “change cos-group n”.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

143 Implementing End-to-End SIP, Issue 1, December 2011, Compas ID 154835

144 SA9115 increases the number of entries in the ip-network-map table from 500 to 4000.

145 CAG capacity has been increased for LARGE systems and members in a CAG has been increased
across the board for all platforms. The SA9123 allows CAGs that are adjacent in a coverage path to
have the same extensions.

146 CM 6.2.5 (6.2 FP1) is now available as a virtual appliance on VMware. This is called CM VE (Virtual
Enablement). During installation of CM-VE, the memory footprint can be configured as LARGE,
MEDIUM or SMALL. The capacities of CM-VE is same as that of CM deployed over System Platform.

147 CM can be deployed using a LARGE, MEDIUM or SMALL footprint. HW requirements and capacity of
the system are dependent on the memory footprint / size. Please note that there are additional factors
that determine the capacity of a CM – including whether it is operating as a Main server or survivable
server.

148 IP Network regions and Locations have been increased from 250 to 2000 to support Large enterprises
that have multiple branch sites. It is available only with LARGE memory footprint.

The existing network regions 1 to 250 are referred to as CORE network regions, the new ones 251 to
2000 are referred to as STUB network regions. The Core network regions can have media resources
and endpoints. The Stubs can only have endpoints and act as far-end of a signaling group. They
cannot have any media resource. Every stub region MUST be connected to a core region for its media
requirements. A stub region can be connected to only 1 core region.

149 Number of switch classified calls is not platform dependent, but to classify a call, call classification
resources are needed. Number of call classification resources in a system is dependent on the
platform. See footnote 39 and 124.

150 Dial Plan Analysis is per location. Every dial plan analysis (DPA) form supports a max of 12 pages x 45
entries per page = 540. The all-location DPA form allows entries with any call type; the per-location
DPA form allows only the udp call type. The max number of DPA entries is limited by capacity form field
AAR/ARS Analysis Entries and is 16000.

151 10 CES servers can be administered if CES servers are directly connected to CM over a SIP signaling
group. However 22 CES servers can be supported if CES servers are connected to SM and then
aggregated over a signaling group to CM.
Note: Max limit of 22 CES is applicable only if H.323 or DCP stations are configured on Communication
Manager. If number of SIP station configured on Communication Manager increases, then the number
of maximum CES server supported will decrease.

152 40K channels is the CM license file limit. This is the number of audio channels that can be established
from CM to the set of configured AMSs. The licensed limit is independent of the codec types used.
Individual media server channel capacity is a function of the server type, cpu-speed, memory
configuration, processor architecture and codec types used
TLS for H.323 IP stations is introduced only for JITC customers.

153 For CM Duplex server or equivalent

154 For CM High Duplex server or equivalent

155 For a CSR1 or CSR2 equivalent server

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura® Communication Manager and Call Center Release 7.0

System Capacities – Endnotes

Endnote Detailed Description

156 For S8300D or equivalent server configuration

157 For S8300E or equivalent server configuration

158 This offer is for migration of Midsize Enterprise template from 6.3.x to Aura 7.

159 Offline call log feature stores call log entries for H.323 users who are not registered. When they register
back to Communication Manager, Communication Manager pushes the call log entries to the endpoint.
The buffer holds up to 10 entries per user subject to the system limit mentioned in the capacity table.
The offline call log entries are stored on FIFO (First In, First Out) basis.

At a user level, if the buffer is full with 10 log entries and another call activity takes place,
Communication Manager removes the oldest entry to make room for the latest entry. At the system
level, if the buffer is full with call log entries and another call activity takes place, Communication
Manager removes the oldest record at the system level to make room for the latest entry. The entry to
be removed may belong to a user who has not yet reached the individual max call log entries limit.

160 The maximum number of simultaneous calls where out-of-band DTMF is received and needs to be
retransmitted to the far end either as in-band DTMF or out-of-band DTMF counts against this limit. The
parties involved in the call can be stations or trunks of any protocol, such as DCP, H.323 or SIP.

Avaya Aura® Communication Manager System Capacities Table August 2015

Avaya Aura Communication Manager System Capacities Table R10.1 Dec2021
No ratings yet
Avaya Aura Communication Manager System Capacities Table R10.1 Dec2021
71 pages
Using AACC Reports and Displays - 07.04 - October 2020
No ratings yet
Using AACC Reports and Displays - 07.04 - October 2020
158 pages
Administering POMUsing Avaya Control Manager
No ratings yet
Administering POMUsing Avaya Control Manager
50 pages
AIC 734 ReleaseNotes
No ratings yet
AIC 734 ReleaseNotes
166 pages
Avaya Aura Conferencing Port Matrix
No ratings yet
Avaya Aura Conferencing Port Matrix
59 pages
DevLink3 IPOffice R11 - 1-I1 - 1
No ratings yet
DevLink3 IPOffice R11 - 1-I1 - 1
30 pages
Avaya Interaction Center Service Pack Release Notes R7.3.11
No ratings yet
Avaya Interaction Center Service Pack Release Notes R7.3.11
190 pages
Avaya Communicator For Web
No ratings yet
Avaya Communicator For Web
104 pages
Administering Avaya E129 SIPDeskphone
No ratings yet
Administering Avaya E129 SIPDeskphone
93 pages
AACC Terminology - 07.01 - June - 2019
No ratings yet
AACC Terminology - 07.01 - June - 2019
90 pages
Avaya Aura Contact Center Overview and Specification
No ratings yet
Avaya Aura Contact Center Overview and Specification
445 pages
AACCandAvayaCommunicationServer1000SolutionDescription 01.06 July 2018
No ratings yet
AACCandAvayaCommunicationServer1000SolutionDescription 01.06 July 2018
50 pages
Maintaining AACC - 07.03 - September - 2019
No ratings yet
Maintaining AACC - 07.03 - September - 2019
96 pages
AvayaIPOffice PlatformSolutionDescription
No ratings yet
AvayaIPOffice PlatformSolutionDescription
151 pages
RN8139
No ratings yet
RN8139
393 pages
AACC Commissioning For Avaya Communication Server 1000 - 07.01 - June - 2019
No ratings yet
AACC Commissioning For Avaya Communication Server 1000 - 07.01 - June - 2019
308 pages
HardwareDescription 167500
No ratings yet
HardwareDescription 167500
1,480 pages
POM4 Rest
No ratings yet
POM4 Rest
442 pages
Administering Avaya IPOffice With Manager
No ratings yet
Administering Avaya IPOffice With Manager
1,091 pages
Getting Started With Avaya Aura Orchestration Designer
No ratings yet
Getting Started With Avaya Aura Orchestration Designer
51 pages
Utility Services 7.1
No ratings yet
Utility Services 7.1
99 pages
IPOCC9 1 7InstallationTaskBasedGuideIssue1 0
No ratings yet
IPOCC9 1 7InstallationTaskBasedGuideIssue1 0
503 pages
Avaya Aura System Manager Overview and Specification Release 81x Issue8 Feb08 2021
No ratings yet
Avaya Aura System Manager Overview and Specification Release 81x Issue8 Feb08 2021
71 pages
Avaya Interaction Center: Administration Guide
No ratings yet
Avaya Interaction Center: Administration Guide
657 pages
Avaya Aura Communication Manager DenialEvents 7 0
No ratings yet
Avaya Aura Communication Manager DenialEvents 7 0
200 pages
Administering Avaya Aura Messaging
No ratings yet
Administering Avaya Aura Messaging
588 pages
Using Avaya Agent For Desktop: Release 2.0.0 Issue 1.1 October 2019
No ratings yet
Using Avaya Agent For Desktop: Release 2.0.0 Issue 1.1 October 2019
56 pages
Avaya Aura 7 - 0 - 1 - 2 Release Notes I2
No ratings yet
Avaya Aura 7 - 0 - 1 - 2 Release Notes I2
254 pages
AvayaAura Upgrading SystemManager To 7 X Release713 Issue08 Dec 27 2018N
No ratings yet
AvayaAura Upgrading SystemManager To 7 X Release713 Issue08 Dec 27 2018N
218 pages
Using Avaya J139 IP Phone in An Avaya Cloud Office - Issue2
No ratings yet
Using Avaya J139 IP Phone in An Avaya Cloud Office - Issue2
74 pages
Administering Avaya H100 Series Video Collaboration Stations
No ratings yet
Administering Avaya H100 Series Video Collaboration Stations
81 pages
Administering AAM7.0.0
No ratings yet
Administering AAM7.0.0
544 pages
Using Avaya Workspaces For AACC and ACCS - 01.02 - July - 2019
No ratings yet
Using Avaya Workspaces For AACC and ACCS - 01.02 - July - 2019
53 pages
Maintaining and Troubleshooting Avaya Aura Conferencing
No ratings yet
Maintaining and Troubleshooting Avaya Aura Conferencing
295 pages
Maintaining Avaya Aura Session Manager 7.1
No ratings yet
Maintaining Avaya Aura Session Manager 7.1
139 pages
Documentation Catalog For Avaya Aura R8.0 July 2018
No ratings yet
Documentation Catalog For Avaya Aura R8.0 July 2018
22 pages
AACC and Avaya Aura Unified Communications Solution Description - 02.07 - April - 2022
No ratings yet
AACC and Avaya Aura Unified Communications Solution Description - 02.07 - April - 2022
114 pages
Avaya Aura 10 1 X X Release Notes Issue 22 August 2023
No ratings yet
Avaya Aura 10 1 X X Release Notes Issue 22 August 2023
196 pages
Overview and Specification For Avaya Aura Conferencing (Turnkey)
No ratings yet
Overview and Specification For Avaya Aura Conferencing (Turnkey)
97 pages
AvayaAura Administering SystemManager Rls 8 1 X Issue 26 Feb 2023
No ratings yet
AvayaAura Administering SystemManager Rls 8 1 X Issue 26 Feb 2023
1,594 pages
Avaya Communication Manager Administering R8.1.2 Mar2020
No ratings yet
Avaya Communication Manager Administering R8.1.2 Mar2020
521 pages
AACC and Avaya Aura Unified Communications Platform Integration - 07.06 - September - 2021
No ratings yet
AACC and Avaya Aura Unified Communications Platform Integration - 07.06 - September - 2021
238 pages
Deploy Session MGR in Virtualized Env Release 10.1 Issue2 Mar 2022
No ratings yet
Deploy Session MGR in Virtualized Env Release 10.1 Issue2 Mar 2022
77 pages
Using Collaboration Agent
No ratings yet
Using Collaboration Agent
94 pages
ACCS Advanced Administration - 03.07 - April - 2022
No ratings yet
ACCS Advanced Administration - 03.07 - April - 2022
424 pages
InstallingandMaintainingAvayaH100 Series
No ratings yet
InstallingandMaintainingAvayaH100 Series
70 pages
CMSdocroadmap Nov3
No ratings yet
CMSdocroadmap Nov3
10 pages
ImplementingAvayaProactiveOutreachManager4 0 115mar2022
No ratings yet
ImplementingAvayaProactiveOutreachManager4 0 115mar2022
152 pages
Upgrading Avaya Aura Conferencing
No ratings yet
Upgrading Avaya Aura Conferencing
284 pages
Avaya IP Office Platform Short Code and Button Action Reference - en
No ratings yet
Avaya IP Office Platform Short Code and Button Action Reference - en
233 pages
AvayaAura®DocumentationCatalog R10.1x Issue2 Feb2023
No ratings yet
AvayaAura®DocumentationCatalog R10.1x Issue2 Feb2023
20 pages
Using Avaya H175 Video Collaboration Station: Release 1.0.2 April 2016
No ratings yet
Using Avaya H175 Video Collaboration Station: Release 1.0.2 April 2016
176 pages
Avaya Aura 81xx Release Notes Issue 1 52 Aug 07 2023
No ratings yet
Avaya Aura 81xx Release Notes Issue 1 52 Aug 07 2023
391 pages
Using Conference Manager For Outlook
No ratings yet
Using Conference Manager For Outlook
24 pages
Avaya Aura Core Solution Description
No ratings yet
Avaya Aura Core Solution Description
219 pages
Migrating Avaya Aura Conferencing
No ratings yet
Migrating Avaya Aura Conferencing
210 pages
Avaya Aura Messaging Overview and Specification R7.2.0 November 2021
No ratings yet
Avaya Aura Messaging Overview and Specification R7.2.0 November 2021
119 pages
Vantage Ug
No ratings yet
Vantage Ug
61 pages
Using Avaya B189 IP Conference Phone
No ratings yet
Using Avaya B189 IP Conference Phone
39 pages
AWS Certified Developer Associate Step by Step Certification Study Guide, to Pass the Developers Exam With Confidence
From Everand
AWS Certified Developer Associate Step by Step Certification Study Guide, to Pass the Developers Exam With Confidence
Jamie Murphy
No ratings yet
Admin Exam Practice Test Webassesoe
No ratings yet
Admin Exam Practice Test Webassesoe
27 pages
Pmis Presentation 1
No ratings yet
Pmis Presentation 1
19 pages
Unit 1. The Digital Age
No ratings yet
Unit 1. The Digital Age
63 pages
Ad Solutions Brochure
No ratings yet
Ad Solutions Brochure
4 pages
K 2 BW1292
No ratings yet
K 2 BW1292
20 pages
Mid-Term Participation Proposal - Instructions
No ratings yet
Mid-Term Participation Proposal - Instructions
3 pages
Thủ tục đã cấu hình trên OLT
No ratings yet
Thủ tục đã cấu hình trên OLT
2 pages
141-Smasher HTB Official Writeup Tamarisk
No ratings yet
141-Smasher HTB Official Writeup Tamarisk
23 pages
(Ebook PDF) Internet of Things and Data Analytics Handbook PDF Download
100% (5)
(Ebook PDF) Internet of Things and Data Analytics Handbook PDF Download
57 pages
Ms Word Assignments Desjardins
No ratings yet
Ms Word Assignments Desjardins
2 pages
PME - DC - Ed - Commissioning - Guide 7EN02-0385-00
No ratings yet
PME - DC - Ed - Commissioning - Guide 7EN02-0385-00
142 pages
Electronic Commerce Research and Applications: Mehmet Türkay Yoldar, U Ğur Özcan T
No ratings yet
Electronic Commerce Research and Applications: Mehmet Türkay Yoldar, U Ğur Özcan T
17 pages
The Need For A Protocol Architecture - 296
No ratings yet
The Need For A Protocol Architecture - 296
2 pages
Using The WAGO 750-340 PROFINET Coupler As Remote I/O With A Siemens S7 PLC
No ratings yet
Using The WAGO 750-340 PROFINET Coupler As Remote I/O With A Siemens S7 PLC
30 pages
Bizhub 4020 DataSheet
No ratings yet
Bizhub 4020 DataSheet
4 pages
MIT APP Inventor Extension
No ratings yet
MIT APP Inventor Extension
7 pages
Ubantu Basic Commands
No ratings yet
Ubantu Basic Commands
28 pages
Cisco Sd-Wan: Secure Multicloud and Saas
No ratings yet
Cisco Sd-Wan: Secure Multicloud and Saas
41 pages
Interskill Learning Course Assessment List
100% (1)
Interskill Learning Course Assessment List
5 pages
XXX Archita Pukham Video
No ratings yet
XXX Archita Pukham Video
3 pages
Dameware Server Administrator Guide
No ratings yet
Dameware Server Administrator Guide
60 pages
Diploma in Information Technology Coursework: Subject: Web Design Subject Code: DIT2283
No ratings yet
Diploma in Information Technology Coursework: Subject: Web Design Subject Code: DIT2283
15 pages
VDC Part 1
No ratings yet
VDC Part 1
4 pages
7.4.2.4 Packet Tracer - Server Firewalls and Router ACLs
No ratings yet
7.4.2.4 Packet Tracer - Server Firewalls and Router ACLs
5 pages
Building Information Modelling (BIM) User Guide For Development and Construction Division of Hong Kong Housing Authority PDF
No ratings yet
Building Information Modelling (BIM) User Guide For Development and Construction Division of Hong Kong Housing Authority PDF
53 pages
Chat
No ratings yet
Chat
109 pages
CMC Reviewer - 032251
No ratings yet
CMC Reviewer - 032251
4 pages
Unit Iii Iaia
No ratings yet
Unit Iii Iaia
16 pages
Lower Secondary English Paper B
No ratings yet
Lower Secondary English Paper B
11 pages
Tascr Manager Proposal: Roposal Ummary
No ratings yet
Tascr Manager Proposal: Roposal Ummary
2 pages