Documentation

SIP Checks

About SIP Checks

SIP stands for "Session Initiation Protocol," and refers to a signaling protocol that can run over UDP, TCP, TLS, or Websockets and is commonly used for voice and video communications. SIP servers are often the connection points for VOIP calls.

When to use SIP Checks

NodePing's SIP monitoring can verify that your SIP server is available and responding to new requests. The check does not initiate a call, but rather tests that the server accepts a SIP connection by sending the OPTIONS command and watching for the response. If your server does not support the OPTIONS command and returns an error, this indicates that the server is up and operating, so the check will pass.

Using SIP Checks

To set up SIP server monitoring,

Select SIP from the Check type drop down.
Give it a friendly label to identify this check in lists and notifications.
Enable Automated Diagnostics if you'd like detailed technical info about the failure that may help you troubleshoot a failure.
Set how often you want the check to run on the Check Frequency field.
Set the IP address or fully qualified name of the DNS server. If you're running your SIP service on a port other than the default 5060, you can specify the port in colon notation such as 'mysipendpoint.nodeping.com:6550'
If you want return statuses greater than 499 to not fail the check, add a comma delimited list of status codes you want to ignore in the "Ignore these status codes" field.
Use the 'Transport' dropdown to choose how we should attempt to connect to your SIP service. Default is to try UDP then TCP and should work for nearly all SIP services. We also support SIP over TLS as well as SIP over Websocket.
Set a time out. The default 5 seconds works fine for most situations.
Set the Sensitivity. High is usually appropriate.
Set the notifications for this check. More information about notifications.

Common usage:
Use the SIP check to ensure your VOIP gateways are route-able and replying to commands.

Other considerations

If you're running your SIP service on a port other than the default 5060, you can specify the port in colon notation such as 'sip.nodeping.com:6550'

You should have a SRV DNS record set for the sip