Hello.
Initially the integration with asterisk works and you can dial into the jitsi meeting. But after awhile it stops. Asterisk shows the error below. After getting that error, I reboot the jitsi server and everything works again for awhile. Any ideas?
I checked the jigasi log and didn’t see an error today. I’m not sure if that’s always the case or not.
[2022-02-17 10:00:16] VERBOSE[3619][C-00002f8f] pbx.c: Executing [s@Jitsi-Conference-Entry:25] Set("SIP/2053-00006037", "SPYGROUP=1000") in new stack
[2022-02-17 10:00:16] VERBOSE[3619][C-00002f8f] pbx.c: Executing [s@Jitsi-Conference-Entry:26] Dial("SIP/2053-00006037", "SIP/92710,3,m(silence)A(/tmp/name-1135920415)M(Jitsi-join)") in new stack
[2022-02-17 10:00:16] WARNING[3619][C-00002f8f] app_dial.c: Unable to create channel of type 'SIP' (cause 20 - Subscriber absent)
[2022-02-17 10:00:16] VERBOSE[3619][C-00002f8f] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
[2022-02-17 10:00:16] VERBOSE[3619][C-00002f8f] pbx.c: Executing [s@Jitsi-Conference-Entry:27] Verbose("SIP/2053-00006037", "0, Contacting 92710... Status is CHANUNAVAIL ") in new stack
[2022-02-17 10:00:16] VERBOSE[3619][C-00002f8f] app_verbose.c: Contacting 92710... Status is CHANUNAVAIL
Also, I have this line in my sip-communicator.properties which I thought was supposed to fix this problem last time people at my org reported it.
net.java.sip.communicator.plugin.reconnectplugin.ATLEAST_ONE_SUCCESSFUL_CONNECTION.SIP\:92710@pbx.fqdn.com=true
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.KEEP_ALIVE_INTERVAL=25
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.KEEP_ALIVE_METHOD=OPTIONS
That sounds like the options keep-alive to handle that.
Maybe add pings and from the asterisk side or share your whole config after masking private info.
The SIP registration stayed connected for a long time, but today we had some VPNs go down that connect the servers. The system never re-registered after the VPN came back up.
The VPN went down at 17:20 and didn’t come up for about 2 hours later. It looks like jigasi only tries to reconnect twice and then gives up.
Does this seem like the intended behavior or are config files needed?
2022-03-02 17:20:40.882 INFO: [37] plugin.reconnectplugin.PPReconnectWrapper.scheduleReconnectIfNeeded().425 Reconnect ProtocolProviderServiceSipImpl(SIP:92710@pbx.mydom.com) after 4000 ms.
2022-03-02 17:20:40.883 INFO: [37] org.jitsi.jigasi.SipGateway.registrationStateChanged().120 REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:92710@pbx.mydom.com) -> RegistrationStateChangeEvent[ oldState=Registered; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]
2022-03-02 17:20:44.884 INFO: [39] plugin.reconnectplugin.PPReconnectWrapper.run().452 Start reconnecting ProtocolProviderServiceSipImpl(SIP:92710@pbx.mydom.com)
2022-03-02 17:20:44.904 INFO: [39] org.jitsi.jigasi.SipGateway.registrationStateChanged().120 REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:92710@pbx.mydom.com) -> RegistrationStateChangeEvent[ oldState=Unregistered; newState=RegistrationState=Registering; userRequest=false; reasonCode=-1; reason=null]
2022-03-02 17:21:16.918 INFO: [106431] org.jitsi.jigasi.SipGateway.registrationStateChanged().120 REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:92710@pbx.mydom.com) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]