locked
IDD Authorization Code for Microsoft Lync Voice RRS feed

  • Question

  • Hello Friends,

    We are in need to provide an IDD Authorization module for Lync Voice. When the user make an IDD call, user should use an Authorization or Pin code. For invalid codes the IDD call should be restricted as well.

    I wonder whether Lync naturally support such feature?

    Or, should we need to place some server side application in between?

    Any enlightening is greatly appreciated and thanks a lot in advance.

    thank u


    Life is a Gift. To be a Gift

    Monday, July 21, 2014 3:41 AM

Answers

  • Another option that might possibly work is to set up a special dial plan and route that requires you to use an authorization code prefix. You can then strip it back off in a trunk configuration called number translation rule. Apply the dial plan and policy to the users who would need it.

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Wednesday, July 23, 2014 1:39 AM

All replies

  • Hi,

    This is a typical PBX feature. Lync doesn't do like that. For Lync, it's all about the PSTN Usage and the Voice policy. The person who has a voice policy assigned with a PSTN Usage that allow IDD, that person can dial IDD and the ones doesn't have the usage, won't be able to. What you can do is that, you may need to ask some one who has IDD access to log in to the phone in order to make an IDD call.


    http://thamaraw.com

    Monday, July 21, 2014 5:06 AM
  • Thanks Thamara. 

    So every user who need to make IDD call need the voice policy right? But no way to give some pin codes for further security?

    thanks a lot!


    Life is a Gift. To be a Gift

    Monday, July 21, 2014 5:56 AM
  • Hi,

    Unfortunately, there's nothing out-of-the-box that fills this gap. 

    I do remember looking at a 3rd party solution for a customer a few years ago, but I can't vouch for how well it works, if at all.

    http://www.idc.it/solutions/telpin

    http://www.youtube.com/watch?v=lT1IyS1APNk

    I can't tell you whether or not this software works on Lync 2013, but at the least you can see that the API does provide a method to write a custom application that can do what you want.

    I hope that helps.

    Dan.


    • Edited by DanInAus Monday, July 21, 2014 10:41 AM
    Monday, July 21, 2014 10:40 AM
  • thank you Dan!

    Life is a Gift. To be a Gift

    Tuesday, July 22, 2014 2:59 AM
  • Another option that might possibly work is to set up a special dial plan and route that requires you to use an authorization code prefix. You can then strip it back off in a trunk configuration called number translation rule. Apply the dial plan and policy to the users who would need it.

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Wednesday, July 23, 2014 1:39 AM
  • Nice one. You could do this. This would kind of act as a "PIN" code. But, it would be a single tiring of digits and won't be "Personal" though.

     

    http://thamaraw.com

    Wednesday, July 23, 2014 3:32 AM
  • If we make use of some API's like UCMA, can we make some IDD Authorization which works like an IVR ?

    Life is a Gift. To be a Gift

    Wednesday, July 23, 2014 6:23 AM
  • you can do that as well. 


    http://thamaraw.com

    Wednesday, July 23, 2014 7:27 AM
  • Yeah, to get the dial plan/route trick to have personal pins, you're either talking about multiple dial plans and routes, or one large one with multiple pins inside of it.  If you needed different pins for thousands of users, that just wouldn't be feasible.  For fewer, this might be an interesting script to automate or manage it. 

    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications

    Wednesday, July 23, 2014 1:12 PM