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

Ovidiu Sas osas at voipembedded.com
Thu Feb 21 07:34:03 CET 2008


Hello Sebastian,

When the dialog expires, there are no actions taken by the dialog module:
 - no BYE is sent,
 - no accounting is logged.

A dialog can be terminated via an MI command, and that one will
generate BYEs on both ends, but no accounting.

The sst module will enforce periodic re-INVITEs if at least one of the
participants has support for SIP session timers.
If SIP session timers is not supported by at least one of the
participants, then no periodic re-INVITEs will occur and the dialog
timer will not be restarted.


Hope this helps,
Ovidiu Sas

On Wed, Feb 20, 2008 at 5:24 PM, Schumann Sebastian
<Sebastian.Schumann at t-com.sk> wrote:
> 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 at gmail.com on behalf of Ovidiu Sas
>  Sent: Tue 2/19/2008 19:13
>  To: Schumann Sebastian
>  Cc: users at 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&group_id=139143&atid=743023
>
>
>  Regards,
>  Ovidiu Sas
>
>  On Feb 19, 2008 9:37 AM, Schumann Sebastian <Sebastian.Schumann at t-com.sk> wrote:
>  >
>  >
>  > Dear all
>  >
>  > I am looking for a possibility to somehow assure, that the accounting CDR
>  > produced will not be infinite, if a call is interrupted without sending a
>  > final BYE.
>  >
>  > I thought to do it like this:
>  >
>  > Use SST module to create certain time limit (e.g N) for a session. Use
>  > dialog module to cut dialog after certain time expired (e.g. 2N). As long as
>  > SST creates active sessions (i.e. the client is alive) the dialog does not
>  > expire, if the call is interrupted, the dialog expires worst case with 2N
>  > time accounted.
>  >
>  > The problem is, I cannot generate CDR to stop accounting for a certain call
>  > where the dialog expired. Is this possible to do in a way?
>  >
>  > Thanks for your help.
>  >
>  > Best regards
>  > Sebastian
>  > _______________________________________________
>  > Users mailing list
>  > Users at lists.openser.org
>  > http://lists.openser.org/cgi-bin/mailman/listinfo/users
>  >
>  >
>
>




More information about the Users mailing list