[OpenSIPS-Devel] [ opensips-Feature Requests-3603588 ] RTPPROXY timeout event

SourceForge.net noreply at sourceforge.net
Mon Mar 11 17:25:19 CET 2013

Feature Requests item #3603588, was opened at 2013-02-06 09:24
Message generated for change (Comment added) made by vladut-paiu
You can respond by visiting: 

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: dexteruk (dexteruk)
Assigned to: Nobody/Anonymous (nobody)
Summary: RTPPROXY timeout event

Initial Comment:
For the purposes of being able to make informed decisions about the voip providers you work with.  It would be nice to be able to have an event for RTPPROXY media timeout, so you can see that a BYE was never received and instead your opensips/rtpproxy timed the call out and passed the BYE to both legs of the call, so this could be logged in the acc.

For example, with the dialog timeout-avp when this happens you can create and local route 

        if (is_method("BYE") && $DLG_dir=="UPSTREAM") {

                acc_db_request("200 Dialog Timeout", "acc");


So when this event happens, in the acc you see a 200 Dialog Timeout



>Comment By: Vladut-Stefan Paiu (vladut-paiu)
Date: 2013-03-11 09:25


I have just added a new PVAR, $DLG_end_reason , in OpenSIPS trunk, which
will tell you the reason for the dialog termination.

See http://www.opensips.org/html/docs/modules/devel/dialog#id295868

Best Regards,


Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2013-02-07 03:58

The idea will be to add a new variable to be provided by the dialog module.
This variable will contain a dialog termination reason string and will be
automatically published by dialog module when a dialog is terminated. So it
will be available in request route after handling a BYE for a dialog or in
local route when a dialog is terminated. 

In local route, it will publish (via internal dlg_end_dlg) if the
termination was becuase of MI function, of session timeout or RTP timeout.



You can respond by visiting: 

More information about the Devel mailing list