Jigasi not terminating calls on conference end

Upon closing a conference with the hangup button, any dialed in users remain connected.
Also , If I kick a dialed in user, their phone remains active. Jigasi is not sending a BYE message to terminate the call.

Any place to validate how/why jigasi is not terminating a call?

Last few lines of my Jigasi log after hanging up via web:

2020-05-15 12:37:33.450 INFO: [460] org.jitsi.jigasi.JvbConference.callStateChanged().1182 [ctx=15895606518181245923668] JVB conference call IN_PROGRESS.
2020-05-15 12:37:40.175 INFO: [1294] impl.protocol.jabber.ChatRoomJabberImpl.left().1300 testing@conference.myllama/d31d4a70 has left the testing@conference.meet.myllama.com ch>
2020-05-15 12:37:40.175 INFO: [1294] org.jitsi.jigasi.JvbConference.memberPresenceChanged().986 [ctx=15895606518181245923668] Member left : OWNER rhfstewydci4jtyh@guest.meet.myllama/s>
2020-05-15 12:38:00.210 INFO: [1294] org.jitsi.jigasi.JvbConference.onJvbCallEnded().877 [ctx=15895606518181245923668] Proceed with gwSession call on xmpp call hangup.
2020-05-15 12:38:00.218 SEVERE: [1334] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to send a packet to target /192.16.0.32:10000:java.io.IOException: No active socket.
2020-05-15 12:38:00.223 SEVERE: [1332] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to send a packet to target /192.16.0.32:10000:java.io.IOException: No active socket.
2020-05-15 12:38:00.224 SEVERE: [1294] org.jitsi.impl.neomedia.RTPConnectorOutputStream.log() Failed to send a packet to target /192.16.0.32:10000:java.io.IOException: No active socket.

Hi Craig
I’m getting the same issue. Did you figure out this ?

Thank you

No, haven’t figured that one out. I would think there should be a setting to destroy the room upon host leaving, but I haven’t found anything like that document.

Gotcha. Thank you

What is your setting for org.jitsi.jigasi.JVB_INVITE_TIMEOUT? This is the time the sip call will not be hanguped waiting for another web participant to join.

Hi @damencho

The issue is not the SIP call getting hung up. The problem is that if you end the conference call on JITSI-Meet (browser), the call never hung up and JIGASI never sends the BYE back to the PBX therefore caller is on the call.
I don’t have this setting org.jitsi.jigasi.JVB_INVITE_TIMEOUT but I tried puting this in but it didn’t work either.
Thank you

In simple words,

When conference session is ended on web (browser), SIP call is not getting hungup and is on conference room.

What is your version of jigasi that you use?

2020-05-15 12:38:00.210 INFO: [1294] org.jitsi.jigasi.JvbConference.onJvbCallEnded().877 [ctx=15895606518181245923668] Proceed with gwSession call on xmpp call hangup.

This log means that the xmpp call was hangup, and the sip call is not hangup waiting for timeout to pass or new participant to join … But if you don’t have jvb_invite_timeout that sounds strange …

Hi @damencho

I’m using ->
ii jigasi 1.1-107-g6928850-1 amd64 Jitsi Gateway for SIP
ii jitsi-meet 2.0.4627-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.4127-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-turnserver 1.0.4127-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.4127-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.4127-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-202-g5f9377b9-1 all WebRTC compatible Selective Forwarding Unit (SFU)

Share your jigasi config, please, masking the personal config.

Please find the attached file.

Thanks for looking tho.jigasi.txt (8.7 KB)

I see that the default value is 30 seconds. Are you waiting for 30 seconds when testing this? And the call continues after these 30 seconds?

Hi,

SIP call keeps on going even after 30 seconds.

Any updates @damencho Our customers are paying for the SIP call which is not getting hung up after destroying the conference bridge on browser.

Thanks for helping

I don’t have an idea at the moment. We are using this in production with no problem.
You can put some prints around Proceed with gwSession call on xmpp call hangup and see why the call does not go into hangup, it should after 30 seconds.
You can enable the pcap logging and check the sip messages …
You can also experiment with jvb timeout setting it to -1 … Or 0.

Setting that value to 0 fixes the problem. Thank you @damencho