FreeSWITCH: No route, Aborting

What it means

The dialplan context processed the call and no extension matched, so the call is dropped (often with NO_ROUTE_DESTINATION).

Why it happens

• The destination number arrives in a format your regex does not match (+, country code, 8).
• The call landed in the public context, but your rules are in default.
• A missing transfer from public to the right context for inbound DIDs.

How to fix it

1. Find the destination_number in the log and test it against your expressions.
2. Check which context the profile sends calls to (context param of the profile).
3. For inbound DIDs add an extension in public that transfers to default or your IVR.

Useful tools

Dialplan pattern tester · Dialplan converter

Other FreeSWITCH errors

• mygateway Failed Registration with status Forbidden [403]. failure #3
• IP 203.0.113.5 Rejected by acl "domains". Falling back to Digest auth.
• Can't find user [1000@203.0.113.10] from 198.51.100.7
• Hangup sofia/external/74951234567 [CS_EXCHANGE_MEDIA] [INCOMPATIBLE_DESTINATION]
• Hangup sofia/internal/101@pbx.example [CS_EXCHANGE_MEDIA] [MEDIA_TIMEOUT]