Outbound call "No Route Exists"

Emmett H

Silver Partner
Joined
May 2, 2024
Messages
5
Reaction score
0
I have someone trying to add someone to a conference call and the call failed. I checked the call log and the reason states "No Route Exists".

From the screenshots below, in Call 1, there is +6104XXXX, but I have an outbound rule to strip the first 4 and replace with +61, maybe I set this up incorrectly? Also, in Call 2, you can see that it has the correct +614XX XXX XXX number but states no route exists. I've also noticed this is the only time where the number is separated instead of +61XXXXXXXX, not sure if that has something to do with it.

Any assistance would be greatly appreciated.
 

Attachments

  • Call Attempts.jpg
    Call Attempts.jpg
    78.9 KB · Views: 69
  • OutboundRule.jpg
    OutboundRule.jpg
    42.7 KB · Views: 66
Hi @Emmett H ,

Do you have other outbound rules that this call might be matching before it reaches this one?
Can you share a screenshot of your outbound rules? Obviously hide any sensitive information if any.
 
Sure, here's all the outbound rules.
 

Attachments

  • OutboundRules.jpg
    OutboundRules.jpg
    72 KB · Views: 87
Assign the rules to a department
 
Thanks, I'll have them test after I make the changes. Thanks
 
I have assigned all departments to all outbound rules. Unfortunately, it's now saying "Target not found" when dialing out from Conference.
 

Attachments

  • Targetnotfound.jpg
    Targetnotfound.jpg
    106.9 KB · Views: 43
Your outbound rule is configured with prefix +610 while you dial +614.
Remove the 0 from the prefix and check.
 
Hi, I've updated the outbound rules and still experiencing this issue "Target Not Found". I have provided the outbound rules as well. There is a 10 Digit outbound where it should strip the 1st digit and replace with +61. As you can see, the outbound rule did not apply. I tried to apply the outbound rule to Conference (700) but I am unable to find the extension. I am guessing this is by design.
 

Attachments

  • TargetNotFound.jpg
    TargetNotFound.jpg
    92.2 KB · Views: 30
  • OutboundRules.jpg
    OutboundRules.jpg
    94 KB · Views: 32
  • Outbound10.jpg
    Outbound10.jpg
    103.9 KB · Views: 32
Conference extension is a System extension.
There seems to be a misconfiguration there. Check guideline here and try other options to configure them accordingly.
 
Do you have E164 processing turned on, we found that if you had Process E164 enabled that the call would reject.