[jitsi-users] Decreasing offline time for re-registration to backup SIP registrar


#1

Hello,
First of all I would like to say big thanks to whole Jitsi team - great work I think!

.. and my plea for help follows:
I have environment with 3 SIP registrars REG1, REG2, REG3 and DNS SRV record pointing to these 3 servers
REG1 with priority 10, REG2 with priority 20, REG3 with 30 ... Failover works perfectly ...
But the time for registration to the next registrar is prolonged by sending of 11 SIP REGISTER requests (lasting together 31.5 seconds)
Is there any elegant way how to ensure following:
1) decrease the number of REGISTER attempts (currently 11)
2) shorten the maximal interval between sending the REGISTER attempts (currently it is 4 seconds)
3) shorten the 17.5 s timeout after last non-answered REGISTER is sent

Here is brief packet sequence:
RelTime source IPA destination IPA
0.000000 10.14.7.251 10.97.97.42 SIP Request: REGISTER
0.500945 10.14.7.251 10.97.97.42 SIP Request: REGISTER
1.500670 10.14.7.251 10.97.97.42 SIP Request: REGISTER
3.500710 10.14.7.251 10.97.97.42 SIP Request: REGISTER
7.501074 10.14.7.251 10.97.97.42 SIP Request: REGISTER
11.502471 10.14.7.251 10.97.97.42 SIP Request: REGISTER
15.502796 10.14.7.251 10.97.97.42 SIP Request: REGISTER
19.503166 10.14.7.251 10.97.97.42 SIP Request: REGISTER
23.504678 10.14.7.251 10.97.97.42 SIP Request: REGISTER
27.504843 10.14.7.251 10.97.97.42 SIP Request: REGISTER
31.506143 10.14.7.251 10.97.97.42 SIP Request: REGISTER
49.022618 10.14.7.251 10.97.36.10 SIP Request: REGISTER
49.082571 10.97.36.10 10.14.7.251 SIP Status: 100 Trying
49.197027 10.97.36.10 10.14.7.251 SIP Status: 200 OK

The registration to next SIP registrar is started after message in Jitsi log:
INFO: impl.protocol.sip.SipLogger.logInfo().175 Info from the JAIN-SIP stack: the sip stack timer gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped

Thank you in advance for your help
Best Regards
Petr


#2

Hey Petr,

На 18.08.11 15:32, Petr.Valik@tieto.com написа:

Hello,
First of all I would like to say big thanks to whole Jitsi team – great
work I think!

Thank you for your kind words (and sorry for the lag!)

.. and my plea for help follows:
I have environment with 3 SIP registrars REG1, REG2, REG3 and DNS SRV
record pointing to these 3 servers
REG1 with priority 10, REG2 with priority 20, REG3 with 30 … Failover
works perfectly …
But the time for registration to the next registrar is prolonged by
sending of 11 SIP REGISTER requests (lasting together 31.5 seconds)
Is there any elegant way how to ensure following:

   1. decrease the number of REGISTER attempts (currently 11)
   2. shorten the maximal interval between sending the REGISTER attempts
      (currently it is 4 seconds)
   3. shorten the 17.5 s timeout after last non-answered REGISTER is sent

This is possible in theory but from a protocol point of view, messing
with the transaction state machine is not a good idea. If you push down
the timers it becomes unclear whether the remote machine is unreachable
or if there's simply a temporary packet loss issue.

What I'd suggest is using TCP or TLS instead. The TCP RST gives you an
instant indication that the machine is unavailable and we move to the next.

Hope this helps,
Emil

···

Here is brief packet sequence:
RelTime source IPA destination IPA
0.000000 10.14.7.251 10.97.97.42 SIP Request: REGISTER
0.500945 10.14.7.251 10.97.97.42 SIP Request: REGISTER
1.500670 10.14.7.251 10.97.97.42 SIP Request: REGISTER
3.500710 10.14.7.251 10.97.97.42 SIP Request: REGISTER
7.501074 10.14.7.251 10.97.97.42 SIP Request: REGISTER
11.502471 10.14.7.251 10.97.97.42 SIP Request: REGISTER
15.502796 10.14.7.251 10.97.97.42 SIP Request: REGISTER
19.503166 10.14.7.251 10.97.97.42 SIP Request: REGISTER
23.504678 10.14.7.251 10.97.97.42 SIP Request: REGISTER
27.504843 10.14.7.251 10.97.97.42 SIP Request: REGISTER
31.506143 10.14.7.251 10.97.97.42 SIP Request: REGISTER
49.022618 10.14.7.251 10.97.36.10 SIP Request: REGISTER
49.082571 10.97.36.10 10.14.7.251 SIP Status: 100 Trying
49.197027 10.97.36.10 10.14.7.251 SIP Status: 200 OK

The registration to next SIP registrar is started after message in Jitsi
log:
INFO: impl.protocol.sip.SipLogger.logInfo().175 Info from the JAIN-SIP
stack: the sip stack timer
gov.nist.javax.sip.stack.timers.DefaultSipTimer has been stopped

Thank you in advance for your help
Best Regards
Petr

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31