Administration of the Dynamic Configuration service

Last Updated : Jun 10, 2026 |

With the Dynamic Configuration service, Avaya Aura® Device Services can dynamically retrieve and deploy automatic configuration settings on Avaya Workplace Client. You can also use the Dynamic Configuration service to manage configuration settings and generate 46xxsettings.txt files for the following endpoints:

  • Avaya Vantage™.

  • Avaya J100 Series IP Phones.

  • Avaya 9600 Series IP Deskphones.

Avaya Aura® Device Services generates a separate 46xxsettings.txt file for each endpoint category. The generated 46xxsettings.txt files are stored on the Utility Server.

Dynamic configuration provides a centralized place to administer user, group, platform, global, and exception settings:

  • Global Any other settings category can override global settings. Global settings are used for both Avaya Workplace Client and desk phones.

  • Group User, platform, exception, and System Manager settings can override group settings. Group settings are only used for Avaya Workplace Client.

    When a client requests automatic configuration, Avaya Aura® Device Services searches for user groups only in the configured contexts on the LDAP server containing the user. For example, Avaya Aura® Device Services uses two LDAP servers configured as follows:

    • LDAP 1 has the primary base context DN set to PrimaryBase1 and two additional base contexts, Base 2 and Base 3.

    • LDAP 2 has the primary base context DN set to PrimaryBase2 and two additional base contexts, Base 4 and Base 5.

    In this case, for a user that is in LDAP 1, Avaya Aura® Device Services only searches for groups in PrimaryBase1, Base 2, and Base 3.

    Note:

    The authentication domain is an enterprise directory with the Use for authentication check box selected. If a user belongs to an authentication domain and a group that is not in the authentication domain, the Dynamic Configuration service still works correctly.

  • User Platform, exception, and System Manager settings can override user settings. These settings are only used for Avaya Workplace Client.

  • Platform Exception and System Manager settings can override platform settings. These settings are only used for Avaya Workplace Client.

  • Exception Exception settings are specific to the System Manager Home location. These settings are only used for Avaya Workplace Client.

    The Exception settings are not applicable if you use Avaya Aura® Device Services in an environment without Avaya Aura®.

  • Phone model The phone model settings are specific to Avaya Vantage™ endpoints, Avaya J100 Series IP Phones, and Avaya 9600 Series IP Deskphones.

Conflicting group names

Do not publish group settings to LDAP groups if there are users that belong to more than one group. Otherwise, a conflict occurs where the same setting is in two different groups with different values. In this case, Avaya Aura® Device Services must choose one value to return and the mechanism used is based on the ASCII ordering of group names, which could result in users getting the wrong value assigned to them for conflicting settings.

When there is a conflict between two group names, Avaya Aura® Device Services does the following to determine which group name to choose:

  1. Finds the first character in the group names that differ.

    This check is case-sensitive.

  2. Determines the unicode decimal representation of the characters.

    Avaya Aura® Device Services chooses the group name where the character with a unicode decimal representation is the smallest.

When there is a conflict with more than two groups, Avaya Aura® Device Services uses the same algorithm, but it looks at additional characters.

For example, a company has the following LDAP groups:

  • All Users

  • HR

  • Payroll

  • atlanta

  • 101_department

In this example, PHNLDLENGTH is published to both the 101_department and Payroll groups with a value of 7 and 11 respectively. Avaya Aura® Device Services returns the value 11 from the 101_department group. This is because the unicode decimal representation for the number 1 is 49, and the decimal representation for the capital letter P is 80.

The typical unicode representation flow is numbers (0 to 9) > capital letters > lowercase letters.

Conferencing settings

Avaya Aura® Device Services automatically discovers the following settings from the Avaya Meetings Server during Avaya Workplace Client deployment:

  • CONFERENCE_FACTORY_URI

  • CONFERENCE_PORTAL_URI

  • UNIFIEDPORTALENABLED

You can override the values for these settings from the Avaya Aura® Device Services web administration portal with any fixed user, group, phone model, or platform value.

Automatic discovery

Avaya Workplace Client supports discovery of the following settings:

  • Installation parameters as part of the installation process in MS Windows and macOS operating systems.

  • Active Directory Group Policy in MS Windows operating system only.

  • Configuration discovery via equinox cloud client public parameters on accounts.avayacloud.com.

  • Configuration discovery via DNS SRV record.

For more information about setting up automatic configuration on Avaya Workplace Client, see Planning for and Administering Avaya Workplace Client for Android, iOS, Mac, and Windows.

Related information
Adding a new enterprise LDAP server
Dynamic configuration setting priorities