Cisco Meeting Server (Acano) recording not working

[al_vargas]

Hello,

I'm running a single server deployment lab on VMware. Everything is running fine, but recording.

I have done the following:
1) Generated and issued internal CA certificates
2) Configured recorder by CLI with certificates, listen to unbind port 8443
3) Configured by API the recorder URL https://127.0.0.1:8443
4) Created callLegProfiles and callProfile for allowing manual recording
5) Created dmtfProfile with startRecording and stopRecording patterns
6) Set up those profiles as default system profiles

I got the following error message in Status > General:
Recorder "https://127.0.0.1:8443" unavailable (connect failure)

By running openssl s_client -connect I do confirm port 8443 is closed. So I'm assuming recorder is not up. I have already tried versions 2.0.9, 2.1.2 and 2.1.3 without success.

Am I missing something? Has anyone been able to put it working?

The license command output is:

acano> license
Feature: callbridge status: Activated expiry: 2117-Feb-13 (36511 days remain)
Feature: turn status: Activated expiry: 2117-Feb-13 (36511 days remain)
Feature: webbridge status: Activated expiry: 2117-Feb-13 (36511 days remain)
Feature: recording status: Activated expiry: 2117-Feb-13 (36511 days remain)

Regards,

[Patrick Sparkman]

It appears since you've specified the loopback address for the recorder, if it's on the same server as the Call Bridge, did you configure the recorder to use the loopback interface?

recorder listen lo:8443

Can you provide the recorder output from the MMP?

[Eduardo Leon Dominguez]

Hello,

Same issue. My recorder listen on lo:8443 a:8443 but in Status-General appear a fault condition:

Recorder "https://127.0.0.1:8443" unavailable

I checked the port 8443 and it's closed.

If I try to record a videocall in the log appear this entry:

Warning: unable to start recording -- no available recording devices

Any Idea?, I checked all the configuration steps and all seems ok.

[Eduardo Leon Dominguez · Accepted solution]

I answer my own: Fixed, finally I had a problem with the Trust Bundle cert. Thanks.

[mariusstan]

Hello Eduardo,

Same problem on my side. What is with the trust bundle ? What is wrong there?

Regards,

M

[Patrick Sparkman]

A trust bundle is a single file (with an extension of .pem, .cer or.crt) holding a copy of the Root CA’s certificate and all intermediate certificates in the chain, refer to the CMS Certificate Guidelines based on your particular deployment for more information.

[mariusstan]

Hello Patrick,

Thank you for your answer but in my case I it is something related with the NFS share which was not mounted.

Kind regards,

Marius

[ragulan_dms]

Hi Guys, 

I am wondering if Cisco CMS recording support automatic 100% or we need to record via CMA ?  Is it possible to trigger the on-demand recording from TP endpoint or Jabber for a video conference call? 

Regards

Ragu.

[Patrick Sparkman]

CMS recorder can be set to automatically record or by manually using DTMF.  The below is from the deployment guide:

Use the new recordingMode parameter on the API object /callProfiles or /callProfiles/ to select whether a meeting can be recorded or not.

* Automatic - recording occurs without any user intervention, if recording cannot occur the meeting still occurs.

* Manual - users can manually start and stop the recording using DTMF.

* Disabled - no users can record.

Control which users have permission to start and stop recording by setting the recordingControlAllowed parameter on callLegProfiles.

Use the new startRecording and stopRecording parameters for /dtmfProfiles and /dtmfProfiles/ to map the DTMF tones for starting and stopping recording.

[ragulan_dms]

Thanks Partrick

[Mahmut AKALIN]

How can i use api? I tried firefox poster and postman.

https://x.x.x.x/api/v1/callProfiles

<callProfile id="94463e0e-294d-4457-b7da-38b94140fd33">
<recordingMode="Automatic"><recordingMode>
<callProfile>

https://x.x.x.x/api/v1/callProfiles

what is the usage?

Creating: POST method to the /recorders " node

Modifying: PUT to "/recorders/<recorder id>"

Parameters Type/Value Description/Notes

url URL The HTTP or HTTPS URL address that the Acano Call Bridge should

use to reach this recorder.

"/recorders/<recorder id>"

I want to do these steps. I use QNAP with NFS

3) Configured by API the recorder URL https://127.0.0.1:8443
4) Created callLegProfiles and callProfile for allowing manual recording
5) Created dmtfProfile with startRecording and stopRecording patterns
6) Set up those profiles as default system profiles

[Patrick Sparkman]

There are examples of using Chrome Postman and Firefox Poster within the CMS API Guides, as well as a detailed explanations of the different API methods (GET, POST, PUT, DELETE) that are used to configure CMS.

• GET is used for retrieval of existing information
• POST is used to create new objects
• PUT is used to modify an existing object
• DELETE is used to delete an object

Take a look at the CMS Configuration Guides on how to configure the recorder, once configured, the API is used configure Users and Spaces to record their meetings such as DTMF controls etc.

[Jake Riecken]

I think I am very close to getting this to work.  I have one issue.  When I click on the record button in the Meeting app and do a SYSLOG Follow on the CMS CB server I see the recording has started and .temp file get dumped into the NFS.

The problem is that the recording icon never changes to the option to Stop Recording.  It is my understanding that the Stop Recording is what changes the .temp file to a .mp4 file.  Is this correct?

Any idea on why I have no option to Stop Recording?

Thanks!

[danielw730]

I tested it.

If I upgrade my meeting app, it works.

Or using the dtmf to start and stop recording.

Try it!!!

[ypineda16]

Hi Jake, did you resolve the .tmp issue? I have the same issue with automatic recording. CMS logs shows recording is starting and stopping ok, but just getting .tmp file on NFS.

Thanks,