Cisco Meeting Server (CMS) v2.9 with native support for SIP recorder
We are excited to share with you that the Cisco Meeting Server (CMS) from version 2.9 natively supports third-party SIP recording service like REC.VC.
CMS customers have used REC.VC to record and live stream video meetings for years, simply by establishing a SIP session between the CMS room and REC.VC (by calling either way). The big change with CMS version 2.9 is that CMS + REC.VC customers can leverage the native recording button available in the various interfaces used by CMS users.
Cisco has shared the following details in the release notes published on April 8, 2020:
From 2.9, the Meeting Server allows configuration of an external third-party SIP recorder so that when recording is started an administrator-configured SIP URI is called instead of using the Meeting Server internal recorder component.
Note: Support for an external third-party SIP recorder still requires Meeting Server recording licenses.
The new SIP recorder feature:
- allows recorders to negotiate BFCP in order to receive separate video and content streams. This gives more flexible options for how recordings are formatted.
- supports the same resolutions as we do for standard SIP calls
- supports the same audio and video codecs as standard SIP calls
- as with the existing Meeting Server internal recorder, any media content sent by the SIP recorder is discarded
Note: The SIP recorder feature does not support TIP or Active Control.
Specifying the SIP recorder A new API parameter for /callProfile objects is introduced to specify the SIP recorder. It supports GET, PUT and POST and is defined as follows:
- sipRecorderUri — If set, this URI is used to dial out to when recording is enabled. If unset, the Meeting Server recorder component (if configured in /recorders) is used.
Starting / stopping the recording The same start / stop methods supported by the Meeting Server recorder component can be used to initiate a SIP recorder. Which recorder is used depends upon whether you have configured the API parameter sipRecorderUri. The methods currently supported are:
- With the callProfile recordingMode set to automatic, recording starts when users join. Users cannot start / stop the recording.
- When recordingMode is set to manual, users can start / stop recording using a dtmfProfile, Active Control, Meeting App or via an API PUT/POST on calls.
Finding out recording status The same methods supported by the Meeting Server recorder component can be used to find out the SIP recorder status, for example, GET on callLegs/ — the recording value in the status output found here indicates whether this callLeg is recording (true) or not (false).
New to REC.VC? Sign up for a free trial today!