Re: [OpenSER-Users] Interop dialog/sst - acc module to produce CDR for dialog-expired call

Hi Ovidiu Thanks for your response. I thought dialog together with sst it works already as demanded: With sst we re-INVITE and as long as this works fine, the dialog does not expire. If an endpoint breaks, the re-INVITE will not work properly (no answer), the session expires (after Session-Expire time) and the dialog module destroys the dialog (after default-timeout). The only problem I see now is that with destroying the dialog (which works already fine like this), no required actions are performed and can be enabled (BYE to both sides, or at least accounting flag). If it would be anyhow possible, to call this with the destruction of the dialog, the problem would be solved I think. For me, the BYE is not that much necessary. It might not cause any troubles if one endpoint breaks and the other is still running until somebody hangs up. But if I wanna account calls within one domain (only through OpenSER), I need to each started call assured an ending accounting tag. The worst is that the customer gets then default-timeout more accounted as he was online. Am I thinking in the right way or must this be solved differently? I think the dialog module provides already the timer, just the _actions_ (besides internal destruction of the dialog) are missing... Best regards Sebastian -----Original Message----- From: sip.nslu(a)gmail.com on behalf of Ovidiu Sas Sent: Tue 2/19/2008 19:13 To: Schumann Sebastian Cc: users(a)lists.openser.org Subject: Re: [OpenSER-Users] Interop dialog/sst - acc module to produce CDR for dialog-expired call Hello Sebastian, At this point in time, there's nothing you can do on dialog expiration. Take a look at the following patch request: http://sourceforge.net/tracker/index.php?func=detail&aid=1892203&gr… Regards, Ovidiu Sas On Feb 19, 2008 9:37 AM, Schumann Sebastian <Sebastian.Schumann(a)t-com.sk> wrote: