The endpoint client may be having difficulties in generating a good packet stream.
The endpoint client NIC may be misconfigured or dropping packets
Missing or incorrect DSCP setting in Avaya Aura® MS configuration
Missing or incorrect DSCP settings or policies in network routers or switches
The network routers and switches between the client and the Avaya Aura® MS may be overloaded, dropping packets
The Codec selected by the client may not produce a quality audio experience at the network packet loss rate
Avaya Aura® MS may have been installed on a virtual machine (VM) that is improperly configured
Avaya Aura® MS NIC is dropping packets or incorrectly configured.
Proposed solutions
Examine endpoint client to ensure it is producing a quality packet stream.
Examine endpoint client NIC driver or configuration.
Examine Avaya Aura® MS DSCP setting to ensure they match the network policy
Examine client and network switch and routers settings to ensure they enforce the expected packet prioritization.
Examine network configuration to ensure network is not causing unexpected loss due to congestion or other factors
Choose higher quality Codecs compatible with network loss rate specification.
If Avaya Aura® MS is installed on a Virtual Machine, improper VM resource allocation/reservation can cause packets to be lost in the oncoming network drivers. Refer to “Deploying and Updating Avaya Aura® Media Server Appliance FP1” and follow all requirements and recommended best practices for VM configuration.
Examine Avaya Aura® MS server NIC configuration.
If the QoS alarms are determined to be due to Codec preference and network configuration decisions that cannot be changed, the options are:
Disable the QoS alarm, removing a useful warning of unexpected network problems.
Decrease thresholds for QoS warning or critical states such that normal observed levels of quality degradation do not trigger the alarms.
Increase numbers of sessions allowed in the warning or critical states before raising alarms.
