[Flow] Target endpoint for xxxxxx5951 can not be built!

[Matt Stephens]

Note - this is not happening to normal outbound calls, I can call out from my desk phone or 3CX app. This issue is only occurring with out of office and automatic forwarding rules.

This started after upgrading to v16 on Thursday night, and went unnoticed until late last night. Normally we have out of office hours calls routed to an answering service who gets the base info of the caller and sends the transcript to our intake team. They haven't got any calls from our clients since I uninstalled v15.

I can't figure out what might be the cause or fix here. Any ideas?

Thanks in advance


Edit for info: this install is local, on Windows, using a patton gateway SIP trunk. Don't hesitate to ask for more info

 

[cobaltit]

You most likely have your outbound rules scoped to extension groups. Forwarding rules come out as a 'system' extension and not as the extension you are forwarding from so they no longer match your outbound rules. The lines before the line in you subject would say that the call doesn't match any outbound rules.

 

[Matt Stephens]

Updating to report what I've done that seems to have fixed the problem, in someone else experiences this.

First I deleted and recreated all my outbound rules. That somehow made the forwarding work for calls that reach the maximum queue wait time, but not calls that come in after office hours.

Then I deleted the inbound rule these calls are following and recreated that (all with the same exact settings), and that fixed the after hours forwarding.

 

[Matt Stephens]

You most likely have your outbound rules scoped to extension groups. Forwarding rules come out as a 'system' extension and not as the extension you are forwarding from so they no longer match your outbound rules. The lines before the line in you subject would say that the call doesn't match any outbound rules.

Hey thanks for your reply. I had started typing my solution before I saw it. I don't know what the deal was here, but there were no other messages in the activity log when this would happen, only the one in the subject line of this post. Multiple calls in a row looked like this with no filtering.

 

[cobaltit]

Sorry I usually run with verbose logging. If you change it you'll see the logic before that saying that the call doesn't match any outbound rules.

 

[eddv123]

As with what has been mentioned by @cobaltit I would probably keep your troubleshooting for this issue within 3CX but one thing that I must ask:

using a patton gateway SIP trunk

Are you using a separate Patton gateway and SIP trunk ? if not this does not make sense, Patton gateways are normally (when used with 3CX at least) trunking for ISDN or FXO/analogue lines.