Hi, can anyone advise on how to configure the IP7000 Corporate Directory to work using the AD's Global Catalog via LDAP
|Phone Model||SoundStation IP 7000|
|Part Number||3111-40000-001 Rev:J|
|UC Software Version||18.104.22.16807|
|BootROM Software Version||22.214.171.12453|
I've tried and read many posts by SteffenBaierUK (Kudos!) but the result is still unable to search or list the Global Catalog of the AD via LDAP.
welcome to the Polycom Community.
I am not aware of any issues but would suggest to contact your Polycom reseller as they are your Tier 1 support contact.
Set the LDAP logging level to at least 2 / event 2 and provide them with the configuration you have used and the <mac>-app.log & <mac>-boot.log file.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
I've engaged help, however there is still no breakthrough thus I like to seek help from anyone here.
This guide you have posted, I noticed in the example advised - dir.corp.port="389" is the usual LDAP port.
However we would like to use the Global Catalog of MS AD DS, could you or anyone please advise on an example working configuration that would be able to use this?
as stated in the FAQ and the header of the Polycom Community we as Polycom employees do not provide free support.
Your Unit was shipped at the 06/05/2012 and therefore is still within its warranty time and therefore any support should come from your Polycom reseller.
I have created the FAQ to have a central place for certain issues and configuration examples but am unable to cover every possible setup.
The Global Catalog scenario is not covered in the FAQ but may still work.
The LDAP Port Parameter is as specified and should cover the port 3268:
dir.corp.port 0, Null, 1 to 65535 389 (TCP) 636 (TLS) The port that connects to the server if a full URL is not provided.
The FAQ post contains a link to an extensive LDAP / Corporate Directory example including the troubleshooting of it and I would strongly advise to check your logs as suggested above.
In order for you to proceed from a support perspective has been already made clear and should be followed up.
You may get another community member that has already tested this to reply but so far nobody has done so.