Export (0) Print
Expand All

Requirements for Location-Based Routing for conferencing in Lync Server 2013

Lync Server 2013
 

Topic Last Modified: 2013-07-19

The following are the requirements needed for the installation and configuration of the Location-Based Routing Conferencing application:

  • Lync Server 2013 Cumulative Update 2 must be deployed on all servers or pools in your topology.

noteNote:
If a Lync server or pool in your topology does not have Lync Server 2013 Cumulative Update 2 or higher installed, then enforcement of Location-Based Routing of Lync meetings cannot be guaranteed.
  • Lync Server 2013 Location-Based Routing is a pre-requisite for Location-Based Routing Conferencing application. For further information on configuring Lync Server 2013 Location-Based Routing, please refer to Configuring Location-Based Routing.

  • Requirements of Location-Based Routing Conferencing application are the same as the requirements for Lync Server 2013 Location-Based Routing. For more information, please refer to Planning for Location-Based Routing.

The Location-Based Routing Conferencing application requires that Lync Server 2013 Cumulative Update 2 is deployed on all Front-End pools and Standard Edition Servers in your topology. If Lync Server 2013 Cumulative Update 2 is not installed on some Lync Servers in your topology, Location-Based Routing restrictions cannot be fully enforced on Lync meetings and consultative call transfers.

The following table identifies the combination of server roles and versions that support Location-Based Routing.

 

Front-End Pool version

Mediation Server version

Supported

Lync Server 2013 Cumulative Update 2

Lync Server 2013 Cumulative Update 2

Yes

Lync Server 2013 Cumulative Update 2

Lync Server 2013 Cumulative Update 1

No

Lync Server 2013 Cumulative Update 2

Lync Server 2010

No

Lync Server 2013 Cumulative Update 2

Office Communications Server 2007 R2

No

Lync Server 2013 Cumulative Update 1

Any

No

Lync Server 2010

Any

No

Office Communications Server 2007 R2

Any

No

The Lync clients that support Location-Based Routing of Lync meetings are the same clients that support Lync Server 2013 Location-Based Routing. For more information, please refer to Client and Server Support for Location-Based Routing.

The Location-Based Routing Conferencing application requires deploying stand-alone Mediation Servers in order to enforce Location-Based Routing restrictions on consultative call transfers.

To enforce Location-Based Routing of consultative call transfers, the Mediation Server must be associated with only one Mediation Server peer (i.e. PBX, SIP gateway, etc) in network regions where Location-Based Routing is required. If additional Mediation Server peers are deployed in the same network region, the Mediation Server peer must be associated with a different Mediation Server . This Requirement is detailed as follows:

  • Single Mediation Server per multiple Mediation Server peers When a consultative call transfer is routed to a Mediation Server peer through a Mediation Server that’s configured with multiple SIP trunks to multiple peers (i.e. PBXs and gateways), the consultative call transfer is blocked to prevent PSTN toll bypass if the consultative call transfer is permitted through some SIP trunks but disallowed through other SIP trunks.

    For example, in the case of a single Mediation Server servicing a PSTN Gateway Mediation Server Peer and a PBX Mediation Server Peer, the following behavior will be observed:

    • When a Lync user from a given site (i.e. site 1) attempts to transfer a call with a PSTN endpoint to a Lync user from a different site (i.e. site 2) via consultative transfer, the call will be disallowed to prevent PSTN toll bypass.

    • When a Lync user from a given site (i.e. site 1) attempts to transfer a call with a PBX endpoint in the same site (site 1) to a Lync user from a different site (i.e. site 2) via consultative transfer, the call will be disallowed even if it doesn’t incur in potential PSTN toll bypassing.

  • Separate Mediation Servers per Mediation Server peer

    When a consultative transfer is targeted at a Mediation Server Peer, the consultative transfer will be evaluated against the single Mediation Server Peer serviced by the Mediation Server. The call will be disallowed or allowed based in its potential to incur in PSTN toll bypass regardless of all other Mediations Server Peers in the site as they’re serviced by separate Mediation Servers.

    For example, in the case of a separate Mediation Servers servicing a PSTN Gateway Mediation Server Peer and a PBX Mediation Server Peer, the following behavior will be observed:

    • When a Lync user from a given site (i.e. site 1) attempts to transfer a call with a PSTN endpoint to a Lync user from a different site (i.e. site 2) via consultative transfer, the call will be disallowed to prevent PSTN toll bypass.

    • When a Lync user from a given site (i.e. site 1) attempts to transfer a call with a PBX endpoint in the same site (site 1) to a Lync user from a different site (i.e. site 2) via consultative transfer, the call will be allowed as it doesn’t incur in potential PSTN toll bypassing.

The following capabilities are not supported by the Location-Based Routing Conferencing application:

  • Dial-in conferencing. Location-Based Routing cannot be enforced for Dial-in conferencing. Any dial-in request to a given conference will not be restricted by Location-Based Routing even if the conference organizer is a Lync user enabled for Location-Based Routing.

  • It’s recommended not to provision conferencing access numbers in regions where Location-Based Routing restrictions need to be enforced.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft