Troubleshooting SIP Entity Monitoring alarms

Last Updated : Apr 26, 2023 |

About this task

The alarmed SIP entity is not successfully responding to SIP OPTIONS requests. SIP entities are reachable through multiple addresses, which depends on the Local Host Name Resolution administration and the DNS address resolution.

If the state of the entity is Down, none of the entity addresses respond to OPTIONS requests successfully. If the state of the entity is Partially Up, minimum one of the entity addresses responds successfully and minimum one address does not respond successfully.

Before you begin

Verify the details of the SIP entity, such as the status of the multiple addresses of the SIP entity and the response codes returned by the addresses. The response codes are the standard SIP responses based on RFC 3261, Section 21. View the details of the SIP entity on the SIP Entity Link Monitoring Status Summary page of System Manager at Elements > Session Manager > System Status > SIP Entity Monitoring.

Procedure

  1. Check the network connections of the SIP entity.
  2. Run the following command to check the network connection between Avaya Breeze® platform and the SIP entity: ping
  3. Using the SIP Tracer tool or a network protocol analyzer, such as Wireshark, verify that:

    • An OPTIONS request can be sent from the Avaya Breeze® platform to the SIP entity.

    • The SIP entity send the following response: 200 OK

  4. Check the Avaya Breeze® platform configuration.
  5. Check the network configuration.
  6. Check the local host name resolution configuration.

Next Steps

If the problem persists, contact Avaya Support: https://support.avaya.com.

Related information
Avaya Breeze platform troubleshooting