3.24.7 TxAnswerTimeout
- Measurement ID
 - 10044
 - Measurement Group
 - Diameter Egress Transaction
 - Measurement Type
 - Simple
 - Measurement Dimension
 - Arrayed (by Connection ID)
 - Description
 - 
                        
The number of times that an Answer response was not received from a peer before the maximum allowed time defined by the “Pending Answer Timer” value.
Answer timeouts can be caused by a variety of reasons:- The peer associated with this connection may be experiencing congestion, causing delays in sending the Answer response.
 - IP Network congestion.
 - If the peer associated with this connection is a Diameter Relay Agent, then an upstream node from the peer may be experiencing congestion, causing delays in sending the Answer response.
 
 - Collection Interval
 - 5 min
 - Peg Condition
 - 
                        
When timer PENDING-ANSWER-TIMER expires.
The connection measurement is associated with the connection from which the corresponding Request message was sent.
 - Measurement Scope
 - Server Group
 
Recovery
- If the user-configurable answer response timer is set too low it can cause the timer to expire before a Answer response is received. The user-configurable value is set using the page .
 - It is recommended to contact unresolvable-reference.html#GUID-F069C6FD-5BA3-4F31-AE9E-A187D5B5F729 for assistance if needed.