[cisco-voip] UCM LDAP Filters stopped working

[Chris Ward (chrward)]

I agree with Jason here. Maybe a DNS failure or something like that... Referrals can really mess up an LDAP search.

+Chris
Unity Connection TME

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Tuesday, April 16, 2013 6:49 PM
To: Dana Tong; cisco-voip at puck.nether.net (cisco-voip at puck.nether.net)
Subject: Re: [cisco-voip] UCM LDAP Filters stopped working

Sure the problem isn't on the AD side? How do you know they didn't move, etc? I would run a Wireshark of Full Sync to see what is going on.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Dana Tong
Sent: Tuesday, April 16, 2013 6:42 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>)
Subject: [cisco-voip] UCM LDAP Filters stopped working


Good morning all,

I have a UCM cluster and Unity Connection which is LDAP integrated. The system has been in pilot for about 6 weeks.
Yesterday the LDAP filters stopped working and the users were marked inactive.

As a work-around I've removed the filters and re-sync'd. But this is not working.

The original filter was:   (&(objectclass=user)(telephoneNumber=*)(!(UserAccountControl:1.2.840.113556.1.4.803:=2)))
I have tried: (telephoneNumber=*)


And it still doesn't work. It's quite odd really. Why would this stop working overnight?

Any thoughts out there?

Cheers
Dana



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