How-to Setup a Polycom Trio Corporate Directory Part Two

This is part two of a two-part series detailing the steps to configure Polycom Trios to utilise an external directory source such as Active Directory Lightweight Directory Services (AD LDS) enabling users to search the directory for available contacts.

Setup A Polycom Trio Provisioning Server

Internet Information Services (IIS) is used as the provisioning server in this article. Follow the Server Manager wizard to add the IIS role, including

  • Security > Basic Authentication
  • FTP Server > FTP Service

Once IIS is installed perform the following steps:

  • Create a New Site ‘PolycomTrioProvisioning’ and
    • Set the directory root to an appropriate location e.g. C:\inetpub\wwwroot\PolycomTrioProvisioning
    • Configure the binding if required. In this article HTTP and port 88 is used
    • Configure the mime type ‘.cfg’ as ’text/xml’
    • Enable Basic Authentication
    • Enable Directory Listing
  • Create an FTP site and ‘PolycomTrioLogs’
    • Configure the FTP authorisation to restrict access to a specific user or group. In this article, a Local Group ‘FTP_USERS’ was added which contains a single local user account ‘polycomtrio’
    • Set the directory root to an appropriate location. The FTP site is used only for Trio Logging in this article
    • Configure the appropriate RW permissions on the chosen directory root

Configure the Polycom Trio Provisioning Server

To provide provisioning information to the Polycom Trios, download the latest available version from Polycom support and extract the contents into the C:\inetpub\wwwroot\PolycomTrioProvisioning directory. This includes the 000000000000.cfg file and the Config directory containing the various configuration files.

In the 000000000000.cfg file, update the CONFIG_FILES= with the files you want to use for provisioning on the Trios. In this instance, for the phonebook, the config/features.cfg is specified. Update the LOG_FILE_DIRECTORY= with the FTP details such that the Trios can upload their logs to the central provisioning server.


Edit the config/features.cfg file and update the dir.corp section. Specifically

  • dir.corp.address - ldap://<ad lds server address>
  • dir.corp.baseDN - the DN path to the AD LDS objects to be used for populating the directory
  • dir.corp.password - the password of the AD LDS service account
  • dir.corp.user - the DN of the AD LDS service account user
  • dir.corp.attribute - if desired update the AD LDS attribute mappings that are used for the directory fields. E.g. set to the telephoneNumber attribute instead of the ipPhone attribute.
<dir.corp dir.corp.address="ldap://" dir.corp.autoQuerySubmitTimeout="0" dir.corp.backGroundSync="0" dir.corp.baseDN="OU=directory,DC=directory,dc=internal" dir.corp.bindOnInit="1" dir.corp.cacheSize="128" dir.corp.cacheSize.VVX101="64" dir.corp.customError="" dir.corp.domain="" dir.corp.filterPrefix="(objectclass=*)" dir.corp.pageSize="32" dir.corp.pageSize.Trio8500="64" dir.corp.pageSize.Trio8800="64" dir.corp.pageSize.VVX101="16" dir.corp.password="ldap.password" dir.corp.port="389" dir.corp.querySupportedControlOnInit="1" dir.corp.scope="sub" dir.corp.sortControl="0" dir.corp.transport="TCP" dir.corp.user="CN=ldapuser,OU=users,DC=directory,DC=internal" dir.corp.viewPersistence="0">
      <dir.corp.alt dir.corp.alt.address="" dir.corp.alt.autoQuerySubmitTimeout="0" dir.corp.alt.backGroundSync="0" dir.corp.alt.cacheSize="128" dir.corp.alt.cacheSize.VVX101="64" dir.corp.alt.domain="" dir.corp.alt.label="Global Address Book" dir.corp.alt.password="" dir.corp.alt.port="0" dir.corp.alt.protocol="sopi" dir.corp.alt.secCacheSize="32" dir.corp.alt.sortControl="0" dir.corp.alt.transport="TCP" dir.corp.alt.user="" dir.corp.alt.verifyCert="1" dir.corp.alt.viewPersistence="0">
        <dir.corp.alt.attribute dir.corp.alt.attribute.1.filter="" dir.corp.alt.attribute.1.label="""" dir.corp.alt.attribute.1.sticky="0" dir.corp.alt.attribute.1.type="last_name" dir.corp.alt.attribute.2.filter="" dir.corp.alt.attribute.2.label="""" dir.corp.alt.attribute.2.sticky="0" dir.corp.alt.attribute.2.type="last_name">
        <dir.corp.alt.auth dir.corp.alt.auth.useLoginCredentials="0">
        <dir.corp.alt.backGroundSync dir.corp.alt.backGroundSync.period="86400">
        <dir.corp.alt.utfSubset dir.corp.alt.utfSubset.1.start="" dir.corp.alt.utfSubset.1.stop="" dir.corp.alt.utfSubset.2.start="" dir.corp.alt.utfSubset.2.stop="">
      <dir.corp.attribute dir.corp.attribute.1.addstar="1" dir.corp.attribute.1.filter="" dir.corp.attribute.1.label="Name""sn" dir.corp.attribute.1.searchable="0" dir.corp.attribute.1.sticky="0" dir.corp.attribute.1.type="first_name" dir.corp.attribute.2.addstar="1" dir.corp.attribute.2.filter="" dir.corp.attribute.2.label="Telephone Number""ipPhone" dir.corp.attribute.2.searchable="0" dir.corp.attribute.2.sticky="0" dir.corp.attribute.2.type="phone_number">
      <dir.corp.auth dir.corp.auth.useLoginCredentials="0">
      <dir.corp.backGroundSync dir.corp.backGroundSync.period="86400">
      <dir.corp.viewPersistence dir.corp.viewPersistence.form="1">
      <dir.corp.vlv dir.corp.vlv.allow="0" dir.corp.vlv.sortOrder="">

Save the files and then proceed to configure the Polycom Trios to use the provisioning server.

Configure the Polycom Trio to Use the Provisioning Server

To configure the Polycom Trio to use the HTTP Provisioning Server for configuration information including the location of the AD LDS directory source:

  • Log into the Polycom Trio web interface
  • Navigate to Settings > Provisioning Server
  • Set the following
    • Server Type - HTTP
    • Server Address - http://<IIS Server Address>:<Port if not 80>
    • Server User - The local user account that can authenticate with IIS using Basic Authentication
    • Server Password - The password for the local user account
  • Expand the DHCP Menu
  • Set the Boot Server to ‘Static’ (unless the DHCP Options are being used)


At this point, Polycom Trios should now be connecting to the LDAP server as defined in the features.cfg file and resolving the objects (refer to part-one here) as directory entries from which you can select and call.


To provision the Polycom Trio’s with RealPresence Reasource Manager (RPRM):

  • Log into RPRM and navigate to Endpoint > Phone Management > Phone Management Settings
  • Configure the Provisioning Account Configuration password fields

  • To avoid the Admin password changing to 789 once the Trio Provisioning Server configuration is altered navigate to Endpoint > Phone Management > Configuration Profiles
  • Search for Password
  • Copy¬†the AdminPassword-Change-Template
  • Modify the copied template and set the device.auth.localAdminPassword attribute to the current/desired password
  • Navigate to Endpoint > Phone Management > Profiles Deployment
  • Add the custom template to the Global profiles
  • Log into the Polycom Trio and navigate to Settings > Provisioning Server
  • Set:
    • Server Type - either HTTP or HTTPS
    • Server Address - http://<rprmIP>/phoneservice/configfiles/
    • Server User - PlcmSpIp (or what was configured in the RPRM)
    • Server Password - the password you configured above in the RPRM
    • DHCP Menu > Boot Server - Static or Option66

Reference - How to provision a Trio to the Resource Manager 10.1+