- Introduction
- Integration Requirements
- Cisco Unified Communications Manager Server Setup
- IM and Presence Service Node Setup
- Microsoft Component Integration Setup for IM and Presence Service
- Normalization Rules Setup
- Security Certificate Setup for IM and Presence Service
- Security between IM and Presence Service and Microsoft Lync Setup
- Lync Remote Call Control Installation
- Microsoft Lync Server and Microsoft Lync Client Logging
- Troubleshooting
Normalization Rules Setup
Set Up Normalization Rules on Microsoft Active Directory
A reverse look-up of a directory number to username does not work under these conditions:
- the user is not provisioned for E.164 in Active Directory and
- Active Directory phone number normalization rules are not set up
Under these conditions, the application identifies the call as coming from an extension number, and the username will not display in Microsoft Lync.
Therefore you must set up the correct normalization rules for the Active Directory address book on the Microsoft Lync server to enable the Microsoft Lync user to see the name of the calling party in the popup window that displays when the call is made.
Note | You must provide a normalization rule file for extension dialing. See the sample normalization rules topic for an example. |
The CA-signed certificate for Microsoft Lync must be on the Microsoft Lync PC to achieve correct certificate distribution for address book synchronization. If a common CA is used to sign certificates, for example Verisign or RSA, the CA certificate may already come installed on the PC.
Step 1 | Ensure that normalization is enabled in Lync Server. To do this, open the Lync Server Management Shell and enter the following command: Get-CsAddressBookConfiguration If the UseNormalizationRules value is set to True, normalization is enabled. If the UseNormalizationRules value is set to False, enter the following command to enable normalization: Set-CsAddressBookConfiguration -UseNormalizationRules $True | ||
Step 2 | Locate the ABFiles subdirectory in the Lync Server's shared directory that was configured during initial server deployment. Select \\<Server FQDN>\<Share Folder>\1-WebServices-1\ABFiles to identify the file server FQDN and share name. The path is as follows: | ||
Step 3 | Navigate to the following sample file: C:\Program Files\Microsoft Lync Server 2010\WebComponents\Address Book Files\Files\Sample_Company_Phone_Number_Normalization_Rules.txt | ||
Step 4 | Make a copy of the Sample_Company_Phone_Number_Normalization_Rules.txt file and save it as Company_Phone_Number_Normalization_Rules.txt in the ABFiles directory.
| ||
Step 5 | Open the Company_Phone_Number_Normalization_Rules.txt file in Notepad and remove regex code like [\s()\-\./]* . Microsoft Lync Server ignores non-telephony related digits and only analyzes the continuous 0-9 numerical digit patterns. However it does recognize the + prefix. | ||
Step 6 | In Lync Server Management Shell, enter the following command to import the new settings in the Company_Phone_Number_Normalization_Rules.txt file and apply them to numbers stored in the address book files: Update-CsAddressBook | ||
Step 7 | Wait for five before you force an address book update on the Lync client, see Update Microsoft Lync Address Book. |
What to Do Next
Sample Normalization Rules
## +1 (ddd) ddd-dddd EXTddddd # \+1(\d{10})EXT(\d{5}) +1$1;ext=$2 # # +1 (ddd) ddd-dddd Xddddd # \+1(\d{10})[Xx]{1}(\d{5}) +1$1;ext=$2 # # 1 (ddd) ddd-dddd # 1(\d{10}) +1$1 # # +1 (ddd) 70ddddd # \+1(\d{3})70(\d{5}) +1$170$2;ext=$2 # # 70d-dddd Xddddd # 70(\d{5})[Xx]{1}(\d{5}) +142570$1;ext=$2 # # ddd-dddd Xddddd # (\d{7})[Xx]{1}(\d{5}) +1425$1;ext=$2
Update Microsoft Lync Address Book
With the default server/client settings, the Address Book is not immediately updated. To ensure that the Address Book is updated with the latest users added to the Active Directory, you must force the update on the server side and then force Microsoft Lync to pull down the latest files to update its local GalContacts.db file.
What to Do Next