Saturday 10 March 2012

Cisco Unified Communications Manager and LDAP Integration

Cisco Unified Communications Manager v6 (formerly called Call Manager and then Unified Call Manager) can synchronise its user list with Active Directory (it’s actually a one way synchronisation), and can authenticate users against Active Directory. It does this using LDAP. That’s no surprise and pretty standard. Unfortunately, it doesn’t allow you to specify any search filters. You specify the base DN (or multiple base DNs) and that’s it. It seems that if an account in AD has a first name and last name CUCM adds it to its directory. The account doesn’t need to have a telephone number, it can even be disabled. Note that you can only synchronise accounts – CUCM ignores Contacts.

Didn’t anyone at Cisco think that their clients might possibly want to filter their imports? Did it not occur to them that the structure in AD might not reflect the way clients want to import users into CUCM?

It’s just not good enough!

1 comment:

  1. The most worthwhile operators, or Tier 1xbet 1 operators spend a lot as} 18% of their gross income on bonuses so as to to} appeal to new clients. However, Tier 2, or lower-level operators, who wouldn't have the identical budget or native licenses needed to promote, are almost totally reliant on bonuses and affiliate schemes. If fraudsters are able to to} benefit of|benefit from|reap the benefits of} the offers, you’re not simply risking short-term damages, you’re seriously placing your organization at risk for the long term|the lengthy run}. By default, most systems are weak on detecting whether or not or not a single individual has a number of} accounts. As a end result, bonus abusers can easily sign a lot as} receive the identical signup bonus by registering with a number of} identities.