Caveats

TLS encrypted/secured SIP communication between the border device and QMS.

SRTP secured audio streams for call medias.

RTCP feedback from the recorder on live audio streams.

Recording multimedia calls with a video component.

The Cisco Unified Border Element Configuration Guide documents Call scenarios/configurations as not being supported.

The Mediant Soft SBC User’s manual documents Call scenarios/configurations as not being supported. The Mediant SBC has a very minimalistic conversation with the QMS recorder, which creates some deficiencies in normal QMS functionality. Specifically, if a recorded user has more than one active call at the same time the call state in the QMS client Realtime view may be incorrect. QMS will display the most recently started call as being the active call, even though the user may be switching among their active calls. Similarly, in the case of live monitoring only the most recently created call can be monitored. These deficiencies only affect the real-time aspects of a recording, the persisted recordings and later review of those recordings are unaffected. Additionally, in a Mediant installation, all the calls will appear as two party calls, a conference call is recorded correctly, but the metadata of the recorded call will not indicate it is a conference call.

Support for Khomp and Dialogic SBCs is limited to two party call scenarios.

SBCs that don’t support attaching customer SIP headers to a SipRec conversation must contain a participant in the participant set that identifies a unique QMS user by Sip URI or extension data.