Solved Can't forward calls by caller ID: Target endpoint for ___ can not be built

[SteveITS]

We're trying to intercept a particular external call and forward it to another external number. I created a CID rule using Forward To Outside Number (in and out of hours). The CID rule seems to work as it is logged in the call log. The outbound fails with this logged in the Activity log:

[Flow] Target endpoint for 630nnnnnnn can not be built!

Dialed from an extension, that number works. I've tried with 1630... and multiple numbers also.

The (only) outbound rule has "Calls from extension(s)" set to 700, extension group DEFAULT, and "Calls to numbers starting with prefix" and "Calls to Numbers with a length of" are blank. I tried setting the length to 10, same result.

I feel like I'm missing a permission somewhere...? I have previously set up clients with a DR that has a number choice to forward calls, but in this case it's an automated call.

I also tried changing the call routing on the SIP trunk, same result. And same result on our 3CX server.

Linux, v18u1, no phones involved.

 

[Saqqara]

You need to relax / add outbound rule , as 3cx will use a system account to do forwarding

Create a rule with prefix of the number, leave all other fields blank. Place this rule at the top

 

[SteveITS]

That's along that lines of what I thought, but I get the same symptom. One test call, call log shows four outbound attempts, activity log shows four errors.

Outbound rule: Prefix 630yyyyyyy, Route1 = SIP trunk, at top of list.
Inbound rule: CID 630yyyyyyy, forward to outside number 630nnnnnnn.

activity log:
10/29/2021 9:11:48 PM - [Flow] Target endpoint for 630nnnnnnn can not be built!
10/29/2021 9:11:48 PM - [Flow] Target endpoint for 630nnnnnnn can not be built!
10/29/2021 9:11:47 PM - [Flow] Target endpoint for 630nnnnnnn can not be built!
10/29/2021 9:11:47 PM - [Flow] Target endpoint for 630nnnnnnn can not be built!

Call log shows the same four calls from ContactName:CIDrule (630yyyyyyy) to 630nnnnnnn, as Not Answered.

 

[Saqqara]

,You need to change prefix to 630nnnnnnn , as this is the outbound number

 

[SteveITS]

,You need to change prefix to 630nnnnnnn , as this is the outbound number

Oh, duh. "Calls to numbers..." Hazard of doing that late at night, I guess. Works fine now, thanks.

I looked again at a client where we had forwarding set up in a DR. They have the DR choice going to an extension, and the extension forwarding to the external number. It doesn't show that way in the call log but presumably that doesn't need a special route because the extensions are allowed to make external calls. So it would have also worked if I created an extension, forwarded it, and had the inbound call rule send to that fake extension. We were trying to get the call (MFA code) before it got to a DR, and the office was closed.

 

[ChrisC_3CX]

As this has been taken care of I'll be marking this thread as resolved.