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

[Shadragon]

Activity Log error message received for a specific ext on an incoming call is "[Flow] Target endpoint for can not be built!"

Call log has "PBX" under the To field and "Not answered" under Talking.

DID is on the SIP, inbound rule is in place, three digit calls to the ext work, but incoming external calls get a "This number is not in service" message.

I changed his ext on that DID inbound rule to my ext and get the same message on a test call.

This ext used to work, it was one of the first we setup, until he was unable to log into a queue. Tried everything and eventually I deleted the ext and re-entered it. That fixed the inability to log into the queue. Worked for a day, now he is unable to take external calls. Really weird as all other DID's are working.

 

[craigreilly]

The message you are getting sounds like a message from the provider and not from 3cx. Looking at the System Prompts - I do not see anything that fits that description "This number is not in service".

If I call a non-existent number from within the system, I get a rapid busy signal and the display shows 404-Not Found.

Does the DID the provider is sending match the DID in the incoming rules? I have a * in front of my DID's in case for some reason a 1 or +1 is sent... my rules are all entered as *4805551212

 

[Shadragon]

Yes sir. All DID's are entered the same way with the *. I deleted the incoming rule for that DID and off the SIP trunk and manually re-entered it. No joy.
I see the time / date of the call on the log along with my cell phone caller ID so I know the call is getting to the PBX.

 

[YiannisH_3CX]

Hello @Shadragon

Try pointing the same DID to a different extension and see if that works. You can also point a different DID to the problematic extension. That should tell you if the issue is with the extension or the DID.

 

[Shadragon]

Hi Yiannish,

I did do that and it failed also.
I found the issue. On the second SIP we had (the old phone system) the calls were set to "End call". I set it to the ext and everything kicked to life.
Why this affected the call, which comes in on the new 3CX system is beyond me.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution. If the trunk was activated in 2 systems then the calls was randomly routing to the other system and was going to End call.