[OpenSIPS-Users] destroy dialog on transaction timeout and load balancer

[Bogdan-Andrei Iancu]

Hi Bobby,

Form dialog state machine point of view, an dialog without 200OK ACK is 
ok, it will not timeout it. So, I see 2 future solutions:

    1) we change the code so that (optional) timeout and dialog 
termination will be done for missing ACK also

    2) make a small shell script that takes the list of dialogs 
(opensipsctl fifo dlg_list), greps for the dialogs in CONFIRMED BUT NOT 
ACKED state and if lifetime longer than X sec, it terminates the dialog 
via "opensipsctl fifo dlg_end_dlg"

Regards,
Bogdan

Bobby Smith wrote:
> Is there an easy way/example from a scripting perspective to check if 
> a dialog's status is 3 (not received an ACK yet), after a certain 
> period of time, time out ONLY dialogs in this state?
>
> I've identified a situation where, if the UAC goes unresponsive, and 
> never sends an ACK, we will eventually stop retransmitting the 200 OK 
> to this but the dialog will remain established in memory.  Because of 
> this, the load balancer resources list becomes highly inaccurate over 
> time.  I'm hesitant to set the dialog default timeout flag, because 
> there are certain situations where a long call (6 hours +) could 
> occur, and we need resource accuracy to be < 1 hour ish.
>
> Thanks,
> Bobby Smith
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


-- 
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
www.voice-system.ro