Integration · 2 min read

IP whitelist vs registration auth — which to pick

Trade-offs between IP-based auth and username/password registration on your trunk.

Registration (default)

Your softswitch registers to sip.non-cli.site with username + password. Works from any IP. Re-registers every 60s.

Pros: zero config on our side, works behind NAT, easy to move servers. Cons: registration churn under load, password is a credential to protect.

IP whitelist

You give us 1–4 static public IPs. We accept INVITEs from those IPs with no authentication. No registration needed.

Pros: lower setup latency, no password to leak, cleaner SIP traces, marginally better failover. Cons: locked to specific IPs, no good if your softswitch IP changes often.

How to request IP auth

Open a ticket with:

  • Trunk username
  • Static IPs to whitelist
  • Whether to keep registration as a fallback (yes/no)

We provision within minutes during EU/US business hours.

Hybrid

You can have both — registration as primary, IP whitelist as fallback. Useful during server migrations.

Related in Integration

Still stuck?

Open a ticket