|
Resolution:
First, you will notice QoS settings for the ALG Proxy both on the MXM console and the local ALG configuration utility. It is strongly recommended that QoS changes be made via the MXM console. The setting on the local ALG configuration utility should only be used if the ALG Proxy is registered to a non-MXM gatekeeper. The MXM will override any local QoS settings made on the ALG.
Secondly, both the LAN proxy and the WAN proxy have these QoS settings, so make sure both are set to the desired values. The configuration screen on the MXM allows for easy selection of the QoS method (IP Precedence or DiffServ) as well as the specific QoS value.
Changing the QoS values on the ALG Proxy will cause it to unregister and re-register to the gatekeeper.
If the ALG Proxy is registered to a non-MXM gatekeeper, then the local configuration utility must be used to change QoS markings. The data is entered as a decimal value. As a result, the network administrator will need to first determine the exact desired binary makeup of the TOS byte and then convert this to a decimal number. IP Precedence values are reflected in the first three (highest order) bits of the TOS byte. Therefore, decimal 96 = priority 3, 128 = priority 4, 160 = priority 5 and 192 = priority 6. The ALG will already have default values entered which are typically acceptable. DiffServ implements what is called a DiffServ Code Point. The value is reflected in the first 6 bits of the TOS byte.
The field labeled "Data" on the local ALG Config Utility corresponds with RTCP streams. These are very important control streams and typically carry a higher QoS priority than audio and video. On the MXM console, this setting is labeled "RTCP".
| 
