Group Rights after Update to 16.0.7

[treynolen]

Customer reported that they could no longer pickup other ringing extensions (*20*) after update to 16.0.7. The "Perform operations (divert, transfer, pickup)" right was granted to extensions at the group level, but after the update this right was no longer working. The fix was to assign the right to each extension itself. This had been working since 15.x and just stopped after the latest update. Has anyone else seen issues with group rights not propagating to the extensions? I'm not sure if only this particular right is affected.

 

[JohnS_3CX]

Hi Trey,

If the Group has the option ticked, then I would expect that the groups members should also have it automatically. If you had to assign it manually then it means that the extensions were not following.

What you can do is edit the Group and disable the right (and save). Then edit it again and add the right, this should overwrite the setting for all members.

While testing a local PBX here, the upgrade from U6 to U7 did not affect my extensions, their rights were not revoked after the update.

 

[treynolen]

Thanks. Unfortunately, this is one of our less tolerant customers so I'm not able to play around with their settings, but if I see it happen on another system, I'll try the approach you outlined. Thank you for testing.

 

[Thiek]

Trey, I thought we had this problem as well, one of our sites reported this so I did some testing on our dev system which did not have update "7 Final". Before installing it I did "pickup" tests and it worked just fine and after the update (was 16.0.7.1078) it continued to work with no issues. Also, we do not have "Perform Operation (divert, transfer, pickup) checked off at the Group level under User Rights, but for those who pickup calls within their dept., using a pre-programmed BLF key on their phone, they do have this option checked under their Extension/Profile under the Rights tab.

I was thinking this issue that was reported, can't pick up each other's calls, might be related to an extension being listed under more than one Group. Our extensions will be under the group Default, and they will also fall under one other group which is used to designate where their phone is located in the building, and this group is then used under Settings>General>Emergency Numbers for 911 calls. The only issue I came across, for some people/extensions, their Group Membership (Rights tab) was flipping to the secondary group as to Default group and this did mess up specific individual settings. Plus, I could not get it to flip back to Default and save. Eventually, I got it to stick. I had to delete their ext. from the secondary group, which by default set their Group Membership back to Default, and then add their ext. back to the secondary group.

When I called the site and worked with someone who was actually experiencing the issue, it was a missing BLF key on each of the dept. phones. Somehow x4455 got deleted from 5 phones, I simply had to add the BLF key to each ext.

 

[treynolen]

I was thinking this issue that was reported, can't pick up each other's calls, might be related to an extension being listed under more than one Group. Our extensions will be under the group Default, and they will also fall under one other group which is used to designate where their phone is located in the building, and this group is then used under Settings>General>Emergency Numbers for 911 calls. The only issue I came across, for some people/extensions, their Group Membership (Rights tab) was flipping to the secondary group as to Default group and this did mess up specific individual settings. Plus, I could not get it to flip back to Default and save. Eventually, I got it to stick. I had to delete their ext. from the secondary group, which by default set their Group Membership back to Default, and then add their ext. back to the secondary group.

Interesting. I've got to try to remember the customer we were seeing this issue with (I mentioned "intolerant" but that doesn't narrow it down a whole lot ). If I can find out who it was, I'll take a look at the group setup to see if there are multiple groups and make sure that all of them have the proper permissions.