TomatoUSB

I was having some issues with choppy sound so I decided to try to prioritize traffic to the VOIP ATA device.

The Device IP on the local network is 192.168.1.181, and SOME of the ports involved are 5060 and 5061 (I'll add more ports later.)

Is this all I need to enter into the QOS Classification section?

From 192.168.1.181
TCP/UDP
Src Port: 5060,5061

I've also moved it up the queue list so I'm assuming that it is more higher prioritized.

I'm a little confused with all the Source and Destination information, but that's all the information I'll assume that I need? Do I even need to specify an IP address if I've specifically describe the ports?

Your VOIP protocol may be something besides TCP/UDP. A pair of rules that match "To" and "From" the IP address would be best. Be sure the device is programmed for a static IP address or use Static DHCP reservation in the router.

Putting the rules at the top of the list is only part of the prioritization process. You also need to be sure nothing else has a category with more bandwidth, and be sure none of the other categories go up to 100%. For the bandwidth of the VOIP class make all fields = 100%.

totally agree… the ports may not work too well sometimes, for example, I assigned Google voice ports for VOIP, then a lot of other devices try to steal those ports for something else!

Instead of IPs, is there anyway to use domain name or host name? eg, *.google.com with ports in QOS settings? I found most of VOIP has multi servers and I don't know how many servers IP I should open for them.. and they are so far away from each IPs.. I guess because they are in different countries…

thanks.

Oh wait, I think I figured it out. The IP address you mentioned in your QOS rule was the IP address of the VOIP device on my network. Smart !!

Yes, I keep a high number so that it doesn't get assigned to anything else.

I'll also add a rule for a TO rule, and change it to any protocol.

The other idea I have is to add it to the bandwidth limiter, but assign it a high UL, however, I don't want that bandwidth completely reserved 100% of the time, only when making calls. Not sure if that would be the best idea.

…add it to the bandwidth limiter, but assign it a high UL, however, I don't want that bandwidth completely reserved 100% of the time, only when making calls…

The QOS rule is what you need. The 100% reservation will not prevent bandwidth usage by other services unless VOIP wants all 100%. By allocating the 100% reservation to VOIP you ensure that VOIP will never be throttled, but in practicality it would not likely ever need or take a very large percentage of your available bandwidth.

I created a classification for the VOIP Device using To/From the IP of my ata device. Put it into a high classification group (voip, QOS rule 80kbps-120kbps) and High priority (5)

Classification RulesMatch Rule    Class    Description    #
TCP/UDP
Dst Port: 53
Transferred: 0 - 10KB    Service    DNS    1
TCP/UDP
Dst Port: 37
Transferred: 0 - 10KB    Service    Time    2
UDP
Dst Port: 123
Transferred: 0 - 10KB    Service    NTP    3
TCP/UDP
Dst Port: 3455
Transferred: 0 - 10KB    Service    RSVP    4
From 192.168.1.181    VOIP/Game    VIOP.ms    5
To 192.168.1.181    VOIP/Game    Voip.ms    6

Outbound Rates / LimitsMax Bandwidth Limit     kbit/s (Set to measured bandwidth less 15-30%)

Service        19 - 380 kbit/s
VOIP/Game        91 - 152 kbit/s
WWW        76 - 380 kbit/s
Remote        19 - 380 kbit/s
Media        19 - 190 kbit/s
Mail        19 - 266 kbit/s
Messenger        3 - 266 kbit/s
FileXfer        3 - 266 kbit/s
P2P/Bulk        3 - 114 kbit/s
Crawl        3 - 19 kbit/s

Inbound Rates / LimitsMax Bandwidth Limit     kbit/s (Set to measured bandwidth less 15-30%)

Service        1,300 - 26000 kbit/s
VOIP/Game        1,300 - 7800 kbit/s
WWW        5,200 - 23400 kbit/s
Remote        1,300 - 26000 kbit/s
Media        1,300 - 10400 kbit/s
Mail        1,300 - 15600 kbit/s
Messenger        1,300 - 15600 kbit/s
FileXfer        1,300 - 15600 kbit/s
P2P/Bulk        1,300 - 5200 kbit/s
Crawl        260 - 1300 kbit/s

It works fine, except for heavy uploading. For some reason, I still have jittery and choppy outgoing voice during heavy upload periods.

I think that I've used the proper build (tomato-E900-NVRAM64K-1.28.0502.1MIPSR2Toastman-RT-N-Std) and configured the rules properly.

I think the bottleneck is the 300mhz processor of the router, and my 512kb (at best) upload?

For some reason, I still have jittery and choppy outgoing voice during heavy upload periods.

If you would program it the way I suggested then it would work properly.

Ok, I reread your original post. I was afraid that setting it to 100% would somehow take from another class, but I have WWW originally set to 100% and my voip still 'worked' so I don't know why I was so hesitant.

Here are my revised outgoing settings.

Outbound Rates / LimitsMax Bandwidth Limit     kbit/s (Set to measured bandwidth less 15-30%)

Service        19 - 361 kbit/s
VOIP/Game        91 - 380 kbit/s
WWW        76 - 342 kbit/s
Remote        19 - 342 kbit/s
Media        19 - 190 kbit/s
Mail        19 - 266 kbit/s
Messenger        3 - 266 kbit/s
FileXfer        3 - 304 kbit/s
P2P/Bulk        3 - 266 kbit/s
Crawl        3 - 19 kbit/s

Basically voip is set at 100% of the 380

Cool story broux.