UCPrimer
  • Tech Blog
  • About UCPrimer.com

Lync 2013 Conferencing Location Based Routing (LBR)

3/31/2015

5 Comments

 
In the previous blog article, we discussed the capabilities of Lync 2013 LBR that was introduced in CU1. This allows the prevention of PSTN Toll By-pass which is prohibited by government regulations in countries such as India. For example, Lync user A in Delhi can make a call to a local Delhi PSTN number using the PSTN Gateway in Delhi. But when the same user travels to Mumbai and tries to make a call back to a local Delhi PSTN number, LBR will not allow this user to use the same PSTN Gateway in Delhi via the Mumbai-Delhi WAN link. While this covers the Peer-2-Peer calling restrictions, it does not address conferencing scenarios. For example, Lync user A in Delhi first makes a call to a local Delhi PSTN number using the PSTN Gateway in Delhi, then adds Lync user B in Mumbai to create a 3 party AVMCU conference. If the conference is allowed, then User B is effectively using PSTN Toll-Bypass, and TRAI regulations also prohibit the mixing of VOIP and PSTN calls. To address this scenario, we need to configure and enable Conferencing LBR, which was introduced in Lync 2013 CU2. In this article we explore the configuration of Conferencing LBR and testing with Polycom CX600 phones. Below is the diagram of the test scenario:
Picture
We can think of Conferencing LBR as an enhancement to the original LBR, which means that LBR must first be properly configured. This includes the sites and subnets information, the new Voice Routing Policy and assigning it to the network site, the Trunk Configuration settings and enabling LBR on the global routing configuration. All these steps were covered in the previous article and thus will not be repeated here. Note that enabling Conferencing LBR will also apply location based routing restrictions to Consultative Call Transfers, but this requires a standalone Mediation Server to be deployed and a single Mediation Server should only be associated with a single PBX or PSTN Gateway. It's also worthwhile to note that Conferencing LBR does not apply to Dial-in conferencing and hence we should not provide conferencing access numbers in regions where LBR restrictions need to be enforced

Once LBR is configured correctly we can proceed to enable Conferencing LBR as per the TechNet guidance. We just need to enable the LBRouting application with the correct priority. We can discover the list of running apps with the Lync Management Shell cmdlet:

Get-CsServerApplication -Identity Service:Registrar:<Pool FQDN>

From the list of apps returned, the UdcAgent app will have a default priority of 2 while the DefaultRouting app has a priority of 9. We need to assign the LBRouting app a lower priority than UdcAgent but higher than DefaultRouting. So we can simply run the following cmdlet to enable the LBRouting app at a priority of 3:

New-CsServerApplication -Identity Service:Registrar:<Pool FQDN>/LBRouting -Priority 3 -Enabled $true -Critical $true -Uri http://www.microsoft.com/LCS/LBRouting

That's all that's needed to enable Conferencing LBR and we can proceed to test. We have a Lync user on CX600 (Brennon) makes a call to extension 3001 on the Asterisk PBX over the SIP Trunk that has LBR enabled. The call goes through as expected and below is the SIP Trace showing the call being routed through the Trunk to the Asterisk "PSTN Gateway":
Picture
Next, from the CX600 phone we select "Add User" to create a conference and choose the contact "Lionel" who is logged in on a PC Lync client on a different subnet. From the SIP trace we can see the conference starting up using the AVMCU:
Picture
The user Lionel receives a incoming call pop-up and when he tries to accept, he is unable to connect to the conference, while the connection between the CX600 and the PSTN user stays up. An error message appears on the PC Lync client (Lionel) showing "We couldn't connect you to the call because of regional policies":
Picture
Below is the SIP Trace that shows the LBRouting app rejecting the call:
Picture
Conclusion
In deploying Lync Enterprise Voice, in order to properly implement LBR for both P2P and Conferencing scenarios, we need to apply Lync Server 2013 CU2 and make sure we configure the components correctly. This will ensure that government telecom authority regulations are adhered to where required
5 Comments
Alex J Wang
11/19/2015 05:09:35 am

i have 2 sites, Shanghai and India, India site is LBR enabled. india user created a meeting, then invite a PSTN endpoint join the meeting, the meeting scenario will be changed from SingleVoip to VoipAndPstn. in this scenario, if i ask shanghai user to join the meeting by dial-in, dial-in access number configured on Shanghai FE server, LBR just let the shanghai user join the meeting. i think this should not happens.

Reply
Brennon link
11/19/2015 07:27:33 pm

Yes it should not. But Conferencing LBR does not apply to Dial-in conferencing and hence we should not provide conferencing access numbers in regions where LBR restrictions need to be enforced

Reply
de la croix
2/3/2016 12:57:23 am

thank you very much for this details

Reply
Rajarajan Dayalan
3/31/2016 10:57:20 pm

Thanks for the article,

I had an doubt in a specific scenario,
Initiate a MeetNow conference on Lync client1 form Site 1
Add LC2 from Site 2
Then Add a PSTN user from Site 1.

Currently conference between all three user is established.

In this what will be the expected result.

Reply
Shankar
8/27/2018 12:05:54 pm

This will fail because the Lync user from Site1 & Lync User from site will be from a different network site. The PSTN conference will fail

Reply

Your comment will be posted after it is approved.


Leave a Reply.

    Picture
    Picture

    Important Links

    Microsoft Teams Docs
    Microsoft Learn

    ​Microsoft MVP Blogs

    Michael Tressler’s Blog
    Michael’s MTR Quick Tip Videos
    Jimmy Vaughan’s Blog
    Jeff Schertz
    Adam Jacobs
    James Cussen
    ​Damien Margaritis

    Archives

    September 2022
    August 2022
    March 2022
    February 2022
    January 2022
    December 2021
    November 2021
    October 2021
    September 2021
    August 2021
    June 2021
    April 2021
    March 2021
    December 2020
    October 2020
    September 2020
    August 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    March 2019
    November 2018
    October 2018
    September 2018
    August 2018
    June 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    August 2017
    July 2017
    April 2017
    March 2017
    February 2017
    January 2017
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    January 2016
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    September 2012
    August 2012

    Categories

    All
    Edge
    Exchange 2013
    Hybrid
    Lpe
    Lync 2010
    Lync 2013
    Mobility
    Oauth
    Office365
    Polycom
    Ucs

    RSS Feed

    This website uses marketing and tracking technologies. Opting out of this will opt you out of all cookies, except for those needed to run the website. Note that some products may not work as well without tracking cookies.

    Opt Out of Cookies