Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[naughticl]

I haven't yet hit the right setup for QOS so that VoIP works without problems. I have the VOIP box given #1 priority and torrent apps given #250 priority. But still, phone calls are garbled until torrents are shut down. Isn't this what QOS is supposed to manage?

For the IP assigned to VoIP (Vonage) box, it's set to priority 1, Protocol Both, local port range 0 - 65535, remote IP range 1 - 255, remote port range 0 - 65535. And it's activated.

Is there any way to improve the QOS performance beyond this?

thnx

[dblagent]

If possible with your Vonage box, Put the modem, then the Vonage device, then the router.  Then no matter what the Vonage device has priority as the router is behind it.  Works the best in every setup I have ever tried regardless of router.

[naughticl]

Interesting idea, but the D-Link Vonage box has only one network port. So how could it go first?

[rrance]

I have the same setup you do.  Don't use QOS settings.  I tried and had the same results.  I did a little digging and found if you use the wish configuration it works great!  Here are my settings: Priority (Voice<VO>), protocol select both, Host 1 range 0.0.0.0 to 255.255.255.255,host 1 port 5061 to 5061, Host 2 IP randge 0.0.0.0 to 255.255.255.255, host 2 port range 10050 to 10061.

 Hope this helps...

[buckzor]

What do you mean the wish configuration? 

[Lycan]

Guys Wish is ONLY FOR WIRELESS clients.

[funchords]

QOS can't make a pint glass hold a gallon of milk -- no matter how you rearrange the liquid, some is going to spill.  So if your network traffic is insane, using QOS will just help you automate the insanity -- it won't cure it.

My advice:  Don't set ANY rules.  Just turn on Auto-Classification in QOS Engine and it will treat Vonage just right.  No fuss, no muss.

Think of Priority as a slider bar on an equalizer.  You don't tend to run with these at the extreme top or bottom.

If you do need a rule to keep some heavy bandwidth usage (not Vonage) ahead of the rest, then add the rule with a priority of 100.  This will keep the affected traffic biased ahead of other traffic without starving the other traffic (which defaults at priority 128 and moves toward 200 the heavier it is). 

Settings near 1 and 255 cause starvation or near starvation.  No network application is designed to work in those conditions. 

[EddieZ]

Agree. 255 works well to keep the kids' PC's at a distance in the LAN though