feat(chart): add jigasi

[emrahcom]

This PR adds jigasi.

jigasi allows SIP clients to join Jitsi meetings and transciption. No need to publicly open ports if SIP server allows media traffics over itself.

Even some use-cases are tricky as mentioned in this issue, there are some other uses-cases which work with simple settings.

[spijet]

Hello @emrahcom! Thank you for your PR 🧡

I have a couple of questions/nitpicks, if you don't mind. Please check the review. :)

[spijet]

Do I understand it right, that Jigasi in this case doesn't need to receive any incoming connections from the outside world? How exactly is it going to communicate with the SIP server and receive incoming calls?

[emrahcom]

Do I understand it right, that Jigasi in this case doesn't need to receive any incoming connections from the outside world? How exactly is it going to communicate with the SIP server and receive incoming calls?

No, it can still receive incoming calls because it is registered SIP server and since SIP server is publicly accessible, jigasi is also publicly accessible through SIP server.

By the way, I tested this use-case in my deployment and it works. I created a jigasi instance by using this Helm Charts and I have no open ports for this instance but the incoming call and media traffic through SIP server work.

[spijet]

By the way, I tested this use-case in my deployment and it works. I created a jigasi instance by using this Helm Charts and I have no open ports for this instance but the incoming call and media traffic through SIP server work.

Hmm, that's interesting. I was weary of trying Jigasi out myself since I don't have any SIP infrastructure around, and the official Jitsi Meet on Docker documentation mentions something about ports 20000~20050/UDP needed for it.

[spijet]

Anyway, LGTM. Let's merge it and wait for @at-platform24 to finalize #92 before tagging a new release.

[emrahcom]

By the way, I tested this use-case in my deployment and it works. I created a jigasi instance by using this Helm Charts and I have no open ports for this instance but the incoming call and media traffic through SIP server work.

Hmm, that's interesting. I was weary of trying Jigasi out myself since I don't have any SIP infrastructure around, and the official Jitsi Meet on Docker documentation mentions something about ports 20000~20050/UDP needed for it.

If the SIP server doesn't allow media traffic (RTP) over itself then these port should be publicly open on Jigasi but this is not the only option.

And jigasi is also used for other purpose such as transcription.

[Yerachmiel-Wand]

Hi, about

And jigasi is also used for other purpose such as transcription.

Would you mind pointing to any docs explaining how to setup jigasi for transcription with the helm chart?
I don't need SIP, only the ability to generate transcriptions from calls, even not real time.

Thank you. :)