Searching the archives there has been some discussion about the need for QOS routing on a mixed voice data broadband like ADSL. Has anyone run * on a production system with voice and data. Can anyone share what has to be done to secure the voice and throttle back the data? If a linux router is need can that run on the * box to reduce cost? All help is gratefully received, so I can plan a multi-office rollout. Fred __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/
fred alexander <fredvoip@yahoo.com> writes:> Can anyone share what has to be done to secure the > voice and throttle back the data?Many routers allow you to prioritize certain types of traffic -- effectively letting the packets "jump the queue". If you strictly prioritize the voice packets over data packets, you'll probably do quite well. -- Perry E. Metzger perry@piermont.com
fred alexander wrote:>Searching the archives there has been some discussion >about the need for QOS routing on a mixed voice data >broadband like ADSL. > >Has anyone run * on a production system with voice and >data. > >Can anyone share what has to be done to secure the >voice and throttle back the data? > >If a linux router is need can that run on the * box to >reduce cost? > >All help is gratefully received, so I can plan a >multi-office rollout. > >Fred > > >You can't use QOS on the internet.. Its just not supported.. *IF* your ADSL router supports QOS it will only be effective on outbaound traffic.. Inbound would still come in as it always has..
> -----Original Message----- > From: Perry E. Metzger [mailto:perry@piermont.com] > > > fred alexander <fredvoip@yahoo.com> writes: > > Can anyone share what has to be done to secure the > > voice and throttle back the data? > > Many routers allow you to prioritize certain types of traffic -- > effectively letting the packets "jump the queue". If you strictly > prioritize the voice packets over data packets, you'll probably do > quite well.For Cisco routers, look at the fair-queuing modes (but stay away from weighted fair queuing as that can have a deleterious effect on VoIP traffic). Under Linux, check out http://lartc.org/ which deals with configuring routing under Linux with traffic shaping. For asymmetric configurations such as Cable/DSL, if you are willing to lower your download by and upload speeds by a bit, you can get nominal quality even with large downloads that would normally saturate your link. Under Cisco, look to setup multiple queues at different priorities. These can then be assigned to the WAN links (serial, etc). For Linux, look at http://lartc.org/howto/lartc.cookbook.ultimate-tc.html. That's what I use at home with my Vonage connection (soon to be a trunk line to my * install :). Drops download speeds from 1.5Mbit to about 1.4Mbit and uploads go from 256Kbit to 210Kbit. You're on your own across the Internet as a whole, but in the past 3 years I have seen very little to no tier 1 or tier 2 provider congestion, including trans-atlantic connections. YMMV, IMHO, etc. Regards, --- Gavin
> Has anyone run * on a production system with voice and > data.Working on it. Mixed results so far.> If a linux router is need can that run on the * box to > reduce cost?Outgoing is easy -- use lartc.org's script and do a little customization to taste. My biggest problem has been incoming and my upstream ISP (MCI) -- it seems I get some pretty nasty ping times just going across the T1... 4-7ms normally but jumps to 200 on occassion. That's from my router to theirs... nothing goofy, traffic averaging around 400kbps. In order to try and keep the upstream router from queueing up a shitload of traffic and bogging down VOIP, I have a strict policing policy in place on my s0/0: rate-limit input access-group 105 128000 65536 65536 conform-action set-prec-transmit 5 exceed-action set-prec-continue 0 rate-limit input 1408000 8000 8000 conform-action transmit exceed-action drop Basically ACL105 is my VOIP ACL. Anything matching it under 128kbps should get through without trouble (and get top precedence going through the router). Everything not matching that, or exceeding that gets shaped to 1408kbps. That SHOULD keep the upstream router from plugging the link and so far it seems ... alright. Not stellar, but alright. I'm sure if I could convince them to do something similar on their end it would be a LOT better. I'm using LLQ on this 2610 which is what Cisco recommends for voice-type traffic. My policy mapping looks like this: class-map voice match access-group 105 policy-map policy1 class voice priority 96 class class-default fair-queue basically I'm giving anything matching my voice class 96kbps guaranteed on outgoing, and letting everything else fight for what's left. Regards, Andrew
hi fred, i don't know if this question has been already answered... i haven't tested it whit asterisk YET, (i have to) check the following links: http://luxik.cdi.cz/~devik/qos http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/ADSL-Bandwidth-Management-HOWTO.html and tell me if you have found a solution -- santiago jos? ruano rinc?n administraci?n servidores y servicios de internet red de datos universidad del cauca http://www.unicauca.edu.co/~santiago/llaves/santiago_pub.asc hay 10 tipos de personas, las que entienden binario y las que no