SIP trunk does not come back after router reboot or provider incident.
Often the old registration lingers on the provider side or NAT binding is missing. Sometimes you have to re-register explicitly.
Try this first
- 1Check PBX status: registered, not just reachable
- 2Force a re-register on the PBX
- 3Set NAT keepalive (OPTIONS) to a shorter interval
- 4Kill the old session in the provider portal if available
When to bring us in
Trunk stays stuck despite force-register: provider incident, ask explicitly for a server-side drop-registration and keep the ticket ID.
See also
- Voys, BelXS or RoutIT, which cloud PBX fits?Three popular NL platforms, differences are admin UI, partner model and per-user price.
- Teams Phone: Calling Plan, Direct Routing or Operator Connect?Three ways to connect PSTN to Teams, cost and management differ a lot.
- 3CX: self-host on VPS or take 3CX cloud?Self-host saves licence, but you own SBC, backup and updates.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.