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: Thu, 17 Feb 2005 14:07:52 +0000	[thread overview]
Message-ID: <4214A538.2080502@wildgooses.com> (raw)
In-Reply-To: <20050216001928.D7B28408D@outpost.ds9a.nl>


>I'm very
>tempted to just go back to my Cisco gear for the QoS and leave this stuff
>be.
>
>The only last lucid--somewhat--thought that I had was that I might need to
>slow down my eth1 connection, which is to the switch, and hence all devices
>including my desktop--the one which hogs all bandwidth--because maybe the
>Vonage box can't get through.  Only trouble with that theory, though, is
>watching in Ethereal, the SIP packets come in with no delay... It's the RTP
>stuff that gets hung up on the way out.
>  
>

I think you need to backup a bit and do some more debugging.  You need 
to discover if your QOS is working or not on your data.  If it is, then 
remember that you have full control of the outgoing connection so no 
queuing should ever occur if you don't want it o.  If your packets are 
being held up then change your packet marking so that they dont.  You 
are going to have the same problems on your CISCO box I should think if 
it's just a config problem.

The other issue though is that you might genuinely be releasing packets 
too fast and getting queuing on your modem buffer.  Try turning down the 
outlet speed quite a lot, say 50% and see how you get on.  Debug that 
part first before turning it up again.

Also try to turn on some kind of QOS bits with the vonage router so that 
it's a little easier to mark your packets.  Use something like ethereal 
or tcpdump to check that everything really is going to and from the 
addresses that you think it is.

Please also trim your replies when sending to mailing lists...

Good luck

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-17 14:07 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 [this message]
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=4214A538.2080502@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.