Hello,

I am curious if there is a limit on the amount of devices we can monitor on one socket when connecting to the DMCC .NET SDK. We are trying to determine how many devices a single application instance can monitor?

We are monitoring the devices, not registering them. When we are monitoring these VDNs and skills, we are not seeing all events from AES. If we limit it to a smaller amount of devices we do see all events. So we are trying to determine what the limit is per application instance.

Thanks!
Dan

I'm guessing you are referring to a call control monitor. Further I am gussing you are interested in the number of station monitors and not monitors on other types of devices. The DMCC call control monitor is the only monitor type (within DMCC) that will provide events without the application registering the device. Assuming that these assumptions are correct, then AES DMCC can support the same number of call control monitors that a TSAPI application can monitor through a single socket (the number of sockets does not influence the maxim).

The AES capacities are described in the Overview document and in the Communication Manager Capacities document. The information varies by release of the AES so starting with the right document is important. Here is a link to the 7.1.3 (most recent as I write this)
https://www.devconnectprogram.com/fileMedia/download/f12f6314-3d0e-4518-8d26-8fec5d0dd484

This limit was recently increased per this statement"
"Active Controlling Associations capacity increased from 32K to 50K
Active Controlling Associations are used to monitor stations only. The system wide capacity has
been increased from 32000 associations to 50000 associations. Previously, the capacity was
32000 associations for large Communication Manager platforms, 32000 associations for medium
Communication Manager platforms, and 2000 associations for small Communication Manager
platforms."


Some of the important variables related to achieving this capacity limit is dependent on the release, the AES server, the CM config (small, medium, large) other traffic on the AES server (e.g. SMS or other DMCC applications), how the AEP/CTI link is provisioned (# of CLANs or processor ethernet), the network throughput 10M versus 10G, and on how your application is implemented (# of threads) and the server your application is running on.

John,

We are monitoring VDNs and Stations. The information you provided is mainly for the AES capacity. However, what we are trying to know is that we have an application utilizing Avaya DMCC .NET SDK. What is the maximum number of VDNs and Stations a single connection to AES an application using DMCC SDK can monitor?

After a couple of layers of digging, in AE Services release 7.1, the answer is 80,000 monitors (could be a mix of station and VDN or all of one or the other). This limit comes from the DMCC portion of the code. The AE Services server would need connected to at least 3 separate Communication Manager's to achieve that limit as there is a 32,000 monitor maxima on a CTI link.