Plans that scale with your customer book

Questions a NOC would ask

Do I need to allowlist your probes?

If your SBC drops SIP from unknown sources (it probably should), yes. Our cloud probe IP ranges are published and stable; allowlist them once. Or run a private probe inside your own network and skip the question entirely.

Is the REGISTER check safe for production?

The check registers with a short expiry, removes only its own binding afterwards, and never sends Contact: *. Still: point it at a dedicated test extension, not a phone’s AOR. The docs explain exactly why.

What counts as a monitor?

One check against one target — an OPTIONS check and a TLS check on the same SBC are two monitors. Pause a monitor and it stops counting against your limit the moment you delete it.

Can my customers see their own status page?

Yes — every customer group can have a public status page with live states and 90 days of uptime. On the MSP plan you can white-label it with the customer’s own name and logo.

What about test calls and MOS scores?

Call-based checks with estimated MOS (ITU-T G.107 from measured jitter, loss, and latency) are on the roadmap. Signaling checks catch the large majority of outages long before media quality is the question.

Where does SIP Sentry run?

Probes and API run in the EU (primary region: Amsterdam). We’re GDPR-native — check payloads carry protocol metadata, not call content. There is no audio anywhere in the system.