Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

QOS for WhatsApp

This thread has been viewed 8 times
  • 1.  QOS for WhatsApp

    Posted Aug 22, 2017 04:09 AM

    Hi,

     

    Currently I've succesfully implemented QOS for Skype4B and Facetime on both a controller-based and IAP environment, based on the Aruba user guide documentation which is very helpfull.

    As lots of users within the company are using Whatsapp, I want to implement QOS for this app as well.

     

    Unfortunately I haven't been able to find anything on this in the Aruba documentation.

    After some investigation on the internet, I found out that WhatsApp is using the following communication ports:

     

    TCP 80

    TCP 443

    TCP 4244
    TCP 5222
    TCP 5223
    TCP 5228
    TCP 5242
    UDP 3478
    UDP 45395
    TCP/UDP 50318
    TCP/UDP 59234

     

    As some of these ports are overlaping (TCP 5223 and UDP 3478) with Skype4B and Facetime, I'm wondering what would be the way to configure this without having the Aruba WLAN mixing up QOS application assignment/categorization as similar ports are being used by different apps.

    Also, it would be great if the destination network can be configured to define a more specific policy (ALG).



  • 2.  RE: QOS for WhatsApp

    Posted Dec 11, 2017 03:17 AM

    For those who are interested in my current solution, I've configured the following in my environment to prioritize whatsapp traffic:

     

    TCP 4244
    TCP 5222
    TCP 5223
    TCP 5228
    TCP 5242
    UDP 3478
    UDP 45395
    TCP/UDP 50318
    TCP/UDP 59234

     

    I've specifically not configured TCP 80 and TCP 443 as this would have huge impact on the controller CPU.

    The remaining item that I'm trying to find out is if whatsapp works the same like facetime, where an apple device connects to a public apple IP-network frist (17.0.0.0). I would then be able to configure TCP 80 and TCP 443 as well but with the specific destination network included (to prevent all 80 and 443 traffic to be inspected by the controller).