cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4209
Views
5
Helpful
6
Replies

CMS Recorder Error

Jake Riecken
Level 1
Level 1

Hello all,

I think we are close to getting this setup.  We have the recorder sending .temp files to the NFS however they never convert to .mp4.

We have 2 CMS CB Servers and a CMS Recorder.  This is the error we are getting from the SYSLOG FOLLOW on the CMS Recorder.  I know it obviously has to be something with the cert but scratching my head here.  Any help would be awesome!

----------------------------------------------------------------------

Apr 28 15:01:42 user.info onb-cms-recorder recorder[1]: Start session d2fcafd1-a734-4910-8e31-a341d327d377
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Start send
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Start Keepalives
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Bot started
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Media Framework listening on /tmp/acano-socket-d2fcafd1-a734-4910-8e31-a341d327d377
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Media Framework connected
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Media Framework is up.
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Create acano.mf.Object(1, video_decoder)
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Create acano.mf.Object(2, audio_decoder)
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Create acano.mf.Object(3, video_compose)
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Create acano.mf.Object(4, sync_pipe)
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Connect acano.mf.Object(1, video_decoder), 0 to acano.mf.Object(3, video_compose), 0
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Connect acano.mf.Object(3, video_compose), 0 to acano.mf.Object(4, sync_pipe), 0
Apr 28 15:01:42 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Connect acano.mf.Object(2, audio_decoder), 0 to acano.mf.Object(4, sync_pipe), 0
Apr 28 15:01:43 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:43 Connection from 172.XX.XXX.24:45598: Handshake failed: [tls: client didn't provide a certificate]
Apr 28 15:01:43 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:43 Connection from 172.XX.XXX.26:57553: Authentication succeeded
Apr 28 15:01:43 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:43 Connection from 172.XX.XXX.26:57553: Connection terminated
Apr 28 15:01:44 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:44 Connection from 172.XX.XXX.27:58948: Authentication succeeded
Apr 28 15:01:44 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:44 Connection from 172.XX.XXX.27:58948: Connection terminated
Apr 28 15:01:45 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:45 Connection from 172.XX.XXX.24:50242: Handshake failed: [tls: client didn't provide a certificate]
Apr 28 15:01:47 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:47 Connection from 172.XX.XXX.24:39070: Handshake failed: [tls: client didn't provide a certificate]
Apr 28 15:01:49 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:49 Connection from 172.XX.XXX,24:48505: Handshake failed: [tls: client didn't provide a certificate]
Apr 28 15:01:51 daemon.info onb-cms-recorder recorder-proxy[1]: 2017/04/28 15:01:51 Connection from 172.XX.XXX.24:36141: Handshake failed: [tls: client didn't provide a certificate]
Apr 28 15:01:52 user.err onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Client connect timed out
Apr 28 15:01:52 user.err onb-cms-recorder recorder[1]: Bot d2fcafd1-a734-4910-8e31-a341d327d377 failed: CLIENT_CONNECT_FAILED
Apr 28 15:01:52 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: End send
Apr 28 15:01:52 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: End Keepalives
Apr 28 15:01:52 user.info onb-cms-recorder recorder.d2fcafd1-a734-4910-8e31-a341d327d377[12244]: Bot finished without error

Thanks!

1 Accepted Solution

Accepted Solutions

You also need a SRV record in the Recorder (as a XMPP client) pointing to the XMPP server:

"User configured RRs": [
"_xmpp-client._tcp.DOMAIN IN A XMPP_SERVER_IP",
"_xmpp-client._tcp.DOMAIN 86400 IN SRV 0 5 5222 XMPP_FQDN"

Regards

View solution in original post

6 Replies 6

Ammar Saood
Spotlight
Spotlight

1. The Recorder behaves as an XMPP client, so the XMPP server needs to be enabled on the
Meeting Server hosting the Call Bridge

2. to keep it simple, use webadmin certificate for recorder as well.

3. double check your CLI config. it must be similar to that

recorder listen lo:8443 b:8443 (loopback if recorder uses same Callbridge server)
recorder certs webadmin.key webadmin.crt caroot.crt
recorder trust Callbridge.crt
recorder nfs 198.18.133.1:recordings/home/nfs

4.Remember to set the permissions on your NFS to rw and change the chown and chmod
permissions on the directory. For example:
sudo chown nobody:nogroup /record
sudo chmod -R 777 /record

5. Specify the HTTPS URL address that the Call Bridge will use to reach this recorder. . If using a local Recorder, the URL must be the loopback interface, for example
https://127.0.0.1:8443 or 192.x.x.x:8443

HTH

AMMAR 

please rate and mark answered if helpful.

You also need a SRV record in the Recorder (as a XMPP client) pointing to the XMPP server:

"User configured RRs": [
"_xmpp-client._tcp.DOMAIN IN A XMPP_SERVER_IP",
"_xmpp-client._tcp.DOMAIN 86400 IN SRV 0 5 5222 XMPP_FQDN"

Regards

Hi, I've already done to deploy cms standalone server as recorder and one standalone server as callbridge.

I glade to say that it is working, after 2 weeks of bad attempts.

If you still need help, let us know what is your status now...

can you please help me

I tryed without success

dns add rr "_xmpp-client._tcp.b00b IN A 10.80.60.10"

dns add rr "_xmpp-client._tcp.b00b 86400 IN SRV 0 5 5222 10.80.60.10"

and I also tryed without success localhost IP because it is single server

dns add rr "_xmpp-client._tcp.b00b IN A 127.0.0.1"

dns add rr "_xmpp-client._tcp.b00b 86400 IN SRV 0 5 5222 127.0.0.1"

domain is from xmpp config

acano> xmpp
Enabled : true
Clustered : false
Domain : b00b
Listening interfaces : a
Key file : recorder.key
Certificate file : recorder.crt
CA Bundle file : recorder.crt
Max sessions per user : unlimited
STATUS : XMPP server running
acano>

Hi

can you please explane

1. webadmin.key webadmin.crt      -- selfsigned ?

2. caroot.crt   -- if we use selfsigned in 1.  so where to find ROOT certificate ? 

3. recorder trust Callbridge.crt       -- selfsigned ?

Patrick Sparkman
VIP Alumni
VIP Alumni

In addition to the information Ammar has provided, you can use the Configure Recorder in CMS/Acano Call Bridge configuration example as a reference to setup and deploy the recorder on your CMS.