Dial 0 for reception using SIP ID

[Mark Phillips]

Last week, I set the SIP ID on a reception phone to 0, thus meaning that any extension could simply dial 0 to call the reception. This worked immediately and without any further configuration.

Now, for some reason, it has stopped working and I see the message "[Flow] Target endpoint for 0 can not be built!" in the activity log. Clearly I am missing something as I think this error is being generated by the Outbound Rules processing...and I believe that a direct SIP call should bypass Outbound Rules all together.

Any ideas?

Thanks
Mark

 

[leejor]

Did you make changes to the outbound rules, an entry that begins with zero? Do you have rules that begin with zero tbut don't have a set number of digits in length? Something must have changed for this to stop working. In the past, I've found the SIP ID to take precedence over outbound rules.

 

[Mark Phillips]

my only outbound rules are:
Prefixed with 9 -> strip 9 -> send to SIP trunk
Length of 7, prefixed with 9 -> strip 9 and add local area code -> send to SIP trunk
Length of 11 -> send to SIP trunk
Length of 6 -> prepend local area code -> send to SIP trunk

 

[Mark Phillips]

Yep, definitely getting caught in outbound rule processing - here's an extract from the verbose log (read bottom up).

12/03/2019 19:30:12 - [CM503016]: Call(C:395): Attempt to reach <sip:[email protected]:5060> from Extn:0002 has failed. Reason: Not Found

12/03/2019 19:30:12 - [CM503014]: Call(C:395): No known route from Extn:0002 to target: <sip:[email protected]:5060>

12/03/2019 19:30:12 - Call(C:395): from Extn:0002 to 0 doesn't match any outbound rule. No outbound rule could be selected.

12/03/2019 19:30:12 - [Flow] Target endpoint for 0 can not be built!

12/03/2019 19:30:12 - Looking for outbound rule: dialed = [0], processed: [0]; from-ext:

12/03/2019 19:30:12 - [Flow] Building target endpoint to 0 from "Joe Bloggs" <sip:[email protected]:5060>

12/03/2019 19:30:12 - [CM503010]: Call(C:395): Making route(s) from Extn:0002 to <sip:[email protected]:5060>

 

[Rhys Haskell]

I had the exact same issue that you are describing, I deleted and recreated the dummy user and it worked. If you are not using a dummy user then try to make a dummy user and forward to the reception user.

 

[cobaltit]

Why were you using the SIP ID for that? The operator extension setting under General Settings should already do that.

 

[Rhys Haskell]

Why were you using the SIP ID for that? The operator extension setting under General Settings should already do that.

If a user dials 0 from any phone this will not connect to the operator will it without SIP ID?

 

[cobaltit]

If a user dials 0 from any phone this will not connect to the operator will it without SIP ID?

No, I misread that part. Never had that request so I didn't think of it from that side. I guess anyone who had a need to dial the receptionist either can remember the extension or we put a BLF for it. Odd that it should work and then hit the outbound rules. I also noticed you have extension 0002 in that log. Was that edited or do you actually have extensions with leading zeroes? Or did the change the log formatting and I didn't notice.

 

[Rhys Haskell]

No, I misread that part. Never had that request so I didn't think of it from that side. I guess anyone who had a need to dial the receptionist either can remember the extension or we put a BLF for it. Odd that it should work and then hit the outbound rules. I also noticed you have extension 0002 in that log. Was that edited or do you actually have extensions with leading zeroes? Or did the change the log formatting and I didn't notice.

We have had quite a few requests for this, as on legacy systems such as Avaya and Samsung this was a widely used feature. This is also sometimes used when a client puts a phone on the wall with a note to dial 0 for entry.

 

[cobaltit]

Hmm.. I've replaced a few legacy systems and never had this request, but I never sold legacy systems. And for door entry, it seems that note could just as easily say dial '100' or have a BLF or if I'm replacing the system put an actual door phone. But I guess there is a use case for most anything. But regardless it's definitely odd that is just stopped working. Curious to see what the resolution is.

 

[Mark Phillips]

The reason for wanting to do this is because we have a phone in a public area (in a small hotel) and we want to keep things as simple as possible - therefore "press 0 for reception". It seems fairly common (in UK hotels at least) to dial 0 to speak to reception.

The 0002 extension is one of my testing extensions. The "real" extensions start at 1000. Though I definitely have previously set the SIP ID to 0 on extn 0002 during testing.

 

[Mark Phillips]

Okay found it -
Under Settings->Network->Direct SIP, I must have un-checked "Allow calls from/to external SIP URIs" at some point, thinking that "external" meant external callers. I have checked the box and now I am able to dial 0 to call the extension.

 

[cobaltit]

Ok, you've convinced me! I'm making sure all installs can now press 0 to reach the operator!

In all seriousness though, that's why I hang out here on the forums. While we see a lot in what we do, there's obviously a lot of different scenarios we don't see. And with 3CX being what it is a lot of times we try to focus on the why people do things as 3CX doesn't replicate a lot of common features of legacy PBXes but can be configured to accomplish the same goal in other ways.

Thanks for updating the thread with the 'fix'

 

[leejor]

The basic Idea (and how to)of dialling zero for the operator was documented almost 9 years ago.
https://www.3cx.com/blog/docs/dial-0-for-operator/