SIP Monitor Alarm

Last Updated : Oct 03, 2013 |

The alarmed SIP entity is not successfully responding to SIP OPTIONS requests.

A SIP entity can be reachable through several addresses, depending on Local Host Name Resolution administration and 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, at least one of the entity addresses is responding successfully and at least one address is not responding successfully.

The SIP Monitoring Status page on the System Manager provides more detail, including the status of the entity’s various addresses and the response codes returned by the various addresses. The response codes are the standard SIP responses according to RFC 3261, section 21.

Troubleshooting SIP Monitoring alarms

Procedure

  1. Check the SIP Monitoring Status page for more details.
  2. Verify network connectivity exists between Session Manager and the alarmed SIP entity using the ping command.
  3. Using the SIP Tracer tool or a network protocol analyzer such as Wireshark, verify that an OPTIONS request is sent from the Session Manager to the alarmed entity, and that the entity responds successfully. A typical response is 200 OK.