All of lore.kernel.org
 help / color / mirror / Atom feed
From: vincent perrier <vincent-perrier@club-internet.fr>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] VOIP Challenges...
Date: Thu, 17 Feb 2005 20:19:43 +0000	[thread overview]
Message-ID: <1108671583.4160.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050216001928.D7B28408D@outpost.ds9a.nl>

Le mercredi 16 février 2005 à 19:40 -0800, Some Clown a écrit :
>  
> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On
> Behalf Of Ed Wildgoose
> Sent: Wednesday, February 16, 2005 1:44 PM
> 
> Debug this first.  It's not hard to sit and watch the byte counters scroll
> up.  If any traffic goes to queues that you don't expect then you know
> something is wrong.
> 
> By the way, your other errors indicate that you don't have the correct
> kernel modules loaded....
> 
> As I said though, my softphone on the PC kept going stuttery on the uplink
> even though QOS was working. (And only the uplink, downlink was perfect).
> With the hardware phone it's perfect even when the link is under stress.
> I'm not sure exactly why, but I did notice that after a few mins the
> softphone usually got it's act together so I suspect it's a default delay
> thing which needs to get settled down to the level of jitter on the line....
> -----Original Message-----
> 
> Well, the byte counters seem to be doing what they should... When using a
> 'tc -s class show dev eth0' over and over again <grin> 

To have a real time graphical monitoring of your qdiscs/class without
using tc -s class show dev eth0, you can try the last version of the 
qdisc monitoring tool at http://rawsoft.org


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-02-17 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  0:18 [LARTC] VOIP Challenges Some Clown
2005-02-16  0:27 ` rsenykoff
2005-02-16  0:40 ` Dan Cox
2005-02-16 14:58 ` Ed Wildgoose
2005-02-16 19:55 ` Some Clown
2005-02-16 21:43 ` Ed Wildgoose
2005-02-17  3:40 ` Some Clown
2005-02-17 14:07 ` Ed Wildgoose
2005-02-17 20:19 ` vincent perrier [this message]
2005-02-17 22:11 ` Jason Boxman
2005-02-18  0:22 ` Some Clown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1108671583.4160.3.camel@localhost.localdomain \
    --to=vincent-perrier@club-internet.fr \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.