Jigasi gives up on reaching the SIP server after several minutes

[denzs]

Description

We are using Jigasi with Asterisk (via udp on 127.0.0.1) to allow SIP-based Dialins for our Jitsi Conferences. This works fine as long as Asterisk is already running. If Asterisk is not reachable for some minutes Jigasi wont try to REGISTER anymore and has to be restarted.

Current behavior

Jun 18 15:46:12 meet-sipgw conmon[2405674]: 2024-06-18 13:46:12.317 INFO: [323] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /127.0.0.1:5060
Jun 18 15:46:12 meet-sipgw podman[2405647]: 2024-06-18 13:46:12.317 INFO: [323] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /127.0.0.1:5060

# asterisk stopped...

Jun 18 15:52:22 meet-sipgw conmon[2405674]: 2024-06-18 13:52:22.880 INFO: [34] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Registered; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]
Jun 18 15:52:22 meet-sipgw podman[2405647]: 2024-06-18 13:52:22.880 INFO: [34] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Registered; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]
Jun 18 15:52:22 meet-sipgw conmon[2405674]: 2024-06-18 13:52:22.891 INFO: [34] net.java.sip.communicator.plugin.reconnectplugin.PPReconnectWrapper.scheduleReconnectIfNeeded: Reconnect ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) after 5000 ms.
Jun 18 15:52:22 meet-sipgw podman[2405647]: 2024-06-18 13:52:22.891 INFO: [34] net.java.sip.communicator.plugin.reconnectplugin.PPReconnectWrapper.scheduleReconnectIfNeeded: Reconnect ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) after 5000 ms.
Jun 18 15:52:22 meet-sipgw conmon[2405674]: 2024-06-18 13:52:22.903 INFO: [34] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:52:22 meet-sipgw podman[2405647]: 2024-06-18 13:52:22.903 INFO: [34] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:52:23 meet-sipgw conmon[2405674]: 2024-06-18 13:52:23.905 INFO: [34] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:52:23 meet-sipgw podman[2405647]: 2024-06-18 13:52:23.905 INFO: [34] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:52:27 meet-sipgw conmon[2405674]: 2024-06-18 13:52:27.901 INFO: [37] net.java.sip.communicator.plugin.reconnectplugin.PPReconnectWrapper$ReconnectTask.run: Start reconnecting ProtocolProviderServiceSipImpl(SIP:jigasi@localhost)
Jun 18 15:52:27 meet-sipgw podman[2405647]: 2024-06-18 13:52:27.901 INFO: [37] net.java.sip.communicator.plugin.reconnectplugin.PPReconnectWrapper$ReconnectTask.run: Start reconnecting ProtocolProviderServiceSipImpl(SIP:jigasi@localhost)
Jun 18 15:52:27 meet-sipgw conmon[2405674]: 2024-06-18 13:52:27.910 INFO: [37] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been started
Jun 18 15:52:27 meet-sipgw podman[2405647]: 2024-06-18 13:52:27.910 INFO: [37] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been started
Jun 18 15:52:27 meet-sipgw conmon[2405674]: 2024-06-18 13:52:27.925 INFO: [37] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
Jun 18 15:52:27 meet-sipgw podman[2405647]: 2024-06-18 13:52:27.925 INFO: [37] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
Jun 18 15:53:33 meet-sipgw conmon[2405674]: 2024-06-18 13:53:33.901 INFO: [325] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]
Jun 18 15:53:33 meet-sipgw podman[2405647]: 2024-06-18 13:53:33.901 INFO: [325] SipGateway.registrationStateChanged#120: REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:jigasi@localhost) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]
Jun 18 15:53:33 meet-sipgw conmon[2405674]: 2024-06-18 13:53:33.911 INFO: [325] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:53:33 meet-sipgw podman[2405647]: 2024-06-18 13:53:33.911 INFO: [325] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:53:34 meet-sipgw conmon[2405674]: 2024-06-18 13:53:34.912 INFO: [325] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped
Jun 18 15:53:34 meet-sipgw podman[2405647]: 2024-06-18 13:53:34.912 INFO: [325] net.java.sip.communicator.impl.protocol.sip.SipLogger.logInfo: Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped

# starting asterisk again

Expected Behavior

It would be desirable to have Jigasi try to re-establish the SIP Registration and not giving up finally.

Possible Solution

Maybe it is possible to configure the SIP-Timers behaviour to not time out?!

Steps to reproduce

• register Jigasi to a SIP-Server
• shut down the SIP-Server
• wait ~ 5 Minutes
• restart SIP-Server
• watch Jigasi not register anymore

Environment details

We are using Jigasi1.1.329-g04ad08fLinux respectively Container Image: jitsi/jigasi:stable-9457-2 with Asterisk 18.10.0~dfsg+~cs6.10.40431411-2 (should not matter).