Author Message
AbdulKA
Joined: Nov 6, 2013
Messages: 35
Offline
Hi,
we are planning to deploy our voice logging solution for a call centre having 300 extensions. we are running our TSAPI and DMCC applications in a system which can handle audio streams of up to 100 extensions. In the mentioned case we need to provide 3 systems with recording of 100 extensions in each server. Recording is done in SSC mode using TSAPI and media recorded using DMCC. Following are my queries. we will be using AES 4.2 and CM 5.1

1. If we open connections from 3 different systems to the AES for TSAPI and DMCC each. will we face some license restrictions?

2. Is there any limit on the number of monitors on extension devices from TSAPI and DMCC ? we have tried only up to 25 monitors for both.

Thanks and Regards
Abdul Rasheed
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Hi Abdul,

Licenses on a single AES can easily be shared by multiple TSAPI sessions. Each session would consume a number of licenses equal to the number of monitored devices. One interesting note here is if you for some reason had multiple stations monitoring the same station, only one license is consumed per station.

The same is true of DMCC. The one thing to be aware of with respect to DMCC is that if you want to be able to monitor the same device from different sessions you will want to ensure that you set the "controllableByOtherSessions" to true.

With respect to the number of Monitored stations per AES, the only limit is the rate of ASAI messages exchanged between AES and CM, which cannot exceed 720 messages per second. You would need a very large number of monitors to exceed this limit, and 100 is well within that range. Please see our overview document for these capacities and others that may be of interest (such as DMCC registered station capacity).

One other question: are you planning to use server media mode or client media mode for your DMCC recordings? We suggest client media mode for a variety of reasons, not least of which is that a MUCH higher number of registrations is supported per AES (4,000 versus 120).

Joel
AbdulKA
Joined: Nov 6, 2013
Messages: 35
Offline
Hi Joel,
Thanks a lot for all these details. Appreciate your quick reply and great support.

Regards
Rasheed
AbdulKA
Joined: Nov 6, 2013
Messages: 35
Offline
Hi Joel,
Sorry that i forget to update you one point. Yes we are using Client Media mode for DMCC recording. I have one more small query. we are using SSC for recording , is there any specific advantage for service observe as compared to SSC?

Regards
Rasheed
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
The only real advantage for service observing is that your app doesn't have to take any action to involve the DMCC recording station in each call: that's done automatically. The disadvantage is that there are only 2 observers (CM 4.0 and later) allowed per call at any given time.

Joel
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
There are a list of pro's and cons of the different call recording approaches described in
https://devconnect.avaya.com/public/flink.do?f=/public/download/AES/WhitePapers/AEServicesCallRecording_SVC4050.pdf
AbdulKA
Joined: Nov 6, 2013
Messages: 35
Offline
Thanks a lot John and Joel

Regards
Rasheed
Go to:   
Mobile view