Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
Forum Index » DMCC APIs » Maximum number of DMCC connections   XML
Author Message

Joined: 12/11/2013 02:49:12
Messages: 12


We need to know how many DMCC client applications (e.g. call recorders) can be connected to a single AES Server in parallel.
In documentation, we've found a value for max. TSAPI service capacity, which is 2500 TLinks.
Is this the restriction that is also relevant for DMCC clients?

Claus Suffel

Joined: 30/11/2009 05:00:18
Messages: 1751

Hi Claus,

Limitations on how many DMCC terminals can be registered per AE Service are discussed in the "Communication Manager capacities for DMCC" section of the AE Services Overview document.

So, for example, with AE Services Profile 3 connected to a large Communication Manager using procr and no encryption, each AE Service can register up to 8000 terminals.

There is no limit on how these registrations are distributed amongst DMCC clients. For example, a single DMCC application can register all these terminals using a single connection. Alternatively, 8000 different clients can each register a single terminal.


Joined: 20/06/2005 14:06:52
Messages: 815
Location: Thornton, CO

adding to what Martin said, relative to the TSAPI 2500 limit, since DMCC uses a single connection from DMCC to TSAPI process within AE Services, that limit only impacts TSAPI/JTAPI and not the DMCC applications (thus all 8000 application instances could create a DMCC Call Control monitor if necessary) although it does use one out of the 2500 I suspect.
Go to: