Cisco Meeting Server records conferences by creating a SIP connection to a recoding server and streaming the conference to the recorder. By using a standard SIP connection, the options for recording will include most third-party recording services and Cisco Meeting Servers own recording service.
Call Leg profiles are created for recording connections to determine features on the connection. Controllable features include; screen layouts and presentation channel options including whether a separate content channel is used for the recording. Profiles allow greater flexibility in the final rendered recording on advanced Recording Servers where editing of the recording is allowed, and if the content and video channel are both available to manipulate separately.
The Cisco Meeting Server recoding service provides a basic recording service where it will receive a SIP media connection and transcode the stream into MP4 format and place the recording file on a network file server. The files are stored in a sub folder on the server /spaces/<space ID> where a separate folder is created for each space to allow recordings to be better organized. The Cisco Meeting Server recorder will support resolutions up to 1080p at 30fps to give high-quality recordings.
In the diagram above, the Call Profile has the sipRecorderURI parameter set to firstname.lastname@example.org. When a user in this space starts the recording, the Call Bridge will look at the Call Profile to get the URI and then search for a dial plan rule that matches the domain. It will then send a SIP INVITE message to the address in the SIP Proxy field and establish a SIP connection and start streaming the media.
If you are using a third-party recoding server, then the Outbound Rule will need to route the call to the appropriate place which may be somewhere on the network or potentially out through the Expressway to a cloud-based service.
1.User in this space starts the recording.
2.The Call Bridge will look at the Call Profile to get the URI email@example.com
3.The Call Bridge search for an Outbound Call rule that matches the domain rec.lab.local.
4.It will send a SIP INVITE message to the address in the SIP Proxy field 10.1.5.50.
5.And establish a SIP connection and start streaming the media.
If you are deploying multiple Cisco Meeting Server recorders, it is recommended to deploy them behind a Call Control device such as Cisco Unified CM. The Call Control device will be able to provide load balancing and failover support. In this scenario, the recording URI Outbound Dial Plan rule needs to route to the Call Control device rather than directly to the Recording Server. If the Call Control device is Cisco Unified CM, you will need to create a SIP trunk to each of the recorders and add them all to the same route group and route list. If the Call Control is Cisco Expressway-C, then each recorder should have their own neighbor zone and search rules with the same priority to manage the load balancing of the calls equally across the recorders.
When deploying the Cisco Meeting Server, there are several supported deployment architectures. You can have multiple Call Bridges connected to a single Recorder storing files in sub directories on a single NFS server.
You can deploy multiple recorders with a single Call Bridge and in this scenario, you will need to route the calls through a Call Control device such as Cisco Unified CM. The Call Control will balance the load between the two recorders, and they can store the files to different NFS servers. If you were using VBrick or another content management server, then you would need to enable two uploaders to upload the files from different locations to the content manager.
Alternatively, you can have multiple Call Bridges and multiple recorders with all calls routed through the Call Control and the recordings stored on different NFS servers.
You can have multiple recorders storing files into the same location and in this scenario if you were using a content management server you would only need to enable one uploader to transfer the files.
Enabling the Cisco Meeting Server recorder on the same physical server as the Call Bridge is not supported in a production environment. It is only supported in a lab or testing environment due to the potential performance impact of having both services, which are resource-intensive, using the same physical hardware.
Once the recorders and Call Bridge configurations are complete, you will need to configure a DTMF Profile, Call Profile and Call Leg Profile to control how the Recording Server will be used.
The DTMF profile controls the touch tones that are used to start and stop a recording. The DTMF profile is assigned to the global profile, which means users and guests must use the same tones, you cannot have different users assigned different DTMF profiles.
The Call Profile can be assigned to the global profile, to a space, or assigned to an active call. The Call profile determines whether a meeting can be recorded or not and the SIP Recording URI that is used to set up the SIP call to the Recording Server. If the Call Profile is assigned to the global profile, then that becomes the default for all spaces and calls unless they have their own profile set. A profile set against an active call has a higher priority than one set on a space which itself will override the default profile.
A Call Leg Profile will be assigned to a user when they join a meeting and determines whether they are allowed to start and stop the recording. The call leg profile can be set in many locations and depending on how the user joins the call will determine which profile they pick up and therefore whether they can record the call or not. It is perfectly possible that a user will be allowed to control the recording in one meeting but not in another.
Hello, I need help to figure out how to convert my .webex meeting recording to .mp4. I shut down my computer right after ending the meeting so the conversion did not take place and now I cannot access the content of my recording. I can't use the NBRC...
By definition Each Unified CM node can support registration for a maximum of 10,000 endpoints. Each cluster can support configuration and registration for a maximum of 40,000 endpoints. In a CLUSTER with eight nodes running Call Processing, if ...
Greetings, Wanted to share a few lessons learned while migrating from a distributed to centralized IMP deployment. Our current setup included many CUCM/IMP distributed clusters with centralized Expressway server for MRA login. We did not wish to perf...