How can I setup Jitsi to receive as SIP video call and also invite SIP account for video call?

I have setup Jigasi for SIP audio call, and it is working with my asterisk server. Both incoming and outgoing call. my jitsi setup is done in docker deployment in private server.

Now as I want to recieve incoming SIP video call and add the SIP participant in conference with his video on. I know there are some forum links but I am unable to get started.
I was following these links but couldnt undersatnd where to begin or is it the main doc for configuer SIP Jibri. Also as for docker deployment what is the step by step guide.
Can anyone please help to start the config process, to achieve Jisti SIP incoming video?

Thanks, any help would be appriciated.

sorry for pinging. @damencho, @saghul can you please help.

Jigasi is for audio-only call. You may check jitsi-videosipgw installer for non-Dockerized setup.

I think some changes are needed (see issue #496) to allow concurrent incoming calls.

ok. for dockerized Jitsi is there any guide?

does jigasi still be used when SIP jibri configured? I mean SIP audio is handled through jigasi and SIP video handled by Jibri? or jibri can do both ?

You can use both of them on the same setup

right now struggling to setup SIP video for dockerized verison though.

hi @emrah . can you suggest any docker based implementation of Jibri SIP video.
in this, link does it indicate for video SIP gateway?

I don’t know any Docker based implementation

Hi @Code_Conf and all,

FYI, at Renater we are developing our own (dockerized) solution: SIPMediaGW which is, in principle, quite close to the Jitsi videosipgw.
The main difference regarding Jitsi videosipgw is the call flow: the call is initiated from outside SIP endpoints.
We also use a different SIP client/library: Baresip (instead of PJSIP).

Hope it helps,


Thank you @Nicolas_Tizon :slightly_smiling_face:.
Let us check. So SIPMediaGW can be integrated with jitsi dockerized veriosn for SIP audio-video, and is it in developing phase?

It is worth mentioning that SIPMediaGW is totally independent from the Jitsi Meet instance in terms of deployment.

As previously mentioned, SIPMediaGW is a docker based gateway.

That said, the loopback video (and audio if WITH_ALSA=true) devices must be created on the host and shared to the container so the gateway itself is not 100% self-contained.

For Kamailio and Coturn, we use docker-compose as well but network_mode is set to ‘host’ for convenience: classically these server applications are configured to bind on a public IP interface but it should be possible to make them work with a docker NAT.

About the maturity level of this project: we keep developing new features (+bugs fixing, upgrades…) and in the same time, at Renater, we start to provide this alternative SIP access on top of our JitsiMeet based service (A.k.a Rendez-Vous).

1 Like