If you see the error message 403 Failed to get a destination SBC, it means that the platform was unable to route your call because there is no matching Session Border Controller (SBC) for the number you dialed.
This typically happens for one of two reasons:
1. No Connections Configured
You have not set up any Connections in your account. Connections define where and how calls should be routed — for example, to your own PBX or SIP provider.
How to fix it:
- Go to the Connections section in the Admin Control Panel.
- Create a new Connection and define its matching pattern (e.g., all calls starting with
+44or specific area codes). - Make sure the Connection includes a valid endpoint (your PBX or ISP) that can handle calls.
2. Number Doesn’t Match Any Connection Pattern
You have configured Connections, but the number you’re trying to call doesn’t match any of the patterns defined in your existing Connections.
For example:
- You have a Connection set up for numbers starting with
+1(USA), but you’re trying to call a+44(UK) number. - The pattern in your Connection is too restrictive or doesn’t account for your intended destination.
How to fix it:
- Review your Connection patterns under the Connections tab.
- Adjust your match patterns to ensure they cover the full range of numbers you want to allow.
- Use a wildcard pattern like
.to match all numbers (for testing purposes), but be sure to narrow it down in production to avoid misrouting.
How do i see the SIP Trace
If you no longer get this message after your changes, well done, but you may wonder how you can see the SIP traces.