Friday, February 27, 2009

QOS Questions and Answers

If we are completely in control of the outgoing packets, then the router / modems only way to mess up the outgoing is with a big-old-buffer.

So you starve the buffer by sending less in than it can transmit out. You keep lowering how much you send out until you get the desired results.

If you give voice absolute priority and limit outbound to your expected voice bandwidth, nothing is going to buffer.

Downlink is the same way only you don't really have any control. You still want the ISP's buffers empty.

So you set the incoming bandwidth below it's rated speed all the way down to only allow expected voice. At some point TCP traffic is so disrupted that all the senders are in retry mode backing down expected throughput until there is no buffering.

Doesn't work so well on HTTP because every little bit of traffic is it's own connection.

So when you completely disrupt the TCP traffic enough that the voice sounds good, the user is convinced to get another DSL line so his data gets through.

Or you can simply order another DSL for voice, get a cup of coffee, and it all works.

We have customerss changing their private LAN to voice only and they are ecstatic?

All voice and no data makes your ISP connection have QOS. :-) Cheers :-)

No comments:

Post a Comment