3CX app recent calls Not Found adds 1 digit on outbound calls for Flow Route

[rjamesm2884]

Hello,

I'm trying to understand why if Flow route requires 1 for outbound, then why when we dial a number without 1 it adds it to the recent history, if I click to dial that number with 1 it fails with Not Found.

 

[leejor]

...you are adding 1 (prefix), in your outbound rules, after the number gas been dialled, or you actually dial, with a leading 1, and the outbound rules leave the number unmodified?
Have you checked the 3CX Activity Log to see what number, is actually being sent to 3CX, when you click to dial. That number probably does not match an outbound rule.

 

[rjamesm2884]

...you are adding 1 (prefix), in your outbound rules, after the number gas been dialled, or you actually dial, with a leading 1, and the outbound rules leave the number unmodified?
Have you checked the 3CX Activity Log to see what number, is actually being sent to 3CX, when you click to dial. That number probably does not match an outbound rule.

Yes, 1 is added as a prefix on Outbound Rules because Flowroute requires it for outbound calls. If I dial from the 3CX app a number not including 1, the recent history flags it with a leading 1 making it impossible to call from recent history.

3CX activity logs shows the number with 1 leading being added but Not Found.

 

[rjamesm2884]

Ok after hours playing around with this I found the solution. Outbound rules for Flow Route need to be set.

Calls to Numbers with a length of > blank

Route 1 > flow route sip > strip 0 > prepend blank
Route 2 > flow route sip > strip 0 > prepend 1

 

[leejor]

If those routes are in the same rule, then route 2 is the same physical trunk group as route 1? If that is the case, then no calls would route there unless route 1 were all busy/not available.
You can create two different rules, one that deals with calls with no leading 1,and adds it, and a rule that deals with calls with the leading 1 and removes no digits