0% found this document useful (0 votes)

60 views86 pages

Sys Cap Table

The document outlines the system capacities for Avaya Aura Communication Manager Release 6.3, detailing various license types and their usage limitations. It highlights significant increases in capacities such as the number of simultaneous calls, SIP agents, and network regions compared to previous releases. Additionally, it includes disclaimers regarding warranties, documentation accuracy, and toll fraud prevention measures.

Uploaded by

konri75

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)

60 views86 pages

Sys Cap Table

Uploaded by

konri75

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/ 86

Avaya Aura® Communication

Manager System Capacities Table

Release 6.3

Release 6.3
03-300511
Issue 4
June 2014
© 2014 Avaya Inc. Concurrent User License (CU). End User may install and use the Software on
All Rights Reserved. multiple Designated Processors or one or more servers, so long as only the
licensed number of Units are accessing and using the Software at any given
Notice time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the
While reasonable efforts have been made to ensure that the information in this pricing of its licenses and can be, without limitation, an agent, port or user, an
document is complete and accurate at the time of printing, Avaya assumes no e-mail or voice mail account in the name of a person or corporate function
liability for any errors. Avaya reserves the right to make changes and (e.g., webmaster or helpdesk), or a directory entry in the administrative
corrections to the information in this document without the obligation to notify database utilized by the Software that permits one user to interface with the
any person or organization of such changes. Software. Units may be linked to a specific, identified Server.
Database License (DL). End User may install and use each copy of the
Documentation disclaimer
Software on one Server or on multiple Servers provided that each of the
“Documentation” means information published by Avaya in varying mediums Servers on which the Software is installed communicates with no more than a
which may include product information, operating instructions and performance single instance of the same database.
specifications that Avaya generally makes available to users of its products.
CPU License (CP). End User may install and use each copy of the Software
Documentation does not include marketing materials. Avaya shall not be
on a number of Servers up to the number indicated in the order provided that
responsible for any modifications, additions, or deletions to the original
the performance capacity of the Server(s) does not exceed the performance
published version of this documentation unless such modifications, additions,
capacity specified for the Software. End User may not re-install or operate the
or deletions were performed by Avaya. End User agrees to indemnify and hold
Software on Server(s) with a larger performance capacity without Avaya’s prior
harmless Avaya, Avaya's agents, servants and employees against all claims,
consent and payment of an upgrade fee.
lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation, to the Named User License (NU). You may: (i) install and use the Software on a
extent made by End User. single Designated Processor or Server per authorized Named User (defined
below); or (ii) install and use the Software on a Server so long as only
Link disclaimer authorized Named Users access and use the Software. “Named User” means
Avaya is not responsible for the contents or reliability of any linked websites a user or device that has been expressly authorized by Avaya to access and
referenced within this site or documentation provided by Avaya. Avaya is not use the Software. At Avaya's sole discretion, a “Named User” may be, without
responsible for the accuracy of any information, statement or content provided limitation, designated by name, corporate function (e.g., webmaster or
on these sites and does not necessarily endorse the products, services, or helpdesk), an e-mail or voice mail account in the name of a person or corporate
information described or offered within them. Avaya does not guarantee that function, or a directory entry in the administrative database utilized by the
these links will work all the time and has no control over the availability of the Software that permits one user to interface with the Software.
linked pages. Shrinkwrap License (SR). You may install and use the Software in
accordance with the terms and conditions of the applicable license
Warranty agreements, such as “shrinkwrap” or “clickthrough” license accompanying or
Avaya provides a limited warranty on its hardware and Software (“Product(s)”). applicable to the Software (“Shrinkwrap License”).
Refer to your sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language, as well as information regarding Heritage Nortel Software
support for this product, while under warranty is available to Avaya customers “Heritage Nortel Software” means the software that was acquired by Avaya as
and other parties through the Avaya Support website: part of its purchase of the Nortel Enterprise Solutions Business in December
http://support.avaya.com. 2009. The Heritage Nortel Software currently available for license from Avaya
Please note that if you acquired the Product(s) from an authorized Avaya is the software contained within the list of Heritage Nortel Products located at
reseller outside of the United States and Canada, the warranty is provided to http://support.avaya.com/LicenseInfo/ under the link “Heritage Nortel
you by the said Avaya reseller and not by Avaya. “Software” means computer Products”. For Heritage Nortel Software, Avaya grants Customer a license to
programs in object code, provided by Avaya or an Avaya Channel Partner, use Heritage Nortel Software provided hereunder solely to the extent of the
whether as stand-alone products or pre-installed on hardware products, and authorized activation or authorized usage level, solely for the purpose specified
any upgrades, updates, bug fixes, or modified versions thereto. in the Documentation, and solely as embedded in, for execution on, or (in the
event the applicable Documentation permits installation on non-Avaya
Licenses equipment) for communication with Avaya equipment. Charges for Heritage
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, Nortel Software may be based on extent of activation or use authorized as
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO specified in an order or invoice.
ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA
Copyright
SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR
AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A Except where expressly stated otherwise, no use should be made of materials
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA on this site, the Documentation, Software, or hardware provided by Avaya. All
RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, content on this site, the documentation and the Product provided by Avaya
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS including the selection, arrangement and design of the content is owned either
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE by Avaya or its licensors and is protected by copyright and other intellectual
OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT property laws including the sui generis rights relating to the protection of
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR databases. You may not modify, copy, reproduce, republish, upload, post,
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, transmit or distribute in any way any content, in whole or in part, including any
DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS code and software unless expressly authorized by Avaya. Unauthorized
TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR reproduction, transmission, dissemination, storage, and or use without the
WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE express written consent of Avaya can be a criminal, as well as a civil offense
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS under the applicable law.
“YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR
THE APPLICABLE AVAYA AFFILIATE (“AVAYA”). Virtualization
Avaya grants you a license within the scope of the license types described Each virtual appliance has its own ordering code. Note that each instance of a
below, with the exception of Heritage Nortel Software, for which the scope of virtual appliance must be ordered separately. If the end-user customer or
the license is detailed below. Where the order documentation does not Business Partner wants to install two of the same type of virtual appliances,
expressly identify a license type, the applicable license will be a Designated then two virtual appliances of that type must be ordered.
System License. The applicable number of licenses and units of capacity for
which the license is granted will be one (1), unless a different number of
licenses or units of capacity is specified in the documentation or other materials Third Party Components
available to you. “Designated Processor” means a single stand-alone Certain software programs or portions thereof included in the Software may
computing device. “Server” means a Designated Processor that hosts a contain software (including open source software) distributed under third party
software application to be accessed by multiple users. agreements (“Third Party Components”), which may contain terms that expand
or limit rights to use certain portions of the Software (“Third Party Terms”).
License type(s) Information regarding distributed Linux OS source code (for those product that
Designated System(s) License (DS). End User may install and use each have distributed Linux OS source code), and identifying the copyright holders
copy of the Software only on a number of Designated Processor up to the of the Third Party Components and the Third Party Terms that apply is
number indicated in the order. Avaya may require the Designated Processor(s) available in the Documentation or on Avaya’s website at:
to be identified in the order by type, serial number, feature key, location or other http://support.avaya.com/ThirdPartyLicense/
specific designation, or to be provided by End User to Avaya through electronic You agree to the Third Party Terms for any such Third Party Components.
means established by Avaya specifically for this purpose.
Preventing Toll Fraud
“Toll fraud” is the unauthorized use of your telecommunications system by an
unauthorized party (for example, a person who is not a corporate employee,
agent, subcontractor, or is not working on your company's behalf). Be aware
that there can be a risk of Toll Fraud associated with your system and that, if
Toll Fraud occurs, it can result in substantial additional charges for your
telecommunications services.

Avaya Toll Fraud Intervention

If you suspect that you are being victimized by Toll Fraud and you need
technical assistance or support, call Technical Service Center Toll Fraud
Intervention Hotline at +1-800-643-2353 for the United States and Canada. For
additional support telephone numbers, see the Avaya Support website:
http://support.avaya.com. Suspected security vulnerabilities with Avaya
products should be reported to Avaya by sending mail to:
[email protected].

Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this site, the
Documentation 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 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 the registered trademarks of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners, and
"Linux" is a registered trademark of Linus Torvalds.

Downloading documents
For the most current versions of documentation, see the Avaya Support
website: http://support.avaya.com.

Contact Avaya Support

See the Avaya Support website: http://support.avaya.com for product notices
and articles, or to report a problem with your Avaya product.
For a list of support telephone numbers and contact addresses, go to
the Avaya Support website: http://support.avaya.com, scroll to the
bottom of the page, and select Contact Avaya Support.
INTRODUCTION
®
This document contains the Avaya Aura Communication Manger Release 6.3 system software-defined capacities information for all templates of
Communication Manager, 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 Communication Manager, Release 6.3. The offer limits are
highlighted in tan for easy identification. They are enforced by license files and by the Avaya support policy.
The capacities table in this document is the basis for the offer-based system capacities table posted on the Avaya website which is accessed by
the Avaya sales people, offer managers and customers. The document shows only the offer limits when the offer limits are less than the
corresponding software limits.
Because the information compiled here is obtained from various sources, the authors appreciate review of the document by a wider audience. This
helps reduce errors and inconsistencies and refine the information contained in these tables. MRs must be written against this document for
changes related to the capacities table.
Highlights of Communication Manager Release 6.3
See the capacities table for details. Communication Manager Release 6.3 introduces:
 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 in 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. The maximum 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.
 The VE offer. See footnote 146.

Highlights of Communication Manager Release 6.2

See the capacities table for details. Communication Manager Release 6.2 introduces:
 Increase in the offer limit for SIP endpoints (stations) from 18,000 to 36,000 for general business configurations.
 Increase in the number of Crisis Alert buttons for special application SA8608 from 250 to 750. Increase in the “Max number of Bridges
to a Principal’s Call Appearance from 25 to 63 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
 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)
140
o Avaya Aura® for Survivable Remote Simplex configuration (CM_SurvRemote )
o Avaya Aura® Main Embedded configuration (CM_onlyEmbed)
o Avaya Aura® for Survivable Remote Embedded configuration (CM_SurvRemoteEmbed 140)
 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, 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, G350 gateways

Highlights of Communication Manager Release 5.2.1

See the capacities table for details. Communication Manager Release 5.2.1 introduces:
 The 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
 A 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.

Highlights of Communication Manager Release 3.1

See the capacities table 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 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
screen.
 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Highlights of Communication Manager Release 2.2
See the capacities table 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.
 G350 in Call Center Applications: the G350 can be used in both ICC (S8300/G350) and ECC (as media gateway and survivable remote
1 2
(formerly LSP)). See footnotes [ ] and [ ] 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.

1
Tone Detectors: G700 and G350 have a limit of 15 Tone Detectors, which is sufficient for most call center applications consid ering 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 and Call Center Release 6.3 System Capacities Table June 2014
 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
template.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Row CM Capacity Item Avaya Aura® ™ for
Main / Main / Survivable Main Survivable Remote Midsize
Survivable Survivable Core Remote Simplex Embedded Embedded Enterprise
Core Duplex Simplex (CM_SurvRemote) (CM_onlyEmb (CM_SurvRemoteE (Midsize_Ent)
136 136 136 137 138 146, 147
(CM_Duplex) (CM_Simplex) ed) mbed) MEDIUM
146, 147 146, 147 146, 147 146, 147 146, 147
LARGE LARGE LARGE SMALL SMALL
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 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 Avaya Aura® Contact Center Planning Engineering Guide (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
68
70 AD Lists per System 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 both enhanced
100 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
Max entries per
110 list 100 100 100 100 100 100
Group lists /
115 extension 3 3 3 3 3 3

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
CMS Capacities

R17.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 500,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 250
CMS - 14 Logged-in Agent-Split/Skill Pairs over 8 ACDs 200,000
CMS - 15 Logged-in Agent-Split/Skill Pairs per ACD 100,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 40,000
CMS - 19 Measured Trunks per ACD (R14 and Later) 84 12,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

Avaya Aura® Communication Manager and Call Center Release 6.3

System Capacities Table June 2014
Endnotes
The capacities table for Communication Manager Release 6.3 contains the offer limits for Communication Manager. 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 the end-of-sale of platforms such as G3R and G3si, see the introduction and the notes at the beginning of the capacities
table.

Endnote Detailed Description

* The software-defined capacity might not be reachable due to hardware limits or processor capacity
limits or both 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 row states the number of simultaneous sessions each template 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 Communication Manager Release 6.0 support for

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

fiber connections uses only 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 CM_Duplex, CM_Simplex,
140 140
CM_SurvRemote , and CM_SurvRemoteEmbed templates. SA9050 provides 8 routing plans and
time of day charts on the CM_onlyEmbed template.

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.

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 need to 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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
140
is 5,000 for the CM_onlyEmbed and CM_SurvRemoteEmbed templates and 15,000 for the
140
CM_Duplex, CM_Simplex, and CM_SurvRemote templates.

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
®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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 the 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 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 CM_onlyEmbed and CM_SurvRemoteEmbed 140 templates, 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 the 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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.
140
For the CM_onlyEmbed and CM_SurvRemoteEmbed templates, 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 templates.
27 Integrated Directory Entries = stations + attendant consoles.

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

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

28.2 Endnote removed.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

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 CM_Duplex, CM_Simplex, CM_onlyEmbed and
140 140
and CM_SurvRemote CM_SurvRemoteEmbed
templates templates
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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

32 These numbers are node number addresses.

33 Special Application SA8927 increases the number of speakerphone paging groups to 999 on the
140 140
CM_Duplex, CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed templates, and to 256
on the onlyEmbed template.

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.

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

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 CM_onlyEmbed or
CM_SurvRemoteEmbed 140 template 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 CM_Duplex,
140 140
CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed templates, but leaves it at 240 on
the CM_onlyEmbed template.

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

 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 can
not 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.

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description
140 140
trunks on the CM_Duplex, CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed
templates, and 50 x 16 = 800 trunks on the CM_onlyEmbed template. 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 31

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

1
To avoid changing the Channel Block Management (large blocks vs small blocks) strategy, this will be left as 3 slots.
®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

requires an external data module.

45 Capacities depend upon the version of IP phones.

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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
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 Offer Limit:
Maximum Concurrently Registered H.323 Stations rows. 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.
®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

58 Endnote removed.

59 Endnote removed.

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

61 For the CM_onlyEmbed and CM_SurvRemoteEmbed 140 templates, 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 and Call Center Release 6.3 System Capacities Table June 2014
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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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 to Data  6000 total trunks, in disaster mode to Data
Center 1 Center 2
 SBC load balances traffic between SBC1  SBC load balances traffic between SBC3
and SBC 2 (3000 to each) and SBC 4 (3000 to each)
 In event of SM failure remaining SM must take all  In event of SM failure remaining SM must
6000 calls take all 6000 calls
 CM needs 6000 trunks to each SM in DC1  CM needs 6000 trunks to each SM in DC2

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
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 CM_Duplex, CM_Simplex, and CM_SurvRemote140 templates.

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. Communication Manager 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

The CM_onlyEmbed and CM_SurvRemoteEmbed 140 templates don't use the TN-pack based IP Media
Resources TN2302AP and TN2602AP. This is because TN packs need port networks, but S8300D
140
does not support port networks. The CM_onlyEmbed and CM_SurvRemoteEmbed templates' 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 Media Servers
Connect  IP- Fiber (CSS) Comments
1
Gateways Connect Connect
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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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
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 

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

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
®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

93 The system requires a fixed length account code between 1 and 15 unless SA7991 Variable Length
Account Codes is enabled.
140 140
94 On the CM_Duplex, CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed templates 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
CM_Duplex, CM_Simplex, CM_SurvRemote140, and CM_SurvRemoteEmbed 140 templates.

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

This resource is called Facility Status tracking buttons (Facility Busy Indicators or FBIs). It includes the

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

following. Maximum SBIs on stations + Maximum Queue status buttons + total DTGS buttons on
Attendants + SBIs on attendants (2 SBIs per attendant).
140 140
For the CM_Duplex, CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed templates, 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 CM_onlyEmbed template, 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 can not be exceeded when arriving at total FBIs on the system. For
example, maximum queue status buttons can not 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
templates

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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 template-
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
 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

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

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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
o 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 if the Session Manager
servers are duplicated servers. 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.
o 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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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.

TDM VoIP
124 Announcement
Gateway Timeslots
1
TTR Channels
11
(pairs) Ports Time Files
G250 (analog,
10
BRI) 113/117 8 7 15 min. 256 10
G250
10
(DCP, DS1) 113/117 16 7 15 min. 256 16
2
G350 234/238 16 7 15 min. 256 32
8 9
G430 229/237 32 16 45/240 min . 256 25
G450 206/238 64 64 45/240 min8 1024 80 to 320 7
G700 230/238 15 16 20 min. 256 643,5
6 2,4
IG550 128 32 16 20 min. ? 10/20/80
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. G430 is equipped with an on-board DSP that has the capacity to support 25 VoIP channels for

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

G.711 or G.726, 20 VoIP channels for G.729, or a combination of both. There is an option to
add more DSP resources by using add-on boards:
a. MP10 to increase the channel allotment by 10 for G.711, G.729, and G.726 codecs.
b. MP20 to increase the channel allotment by 25 channels for G.711 or G.726 codec or
20 channels for G.729 codec
c. 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
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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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 CM_Duplex,
140 140
CM_Simplex, CM_SurvRemote , and CM_SurvRemoteEmbed templates. Special Application
SA9035 allows a maximum of 128 Intercom Groups on the CM_onlyEmbed template.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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
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"

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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

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.

®
Avaya Aura Communication Manager and Call Center Release 6.3 System Capacities Table June 2014
Endnote Detailed Description

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 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.
151 The maximum number of simultaneous calls where out-of-band DTMF is received and needs to be re-
transmitted 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 and Call Center Release 6.3 System Capacities Table June 2014

Computer MCQs For Pharmacy Technician
No ratings yet
Computer MCQs For Pharmacy Technician
14 pages
Performance Tuning Basics 15 - AWR Report Analysis - Expert Oracle
100% (1)
Performance Tuning Basics 15 - AWR Report Analysis - Expert Oracle
63 pages
ReleaseNotesCommunicationManager5 2 1SP14
No ratings yet
ReleaseNotesCommunicationManager5 2 1SP14
207 pages
Upgrading To Communication Manager 636
No ratings yet
Upgrading To Communication Manager 636
1,778 pages
R17 CMS Capacities
No ratings yet
R17 CMS Capacities
16 pages
CMS ODBC Connectivity
No ratings yet
CMS ODBC Connectivity
48 pages
R17 SIMT - Linux - Book PDF
No ratings yet
R17 SIMT - Linux - Book PDF
222 pages
Simt Linux
No ratings yet
Simt Linux
252 pages
Data Dictionary CMS
No ratings yet
Data Dictionary CMS
82 pages
Avaya CMS Supervisor R18 Installation
No ratings yet
Avaya CMS Supervisor R18 Installation
140 pages
Avaya Call Management System Software Installation, Maintenance, and Troubleshootingfor Linux R18
No ratings yet
Avaya Call Management System Software Installation, Maintenance, and Troubleshootingfor Linux R18
254 pages
Upgrading Avaya Call Management System 19.0 June 2019
No ratings yet
Upgrading Avaya Call Management System 19.0 June 2019
108 pages
Avaya Call Management System - Maintenance
No ratings yet
Avaya Call Management System - Maintenance
260 pages
Avaya CMS HA Connectivity Upgrade and Administration 19.2 March 2021
No ratings yet
Avaya CMS HA Connectivity Upgrade and Administration 19.2 March 2021
56 pages
Avaya CMS HA Connectivity Upgrade and Administration 19.2 March 2021
No ratings yet
Avaya CMS HA Connectivity Upgrade and Administration 19.2 March 2021
56 pages
Avaya CMS Using LAN Backup 19.2 March 2021
No ratings yet
Avaya CMS Using LAN Backup 19.2 March 2021
102 pages
Avaya CMS Base Load Upgrade 19.2 March 2021
No ratings yet
Avaya CMS Base Load Upgrade 19.2 March 2021
62 pages
Avaya CMS Using High Availability 19.2 March 2021
No ratings yet
Avaya CMS Using High Availability 19.2 March 2021
72 pages
Avaya CMS Call History Interface 19.2 March 2021
No ratings yet
Avaya CMS Call History Interface 19.2 March 2021
94 pages
Avaya CMS Supervisor Clients Installation and Getting Started R20 June 2023
No ratings yet
Avaya CMS Supervisor Clients Installation and Getting Started R20 June 2023
126 pages
Avaya CMS and Communication Manager Connections Administration and Troubleshooting 19.2 March 2021
No ratings yet
Avaya CMS and Communication Manager Connections Administration and Troubleshooting 19.2 March 2021
86 pages
Avaya CMS Planning For Upgrades 19.2 March 2021
No ratings yet
Avaya CMS Planning For Upgrades 19.2 March 2021
32 pages
Avaya CMS Maintaining and Troubleshooting 19.2 March 2021
No ratings yet
Avaya CMS Maintaining and Troubleshooting 19.2 March 2021
308 pages
Avaya CMS Upgrading 19.2 March 2021
No ratings yet
Avaya CMS Upgrading 19.2 March 2021
114 pages
Avaya CMS Maintaining and Troubleshooting 19.1 February 2020
No ratings yet
Avaya CMS Maintaining and Troubleshooting 19.1 February 2020
292 pages
Avaya Cms Using Odbc and JDBC r20 June 2023
No ratings yet
Avaya Cms Using Odbc and JDBC r20 June 2023
74 pages
Avaya CMS Custom Reports 19.2 March 2021
No ratings yet
Avaya CMS Custom Reports 19.2 March 2021
178 pages
Avaya CMS Supervisor Clients Installation and Getting Started 19.2 March 2021
No ratings yet
Avaya CMS Supervisor Clients Installation and Getting Started 19.2 March 2021
132 pages
Avaya System Capacities Table
No ratings yet
Avaya System Capacities Table
87 pages
COM 3.1.3.1 RN Apr2017
No ratings yet
COM 3.1.3.1 RN Apr2017
16 pages
Avaya Aura Communication Manager: Release 6.3 03-300468 Issue 10 October 2013
No ratings yet
Avaya Aura Communication Manager: Release 6.3 03-300468 Issue 10 October 2013
44 pages
Accessing and Managing Utility Services
No ratings yet
Accessing and Managing Utility Services
78 pages
ImplementingCMM Embedded
No ratings yet
ImplementingCMM Embedded
104 pages
A Vaya Call Management System Database Items and Calculations
No ratings yet
A Vaya Call Management System Database Items and Calculations
359 pages
Avaya Reference Programming 7 1
No ratings yet
Avaya Reference Programming 7 1
127 pages
Administering Avaya Flare Experience For Ipad Devices and Windows
No ratings yet
Administering Avaya Flare Experience For Ipad Devices and Windows
26 pages
ScreenReference 167487
No ratings yet
ScreenReference 167487
1,860 pages
AEP Solutions Guide R8.0
No ratings yet
AEP Solutions Guide R8.0
77 pages
Implementing Avaya Aura CM6
No ratings yet
Implementing Avaya Aura CM6
194 pages
Avaya Client SDK External Application API
No ratings yet
Avaya Client SDK External Application API
70 pages
ExtensiontoCellular 210 100 700
No ratings yet
ExtensiontoCellular 210 100 700
92 pages
AEP Implement
No ratings yet
AEP Implement
135 pages
Avaya Diagnostic Server Deployment Guide
No ratings yet
Avaya Diagnostic Server Deployment Guide
174 pages
Administering Avaya IP Office With Manager - En-Us
No ratings yet
Administering Avaya IP Office With Manager - En-Us
1,220 pages
Avaya Aura®Application Enablement Services Overview
No ratings yet
Avaya Aura®Application Enablement Services Overview
107 pages
Overview of Avaya Aura System Platform
No ratings yet
Overview of Avaya Aura System Platform
11 pages
Job Aid For Field Replacement Units For The Avaya S8300E Server With G450 or G430 Branch Gateway
No ratings yet
Job Aid For Field Replacement Units For The Avaya S8300E Server With G450 or G430 Branch Gateway
24 pages
Avaya Comunicator
No ratings yet
Avaya Comunicator
86 pages
Avaya Aura Communication Manager System Capacities Table
No ratings yet
Avaya Aura Communication Manager System Capacities Table
70 pages
Avaya Experience Portal Administering R8.0 October 2020 v1.1
No ratings yet
Avaya Experience Portal Administering R8.0 October 2020 v1.1
742 pages
AEP Deploy
No ratings yet
AEP Deploy
107 pages
Aes61 DMCC Dotnet Prog
No ratings yet
Aes61 DMCC Dotnet Prog
168 pages
CM Server Options Book
No ratings yet
CM Server Options Book
78 pages
Avaya Call Management System Database Items and Calculations
No ratings yet
Avaya Call Management System Database Items and Calculations
358 pages
Using Avaya Health Check Tool
No ratings yet
Using Avaya Health Check Tool
24 pages
Avaya Secure Access Link Gateway Using VMware® in The Virtualized Environment Deployment Guide PDF
No ratings yet
Avaya Secure Access Link Gateway Using VMware® in The Virtualized Environment Deployment Guide PDF
64 pages
Avaya Contact Recorder: Release 12.0 Planning, Installation and Administration Guide
No ratings yet
Avaya Contact Recorder: Release 12.0 Planning, Installation and Administration Guide
408 pages
Using Avaya Health Check Tool
No ratings yet
Using Avaya Health Check Tool
24 pages
Experience Portal Documentation Roadmap
No ratings yet
Experience Portal Documentation Roadmap
12 pages
AdministeringExperiencePortal PDF
No ratings yet
AdministeringExperiencePortal PDF
680 pages
Avaya CMS Supervisor
No ratings yet
Avaya CMS Supervisor
208 pages
Overview and Specification For Avaya Aura Conferencing (Turnkey)
No ratings yet
Overview and Specification For Avaya Aura Conferencing (Turnkey)
97 pages
Overview and Specification For Avaya Aura Conferencing (Aura)
No ratings yet
Overview and Specification For Avaya Aura Conferencing (Aura)
96 pages
909A909B
No ratings yet
909A909B
38 pages
Using Conference Manager For Outlook
No ratings yet
Using Conference Manager For Outlook
24 pages
Using Collaboration Agent
No ratings yet
Using Collaboration Agent
94 pages
Using Collaboration Agent For Android
No ratings yet
Using Collaboration Agent For Android
39 pages
Deploying A Vaya Aurac M
No ratings yet
Deploying A Vaya Aurac M
163 pages
Avaya Aura Conferencing Solution Description For Large
No ratings yet
Avaya Aura Conferencing Solution Description For Large
44 pages
Avaya Aura Conferencing Accounting Records
No ratings yet
Avaya Aura Conferencing Accounting Records
82 pages
Avaya Aura Conferencing Port Matrix
No ratings yet
Avaya Aura Conferencing Port Matrix
59 pages
Installing The HP ProLiant DL360p G8 Server
No ratings yet
Installing The HP ProLiant DL360p G8 Server
20 pages
Avaya Aura Conferencing Alarms and Logs
No ratings yet
Avaya Aura Conferencing Alarms and Logs
461 pages
Solution Design Considerations
No ratings yet
Solution Design Considerations
264 pages
Migrating From Intuity Audix LX R1.1 To Avaya Aura Communication Manager Messaging R6.3
No ratings yet
Migrating From Intuity Audix LX R1.1 To Avaya Aura Communication Manager Messaging R6.3
22 pages
Maintaining The Avaya S8800 Server For Avaya Aura Communication Manager
No ratings yet
Maintaining The Avaya S8800 Server For Avaya Aura Communication Manager
64 pages
LEDs
No ratings yet
LEDs
66 pages
Migrating From Intuity Audix LX R2.0 To Avaya Aura CMM Federal R6.3
No ratings yet
Migrating From Intuity Audix LX R2.0 To Avaya Aura CMM Federal R6.3
30 pages
Installing The Dell PowerEdge R620 Server
No ratings yet
Installing The Dell PowerEdge R620 Server
20 pages
Communication Manager Reports
No ratings yet
Communication Manager Reports
318 pages
A Vaya Aurac M Product Description
No ratings yet
A Vaya Aurac M Product Description
54 pages
Deploying CM MV MW Are
No ratings yet
Deploying CM MV MW Are
64 pages
Avaya Communication Suite
No ratings yet
Avaya Communication Suite
44 pages
Maintenance Procedures
No ratings yet
Maintenance Procedures
358 pages
Using 96X1 SIP Agent Deskphones With Avaya Aura Call Center Elite
No ratings yet
Using 96X1 SIP Agent Deskphones With Avaya Aura Call Center Elite
55 pages
Administering Avaya Aura Call Center Elite 6.3 Features
No ratings yet
Administering Avaya Aura Call Center Elite 6.3 Features
352 pages
Utility Services Deployment Guide
No ratings yet
Utility Services Deployment Guide
60 pages
MIT App Inventor
No ratings yet
MIT App Inventor
1 page
mIRCScriptingPrimer PDF
No ratings yet
mIRCScriptingPrimer PDF
24 pages
Introduction To Microsoft PowerPoint
No ratings yet
Introduction To Microsoft PowerPoint
15 pages
A2 A6 PEK Version 2
No ratings yet
A2 A6 PEK Version 2
70 pages
Splunk 7.0.2 SearchReference
No ratings yet
Splunk 7.0.2 SearchReference
637 pages
Microsoft PowerPoint - Intro - To - Visual Inspection
No ratings yet
Microsoft PowerPoint - Intro - To - Visual Inspection
68 pages
20767A - Implementing A SQL Data Warehouse
No ratings yet
20767A - Implementing A SQL Data Warehouse
572 pages
A Tyranny of Excellence
No ratings yet
A Tyranny of Excellence
17 pages
Cambridge International Advanced Subsidiary and Advanced Level
No ratings yet
Cambridge International Advanced Subsidiary and Advanced Level
11 pages
CyBOK v1.1.0-4
100% (1)
CyBOK v1.1.0-4
200 pages
Registration Issue
No ratings yet
Registration Issue
5 pages
Unix Question Bank M1, M2, M3, M4, M5
No ratings yet
Unix Question Bank M1, M2, M3, M4, M5
6 pages
CS604p Final Term Live
No ratings yet
CS604p Final Term Live
17 pages
Performance Assessment LGEC PDF
No ratings yet
Performance Assessment LGEC PDF
114 pages
OS Tools Project Expanded v2
No ratings yet
OS Tools Project Expanded v2
3 pages
Sanako - Connect Sanako - Connect: Feasibility Feasibility
No ratings yet
Sanako - Connect Sanako - Connect: Feasibility Feasibility
9 pages
Seif Ezzat
No ratings yet
Seif Ezzat
3 pages
DL LWB
No ratings yet
DL LWB
116 pages
Autopipe: Connect V11.1
No ratings yet
Autopipe: Connect V11.1
29 pages
Chapter 10
No ratings yet
Chapter 10
52 pages
100 Node - Js Interview Questions and Answers For 2024 - Turing
No ratings yet
100 Node - Js Interview Questions and Answers For 2024 - Turing
33 pages
ANSYS Ncode Review
No ratings yet
ANSYS Ncode Review
17 pages
Elektor Electronics 1998-12
100% (1)
Elektor Electronics 1998-12
82 pages
Cisco Catalyst 2960-L Series Switches: Data Sheet
No ratings yet
Cisco Catalyst 2960-L Series Switches: Data Sheet
21 pages
Social Labs Fieldbook D12
No ratings yet
Social Labs Fieldbook D12
38 pages
English Homework: Name: Diana Patricia Poveda Rodriguez
No ratings yet
English Homework: Name: Diana Patricia Poveda Rodriguez
26 pages
Foxboro DCS: FBM222, Redundant PROFIBUS Communication
No ratings yet
Foxboro DCS: FBM222, Redundant PROFIBUS Communication
16 pages
Database Mirroring Questions and Answers
No ratings yet
Database Mirroring Questions and Answers
9 pages

Sys Cap Table

Uploaded by

Sys Cap Table

Uploaded by

Avaya Aura® Communication

Manager System Capacities Table

Avaya Toll Fraud Intervention

Contact Avaya Support

Highlights of Communication Manager Release 6.2

Highlights of Communication Manager Release 6.1 (6.0.1)

Highlights of Communication Manager Release 6.0

Highlights of Communication Manager Release 5.2.1

Highlights of Communication Manager Release 5.2

Highlights of Communication Manager Release 5.1

Highlights of Communication Manager Release 5.0

Highlights of Communication Manager Release 4.0

Highlights of Communication Manager Release 3.1

Highlights of Communication Manager Release 3.0

Highlights of Communication Manager Release 2.1

Highlights of Communication Manager R2.0

SYMBOL USED IN THE CAPACITIES TABLES:

CMS -1 ACD Admin Log Records 30,000

Avaya Aura® Communication Manager and Call Center Release 6.3

Endnote Detailed Description

3.1 Endnote removed.

4.2 Endnote removed.

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

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

10.1 Endnote removed.

28.2 Endnote removed.

31 INTUITY® supports 20 DCS nodes.

32 These numbers are node number addresses.

40 Counts towards the total number of DS1 circuit packs.

42.1 Endnote removed

The MM721 capacities per media gateway are as follows:

Gateway G450 G430 G700 G350

44 All BRI stations can be display stations.

requires an external data module.

45 Capacities depend upon the version of IP phones.

48 Endnote removed. It was replaced by endnote 95.1.

56.1 Endnote removed.

Total Time Slots:

Total Time Slots for Voice & Data

For non-Session configurations designed for fault tolerance:

Local Far End

Far End Far End

For Session Manager configurations designed for fault tolerance:

SM1 SM2 SM3 SM4

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

1. Fiber connect is only for federal government use.

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

71.2 Endnote removed.

71.3 Endnote removed.

Avaya IG550 Integrated Gateway:

J2320 J2350 J4350 / J6350

81.1 Endnote removed. It was replaced by endnote 78.

92 BRI Link capacity limited to 8.

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

103 Endnote removed.

105 EC500 / EC500 OPTIM

106 Location administration allows:

107 Endnote removed.

109 Endnote removed.

110 Endnote removed.

111 Endnote removed.

113 Endnote removed.

115 Endnote removed.

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

Capacities with DMCC/CMAPI call recording:

129 Endnote removed

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

140 Endnote removed.

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

You might also like