All is working well on this recent install except:
the organisation has about a dozen users who are members of the domain admins (a protected group with inherit permissions unchecked) who all reside in a container called 'administrators' separate from other users. We can't add or delete these administrators without checking 'grant inherited permissions') and running the permissions wizard. Once added everything is fine for a while but then the 'inherited permissions' box on each user reverts automatically back to unchecked each night and we are unable to edit these users the next day (e.g. can't change a PW or uncheck first time enrolment) and when they send a message to an internal subscriber their names DO NOT appear in the from field of the voicemail.
Is there anyway I can set the required permissions independently for each user in the administrator container or make the 'allow inherited permissions' checkbox stick?
A better, more secure way to handle this problem would be to have your Domain Admins use separate accounts from their Unity enabled ones. Users should not be performing normal day to day operations logged on with accounts that have this level of privilege. But with your existing design, this may help.
We can now modify protected user accounts from the SA but they still don't get tagged in the from field on subscriber to subscriber messaging. Can I be cheeky and ask if you have any ideas on this issue?
Are these users on a different Unity server than your other internal subscribers? This almost sounds like identified subscriber messaging is not working. What does the From field say when one of these admin users sends a voice message to your internal users?
No other Unity server is present. The ISM works for all other users. They are identified as the message sender in the 'from' field of the email. The protected domain admin users get 'unity messaging system' in the from field with their extension number in the subject field. I can get it to work for the admin users by going into advanced options and checking the inherit permissions tab and then running the permissions wizard on the container. We then do a test and ISM works properly for a while. However, overnight the permissions are reversed and we are back to square one. Its only a few users so I'd like to set the permissions manually but I don't know which permission on which account would control the information in the from field!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...