locked
Normalization Rule in Lync 2010 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi I seen in article about normalization rules.

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

    Ex:

    Rule name Description Number pattern Translation Example

    4digitExtension

    Translates 4-digit extensions

    ^(\d{4})$

    +1425555$1

    0100 is translated to +14255550100

    In above i have 4 digit extension only 0100 for Internal users why rule has to resolve like this +14255550100 ??? could you please assist

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Chandru CT-HCL

    Thanks Chandru CT. MCITP

    Wednesday, August 14, 2013 2:43 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    It is best practice to assign your LIneURI's as a full e.164 address. So instead of just assiging 0100 you would assign +14255550100;ext-0100. The main reason for this is so that as your Lync environment grows you will avoid situations of overlapping extensions ranges. I highly recommend reading the following two articles as it explains this in great detail:

    http://ucken.blogspot.com/2010/12/enterprise-voice-best-practices-in-lync.html

    http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html

     

    Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

    • Marked as answer by Lisa.zheng Monday, August 26, 2013 9:03 AM
    Wednesday, August 14, 2013 2:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As I tested, the normalization rule works fine.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Lisa.zheng Monday, August 26, 2013 9:03 AM
    Saturday, August 17, 2013 9:47 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    It is best practice to assign your LIneURI's as a full e.164 address. So instead of just assiging 0100 you would assign +14255550100;ext-0100. The main reason for this is so that as your Lync environment grows you will avoid situations of overlapping extensions ranges. I highly recommend reading the following two articles as it explains this in great detail:

    http://ucken.blogspot.com/2010/12/enterprise-voice-best-practices-in-lync.html

    http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html

     

    Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

    • Marked as answer by Lisa.zheng Monday, August 26, 2013 9:03 AM
    Wednesday, August 14, 2013 2:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As I tested, the normalization rule works fine.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Lisa.zheng Monday, August 26, 2013 9:03 AM
    Saturday, August 17, 2013 9:47 AM