[OpenSIPS-Users] [RFD] dialog expire event in dialog module

[Alex Massover]

Hi!

Great idea! You probably know better about implementation but the following functionality will be usefull:
a) send BYE (optionally)
b) if BYE is sent to trigger accounting.

--
Best Regards,
Alex Massover

-----Original Message-----
From: users-bounces at lists.opensips.org [mailto:users-bounces at lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Monday, October 06, 2008 12:30 PM
To: users at lists.opensips.org; devel at lists.opensips.org
Subject: [OpenSIPS-Users] [RFD] dialog expire event in dialog module

Hi everybody,

I want to bring into discussion an older topic as we need to take a
decisions on this - it is what to do when a dialog gives timeout in
dialog module.

Right now, nothing is done. The dialog module simply stops monitoring
the dialog without taking any action.

There were several demanded actions to be done, as:
    - accounting (to be able to account hanged calls)
    - send BYE in both directions
    - etc.....

Of course, we are looking for a mechanism to cover as many cases as
possible and not to hardcode one of them.

So, I would like to get some feedback on:
    1) what are the actions that could be done when a dialog gives timeout
    2) how the implementation should look like?

For 2), we already have some ideas:
    A) use bitmask flags to select the action to be done at dialog
timeout event.
    B) set a route to be called when the dialog timesout


So, ideas and comments are welcomed.

REgards,
Bogdan

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



******************************************************************************

 This footnote confirms that this email message has been scanned by Jajah Inc. Mail system for the presence of malicious code, vandals & computer viruses.

******************************************************************************




******************************************************************************
 This footnote confirms that this email message has been scanned by Jajah Inc. Mail system for the presence of malicious code, vandals & computer viruses.
******************************************************************************