Based on this thread -
https://www.3cx.com/community/threads/paging-ring-group-putting-current-call-on-hold.63010/
@YiannisH_3CX
Seems to indicate that since "intercom and hunts" are the same - and accepting multiple calls will allow the "page" to barge in.
@Harry Torres Didn't update to let us know if what he tried helped, but looking at the templates I see
features.intercom.barge = 0
which technically should fix this..
Is anyone else experiencing this issue and is there any resolutions so that page should NOT put a call on hold? (Yealink T7/9)
https://www.3cx.com/community/threads/paging-ring-group-putting-current-call-on-hold.63010/
@YiannisH_3CX
Seems to indicate that since "intercom and hunts" are the same - and accepting multiple calls will allow the "page" to barge in.
- I understand the logic, but utilizing the same "function" under the hood doesn't mean you can not change the way they work -
- Based on the above we have had complaints where soft phones for example ring during a page group call.
@Harry Torres Didn't update to let us know if what he tried helped, but looking at the templates I see
features.intercom.barge = 0
which technically should fix this..
Is anyone else experiencing this issue and is there any resolutions so that page should NOT put a call on hold? (Yealink T7/9)
