Introduction
The Media Gateway Timeout report measures amount of H.248 transaction time-out errors encountered between the Media Gateway and the MGC (Media Gateway Controller).
Typical escalation of a poor connection is H.248 timeout > H.248 Signalling Channel Restart > Link Bounce. A link bounce is service-impacting.
The H.248 data is used for control purposes. Even though the bandwidth consumed is relatively small, it is very important that QoS policy is applied.
If the network does not meet Avaya's recommended performance standards, parts or all of the solution can restart, causing major business interruption.
Uses
- Identify, over an extended time period, the performance of the network(s) serving the Media Gateway(s).
- An indicator of potential problems when there are peg counts present.
- Detect and resolve issues before they become business-impacting.
- Perform Root Cause Analysis to prevent a reoccurrence of the incident
Examples
Example 1
In this example Media Gateway is seeing no H.248 transaction timeouts. The network is working within the Avaya recommendations.
Example 2
In this example Media Gateway is seeing many H.248 transaction timeouts. The network is not working within the Avaya recommendations.
The UC team need to work in conjunction with the data team to improve the performance of the network prior to there being an outage.