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)
Mode |
Platform |
Maximum one-X Portal Clients |
Maximum Solution Call Rate (BHCC) |
Primary |
Stand Alone |
IP Office Server Edition |
Dell R260 |
375 |
750 |
7200 |
Dell R660 |
750 |
750 |
9000 |
Virtual[1] |
750 |
750 |
9000 |
IP Office Select IP Office Subscription (Linux) |
Dell R660 |
1500 |
3000 |
10000 |
Virtual[1] |
1500 |
3000 |
10000 |
IP500 V2 |
UCM V2 |
- |
50 |
3600 |
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.
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 7200/9000/10000 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.
