![]() |
The number of simultaneous active calls that Device, Media, and Call Control (DMCC) applications can expect to handle depends on many factors.
If either Client or Server Media mode is used, the following should be taken into consideration:
Your application’s demand for VoIP resources relative to the VoIP resources available on Communication Manager
The codec used and packet size chosen for media
Media encryption
Whether encryption is used for the application link or the signaling link
Compare the DMCC capacities listed in Table 1 and Table 2 with the Communication Manager resources and capacities described in capacities for DMCC to make sure that you have adequate Communication Manager resources for a given DMCC implementation.
Session and H323 Signaling Encryption Profile | AE Server Capacity | Traffic Rate for Applications | ||||
---|---|---|---|---|---|---|
None |
8,000 endpoints and a 36,000 BHCC on the following Avaya Common
Servers:
|
AE Services and Communication Manager can support up to 20 outstanding registration requests
by an application at any time
If multiple CLANs are used, the client must distribute 20 outstanding registration requests evenly among allocated CLANs. If signaling encryption is used, the number of outstanding registration requests must not exceed 10. |
||||
PIN-EKE |
3,200 endpoints and a 28,800 BHCC on the following Avaya Common
Servers
|
AE Services and Communication Manager can support up to 20 maximum registration requests by
an application in a 10-second interval. Based on a recommendation
of 5 registrations per CLAN, this can be reached by having 4 CLANs,
which are able to process 5 encrypted registrations each. Note that
the same limit of 20 registrations in a 10-second limit applies for
Processor Ethernet also.
Developers need to consider this limit when designing applications (that is, a gap of 10 seconds is required between each set of 20 registrations if 4 CLANs are being utilized; a gap of 10 seconds is required between each set of 15 registrations if 3 CLANs are being utilized; a gap of 10 seconds is required between each set of 20 registrations if 10 CLANs are being utilitzed with 4 registrations per CLAN; and so forth). |
||||
H323TLS |
2,000 endpoints and a 18,000 BHCC on the following Avaya Common
Servers
For more information see, Additional AE Services Restrictions. |
AE Services and Communication Manager can support up to 20 registration,
when sent by an application, in a 10-second interval. Avaya recommends
5 registrations per CLAN. 4 CLANs can fulfill the capacity for 20
registrations.
|
Code Type | AE Server Capacity | Traffic Rate for Applications | |
---|---|---|---|
No signaling and media encryption | G729 | 120 endpoints |
AE Services and Communication Manager can support up to 100 maximum simultaneous registration
requests by an application in a 10-second interval. Based on a recommendation
of 20 registrations per CLAN, this can be reached by having 10 CLANs,
which are able to process 20 unencrypted registrations each per 10-second
interval. Note that the same limit of 100 registrations in a 10-second
interval applies for Processor Ethernet also.
Developers need to consider this limit when designing applications (that is, a gap of 10 seconds is required between each set of 100 registrations if 10 CLANs are being utilized; a gap of 10 seconds is required between each set of 80 registrations if 4 CLANs are being utilized; and so forth). |
G711 | 75 endpoints |
AE Services and Communication Manager can support up to 75 maximum simultaneous registration
requests by an application in a 10-second interval. Based on a recommendation
of 20 registrations per CLAN, this can be reached by having 4 CLANs,
which are able to process 20 unencrypted registrations each per 10-second
interval. Note that the same limit of 75 registrations in a 10-second
interval applies for Processor Ethernet also.
Developers need to consider this limit when designing applications (that is, a gap of 10 seconds is required between each set of 75 registrations if 4 CLANs are being utilized; a gap of 10 seconds is required between each set of 60 registrations if 3 CLANs are being utilized; and so forth). |
|
Signaling and media encryption | G729 | 96 endpoints |
AE Services and Communication Manager can support up to 96 maximum registration requests by
an application in a 10-second interval. Based on a recommendation
of 5 registrations per CLAN, this can be reached by having 20 CLANs,
which are able to process 5 encrypted registrations each. Note that
the same limit of 96 registrations in a 10-second limit applies for
Processor Ethernet also.
Developers need to consider this limit when designing applications (that is, a gap of 10 seconds is required between each set of 20 registrations if 4 CLANs are being utilized; a gap of 10 seconds is required between each set of 15 registrations if 3 CLANs are being utilized; a gap of 10 seconds is required between each set of 20 registrations if 10 CLANs are being utilitzed with 4 registrations per CLAN; and so forth). |
G711 | 60 endpoints |
AE Services and Communication Manager can support up to 60 maximum registration requests by
an application in a 10-second interval. Based on a recommendation
of 5 registrations per CLAN, this can be reached by having 12 CLANs,
which are able to process 5 encrypted registrations each. Note that
the same limit of 60 registrations in a 10-second limit applies for
Processor Ethernet also.
Developers need to consider this limit when designing applications (that is, a gap of 10 seconds is required between each set of 20 registrations if 4 CLANs are being utilized; a gap of 10 seconds is required between each set of 15 registrations if 3 CLANs are being utilized; a gap of 10 seconds is required between each set of 20 registrations if 10 CLANs are being utilitzed with 4 registrations per CLAN; and so forth). |
![]() | Note |
Traffic rate for applications is a gap of 10 seconds between each set of 100 registrations. |