Network Diagnostics

New: SIP OPTIONS Diagnostic — is your SIP server answering from outside?

Send one SIP OPTIONS request over UDP, TCP or TLS to a SIP server you own and see the response code, server identification, advertised methods and extensions and the TLS certificate — after DNS TXT verification.

By NetTools.tech · · 4 min read

Your SIP trunk provider says the PBX stopped answering their keepalives. A remote office cannot register after a firewall change. A new session border controller is in place and you want to know whether the world can see it. VoIP problems are hard to narrow down because a SIP server that does not want to talk to you usually says nothing at all.

The new SIP OPTIONS Diagnostic sends one SIP OPTIONS request from the NetTools server to a SIP server you own, over UDP, TCP or TLS, and shows exactly what came back.

What the test does

SIP OPTIONS asks a server "what can you do?" without starting a call. It is the request PBXs, proxies and trunk providers use as a health check. You enter the server's host name or IP address, the port (5060 for UDP and TCP, 5061 for TLS by default) and the transport, and press Send SIP OPTIONS. The result shows:

  • the outcome, in plain words — for example SIP Server Responded, Authentication Required, Request Rejected or No SIP Response;
  • the status line and the response time;
  • the server identification from the Server or User-Agent header, if the server discloses it;
  • advertised methods and extensions from the Allow and Supported headers, as a grid;
  • for TLS, the certificate: subject, issuer, validity and the TLS version, checked before anything is sent;
  • the raw request and response, so you can compare them with your own SIP traces.

The test sends OPTIONS and nothing else. There is no INVITE, REGISTER, SUBSCRIBE or MESSAGE, no authentication, and no probing for users or extensions. If the server answers with a redirect, the redirect is shown, not followed.

Verify first, then test

Sending SIP requests to servers you do not control looks like reconnaissance, and it can set off intrusion detection or get an address blocked. So the tool only tests infrastructure you have proved you control:

  1. Enter your SIP server and press Start verification. The tool gives you a TXT record to publish at _nettools-sip-verification.<your domain>, with a value that starts with nettools-sip-verification=.
  2. Publish the record and press Verify. Once the record is found, the domain is verified for 30 days (an unverified request expires after 72 hours).
  3. Test the domain, any subdomain, or an IP address that the domain's DNS points to: its A/AAAA records or the targets of its _sip._udp, _sip._tcp or _sips._tcp SRV records.

The NetTools server looks up the TXT record again before every test. Remove the record and the authorization ends with the next attempt. Only hashes of the verification ID and token are stored, never the values themselves. An administrator can also approve specific addresses, which is the only way to test private networks.

Reading a result

Any SIP response proves that a SIP server is listening and answering, even if it says no:

OutcomeWhat it means
SIP Server Responded2xx: the server answered OPTIONS normally
Authentication Required401 or 407: a SIP server answered and wants credentials, which NetTools never sends
Request Rejected403: the server answers but refuses OPTIONS from this source or for this domain
Method Not Allowed405: the server does not permit OPTIONS
No SIP ResponseNothing came back before the timeout
Connection RefusedTCP or TLS: nothing accepts connections on that port
TLS Connection FailedThe certificate or handshake failed, so no request was sent
Malformed ResponseSomething answered, but not with valid SIP

"No SIP Response" deserves a careful reading. Many SIP servers, session border controllers and firewalls drop OPTIONS from unknown sources on purpose, to stay invisible to scanners. Silence therefore does not prove that the server is offline or the port is closed. Check source-address filters and the transport before concluding anything.

A 200 OK is good news, but it does not mean calls will work. Registration, routing, codecs and the RTP media path are outside what a read-only OPTIONS test can see.

Built not to be a scanner

The tool enforces limits so it cannot be used to sweep networks:

  • one OPTIONS transaction per test; over UDP at most two retransmissions, and only until something answers;
  • 20 tests per visitor per hour, 30 per verification and 30 per target per hour, and 10 new verifications per visitor per hour;
  • public addresses only unless an administrator approved a private one; loopback, link-local (including cloud metadata), multicast and broadcast are never allowed;
  • host names are resolved, every address is checked, and the connection goes to the checked address;
  • no port ranges and no target lists.

IPv6 targets are refused for now because the NetTools probe server has no IPv6 connectivity yet.

Exports

Results can be copied or exported as JSON, CSV or a print-friendly report, with the outcome, status, timing, server identification, methods, extensions, TLS details and all response headers. From the result, Port Checker, Ping and Traceroute are one click away for the layers below SIP, and the SNMP Diagnostic covers the device side.

Try it

Open the SIP OPTIONS Diagnostic, verify your domain and send a first OPTIONS request. The guide explains the protocol, every option and every outcome in detail.