Cisco Cisco Expressway
—
TCP may not work for Microsoft environments that include hardware load balancers (HLBs) and / or Director
—
A static route using TCP must go to the destination IP address. So, with TCP you cannot get redundancy
from a clustered Gateway Expressway, which you can when you configure a TLS static route to the
cluster's FQDN
from a clustered Gateway Expressway, which you can when you configure a TLS static route to the
cluster's FQDN
■
If the Gateway is a cluster, you must configure the primary peer and allow the configuration to be replicated to
the other peers automatically. When you see the
the other peers automatically. When you see the
†
in the web interface, it indicates that a field must be
completed on each peer.
Deployment Components
We are integrating your Microsoft environment with your video network to provide video calling and screen sharing
between Cisco Collaboration endpoints and Microsoft clients.
between Cisco Collaboration endpoints and Microsoft clients.
Figure 1 Topology used in this deployment guide
What's in the diagram?
The Microsoft deployment has:
■
A pool of Microsoft Servers with Front End Server role (one server shown for clarity).
■
A Microsoft Server with Edge Server role.
■
On-premises Microsoft clients registered to Microsoft FE Server.
■
Off-premises Microsoft clients registered to Microsoft Edge.
The Cisco video deployment has:
6
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Introduction