Configuring Corporate Directory support

Last Updated : Feb 25, 2020 |
Prolog information
Metadata
Keywords:
Corporate directory allows UNIStim and 39xx endpoints to display and access a corporate-wide telephone directory.
Before you begin
Corporate Directory support requires the use of Avaya Aura® Device Services (AADS). Ensure that AADS is available in your Avaya Aura® solution prior to performing this procedure.
  1. On the endpoints, set CLS to CRPA.
  2. Log on to System Manager by using administrative credentials.
  3. On the System Manager web console, navigate to Elements Avaya Breeze®Configuration.
  4. Click Attributes.
  5. Depending on whether you want to configure the Corporate Directory support at a cluster level or a global level, do one of the following:
    • Click the Service Clusters tab, select the cluster, and then select the service as DeviceAdapter.
    • Click the Service Global tab and select the service as DeviceAdapter.
  6. On the Attributes Configuration page, navigate to the Contacts group and do the following:
    1. In the Enable Corporate Directory field, in Effective Value, click Yes to enable Corporate Directory support.
    2. In the Avaya Aura Device Services (AADS) FQDN field, in Effective Value, type the FQDN that you want to use to access the AADS server.
    3. In the Avaya Aura Device Services (AADS) Port field, in Effective Value, type the port number that you want to use to access the AADS server.
      ADDITIONAL INFORMATION:
      The default port is 8443 or 443.
    4. Click Commit.
  7. Click Services Inventory Manage Elements.
  8. On the Manage Elements page, on the Manage Elements tab, click New and configure AADS.
    ADDITIONAL INFORMATION:
    For more information, see Avaya Aura® Device Services documentation.
  9. Do the following to assign Session Manager to a data center and pair the assigned data center with Avaya Aura® Device Services:
    1. On the System Manager web console, navigate to Elements Session Manager System Status.
    2. Click User Data Storage.
    3. On the User Data Storage page, click the Data Center tab.
    4. Select the data center for which you want to assign the Session Manager and click Edit.
    5. In the Data Center field, click the configured data center and click Commit to save the changes.
    6. Click the Backup and Restore tab.
    7. Click Configure Backup and enter the required details of the backup server.
    8. Click Test Connection to check the connectivity of the data center and Session Manager and click OK to exit the dialog box.
    9. On the System Manager web console, navigate to Elements Session Manager Session Manager Administration.
    10. Click the Session Manager Instances tab.
    11. Select the Session Manager instance that you want to pair with Avaya Aura® Device Services and click Edit.
    12. In the Data Center field, click the configured data center assigned to Session Manager.
    13. In the Avaya Aura Device Services Server Pairing field, select the available and configured Avaya Aura® Device Services for pairing.
    14. Click Commit to save the changes.
  10. Do the following to generate and export the SIP certificate:
    1. On the System Manager web console, navigate to Services Inventory
    2. Click Manage Elements, and then select the Avaya Breeze® platform server.
    3. Click More Actions Manage Identity Certificates.
    4. In the Manage Identity Certificates window, click the SIP certificate, and then click Export.
  11. On AADS server, import the certificate that you generated in Step 10 to add the FQDN of Avaya Breeze® platform to the trusted hosts.
    ADDITIONAL INFORMATION:
    If Avaya Breeze® platform, Session Manager, and AADS are on the same System Manager, then AADS can register itself on the System Manager to get the certificates automatically. You can also import System Manager root CA to the AADS server.
    For more information, see the Avaya Aura® Device Services documentation.
  12. Create users on the LDAP server. For corporate directory to function, only one LDAP user is required. The login name of the user must match the FQDN of the Avaya Breeze® platform Asset Interface.
    ADDITIONAL INFORMATION:
    For more information about LDAP server configuration, see Deploying Avaya Aura® Device Services guide.
  13. Add the CS 1000 users to the System Manager UPM. Device Adapter updates the Corporate Directory data with the System Manager UPM data.
    ADDITIONAL INFORMATION:
    Do the following for various CS 1000 releases:
    • If you run CS 1000 release 6.0 or earlier or releases 7.0 through 7.5, and use a simple CSV file import, do a bulk import into UPM according to the CSV format that UPM supports. For more information, see the Administering Avaya Aura® System Manager guide.
    • If you run CS 1000 release 7.0 through 7.5 and sync the user accounts for Corporate Directory from LDAP, import the LDAP users into UPM. For more information, see Administering Avaya Aura® System Manager guide.
    • If you run CS 1000 release 7.6, which is integrated with System Manager, you need not do anything.
      For CS 1000 release 7.6, all users are included in the Corporate Directory, regardless of whether you enable or disable the