Dial 0 for Operator

[Simon Phelon]

I know this is a topic covered by a few other posts - I've read those and followed their advice.
I have taken over a system that was setup by a different company, tweaking the system to run pretty much as the organisation wants, just this last issue has beaten me.
I found that almost every extension had it's SIP ID set to 0 so I have deleted all those entries apart from the receptionist's extension. Next, I checked and found that the Allow calls from/to external SIP URIs was not enabled so I have enabled that.
This has made no difference, ringing 0 from an extension still gets the 404 not found error.

I know that it is not an outbound rule issue as there is only one rule that addresses calls to numbers starting with 0, and that one also uses the 'Calls to Numbers with a length of' field with a value of 9-13 so it shouldn't be affecting the 0 calls.
Just to make sure, I changed this rule to numbers starting with 00, rang 0 got the same result then changed the rule back.

Looking in the Log I get 09/17/2019 5:28:47 PM - [Flow] Target endpoint for 0 can not be built!
Which suggests to me that the system cannot find the SIP ID but I might be wrong. I'm out of ideas.

 

[Saqqara]

Are you sure you have removed all the SIP ID, except the receptionist. What happens for a test you enter 1

Have you tried rebooting the system

 

[Simon Phelon]

I'm fairly sure I've got them all, I've gone through all 70 odd extensions 3 times, and couldn't see any SIP ID settings on any groups. Rebooting is a good idea, I'll see if I can get permission to do that tomorrow.

 

[Alphabetic]

It's not something silly like they're using 0 in dial codes?

 

[Simon Phelon]

Hey great news, the reboot did the trick dialing 0 now rings the operator.