John Voigt wrote:
> ----- Original Message -----
>>It is actually my question. No did not manage to setup Traffic Shaper for
>>VoIP, because I do not know what to do. I wrote this to get some help with
> 1. Go into traffic shaper.
> 2. Create 2 pipes - one inbound and one outbound both bigger than your
> actual bandwidth.
> 3. Create 4 queues 2 inbound and 2 outbound (using pipes above) make 1 in
> and 1 out a higher weight that the others
> 4. Create rules to pass your VOIP traffic through the higher weight queues
> 5. Create rules to pass everything else through the other queues
> Hope that helps,
Sorry for budding in, but I was wondering:
Why "both bigger than you actual bandwidth"?
I would have suggested "just a tad smaller than you actual (measured)
bandwidth", in order to avoid queue congestions in other WAN devices
(ie. broadband modem, ISP routers etc.) which (AFAIK) will otherwise
interfere with the shaper, but perhaps I'm missing something here (in
which case I need to change my own shaper config!)
P.S. Ulrich: The suggested configuration gives you dynamic shaping
(ie. when not using VoIP you can use the full bandwidth for other
things). If this does not work satisfactory for you, you can try a
static shaping config instead (where you permanently set aside part of
your bandwidth for VoIP, which then can NOT be used by anything else,
even if you don't use VoIP), which will typically provide a more
stable allocation of bandwidth to your VoIP.
To do so, you must make two queues (for each direction), one with the
bandwidth you want to set aside for VoIP, and one with the remaining
bandwidth (actual minus VoIP). You should then change the VoIP queue
to go to the VoIP pipe and the "other" queue to go to the "remaining"
pipe. The queue weights will not matter in this config, and you should
be able to just leave the rules as they were (since the queues are the