locked
PSTN Call Routing from and to a branch site RRS feed

  • Question

  • Hi

    I have a client who has a remote branch site location.  The result of this is that their WAN connectivity is provided by satellite and has a data cap on this.  In order to avoid this being used up by Lync they have asked if all calls from the branch site to other Lync users at the central and other branch sites can be routed via the PSTN.

    I understand that if a user opts for Lync call or by specifying the named individual that this would always route via the WAN but what if the users were to dial the DDIs of the other users - can this be forced via the PSTN rather than being determined by Lync as an internal number that then routes via the WAN anyway.

    The central site is Lync Standard 2010 with a NET UX2000 Gateway.  The branch site in question is a Lync SBS server with a Tenor AFM PSTN gateway with analogue lines.

    Any advice on whether this is possible and how to achieve it would be much appreciated.

    Thanks,

    Alastair

    Sunday, September 1, 2013 9:30 PM

Answers

  • Hi - You might be able to achieve this through Call Admission Control and PSTN re-route

    check this blog: http://blogs.technet.com/b/jenstr/archive/2010/10/15/bandwidth-management.aspx



    Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini

    Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR


    Sunday, September 1, 2013 9:43 PM
  • Yes. CAC was specifically designed to provide a mechanism to ensure WAN links don't get oversubscribed by Lync media traffic.

    Putting it very simple, for a given WAN link, you configure session limits (that is, maximum bandwidth that single and total sessions can use). When a new call is trying being established, bandwidth availability is checked through the bandwidth policy service. If it's determined that not enough BW is available, the media portion of the call is rerouted either to egde servers, or to the PSTN.

    Note, i have explained this in very simple terms. There are several implications and steps you need to go through to enable CAC, so i'd recommend you read through carefully.

    http://technet.microsoft.com/en-us/library/gg398529.aspx

    http://blogs.technet.com/b/nexthop/archive/2010/11/17/call-admission-control-in-lync-server-2010.aspx

    Also note, as said, CAC is primarily designed as a bandwidth control mechanism and not as a feature to add routing intelligence.

     

    Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini
    Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR

    • Marked as answer by Lisa.zheng Wednesday, September 11, 2013 2:13 AM
    Monday, September 2, 2013 11:29 AM

All replies

  • Hi - You might be able to achieve this through Call Admission Control and PSTN re-route

    check this blog: http://blogs.technet.com/b/jenstr/archive/2010/10/15/bandwidth-management.aspx



    Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini

    Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR


    Sunday, September 1, 2013 9:43 PM
  • You can use Set-CsclientPolicy EnableVoipCallDefault $ture to replace Lync call with Voip call as the default call. But you can not disable the lync call option. And this policy setting only affects the initial state of the click-to-call feature. If the user modifies the value of the click-to-call setting then the user-selected value will override this policy setting.


    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.

    Monday, September 2, 2013 9:59 AM
  • By VoIP call do you mean that this would then force it via the PSTN?
    Monday, September 2, 2013 11:16 AM
  • Yes. CAC was specifically designed to provide a mechanism to ensure WAN links don't get oversubscribed by Lync media traffic.

    Putting it very simple, for a given WAN link, you configure session limits (that is, maximum bandwidth that single and total sessions can use). When a new call is trying being established, bandwidth availability is checked through the bandwidth policy service. If it's determined that not enough BW is available, the media portion of the call is rerouted either to egde servers, or to the PSTN.

    Note, i have explained this in very simple terms. There are several implications and steps you need to go through to enable CAC, so i'd recommend you read through carefully.

    http://technet.microsoft.com/en-us/library/gg398529.aspx

    http://blogs.technet.com/b/nexthop/archive/2010/11/17/call-admission-control-in-lync-server-2010.aspx

    Also note, as said, CAC is primarily designed as a bandwidth control mechanism and not as a feature to add routing intelligence.

     

    Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini
    Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR

    • Marked as answer by Lisa.zheng Wednesday, September 11, 2013 2:13 AM
    Monday, September 2, 2013 11:29 AM