Has anyone run into an issue where group membership enable/disable can't be toggled?
We're working on a 2 site SCN system with the HG's at the primary location (have tried at both and get the same result).
Members at the remote location can not toggle their HG membership; and, we can not enable or disable the membership through Manager. We can remove members from the groups, but the users can't use an enable button to toggle whether they get calls or not, nor can we just uncheck them in Manager. Within Manager, we can uncheck a user, then click OK without issue, but when the screen refreshes, the users come back as checked every time.
We've tried creating new groups, deleting and recreating users, etc but get the same result each time. Local users (the ones on the primary system) do not have this issue - only the users on the other system connected via SCN.
We've changed the SCN trunk from fallback to normal and recieved the same results as well. Our next step is to delete the remote users from the groups and delete the SCN trunk completly, reboot each system, then re-add the trunks to see if this is still present. After everything we've tested, we don't think it'll work and this is feeling more and more like an Avaya case to us. Admittadly I may be forgetting something since we've been doing a lot more Server Edition than SCN, but I feel like we've covered all of our bases.
We're working on a 2 site SCN system with the HG's at the primary location (have tried at both and get the same result).
Members at the remote location can not toggle their HG membership; and, we can not enable or disable the membership through Manager. We can remove members from the groups, but the users can't use an enable button to toggle whether they get calls or not, nor can we just uncheck them in Manager. Within Manager, we can uncheck a user, then click OK without issue, but when the screen refreshes, the users come back as checked every time.
We've tried creating new groups, deleting and recreating users, etc but get the same result each time. Local users (the ones on the primary system) do not have this issue - only the users on the other system connected via SCN.
We've changed the SCN trunk from fallback to normal and recieved the same results as well. Our next step is to delete the remote users from the groups and delete the SCN trunk completly, reboot each system, then re-add the trunks to see if this is still present. After everything we've tested, we don't think it'll work and this is feeling more and more like an Avaya case to us. Admittadly I may be forgetting something since we've been doing a lot more Server Edition than SCN, but I feel like we've covered all of our bases.
