IP recording
Support for IP Recording includes Gateway and Extension-Side recording, DMS, Real-time Transport Protocol (RTP) Detection, and SIP Trunk Recording.
Gateway recording in IP environments can be compared to trunk-side recording in TDM environments. Configure gateway recording by SPANning the gateway and the call control server. In Cisco environments, the call control server is Call Manager. To record conference calls, any conference bridge resources/participants must be SPANned. At the same time, care must be taken to ensure that SPANning the conference bridge resources does not take the IP Recorder over the maximum number of concurrent channels for which it is configured. A possible limitation of this configuration is that it can be difficult to record employee to employee calls, since these calls do not usually go over the gateway.
Spanning the gateway enables the Recorder to see the RTP traffic between the IP device and the gateway. When a conference is established, the RTP traffic flows between the gateway and the conference bridge, meaning that the IP Recorder cannot associate it with any device. The conference bridge must be SPANned, therefore, to enable the IP Recorder to access and record the RTP streams going to and from IP devices.
Extension-Side IP Recording
Extension-side recording in IP environments is comparable to station-side recording in TDM environments. Configure extension-side recording by SPANning (that is, copying) the traffic to and from an IP phone, typically using either port or VLAN SPANning.
SPANning the IP device itself means that the IP Recorder receives all RTP traffic to and from that device, and traffic between the device and the Cisco Call Manager Server/Cluster. In this configuration, it is not necessary to explicitly SPAN the Call Manager or any of the conference bridge resources.
Unified Trading Recording
Unified Trading Recording is supported. See the appropriate Integration Guide for more information.
In IP Recording, you can use RTP detection Function of the IAFD product that compares a caller’s voice to one or more voiceprints in a watch list to detect if a target is participating in a call. to record calls in Recorder Controlled or CTI Controlled spanning environments (either all the time or in fallback mode).
RTP detection is always enabled in Performance mode (which prevents loss of audio due to CTI disconnection) and Liability modes (in which audio records either by CTI or VOX and as VOX in between CTI calls).
RTP detection is not supported when the RTP payload type is in the dynamic payload range of 96–127 (such as video) and for any encrypted media streams (such as Lync). Therefore, RTP detection is not supported for video recording and Lync recording.