Jibri Docker issue to connect Jitsi-Server for multiple recording

Install & Config Docker
1

Hi Everyone,

We installed our Jitsi service in AWS EC2 instance and Jibri in a separate Docker machine. Jibri having 4 docker images.

Issue :
We can record one meeting at a time without any issues, while start second recording, it says “Recording Failed”.

Can anyone help us to recoding multiple meeting simultaneously using jibri docker.

Thanks in Advance

Ramachandran Umapathi

2

At the same time, only single recording is allowed. you need to run multiple instances(scale jibri) for multiple recording.you can follow the jitsi-handbook for further info.

1 Like
3

Thanks for your response @metadata,

I scaled Jibri Docker instance into four. but still I can record only one meeting at a time.
This is my Environment(attached)

Iamge
Iamge1360×621 17 KB

Regards,
Ram U

4

Have you adjusted asoundrc file?

5

Thanks for your response,

I execute the following commands, can you confirm is this correct?

docker exec -t docker-jitsi-meet_jibri_1 sed -i ‘s/Loopback/0/g’ /home/jibri/.asoundrc
docker restart docker-jitsi-meet_jibri_1

docker exec -t docker-jitsi-meet2_jibri_1 sed -i ‘s/Loopback/1/g’ /home/jibri/.asoundrc
docker restart docker-jitsi-meet_jibri_1

docker exec -t docker-jitsi-meet_jibri_2 sed -i ‘s/Loopback/2/g’ /home/jibri/.asoundrc
docker restart docker-jitsi-meet_jibri_2

docker exec -t docker-jitsi-meet2_jibri_2 sed -i ‘s/Loopback/3/g’ /home/jibri/.asoundrc
docker restart docker-jitsi-meet_jibri_2

Reagrds,
Ram U

6

This is my config for jibri instance 1:

# playback PCM device: using loopback subdevice 0,0
pcm.amix {
  type dmix
  ipc_key 219345
  slave.pcm "hw:Loopback_1,0,0"
}

# capture PCM device: using loopback subdevice 0,1
pcm.asnoop {
  type dsnoop
  ipc_key 219346
  slave.pcm "hw:Loopback_1,0,1"
}

# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "amix"
  capture.pcm "asnoop"
}
pcm.bmix {
  type dmix
  ipc_key 219347
  slave.pcm "hw:Loopback_1,1,1"
}

pcm.bsnoop {
  type dsnoop
  ipc_key 219348
  slave.pcm "hw:Loopback_1,1,0"
}

pcm.bduplex {
  type asym
  playback.pcm "bmix"
  capture.pcm "bsnoop"
}
# ------------------------------------------------------
# for jack alsa_in and alsa_out: looped-back signal at other ends
#pcm.ploop {
#  type plug
#  slave.pcm "hw:Loopback_1,1,1"
#}

#pcm.cloop {
#  type dsnoop
#  ipc_key 219348
#  slave.pcm "hw:Loopback_1,0,1"
#}

# ------------------------------------------------------
# default device

pcm.!default {
  type plug
  slave.pcm "aduplex"
}

and this is for instance 2:

# playback PCM device: using loopback subdevice 0,0
pcm.amix {
  type dmix
  ipc_key 219345
  slave.pcm "hw:Loopback_2,0,0"
}

# capture PCM device: using loopback subdevice 0,1
pcm.asnoop {
  type dsnoop
  ipc_key 219346
  slave.pcm "hw:Loopback_2,0,1"
}

# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "amix"
  capture.pcm "asnoop"
}
pcm.bmix {
  type dmix
  ipc_key 219347
  slave.pcm "hw:Loopback_2,1,1"
}

pcm.bsnoop {
  type dsnoop
  ipc_key 219348
  slave.pcm "hw:Loopback_2,1,0"
}

pcm.bduplex {
  type asym
  playback.pcm "bmix"
  capture.pcm "bsnoop"
}
# ------------------------------------------------------
# for jack alsa_in and alsa_out: looped-back signal at other ends
#pcm.ploop {
#  type plug
#  slave.pcm "hw:Loopback_2,1,1"
#}

#pcm.cloop {
#  type dsnoop
#  ipc_key 219348
#  slave.pcm "hw:Loopback_2,0,1"
#}

# ------------------------------------------------------
# default device

pcm.!default {
  type plug
  slave.pcm "aduplex"
}

Please check your config with these files.
As it shows, the only difference between two file is at “hw:Loopback_x,x,x”.
By this template, you can run any number of jibri instances.

7

I prepared a complete manual on Installing Multiple Jibris on Docker. See here;

8

Hello. I have a separate server for jibri and it works fine with jitsi. I decided to scale the number of jibri services and raised jibri to docker using this manual https://doganbros.com/index.php/jitsi/installing-jibri-as-docker-images-scallable-and-managable-way-of-conference- recording/. However jibri in docker doesn’t work with my jitsi. If I change .env to another jitsi server, then everything picks up there. I can’t understand what the problem is and where to dig?

9

I found the problem. The jitsi server is behind my NAT. Jibri connects via a local IP and has a mapping of the domain and a local IP in his hosts, and the docker, when it connects, tries to do this via the global IP, and access is closed on port 5222 via it.