AD Contact Numbers not showing in Lync


Its always frustrating how Administrators don’t have any standard format in which they add telephone numbers to user in AD.
Its even more frustrating when Lync WONT collect these numbers and send to the RTCAB database cause they aren’t in E.164 format.

It is possible to add normalization rules for modifying numbers from AD to E.164 so that they are recognised by Lync and sent off to the Database.

If this happens the AddressBook Service will gladly distribute these to Lync user via GAL or WEB.

It will even distribute numbers that aren’t in E.164 as long as they have a normalization rule in the “Company Phone Number Normalization Rules” text file that matches the format in AD (as per the Extension Example below)

So how does this work?
Simply create a txt file and copy to the Lync Share

….LyncShare1-WebServices-1ABFiles

Company_Phone_Number_Normalization_Rules.txt

Now populate the txt file with your rules as per the example below:

#Start
#
# Normalize 4-digit extension numbers from Active Directory into E.164
#
# Legacy extensions
#
(d{4})
+643321$1
#Normalize NZ National Numbers from Active Directory into E.164
#+64$1
0([3-9]d{7})
+64$1
#Normalize NZ Cell numbers from Active Directory into E.164
#+642$1
0(2d+)
+642$1
#Extension Dialing for 8xxx range
(8d{3})
$1
#End


To find further Active Directory Normalization failures navigate to the directory:
C:LyncShare1-WebServices-4ABFiles0000000-0000-0000-0000-0000000000000000000-0000-0000-0000-000000000000Invalid_AD_Phone_Numbers.txt

NB
Just be warned, this isnt validated so if you make any typos you wont find this reported

BUT you can test this by running the ABServer.exe -testphonenorm switch.
Simply run the ABServer .exe from the directory:-
C:Program FilesMicrosoft Lync Server 2010ServerCore

Example


..Program FilesMicrosoft Lync Server 2010ServerCoreABServer.exe” -testphonenorm “021 123 4568”



Advertisements

About Paul B

My name is Paul Bloem and I am employed at Lexel Systems in New Zealand as a Principal Consultant for Unified Communications. I have been working on enterprise voice solutions for over 20 years. My first 10 years were spent working for a Telco in South Africa (Telcom SA). This is where all the groundwork happened as I was exposed to just about every aspect of telecommunication you could imagine. I develop an interest in PBX technologies and eventually became the go-to guy. Next, I had a 10 year run at Siemens South Africa, most of my time there was as a Technical Trainer. During this time VoIP hit the world stage, I had the privilege of introducing VoIP both as H.323 and later SIP across the Siemens HiPath 4000 solution stack. In 2008 I immigrated to New Zealand with my newly attained MCSE, I was ready to go where no PBX Techie had gone before. I was employed to explore OCS 2007 and that was pretty much the beginning of the end for me. I have been working on OCS and Lync ever since. My current role focuses exclusively on Lync and associated technologies.. That includes pre-sales, consulting, architecture and design, training and support. I even get to play in the development space from time to time - focus on play ;-) I was nominated as a Microsoft VTSP for Lync early in 2013 and also awarded Microsoft's MVP award for Lync in 2014.
This entry was posted in ABS, ABServer, AD Normalization, ADContacts, AddressBook Service, contacts, E.164, Invalid AD Phone Numbers, Normalisation, Normalization, Test. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s