0% found this document useful (0 votes)

20 views90 pages

IP Office Platform Platform Guidelines Capacity - En-Us

Uploaded by

eng.elsayed khalil

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)

20 views90 pages

IP Office Platform Platform Guidelines Capacity - En-Us

Uploaded by

eng.elsayed khalil

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

IP Office Platform Guidelines Capacity

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

Chapter 1: Purpose................................................................................................................... 7
Intended Audience.................................................................................................................. 7
Disclaimer............................................................................................................................... 7
Information classifications and NDA requirements...................................................................... 8
Applicability............................................................................................................................. 8
Chapter 2: Overview................................................................................................................. 9
Definitions............................................................................................................................. 10
Changes from Previous Release............................................................................................ 10
Virtualized Deployments........................................................................................................ 10
IP Office Select/IP Office Subscription..................................................................................... 11
Subscription.......................................................................................................................... 12
Avaya Contact Center Applications......................................................................................... 12
Chapter 3: Capacity Planning................................................................................................ 13
Chapter 4: Primary and Secondary Server Capacity........................................................... 14
Audio Conferencing............................................................................................................... 14
Call Capacity......................................................................................................................... 16
Call Destination Server.......................................................................................................... 18
Call Media Path (Linux).......................................................................................................... 19
Call Recording...................................................................................................................... 19
Call Traffic Profile.................................................................................................................. 21
Extension/User/Site Capacity................................................................................................. 23
Hunt and Presence Groups.................................................................................................... 25
IP Infrastructure, Bandwidth and VoIP QoS............................................................................. 26
Multi-Site Network Link Capacities.......................................................................................... 28
Resilience and Failover.......................................................................................................... 29
Trunk Capacity...................................................................................................................... 29
Voicemail or Auto-Attendant or IVR......................................................................................... 31
Chapter 5: one-X Portal Server.............................................................................................. 33
Chapter 6: IP500 V2/V2A Servers.......................................................................................... 35
Audio Conferencing............................................................................................................... 35
Call Capacity......................................................................................................................... 37
Call Destination Server.......................................................................................................... 39
Call Media Path (IP500 V2/V2A)............................................................................................. 39
Call Recording...................................................................................................................... 40
Call Traffic Profile.................................................................................................................. 42
Extension/User Capacity........................................................................................................ 44
Hunt and Presence Groups.................................................................................................... 44
IP Infrastructure, Bandwidth and VoIP QoS............................................................................. 45
Multi-Site Network Link Capacities.......................................................................................... 48

August 2024 IP Office Platform Guidelines Capacity 4

Comments on this document?
Resilience and Failover.......................................................................................................... 48
Small Community Network Capacity....................................................................................... 49
Maximum Trunk Capacity....................................................................................................... 49
VCM Channel Capacity.......................................................................................................... 51
Voicemail or Auto-Attendant or IVR......................................................................................... 53
Chapter 7: Linux Expansion Server...................................................................................... 55
Chapter 8: General Capacity Considerations....................................................................... 56
Account Codes...................................................................................................................... 57
Audio Conferencing............................................................................................................... 57
Button Modules..................................................................................................................... 59
Appearance Button Programming........................................................................................... 60
Call Destination Server.......................................................................................................... 60
Call Logs/Call History............................................................................................................ 61
Call Recording...................................................................................................................... 62
Media Manager Recording Capacity....................................................................................... 64
Call Traffic Profile.................................................................................................................. 65
CTI & TAPI............................................................................................................................ 66
DECT R4.............................................................................................................................. 67
Directory............................................................................................................................... 68
Hunt and Presence Groups.................................................................................................... 68
Incoming Call Routes............................................................................................................. 69
IP Infrastructure, Bandwidth and VoIP QoS............................................................................. 70
IP Office SoftConsole............................................................................................................ 72
Multi-Site Network Link Capacities.......................................................................................... 73
Paging.................................................................................................................................. 74
Remote Support Services...................................................................................................... 75
Resilience and Failover.......................................................................................................... 75
Unified Messaging Capacity................................................................................................... 76
Voicemail or Auto-Attendant or IVR......................................................................................... 77
WebRTC Gateway................................................................................................................. 79
WebLM Server...................................................................................................................... 80
Chapter 9: Capacity Planning Beyond 3000 Users.............................................................. 81
Inter Server Edition Link......................................................................................................... 83
Directory............................................................................................................................... 83
Dial plan............................................................................................................................... 84
Outgoing Call routing............................................................................................................. 84
Hunt Groups......................................................................................................................... 84
Administration....................................................................................................................... 85
Versions or Upgrades............................................................................................................ 85
Chapter 10: Additional Help and Documentation................................................................ 86
Additional Manuals and User Guides...................................................................................... 86
Getting Help.......................................................................................................................... 86
Finding an Avaya Business Partner........................................................................................ 87

August 2024 IP Office Platform Guidelines Capacity 5

Comments on this document?
Additional IP Office resources................................................................................................. 87
Training................................................................................................................................ 88

August 2024 IP Office Platform Guidelines Capacity 6

Comments on this document?
Chapter 1: Purpose

The following document covers various aspects of IP Office 11.1 capacity and performance that may
have an influence on the design of a specific customer’s solution. This document also includes the
relevant aspects of the IP Office Selectand IP Office Subscription product offers and when it should
be considered.
Related links
Intended Audience on page 7
Disclaimer on page 7
Information classifications and NDA requirements on page 8
Applicability on page 8

Intended Audience
This document is intended for pre-sales, solution design, installation, administration and support
personnel who required knowledge of IP500 V2/V2A, IP Office Server Edition, IP Office Select and
IP Office Subscription capacity and performance.
Related links
Purpose on page 7

Disclaimer
Avaya has used reasonable commercial efforts to ensure that the information provided here under
is accurate at this date. Avaya may change any underlying processes, architecture, product,
description or any other information described or contained in this document. Avaya disclaims any
intention or obligation to update or revise the document, whether as a result of new information,
future events or otherwise. This document is provided “as is,” and Avaya does not provide any
warranty of any kind, express or implied.
Related links
Purpose on page 7

August 2024 IP Office Platform Guidelines Capacity 7

Comments on this document?
Purpose

Information classifications and NDA requirements

Avaya provides security related information according to the following information classifications:

Classification Description
Avaya Restricted This classification is for extremely sensitive business information, intended strictly
for use within Avaya. Unauthorized disclosure of this information can have a severe
adverse impact on Avaya and the customers, the Business Partners, and the
suppliers of Avaya.
Avaya Confidential This classification applies to less sensitive business information intended for use
within Avaya. Unauthorized disclosure of this information can have significant
adverse impact on Avaya, and the customers, the Business Partners, and the
suppliers of Avaya. Information that can be private for some people is included in
this classification.
Avaya Proprietary This classification applies to all other information that does not clearly fit into the
above two classifications, and is considered sensitive only outside of Avaya. While
disclosure might not have a serious adverse impact on Avaya, and the customers,
Business Partners, and suppliers of Avaya, this information belongs to Avaya, and
unauthorized disclosure is against Avaya policy.
Public This classification applies to information explicitly approved by Avaya management
as nonsensitive information available for external release.

As this document is generally available, the information herein is considered Public. This
document contains references to additional information sources which may disclose both
confidential and proprietary information and require a non-disclosure agreement (NDA) with
Avaya.
Related links
Purpose on page 7

Applicability
The following information is applicable to IP Office Select, IP Office Server Edition, IP Office
Subscription, IP500 V2/V2A and attached endpoints for IP Office Release 11.1.3.
Related links
Purpose on page 7

August 2024 IP Office Platform Guidelines Capacity 8

Comments on this document?
Chapter 2: Overview

Before proceeding with any capacity analysis or planning, the following resources should be
consulted:
• The "Avaya IP Office Solution Description" gives a high level view on deployment components.
• IP Office Technical Bulletins: Bulletins announce the general availability of new releases and
their content. They can be found at: https://ipofficekb.avaya.com/bulletins
• Virtualized Deployments: Linux-based server components are supported in a virtualized
environment using VMware technologies; the performance and capacity is directly governed
by static and dynamic resource assignments which are not covered here. For more information,
see "Deploying IP Office Servers as Virtual Machines".
• Avaya Contact Center Applications: IP Office Server Edition supports differing capacity and
performance levels when Avaya Contact Center Select (ACCS) is attached. See Avaya
Contact Center Applications on page 12
• Other attached Avaya DevConnect applications: Please refer to the relevant application
documentation.
The "Avaya IP Office Solution Description" provides information about solution components, their
capabilities and capacities sufficient to allow a high level design. This capacity planning document
should subsequently be used to qualify and refine that design.
The most complex single component to consider is generally the IP500 V2/V2A when acting as a
expansion system in a Linux-based primary server network, due to its combination of VoIP, digital
and analog phones/trunks, and the flexibility of constructs.
The Linux-based server components (primary, secondary Server and Linux-based expansion) are
VoIP only and single construct, save for the decision whether to move the one-X Portal server from
the Primary to a separate platform (an IP Office Application Server) for capacity.
Releases prior to IP Office R11.1 have differing capacities and performance limits; the
corresponding release documentation should be used.
Related links
Definitions on page 10
Changes from Previous Release on page 10
Virtualized Deployments on page 10
IP Office Select/IP Office Subscription on page 11
Subscription on page 12
Avaya Contact Center Applications on page 12

August 2024 IP Office Platform Guidelines Capacity 9

Comments on this document?
Overview

Definitions
The following terms are used within this document:

Term Definition
Linux-Based Network This refers to a network of servers centered around a Linux-based IP Office
primary server. The network can then included a Linux-based secondary server
and expansion servers plus IP500 V2/V2A expansion server systems. This type
of network can run in IP Office Server Edition, IP Office Select and IP Office
Subscription mode.

Changes from Previous Release

None.
Related links
Overview on page 9

Virtualized Deployments
Server Edition components are supported in a virtualized environment using VMware vSphere,
Microsoft Hyper-V, Amazon AMI and Microsoft Azure. This document refers to the option as ‘OVA’
(Open Virtual Appliance).
In general, the OVA is regarded as equivalent to a Dell R640, noting that:
• The necessary host and Virtual Machine (VM) resources have been assigned. Hyper-V and
Azure require additional resources over VMware.
• To achieve the stated capacity and performance virtual disk provisioning must be Thick
Provision Eager Zeroed or equivalent – i.e. all vHDDs must be pre-provisioned and initialized
during VM deployment.
• The supported maximum capacities and performance of an IP Office expansion differs from a
primary or secondary regardless of the platform.
• IP Office Select operation is required as necessary, see IP Office Select/IP Office
Subscription on page 11.
For further information about VM resourcing and OVA-specific planning, see "Deploying IP Office
Servers as Virtual Machines".

August 2024 IP Office Platform Guidelines Capacity 10

Comments on this document?
IP Office Select/IP Office Subscription

IP Office Select/IP Office Subscription

Avaya IP Office Select is a premium IP Office Server Edition offer providing extended capacity,
performance and features over basic IP Office Server Edition. The following also apply to IP Office
Subscription when running on the Linux-based server platforms.
Additional Capacity
In summary, IP Office Select offers the following increased capacities. Note that the capacities are
also be subject to meeting server platform requirements, refer to the individual sections on each
feature.
Feature Capacity Change
User/Extensions per server: 1500 > 3000
Users/Extensions whole solution: 2000 > 3000
Expansion systems: 30 > 148
Power User/UC clients: 2000 > 3000
Voicemail/Attendant/Recording channels: 250 > 500
Conference channels: 256 > 512
SIP trunk calls: 512 > 1024
Inter IP Office line channels: 250 > 500
Solution SoftConsole instances: 32 > 75
Button module buttons per Linux server: 4096 > 8192
Peak call Rate: 18,000 > 20,000

Additional Features
IP Office Select also offers the following additional features:
• Expansion to Expansion Inter IP Office lines
• Location based phone resilience
• Expansion to Expansion phone and hunt group resilience
• VMware High Availability (HA) - Note: Not compatible with resilience features. Either VMware
HA or resilience can be used but not both.
• Resilient Avaya one-X® Portal server on a second Avaya one-X® Portal server or Secondary
Server
The decision to deploy IP Office Server Edition or IP Office Select should be made at the outset.
However it is possible to convert a IP Office Server Edition to an IP Office Select solution at a later
date without loss of configuration or data. Moving from IP Office Select to IP Office Server Edition
requires complete reconfiguration.

August 2024 IP Office Platform Guidelines Capacity 11

Comments on this document?
Overview

Avaya Contact Center Applications

IP Office supports Avaya Contact Center Select (ACCS). When ACCS is connected, certain
aspects of IP Office Server Edition capacity and performance are determined by that application.
These include:
• Maximum agents
• Supported call rate
• Maximum Recording channels
• Available capacity and performance for non-agent users
• Maximum Conference channels for recording calls
These are irrespective of the mode (IP Office Select, IP Office Server Edition or IP Office
Subscription being used as the IP Office system.
Maximum conference and recording channels are covered in Audio Conferencing on page 14
and Call Recording on page 19; please refer to the relevant application documentation for all
other aspects:
Related links
Overview on page 9

August 2024 IP Office Platform Guidelines Capacity 12

Comments on this document?
Chapter 3: Capacity Planning

When designing a solution using a Linux-based IP Office primary server, many aspects need to be
considered for capacity. These include:
• IP Office Subscription, IP Office Select or IP Office Server Edition deployment
• Maximum extension, and user capacity required; both per server and solution
• Maximum anticipated site/node capacity
• Maximum trunk capacity
• Hunt group quantity, size and location
• The total concurrent VoIP call capacity
• Call media destination location and type; both intermediate and final
• Direct/indirect/secure VoIP media
• Conference, and recording capacity
• Multi-site Network link capacities
• Call Destination
• IP Infrastructure & VoIP QoS
• Trunk utilization and call traffic profile
• Resilience and Failover requirements
• Available licenses
All should be assessed as one factor may limit another.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.

August 2024 IP Office Platform Guidelines Capacity 13

Comments on this document?
Chapter 4: Primary and Secondary Server
Capacity

The following sections cover capacity considerations specific to Linux-based primary and secondary
servers
Related links
Audio Conferencing on page 14
Call Capacity on page 16
Call Destination Server on page 18
Call Media Path (Linux) on page 19
Call Recording on page 19
Call Traffic Profile on page 21
Extension/User/Site Capacity on page 23
Hunt and Presence Groups on page 25
IP Infrastructure, Bandwidth and VoIP QoS on page 26
Multi-Site Network Link Capacities on page 28
Resilience and Failover on page 29
Trunk Capacity on page 29
Voicemail or Auto-Attendant or IVR on page 31

Audio Conferencing
Primary/Secondary Server
Each Primary and Secondary supports a local audio conference capability with the following
capacities:
System Mode Primary/Secondary Total Conference Maximum Total Conference
server Channels conference size Channels with
ACCS
IP Office Server Dell R240 128 128 414
Edition HP DL360 256 256 825
Dell R640 256 256 1650
Table continues…

August 2024 IP Office Platform Guidelines Capacity 14

Comments on this document?
Audio Conferencing

System Mode Primary/Secondary Total Conference Maximum Total Conference

server Channels conference size Channels with
ACCS
OVA 256 256 1650
IP Office Select Dell R640 512 256 1650
IP Office OVA 512 256 1650
Subscription

IP500 V2/V2A and Linux Expansion System

Each IP500 V2/V2A and Linux Expansion System supports a local audio conference capability
with the following capacities:
Expansion Platform Total Conference Maximum conference Total Conference
Channels size Channels with ACCS
Linux/OVA 128 128 128
IP500 V2/V2A 128 64 128

System Conferences
System conferences use the same conference capacity as above but are subject to the following
additional limits:
• IP Office Essential Edition/Preferred Edition: 30.
• IP Office Server Edition/IP Office Select: 120. System conferences are hosted by the
primary server (secondary server during resilience).
Notes
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• OVA always advertises these figures. However, capacity depends on assigned profiling as
detailed in "Deploying IP Office Servers as Virtual Machines".
• The figures cover both ad-hoc and meet-me conference types.
• With one-X Portal users active, a solution-wide limit of 750 conference channel participants
applies, but this does not include conferences used for call recording.
• IP Office Server Edition supports differing capacity and performance levels when Avaya
Contact Center Select (ACCS) is attached. See Avaya Contact Center Applications on
page 12.
• The increased capacities for ACCS are only supported when the applications are actively
connected to the host IP Office and should only be used for call recording purposes.
• No dynamic solution-wide conference allocation is supported, only static via call flows or
Conference Meet Me short code Line Group ID.
• V2 Expansion conferences exist in the digital domain; hence all VoIP parties (trunk or
extension) will require a VCM channel for the duration. See VCM Channel Capacity on
page 51.

August 2024 IP Office Platform Guidelines Capacity 15

Comments on this document?
Primary and Secondary Server Capacity

• Further information on conferences can be found

at: http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/
manager/_frame2.html?Conferencing.Overview.html
Which Servers Conference Resources are Used?
The location of the conference resource used when a conference is started are determined by a
number of factors:
• A user performing an ad-hoc conference uses the conference resources of the server on
which they are logged in.
• A meet-me conference using a user’s personal meet-me bridge uses the conference
resources of the server on which they are logged in.
• A meet-me conference created by Voicemail Pro call flow, or the Conference meet-me short
code feature use the system on which the feature was invoked.
• To invoke a meet-me Conference using the resources of a remote system, use the Line
Group ID field of the Conference Meet Me short code feature. By default this is set to 0, for
local system.
• For the case where a conference is scheduled by Avaya one-X® Portal and at the scheduled
time the conference dials the delegates: The conference location is the server to which the
active Avaya one-X® Portal is attached.
Recording a conference requires an additional conference channel, as well as an IP Office Line
(SCN trunk) channel to the recording destination (Primary or Secondary Server, alternate during
fail over operation). Neither IP Office nor Voicemail Pro can automatically link or move conference
locations, but existing conferences can be connected together.
When conference resources run out, attempts to record calls, join or create conferences are
rejected.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Capacity
Each server type is rated to support every single extension engaged in a call providing it is direct
media and regardless of security settings. If the media stream passes through the server, the
capacity is reduced.

August 2024 IP Office Platform Guidelines Capacity 16

Comments on this document?
Call Capacity

System Mode Primary/Secondary Concurrent Calls

server Direct Media Indirect Media Secure Indirect
Media
IP Office Server Dell R240 750 128 64
Edition HP DL360G7 1500 256 128
Dell R640 2000 1024 512
OVA[1] 2000 1024 512
IP Office Select Dell R640 3000 1024 512
IP Office OVA[1] 3000 1024 512
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• One VoIP call is one pair of RTP or SRTP streams between IP Office and a VoIP endpoint
– for example VoIP phone, VoIP trunk, IP Office line, Voicemail Pro. Note that an indirect
media call via IP Office from one VoIP endpoint to another counts as two calls; one between
IP Office and endpoint A and one between IP Office and endpoint B.
• Direct media is RTP/SRTP data directly between VoIP endpoints, not via IP Office. There are
some IP Office networking constraints to achieve direct media. See Call Media Path (IP500
V2/V2A) on page 39.
• Transcoding between any codec does not reduce the server indirect media concurrent call
capacity.
• Direct media with SRTP does not reduce the direct media capacity.
• One SRTP indirect media call reduces the available RTP call capacity by 2 (and vice versa).
• If SRTP transcoding is present (for example where the security parameters are mismatched
between two phones), the capacity is reduced by a further 50%.
• If the server is running Voicemail Pro, one call to voicemail, attendant, recording or IVR
consumes one indirect media call.
• If the server is the location for an audio conference, each member consumes one indirect
media call.
Administration
Concurrent call maximum capacity can be administered via IP Office Server Edition Manager in a
number ways to ensure limits are not exceeded:
• Number of Channels and Outgoing Channels setting in the Line > VoIP tab of IP Office
lines.
• Max Calls per Channel setting in the Line > SIP URI tab of SIP trunks.

August 2024 IP Office Platform Guidelines Capacity 17

Comments on this document?
Primary and Secondary Server Capacity

• Call Admission Control area of the Location settings.

• VoIP Security area of the System settings.
• Media Security area in the Line > VoIP Settings tab.
• Media Security area in the Extension > VoIP tab.
The following occurs if the maximum numbers are exceeded:
• Unless administered, IP Office does not limit the number of concurrent calls and makes a
best effort to service all.
• VoIP voice quality degrades as load increases; high overload conditions cause the Server to
perform poorly in general.
Related links
Primary and Secondary Server Capacity on page 14

Call Destination Server

When considering Expansion or Server planning from a media perspective it is important to note
that communication with any other IP Office Server Edition component will use VoIP and hence is
limited by the media, IP Office Line (SCN trunk) and VCM capacities. This includes:
• Calls to/from Primary/Secondary and other Expansions
• Call recording - one VoIP channel per recorded call. Destination is the location of the active
Voicemail Pro.
• Auto Attendants/IVR - one VoIP channel per call when connected to the Auto Attendant/IVR.
Destination is the location of the active Voicemail Pro.
• Conferencing when the conference focus is not the local system - one VoIP channel per local
member
• Local conferences involving remote users - one VoIP channel per remote member when
connected to the conference
• Voicemail leave and collect - one VoIP channel per VM caller when. Destination is the
location of the active Voicemail Pro.
• Announcements - one VoIP channel per call when generating announcements. Destination is
the location of the active Voicemail Pro.
• Centralized Music on Hold – one VoIP channel per central MOH source when playing to held
calls. Destination is the location of the Music on Hold source.
For all VoIP connections between systems, the codec used will be according to the IP Office Line
settings of those two nodes.
Consideration should also be given to intermediate destinations to ensure adequate capacity is
present. For example a consultation call will open a secondary channel for the consultation whilst
keeping the initial call connected.

August 2024 IP Office Platform Guidelines Capacity 18

Comments on this document?
Call Media Path (Linux)

Lastly, any call on the IP Office Line will take into consideration administered channel limits
and Call Admission Control (CAC) if active. Please refer to the CAC section of the IP Office
administration documentation for behaviors when CAC limits are exceeded.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Media Path (Linux)

Where calls go between VoIP endpoints (e.g. SIP trunk to H.323 extension) there are two options:
Direct and indirect media. Direct media does not use the server’s routing engine and hence the
base capacity concurrent calls will apply.
Direct media is a configurable parameter for VoIP trunks and extensions with a default of active.
Indirect media will occur either where configured, or if direct media is not possible (even if
configured). Some causes would be:
• VoIP traffic routed between the LAN1 and LAN2 interface
• Unsuccessful codec negotiation (including silence suppression, DTMF transport as well as
basic codec support)
• A VoIP endpoint that does not support direct media
• Mismatch of RTP and SRTP
• Mismatched SRTP or SRTCP security settings such as no common cipher suite. These
should be avoided if at all possible due to the limited indirect media SRTP capacity.
• Network Address Translation (NAT) traversal usually associated with Remote Worker phone
deployments.
The above should be avoided if at all possible due to the limited indirect media capacity.
Related links
Primary and Secondary Server Capacity on page 14

Call Recording
Each Primary and Secondary supports a voice call recording capability with the following
capacities:

August 2024 IP Office Platform Guidelines Capacity 19

Comments on this document?
Primary and Secondary Server Capacity

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• OVA always advertises these figures. However, capacity depends on assigned profiling as
detailed in "Deploying IP Office Servers as Virtual Machines".
• Call recording uses a 3-party conference per recorded call. Note that without ACCS
connected, the primary server does not have sufficient conference channels for the whole
solution - other server's conference resources must be used.
• Conference recording adds a further conference channel to an existing conference.
• Each recording requires one licensed (and available) voicemail channel, a VCM (for the
IP500 V2 Expansion) and IP Office Line (SCN trunk) channel as the recording destination is
on the Primary or Secondary Server. See VCM Channel Capacity on page 51.
• The system supports differing capacity and performance levels when Avaya Contact Center
Select (ACCS) is attached. See Avaya Contact Center Applications on page 12.
• The increased capacities for ACCS are only supported for call recording, and are active when
the application is connected to the host IP Office.
• The solution internal call recording capacity is fixed at 333 hours total (555 hours for IP Office
Select). This is separate from the voicemail mailbox recording capacity, see Voicemail or
Auto-Attendant or IVR on page 31. It is also separate from Media Manager storage capacity,
see Media Manager Recording Capacity on page 64.
• The Media Manager application supports recordings management at the maximum channel
and call rate appropriate to the server platform.
• If the dual Voicemail Pro feature is active IP Office Select and IP Office Subscription only) the
maximum solution capacity is doubled to maximum of 500 channels, the per-server capacity
remains unchanged.

August 2024 IP Office Platform Guidelines Capacity 20

Comments on this document?
Call Traffic Profile

• One active recording channel consumes one voicemail/AA channel. If the call is being
recorded in two places – for example at the user and the incoming trunk – two licensed
and available voicemail channels are required.
• Maximum recording call rate is 7200/9000/10000 BHCC for a primary/secondary Linux-based
server, 3,600 BHCC for an Expansion. See Call Traffic Profile on page 21.
Recording call rate is further reduced for ACCS. See Avaya Contact Center Applications on
page 12.
Which Servers Conference Resources are Used?
The location of conference resource used is determined by the point of recording:
• Incoming Call Route (ICR) recording is done at trunk’s location
• User recording is done at user’s location.
• Hunt group recording is done at the group's location.
• System recording is done at the system’s location.
• Conference recording at conference location: Ad-hoc conference recording is done at the
initial user's location. Meet-me conference recording can specify the location.
• Account code recording is done at the user's location.
Administration
To ensure Voicemail Pro channel capacity is available for recordings, the IP Office Server Edition
Manager settings Voicemail Channel Reservation on the Primary and Secondary Server’s
System > Voicemail tab can be configured to reserve channels exclusively for specific uses.
• If recording channel resources run out:
- If the recording is mandatory, busy is returned.
- If the recording is not mandatory, further attempts to record calls or conferences are not
successful, but there may still be visual recording indications.
If exceeded:
If recording storage resources run out, further attempts to record calls or conferences will not be
successful and receive announcements to that effect.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Traffic Profile

General traffic engineering is outside the scope of this document, however the following IP Office
Server Edition factors should be considered:

August 2024 IP Office Platform Guidelines Capacity 21

Comments on this document?
Primary and Secondary Server Capacity

System Mode Platform Maximum Call Rate (BHCC)

Server Solution
IP Office Server Edition Dell R240 7,200 7,200
HP DL360G7 18,000/9,000[3] 18,000/9,000[3]
Dell R640 18,000/9,000[3] 18,000/9,000[3]
OVA[1] 18,000/9,000[3] 18,000/9,000[3]
IP Office Select Dell R640[2] 20,000/10,000[3] 20,000/10,000[3]
IP Office Subscription OVA[1, 2] 20,000/10,000[3] 20,000/10,000[3]
All Linux 7200 -
IP500 V2/V2A Expansion 3600 -

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
2. These platforms (Dell R640 or OVA) only. Other servers only support the lower
18,000/9,000 call rate.
3. Lower call rate when any Avaya one-X® Portal user active.
• The quoted Busy Hour Call Completion (BHCC) rates assumes a Normal call distribution.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• Total solution BHCC must not exceed 9,000/10,000 BHCC when Avaya one-X® Portal users
are active
• Continuously running at the maximum supported solution call rate when Avaya one-X® Portal
users are active should not exceed 24 hours.
• Avaya one-X® Portal users include: Web Client, Call Assistant, Outlook Integration, Lync
Integration, one-X preferred Mobile Clients
• The maximum rate for call recording and Voicemail leave combined is 7,200/9,000/10,000
BHCC.
• The Maximum Solution Call Rate can be further reduced by the presence of Call recording,
CTI or Contact Center application such as ACCS. See Avaya Contact Center Applications on
page 12.
• IP Office Subscription is an OPEX licensed offer which supports the same capacity and
performance as IP Office Select (see IP Office Select/IP Office Subscription on page 11). A
stand-alone IP500 V2/V2A running IP Office Subscription has the same capacity as other
IP500 V2/V2A offers (see IP500 V2/V2A Servers on page 35 ).
The following occurs if these figures are exceeded:
If the call rate is exceeded, there may be disruption to call voice quality, recordings, or a general
slowdown in other operation such as UC or management clients.

August 2024 IP Office Platform Guidelines Capacity 22

Comments on this document?
Extension/User/Site Capacity

Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Extension/User/Site Capacity
The server platform type should be selected to support the maximum potential users/extensions/
sites according to the following table.
• The extension limits shown are for 1600/9600/J100 extensions not using TLS. Each VoIP
extension that uses TLS for signaling or configuration reduces the extension capacity by 2.
This table is for Linux-based IP Office systems and networks. For IP500 V2-based IP Office
systems and networks, see Small Community Network Capacity on page 49.

System Mode Primary, Maximum Users, Extensions Maximum

Secondary server Server Solution Expansion
Systems
IP Office Server Dell R240 750 1500 30
Edition HP DL360G7 1500 2000 30
Dell R640 2000 2000 30
OVA[1] 2000 2000 30
IP Office Select Dell R640 3000 3000 148
IP Office OVA[1] 3000 3000 148
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
2. The secondary server and primary server platforms must match in terms of capacity and
performance.
3. Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers
are equivalent.
4. Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
5. A mix of physical and virtualized servers is supported, providing the resources assigned to
the virtual server match those of the physical server.
6. Maximum users and extensions are configuration limits as well as a currently active/
registered limit.
7. Extension and user limits include potential resilience failover extensions/users and
simultaneous VoIP extensions. Again these are configuration limits as well as currently
active/registered limits.

August 2024 IP Office Platform Guidelines Capacity 23

Comments on this document?
Primary and Secondary Server Capacity

8. Extension capacity support includes the system acting as DHCP and file server for the
phones. File server performance of Linux-based servers is limited as follows. If higher
performance is required, an external HTTP/S server can be used.
• Dell R240: 100 phones per 50 minutes.
• HP DL360G7: 200 phones per 50 minutes.
• Dell R640: 300 phones per 50 minutes.
• OVA: Up to 300 phones per 50 minutes.
9. The special user ‘NoUser’ is not counted.
10. Simultaneous user extensions are counted in the total.
11. An Avaya Workplace Client counts as one SIP extension and one CTI load. It does not use
Avaya one-X® Portal capacity.
12. Avaya Communicator for Web counts as one SIP extension, one WebRTC load and one
Avaya one-X® Portal client.
13. Each VoIP extension that uses TLS for signaling or configuration reduces the extension
capacity by 2.
14. Maximum per server capacity of other extension types can be lower; for example DECT R4
(750 per system), 1100/1200 Series phones (1000, 500 with TLS).
15. DECT R4, D100 DECT and 1100/1200 Series phones have directory capacity limitations.
See Directory on page 68.
16. Remote worker 9600 H323 extensions are supported at a lower capacity for the HP
DL360G7 (maximum 256 remote workers) and R220 servers (maximum 128 remote
workers). Other server and endpoint types have no such restrictions.
17. OVA always advertises these figures. However, capacity depends on assigned profiling as
detailed in "Deploying IP Office Servers as Virtual Machines".
18. On non-IP Office Select or IP Office Subscription systems, if the above figures are
exceeded:
• IP Office Manager will not permit more than 2000 extensions/users (whether per server
and whole solution).
• IP Office Manager will not permit more than 30 Expansions (it always reserve one
system for a Secondary Server).
• The Primary/Secondary Server will not accept phone registrations from more than the
above per-server quantity of extensions; any more are rejected. This is important when
considering fallback scenarios.
Related links
Primary and Secondary Server Capacity on page 14

August 2024 IP Office Platform Guidelines Capacity 24

Comments on this document?
Hunt and Presence Groups

Hunt and Presence Groups

Hunt Groups are sets of telephone users targeted by calls. Presence groups are sets of XMPP
users for IM purposes. Both are viewed together for group capacity, of which there are both
per-solution and per system limits:

System Mode Platform Maximum Maximum Groups Total Hunt

Server Group Server Solution Solution Group
size Members
Essential IP500 V2/V2A 384 200 300 3000
Edition
Preferred
Edition
IP Office Server Linux/OVA 750 300 300 3000
Edition IP500 V2/V2A 384 200 300 3000
IP Office Select Linux/OVA 1250 600 600 6000
IP Office IP500 V2/V2A 384 200 600 6000
Subscription

• Maximum Solution Groups is the total number of hunt and presence groups over the whole
solution.
• Maximum Server Group size is the maximum number of members in a single hunt/presence
group.
• Total Solution Group Members is the total members over all hunt/presence groups.
The following occurs if these figures are exceeded:
• IP Office Manager does not permit the administration of more than 300 solution groups if the
solution is not IP Office Select or IP Office Subscription.
• IP Office Manager does not permit the administration of more than 750 per group members if
the solution is not IP Office Select or IP Office Subscription.
• If the number of groups or individual size is exceeded (particularly if the Ring Mode
is Collective or Collective Call Waiting), there may be inaccurate hunt group call
presentation, or a general slowdown in other operation such as UC or management clients.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 25

Comments on this document?
Primary and Secondary Server Capacity

IP Infrastructure, Bandwidth and VoIP QoS

It is not within the scope of this document to cover detailed aspects of Ethernet and IP
infrastructure.
• IP500 V2 supports two 10/100 Mbit/s, Full/Half duplex 802.3 Ethernet interfaces with
DSCP/ToS support.
• Avaya IP Office Linux servers supports two 10/100/1000 Mbit/s, Full/Half duplex 802.3
Ethernet interfaces with DSCP/ToS and static 802.1Q VLAN support.
• Subject to IP infrastructure: All supported IP Office traffic can be routed via a single LAN
interface: All supported IP Office traffic can be routed between the LAN interfaces, however
this may lead to inefficiencies and limit performance for the IP500 V2 platform.
For more information on LAN interface support, see the IP Office Server Edition LAN Support
chapter of "Deploying IP Office Server Edition".
Note that secure VoIP (SRTP) can increase the required bandwidth by up to 8%, see the ‘VoIP
Security’ chapter of Avaya IP Office™ Platform Security Guidelines.
In addition to the network requirements for VoIP calls, additional bandwidth should be reserved for
the corresponding inter-node signaling and management paths. This should include any access
via SSLVPN (IPOSS) or Remote Support Service (RSS). The following suggested minimum
bandwidths should be made available for these additional paths:

Traffic Suggested Minimum Comments

August 2024 IP Office Platform Guidelines Capacity 26

Comments on this document?
IP Infrastructure, Bandwidth and VoIP QoS

Traffic Suggested Minimum Comments

Bandwidth
Backup/Restore 256 – 2048 kbit/s Between Backup Server and each Expansion
Between Backup Server and Primary
Between Backup Server and Secondary
An IP Office Linux platform can be designated as the
backup server.
Bandwidth is only required when a backup or restore
operation is active, and only between participating
nodes.
The bandwidth required depends on the backup/
restore content.
Voicemail Pro client 512 kbit/s Between Voicemail Pro PC and Primary (or Secondary
under failover conditions) when a Voicemail Pro server
management session is active
Voicemail Pro Server <> 1024 kbit/s Bursty traffic, peaking after start-up or restoration of
Voicemail Pro Server Server to Server connectivity
32 kbit/s per active Extra traffic between Secondary and Primary when
channel Dual Voicemail Pro active
Voicemail Pro Server <> 32 kbit/s per active Bursty SFTP traffic, between Primary and external
IP Office Media Manager channel server running IP OfficeMedia Manager. Typically IP
Office Media Manager runs coresident with Voicemail
Pro. For dual active Voicemail Pro, the Secondary
Voicemail Pro will send all recordings to the server
running IP Office Media Manager.
WebRTC Client 6 – 256 kbit/s Between each active Avaya Communicator for Web
client and the WebRTC Gateway
one-X Server <> one-X 1–500 users: 512 kbit/s Bursty traffic, peaking after start-up or restoration of
Server Server to Server connectivity
500–1500 users: 1024
kbit/s
1500–3000 users: 2048
kbit/s
SoftConsole 64–1024 kbit/s Bursty traffic, peaking after start-up. Higher figure for
maximum 3000 user deployment.
Between each SoftConsole application and the IP
Office server.
SMDR 1 kbit per call report (or Average SMDR message size for typical call pattern
7.2 kbit/s @ 7,200 BHCC)
RSS to co-located 64 –1024 kbit/s per TCP Between remote client and col-located server when a
server Tunnel remote management session is active

• These figures are for general guidance only as they do not reflect the specific requirements
for a given installation. For example management operations are typically session based;

August 2024 IP Office Platform Guidelines Capacity 27

Comments on this document?
Primary and Secondary Server Capacity

backup/restore content and frequency are administerable; many are bursty in nature and may
or may not coincide with others.
• Only the major signaling and management paths are included here, further network
bandwidth may be required for SSA, SysMonitor, syslog, SNMP, etc.
• An IP Office port matrix document that covers all possible IP communications should also be
consulted. It is available via the Avaya Support site (https://support.avaya.com).
• Server internal communications do not require bandwidth assessment
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Multi-Site Network Link Capacities

A multi-site network link is the IP Office Line connection between each server (node). The links
are arranged in a star topology with the Primary Server at the center, or double star when a
Secondary is present.
Regardless of direct/indirect media, VCM or codec used, a further capacity consideration is the
multi-site network links between all nodes. Each IP500 V2 or Linux link has a maximum capacity
of 250 channels/calls (500 for IP Office Select Linux servers). The maximum total and outgoing
channels are independently configurable in Manager via the IP Office Line > VoIP Line tab, and
have a default of 128 for both.
This is per link, not a per system limit; for example a Primary or Secondary may have up to
250/500 concurrent calls to each Expansion system. Due to the star topology of IP Office Server
Edition, calls between Expansion systems typically go via the Primary or Secondary and therefore
these calls must also be taken into account when considering Multi-site network link capacity.
For IP Office Select/IP Office Subscription, it is possible to add IP Office lines between expansion
Systems. There is a limit of one link between each pair of expansions. This link can be used
to increase capacity or resilience. Calls between Expansions will go direct rather than via the
Primary/Secondary.
It is not possible to add additional multi-site network links between the Primary/Secondary and
Expansions – if the capacity is exhausted an additional Secondary or Expansion system should be
considered.
The following occurs if the maximum numbers are exceeded:
• If the configured values are exceeded, additional outgoing calls can be routed via ARS
configuration providing an alternative route exists; additional incoming calls are automatically
routed, again providing an alternative route exists.
• Alternative routes only exist when a Secondary Server is present.

August 2024 IP Office Platform Guidelines Capacity 28

Comments on this document?
Resilience and Failover

• If no alternative route, incoming calls remain ringing until a channel is free, outgoing calls
indicate busy.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Resilience and Failover

Resilience is supported in Linux-based networks. However, the use of resilience requires
consideration of various capacity issues:
• The total extensions/users on any single Primary, Secondary or Expansion must not be
configured to exceed their supported limits under any circumstances.
• Primary failure when Secondary present will route all non-local Expansion calls, Voicemail
leave and collect, IVR and Auto Attendants to the Secondary
• Primary failure when Secondary present will move Hunt group processing and management
access to the Secondary. This will increase the management bandwidth from the Secondary
to the Expansion systems.
• Users whose extension or application fails over retain their existing user profiles rights
without needing or consuming an licenses on the fallback server.
• Any voicemail channel entitlements associated with the Primary, move to the Secondary on
failover; no separate license provision on the fallback server is required – unless the dual
active Voicemail Pro feature is enabled.
For further information, refer to the IP Office Resilience Overview manual.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Trunk Capacity
The Primary/Secondary Server supports three types of trunk/line: SIP, H323 and IP Office.

August 2024 IP Office Platform Guidelines Capacity 29

Comments on this document?
Primary and Secondary Server Capacity

System Mode Primary/ Maximum Total SIP Trunk Maximum IP Maximum

Secondary Registered SIP Calls (direct/ Office (SCN) Expansion
server Trunks indirect media) Trunks Systems
IP Office Server Dell R240 125 256/128 32 250
Edition HP DL360G7 250 512/256 32 250
Dell R640 250 512/256 32 250
OVA[1] 250 512/256 32 250
IP Office Select Dell R640 250 1024/512 150 500
IP Office OVA[1] 250 1024/512 150 500
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• The Total SIP Trunk Calls figure is the maximum number of concurrent SIP trunk calls/
sessions for one system. They can be distributed over one or more trunks on the same
system.
• SIP trunk concurrent call capacity is also limited by available licenses and the SIP Line >
SIP URI > Max Calls per Channel setting and the maximum server call capacity. See Call
Capacity on page 16.
• The number of SIP trunk session licenses requested by each system is defined by the
Maximum SIP Sessions setting on the License > Remote Server > Reserved Licenses
tab of IP Office Server Edition Manager. One available SIP Trunk session license enables
one concurrent SIP session or call.
• The maximum number of configured URIs per SIP trunk is 150. This is not correlated with
maximum SIP trunks or concurrent calls or sessions.
• The Maximum Calls/Sessions per SCN Trunk figure is the maximum number of concurrent
sessions supported on a single inter-node link whether WebSocket or Proprietary type. The
number of concurrent sessions is controlled by the Line > IP Office Line > Number of
Channels setting and is also limited by the maximum server call capacity
• H323 trunks are distinct from SCN (IP Office Line), but are taken from the same capacity
pool.
• The above figures are a theoretical maximum; other factors can reduce what can be utilized
on a concurrent basis:
- Available licenses
- Trunk configuration
- Maximum server call capacity

August 2024 IP Office Platform Guidelines Capacity 30

Comments on this document?
Voicemail or Auto-Attendant or IVR

- IP infrastructure
The following occurs if the maximum numbers are exceeded:
Unless administered, IP Office does not limit the number of concurrent trunk calls and makes
a best effort to service all. VoIP voice quality will degrade as load increases; high overload
conditions will cause the server to perform poorly in general.
Related links
Primary and Secondary Server Capacity on page 14

Voicemail or Auto-Attendant or IVR

Leaving a Voicemail for a user or hunt group will use one licensed (and available) voicemail
channel and consume one from the indirect media call capacity of the Voicemail Pro server
(Primary or Secondary).
• If the endpoint is remote, an IP Office Line (SCN trunk) channel is used.
• If the source of the call is digital/analog, a VCM channel is also required.
A voicemail collect operation uses the same resources as voicemail leave. Invoking an Auto
Attendant, Announcement or IVR script uses the same resources as voicemail, and is taken
from the same pool of licenses and voicemail channel capacity; one active Auto Attendants/IVR/
Announcement takes one channel and license.
The total solution voicemail channel capacity is determined by a number of factors:
• The number of per-server supported voicemail channels:
Server Maximum Voicemail Channels
Dell R640/OVA 250
HP DL360 150
Dell R230 75
IP500 V2 40

• If dual Voicemail Pro feature is active (IP Office Select and IP Office Subscription only) – this
doubles the maximum capacity to 500 channels.
• The number of licensed voicemail channels: Each active master Voicemail Pro must have its
own licenses. It inherits the other set when active as a backup.
• Call recording also uses licensed voicemail channels. One active recording channel
consumes one voicemail/AA channel.
Dual Voicemail Server Operation
When the dual Voicemail Pro feature is active (IP Office Select and IP Office Subscription
only) and not under failover conditions, users are provided voicemail services (voicemail,

August 2024 IP Office Platform Guidelines Capacity 31

Comments on this document?
Primary and Secondary Server Capacity

announcements, call recording, auto attendant, IVR, etc) services from one of the Voicemail Pro
servers:
• All Primary users’ voicemail invocations are directed to the Primary Voicemail Pro instance.
• All Secondary users’ voicemail invocations are directed to the Secondary Voicemail Pro
instance.
• All Expansion users’ voicemail invocations are directed to the Voicemail Pro instance defined
by the System > Voicemail > Voicemail Destination setting. This is initially selected by the
Initial Configuration Utility (ICU).
Administration
To ensure Voicemail Pro channel capacity is available for voicemail, call flow and announcement
operations, the IP Office Server Edition Manager settings Voicemail Channel Reservation on the
Primary and Secondary Server’s System > Voicemail tab can be configured to reserve channels
exclusively for specific uses.
Mailbox capacity
The Voicemail Pro automatically creates a mailbox for each user and hunt group in the IP Office
configuration. The individual capacity is fixed at 60 minutes per user or group mailbox.
If voicemail channel resources run out:
• Unanswered calls continue to alert rather than going to voicemail.
• Voicemail collect fails to connect to the voicemail.
• Calls to attendants and call-flows will continue to alert. However, text-to-speech (TTS) will not
be output during call flows.
• Announcements are not played.
• Note that the TTS channel capacity is 250.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
What happens if mailbox storage resources run out?
• Voicemail leave operations will receive an announcement that the user/group’s mailbox is full.
• Voicemail collect will continue to function.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 32

Comments on this document?
Chapter 5: one-X Portal Server

The following Avaya one-X® Portal client capacity is supported with three main options:
• The Avaya one-X® Portal server running on the Primary
• Standalone server IP Office Application Server to allow increased Avaya one-X® Portal user
capacity.
• Second portal server to provide geo-resilience (running on Secondary server or secondary with
second standalone IP Office Application Server)

System Mode Platform Maximum one-X Portal Clients Maximum Solution

Primary Stand Alone Call Rate (BHCC)

IP Office Server Dell R240 375 750 7200

Edition HP DL360G7 750 750 9000
Dell R640 750 750 9000
OVA[1] 750 750 9000
IP Office Select Dell R640 1500 3000 10000
IP Office OVA[1] 1500 3000 10000
Subscription

• Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• The quoted Busy Hour Call Completion (BHCC) rates assumes a Normal call distribution.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• If Avaya one-X® Portal server geo-resilience is required, it must be a Secondary if Primary
one-X server used, or another standalone one-X server if standalone one-X server used.
• The maximum supported total solution call rate is 7,200/9,000/10,000 BHCC when Avaya
one-X® Portal users are active.
• The Avaya one-X® Portal client types can be of any mix, including plugins. HTTP or HTTPS.
• Each connected Avaya one-X® Portal client counts as one load.
• An Avaya Workplace Client counts as one SIP extension and one CTI load. It does not use
Avaya one-X® Portal capacity.

August 2024 IP Office Platform Guidelines Capacity 33

Comments on this document?
one-X Portal Server

• Avaya Communicator for Web counts as one SIP extension, one WebRTC load and one Avaya
one-X® Portal client.

August 2024 IP Office Platform Guidelines Capacity 34

Comments on this document?
Chapter 6: IP500 V2/V2A Servers

This section provides capacity notes for IP500 V2/V2A systems. That includes all modes except IP
Office Basic Edition.
When designing a Server Edition/Select solution that includes an IP500 V2/V2A as an expansion
System, many aspects need to be considered for capacity.
Related links
Audio Conferencing on page 14
Call Capacity on page 37
Call Destination Server on page 18
Call Media Path (IP500 V2/V2A) on page 39
Call Recording on page 19
Call Traffic Profile on page 21
Extension/User Capacity on page 44
Hunt and Presence Groups on page 25
IP Infrastructure, Bandwidth and VoIP QoS on page 26
Multi-Site Network Link Capacities on page 28
Resilience and Failover on page 29
Small Community Network Capacity on page 49
Maximum Trunk Capacity on page 49
VCM Channel Capacity on page 51
Voicemail or Auto-Attendant or IVR on page 31

Audio Conferencing
Primary/Secondary Server
Each Primary and Secondary supports a local audio conference capability with the following
capacities:

August 2024 IP Office Platform Guidelines Capacity 35

Comments on this document?
IP500 V2/V2A Servers

System Mode Primary/Secondary Total Conference Maximum Total Conference

server Channels conference size Channels with
ACCS
IP Office Server Dell R240 128 128 414
Edition HP DL360 256 256 825
Dell R640 256 256 1650
OVA 256 256 1650
IP Office Select Dell R640 512 256 1650
IP Office OVA 512 256 1650
Subscription

IP500 V2/V2A and Linux Expansion System

August 2024 IP Office Platform Guidelines Capacity 36

Comments on this document?
Call Capacity

• V2 Expansion conferences exist in the digital domain; hence all VoIP parties (trunk or
extension) will require a VCM channel for the duration. See VCM Channel Capacity on
page 51.
• Further information on conferences can be found
at: http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/
manager/_frame2.html?Conferencing.Overview.html
Which Servers Conference Resources are Used?
The location of the conference resource used when a conference is started are determined by a
number of factors:
• A user performing an ad-hoc conference uses the conference resources of the server on
which they are logged in.
• A meet-me conference using a user’s personal meet-me bridge uses the conference
resources of the server on which they are logged in.
• A meet-me conference created by Voicemail Pro call flow, or the Conference meet-me short
code feature use the system on which the feature was invoked.
• To invoke a meet-me Conference using the resources of a remote system, use the Line
Group ID field of the Conference Meet Me short code feature. By default this is set to 0, for
local system.
• For the case where a conference is scheduled by Avaya one-X® Portal and at the scheduled
time the conference dials the delegates: The conference location is the server to which the
active Avaya one-X® Portal is attached.
Recording a conference requires an additional conference channel, as well as an IP Office Line
(SCN trunk) channel to the recording destination (Primary or Secondary Server, alternate during
fail over operation). Neither IP Office nor Voicemail Pro can automatically link or move conference
locations, but existing conferences can be connected together.
When conference resources run out, attempts to record calls, join or create conferences are
rejected.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Capacity
The concurrent call capacity between digital/analog extensions and/or digital/analog trunks is
non-blocking. That is, all extensions and trunks can be involved in calls simultaneously. VoIP calls
do not affect this capacity.
The IP500 V2/V2A Expansion has a number of concurrent VoIP call capacities that can influence
the solution design:

August 2024 IP Office Platform Guidelines Capacity 37

Comments on this document?
IP500 V2/V2A Servers

Parameters Concurrent Comment

VoIP calls
Unsecure or Direct media 384 Calls with direct media between VoIP endpoints/trunks.
Secure
Unsecure Indirect media, 120 Calls between the VoIP and digital/analog domain.
IP500 V2 VCM Also limited by the available VCM channel capacity
(see below).
Unsecure or Indirect media, 120 Calls between VoIP endpoints/trunks that cannot go
secure IP500 V2 RTP direct media, but do not require a VCM.
relay
Note that a VCM channel is always required during call
setup.
The value is per call leg. For example 60 H.323
extensions calling 60 H.323
extensions constitutes 120 total calls.
Secure Indirect media, 40 The value is per call leg. This means 40 VCM calls or
IP500 V2 20 indirect media calls if some SRTP settings demand
decoding, then re-encoding.
If a mixed RTP/SRTP call environment, each SRTP leg
removes three from the RTP call capacity.

These are not cumulative VoIP capacity figures – for example, a mixture of two call types changes
the capacity to a value between the two limits. Calls that remain in the digital/analog domain do
not affect this VoIP call capacity.
Administration
Concurrent call maximum capacity can be administered via IP Office Server Edition Manager in a
number ways to ensure limits are not exceeded:
• Number of Channels and Outgoing Channels setting in the Line > VoIP tab of IP Office
lines
• Max Calls per Channel setting in the Line > SIP URI tab of SIP trunks
• Call Admission Control area of the Location settings.
• VoIP Security area of the System settings.
• Media Security area in the Line > VoIP Settings tab.
• Media Security area in the Extension > VoIP tab.
The following occurs if the maximum numbers are exceeded:
Unless administered, the IP500 V2 Expansion does not limit the number of concurrent calls and
makes a best effort to service all. VoIP voice quality will degrade as load increases; high overload
conditions will cause the IP500 V2 Expansion to perform poorly in general.
Related links
IP500 V2/V2A Servers on page 35

August 2024 IP Office Platform Guidelines Capacity 38

Comments on this document?
Call Destination Server

Call Destination Server

Call Media Path (IP500 V2/V2A)

Where calls start and remain in the digital and/or analog domain, the IP500 V2/V2A Expansion’s
VCM and VoIP capacities have no effect. The base non-blocking capacity of the IP500 V2/V2A
Expansion will apply.

August 2024 IP Office Platform Guidelines Capacity 39

Comments on this document?
IP500 V2/V2A Servers

Where calls go between VoIP and digital/analog domains within the IP500 V2/V2A Expansion, the
indirect media limit of 120 concurrent calls and VCM availability will always apply.
Where calls go between VoIP domains (for example SIP trunk to H.323) there are two options:
Direct and indirect media. Direct media does not use the IP500 V2 Expansion’s routing engine and
hence the base capacity of 384 concurrent calls will apply.
Direct media is a configurable parameter for VoIP trunks and extensions with a default of active.
Indirect media will occur either where configured, or if direct media is not possible (even if
configured). Some of the reasons are:
• VoIP traffic routed between the LAN1 and LAN2 interface
• Unsuccessful codec negotiation (including silence suppression, DTMF transport as well as
basic codec support)
• A VoIP endpoint that does not support direct media
• Mismatch of RTP and SRTP
• Mismatched SRTP or SRTCP security settings such as no common cipher suite. These
should be avoided if at all possible due to the limited indirect media SRTP capacity.
• Network Address Translation (NAT) traversal usually associated with Remote Worker phone
deployments.
Related links
IP500 V2/V2A Servers on page 35

Call Recording
Each Primary and Secondary supports a voice call recording capability with the following
capacities:

System Mode Platform Recording Channels

August 2024 IP Office Platform Guidelines Capacity 40

Comments on this document?
Call Recording

System Mode Platform Recording Channels

Server[1] Solution Solution with
ACCS
IP500 V2 Preferred Edition 40 40 40

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• OVA always advertises these figures. However, capacity depends on assigned profiling as
detailed in "Deploying IP Office Servers as Virtual Machines".
• Call recording uses a 3-party conference per recorded call. Note that without ACCS
connected, the primary server does not have sufficient conference channels for the whole
solution - other server's conference resources must be used.
• Conference recording adds a further conference channel to an existing conference.
• Each recording requires one licensed (and available) voicemail channel, a VCM (for the
IP500 V2 Expansion) and IP Office Line (SCN trunk) channel as the recording destination is
on the Primary or Secondary Server. See VCM Channel Capacity on page 51.
• The system supports differing capacity and performance levels when Avaya Contact Center
Select (ACCS) is attached. See Avaya Contact Center Applications on page 12.
• The increased capacities for ACCS are only supported for call recording, and are active when
the application is connected to the host IP Office.
• The solution internal call recording capacity is fixed at 333 hours total (555 hours for IP Office
Select). This is separate from the voicemail mailbox recording capacity, see Voicemail or
Auto-Attendant or IVR on page 31. It is also separate from Media Manager storage capacity,
see Media Manager Recording Capacity on page 64.
• The Media Manager application supports recordings management at the maximum channel
and call rate appropriate to the server platform.
• If the dual Voicemail Pro feature is active IP Office Select and IP Office Subscription only) the
maximum solution capacity is doubled to maximum of 500 channels, the per-server capacity
remains unchanged.
• One active recording channel consumes one voicemail/AA channel. If the call is being
recorded in two places – for example at the user and the incoming trunk – two licensed
and available voicemail channels are required.
• Maximum recording call rate is 7200/9000/10000 BHCC for a primary/secondary Linux-based
server, 3,600 BHCC for an Expansion. See Call Traffic Profile on page 21.
Recording call rate is further reduced for ACCS. See Avaya Contact Center Applications on
page 12.

August 2024 IP Office Platform Guidelines Capacity 41

Comments on this document?
IP500 V2/V2A Servers

Which Servers Conference Resources are Used?

The location of conference resource used is determined by the point of recording:
• Incoming Call Route (ICR) recording is done at trunk’s location
• User recording is done at user’s location.
• Hunt group recording is done at the group's location.
• System recording is done at the system’s location.
• Conference recording at conference location: Ad-hoc conference recording is done at the
initial user's location. Meet-me conference recording can specify the location.
• Account code recording is done at the user's location.
Administration
To ensure Voicemail Pro channel capacity is available for recordings, the IP Office Server Edition
Manager settings Voicemail Channel Reservation on the Primary and Secondary Server’s
System > Voicemail tab can be configured to reserve channels exclusively for specific uses.
• If recording channel resources run out:
- If the recording is mandatory, busy is returned.
- If the recording is not mandatory, further attempts to record calls or conferences are not
successful, but there may still be visual recording indications.
If exceeded:
If recording storage resources run out, further attempts to record calls or conferences will not be
successful and receive announcements to that effect.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Traffic Profile

General traffic engineering is outside the scope of this document, however the following IP Office
Server Edition factors should be considered:

System Mode Platform Maximum Call Rate (BHCC)

Server Solution
IP Office Server Edition Dell R240 7,200 7,200
HP DL360G7 18,000/9,000[3] 18,000/9,000[3]
Dell R640 18,000/9,000[3] 18,000/9,000[3]
Table continues…

August 2024 IP Office Platform Guidelines Capacity 42

Comments on this document?
Call Traffic Profile

System Mode Platform Maximum Call Rate (BHCC)

Server Solution
OVA[1] 18,000/9,000[3] 18,000/9,000[3]
IP Office Select Dell R640[2] 20,000/10,000[3] 20,000/10,000[3]
IP Office Subscription OVA[1, 2] 20,000/10,000[3] 20,000/10,000[3]
All Linux 7200 -
IP500 V2/V2A Expansion 3600 -

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

August 2024 IP Office Platform Guidelines Capacity 43

Comments on this document?
IP500 V2/V2A Servers

Extension/User Capacity
A single IP500 V2/V2A Expansion can support 384 users and up to 384 Analog/digital/IP
extensions (H.323, SIP and or DECT R4). Analog and digital extension capacity is dependent
upon the hardware fitted to the system.
• Maximum users and extensions are configuration limits as well as a currently active/
registered limit.
• Extension and user limits include any resilience fail-over extensions/users; again these are
configuration limits as well as a currently active/registered limit.
• Extension capacity support includes IP Office acting as a server for any DHCP, upgrade and
other operational files. 1600/9600/J100 phone upgrade performance is limited to 50 within 50
minutes for the same phone type.
• Upgrading more than 50 phones at a time from an IP500 V2/V2A is not recommended. If
upgrade performance above these figures are required, an external HTTP/S server can be
used.
• For non-subscription systems, H323, DECT R4 and SIP extension capacity is also limited by
available licenses.
• 9600 H323 Remote worker extensions are supported at a lower capacity; maximum 120.
• 9600 H323 extensions with TLS are supported at a lower capacity; maximum 128. That is,
each VoIP extension that uses TLS reduces the extension capacity by 3.
Related links
IP500 V2/V2A Servers on page 35

Hunt and Presence Groups

System Mode Platform Maximum Maximum Groups Total Hunt

Server Group Server Solution Solution Group
size Members
Essential IP500 V2/V2A 384 200 300 3000
Edition
Preferred
Edition
Table continues…

August 2024 IP Office Platform Guidelines Capacity 44

Comments on this document?
IP Infrastructure, Bandwidth and VoIP QoS

System Mode Platform Maximum Maximum Groups Total Hunt

Server Group Server Solution Solution Group
size Members
IP Office Server Linux/OVA 750 300 300 3000
Edition IP500 V2/V2A 384 200 300 3000
IP Office Select Linux/OVA 1250 600 600 6000
IP Office IP500 V2/V2A 384 200 600 6000
Subscription

IP Infrastructure, Bandwidth and VoIP QoS

August 2024 IP Office Platform Guidelines Capacity 45

Comments on this document?
IP500 V2/V2A Servers

For more information on LAN interface support, see the IP Office Server Edition LAN Support
chapter of "Deploying IP Office Server Edition".
Note that secure VoIP (SRTP) can increase the required bandwidth by up to 8%, see the ‘VoIP
Security’ chapter of Avaya IP Office™ Platform Security Guidelines.
In addition to the network requirements for VoIP calls, additional bandwidth should be reserved for
the corresponding inter-node signaling and management paths. This should include any access
via SSLVPN (IPOSS) or Remote Support Service (RSS). The following suggested minimum
bandwidths should be made available for these additional paths:

Traffic Suggested Minimum Comments

August 2024 IP Office Platform Guidelines Capacity 46

Comments on this document?
IP Infrastructure, Bandwidth and VoIP QoS

Traffic Suggested Minimum Comments

Bandwidth
Voicemail Pro Server <> 1024 kbit/s Bursty traffic, peaking after start-up or restoration of
Voicemail Pro Server Server to Server connectivity
32 kbit/s per active Extra traffic between Secondary and Primary when
channel Dual Voicemail Pro active
Voicemail Pro Server <> 32 kbit/s per active Bursty SFTP traffic, between Primary and external
IP Office Media Manager channel server running IP OfficeMedia Manager. Typically IP
Office Media Manager runs coresident with Voicemail
Pro. For dual active Voicemail Pro, the Secondary
Voicemail Pro will send all recordings to the server
running IP Office Media Manager.
WebRTC Client 6 – 256 kbit/s Between each active Avaya Communicator for Web
client and the WebRTC Gateway
one-X Server <> one-X 1–500 users: 512 kbit/s Bursty traffic, peaking after start-up or restoration of
Server Server to Server connectivity
500–1500 users: 1024
kbit/s
1500–3000 users: 2048
kbit/s
SoftConsole 64–1024 kbit/s Bursty traffic, peaking after start-up. Higher figure for
maximum 3000 user deployment.
Between each SoftConsole application and the IP
Office server.
SMDR 1 kbit per call report (or Average SMDR message size for typical call pattern
7.2 kbit/s @ 7,200 BHCC)
RSS to co-located 64 –1024 kbit/s per TCP Between remote client and col-located server when a
server Tunnel remote management session is active

• These figures are for general guidance only as they do not reflect the specific requirements
for a given installation. For example management operations are typically session based;
backup/restore content and frequency are administerable; many are bursty in nature and may
or may not coincide with others.
• Only the major signaling and management paths are included here, further network
bandwidth may be required for SSA, SysMonitor, syslog, SNMP, etc.
• An IP Office port matrix document that covers all possible IP communications should also be
consulted. It is available via the Avaya Support site (https://support.avaya.com).
• Server internal communications do not require bandwidth assessment
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 47

Comments on this document?
IP500 V2/V2A Servers

Multi-Site Network Link Capacities

Resilience and Failover

August 2024 IP Office Platform Guidelines Capacity 48

Comments on this document?
Small Community Network Capacity

• Primary failure when Secondary present will route all non-local Expansion calls, Voicemail
leave and collect, IVR and Auto Attendants to the Secondary
• Primary failure when Secondary present will move Hunt group processing and management
access to the Secondary. This will increase the management bandwidth from the Secondary
to the Expansion systems.
• Users whose extension or application fails over retain their existing user profiles rights
without needing or consuming an licenses on the fallback server.
• Any voicemail channel entitlements associated with the Primary, move to the Secondary on
failover; no separate license provision on the fallback server is required – unless the dual
active Voicemail Pro feature is enabled.
For further information, refer to the IP Office Resilience Overview manual.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Small Community Network Capacity

IP500 V2 servers can be used in a network of IP Office servers. The details here cover IP500 V2
servers connected in a Small Community Network (SCN). For use as expansion servers in Server
Edition/Select networks, see Extension/User/Site Capacity on page 23.
Small Community Network Capacity
• Maximum: 32 nodes with a total of 1000 users.
Related links
IP500 V2/V2A Servers on page 35

Maximum Trunk Capacity

A single IP500 V2/V2A Expansion can support up to:
• 204 Analog trunks total
• 8 E1/PRI digital trunks with 240 channels total
• 8 T1/PRI digital trunks with 192 channels total
• 16 BRI digital trunks with 32 channels total
• 125 SIP trunks with 128 concurrent calls total
• 32 H323/SCN trunks with 250 concurrent calls per trunk

August 2024 IP Office Platform Guidelines Capacity 49

Comments on this document?
IP500 V2/V2A Servers

This is a theoretical maximum possible trunk channels that can be supported, but other factors will
reduce what can be utilised on a concurrent basis:
• Available licenses
• Trunk configuration
• VCM channels
• Maximum server call capacity
Analog and digital trunk capacity is dependent upon the hardware fitted to the system unit. The
following table shows the various constructs and the resulting maximum (note that many variants
are not shown):

Trunk Trunk Trunk Trunk Exp. Exp. Max BRI Max PRI Max
Card #1 Card #2 Card #3 Card #4 Module Module E1/T1 Analog
#1-8 #9-12
Dual PRI Dual PRI Dual PRI Dual PRI ATM 16 - 0 240/192 128
ATM 4 ATM 4 ATM 4 4 Port ATM 16 ATM 16 0 0 204
Exp.
BRI 8 BRI 8 BRI 8 BRI 8 ATM 16 - 32 0 128
- - - - - - 0 0 0

Server Type Maximum Total SIP Trunk Maximum IP Office Maximum Calls per
Registered SIP Calls (direct/ (SCN) Trunks SCN Trunk
Trunks indirect media)
IP500 V2/V2A 125 128/120 32 250

• The Total SIP Trunk Calls figure is effectively the maximum number of concurrent SIP trunk
calls/sessions. They can be distributed over one or more trunks on the same system.
• SIP trunk concurrent call capacity is also limited by available licenses and the SIP Line > SIP
URI > Max Calls per Channel setting.
• The number of SIP Trunk session licenses requested by each system is defined by the
Maximum SIP Sessions setting on the License > Remote Server > Reserved Licenses
tab of IP Office Server Edition Manager. One available SIP Trunk session license enables
one concurrent SIP session/call.
• The maximum number of configured URIs per SIP trunk is 150. This is not correlated with
maximum SIP trunks or concurrent calls.
• The Maximum Calls per SCN Trunk figure is the maximum number of concurrent sessions
supported on a single inter-node link whether WebSocket or Proprietary type. Note that the
number of SCN channels is controlled by the Number of Channels setting on the IP Office
Line > Line tab of IP Office Server Edition Manager.
• H323 trunks are distinct from SCN, but are taken from the same capacity pool.
• The PRI trunk capacity is also limited by available licenses. One available PRI Trunk Channel
license enables one concurrent PRI call.

August 2024 IP Office Platform Guidelines Capacity 50

Comments on this document?
VCM Channel Capacity

Related links
IP500 V2/V2A Servers on page 35

VCM Channel Capacity

Voice Compression Module (VCM) channels allow the IP500 V2 Expansion to convert media (for
example speech) between analog/digital and IP. These are essential when routing analog/digital
trunk calls to or from VoIP endpoints.
It is important to note that in a Linux-based server network, media communication with any other
server components requires the use of VoIP, including Primary, Secondary, other expansions, call
recording, attendants, IVR, conferencing and voicemail.
Local IP500 V2/V2A Expansion conferences and music on hold use the digital domain; hence all
VoIP parties (trunk or extension) require a VCM channel.
VCM channels are also used to perform VoIP transcoding. Transcoding is used where the VoIP
codec differs between two legs of a call; for example a VoIP endpoint supporting only G.729
calling a SIP trunk with only G.711. This case uses 2 VCM channels and should be avoided
wherever possible.
The following table summarizes VCM channel usage.

Endpoint A Endpoint B Channels used Notes

[1]

Analog/Digital trunk Analog/Digital trunk None D100 and DECT R4 endpoints are classified
or extension or extension as VoIP
Local Conference None Conference hosted on the IP500 V2
Local Music on Hold None
Embedded Voicemail None Includes voicemail, attendants,
announcements Embedded Voicemail not
supported in IP Office Server Edition
Analog/Digital trunk VoIP trunk or 1
or extension extension
Central Voicemail 1 Includes voicemail, IVR attendants,
announcements
Remote Conference 1
Remote Music on 1 Maximum of 3 MOH sources streamed from
Hold Primary Server using a maximum of 3 VCM
channels
Call recording 1 Using Voicemail Pro or ACCS.
Table continues…

August 2024 IP Office Platform Guidelines Capacity 51

Comments on this document?
IP500 V2/V2A Servers

Endpoint A Endpoint B Channels used Notes

[1]

VoIP trunk or VoIP trunk or None[2] VoIP endpoints includes IP Office Line (SCN
extension extension trunk), SM and H323 lines, DECT endpoints
Central Voicemail None[2] Includes voicemail, IVR attendants,
announcements
Remote Conference None[2]
Remote Music on None[2] Streamed from Primary Server
Hold
Call recording None[2] Using Voicemail Pro or ACCS.
VoIP trunk or Analog/Digital trunk 1
extension or extension
Local Conference 1 Conference hosted on the IP500 V2
Local Music on Hold 1 per MOH Maximum of 4 MOH sources. One VCM
source[2] channel is used per codec type per source.
Embedded Voicemail 1 Includes voicemail, attendants,
announcements
Embedded Voicemail is only supported for
non-networked IP500 V2/V2A servers.

1. 1. Unless otherwise specified, the VCM channel is used for the duration of the call and the
VCM resource is always local.
2. 2. Assumes both endpoints’ VoIP codecs match, if they do not match 2 VCM channels are
used.
Three base card types provide VCM channel capacity for the IP500 V2/V2A Expansion:
• VCM 32
• VCM 64
• Combination card
Each base card can carry a trunk module, however the Combo card can only support BRI and
analog. Hence, if more than two dual PRI cards are required, the VCM capacity is reduced. Also
note that the type of trunk module fitted to the Combo card is fixed.
The following table shows various constructs and the resulting theoretical maximum. Not all the
variants are listed. Only those variants that provide the maximum capacity are listed.

Base Card Base Card Base Card Base Card Maximum Maximum Maximum Maximum
#1 #2 #3 #4 G.711 calls G.729 calls G.723 calls G.722 calls
VCM 64 VCM 64 - - 128 120 88 120
VCM 64 VCM 64 Combo - 138 130 98 130
VCM 64 VCM 64 Combo Combo 148 140 108 140

August 2024 IP Office Platform Guidelines Capacity 52

Comments on this document?
Voicemail or Auto-Attendant or IVR

The capacity in the above table is for a bidirectional channel between a VoIP and an analog or
digital endpoint and assumes the calls are of the same codec type. Differing codec types can be
supported at the same time; the lowest channel figure should be used for calculations.
If VCM channels are used to convert SRTP media, a maximum of 40 calls per system are
supported regardless of codec type.
The IP500 V2/V2A Expansion manages this common resource as efficiently as possible but if
there are insufficient at any one time:
• Outgoing calls will not get connected (they do not receive dial tone)
• Incoming calls will queue until a VCM channel is free
• Transfers cannot be made
Related links
IP500 V2/V2A Servers on page 35

Voicemail or Auto-Attendant or IVR

August 2024 IP Office Platform Guidelines Capacity 53

Comments on this document?
IP500 V2/V2A Servers

• Call recording also uses licensed voicemail channels. One active recording channel
consumes one voicemail/AA channel.
Dual Voicemail Server Operation
When the dual Voicemail Pro feature is active (IP Office Select and IP Office Subscription
only) and not under failover conditions, users are provided voicemail services (voicemail,
announcements, call recording, auto attendant, IVR, etc) services from one of the Voicemail Pro
servers:
• All Primary users’ voicemail invocations are directed to the Primary Voicemail Pro instance.
• All Secondary users’ voicemail invocations are directed to the Secondary Voicemail Pro
instance.
• All Expansion users’ voicemail invocations are directed to the Voicemail Pro instance defined
by the System > Voicemail > Voicemail Destination setting. This is initially selected by the
Initial Configuration Utility (ICU).
Administration
To ensure Voicemail Pro channel capacity is available for voicemail, call flow and announcement
operations, the IP Office Server Edition Manager settings Voicemail Channel Reservation on the
Primary and Secondary Server’s System > Voicemail tab can be configured to reserve channels
exclusively for specific uses.
Mailbox capacity
The Voicemail Pro automatically creates a mailbox for each user and hunt group in the IP Office
configuration. The individual capacity is fixed at 60 minutes per user or group mailbox.
If voicemail channel resources run out:
• Unanswered calls continue to alert rather than going to voicemail.
• Voicemail collect fails to connect to the voicemail.
• Calls to attendants and call-flows will continue to alert. However, text-to-speech (TTS) will not
be output during call flows.
• Announcements are not played.
• Note that the TTS channel capacity is 250.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
What happens if mailbox storage resources run out?
• Voicemail leave operations will receive an announcement that the user/group’s mailbox is full.
• Voicemail collect will continue to function.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 54

Comments on this document?
Chapter 7: Linux Expansion Server

When designing a IP Office Server Edition solution that includes a Linux-based Expansion System,
the same aspects that are covered for the IP500 V2/V2A Servers on page 35 need to be assessed,
with the following differences:
• Maximum extension capacity for each Linux Expansion:
- No digital or analog extensions
- Maximum users/extensions 750 (including DECT R4).
- 128 maximum remote worker 9600 Series H323 extensions.
• Maximum trunk capacity for each Linux Expansion:
- No digital or analog trunks.
- Maximum SIP sessions/calls 256 total.
• The concurrent call capacity of the Linux Expansion:
- No analog/digital calls
- Indirect media capacity 128 (64 when SRTP used)
- Direct media capacity 750
• The VCM channel capacity for each Linux Expansion:
- Only transcoding is relevant; 128 channels
- There is no capacity difference due to codec type
Note:
The server type may additionally be an HP DL360G7, Dell R640 or OVA. However, the
supported capacities/performance are not increased.
All of the above should be assessed as one factor may limit another.

August 2024 IP Office Platform Guidelines Capacity 55

Comments on this document?
Chapter 8: General Capacity
Considerations

The following capacity topics apply to all types of server and mode of operations.
Related links
Account Codes on page 57
Audio Conferencing on page 14
Button Modules on page 59
Appearance Button Programming on page 60
Call Destination Server on page 18
Call Logs/Call History on page 61
Call Recording on page 19
Media Manager Recording Capacity on page 64
Call Traffic Profile on page 21
CTI & TAPI on page 66
DECT R4 on page 67
Directory on page 68
Hunt and Presence Groups on page 25
Incoming Call Routes on page 69
IP Infrastructure, Bandwidth and VoIP QoS on page 26
IP Office SoftConsole on page 72
Multi-Site Network Link Capacities on page 28
Paging on page 74
Remote Support Services on page 75
Resilience and Failover on page 29
Unified Messaging Capacity on page 76
Voicemail or Auto-Attendant or IVR on page 31
WebRTC Gateway on page 79
WebLM Server on page 80

August 2024 IP Office Platform Guidelines Capacity 56

Comments on this document?
Account Codes

Account Codes
A maximum of 1500 account codes are supported on any IP Office server. For servers in a
network using consolidated obejcts, that also sets the maximum for the whole network.
The maximum is for account codes entered into the system configuration. Using wildcards in the
account code entries, a larger number of dialed account codes can match configured codes.
Related links
General Capacity Considerations on page 56

IP500 V2/V2A and Linux Expansion System

August 2024 IP Office Platform Guidelines Capacity 57

Comments on this document?
General Capacity Considerations

Notes
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• OVA always advertises these figures. However, capacity depends on assigned profiling as
detailed in "Deploying IP Office Servers as Virtual Machines".
• The figures cover both ad-hoc and meet-me conference types.
• With one-X Portal users active, a solution-wide limit of 750 conference channel participants
applies, but this does not include conferences used for call recording.
• IP Office Server Edition supports differing capacity and performance levels when Avaya
Contact Center Select (ACCS) is attached. See Avaya Contact Center Applications on
page 12.
• The increased capacities for ACCS are only supported when the applications are actively
connected to the host IP Office and should only be used for call recording purposes.
• No dynamic solution-wide conference allocation is supported, only static via call flows or
Conference Meet Me short code Line Group ID.
• V2 Expansion conferences exist in the digital domain; hence all VoIP parties (trunk or
extension) will require a VCM channel for the duration. See VCM Channel Capacity on
page 51.
• Further information on conferences can be found
at: http://marketingtools.avaya.com/knowledgebase/businesspartner/ipoffice/mergedProjects/
manager/_frame2.html?Conferencing.Overview.html
Which Servers Conference Resources are Used?
The location of the conference resource used when a conference is started are determined by a
number of factors:
• A user performing an ad-hoc conference uses the conference resources of the server on
which they are logged in.
• A meet-me conference using a user’s personal meet-me bridge uses the conference
resources of the server on which they are logged in.
• A meet-me conference created by Voicemail Pro call flow, or the Conference meet-me short
code feature use the system on which the feature was invoked.
• To invoke a meet-me Conference using the resources of a remote system, use the Line
Group ID field of the Conference Meet Me short code feature. By default this is set to 0, for
local system.
• For the case where a conference is scheduled by Avaya one-X® Portal and at the scheduled
time the conference dials the delegates: The conference location is the server to which the
active Avaya one-X® Portal is attached.
Recording a conference requires an additional conference channel, as well as an IP Office Line
(SCN trunk) channel to the recording destination (Primary or Secondary Server, alternate during
fail over operation). Neither IP Office nor Voicemail Pro can automatically link or move conference
locations, but existing conferences can be connected together.

August 2024 IP Office Platform Guidelines Capacity 58

Comments on this document?
Button Modules

When conference resources run out, attempts to record calls, join or create conferences are
rejected.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Button Modules
Button module capacity is defined in terms of the total number of additional buttons per system,
whether used or not.

System Mode Platform Total Maximum

Buttons BM32 DBM32 BM12 Appearances
[1]
SBM24
JBM24
JEM24[2]
IP Office Server All 4096 128 - 170 20
Edition
IP Office Select All 8192 256 - 340 40
IP Office
Subscription
All IP500 V2/ V2A 1024 32 32 42 10

1. Maximum Appearances is the supported limit for the total solution-wide buttons that can be
programmed to the same call appearance, line appearance or covered user.
2. With J179/J169 phones, JEM24 button module capacity depends on whether a single or
multiple modules are attached to phones:
• A single JEM24 module on a phone provides 72 buttons in 3 pages of 24. In this mode,
single modules are equivalent to 3 modules for overall capacity.
• Multiple JEM24 modules on a phone only provide 24 buttons each.
• Capacities are regardless of whether the buttons are configured for use or not, and whether
physical or logical (as in the case of BM12 or JEM24).
- BM12: 24 buttons each in 2 pages of 12. 9608, 9611 and 9641 IP telephones.
- BM32: 32 buttons each. 1616 IP telephones.
- DBM32: 32 buttons each. 1416 digital telephones.
- JBM24: 24 buttons each. J169 and J179 IP telephones.

August 2024 IP Office Platform Guidelines Capacity 59

Comments on this document?
General Capacity Considerations

- JEM24: J169/J179 - 24 or 72 buttons each, see note 2 above. J189 - 24 buttons each.
- SBM24: 24 buttons each. 9608, 9611 and 9641 IP telephones.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
Related links
General Capacity Considerations on page 56

Appearance Button Programming

The following limits apply to appearance buttons:
• Supported maximum number of bridged appearances to the same call appearance.
• Supported maximum number of line appearances to the same line.
• Supported maximum number of call coverage appearances of the same covered user.
The limits are:
• 10 for IP500 V2/V2A systems.
• 20 for Server Edition.
• 40 for Server Edition Select and Linux-based IP Office Subscription.
MADN Buttons
You can have up to 30 MADN buttons associated with the same user.
Related links
General Capacity Considerations on page 56

Call Destination Server

August 2024 IP Office Platform Guidelines Capacity 60

Comments on this document?
Call Logs/Call History

• Conferencing when the conference focus is not the local system - one VoIP channel per local
member
• Local conferences involving remote users - one VoIP channel per remote member when
connected to the conference
• Voicemail leave and collect - one VoIP channel per VM caller when. Destination is the
location of the active Voicemail Pro.
• Announcements - one VoIP channel per call when generating announcements. Destination is
the location of the active Voicemail Pro.
• Centralized Music on Hold – one VoIP channel per central MOH source when playing to held
calls. Destination is the location of the Music on Hold source.
For all VoIP connections between systems, the codec used will be according to the IP Office Line
settings of those two nodes.
Consideration should also be given to intermediate destinations to ensure adequate capacity is
present. For example a consultation call will open a secondary channel for the consultation whilst
keeping the initial call connected.
Lastly, any call on the IP Office Line will take into consideration administered channel limits
and Call Admission Control (CAC) if active. Please refer to the CAC section of the IP Office
administration documentation for behaviors when CAC limits are exceeded.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Call Logs/Call History

The following call log capacities are supported:

Platform Personal Call Log Per User

Linux/OVA[1] 60
IP500 V2/V2A 30

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• For calls from/to the same number, the system only keeps the details of the last such call
status plus a count of the number of such calls.
• If a user hot desks to/from a IP500 V2/V2A Expansion, only the last 30 retained.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.

August 2024 IP Office Platform Guidelines Capacity 61

Comments on this document?
General Capacity Considerations

• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.

Related links
General Capacity Considerations on page 56

Call Recording
Each Primary and Secondary supports a voice call recording capability with the following
capacities:

System Mode Platform Recording Channels

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

August 2024 IP Office Platform Guidelines Capacity 62

Comments on this document?
Call Recording

• The solution internal call recording capacity is fixed at 333 hours total (555 hours for IP Office
Select). This is separate from the voicemail mailbox recording capacity, see Voicemail or
Auto-Attendant or IVR on page 31. It is also separate from Media Manager storage capacity,
see Media Manager Recording Capacity on page 64.
• The Media Manager application supports recordings management at the maximum channel
and call rate appropriate to the server platform.
• If the dual Voicemail Pro feature is active IP Office Select and IP Office Subscription only) the
maximum solution capacity is doubled to maximum of 500 channels, the per-server capacity
remains unchanged.
• One active recording channel consumes one voicemail/AA channel. If the call is being
recorded in two places – for example at the user and the incoming trunk – two licensed
and available voicemail channels are required.
• Maximum recording call rate is 7200/9000/10000 BHCC for a primary/secondary Linux-based
server, 3,600 BHCC for an Expansion. See Call Traffic Profile on page 21.
Recording call rate is further reduced for ACCS. See Avaya Contact Center Applications on
page 12.
Which Servers Conference Resources are Used?
The location of conference resource used is determined by the point of recording:
• Incoming Call Route (ICR) recording is done at trunk’s location
• User recording is done at user’s location.
• Hunt group recording is done at the group's location.
• System recording is done at the system’s location.
• Conference recording at conference location: Ad-hoc conference recording is done at the
initial user's location. Meet-me conference recording can specify the location.
• Account code recording is done at the user's location.
Administration
To ensure Voicemail Pro channel capacity is available for recordings, the IP Office Server Edition
Manager settings Voicemail Channel Reservation on the Primary and Secondary Server’s
System > Voicemail tab can be configured to reserve channels exclusively for specific uses.
• If recording channel resources run out:
- If the recording is mandatory, busy is returned.
- If the recording is not mandatory, further attempts to record calls or conferences are not
successful, but there may still be visual recording indications.
If exceeded:
If recording storage resources run out, further attempts to record calls or conferences will not be
successful and receive announcements to that effect.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35

August 2024 IP Office Platform Guidelines Capacity 63

Comments on this document?
General Capacity Considerations

General Capacity Considerations on page 56

Media Manager Recording Capacity

Media Manager requires an additional drive which it use as the location of its primary call storage
folder. Media Manager uses this location to store recordings after transferring them from the
temporary storage folder used by Voicemail Pro.
Important:
• Avaya does not support Media Manager using the same drive that is hosting the
Voicemail Pro service. Doing so will cause space conflicts with other IP Office
applications and risks losing recordings during other IP Office maintenance activities.
You must either:
• Add an additional drive to the server hosting the Voicemail Pro service. Avaya recommends
you add a pair of drives configured for RAID.
• Configure a cloud-based service as the primary call storage. Media Manager supports the
following:
- Google Bucket
- Azure Blob
- Amazon S3 Bucket
• Warning:
- When using storage other than an additional hard-disk in the IP Office system, you
must check the file aging policies of that other storage, as they may differ from the file
aging policy applied by the Media Manager settings.
In operation, you can optimize the use of the primary call storage by having Media Manager also
copy recordings to separate archive storage, which can be a DVD, NAS or cloud-based storage.
After a time, the primary call storage will contain just the newest recordings whilst the archive
contains old recordings.
Estimating the storage capacity required
The required capacity for the storage you use for Media Manager depends on factors that will
vary between different customers. You need to estimate the typical number and length of calls
recordings that the customer's business will generate.
You also need to include how long the customer wants to retain recordings, and how the customer
wants to use recordings in the primary call storage and those in a separate archive (if installed).
For both types of storage, you can use the following figures:
• Media Manager recordings require 60KB a minute for non-authenticated files, 120KB a
minute for authenticated files.

August 2024 IP Office Platform Guidelines Capacity 64

Comments on this document?
Call Traffic Profile

• For the primary call storage, the minimum size Avaya support is 30GB. However, Avaya
recommends 300GB or larger.
Related links
General Capacity Considerations on page 56

Call Traffic Profile

General traffic engineering is outside the scope of this document, however the following IP Office
Server Edition factors should be considered:

System Mode Platform Maximum Call Rate (BHCC)

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

August 2024 IP Office Platform Guidelines Capacity 65

Comments on this document?
General Capacity Considerations

• The Maximum Solution Call Rate can be further reduced by the presence of Call recording,
CTI or Contact Center application such as ACCS. See Avaya Contact Center Applications on
page 12.
• IP Office Subscription is an OPEX licensed offer which supports the same capacity and
performance as IP Office Select (see IP Office Select/IP Office Subscription on page 11). A
stand-alone IP500 V2/V2A running IP Office Subscription has the same capacity as other
IP500 V2/V2A offers (see IP500 V2/V2A Servers on page 35 ).
The following occurs if these figures are exceeded:
If the call rate is exceeded, there may be disruption to call voice quality, recordings, or a general
slowdown in other operation such as UC or management clients.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

CTI & TAPI

Each CTI or TAPI connection contributes to the overall loading of a system, whether directly or
indirectly connected. Capacity is specified in three ways per system:
• Total number of CTI links (sessions)
• Number of CTI controlled users per session
• Total number of CTI controlled users

System Mode Platform Maximum CTI Maximum CTI Total CTI Maximum
sessions users per controlled BHCC
session users
IP Office Server Dell R240 5 750 3750 9000
Edition HP DL360G7 5 1500 7500 9000
Dell R640 5 2000 10000 9000
OVA[1] 5 2000 15000 10000
IP Office Select Dell R640 5 3000 15000 10000
IP Office OVA[1] 5 3000 15000 10000
Subscription
All IP500 V2/V2A 3 384 1152 7200

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• The quoted Busy Hour Call Completion (BHCC) rates assumes a Normal call distribution.

August 2024 IP Office Platform Guidelines Capacity 66

Comments on this document?
DECT R4

• An active Avaya one-X® Portal or ACCS server counts as one CTI session for each and
every server in the solution.
• An active Avaya one-X® Portal is one that has at least one portal client of any type or an open
API session.
• An active 3rd Party TAPI session counts as one CTI session for that IP Office.
• All 1st party TAPI sessions together count as one CTI session for that IP Office.
• An active one-X Portal makes every user a CTI controlled user for each and every system.
• An active ACCS makes every Agent a CTI controlled user for that IP Office.
• An active portal open API session counts as one CTI session for each and every system.
• A single portal open API session supports the BHCC and CTI users per session quoted
above.
• An Avaya Workplace Client counts as one SIP extension and one CTI load. It does not use
Avaya one-X® Portal capacity.
• Avaya Communicator for Web counts as one SIP extension, one WebRTC load and one
Avaya one-X® Portal client.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
Related links
General Capacity Considerations on page 56

DECT R4
The IP Office system can support DECT handsets through the attachment of a DECT R4 system.
The following capacity considerations apply:
• The DECT handset capacity must be within the overall extension capacity of the IP Office
system solution.
• Each DECT R4 system supports:
- A maximum of 750 DECT extensions (384 on IP500 systems).
- A maximum of 256 DECT base stations. 128 of those can be digital base stations
connected through IP DECT Digital Gateways.
- For digital base stations, up to 8 IP DECT Digital Gateways, each supporting up to 16
digital base stations.
- Up to 2000 directory entries from the IP Office system.
Related links
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 67

Comments on this document?
General Capacity Considerations

Directory
The following directory capacities are supported:
Platform System Directory Personal Directory
LDAP HTTP Configuration Per User Per System
Linux/OVA[1] 10,000 10,000 10,000 250 100,000
IP500 V2/V2A 10,000 10,000 2,500 250 10,800

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• The system directory capacity is solution-wide and cannot exceed 10,000 entries total
• Any duplicate entries are discarded on import.
• Only the Primary can be administered with external directory entries as part of the
configuration.
• The display of directory entries is limited on some phones:
- 1100/1200 cannot support above 1000 directory entries.
- DECT R4 cannot support above 2000 directory entries.
- D100/D160 DECT cannot support above 100 directory entries.
• If the number of supported entries is exceeded, the directory is truncated to the supported
system limit.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
Related links
General Capacity Considerations on page 56

Hunt and Presence Groups

August 2024 IP Office Platform Guidelines Capacity 68

Comments on this document?
Incoming Call Routes

System Mode Platform Maximum Maximum Groups Total Hunt

Incoming Call Routes

The following maximums apply to the number of supported incoming call routes.

System Mode Platform Maximum Server Maximum Solution

IP Office Server Edition 2300 4600
Table continues…

August 2024 IP Office Platform Guidelines Capacity 69

Comments on this document?
General Capacity Considerations

System Mode Platform Maximum Server Maximum Solution

IP Office Select 3000 6000
IP Office Subscription
Expansion Linux 1000 As above
IP500 V2/V2A 1000 -

Related links
General Capacity Considerations on page 56

IP Infrastructure, Bandwidth and VoIP QoS

August 2024 IP Office Platform Guidelines Capacity 70

Comments on this document?
IP Infrastructure, Bandwidth and VoIP QoS

Traffic Suggested Minimum Comments

Bandwidth
Inter-node Signaling/ 256 kbit/s Between Primary and each Expansion
Status
Between Primary and Secondary
Between Secondary and each Expansion.
Limited signaling/status directly between Expansions
Bursty traffic, peaking after start-up or restoration of
node to node connectivity.
one-X Portal CTI 96 kbit per call (or 192 Between one-X Portal server location and Expansion
kbit/s @ 7,200 BHCC) when one-X Portal server active.
Web Management 512 kbit/s Between Web Manager PC and Primary (or Secondary
under failover conditions) when a Web Management
session is active
IP Office Server Edition 512 kbit/s Between SE Manager PC and each node when a IP
Manager Office Server EditionManager session is active
Upgrade 512 kbit/s Between Primary and each node when upgrade is
being performed
Backup/Restore 256 – 2048 kbit/s Between Backup Server and each Expansion
Between Backup Server and Primary
Between Backup Server and Secondary
An IP Office Linux platform can be designated as the
backup server.
Bandwidth is only required when a backup or restore
operation is active, and only between participating
nodes.
The bandwidth required depends on the backup/
restore content.
Voicemail Pro client 512 kbit/s Between Voicemail Pro PC and Primary (or Secondary
under failover conditions) when a Voicemail Pro server
management session is active
Voicemail Pro Server <> 1024 kbit/s Bursty traffic, peaking after start-up or restoration of
Voicemail Pro Server Server to Server connectivity
32 kbit/s per active Extra traffic between Secondary and Primary when
channel Dual Voicemail Pro active
Voicemail Pro Server <> 32 kbit/s per active Bursty SFTP traffic, between Primary and external
IP Office Media Manager channel server running IP OfficeMedia Manager. Typically IP
Office Media Manager runs coresident with Voicemail
Pro. For dual active Voicemail Pro, the Secondary
Voicemail Pro will send all recordings to the server
running IP Office Media Manager.
Table continues…

August 2024 IP Office Platform Guidelines Capacity 71

Comments on this document?
General Capacity Considerations

Traffic Suggested Minimum Comments

Bandwidth
WebRTC Client 6 – 256 kbit/s Between each active Avaya Communicator for Web
client and the WebRTC Gateway
one-X Server <> one-X 1–500 users: 512 kbit/s Bursty traffic, peaking after start-up or restoration of
Server Server to Server connectivity
500–1500 users: 1024
kbit/s
1500–3000 users: 2048
kbit/s
SoftConsole 64–1024 kbit/s Bursty traffic, peaking after start-up. Higher figure for
maximum 3000 user deployment.
Between each SoftConsole application and the IP
Office server.
SMDR 1 kbit per call report (or Average SMDR message size for typical call pattern
7.2 kbit/s @ 7,200 BHCC)
RSS to co-located 64 –1024 kbit/s per TCP Between remote client and col-located server when a
server Tunnel remote management session is active

IP Office SoftConsole
IP Office SoftConsole is an operator/receptionist application that can be assigned to particular
extension users.

August 2024 IP Office Platform Guidelines Capacity 72

Comments on this document?
Multi-Site Network Link Capacities

Platform Maximum SoftConsole Users Monitor Max. Hunt

Server Solution Groups / Users

Standard/IP Office Linux/OVA[1] 10 32 20

Server Edition IP500 V2/V2A 4 32 10
IP Office Select Linux/OVA[1] 10 75 40
IP Office IP500 V2/V2A 4 75 10
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• The number of supported IP Office SoftConsole users depends on licensing/subscriptions:
- For IP Office Subscription mode systems, the maximums and the number of subscriptions
control the number of users who can be configured as IP Office SoftConsole users.
- For other modes, the maximums and the number of licenses control the number of
simultaneous active IP Office SoftConsole users
• Monitor Max. Hunt Groups /Users - The maximum active IP Office SoftConsole applications
that can be used to monitor the same hunt group or user.
• IP Office Manager does not permit more than 32 IP Office SoftConsole users if the solution is
not IP Office Select or IP Office Subscription.
Related links
General Capacity Considerations on page 56

Multi-Site Network Link Capacities

August 2024 IP Office Platform Guidelines Capacity 73

Comments on this document?
General Capacity Considerations

to increase capacity or resilience. Calls between Expansions will go direct rather than via the
Primary/Secondary.
It is not possible to add additional multi-site network links between the Primary/Secondary and
Expansions – if the capacity is exhausted an additional Secondary or Expansion system should be
considered.
The following occurs if the maximum numbers are exceeded:
• If the configured values are exceeded, additional outgoing calls can be routed via ARS
configuration providing an alternative route exists; additional incoming calls are automatically
routed, again providing an alternative route exists.
• Alternative routes only exist when a Secondary Server is present.
• If no alternative route, incoming calls remain ringing until a channel is free, outgoing calls
indicate busy.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Paging
The paging function is limited by the number of extensions present in the paging group, and the
platform type.

System Mode Platform Maximum Paging Group Size

IP Office Server Edition Dell R240 128
HP DL 360 128
Dell R640 512
OVA[1] 512
IP Office Select Dell R640 512
IP Office Subscription OVA[1] 512
All IP500 V2/V2A 64

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• Paging groups that include any user on a IP500 V2/V2A Expansion are limited to 64.
• Paging groups with SRTP endpoints reduces the maximum size pro-rata up to 50%.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.

August 2024 IP Office Platform Guidelines Capacity 74

Comments on this document?
Remote Support Services

• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.

Related links
General Capacity Considerations on page 56

Remote Support Services

Remote Support Services (RSS) is a TCP tunneling mechanism supported by IP Office
Subscription, used for both internal IP Office and co-located server management interfaces.
The following RSS capacities are supported:
Platform Total RSS Maximum TCP Notes
bandwidth Mbit/s Tunnels
Dell R240 10 64 -
HP DL360 10 64 -
Dell R640 20 64 Assumes sufficient VM resources
assigned.
OVA[1] 20 64 -
IP500 V2 1 64 -

Notes
• No bandwidth limits are enforced
• RSS traffic flows between the Primary and Secondary or Expansion using the IP Office line
• The RSS bandwidth of the Primary also determines the total Server Edition deployment
bandwidth
The following occurs if these figures are exceeded:
• If total bandwidth is exceeded, general IP Office processing capacity and performance will
reduce. High overload conditions will cause the IP Office to perform poorly in general.
Related links
General Capacity Considerations on page 56

Resilience and Failover

August 2024 IP Office Platform Guidelines Capacity 75

Comments on this document?
General Capacity Considerations

• Primary failure when Secondary present will move Hunt group processing and management
access to the Secondary. This will increase the management bandwidth from the Secondary
to the Expansion systems.
• Users whose extension or application fails over retain their existing user profiles rights
without needing or consuming an licenses on the fallback server.
• Any voicemail channel entitlements associated with the Primary, move to the Secondary on
failover; no separate license provision on the fallback server is required – unless the dual
active Voicemail Pro feature is enabled.
For further information, refer to the IP Office Resilience Overview manual.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

Unified Messaging Capacity

Voicemail Pro provides a number of integration options for Unified Messaging (UMS):

System Platform Native/ IMAP/ Exchange Integration Gmail Integration

Mode SMTP via EWS via MAPI Copy/ Alert Forward
IP Office Dell R240 750 750 490 750 250
Server HP DL360G7 1500 1500 490 1500 250
Edition
Dell R640 2000 2000 490 2000 250
OVA[1] 2000 2000 490 2000 250
IP Office Dell R640 3000 3000 490 3000 250
Select OVA[1] 3000 3000 490 3000 250
IP Office
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
2. Capacity when one-X Portal is running on the module.
3. Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers
are equivalent.
4. Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
• Use of these options requires the user or hunt group to be licensed, either using an
appropriate IP Office user profile license or the legacy UMS Web Services license.

August 2024 IP Office Platform Guidelines Capacity 76

Comments on this document?
Voicemail or Auto-Attendant or IVR

• Each voicemail server in a dual active Voicemail Pro deployment supports independent UMS
integration capacity.
• When resilience active, UMS integrations are supported at the same per-server capacity.
• The MAPI exchange integration supports 245 users per MAPI proxy service running on the
Exchange Server.
• A maximum of two MAPI proxy services can be running, giving a total of 490 mailboxes.
• Hunt Groups cannot support Gmail integration.
• The Gmail maximum message length is 14 minutes.
Related links
General Capacity Considerations on page 56

Voicemail or Auto-Attendant or IVR

August 2024 IP Office Platform Guidelines Capacity 77

Comments on this document?
General Capacity Considerations

Dual Voicemail Server Operation

When the dual Voicemail Pro feature is active (IP Office Select and IP Office Subscription
only) and not under failover conditions, users are provided voicemail services (voicemail,
announcements, call recording, auto attendant, IVR, etc) services from one of the Voicemail Pro
servers:
• All Primary users’ voicemail invocations are directed to the Primary Voicemail Pro instance.
• All Secondary users’ voicemail invocations are directed to the Secondary Voicemail Pro
instance.
• All Expansion users’ voicemail invocations are directed to the Voicemail Pro instance defined
by the System > Voicemail > Voicemail Destination setting. This is initially selected by the
Initial Configuration Utility (ICU).
Administration
To ensure Voicemail Pro channel capacity is available for voicemail, call flow and announcement
operations, the IP Office Server Edition Manager settings Voicemail Channel Reservation on the
Primary and Secondary Server’s System > Voicemail tab can be configured to reserve channels
exclusively for specific uses.
Mailbox capacity
The Voicemail Pro automatically creates a mailbox for each user and hunt group in the IP Office
configuration. The individual capacity is fixed at 60 minutes per user or group mailbox.
If voicemail channel resources run out:
• Unanswered calls continue to alert rather than going to voicemail.
• Voicemail collect fails to connect to the voicemail.
• Calls to attendants and call-flows will continue to alert. However, text-to-speech (TTS) will not
be output during call flows.
• Announcements are not played.
• Note that the TTS channel capacity is 250.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
What happens if mailbox storage resources run out?
• Voicemail leave operations will receive an announcement that the user/group’s mailbox is full.
• Voicemail collect will continue to function.
Related links
Primary and Secondary Server Capacity on page 14
IP500 V2/V2A Servers on page 35
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 78

Comments on this document?
WebRTC Gateway

WebRTC Gateway
The following WebRTC client capacity is supported with two main options aligned to the Avaya
one-X® Portal Server:
• WebRTC Gateway running on the Primary Server
• Standalone server with increased capacity (IP Office Application Server with just Avaya
one-X® Portal)

System Platform Max. Sessions Max. Clients Max. Call

Mode Primary Stand Alone Primary Stand Alone Rate (BHCC)

IP Office Dell R240 64 128 375 7200 7200

Server HP DL360G7 128 256 750 9000 9000
Edition
Dell R640 512 1024 1024 9000 9000
OVA[1] 512 1024 1024 10000 10000
IP Office Dell R640 512 1024 1024 10000 10000
Select OVA[1] 512 1024 1024 10000 10000
IP Office
Subscription

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• The quoted Busy Hour Call Completion (BHCC) rates assumes a Normal call distribution.
• The WebRTC server application must run co-resident with the Avaya one-X® Portal server.
• The maximum WebRTC sessions figures are the maximum number of WebRTC Gateway
client sessions.
• If video used, capacity is reduced by 2 for each session.
• Each WebRTC session results in a SIP session with indirect media between the WebRTC
Gateway and the user’s IP Office.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
Related links
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 79

Comments on this document?
General Capacity Considerations

WebLM Server
The WebLM server application that is co-resident on the Primary and Application Server is
primarily intended for use by IP Office components, but can be used for other Avaya license
clients such as ACCS providing the following capacities are not exceeded:

Platform Maximum License files Maximum WebLM Maximum client

clients requests
Dell R240 150 300 6000
HP DL360 300 600 12500
Dell R640 300 600 12500
OVA[1] 300 600 12500

1. Assumes virtual machine profiling as detailed in "Deploying IP Office Servers as Virtual

Machines".
• One license type from one client constitutes one client request. For example: one Expansion
System requesting 6 different license types (say Edition, SIP trunk channels, IP Endpoint,
SoftConsole, Power User, Basic User) will result in 6 client requests.
• Unless otherwise stated, Avaya-supplied HP DL120, Dell R210/R220/R230/R240 servers are
equivalent.
• Unless otherwise stated, Avaya-supplied Dell R620/R630/R640 servers are equivalent.
Related links
General Capacity Considerations on page 56

August 2024 IP Office Platform Guidelines Capacity 80

Comments on this document?
Chapter 9: Capacity Planning Beyond 3000
Users

To provide a cost effective solution of more than 3000 users or 150 sites to larger customers, two IP
Office Select systems may be linked together to support a total of 6000 users/extensions:

This construct may also be used when other per-solution capacities are exceeded, for example
Avaya one-X® Portal users, hunt groups or Voicemail/recording channels.
You can create a group by linking two separate IP Office Select systems via IP Office lines to
provide a single system view to users.

August 2024 IP Office Platform Guidelines Capacity 81

Comments on this document?
Capacity Planning Beyond 3000 Users

Each IP Office Server Edition system has its own Primary and Applications, and optional Secondary
Server and Expansion Systems; each IP Office Server Edition system needs to be managed
separately. The systems are set up through configuration to share a common dial plan and directory.

Feature IP Office Select Grouped SE Comment

Maximum Users/ 3000 6000 3000 per system
Extensions
Directory Single Directory Common directory with Can use auto
manual synchronization synchronization for
between the two systems system directory
Directory Size 10000 10000 –
Dial Plan Single dial plan Single dial plan For example, 21xxxx is on
A and 22xxxx is on B
Trunk Sharing across Yes Yes Requires additional ARS
nodes and ICR setup
Dial by name Yes Yes Requires common
directory
Hold/Transfer Yes Yes –
Internal dialing and Yes Yes –
calling user name
Direct Media Yes Yes –
Busy and Presence System Wide Limited to local SE –
Indicators
Hot Desking System Wide Limited to local SE Partial resolution with
multiple accounts
Hunt Groups Fully Networked Partially Networked Hunt groups are limited to
one SE system but can be
linked between systems
Music On Hold 4 per node, either local or 4 per node, either local or Cannot stream MOH from
from Primary from local Primary other Primary
SMDR Single stream per node Single stream per node –
Voicemail Single/Dual Single/Dual VM per SE –
®
Avaya one-X Portal Single Single one-X server per –
SE
SCN telephony features System Wide Limited to local SE –

Related links
Inter Server Edition Link on page 83
Directory on page 83
Dial plan on page 84
Outgoing Call routing on page 84
Hunt Groups on page 84
Administration on page 85

August 2024 IP Office Platform Guidelines Capacity 82

Comments on this document?
Inter Server Edition Link

Versions or Upgrades on page 85

Inter Server Edition Link

The links between the two IP Office Server Edition systems are achieved using IP Office Lines
with the following settings:
• Transport Type: WebSocket Client/Server
• Security: Medium or High
• Networking Level: None
• Allow Direct Media Path: Active
• Out Of Band DTMF: Active
One trunk should be added between each Primary and each Secondary. This allows calls from
one system to appear as though internally dialled on the other. The WebSocket Server end for all
lines should be the same IP Office Select system.
Related links
Capacity Planning Beyond 3000 Users on page 81

Directory
To enable users of one system to be visible in the directory of the other, each Primary’s directory
configuration requires a copy of the other’s:
• Export each node’s users as CSV using IP Office Server Edition Manager.
• Extract Full Name and Extension fields from each file into a single CSV directory file. See
‘Importing and Exporting Settings’ in the "Deploying Avaya IP Office Platform IP500 V2"
manual for more information on the file formats.
• Hunt groups or common system directory entries can also be added to the directory file at
this time if required.
• Import the resultant CSV directory file into the other Primary (only) using IP Office Server
Edition Manager.
• Ensure the total central directory on each SE does not exceed 10,000 entries. See
Directory on page 68.
The centralised system directory mechanism will distribute to all other nodes.
If an external LDAP directory is also used, one Primary can be configured with the LDAP source,
and the other using the first as the HTTP source.

August 2024 IP Office Platform Guidelines Capacity 83

Comments on this document?
Capacity Planning Beyond 3000 Users

For more information on directory options and capacities see 'Directory & Call Log' and
'Centralized System Directory' in "Administering Avaya IP Office Platform with Manager".
Related links
Capacity Planning Beyond 3000 Users on page 81

Dial plan
Each user and hunt group of the cluster must have a unique name and number.
Branch prefix should not be used as this will conflict with the internal routing.
Related links
Capacity Planning Beyond 3000 Users on page 81

Outgoing Call routing

The default outgoing call routing provides a fall-back ARS on every Expansion to Primary then
Secondary. When creating a cluster it is recommended that a further fall-back ARS is added
between each Primary and each Secondary.
PSTN/SIP trunks on one system can be accessed from the other using ARS and/or dial short
codes, along with additional Incoming Call Routes.
Related links
Capacity Planning Beyond 3000 Users on page 81

Hunt Groups
Each IP Office Server Edition System has separate hunt groups. It is not possible to configure
hunt groups with members of both systems. It is possible to support limited overflow between
systems by the use of an overflow group with local users that have hunt group call forwarding
enabled to a remote user. This is only supported on rotary and sequential ring types and must not
be used to link hunt groups.
Related links
Capacity Planning Beyond 3000 Users on page 81

August 2024 IP Office Platform Guidelines Capacity 84

Comments on this document?
Administration

Administration
Each IP Office Server Edition System is managed as a separate entity although both solutions can
be managed from the same workstation if required.
Related links
Capacity Planning Beyond 3000 Users on page 81

Versions or Upgrades
Both IP Office Select systems should be the same software version. Each should be upgraded
separately from their respective Primary Server.
Related links
Capacity Planning Beyond 3000 Users on page 81

August 2024 IP Office Platform Guidelines Capacity 85

Comments on this document?
Chapter 10: Additional Help and
Documentation

The following pages provide sources for additional help.

Related links
Additional Manuals and User Guides on page 86
Getting Help on page 86
Finding an Avaya Business Partner on page 87
Additional IP Office resources on page 87
Training on page 88

Additional Manuals and User Guides

The Avaya Documentation Center website contains user guides and manuals for Avaya products
including IP Office.
• For a listing of the current IP Office manuals and user guides, look at the Avaya IP Office™
Platform Manuals and User Guides document.
• The Avaya IP Office Knowledgebase and Avaya Support websites also provide access to the
IP Office technical manuals and users guides.
- Note that where possible these sites redirect users to the version of the document hosted
by the Avaya Documentation Center.
For other types of documents and other resources, visit the various Avaya websites (see
Additional IP Office resources on page 87).
Related links
Additional Help and Documentation on page 86

Getting Help
Avaya sells IP Office through accredited business partners. Those business partners provide
direct support to their customers and can escalate issues to Avaya when necessary.

August 2024 IP Office Platform Guidelines Capacity 86

Comments on this document?
Finding an Avaya Business Partner

Finding an Avaya Business Partner

If your IP Office system currently does not have an Avaya business partner providing support and
maintenance for it, you can use the Avaya Partner Locator tool to find a business partner.
Procedure
1. Using a browser, go to the Avaya Website at https://www.avaya.com
2. Select Partners and then Find a Partner.
3. Enter your location information.
4. For IP Office business partners, using the Filter, select Small/Medium Business.
Related links
Additional Help and Documentation on page 86

Additional IP Office resources

In addition to the documentation website (see Additional Manuals and User Guides on page 86),
there are a range of website that provide information about Avaya products and services including
IP Office.
• Avaya Website (https://www.avaya.com)
This is the official Avaya website. The front page also provides access to individual Avaya
websites for different regions and countries.
• Avaya Sales & Partner Portal (https://sales.avaya.com)
This is the official website for all Avaya business partners. The site requires registration for
a user name and password. Once accessed, you can customize the portal to show specific
products and information type that you want to see.
• Avaya IP Office Knowledgebase (https://ipofficekb.avaya.com)
This site provides access to an online, regularly updated version of IP Office user guides and
technical manual.
• Avaya Support (https://support.avaya.com)

August 2024 IP Office Platform Guidelines Capacity 87

Comments on this document?
Additional Help and Documentation

This site provide access to Avaya product software, documentation and other services for
Avaya product installers and maintainers.
- Avaya Support Forums (https://support.avaya.com/forums/index.php)
This site provides forums for discussing product issues.
• International Avaya User Group (https://www.iuag.org)
This is the organization for Avaya customers. It provides discussion groups and forums.
• Avaya DevConnect (https://www.devconnectprogram.com/)
This site provides details on APIs and SDKs for Avaya products, including IP Office. The site
also provides application notes for third-party non-Avaya products that interoperate with IP
Office using those APIs and SDKs.
• Avaya Learning (https://www.avaya-learning.com/)
This site provides access to training courses and accreditation programs for Avaya products.
Related links
Additional Help and Documentation on page 86

Training
Avaya training and credentials ensure our Business Partners have the capabilities and skills to
successfully sell, implement, and support Avaya solutions and exceed customer expectations. The
following credentials are available:
• Avaya Certified Sales Specialist (APSS)
• Avaya Implementation Professional Specialist (AIPS)
• Avaya Certified Support Specialist (ACSS)
Credential maps are available on the Avaya Learning website.
Related links
Additional Help and Documentation on page 86

August 2024 IP Office Platform Guidelines Capacity 88

Comments on this document?
Index
A D
account codes ......................................................................57 DECT ................................................................................... 67
administration ...................................................................... 85 definitions .............................................................................10
Administrator ........................................................................86 dial
APIs ..................................................................................... 87 plan ...............................................................................84
applicability ............................................................................ 8 directory ......................................................................... 68, 83
Application Notes .................................................................87 disclaimer ...............................................................................7
audio conferencing .................................................. 14, 35, 57
auto-attendant ..........................................................31, 53, 77
avaya
E
contact center applications ........................................... 12 edition
link ................................................................................ 83
B expansion
server ............................................................................55
bandwidth ................................................................ 26, 45, 70 extensions ......................................................................23, 44
Base Stations .......................................................................67
beyond
users .............................................................................81
F
business partner locator ...................................................... 87 forums ..................................................................................87
button
appearance buttons ......................................................60
modules ........................................................................ 59 H
Help ..................................................................................... 86
C hunt
group ............................................................................ 84
call hunt group ................................................................25, 44, 68
history ........................................................................... 61
logs ............................................................................... 61
media path ....................................................................19 I
routing ...........................................................................84
incoming
traffic profile ...................................................... 21, 42, 65
call routes ..................................................................... 69
call capacity ......................................................................... 16
information
call destination ......................................................... 18, 39, 60
classifications ................................................................. 8
call media path .....................................................................39
intended audience ................................................................. 7
call recording ........................................................... 19, 40, 62
inter
capacity
server ............................................................................83
messaging .................................................................... 76
IP infrastructure ....................................................... 26, 45, 70
planning .................................................................. 13, 81
IP office SoftConsole ........................................................... 72
Capacity ...............................................................................64
IP500 V2/V2A servers ......................................................... 35
Changes .............................................................................. 10
IVR ...........................................................................31, 53, 77
channel
VCM ..............................................................................51
concurrent L
call capacity .................................................................. 37
contacts ............................................................................... 68 linux
courses ................................................................................ 87 expansion ..................................................................... 55
CTI Linux-based network ............................................................10
TAPI .............................................................................. 66
M
mailbox .................................................................... 31, 53, 77

August 2024 IP Office Platform Guidelines Capacity 89

Comments on this document?
Manuals ............................................................................... 86 trunk capacity .......................................................................29
maximum
trunk capacity ............................................................... 49
multi-site network
U
link capacities ................................................... 28, 48, 73 unified
capacity ........................................................................ 76
N user directory ....................................................................... 68
User Guides .........................................................................86
NDA requirements ................................................................. 8 users .............................................................................. 23, 44

O V
one-X portal VCM
server ............................................................................33 channel ......................................................................... 51
outgoing versions
call ................................................................................ 84 upgrades .......................................................................85
overview .................................................................................9 virtualized
deployments ................................................................. 10
voicemail ..................................................................31, 53, 77
P VoIP QoS ................................................................. 26, 45, 70
paging .................................................................................. 74
personal directory ................................................................ 68 W
presence group ........................................................25, 44, 68
Primary ................................................................................ 14 WebLM
purpose ..................................................................................7 server ............................................................................80
WebRTC
gateway ........................................................................ 79
Q websites ...............................................................................87
Quick Reference Guides ......................................................86

R
Recording size ..................................................................... 64
Remote Support Services ....................................................75
Reseller ................................................................................86
resilience
failover .............................................................. 29, 48, 75
RSS ..................................................................................... 75

S
sales .................................................................................... 87
SCN ..................................................................................... 49
SDKs ....................................................................................87
Secondary ............................................................................14
Small Community Network .................................................. 49
subscription ..........................................................................12
support .................................................................................87
System Administrator ...........................................................86
system directory ...................................................................68

T
Technical Bulletins ............................................................... 87
training ........................................................................... 87, 88

August 2024 IP Office Platform Guidelines Capacity 90

Comments on this document?

Avaya IP Office Platform Manuals and User Guides - En-Us
No ratings yet
Avaya IP Office Platform Manuals and User Guides - En-Us
24 pages
IP Office Platform Security Guidelines - Trust Certificate Renewal Instructions
No ratings yet
IP Office Platform Security Guidelines - Trust Certificate Renewal Instructions
197 pages
IP Office J100 Series Phone User Guide - En-Us
No ratings yet
IP Office J100 Series Phone User Guide - En-Us
207 pages
Administering Avaya IP Office With Manager - En-Us
No ratings yet
Administering Avaya IP Office With Manager - En-Us
1,256 pages
IP Office SIP Telephone Installation Notes - En-Us
No ratings yet
IP Office SIP Telephone Installation Notes - En-Us
211 pages
Deploying Avaya IP Office Server Edition Solution - En-Us
No ratings yet
Deploying Avaya IP Office Server Edition Solution - En-Us
197 pages
DeployingAvayaCMS R21.0 November 2024 En-Us
No ratings yet
DeployingAvayaCMS R21.0 November 2024 En-Us
110 pages
IP Office DECT R4 Installation Guide - En-Us
No ratings yet
IP Office DECT R4 Installation Guide - En-Us
276 pages
Deploying Avaya IP Office Servers As Virtual Machines - En-Us
No ratings yet
Deploying Avaya IP Office Servers As Virtual Machines - En-Us
136 pages
R7.1.2.2 UsingAACCReportsandDisplays
No ratings yet
R7.1.2.2 UsingAACCReportsandDisplays
158 pages
R21 AvayaCMSDatabaseItemsandCalculations
No ratings yet
R21 AvayaCMSDatabaseItemsandCalculations
360 pages
Using Avaya Vantage R3 2 October2024
No ratings yet
Using Avaya Vantage R3 2 October2024
186 pages
Avaya CMS Call History Interface R21.0 June 2014
No ratings yet
Avaya CMS Call History Interface R21.0 June 2014
96 pages
Installing Administering Avaya VantageinAura IPO R3 2 October2024
No ratings yet
Installing Administering Avaya VantageinAura IPO R3 2 October2024
405 pages
Avaya Aura Documentation Catalog 10 2 X Dec2023
No ratings yet
Avaya Aura Documentation Catalog 10 2 X Dec2023
20 pages
Deploying Avaya Aura Communication Manager inSoftware-Only and Infrastructure As A Service Environments R 10 2 May 2024
No ratings yet
Deploying Avaya Aura Communication Manager inSoftware-Only and Infrastructure As A Service Environments R 10 2 May 2024
125 pages
Ip - Office - Security - Guidelines - 2025 03 07 14 16 56
No ratings yet
Ip - Office - Security - Guidelines - 2025 03 07 14 16 56
205 pages
AdministeringAvayaAuraCommunicationManagerR10 2 X
No ratings yet
AdministeringAvayaAuraCommunicationManagerR10 2 X
496 pages
Avaya Aura Core Solution Description R10 2 X May 2024
No ratings yet
Avaya Aura Core Solution Description R10 2 X May 2024
183 pages
Avaya Communication Manager Alarms Events and Logs Reference R10.2.x Dec2023
No ratings yet
Avaya Communication Manager Alarms Events and Logs Reference R10.2.x Dec2023
801 pages
Avaya Communication Manager Administering Network Connectivity R10.2.x Dec2023
No ratings yet
Avaya Communication Manager Administering Network Connectivity R10.2.x Dec2023
136 pages
Avaya SBC Deploying On A Hardware Platform
No ratings yet
Avaya SBC Deploying On A Hardware Platform
94 pages
Avaya SBC Deploying On A Hardware Platform
No ratings yet
Avaya SBC Deploying On A Hardware Platform
95 pages
Deploying AvayaSBC GoogleCloudPlatform
No ratings yet
Deploying AvayaSBC GoogleCloudPlatform
46 pages
Avaya SBC Overview and Specification
No ratings yet
Avaya SBC Overview and Specification
124 pages
Avaya SBC Overview and Specification
No ratings yet
Avaya SBC Overview and Specification
112 pages
Avaya SBC Upgrading
No ratings yet
Avaya SBC Upgrading
52 pages
Administering Avaya Call Management System 2025-01-30-16-35-03
No ratings yet
Administering Avaya Call Management System 2025-01-30-16-35-03
610 pages
Administering A Vayas BC
No ratings yet
Administering A Vayas BC
706 pages
Avaya SBC Maintaining and Troubleshooting
No ratings yet
Avaya SBC Maintaining and Troubleshooting
159 pages
Avaya SBC Deploying On Microsoft Azure
No ratings yet
Avaya SBC Deploying On Microsoft Azure
47 pages
Avaya SBC Deploying On An AWS Platform
No ratings yet
Avaya SBC Deploying On An AWS Platform
57 pages
Avaya IX WEM 2024R1 SQL Server Installation and Upgrade
No ratings yet
Avaya IX WEM 2024R1 SQL Server Installation and Upgrade
157 pages
Avaya IX WEM V15 2 Enterprise Manager Configuration and Administration Guide
No ratings yet
Avaya IX WEM V15 2 Enterprise Manager Configuration and Administration Guide
520 pages
Administering Avaya Call Management System 2025-09!04!04!32!53
No ratings yet
Administering Avaya Call Management System 2025-09!04!04!32!53
600 pages
Avaya Sip - Extensions - en PDF
No ratings yet
Avaya Sip - Extensions - en PDF
92 pages
AvayaIPOffice PlatformSolutionDescription
No ratings yet
AvayaIPOffice PlatformSolutionDescription
151 pages
Avaya IX WEM 2024R1 Installation Guide
No ratings yet
Avaya IX WEM 2024R1 Installation Guide
105 pages
SIP Installation Notes
No ratings yet
SIP Installation Notes
146 pages
Avaya IX WEM V15 2 Authentication Configuration
No ratings yet
Avaya IX WEM V15 2 Authentication Configuration
150 pages
Avaya IX WEM V15 2 System Monitoring Messaging and Alarms Guide
No ratings yet
Avaya IX WEM V15 2 System Monitoring Messaging and Alarms Guide
221 pages
Avaya IP Office Platform Short Code and Button Action Reference - en
No ratings yet
Avaya IP Office Platform Short Code and Button Action Reference - en
233 pages
ACR To ACRA Migration: Reference Guide
No ratings yet
ACR To ACRA Migration: Reference Guide
20 pages
Avaya IX WEM V15 2 Technical Overview
No ratings yet
Avaya IX WEM V15 2 Technical Overview
284 pages
Avaya Phone System Manual 2410
No ratings yet
Avaya Phone System Manual 2410
66 pages
Avaya IX WEM V15 2 Framework Administration
No ratings yet
Avaya IX WEM V15 2 Framework Administration
79 pages
Using Avaya H175 Video Collaboration Station: Release 1.0.2 April 2016
No ratings yet
Using Avaya H175 Video Collaboration Station: Release 1.0.2 April 2016
176 pages
Getting Started With Avaya Aura Orchestration Designer
No ratings yet
Getting Started With Avaya Aura Orchestration Designer
51 pages
Administering Avaya H100 Series Video Collaboration Stations
No ratings yet
Administering Avaya H100 Series Video Collaboration Stations
81 pages
Analog Phone User PDF
No ratings yet
Analog Phone User PDF
18 pages
Avaya Interaction Center Service Pack Release Notes R7.3.11
No ratings yet
Avaya Interaction Center Service Pack Release Notes R7.3.11
190 pages
Administering Avaya IPOffice With Manager
No ratings yet
Administering Avaya IPOffice With Manager
1,091 pages
AVAYA Voicemail Pro - Sample Exercises
No ratings yet
AVAYA Voicemail Pro - Sample Exercises
74 pages
Using Avaya J139 IP Phone in An Avaya Cloud Office - Issue2
No ratings yet
Using Avaya J139 IP Phone in An Avaya Cloud Office - Issue2
74 pages
Migrating and Installing Avaya Appliance Virtualization Platform
No ratings yet
Migrating and Installing Avaya Appliance Virtualization Platform
68 pages
Using Collaboration Agent
No ratings yet
Using Collaboration Agent
94 pages
Avaya IP Office Locale Settings - En-Us
No ratings yet
Avaya IP Office Locale Settings - En-Us
147 pages
Ipocc Archiving en
No ratings yet
Ipocc Archiving en
28 pages
Administering Avaya Dynamic Self Service Application 2 9 3 2
No ratings yet
Administering Avaya Dynamic Self Service Application 2 9 3 2
123 pages
1st Draft Ict Diploma November 2024 Exam Timetable
No ratings yet
1st Draft Ict Diploma November 2024 Exam Timetable
5 pages
Akshay Patra q1
No ratings yet
Akshay Patra q1
1 page
House Price Indices in India - 2015
No ratings yet
House Price Indices in India - 2015
48 pages
Computer System Components Guide
No ratings yet
Computer System Components Guide
38 pages
Urs Ftir
No ratings yet
Urs Ftir
5 pages
Survey Soap New
No ratings yet
Survey Soap New
2 pages
Food Export Booklet
No ratings yet
Food Export Booklet
44 pages
NCC-UNEP MoU on Plastic Pollution
No ratings yet
NCC-UNEP MoU on Plastic Pollution
16 pages
Week 01: Application Activity: Team Governance Plan: Name: Course/Year/Blk
No ratings yet
Week 01: Application Activity: Team Governance Plan: Name: Course/Year/Blk
2 pages
TxDOT Fabric Underseal Guide
No ratings yet
TxDOT Fabric Underseal Guide
4 pages
Chapter 2: - Money Market
No ratings yet
Chapter 2: - Money Market
12 pages
Biomedical Devices Catalogue
No ratings yet
Biomedical Devices Catalogue
30 pages
Shell Refrigeration Oil S4 FR-F 100 TDS
No ratings yet
Shell Refrigeration Oil S4 FR-F 100 TDS
2 pages
Literature Review Key Phrases
100% (2)
Literature Review Key Phrases
5 pages
CV Including All Certificates New
No ratings yet
CV Including All Certificates New
18 pages
FBS - 1st Periodical Exam
No ratings yet
FBS - 1st Periodical Exam
6 pages
Presentation By: Shankar.H.S Project Officer, HRMS Centre For E-Governance Phone: 080-22032547 Mobile:9844478794 E-Mail: Po-Hrms@karnataka - Gov.in
No ratings yet
Presentation By: Shankar.H.S Project Officer, HRMS Centre For E-Governance Phone: 080-22032547 Mobile:9844478794 E-Mail: Po-Hrms@karnataka - Gov.in
27 pages
Thomas Alexander Bateman Resume 2017
No ratings yet
Thomas Alexander Bateman Resume 2017
2 pages
Accounting Project for Students
100% (3)
Accounting Project for Students
4 pages
GST Invoice
No ratings yet
GST Invoice
13 pages
13 - NIBL - G.R. No National Marketing V NAMARCO - Digest
No ratings yet
13 - NIBL - G.R. No National Marketing V NAMARCO - Digest
3 pages
Media Production & Coordination Expert
No ratings yet
Media Production & Coordination Expert
1 page
Dr. Beckmann Starch SDS 2014
No ratings yet
Dr. Beckmann Starch SDS 2014
7 pages
Enna - 5S Office Facilitator Guide-Productivity Press
No ratings yet
Enna - 5S Office Facilitator Guide-Productivity Press
80 pages
Fraud Methods and Resources
No ratings yet
Fraud Methods and Resources
4 pages
Platform SAMPLE Project Plan - 7
No ratings yet
Platform SAMPLE Project Plan - 7
10 pages
Geotube Cone Test Prueba de Cono Del Geotube
No ratings yet
Geotube Cone Test Prueba de Cono Del Geotube
12 pages
Automation of Drawbridge Model Using by PLC: Iarjset
No ratings yet
Automation of Drawbridge Model Using by PLC: Iarjset
8 pages
08.02 CCC Chart and Reflection: Event Name Type of Event Causes Course Consequences
No ratings yet
08.02 CCC Chart and Reflection: Event Name Type of Event Causes Course Consequences
4 pages
Dorian Tool Guide No 4
No ratings yet
Dorian Tool Guide No 4
72 pages