Subscribe via RSS Feed Connect on LinkedIn

What Happens with #Lync phone sign in if I have duplicate Extensions?

24/03/2013 1 Comment

 

New Post

Background

This question was posed by and tested by my friend Jed Ellerby (worth following), he tested on Lync Server 2010 and I verified on Lync Server 2013.

Lync Phone edition phones can be signed in by entering your extension and Pin (it can also by signed in via USB tethering on the phones that have USB). Your extension is defined in Lync by appending “;ext=XXX” on SIP Tel URI, e.g. if my extension was 1234, my TelURI might be tel:+442034201234;ext=1234

I can then go up to a phone and type 1234 and my pin (set my administrator or at “dialin.sipdomain.com”) and sign into a Lync phone edition phone.

But what happens if I have two offices with overlapping extension ranges? Their TelURI can still be legal and globally unique, but their extensions clash? e.g.

Michael in office 1 is:

tel:+442034201234;ext=1234

John in office 2 is:

tel:+447078521234;ext=1234

It would be best, if possible, to have non-overlapping extension ranges. However when replacing existing systems, existing dialling habits and/or company acquisitions it’s quite possible to end up with overlap. How does Lync Phone Edition handle it?

WP_20130324_001

WP_20130324_004

Lync server signs them in correctly, as long as their pin is unique

WP_20130324_005

WP_20130324_007

Michael’s pin is 147258

John’s pin is 258369

 

What happens if the extension and pin are the same?

image

The GUI/PowerShell does not do any validation check for duplicates, but if users try to sign in they will see a fail

WP_20130324_010

Pins are usually randomised and 6 digit, so the odds of hitting a clash are slim, but it is something to look out for, especially if you do have known overlapping extension ranges. In an ideal world you would move to a unique extensions globally for easier dialling and management.

Update: Jed found that Microsoft to reference this behavior:

“The Front End Server uses the combination of full phone number or extension, and PIN, to uniquely map enterprise users to their Active Directory credentials”

http://technet.microsoft.com/en-us/library/gg398524.aspx

 

Useful? Please take a second to shareTweet about this on TwitterShare on LinkedInShare on Google+Email this to someone
Tom Arbuthnot

Tom Arbuthnot

Managing Consultant at Modality Systems
Tom Arbuthnot is a Microsoft Lync Certified Master and MVP. He is a blogger, regular on The UC Architects Podcast, contributing writer to Lync Server 2013 Unleashed and speaker at events such as Lync Conference and The Microsoft UC User Group London. He is currently Managing Consultant at Modality Systems.
Tom Arbuthnot
Filed in: Lync • Tags: , ,

Leave a Reply