Paging Ring Group putting current call on hold

[Harry Torres]

Hello,

A setup at a current customer, with Fanvil X6 phones, is having an issue where if someone is on the phone, and someone else pages the group, it places that call on hold for the person on the phone. Is there any way to stop that from happening? If someone is on the phone, they should not get that page...is the ability to receive multiple calls on a ring group an issue?

Thanks.

 

[cobaltit]

is the ability to receive multiple calls on a ring group an issue?

Not sure, seems pretty simple to test though....

 

[Harry Torres]

At my office I have a Yealink, Grandstream, and a Fanvil...I keep a mix here...when I tested it myself, I put myself on a call with my yealink, and when paged, the call wasnt put on hold...then I placed myself on a call with the fanvil, went to another phone to do a page, and it put the call on hold...something on the phone itself I need to modify?

 

[Sean Glasspool]

I had this problem.
Couple of things fixed it for me.
1) G722 doesn't seem to play nice with paging.
2) Remote STUN doesn't play nice with paging.

My issues with a couple of Algo pager units went away when I introduced an SBC.

 

[Harry Torres]

It seems to only be with Fanvil phones, and G722 is not at the top of the list...and the group is set to Paging (as opposed to Multicast). Simple use.."Mike you have a call on Park 1" type of thing. What I'm thinking as I said earlier, I have not tested it yet, is disabling the parameter that allows another call to come in on a ring group if the user is on the phone...except I can't seem to remember what its called...

 

[YiannisH_3CX]

I was able to replicate the behaviour with a Fanvil device which has the option "Accept multiple calls" enabled under the extensions forwarding rules. As paging groups are not actually Ring Groups, the PBX will send the second (paging) call to the extension and this is consistent will all phone brands.
What changes is how the phone handles the second call. On Yealink devices for example you will see the paging call as a normal call waiting on line 2. Fanvil phones answer the call immediately since it's a paging call and has the auto answer flag. In my opinion both behaviours are correct and it is a matter on how you want to handle calls. To avoid this from happening with Fanvil phones i would recommend disabling the option "Accept multiple calls" from the extensions forwarding rules.

 

[Daryl Bajuelo]

Im using yealinks t41s on the company I have being figuring out if there is way to deactivate the hold bottom from the phones so the user only can place the call on park, I know there is an option in the phone itself that deactivates the key, but we have over 50 phones. is there any way i can send a provision form 3cx that will do this on all phones.

 

[Harry Torres]

@YiannisH_3CX awesome thank you for that suggestion. I'm putting it into consideration since it will keep the phone from even getting a call from another extension while on the phone. Which Fanvil device did you try this with? I know for my other customer, using Fanvil X5S phones, after I did the available firmware update, I tested it and the paging call didn't put the current call on hold.

 

[YiannisH_3CX]

I tested this with an X3s and an X6 however i tested this before i updated the phones to the latest firmware that was released last week.
I did test a Fanvil X5s with the new firmware just now and i find that the behaviour is consistent. The phone puts the original caller on hold and picks up the paging when the option "Accept multiple calls" is enabled.

 

[Harry Torres]

I tested this with an X3s and an X6 however i tested this before i updated the phones to the latest firmware that was released last week.
I did test a Fanvil X5s with the new firmware just now and i find that the behaviour is consistent. The phone puts the original caller on hold and picks up the paging when the option "Accept multiple calls" is enabled.

@YiannisH_3CX before I consider disabling the Accept Multiple Calls option on extensions, would disabling the ALLOWUSEBUSYOPTFORGROUP parameter help this? Or is there an option on the phone UI or template I can modify? Thank you for assisting me with this.

 

[YiannisH_3CX]

As you may know the option "ALLOWUSEBUSYOPTFORGROUP " is not supported so all my tests were done with the option off. So i do not think that the behaviour will change by disabling the option.
As far as i know there is no template or UI change that controls this. It is down to the firmware of the device and how Fanvil decided to handle this scenario.

 

[Harry Torres]

As you may know the option "ALLOWUSEBUSYOPTFORGROUP " is not supported so all my tests were done with the option off. So i do not think that the behaviour will change by disabling the option.
As far as i know there is no template or UI change that controls this. It is down to the firmware of the device and how Fanvil decided to handle this scenario.

I am trying one thing that I changed in the UI, and I'm waiting to see if the setting sticks (I tried reprovisioning after the fact, and its still there), because if I have to disable allow multiple calls option I will, but I'm really trying not to. In the UI, on the left click on Phone Settings, then on the page, Intercom Settings, I disabled intercom barging. I'll keep you posted.

Thank you for all your help.

 

[YiannisH_3CX]

Let us know how that goes.