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. The current cloud probe addresses are on the Probes page in the app and at https://app.sipsentry.net/api/v1/probe-addresses, so an allowlist can be kept in step with them. Or, on Pro and MSP, 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. A paused monitor still counts against your limit, because it keeps its configuration and history; deleting it frees the slot.

Can my customers see their own status page?

Yes, on Pro and MSP. Each customer group can publish a public status page at app.sipsentry.net/status/your-slug, with live states and 90 days of uptime for the monitors you choose to show. On the MSP plan it carries your own title and logo, and the Powered by SIP Sentry footer is gone.

Which alert channels are included?

Email and webhooks (signed with HMAC-SHA256 when you set a secret) on every plan; Pro and MSP add Slack, Telegram and SMS. Telegram uses your own bot token, and SMS goes through your own HTTP SMS gateway: we POST the recipient, sender and message as JSON with your API key. That keeps us out of your message billing entirely. On MSP, a rule can send one customer’s alerts to the channel of whoever holds that contract.

What happens if I move to a smaller plan?

Nothing you set up is deleted. Your oldest monitors up to the new limit keep running and the rest wait, still configured, until you upgrade or remove some; intervals slow to the plan’s fastest; history beyond its retention is hidden. Channels, status pages and private probes you already have keep working, you just cannot add more of them on a plan that does not include them.

What about test calls and MOS scores?

Call-based checks are included on every plan. A probe places a real call to a dedicated echo extension, streams G.711, and scores the returning audio with the ITU-T G.107 E-model from measured jitter, loss, and round-trip delay. It is the only check that catches one-way audio, because signaling never sees it.

Where does SIP Sentry run?

Probes and API run in the EU (primary region: Amsterdam). We’re GDPR-native: results carry protocol metadata and the SIP messages a check exchanged, never call content. The RTP check sends near-silent test packets to an echo extension and keeps only the measurements; no audio is recorded.