The Verba recording solution supports Avaya DMCC multiple registration based call recording.
Using Avaya Communication Manager release 5.0 or higher, it is possible to register up to three devices against an extension; using earlier releases, only one device can be registered.
The multiple registrations call recording method, which Verba Recording System uses takes advantage of the multiple registrations capability to register a recording device against the actual extension from which calls are to be recorded. The application simply requests listening services and CM sends a duplicated stream of all traffic from the originally provisioned extension. The forked RTP comes to the recording server from the media resource (formerly MedPro) card. The duplication request takes up a media resource, but does not require conferencing resources or timeslots compared to other recording methods.
For further information, please refer to an official Avaya representative or read the guide below:
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/other.gsp, drill down to What licenses are required for DMCC based Call Recording solution?
The following table summarizes the available recording approaches in Avaya Communication Manager environment and the available Verba support:
|Recording approach||Verba support|
|Passive TDM trunk side recording||No|
|Passive IP trunk side recording||Yes, SIP only|
|Passive IP extension side recording||Yes, SIP only|
|AES: service observing||No|
|AES: multiple registration (RTP forking)||Yes|
The well known passive IP call recording is not officially accepted by Avaya, because the signaling protocol used for Avaya devices is based on a proprietary version of H.323. The new SIP based devices can be monitored passively, but certain PBX functionality is still missing from the SIP based firmwares, so they are very rarely used. The only officially supported recording method is CTI-based recording, which means that the recording solutions must work through the Avaya AES server. On the AES server, there are different APIs:
There are 3 different call recording approaches using the AES:
This method works by operating softphones and monitoring the recorded stations and invoking service observing upon recording request or automatically for each call. This way the softphones can participate in the calls, thus receive the audio. The application uses the AE Services DMCC service to register itself as a standalone recording device. The Service Observing feature is provisioned and activated on the device so that, when the target extension joins a call, the recording device is automatically added to the call. The application receives the calls aggregated RTP media stream via the recording device and records the call.
This method works by operating softphones and monitoring the recorded stations and invoking single-step-conference upon recording request or automatically for each call. In this way the softphones can participate in the calls thus receive the audio. The application uses the AE Services DMCC service to register a pool of standalone recording devices. The application uses the AE Services TSAPI service to monitor the target extension for Established Call events. Whenever the extension joins a call, an Established Call event occurs which triggers the application to use the Single conferencing method to add a recording device to the call. The application receives the calls aggregated RTP media stream via the recording device and records the call.
Using Communication Manager release 5.0 or higher, it is possible to register up to three devices against an extension; using earlier releases, only one device can be registered. Where multiple device registration is supported, the number of DMCC devices that can be registered against an extension is determined as follows: