locked
Normalization in Lync RRS feed

  • Question

  • Hi,

    I have the following phone format stored in AD - +27(11)907-9999 (a standard in South Africa).

    I have a rule that strips the +27 and replaces it with 50 (5 for an external connection and 0 to complete the area code in SA).

    When trying to dial by selecting the phone number from the Lync client the normalization rule does not kick in.

    When I copy and paste the above number into the 'Find a contact or dial a number' space, the rule works perfectly.

     

    The rule I have looks like this:

    Pattern to match: ^\+27(\d{9})$

    Translation Rule: 50$1

     

    What gives???


    Vinkie
    Friday, June 3, 2011 8:41 AM

Answers

  • Normalization of the address book (which is created based on the fields in AD) is done via address book normalization.  Jeff Schertz has a post on how to do this:  http://blog.schertz.name/2010/09/lync-2010-address-book-normalization/

    On a side note, generally the best practice that is followed is to normalize to E164 within Lync and do non-E164 normalization at the next hop from the Mediation server (often a gateway).


    Mike Stacy | http://mikestacy.typepad.com
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 7:51 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Friday, June 3, 2011 2:32 PM
  • you have to translate all numbers to E.164 format

    Pattern to match: ^\+27(\d{9})$

    Translation Rule: +27$1

    then you have to use the trunk configuration

    Pattern to match: ^\+27(\d{9})$

    Translation Rule: 50$1

    all numbers will be translated to E.164 and with the trunk configuration all numbers will be send in a normal format to your gateway.


    regards Holger Technical Specialist UC
    • Proposed as answer by Lasse WedøMVP Sunday, June 5, 2011 8:43 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Saturday, June 4, 2011 8:35 AM
  • It's a tricky one this,

    First you Normalize:

    Take whatever the user is expected to type, let's say 27555522222 (If your users dials differently, you create different Normalization rules)

    You Normalize this to the E.164 of: +27555522222

    Then You must have Dial Plan to and a route to match the +27555522222, and send it to a Trunk.

    Finally, on the Trunk you create a translation Rule as Holger describes and send it out to the PSTN.

    KR,

    Lasse Wedø


    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.
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 7:52 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Sunday, June 5, 2011 8:49 AM

All replies

  • Normalization of the address book (which is created based on the fields in AD) is done via address book normalization.  Jeff Schertz has a post on how to do this:  http://blog.schertz.name/2010/09/lync-2010-address-book-normalization/

    On a side note, generally the best practice that is followed is to normalize to E164 within Lync and do non-E164 normalization at the next hop from the Mediation server (often a gateway).


    Mike Stacy | http://mikestacy.typepad.com
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 7:51 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Friday, June 3, 2011 2:32 PM
  • you have to translate all numbers to E.164 format

    Pattern to match: ^\+27(\d{9})$

    Translation Rule: +27$1

    then you have to use the trunk configuration

    Pattern to match: ^\+27(\d{9})$

    Translation Rule: 50$1

    all numbers will be translated to E.164 and with the trunk configuration all numbers will be send in a normal format to your gateway.


    regards Holger Technical Specialist UC
    • Proposed as answer by Lasse WedøMVP Sunday, June 5, 2011 8:43 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Saturday, June 4, 2011 8:35 AM
  • It's a tricky one this,

    First you Normalize:

    Take whatever the user is expected to type, let's say 27555522222 (If your users dials differently, you create different Normalization rules)

    You Normalize this to the E.164 of: +27555522222

    Then You must have Dial Plan to and a route to match the +27555522222, and send it to a Trunk.

    Finally, on the Trunk you create a translation Rule as Holger describes and send it out to the PSTN.

    KR,

    Lasse Wedø


    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.
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 7:52 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:42 AM
    Sunday, June 5, 2011 8:49 AM
  • Thanks for all the replies. It does seem that we may have conflicting ideas about the implementation of standards.

    I am certainly going to discuss this with my guys.


    Vinkie
    Monday, June 6, 2011 8:21 AM