All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] VOIP Challenges...
Date: Wed, 16 Feb 2005 14:58:27 +0000	[thread overview]
Message-ID: <42135F93.6050509@wildgooses.com> (raw)
In-Reply-To: <20050216001928.D7B28408D@outpost.ds9a.nl>


> I'm new to QoS, so please be gentle (and yes, I've RTFM, though I 
> don't understand every bit of it)
>  
> Here's the thing; I've tried several scripts--simple and complex--for 
> classifying my Vonage traffic into a high-priority queue, but no 
> matter what I do it doesn't seem to work.  Right now I'm using the HTB 
> script I'll include below, which is a mashing together of several 
> scripts I've found along with a lot of the LARTC HOWTO stuff.  Bottom 
> line; if I load up my *outbound* connection and then try to make a 
> Vonage call, my voice is so chopped up at the other end that noone can 
> understand me.


Some others have pointed out a few errors, but can I just check whether 
it's only uplink that gets choppy?

Obviously first of all monitor your qdiscs to make sure traffic is being 
classified as expected, but after that do some testing on your VoIP app.

I tested www.sipgate.co.uk on my PC based softphone and frequently got 
choppy sound for the first 30 secs of the call and then it settled 
down.  Curiously changing to one of these hardware devices, a Budgettone 
in my case, and now the quality is perfect in both directions.  No 
changes in qos settings between the two...

Now, I haven't debugged this further, but I think the actual voip 
settings in the device may help/hinder when there is congestion.

Post some more info on your setup

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

  parent reply	other threads:[~2005-02-16 14:58 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 [this message]
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
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=42135F93.6050509@wildgooses.com \
    --to=lists@wildgooses.com \
    --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.