Skip to main content
You place or the dialer places an outbound call, and it doesn’t connect — it fails immediately, rings nowhere, or ends with an error.

​
Quick checks

  • Is your carrier’s Status Active and Approval Approved?
  • Does an outbound route actually match the number you’re dialing?
  • Does the call appear in Call records at all?

​
Cause: the carrier isn’t active or approved

How to check: Go to Carriers and check the carrier’s Status and Approval columns. How to fix: Set Status to Active if you haven’t. If Approval is still Pending review, contact Get2Dial support — see Connect a SIP carrier.

​
Cause: no outbound route matches the number

How to check: Go to Outbound routes and check whether any active route’s prefix (or regex) matches the number you dialed. How to fix: Add or fix a route — see Add an outbound route. A prefix left blank matches everything, which is useful as a catch-all.

​
Cause: the route points at the wrong carrier, or that carrier is misconfigured

How to check: Confirm the route’s Carrier is the one you expect, and that carrier’s Remote host, Port, and Transport match what your carrier told you. How to fix: Correct the mismatch. A wrong transport or port is the most common reason a call fails despite everything else looking right.

​
Cause: the call was blocked by a compliance rule

How to check: For campaign-driven calls, check whether the lead is on your DNC list, excluded from the campaign, or outside its calling-hours window. How to fix: This is expected behavior, not a bug — adjust the DNC entry, exclusion, or calling-hours window if the block was unintended.

​
If none of this worked