[asterisk-bugs] [Asterisk 0015386]: [patch] Milliwatt() is off by -11dbm
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Aug 2 16:51:35 CDT 2009
The following issue has been UPDATED.
======================================================================
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 16:51 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.
======================================================================
----------------------------------------------------------------------
(0108519) jsmith (administrator) - 2009-08-02 16:51
https://issues.asterisk.org/view.php?id=15386#c108519
----------------------------------------------------------------------
Re-opening and re-assigning back to Russell at original poster's request
(on IRC), as the patch apparently wasn't 100% correct.
<rue_mohr> russellb, you know the r2 patch of my issue did NOT resolve the
problem?
<rue_mohr> kinda worred, cause it looks like it got smunched into a
realease
<rue_mohr> which isn't good, it outputs 1.2dbm, not 0
Issue History
Date Modified Username Field Change
======================================================================
2009-08-02 16:51 jsmith Note Added: 0108519
2009-08-02 16:51 jsmith Description Updated
2009-08-02 16:51 jsmith Additional Information Updated
======================================================================
More information about the asterisk-bugs
mailing list