[cisco-voip] CUCM AD integration

[Ahmed Elnagar]

Watch out for this bug.

If you are using CUMA you must use sAMAccount

""" CUMA does not support any LDAP attribute for user ID other than sAMAccountName"""

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtd78546 

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Thursday, April 29, 2010 3:27 PM
To: Erich Novak
Cc: charl.crofton at gmail.com; cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] CUCM AD integration

You can set this in the ldap directory settings as well but keep in mind this will impact the userid's for all endusers sync'd in via ldap. 

There is also a service parameter to enable alphanumeric userids for EM.

-Ryan

On Apr 29, 2010, at 8:17 AM, Erich Novak wrote:

> Hi,
> 
> it is possible, but not via GUI, you can change it in the Database.
> 
> You need an Active Directory field with the DN of the User (ie. IPPhone) and take care that it is unique in AD.
> 
> Next you log on to the CUCM CLI via ssh, ->
> 
> admin:run sql select * from ldapsystemconfig
> pkid                                 useridattributename tkldapserver syncenabled
> ==================================== =================== ============ ===========
> a1cdb5e3-aaf4-4db0-bfa9-b7c872622365 sAMAccountName      1            t
> 
> 
> you can update the useridattributename to anything you want via run sql update...
> 
> but take care, this also has impact on CUPS etc.
> 
> brgds
> Erich
> 
> -----Ursprüngliche Nachricht-----
> Von: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] Im Auftrag von Ed Leatherman
> Gesendet: Donnerstag, 29. April 2010 14:01
> An: charl.crofton at gmail.com
> Cc: cisco-voip at puck-nether.net
> Betreff: Re: [cisco-voip] CUCM AD integration
> 
> I don't think this is possible Charl. Extension Mobility uses the
> userID and PIN for login, I don't know of a way to change that.
> 
> On Thu, Apr 29, 2010 at 6:03 AM, Charl Crofton <charl.ccrofton at gmail.com> wrote:
>> HI,
>> 
>> Let me try and explain this correctly:
>> 
>> CUCM integrated with AD & using Extension Mobility
>> 
>> So userid will be something like: jsoap (must be username to keep it
>> uniform across the enterprise)
>> My Device Profile will be something like: 12345 (user jsoap's extension number)
>> Device Profile is associated with user jsoap.
>> 
>> I want users to log into the phones with their extension number
>> (12345) instead of having to use their username (jsoap)
>> 
>> Is this possible and if so, how?
>> 
>> thnx
>> charl
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> 
> 
> 
> 
> -- 
> Ed Leatherman
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.