[Home]

Summary:ASTERISK-00902: [patch] New ztmonitor "visual" output.
Reporter:exomorph (exomorph)Labels:
Date Opened:2004-01-23 12:54:42.000-0600Date Closed:2008-06-07 10:33:31
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) ztmonitor.c.v3.diff
Description:This patch is to help people understand what ztmonitor -v is showing. It also add some more information to the output.  See additional info for a sample output.

****** ADDITIONAL INFORMATION ******

./ztmonitor 1 -v

Visual Audio Levels.
--------------------
Middle is optimal. Use zapata.conf file to adjust if needed.
(# = Audio Level  * = True Average  ! = Max Audio Hit)

<----------------(RX)----------------> <----------------(TX)---------------->
################*#############     !   ####*#  !                          
Comments:By: zoa (zoa) 2004-01-23 13:47:11.000-0600

No errors, dunno if


<zoa> Exomorph: its very weird
<Exomorph> What do you mean?
<zoa> its like almost all the time at 100%
<zoa> even if i talk very quietly
<Exomorph> Hmmm  let me check that.
<zoa> it looks awesome
<Exomorph> Where is the *?
<Exomorph> the * on the bar graph that is.
<zoa> its floating around
<zoa> between 2/4 and 2/4
<zoa> sometimes goes up to 4
<Exomorph> Hmmmm
<zoa> but whenever i speak
<zoa> the # is at 100
<zoa> unless is whisper
<zoa> very softly
<zoa> in a way that people can't hear me for sure
<Exomorph> Hmmm   very intresting.  Let me take a look.
<zoa> then its not at 100%
<zoa> dunno how it is with the original
By: exomorph (exomorph) 2004-01-23 14:20:40.000-0600

New patch... Fixes the reported problem from zoa.  Also I forgot to mentiont hat this patch also fixes some buffer overrun's that were causing my server to hard crash. (So badly that I had to power reboot it!)

Whats left if to determin exactly where "optimal" levels are.  I'd stated "middle is optimal" only because that was told to me.  We need to verify this.

Also it would be nice to figure out a better "averaging" algorithm.  The reason is on Sip (and probably any other phone) zaptel reports alot of low numbers via the monitoring. This results in low averages over time and so false readings.
By: zoa (zoa) 2004-01-23 18:11:13.000-0600

Works sweet now, this is how the output looks like:

Visual Audio Levels.
--------------------
Middle is optimal. Use zapata.conf file to adjust if needed.

( # = Audio Level  * = Max Audio Hit )
<----------------(RX)----------------> <----------------(TX)---------------->
######      *                          ######### *
By: John Todd (jtodd) 2004-01-23 21:32:26.000-0600

Works for me.  The only thing is that it seems to "remember" the last values that were presented in the channel, so if I look at a channel that is currently hung up, it still may show a "bar" in TX or RX depending on if there was audio activity at the time the channel was last hung up.  This is not a major problem, IMHO, since the bars don't move for on-hook channels and it is obvious that there is nothing going on.

I think this is a reasonably useful patch.
By: zoa (zoa) 2004-01-23 21:37:57.000-0600

i found out the same, but i think that was in the original version too.
By: exomorph (exomorph) 2004-01-25 19:22:17.000-0600

jtodd,

Its supposed to remember the highest value for the last 5 unchanged displays it sends.  This means, that if the peak hasn't changed for 5 times, only then does it reset the peak to the current level.

This allows you to see more clearly what the peak level was over the last second or so.
By: Brian West (bkw918) 2004-01-28 00:46:56.000-0600

mark wants to make sure this does exactlyw hat it says it does.  I will be on the channel tommorow and testing this .. :P
By: exomorph (exomorph) 2004-01-28 16:55:17.000-0600

Latest patch (v3) removes the "middle is optimal" because we do not know what is the best setting for everyone.  Maybe after some research and lots of tests we can make some sort of conclusion - but not right now.

Also, this latest patch fixes another small bug or two from the old code. Mainly the tx and rx counters could not hold big enough numbers and would rollover.

Latest output from ztmonitor:


Visual Audio Levels.
--------------------
Use zapata.conf file to adjust the gains if needed.

( # = Audio Level  * = Max Audio Hit )
<----------------(RX)----------------> <----------------(TX)---------------->
By: Mark Spencer (markster) 2004-01-28 17:41:11.000-0600

Added to CVS
By: Digium Subversion (svnbot) 2008-06-07 10:33:30

Repository: dahdi
Revision: 303

U   trunk/ztmonitor.c

------------------------------------------------------------------------
r303 | markster | 2008-06-07 10:33:30 -0500 (Sat, 07 Jun 2008) | 2 lines

ztmonitor enhancements (bug ASTERISK-902)

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=303