I'm a techie. I have a 2003 AD Domain setup at home. I'm using RRAS to provide NAT to my lan. I didn't like the idea of installing the V-Portal in between my cable modem and RRAS box. Which led to a small problem. QoS. If the phone adapter is used behind a router (as in my case) the quality of service provided by the phone adapter doesn't do any good.
I host web, email, and an occasion game server on this connection. Any congestion on uplink is very bad for voip. You'll get echos, you'll sound choppy to the person on the other end, and/or the person on the other end will get an echo. I knew about QoS, never had the oppurtinity to implement it until now. I hopped on google, found some stuff, but nothing that really helped (hence why I'm writing this up). I found about tcmon that would allow me to monitor QoS flows and filters, but it wouldn't let me create a new flow or filter. You'll want to get the resource kit and use this to monitor that traffic is going through your flows.
I don't know how, but I stumbled upon a free windows service called wintc. It's pretty easy and striaght forward to configure that allows you to create QoS rules. QoS rules don't persist after reboots, so you need a service to create em. One snag that I did run into though that is worth mentioning is the fact that if you are using NAT, you cannot create rules based on source addresses of NAT'd computers. The rules have to be based on source/dest ports or dest ips.
Here's the wintc.conf file I used. Do note that you'll want these rules to apply to the network card that has the external ip addresses with the default_netif option (read the readme that came with wintc to figure out which interface # to use).
Code: Select all
default_netif = 1 define_flow = flow-prio 19K prio=1 define_filter = cl-von10k dstport=10000/16 proto=udp define_filter = cl-vonrtp dstport=2740/10 proto=udp define_filter = cl-vonrtp2 dstport=2780/10 proto=udp assign_filter = cl-vonrtp2 flow-prio assign_filter = cl-vonrtp flow-prio assign_filter = cl-von10k flow-prio
Hopefully someone will find some use of this info.