Answered by:
Lync Number Resolution - Internal Extensions

Question
-
I'm having a real headache trying to get the lync clients (especially lync phone edition clients) to show extension numbers while dialling.
We have our uri's set in the format tel:+441623726487;ext=201 and the same for the users in AD. All of the contact cards now populate with +441623726487 and when you dial an extension into a phone or client it resolves it to +441623726487. Although if you press call it does call the extension, this is going to be very confusing to users. It also showed on the Phone Edition home screens with +441623726487;ext=201.
The dial plan for internal extensions is set to:
^([2-3]\d{2}|400)$
+441623726487;ext=$1I have played around with the Company_Phone_Number_Normalization_Rules.txt and have added:
(\d{3})
+441623726487;ext=$1This made no difference, so also added:
\+44(\d{4})(\d{6});ext=(\d{3})
$3This converted the home screen number from +441623726487;ext=201 to 201 which looks much better for the user. But nothing seems to work with the contact card or extension resolution. Made more difficult from the fact that the extension isn't shown in the contact card so I wouldn't be able to normalise it anyway.
I thought about using the uri's TEL:201 as the extensions are internal only and not DID, would this cause other problems though?
Please help!
Wednesday, May 8, 2013 8:57 AM
Answers
-
I've done some additional research and have figured out a few interesting things about how Lync clients deal with extensions. Rather than go through it here, I've published a blog post on the topic.
http://ucken.blogspot.ca/2013/05/viewing-extensions-in-lync-client.html
The short story is that you can get extensions to show up properly in the Lync 2010 client, but there appears to be issues with the Lync 2013 client. I'm still testing Lync Phone Edition and will update the post with my findings.
Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com
- Proposed as answer by Charbel Hanna Thursday, May 9, 2013 6:52 AM
- Marked as answer by Andy Way Friday, May 10, 2013 11:14 AM
Wednesday, May 8, 2013 8:01 PM
All replies
-
This appears to be a bug, because I've experienced exactly your issue before. In the Lync 2010 client, North American formatted phone extensions used to show up properly, (ie +1 (555) 222-3333 X4471), but not other countries. The situation has gotten worse in Lync 2013, because even North American extensions don't show up properly anymore.
I've been meaning to bring this up to the product group. Now, I'm definitely going to.
Ken Lasko ucken.blogspot.com
Wednesday, May 8, 2013 1:06 PM -
I've done some additional research and have figured out a few interesting things about how Lync clients deal with extensions. Rather than go through it here, I've published a blog post on the topic.
http://ucken.blogspot.ca/2013/05/viewing-extensions-in-lync-client.html
The short story is that you can get extensions to show up properly in the Lync 2010 client, but there appears to be issues with the Lync 2013 client. I'm still testing Lync Phone Edition and will update the post with my findings.
Ken Lasko | Lync MVP | http://UCKen.blogspot.com | http://LyncOptimizer.com
- Proposed as answer by Charbel Hanna Thursday, May 9, 2013 6:52 AM
- Marked as answer by Andy Way Friday, May 10, 2013 11:14 AM
Wednesday, May 8, 2013 8:01 PM -
Hi Ken
Thank you for the blog, was great. I followed your steps but the number of digits in your +44 number in your blog is one number shorter than our number. Would this make a difference to the normalization rule in the text file?
We also don't usually put .'s in phone numbers. Our format would usually be 01234 567890 or +441234567890. I entered +441234567890 X291 in the AD entries but this doesn't appear to show anywhere, everything is still showing +441234567890.
Strangely once I dialled one of the extension numbers into a handset (HP 4120) it resolved to +441234567890 I forgot to clear the screen (this usually happens automatically) then I looked again a while later and it had somehow resolved to the persons name and showing their presence status and was showing it as a work number with the handset icon. If it can be made to do that always (but straight away) that would be brilliant, I could then roll this out as our phone system.
Just feels so close yet so far!
Thursday, May 9, 2013 10:12 AM -
Ok, the handsets are now showing the format +441234567890;ext=291 when enter 291 into the handsets! A big step forward!
Now if I edit the normalization text file, do you think I could get it to show a 'nicer' format without breaking it?
Also, sometimes if left for 10-20 seconds it will automatically resolve the +441234567890;ext=291 to the persons name and shows presence status. If this could be made quicker it would be perfect!
I've had the Addressbookavailability option set to WebSearchOnly which I thought maybe was causing the delay, I have since set it back to WebSearchandFileDownload but this doesn't appear to have made any difference. I'm not sure if it only works if you've dialled that extension recently and it's cached the persons details or if it is looking up against the address book. Seems very intermittent.
Andy
Thursday, May 9, 2013 11:46 AM