Cisco Cisco Expressway
■
If the Lync environment has no Lync Director but a Hardware Load Balancer in front of Front End Servers then
the B2BUA should be configured to route calls for Lync to the Hardware Load Balancer, and receive calls from
any of the FE Servers:
the B2BUA should be configured to route calls for Lync to the Hardware Load Balancer, and receive calls from
any of the FE Servers:
—
The Gateway B2BUA needs to specify the Hardware Load Balancer as the Lync signaling destination
address.
address.
—
The Gateway B2BUA needs to include the addresses all of the Lync FE Servers as trusted hosts.
—
Search rules that route calls to Lync will target the B2BUA neighbor zone.
■
If Lync is a single FE Server, then the B2BUA should be configured to route calls for Lync directly to that
FE Server, and to receive calls from that FE Server:
FE Server, and to receive calls from that FE Server:
—
The Gateway B2BUA needs to specify the FE Server as the Lync signaling destination address.
—
The Gateway B2BUA needs to include the address of the FE Server as a trusted host.
—
Search rules that route calls to Lync will target the B2BUA neighbor zone.
Multiple Lync Domains and Multiple Gateway Expressways
You can integrate Cisco collaboration infrastructure with more than one Lync domain if required. Wherever you put a
single Expressway as a gateway, you could use a cluster instead.
single Expressway as a gateway, you could use a cluster instead.
The diagram below shows the following different options:
1.
This option is used in this document; there is one gateway Expressway (or cluster) into a single Lync domain.
2.
One gateway or gateway cluster serving multiple Lync domains. Requires multiple search rules to route the
calls to and from Lync correctly.
calls to and from Lync correctly.
3.
It is possible to configure multiple Lync domains with an independent gateway serving each. This option is not
exhaustively tested, nor is it described in this document.
exhaustively tested, nor is it described in this document.
4.
You should avoid configuring multiple gateways to serve one Lync domain.
With this deployment, calls from one video endpoint to another video endpoint that is called via its Lync
domain will get routed via Lync rather than directly through the collaboration infrastructure; users could lose
duo video, far end camera control, and possibly encryption and video quality.
domain will get routed via Lync rather than directly through the collaboration infrastructure; users could lose
duo video, far end camera control, and possibly encryption and video quality.
59
Cisco Expressway with Microsoft Lync Deployment Guide
Appendix 2: Extended Lync Deployments