If your organization has a directory service like Microsoft Active Directory or OpenLDAP, you can load these directories to all your phones by creating a new corporate directory. If your organization has multiple directories, you can add each of them, designate one as the system default, and then override that default on individual devices as needed. By using corporate directories, you only have to make updates in a single location and your changes will mirror on all your phones automatically. Those responsible for implementing a corporate directory should be familiar with LDAP and work closely with their directory system admin during setup.
1. Log in at my.jive.com/PBX.
2. Click Corporate Directories in the left sidebar and then click [ADD CORPORATE DIRECTORY].
3. Enter a Name, Host (optional), and Port for the corporate directory.
4. Click the checkmark icon and then click the newly added corporate directory to edit its settings.
5. From the General tab, you can customize the following:
- Connection settings
- Host: Host DNS name or IP address of the directory server. Devices must be able to resolve this address since the searches are executed directly from the phone to the directory server.
- Port: The default LDAP port is 389. It is unusual for this value to be different. LDAPS is not always supported. As a result, make sure to use a username with read-only access. If LDAPS is deployed, the correct port will need to be entered (usually 636).
- Use TLS: Enable this setting to use LDAP over TLS. This is only supported on Polycom devices and where the LDAP server has a valid certificate.
- Bind DN: The distinguished name (DN) with which devices will bind (authenticate).
- Bind Password: Password required for the phone to authenticate as the given Bind DN. Click Show Password to display/hide the password. LDAPS is only supported on Polycom phones and only if an appropriate certificate (see the Certificate tab below) is uploaded. Unless an appropriate certificate has been uploaded, the bind password will be sent in clear text across the network. If you do not have a valid certificate, it is highly recommended that the bind DN should be a read-only user. Certificates are only usable on Polycom devices. On all other manufacturers handsets, the bind password will ALWAYS be sent in clear text. Failure to use credentials with read-only access can lead to the directory service being compromised.
- Search settings
- Search base: Directory location where searches will be based. We recommend using a narrow search base. The impact of the searches can be minimized by using a more specific search base (i.e. “ou=Users,dc=example,dc=com” is better than “dc=example,dc=com”).
- Search scope: Depth of the search through the directory tree.
- Subtreeb: Searches all entries in and below the location specified in the search base.
- One level: Only searches entries in the location specified in the search base and not any subdirectories.
- Filter: Optional filter added to all searches made by the devices against the directory server. We recommend using a narrow filter. Defining a filter like “(objectclass=person)” can significantly reduce search load in certain directory implementations.
- Display name attribute: Attribute used as the name in results returned to the device in searches. Used for Cisco/Linksys SPA devices. For Polycom SoundPoint IP devices, the results are displayed [Last Name Attribute], [First Name Attribute].
- First name attribute: Attribute that contains the first name in the directory. Devices will also filter against this attribute in searches.
- Last name attribute: Attribute that contains the last name in the directory. Devices will also filter against this attribute in searches.
- Phone number attributes: A comma separated list of phone number attributes in the directory. In the case of Cisco/Linksys SPA devices, the first listed phone number is the only number that the device can directly dial. The rest are only displayed for informational purposes.
6. If you have a Polycom, you can add the certificate in the Certificates tab.
- Add the certificate in the provided text field in base64 PEM format. Make sure to copy and paste the entire contents of the certificate file provided by your certificate authority within the header -----BEGIN CERTIFICATE----- and footer -----END CERTIFICATE-----. Multiple certificates can be entered as needed.
- If your LDAP server is using a certificate signed by a certificate authority that is ‘trusted’ by Polycom, then no settings are needed on this page.
- If you don’t have a certificate signed by a certificate authority that is trusted by Polycom, then you must provide the “public certificate” of the signing certificate authority. You will generally need to contact your certificate authority to obtain this.