locked
Anonymous Call RRS feed

  • Question

  • Hi,

    Is there a setting in Lync to allow a user to make an anonymous call? for example in the uk we can dial 141 before a number to hide the CLI. I cannot see any setting in lync?

     

    thanks

    matt

     

    Thursday, June 2, 2011 5:44 AM

Answers

  • Matt

     

    The 141 prefix will still work. The 141 code is sent to the telco to tell them not to send your CLI to the end party. You would have to configure your Enterprise Voice normalization rules and routes handle it.

     

    Assuming this being the case, you could create a dial plan with normalisation rules that add 141 in front of all calls and assign this dial plan to a group of users if you want all calls from that group to be withheld.

    Mike


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks

    MCITP: Lync, Exchange 2010 & Server Administrator

    Blog
    Thursday, June 2, 2011 5:21 PM
  •  

    You can perminatly mask or change their outgoing CLI, either on Lync or Via the gateway, your telco provider can also do this.

    I can't see how you would do it, ad hoc, without having a code on the outgoing number which was fed to a gateway and causing a gateway based translation rule to mask the outgoing CLI.

    So, always masked is easy, ad hoc masked is a little more complex

    Hope that helps

    Tom


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks
    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Subscribe: RSS
    Twitter @tomarbuthnot
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 9:31 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:17 AM
    Thursday, June 2, 2011 5:07 PM

All replies

  •  

    You can perminatly mask or change their outgoing CLI, either on Lync or Via the gateway, your telco provider can also do this.

    I can't see how you would do it, ad hoc, without having a code on the outgoing number which was fed to a gateway and causing a gateway based translation rule to mask the outgoing CLI.

    So, always masked is easy, ad hoc masked is a little more complex

    Hope that helps

    Tom


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks
    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Subscribe: RSS
    Twitter @tomarbuthnot
    • Proposed as answer by Sharon.Shen Monday, June 6, 2011 9:31 AM
    • Marked as answer by Sharon.Shen Friday, June 10, 2011 5:17 AM
    Thursday, June 2, 2011 5:07 PM
  • Matt

     

    The 141 prefix will still work. The 141 code is sent to the telco to tell them not to send your CLI to the end party. You would have to configure your Enterprise Voice normalization rules and routes handle it.

     

    Assuming this being the case, you could create a dial plan with normalisation rules that add 141 in front of all calls and assign this dial plan to a group of users if you want all calls from that group to be withheld.

    Mike


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks

    MCITP: Lync, Exchange 2010 & Server Administrator

    Blog
    Thursday, June 2, 2011 5:21 PM