Meru Technical Note - How QoS and VoIP works with Meru Wireless LAN System
Description
Scope
Solution
Quality voice traffic has different network requirements than does typical network traffic. The Meru Wireless LAN System is designed to automatically provision voice traffic with a level of QoS appropriate for voice calls. The result is that VoIP traffic works much better over a Meru Wireless LAN System than it does over most WLANs. The controller watches the traffic passing through it and when it sees packets from stations to servers on ports reserved for SIP or H.323 service, it tracks subsequent communication in that sequence and provisions the VoIP call with a level of service appropriate for a VoIP call.
QoS and VoIP with Meru Wireless LAN System
Scope
KB Article Type: Design-External
Related Products: All Controller/ AP models
Related Software Versions: All code version
Keywords: QoS and VoIP with Meru
Solution
Quality voice traffic has different network requirements than does typical network traffic. The Meru Wireless LAN System is designed to automatically provision voice traffic with a level of QoS appropriate for voice calls. The result is that VoIP traffic works much better over a Meru Wireless LAN System than it does over most WLANs. The controller watches the traffic passing through it and when it sees packets from stations to servers on ports reserved for SIP or H.323 service, it tracks subsequent communication in that sequence and provisions the VoIP call with a level of service appropriate for a VoIP call.
The port numbers watched are:
5060 for SIP service (UDP)
1720 for H.323 service (TCP)
5200 for Vocera (UDP)
These are the standard port numbers for these services. If your VoIP devices use these ports to communicate with their servers, you do not need to configure VoIP QoS rules on your system. If your VoIP devices and servers are configured to use different ports, you will need to modify the QoS rules on the controller to match the ports your system uses.
