[asterisk-bugs] [Asterisk 0015807]: rtt should be stored as double in struct ast_rtp_instance_stats

[Asterisk Bug Tracker]

The following issue has been ASSIGNED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15807 
====================================================================== 
Reported By:                klaus3000
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   15807
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 214938 
Request Review:              
====================================================================== 
Date Submitted:             2009-09-01 09:36 CDT
Last Modified:              2009-09-01 18:06 CDT
====================================================================== 
Summary:                    rtt should be stored as double in struct
ast_rtp_instance_stats
Description: 
Hi!

AFAIS member "rtt" in struct ast_rtp_instance_stats stored the RTT in
seconds, using an usigned int. 

As RTTs usually are below 0.5 (at least on earth and for VoIP useable
links) this member is useless as it is always 0.

Shouldn't that be changed to double?
====================================================================== 

---------------------------------------------------------------------- 
 (0109982) tilghman (administrator) - 2009-09-01 18:06
 https://issues.asterisk.org/view.php?id=15807#c109982 
---------------------------------------------------------------------- 
Given that the value is never actually set, how it is stored is kind of
irrelevant, don't you think?  I think it's actually meant to be stored in
number of milliseconds, but given that it's never actually set, it's not
really determined.

file:  should the field be removed? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-01 18:06 tilghman       Note Added: 0109982                          
2009-09-01 18:06 tilghman       Assigned To              tilghman => file    
======================================================================