Managing non DDI numbers in AD during migration


If ever you get cross pollinated contact cards then you have just been a victim of Lync Contact Merge. A good explanation of this is found here. Its a handy feature but not always desirable…

I landed up with this by normalizing the numbers in AD to a common DDI for all non DDI Telephone numbers in AD – not a good idea 😦

My scenario was that a number of users in AD had 4 digit extension numbers set for their Telephone Attribute. Now we all know that this is not going to make the ABS happy as the import requires a + to deem the format acceptable.

*Simply adding a + in front of the ext number wont work as the Lync Normalization rules DON’T apply to numbers that have been imported from AD.

What we want to achieve is a unique number in AD and thus in the ABS to avoid Contact Merge. We also want all the non DDI users in AD (who live on a legacy PBX) to dial a common DDI which presents a prompt to select the extension (a function on the Legacy PBX).

The Solution…
Normalise the AD Telephone Number field to the Common DDI BUT add the actual Extension number on the end of the normalized number. This will ensure that the Attribute stays unique and it will also be a valid number to dial. When the normalized number is passed to Lync for calling it ignored the normalization rules as stated above at *. The number is sent “as is” to the mediation server and thus passed on to the Provider, who simply ignore the extra digits on the end of the valid E.164 number.

Ta Da


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, ADContacts, AddressBook Service, DDI, Normalization. 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