topic Re: CMS recorder cannot work in TelePresence and Video Infrastructure

CMS recorder cannot work

tausifishan — Mon, 18 Mar 2019 20:48:03 GMT

In cms event log

Info call 26: incoming SIP call from "sip:733777@vc-cucm01" to local URI "sip:777777@10.77.10.165:5060"
2018-01-24 07:24:35.971 Info call 26: setting up UDT RTP session for DTLS (combined media and control)
2018-01-24 07:24:35.989 Info call 26: compensating for far end not matching payload types
2018-01-24 07:24:40.884 Info call 26: audio prompt play time out
2018-01-24 07:24:45.004 Info starting automatic recording (space '.... Conference Meeting Room')
2018-01-24 07:24:45.004 Info participant "733777@vc-cucm01" joined space d1e61cda-fd7d-46f6-86a0-0887c8c7773e (..... Conference Meeting Room)
2018-01-24 07:24:45.005 Warning unable to start recording -- no available recording devices

Re: CMS recorder cannot work

Jaime Valencia — Wed, 24 Jan 2018 19:15:27 GMT

What configuration do you have in place?

Is the NFS target is reachable and with read/write access?

Re: CMS recorder cannot work

Patrick Sparkman — Wed, 24 Jan 2018 21:41:21 GMT

Couple of things to check:

Check the certificate in the recorder trust to ensure it's the correct one used by the Call Bridge.
Check the syslog (SFTP to CMS > log file) to see if the NFS storage is mounted.

Troubleshooting recording issues (including the one your facing) is covered in Configure Recorder in CMS/Acano Call Bridge.

Re: CMS recorder cannot work

tausifishan — Thu, 25 Jan 2018 06:51:38 GMT

In CMS event log i found this error

"unable to start recording -- no available recording devices"

Re: CMS recorder cannot work

Patrick Sparkman — Thu, 25 Jan 2018 06:55:00 GMT

Check your configuration using the guide I provided in my earlier reply. Is everything configured correct per the guide?

Re: CMS recorder cannot work

Farrukh ' — Thu, 19 Apr 2018 05:35:01 GMT

I am facing the same issue. how did you resolved your issue??

Further I looked into the recorder logs and it seems like it is not getting anything from the CMS-Core server.

I also verified my CB cert and it seems fine to me.

and BTW the link Patrick shared doesnt cover this issue

Re: CMS recorder cannot work

Patrick Pettit — Thu, 26 Apr 2018 23:44:02 GMT

If you have everything configured properly, you can do a GET via API to /recorders/<recorder id>/status and see if its successfully connected. If you do, seeing the logs from the recorder would be of help to see what happens there. If callbridge is able to connect and authentication is successful, you should see entries in the log like:

recorder-proxy[1]: 2018/04/26 23:39:59 Connection from <callbridge ip>: Authentication succeeded
recorder-proxy[1]: 2018/04/26 23:39:59 Connection from <callbridge ip>: Connection terminated

If so, seeing the recorder logs when the recorder is making an attempt to connect would be helpful to see.