Got a customer looking at deploying CUPS/CUPC 7X with CUCM 7X and integrating with AD where all users belong to a single OU. Customer wants to be able to select certain users only to be available/visible in the search directory of CUPC. Question I have is do the users ONLY show up in the directory if they are configured in CUCM with the proper user info? If not, what would be the best way to handle this?
Unfortunately there is no way for CUPS to say yes to show this user and no to show that user.
The trick some people use in CUCM LDAP sync is to put a ~ is front of the first name. It seems to then skip that name in the LDAP sync. But since CUPC is actually making an LDAP call into the LDAP server in a certain OU, it may not be possible. The only way is move those users to a different OU so CUPC users can not see them in the directory.
To me, if other people show in the directory it's not a big deal. If they have Exchange, they show in the GAL anyways. If they do not have CUPC configured, it not show their Presence such as meetings, on/off hook. They will be in the directory, but nothing more. (click to call them or click to email, no IM, etc.
The way CUPS handles is that users can block other users from contacting them via IM. Basically setting up restrictions.
Never used CUPC but if CUPC account uses an LDAP account to do a look up, can you use LDAP permissions to deny access to those problem user accounts, resulting in them not being listed? I think you can do it on OUs, not sure about users though.
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...