So those rules worked. You can block IM, phone status or both. "Disallow all except" or "allow all except" style of rules from what I can see. The IM prevents the blocked user from STARTING an IM' session with you. You can start an IM session with the blocked user and that user can respond back. That's pretty neat.
Can't see a way for the administrator to do the same thing for the user. So the admin must have the LDAP username and password for the administrator to create these rules. This statement from the SRND P22-31 pretty much kills the administrator idea: "Presence Policy for Cisco Unified Presence is controlled strictly by a defined set of rules created by the user." Haven't explored the required Policies vs the User Defined Policies. ________________________________ From: Cristobal Priego [cristobalpri...@gmail.com] Sent: Friday, June 12, 2009 1:57 PM To: Michael Ciarfello Cc: Jonathan Charles; ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] Blocking CUPC clients from seeing presence of other CUPC clients... Thanks Michael I'm going to check the SRND guide. I have a customer that uses presence and wanted something like these. I went with Cisco and open a TAC case and went to developer support and we have to submit a product enhacement in order to accomplish something like this. however if we can do this through rules, that's great. I'm going to check it out 2009/6/11 Michael Ciarfello <mciarfe...@iplogic.com<mailto:mciarfe...@iplogic.com>> I think I'm on to something but it's late to fully test. Will resume tomorrow. Presence groups don't seem to do anything to CUPC--only on the phones themselves. Remember there is a difference between seeing presence status for a BLF/SD and the "X" directories presence status (corporate, missed, etc.) BLF/SD doesn't honor presence groups since an administrator configures BLF. Still need proper subscribe css assigned though. Presence groups affects X directories presence status. In the CUPC client, under preferneces there is a privacy option. You can add individual users who won't see your status or be able to send IM. They will still appear in the contact list and can still be added, but that seems useless to do. Like talking to a brick wall. In the CUP CCMUSER pages there are more privacy options I haven't fully explored yet. the CCM 7.0 SRND talks about Visibility Rules, Reachability Rules and Filtering Rules. Thanks for the good question ________________________________________ From: ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com> [ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com>] On Behalf Of Jonathan Charles [jonv...@gmail.com<mailto:jonv...@gmail.com>] Sent: Tuesday, June 09, 2009 7:21 PM To: ccie_voice@onlinestudylist.com<mailto:ccie_voice@onlinestudylist.com>; cisco-v...@puck.nether.net<mailto:cisco-v...@puck.nether.net> Subject: [OSL | CCIE_Voice] Blocking CUPC clients from seeing presence of other CUPC clients... How do you block CUPC users from seeing other CUPC users? I have changed Presence Groups for user A and User B so they are disallowed subscriptions... I have changed SUBSCRIBE CSS to not include the partition of the other user... I even changed the LDAP profiles in CUPS so they couldn't see the other OU... and they can still see the presence status, still send/receive IMs... Now, once I changed the LDAP search base on CUPS, you can no longer search for the user and add em to your buddy list... but no presence info is blocked... How do you block this for CUPC? Jonathan
