Single Step Conference
Call Recording monitors phone activity. The Avaya Application Enablement Services server (AES server) informs Call Recording of any calls in progress and requests that the recorder's virtual device is added to a single step conference allowing the recorder to receive the RTP stream.

When a call occurs to a monitored extension (terminal). The AES Server notifies the Call Recording server about the call with a JTAPI Established Call event.

The Call Recording server requests that its virtual phone (recorder) is added to the conversation.

The CM server establishes a single step conference including the caller, the called number, and the virtual phone recorder.
The recording ends when instructed to do so by Call Recording, or ends automatically when the entire call ends.
Registering a Pool of Recorders
Call Recording uses the Application Enablement Services (AES) and Device Media and Call Control (DMCC) Services, to register a pool of standalone recording devices (a recorder group) in Client media mode with the dependency mode Main. The Client media mode means that Call Recording handles the media streams from the DMCC device. The Main dependency mode means that the recorder can receive calls and listen.
During registration, Call Recording sets the following:
- The RTP IP address
- The port number
- The codec
- The encryption settings
These settings are used to send the media stream to the recorder.
Detecting Terminal Activity
Call Recording uses the AES server DMCC service to add a call control listener to monitor the target extension for Established Call events. Whenever the extension joins a call, an Established Call event occurs, which triggers Call Recording to use the Single Step Conferencing method to add a recorder to the call as a virtual phone. Call Recording receives the call’s aggregated RTP media stream via the Media Gateway and records the call.