For my typical North American address book file, I add the following rules (assumes North American numbers are stored as either 10 or 11 digits without the ): The rules you add will be determined by the format phone numbers are stored in Active Directory.It appears that the normalization rule engine hasn't changed since the older versions of Lync, which means that you will still have to enter your normalization rules exactly as you did with the old Company_Phone_Number_Normalization_A constant problem with Enterprise Voice in Lync is the fact that phone numbers stored in Active Directory often are not stored in the E.164 format that Lync requires for proper functionality.
The file location is correct and shows where the current OAB files are.
With this post, I hope to never again have to type the oh-so-memorable filename Company_Phone_Number_Normalization_
Exchange 2013 has gone through an evolution in the way the Offline Address Book is generated and maintained.
So we decided to remove the copy and then create a new database copy. With a single, good database copy, we can now generate, update and download the Offline Address Book.
After we removed, we tested the OAB to see if this would make a difference. Although Microsoft touts that the address book can now reside in multiple locations (CU 7 ) and the generating mailbox can be replicated via a DAG: “This new infrastructure can also take advantage of the high availability architecture of Exchange 2013.