QOS and Video conference (skype, vsee) frusturations

Discussion in 'Tomato Firmware' started by stubish, Apr 2, 2013.

  1. stubish

    stubish Network Guru Member

    Hi all,
    I've set up QOS ala toastman, 60% outbound and inbound. Rest as standard. Any time I make a skypeout call or skypetoskype it cripples the outbound, the person I'm calling has no audio on their end (they hear the first two words and then nothing as QOS seems to 'kick in'). I turn QOS off and it's functional, but still has some troubles.

    Any suggestions on how to proceed? Is there a simpler way to prioritize video call traffic (given there's no filters to filter traffic like that). My mail outbound hog it torrents and possibly usenet (although that's not really an outbound thing).

    Any help would be apprecieated.... it's super frusturating.
  2. Monk E. Boy

    Monk E. Boy Network Guru Member

    Do your minimum values for all categories total up to more than 100%? Total for all Inbound minimums should never exceed 100%, ditto with Outbound.

    How fast of an internet connection do you have?

    I believe Toastman's default categories have Service for the first category and VOIP/Game as the 2nd category. Are you still using the second category for your VOIP (Skype) traffic?

    Unless something's changed recently, the Skype L7 filter doesn't effectively catch all Skype traffic, so what's probably happening is some of your traffic is being classified VOIP while the other traffic is being assigned bulk or P2P priority. You can verify this - during a Skype connection - by reviewing QoS -> View Graphics and looking in either P2P or Crawl for traffic from your Skype system.

    Until the L7 Skype filters are fixed the only way to ensure Skype works is create two rules - one for traffic to, and one for traffic from - your Skype system and make them use your VOIP category. This means setting up a static DHCP lease for that system.

    Ideally you should have all your port/packet-based QoS rules at the top and L7 rules bunched up together at the end, and these two rules (one for traffic to the system, the other for traffic from the system) should be right before L7 (the idea is to classify as much traffic as possible using minimally CPU-intensive port/packet filters, but skip hitting L7 filters for better VOIP performance).

    The fatal flaw with this setup is that this is effectively an "everything" rule for any traffic originating on or flowing to that system. If you run torrents on that system then there's a good chance they'll also end up flagged as VOIP. Normal web browsing should be prioritized appropriately since they're easily classified by port/packet.
  3. kyrios

    kyrios Networkin' Nut Member

    Maybe this help.​
    Default class 27 Skype Phone (deprecated) is disabled.​
  4. Monk E. Boy

    Monk E. Boy Network Guru Member

    BTW, if you want specific help with your rules and categories, post some screenshots. There's a lot of people on here with a good grasp of QoS but the problem is if you've customized QoS then we need to have a complete picture of what's been done, which is only possible by seeing the state the router's in.
  5. Elfew

    Elfew Network Guru Member

    I am interested too. I have default values of QoS, everything works good... but Skype has some problems with my QoS
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice