All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riccardo Losselli <riccardo@e4a.it>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Info about VoiP Qos
Date: Sun, 23 Jan 2005 20:54:53 +0000	[thread overview]
Message-ID: <41F40F1D.6030507@e4a.it> (raw)
In-Reply-To: <41F28A25.1030108@e4a.it>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Thanks again to Jason..
i plotted the classes and they are as i wished them to be..
I also plotted the traffic, while heavily using the link.
I gave Voip a 100Kbit rate (it need between 80 and 90some) and it worked.
There are no visibile spikes (traffic si not exactly flat, but
variations are minimal) and stay betwen 80Kbps and 90some.
So it should be fine.. traffic is prioritarized, prio 1, while the other
traffic is 3 or more..
Leaf classes are sfq perturb 10
I still hear the pops..
If it can be a useful hint, the problem appears only when i'm called,
not when i call (i use two diffent servers when making calls and receiving).
The only one who hears the pops i the one on the POTS phone that is
calling me, i do not hear any pop (but i guess it's because my link is
saturated upstream only)
At first i thought that it was a problem of the server used to call me.
but if I the almost zero the non voip traffic the pops disappear...
Will test more...

Bye,
Ricky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB9A8dwfVi6Z6cQK8RAmg2AJ9Wa7bonOslMsRm6sInLrKA438gHgCdFcge
cYm/fGsXo7XJ5KkHLXD+Mo0=FzbA
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-01-23 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-22 17:15 [LARTC] Info about VoiP Qos Riccardo Losselli
2005-01-22 18:11 ` Jason Boxman
2005-01-22 20:03 ` Riccardo Losselli
2005-01-23 20:54 ` Riccardo Losselli [this message]
2005-01-24 22:32 ` Ed Wildgoose
2005-01-25  9:47 ` Riccardo Losselli

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=41F40F1D.6030507@e4a.it \
    --to=riccardo@e4a.it \
    --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.