Solved 3CX v16 - [Flow] Target endpoint for {Number} can not be built! - SPA3102

[JCLloyd]

It appears we cannot outbound FAX, since the 3CX update to v16.0.0.1581 from v15.5.x.x ...
. The FAX machine speaker reports "Called number does not exist."
. When I check the logs, I see "... [Flow] Target endpoint for {Number} can not be built!"

It is like I suddenly need a new outbound rule I didn't need before... or the SPA3102 is no longer supported...?

I'm digging around to see if I can figure this out, but... If some knows where my energies should be focused, or if this is bug that I cannot fix, I will be most appreciative!

I searched on "FAX" and "Flow" and "can not be built", but didn't get a thread hit. Help!

 

[JCLloyd]

[RESOLVED] "Call from extension(s)" was blank on my outbound rules... Joy.

Hope someone else is helped by this thread...

 

[leejor]

That should not have made a difference. Extension numbers that are entered there, will restrict the rule use to only those extensions.. If it left blank, then it is open for all to use.

While the SPA3102 is no longer "officially" supported, it still works.

 

[JCLloyd]

That is what I thought, Leejor, but there it is. Left blank the FAX numbers, which are in the 8800 range for me, didn't have a rule for outbound. My SIP phones, in a different range, were not affected. I have DIDs pointed to the FAX numbers for inbound, so that was not affected.

Maybe, a wild card value is now needed, or something messed with the field data. I'll try clearing it, after outbound FAX need subsides, and see if it goes back to the way it was.

Just for note... https://www.3cx.com/3cxacademy/videos/advanced/configuring-outbound-routing/outbound-rules/
-
[SLIDE 5]
The Outbound Rules of 3CX are checked in a top down manner, always starting at the top and working down the list.

When a match is made, it will process the call with the matching rule, and will not check the next rule, or any other subsequent rules.

If there are no criteria in the Outbound Rule, this rule will be ignored and the PBX will proceed on to the next rule. Having your criteria blank does not mean that “All Calls” will be processed. On the contrary this rule will be redundant.

The criteria fields of the Outbound Rules can accept single values. For example, a single extension.

Comma separated values can also be added, to have multiple values, for example 100,102 to have both extensions 100 and 102 as values.

You can also use the dash, or minus sign to signify a range of values. For example 100-105 will take extensions 100 to 105 inclusive.

Combinations of the above are also possible. For example 102,105-117,302 will take extensions 102 and 302 as well as the range of extensions 105 till 117.
-

 

[YiannisH_3CX]

Hello @JCLloyd

Indeed one of the criteria in an outbound rule must match for the call to be processed. This was true for previous versions as well. What has changed in V16 is that an outbound rule will no longer match if you selected a group of extensions and the call is coming from a system extension or directly forwarded to an external number.