Use REC.VC to securely capture video meetings on Cisco Meeting Server (CMS):
Access your secure REC.VC account to play or trim your recordings.
Create and share playback links (with or without password), enabling others to play videos you share.
Download recordings in mp4 format.
Use REC.VC to live stream your video meeting in one of the following ways:
*REC.VC supports Facebook, YouTube and other RTMP destinations.
Are you using Cisco Webex?
See REC.VC recording and streaming with Cisco Webex.
When calling from the REC.VC user interface to the meeting on Cisco Meeting Server (CMS), you’ll need to enter the video address for the virtual meeting room or cospace in question. CMS is normally deployed on-premise and the video address structure is typically something like alias@subdomain.domain.com, e.g. meeting-id@video.yourorg.com, name@vmr.yourorg.com or firstname.lastname@meet.yourorg.com. If the meeting is protected by PIN or Access code, you’ll need to add this to the PIN field (in order for REC.VC to authenticate as a legitimate participant for recording or live streaming purposes).
Your REC.VC video address is listed in the top-left corner of the REC.VC interface (it’s not demo@rec.vc 😉):
From 2.9, CMS 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 external SIP recorder feature:
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:
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:
Finding out recording status The same methods supported by the CMS 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).