CounterPath Bria 3.0 Configuration Guide – Retail Deployments - Manual (Page 16)

CounterPath Corporation
12
Use of # to identify the account is now deprecated. The dial plan should be capable of determining the
account to use for this number. However, since users may still be in the habit of entering the prefix, you
may want to include this pattern to handle such a scenario.
• Distinguishing between a local seven-digit call in which 9 is not dialed (to access an outside line) and one
in which 9 is dialed to access an outside line.
2.6 Directory
If you have set up an LDAP directory or Active Directory on a remote server, you can configure Bria to fetch
data from it. This data will be displayed in the Directory in the Resources module.
• To enable the Directory, set feature:ldap:enable or feature:adsi:enable to true; the Directory tab will be
included next to the Contacts tab and History tab in the Resources module.
Make sure to enable the directory only for LDAP or ADSI, not for both!"
• Set all the settings with "key" in their name for the appropriate directory type. For example, set
feature:adsi if you are using Active Directory.
These settings are used to map the attribute in your directory to the corresponding attribute in Bria. Be
careful with this mapping, because if the user creates a contact from the entry, the application will allow/
disallow certain functions (such as sending an IM) based on whether a property of that contact is populated.
• Complete these settings in the appropriate feature: domain/section to control how the data is
retrieved:
• polltime
• search_on_demand
• sizelimit
• timeout
Read the information in the search_on_demand setting in the settings documentation for information on
how these settings work together.
• Compete these settings in the appropriate feature: domain/section to connect to the directory and
find the location of the directory data:
For LDAP:
• ldap:password
• ldap:query
• ldap:root
• ldap:server
• ldap:use_tls
• ldap:username
For ADSI:
• adsi:root