Ask Learn
Preview
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This is the 25th in our series of guest posts by Microsoft Most Valued Professionals (MVPs). You can click the “MVPs” tag in the right column to see all the articles.
Since the early 1990s, Microsoft has recognized technology champions around the world with the MVP Award. MVPs freely share their knowledge, real-world experience, and impartial and objective feedback to help people enhance the way they use technology. Of the millions of individuals who participate in technology communities, around 4,000 are recognized as Microsoft MVPs. You can read more original MVP-authored content on the Microsoft MVP Award Program Blog.
This post is by Ståle Hansen, a Lync MVP. His blog is msunified.net. Than ks very much, Ståle!
Ståle here. A new feature for Enterprise Voice in Lync Server 2013 is the ability to change the display number for users when they dial out. This could be useful in several scenarios:
This feature is configured on the trunk that can be found in the Lync control panel under Voice Routing -> Trunk Configuration -> <Site Trunk or Pool Trunk> . At the bottom of your trunk configuration page you have two options:
We have now configured a simple Calling number translation rule. The regex builder does not support advanced expressions, so you may need to make the rules yourself.
At a customer site I have seen trouble with using this approach when the customer also uses a third-party Lync call center product. The scenario was that it worked for a while, but after a week in production, the user became unable to place calls over the trunk or Lync to Lync. Changing the number to a non-manipulated number resolved the issue. I am not sure if it was a bug or that the third-party product interfered with the feature. You should pilot this feature in your deployment over one or two weeks before you roll it out in your organization.
You should give the different users different numbers that normalize to the number you want to display. Do not use extensions because that will not work and the number will not be normalized.
There is another method to do this and this method where available in Lync Server 2010 as well. You can give the same number to different users and use extensions
All inbound calls will now be routed to the user or queue assigned with ;ext=1. Everyone will show the same number when dialing out, since extensions will not be shown.
There are, however, some lessons learned using this approach. Fellow Lync MVP Ken Lasko has documented some scenarios where this approach will not work and I have experienced them in Lync Server 2013 as well. The problem is that the mediation server may decline the incoming call with the error code 485 Ambiguous call. This is because it thinks the same number is assigned to several users. The problem is actually related to the + sign; if you remove this, it will work. The workaround to this is therefore:
Using the new feature in Lync Server 2013 to change the display number is an easy approach to control what number is shown externally. I hope this gives you some idea of the potential in outbound normalization of the calling number in Lync Server 2013.
Anonymous
April 23, 2013
An update to this post regarding the pattern for the calling number translation rules. I stated in the article that you need to bevare of using extension with this. There is a solution for that as well. You can add (sS)* at the end of the pattern. The pattern in the first example will then be like this: ^+475005(sS)*$. In order to do this you need to edit the pattern and insert it manually. I have tested this approach in the field with success. Doug Deitterick also encountered this issue and solved it adding(;ext=d{4})? at the end before $. Read Doug's post about it here: blogs.technet.com/.../issue-with-calling-number-translation-rules-and-e-164-extensions.aspx
You still need to be aware of incomming calls using this approach though because of the possibility of ambiguous call. I solved this at the customer using a dummynumber range for those users so the incoming number would be unique.
Regards
Ståle
Anonymous
May 28, 2013
How many entries we can put into calling translation ?
What about performance if we add for example 1000 entries ?
Ask Learn is an AI assistant that can answer questions, clarify concepts, and define terms using trusted Microsoft documentation.
Please sign in to use Ask Learn.
Sign in