[OpenSIPS-Users] Accounting BYE response

David Villasmil david.villasmil.work at gmail.com
Fri Sep 7 17:51:49 EDT 2018


I think you should take care of this on your gateway. For example, using
freeswitch or asterisk, you can check for rtps, and when the other end
stops sending rtps for 30 seconds (configurable) it will tear down the call
properly.

Unless you're using a rtp-proxy with opensips which can do this (most can),
that's the way to do this. Anything else is just duct-taping.

My opinion after 20 years on voip.

Hope that helps.

David

On Fri, Sep 7, 2018, 21:43 Ben Newlin <Ben.Newlin at genesys.com> wrote:

> Hi,
>
>
>
> I am having an issue trying to add values to accounting based on the
> response to the BYE request.
>
>
>
> We use the dialog timeout mechanism to terminate long calls in our system.
> In some cases, these are “valid” calls that remained connected for too long
> due to some error elsewhere in the application. But sometimes one or both
> ends of the call believe they have disconnected, but we did not receive or
> process the disconnect, due to a malformed BYE or a network disruption. In
> these cases, when the Dialog timeout is reached and OpenSIPS generates a
> BYE to both parties, they will respond with a 481.
>
>
>
> What I want is to set a CDR flag on receipt of that 481 to indicate that
> there was an error and the calculated call time may not be correct. But it
> seems that any accounting flags set after the BYE is sent are not honored.
> Is there any way to accomplish this?
>
>
>
> This is my attempt:
>
>
>
> failure_route[local_failure]
>
> {
>
>   $acc_extra(disconnect_error) = "true";
>
> }
>
>
>
> local_route
>
> {
>
>   t_on_failure("local_failure");
>
> }
>
>
>
> Ben Newlin
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20180907/9b91687c/attachment.html>


More information about the Users mailing list