[asterisk-bugs] [Asterisk 0015386]: [patch] Milliwatt() is off by -11dbm

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15386 
====================================================================== 
Reported By:                rue_mohr
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   15386
Category:                   Applications/app_milliwatt
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.1.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-06-23 20:15 CDT
Last Modified:              2009-08-02 20:19 CDT
====================================================================== 
Summary:                    [patch] Milliwatt() is off by -11dbm
Description: 
Confirmed on asterisk 1.4.25.1 and 1.6.1.1 that the milliwatt is about
-11dbm 

Standard PC system, T100P T1 card, to Newbridge Mainstreet 3624
using dahdi-linux-complete-2.1.0.4+2.1.0.2
Debian kernel linux-2.6.28
measured with dbm meter from channelbank

its -11dbm at 1.000kHz, and at 1.004kHz

This can be confirmed because it worked perfectly on same hardware before
software upgrade ( kernel-2.6.15  asterisk-1.2.15  zaptel-1.2.13). 

suspect slinear<->ulaw conversion process, can't confirm.

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

---------------------------------------------------------------------- 
 (0108520) russell (administrator) - 2009-08-02 20:19
 https://issues.asterisk.org/view.php?id=15386#c108520 
---------------------------------------------------------------------- 
The issue wasn't actually reopened, but I'm not sure that it needs to.

Even though the commit message said the rev2 patch got committed, it
wasn't exactly that.  I modified the volume arg down to what was suggested
by the reporter from testing. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-02 20:19 russell        Note Added: 0108520                          
======================================================================