Dial Codes aren't all working - strange event log error

[stpaulschurch]

I recently installed a couple more IP phones in our facility and thought I'd do some maintenance and testing of features I've not used since upgrading to v.20.

The very first thing I tried was the paging and intercom features. Neither of them work. I set a dial code of *74 for paging, and created a new ring group called Paging, assigned all our phones to the ring group, and saved. I am not using multicast paging ATM because I wanted to see if this would work as it used to. Well...it doesn't. I get the typical fast beep tone, and "Not found" on the phone's screen (any phone I try to page from including my andriod app).

I looked at the Dashboard and event log, and this is what I see each time I try to page:

There was no user or outbound rule found for the number *74 that Ext. #### dialed.
Replace the #### with the extension number.

Why am I getting an outbound rule error when I'm not trying to do outbound dialing but simply use dial codes. I noticed that Call Park doesn't work either (does nothing). *30 DOES work, changing profile status, as well as *4, voicemail access, *77* hotdesking, but that's about it.

*74 should be paging our phones, but leaves me with an outbound rule error. Any suggestions?

 

[Evolute IT]

*74<ext>

When you use a paging ring group, no need to use the dial code. It's only to page/intercom another extension.

 

[stpaulschurch]

The 3cx instructions seem to suggest otherwise:

Paging is used to make a one-way announcement to a ring group via the phone speaker, without the called party picking up the handset. Paging requires you to set the relevant dial code in “System” > “Dial Codes” > “Paging”, e.g. *9, and a phone that supports and is configured for intercom.

To add a paging group for a ring group go to “Call Handling”> Click on the ring group you want to edit > in the “Ring Strategy” dropdown choose between:

• Paging - add the extensions to the page in the section “Group members”.
• Paging Multicast - is suitable for large paging groups and requires phones supporting multicast, on the same local subnet as 3CX. Define the target multicast address to send the audio stream to and then use the provisioning configuration method to configure the IP phone to listen to this address.
• Click “Save”.

https://www.3cx.com/docs/manual/call-center-queues/#h.58a1izpsus0k

I did try just dialing the ring group number and that didn't work either.

 

[Evolute IT]

1. What phones do you use?

2. The dial code is required for the feature to work but not necessary if you use paging ring group. Also, Multicast doesn't work the same AT ALL. Regular paging should just work if you're using supported phones.

3. Make sure you're on the latest v20 version.

 

[stpaulschurch]

We're not doing multicasting ATM.

We are using Yealink models:
T31p for public phones and regular user phones
T58 for front office phone
T56a for my phone
A number of handsets for the W60b cordless

Last I checked they all claimed to be able to do intercom

We are on the latest v20, hosted at Azure with our SBC run on a Rasberrypi in house.

So, you're saying that, instead of dialing *74, I should just dial the ring group?

 

[Evolute IT]

Yes, usually you just dial the ring group and it sends the Alert-Info automatically to trigger the intercom.

However, this could be a v20 bug. I remember seeing people saying it doesn't work in the latest official v20, but might work in the U1 beta.

 

[stpaulschurch]

Ah. Good to know. I'll give it some time to see if it's a bug. Because, as it stands, everything appears to be setup as it's supposed to be. Thanks!

 

[american10]

I'm also having this same issue trying to intercom extensions after my v18 to v20 upgrade over the weekend. Is this still broken in v20?