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 21:43:48 +0000	[thread overview]
Message-ID: <4213BE94.9040802@wildgooses.com> (raw)
In-Reply-To: <20050216001928.D7B28408D@outpost.ds9a.nl>


>My calls are only choppy on the outbound side, ostensibly because of the
>bandwidth disparity--I have 3Mb down, but only 256Kb up.  When I'm not
>sending anything out, I'm good.  When I load up the outbound however, I not
>only lose the ability to start a *new* ssh connection to my Linux box
>(Xeon), but all interactivity is destroyed (DNS lookups, etc) and my Vonage
>calls are worthless (though I can still hear the caller perfectly).
>
>I'm not discounting the possibility that my MARKs are getting stripped or
>otherwise re-mangled (so to say) in my excessively complex iptables script.
>Up until this attempt at learning QoS, I've never had a need for MARKs, so
>I'm going to sit down and work through my script on that end of things too.
>  
>

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....

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 21:43 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 [this message]
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=4213BE94.9040802@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.