Thanks for your response. Is there any time frame on the fix, as this could prevent a rollout to the organisation if generic accounts, etc show up in our directory searches.
And to clarify, using Jabber for Windows all config is done in the XML file now, so when the issue is rectified I would simply add the below to my directory section in the XML file, to only return users that have a value in the ipPhone attribute.
and therefore in the LDAP search context field, the following would no longer be required
Base filters specify the criteria for the search and Search bases specifies where in Active Directory to begin the search.
So you will specify your criteria in attribute and search context in attributes. You can specify upto five search bases according to the admin guide.
I can't give a timeline when CSCua39052 will be fixed. It is open as a high priority defect as other customers are facing same problem. Can you give me the customer's name? I can then update the bug with more details. This will help to prioritize this defect.
Thanks for your reply. If I understand correctly you would put the search in this order, for example.
which would be the same as LDAP search context, that is no longer required
The organisation I work for is the Gold Coast City Council, Queensland, Australia. As mentioned we are hoping to go into production in the next month once we have few issues sorted, which are with TAC currently.
That is correct. Regarding the fix of CSCua39052, this defect will be triaged in the next few weeks. At this point we don't know the root cause therefore cannot suggest a timeframe. Please keep tracking this defect via bug toolkit for the expected release.
I tried both options suggested, and both did not work. In fact I lost all users in the directory when a search was attempted and my name changed to the sAMAccountName from my real name.
Then I returned back to my original xml file as below, and all of a sudden it worked..It is now only recognising users in that have a value ipPhone. I will continue to monitor to make sure it continues to work but hopefully this is now fixed.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...