Jigasi and 3CX: One way audio only (conference -> phone)

Hi,

I finally managed to get Jigasi to connect to my 3CX and to actually dial into a Jitsi conference.

However, the next problem I ran into is that while on the phone I can hear what is said in the Jitsi conference, the same is not true vice versa: What is said on the phone can’t be heard in the Jitsi conference.

Once the call is established, I see the following error messages from Jigasi:

Jigasi 2021-07-17 05:28:23.377 SEVERE: [1908] net.sf.fmj.media.Log.error()   Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed

Jigasi 2021-07-17 05:28:23.384 SEVERE: [1908] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@5e788691

Jigasi 2021-07-17 05:28:23.390 SEVERE: [1906] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@5e788691

Jigasi 2021-07-17 05:28:24.386 SEVERE: [1831] org.jitsi.jigasi.SipGatewaySession.run().1534 [ctx=162649969967438172529] Stopped receiving RTP for Call: id=1626499699619146676737 peers=1

In case this matters, at this point in time, the incoming call is just from another internal extension (I will try external calls, once the internal ones work).

Any experience with this error (I found topics where people had the one way audio problem but in the other direction)?

Thanks!

Make sure your sip side does latching - send audio to where it comes from.
In old asterisk versions this option was nat=yes.

Do you (or maybe other users) happen to know whether 3CX supports latching and, if it does, how to enable it?

As I said in the other thread, I don’t know what I am doing. But NAT would seem to me to be relevant only with external calls. I will need to enable external calls eventually but currently I am trying to get internal calls to work. So I am not sure whether NAT could be the problem here.

Your jigasi is behind nat and jigasi expects the sip server-side to handle the NAT as most sip providers do so with latching method.

No idea about 3CX :man_shrugging:

Yes, my Jigasi is behind NAT but so is my SIP-Server. They sit both behind my router/firewall.

But, then again, Jigasi sits inside Docker. So there is another NAT probably that they don‘t share.

I will check about 3CX in their forum. Of course I had googled the topic but they only ever seem to discuss door latches that may or may not be able to be opened by 3CX…

Is there maybe another name for latching or a standard (like x.123 or whatever) that I could google/ask about?

https://tools.ietf.org/id/draft-ietf-mmusic-latching-05.html