Solved Paging Ring Group Terminates after v20 Upgrade

[UAC]

Hello,

We recently upgraded to v20 and it appears to have impacted our paging ring groups. Existing and new paging ring groups terminate the call within 1 second, but calling the phones directly work fine. Any advice on debugging?

Thanks!

 

[NikolasA_3CX]

Hi @UAC

Navigate to System >> Dial Codes >> Under the paging dial code add *8 and try again.

 

[UAC]

That worked! We had a different dial code in there but changing it to *8 allowed the paging ring groups to work again. Thank you!!

 

[NikolasA_3CX]

We are glad the issue has been resolved

 

[Dan MacFarline]

Is there an explanation as to why this needs to be changed to make paging work? I have quite a few systems set up with paging that all use a different dial code. It will be a pain to have to change all of them!

 

[NicholasP_3CX]

You may have had a dial code which was clashing with others. *8 is not used anywhere, so this wiped out any doubt for clashes.

 

[hfit.co.uk]

I have the same problem, whatever i put the code to it cuts the call and in the log i can see it says target is busy

 

[BlueWaterNets]

Is there a technical explanation for this? I recently updated a v18 system to v20, which I had just set the calling code to *51 (not used in the system), after upgrade to v20, paging did NOT work. After changing the *51 code to *8 as pictured above, it began to work again. quite odd.

 

[OlegR_3CX]

@BlueWaterNets
Thank you for the feedback. The dial code needs to be *8 as it can be the case of the conflict as shown in the screenshot of the very fist reply, those are default settings.

 

[BlueWaterNets]

In v18 when we set this up, it was blank. We used *51 which didn't appear to be used. after the upgrade to v20, issue. I've set the client to *8 as you noted and confirmed it's working. Question for you - when we create a BLF speed dial - do we do *8xxx or just the extension defined for the page (xxx) ??

 

[Charles_3CX]

For paging a ring group, just the ring group number is required. To intercom directly to an extesnion, you need to dial *8Ext.

 

[SniffwareINC - Doral - FL]

Hello, after several testing, we figured out the problem on the paging is not the *50 and the extension, or *8 and the extension, the problem is the right under the user account. By default the account is under user, if you want a trustful paging you need to elevate the security to Recepcionist, after that, everything should work.

 

[SniffwareINC - Doral - FL]

For paging a ring group, just the ring group number is required. To intercom directly to an extesnion, you need to dial *8Ext

Hello, after several testing, we figured out the problem on the paging is not the *50 and the extension, or *8 and the extension, the problem is the right under the user account. By default the account is under user, if you want a trustful paging you need to elevate the security to Recepcionist, after that, everything should work

 

[SniffwareINC - Doral - FL]

For paging a ring group, just the ring group number is required. To intercom directly to an extesnion, you need to dial *8Ext.

Hello, after several testing, we figured out the problem on the paging is not the *50 and the extension, or *8 and the extension, the problem is the right under the user account. By default the account is under user, if you want a trustful paging you need to elevate the security to Recepcionist, after that, everything should work

 

[SniffwareINC - Doral - FL]

You may have had a dial code which was clashing with others. *8 is not used anywhere, so this wiped out any doubt for clashes.

Hello, after several testing, we figured out the problem on the paging is not the *50 and the extension, or *8 and the extension, the problem is the right under the user account. By default the account is under user, if you want a trustful paging you need to elevate the security to Recepcionist, after that, everything should work