[Flow] Target endpoint for 1########## can not be built!

[MCCDCHS]

[Flow] Target endpoint for 1########## can not be built!
Have 49 other T58A who all can call out, just one extension is unable to call out.
It gets this error [Flow] Target endpoint for 1########## can not be built! in the Activity log, the user hears called number does not exist.
I can go to another Deskphone right next to this one and dial the same number and it rings and works.

The user can still receive calls on the phone.

Tried factory resetting the phone, remove the phone from 3CX and provisioned.

SIP trunk is working, inbound calls and outbound calls are all working... Thoughts?

 

[AWS2P]

is it only for outbound call not working or even if you try to call another extension it fails too?
did you check in ext.options if this is unticked

 

[MCCDCHS]

I ended up Deleting the extension and copying another extension and putting the same extension number, then reprovision phone again and this time it is working. I assume now that I think about it, perhaps PBX deliveries audio was or was not checked. But cant checks now as its working.

 

[AWS2P]

in outbound rule do you use extensions or groups in which your non working extension should have been forgotten

 

[MCCDCHS]

is it only for outbound call not working or even if you try to call another extension it fails too?
did you check in ext.options if this is unticked
View attachment 13867

That was a good suggestion but it was not checked. I assume it had something to do with not having an SBC beforehand and adding an SBC and not needing the PBX delivers Audio Option. I just missed it on this extension I bet.

 

[MCCDCHS]

in outbound rule do you use extensions or groups in which your non working extension should have been forgotten

We use groups, another thing I should have checked.

 

[AWS2P]

As for now you solved the problem , then just have to say " well done" and i'm going to sleep