Cisco Cisco Expressway
■
Unified CM for primary call control of the Cisco Collaboration video network.
■
On-premises Cisco Collaboration endpoints registered to Unified CM.
■
A dedicated Expressway-C for interoperability with the Microsoft environment (referred to as Gateway
Expressway).
Expressway).
■
Cisco Expressway-E in the DMZ to provide TURN services.
Note:
The diagram shows a separate Cisco Expressway-C and Cisco Expressway-E traversal pair, trunked to
Unified CM. This configuration is not required for Microsoft interoperability, but you can use the Cisco
Expressway-E from your MRA or B2B solution for TURN services. The (MRA) Cisco Expressway-C shown here
is not required in this deployment, so it is not shown in other diagrams in this document.
Expressway-E from your MRA or B2B solution for TURN services. The (MRA) Cisco Expressway-C shown here
is not required in this deployment, so it is not shown in other diagrams in this document.
Example Values in this Deployment
The example presented uses the following values:
■
The Microsoft environment uses
example.com
as the SIP domain. The SIP domain for Microsoft need not be the
same as the AD domain of Microsoft clients (the Microsoft login domain used in the login user name may be
different from the SIP domain used in the sign-in address).
different from the SIP domain used in the sign-in address).
■
The Cisco video network’s domain is
video.example.com
(used for video device registrations).
■
Endpoints registered to the video network are provisioned by Unified CM and register with a DN in the format
3xxx.
3xxx.
■
Microsoft clients registered to Microsoft FE servers are identified by URIs, for example:
—
David with a URI
david.jones@example.com
—
Alice with a URI
alice.parkes@example.com
■
Microsoft Front End Server is configured with a static domain route which routes URIs with the Expressway's
video network domain (
video network domain (
video.example.com
) to the Gateway Expressway. Take care when using domain static
routes; any traffic for that domain that Microsoft cannot handle locally will be routed to Expressway.
Features and Limitations
Microsoft Environment
The scale of your Microsoft deployment could mean that your deployment model is more complex than what is
described in this guide.
described in this guide.
options and how the deployment model varies in each case.
Lync / Skype for Business Versions Supported in This Deployment
The following matrix shows which Microsoft Lync and Skype for Business client versions are supported in the
Expressway gateway deployment. Clients in the first column are registered to one of the server versions in the other
columns. Find your client and server version to check whether the combination is supported in this Expressway
deployment.
Expressway gateway deployment. Clients in the first column are registered to one of the server versions in the other
columns. Find your client and server version to check whether the combination is supported in this Expressway
deployment.
Clients (below), when registered to servers (right)
Lync
Server
2010
Server
2010
Lync
Server
2013
Server
2013
Skype for Business
Server 2015
Server 2015
Lync 2010 (Windows desktop)
Supported
Supported
Not supported
Lync for Mac 2011(audio only
1
)
Supported
Supported
Not supported
Table 2 Microsoft Lync and Skype for Business Support in this Deployment
7
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Introduction