locked
Normalization Rule is not working RRS feed

  • Question

  • Hi All,

    I have around 20 users with Lync 2010 Enterprise Voice:

    Two of them have this Linu Uri:

    tel:+5114473210;ext=28601

    tel:+5114473210;ext=28602

    I create a dial plan:

     

     

    As you can see:

    From lync client If I dial 28601 it will be translated to tel:+5114473210;ext=28601. However that is not working as expected. Because when I dial 28601 it's translated to +51128601

     

    Why is no matchig my first dial plan?


    Regards. José Osorio.
    Thursday, February 2, 2012 10:07 PM

Answers

All replies

  •  

    Confirm I can replicate the issue. And this rule works as you would expect:

     

     

    Looking into the issue, bear with me

     

    cheers

     

    Tom


    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Subscribe for updates: Email or RSS
    Twitter @tomarbuthnot
    Friday, February 3, 2012 1:53 PM
  • Hi Tom,

     

    Please could you help me with this issue:

    I've modify my dial plan to add this:

    The normalization rule is ok and the test works fine.However, In lync user when i dial *456455 lync show

     

    As I see the normalization rule is not getting applied.

    The voice route is this:

    ^\+511(\*\d{6})$

    How can i resolve this?


    Regards. José Osorio.
    Sunday, February 5, 2012 11:58 PM
  • Jose,

    The testing tool in the CP is a simple regex checker. * is not a valid character to start a Lync number with, so I'm not overly surprised that doesn't work. However as I see it the first rule should work - I'm going to do further tests on that.

    Tom


    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Join over 300 UC Pros who subscribe for blog updates: Email or RSS
    Twitter @tomarbuthnot
    Monday, February 6, 2012 9:02 AM
  •  

    OK, further testing using snooper reveals this looks like a possible UI bug.

    In the first example even though the User UI shows only the first half of the number, the dialed number is actually the full number you would expect.

    e.g. UI shows +1114473210

    but if you trace the call, +1114473210;ext=1233 is dialed.

    So it seems there is some kind of match to American number formatting in the UI, that present as NUMBER X1244 in some cases.

    I'll raise this with msft PS when I get a chance.

    Tom


    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Join over 300 UC Pros who subscribe for blog updates: Email or RSS
    Twitter @tomarbuthnot
    Monday, February 6, 2012 9:49 AM
  • Hi Tom,

    So * and # are not valid characters to dial a number?

     


    Regards. José Osorio.
    Monday, February 6, 2012 5:39 PM
  •  

    All Lync numbers start with a "+" , * and # can be dialled.

    thanks

    Tom 

     

     

     


    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Join over 300 UC Pros who subscribe for blog updates: Email or RSS
    Twitter @tomarbuthnot
    Monday, February 6, 2012 5:47 PM
  • Hi Tom,

    I want to dial from lync client these number:

     

    #345456 and *345456

    I create the right normalization rule. However as you can see when I dial them lync show this

     


    Regards. José Osorio.
    Monday, February 6, 2012 5:52 PM