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
Mode |
Platform |
Maximum CTI sessions |
Maximum CTI users per session |
Total CTI controlled users |
Maximum BHCC |
IP Office Server Edition |
Dell R260 |
5 |
750 |
3750 |
9000 |
Dell R660 |
5 |
2000 |
10000 |
9000 |
Virtual[1] |
5 |
2000 |
15000 |
10000 |
IP Office Select IP Office Subscription (Linux) |
Dell R660 |
5 |
3000 |
15000 |
10000 |
Virtual[1] |
5 |
3000 |
15000 |
10000 |
All |
IP500 V2 |
3 |
384 |
1152 |
7200 |
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.
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 third-party TAPI session counts as one CTI session for that IP Office.
All first-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.
Unless otherwise stated, R240 and R260 servers capacities are equivalent.
