[cisco-voip] CUPS / LDAP: another question

[James Buchanan]

Actually, that was the Cisco TAC solution when it didn't work right. Of
course, I also had to upgrade to 6.0(3) and get a bug-free version of
the CUPC client for this to work. Had I known that CUP would puke all
over itself if I used the extensions as user IDs I would have used the
AD username (samAccount).

 

From: Rick Mancinelli [mailto:rmancinelli at bisginc.com] 
Sent: Friday, August 08, 2008 8:08 AM
To: James Buchanan; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CUPS / LDAP: another question

 

James-

 

GREAT idea.... Very nice "MacGiver" solution.  ;-)

 

Rick

 

________________________________

From: James Buchanan [mailto:jbuchanan at ctiusa.com] 
Sent: Thursday, August 07, 2008 9:17 PM
To: Rick Mancinelli; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CUPS / LDAP: another question

 

Hello,

 

Having set this up this way a couple of times, I also have hit this. In
the CUPS admin, you must change the samAccountID (I believe) attribute
to point to the telephoneNumber field in order to match. This is
somewhere in the LDAP settings.

 

Thanks,

 

James

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Rick Mancinelli
Sent: Thursday, August 07, 2008 7:01 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CUPS / LDAP: another question

 

Hey folks..

 

I inherited a CUCM-BE install wherein all the users were set up as
extension numbers.  This same client is now installing CUPS and, in
order to get LDAP integration working properly, it looks like I need to
recreate all the users to match their Active Directory user ID's.  Is
this correct or am I missing something obvious?

 

Thanks,

Rick

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080808/29742054/attachment.html>