locked
Understanding Extensions and Normalization Rules RRS feed

  • Question

  • New to OCS/Lync, I am a bit confused on working with extensions and normilazation rules, I have read several resources and forums, but can't seem to get the overall picture on how to get these to work with lync and the proper format for AD user objects. For example, for the most part 90% of users do not have a DID and will have a 4 digit extension, say starting at 2001. With the incoming main office number of (514) 333-2222. (USA) Typical user to user internal call would just dial the 4 digit extension.

    So correct me If I am wrong:

    If I follow the E.164 format, for user Joe

    In Lync:

    Line URI: tel+15143332222;ext=2001

    Normilzation Rule:

    Looking at the "Build Normilzation Rule" Box

    Length set to: Exactly 4

    Digits to add: +15143332222

    Results:

    Pattern to Match: ^(\d(4))$

    Translation Rule: +15143332222$1

    Should I check the Internal Extension option?

    As far as the ordering of Normilzation Rules, where should this extension rule be placed, if other standard rules exist such as International, 11 digit, 10 digit,.. rules?

    On the AD User Object, what is the correct format for the telephone field using RFC3966 formating with an extension?

    Say another internal user decides to call Joe using his contact card information populated from lync (either via the Lync client or a device) which displays +15143332222 X 2001, how does lync handle this call, do I need to create another normilzation rule to handle this?

    Thanks

    Friday, February 25, 2011 5:06 AM

Answers

  • Thanks, I read through that, and also http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html which is more relevant to lync. I did end up figuring everything out. I'll go through my findings.

    As mentioned above users use a main office number with a 4 digit extenstion, for example Joe's full number would be (514) 333-2222 ext 2001, Bob is (514) 333-2222 ext 2002.

    Configuring Joe in Lync:

    Line URI: tel+15143332222;ext=2001

    I then added a normalization rule so when Joe makes and internal call to Bob he is dialing 2002. What I was getting stuck on is the Normaliztion Rule builder in Lync does not support advance Regular expressions, I had to manually modify the Translation rule, Overall it looks like this:

    Pattern to Match: ^(\d(4))$

    Translation Rule: +15143332222;ext=$1

    Dialing 2002 translates to +15143332222;ext=2002

     On the Active Directory Side of things, I used the following format for the telephone field:

    +15143332222 x2002

    Created a Company_Phone_Number_Normalization_Rules.txt document under the Lync Share \1-WebServices-1\ABFiles\ directory with your Normalization Address Book Rules:

    ##
    ## Normalize all AD phone numbers to E.164
    ##
    \+?[\s()\-\./]*1?[\s()\-\./]*\(?\s*([2-9]\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*
    +1$1$2$3

    Resulting in phone numbers appearing as: +1 (514) 333-2222 X2002 in the lync client and device.

    To speed things up I ran a Update-CSAddressBook from the Lync PowerShell, waited about 5 minutes, rebooted my phone, Polycom CX700, signed out of the Lync Client, deleted everything under: C:\Users\%username%\AppData\Local\Microsoft\Communicator

    Everything now works. Comments or suggestions?

    Thanks

    • Marked as answer by hector7869 Saturday, February 26, 2011 12:34 AM
    Friday, February 25, 2011 9:40 PM

All replies

  • The normalization rules are matched top down, so you should place the more specific rules at the top and more general rules at the bottom.  For the telephone

    Take a look at the OCS Normalization articles on this page for additional info: http://blog.schertz.name/2010/06/pointbridge-posts-ocs-enterprise-voice/

     


    Jeff Schertz, Microsoft Solutions Architect - Polycom | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Friday, February 25, 2011 2:10 PM
  • Thanks, I read through that, and also http://ucken.blogspot.com/2011/01/enterprise-voice-best-practices-in-lync.html which is more relevant to lync. I did end up figuring everything out. I'll go through my findings.

    As mentioned above users use a main office number with a 4 digit extenstion, for example Joe's full number would be (514) 333-2222 ext 2001, Bob is (514) 333-2222 ext 2002.

    Configuring Joe in Lync:

    Line URI: tel+15143332222;ext=2001

    I then added a normalization rule so when Joe makes and internal call to Bob he is dialing 2002. What I was getting stuck on is the Normaliztion Rule builder in Lync does not support advance Regular expressions, I had to manually modify the Translation rule, Overall it looks like this:

    Pattern to Match: ^(\d(4))$

    Translation Rule: +15143332222;ext=$1

    Dialing 2002 translates to +15143332222;ext=2002

     On the Active Directory Side of things, I used the following format for the telephone field:

    +15143332222 x2002

    Created a Company_Phone_Number_Normalization_Rules.txt document under the Lync Share \1-WebServices-1\ABFiles\ directory with your Normalization Address Book Rules:

    ##
    ## Normalize all AD phone numbers to E.164
    ##
    \+?[\s()\-\./]*1?[\s()\-\./]*\(?\s*([2-9]\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*
    +1$1$2$3

    Resulting in phone numbers appearing as: +1 (514) 333-2222 X2002 in the lync client and device.

    To speed things up I ran a Update-CSAddressBook from the Lync PowerShell, waited about 5 minutes, rebooted my phone, Polycom CX700, signed out of the Lync Client, deleted everything under: C:\Users\%username%\AppData\Local\Microsoft\Communicator

    Everything now works. Comments or suggestions?

    Thanks

    • Marked as answer by hector7869 Saturday, February 26, 2011 12:34 AM
    Friday, February 25, 2011 9:40 PM