[prev in list] [next in list] [prev in thread] [next in thread] 

List:       asterisk-bugs
Subject:    [Asterisk-bugs] [Asterisk 0009622]: CHANNEL QOS functions do not
From:       noreply () bugs ! diguim ! com
Date:       2007-06-29 18:08:21
Message-ID: 1615d6f77d6b2b51c48d5e7db4eba481 () bugs ! digium ! com
[Download RAW message or body]


email_notification_title_for_status_bug_resolved 
====================================================================== 
http://bugs.digium.com/view.php?id=9622 
====================================================================== 
Reported By:                jtodd
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   9622
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 62039 
Disclaimer on File?:        Yes 
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             04-27-2007 18:02 CDT
Last Modified:              06-29-2007 13:08 CDT
====================================================================== 
Summary:                    CHANNEL QOS functions do not report stats after
hangup
Description: 

Depending on what side of a call hangs up first, the CHANNEL(rtpqos...)
features do not return with any data.  This is related to
http://bugs.digium.com/view.php?id=9610  however it seems to have the
opposite behaviors.

Upon examination, it seems that as soon as the channel is freed (goes to
"h" for whatever reason) then the CHANNEL function cannot report the
summary data.  This makes it impossible to collect data on channels that
hang up, because we're already at "h" by the time we try to collect data
out of the CHANNEL function.

Proposed solution: upon channel hangup, store the last RTP QOS data in the
CHANNEL function and leave it there until the dialplan exits.  It does not
appear to be harmful to do this, and makes post-hangup collection of the
data possible.  The "state" item of the function can be used to ensure that
the call is terminated if that is required, but it is left to the
discretion of the dialplan author.

====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-29-07 13:08  file           Note Added: 0065932                          
======================================================================


_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

Asterisk-bugs mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-bugs

[prev in list] [next in list] [prev in thread] [next in thread]