[Serdev] TCP Blocking Connect issue

[Jiri Kuthan]

At 03:13 AM 8/23/2004, Andrew Mee wrote:
>It seems your assumption is right!
>
>Client Logs in.
>serctl ul show support at 192.168.2.253
><sip:192.168.2.11:10227;transport=tcp>;q=0.00;expires=3546
>
>Crash Client!!
>
>serctl ul show support at 192.168.2.253
><sip:192.168.2.11:10227;transport=tcp>;q=0.00;expires=3457
>
>Restart Client
>
>serctl ul show support at 192.168.2.253
><sip:192.168.2.11:10227;transport=tcp>;q=0.00;expires=3403
><sip:192.168.2.11:14858;transport=tcp>;q=0.00;expires=3585
>
>Ok the question now if the TCP connection cannot be made should it delete the not available connection and then try the next connection... or...
>Should perhaps register delete existing entries and create new ones?

The right way is to have the dead bindings expired. The question is:
if one of the bindings is valid and active, does the INVITE to the
address of record fail? That should not happen, SER should try those
which are available. If that does happen, that would be a shortcoming.
Can you verify that?

Thanks,

-jiri