Cisco Cisco Expressway
Figure 6 Flow Charts Showing Call / Chat Session Establishment in Target Scenario
Scenario 1: Gateway Expressway integration with Microsoft infrastructure; calling,
but no chat/presence
but no chat/presence
The voice/video integration is made possible by the "Gateway Expressway" that interoperates between Microsoft
video and standard SIP.
video and standard SIP.
The detail of the scenario 1 configuration is in the main body of this document, Cisco Expressway and Microsoft
Infrastructure Deployment Guide.
Infrastructure Deployment Guide.
Scenario 1 Migration Overview
■
Create a SIP direct federation from CUCM IM and Presence Service to Microsoft infrastructure:
—
Enable TLS between IM&P and the Microsoft servers
—
Create cluster-wide static routes from IM&P publisher nodes to the Microsoft servers
—
Create trusted applications (to represent the IM&P nodes) on Microsoft server and put them in trusted
application pools
application pools
—
Do not create the reverse static routes, from MS to IM&P nodes. The intradomain federation guide requires
this, but this configuration supersedes that requirement: here, we’ll create the static routes from Microsoft
servers to the Gateway Expressway instead.
this, but this configuration supersedes that requirement: here, we’ll create the static routes from Microsoft
servers to the Gateway Expressway instead.
■
Enable the SIP broker on the Gateway Expressway, and give it the addresses and port of the listening IM and
Presence Service nodes.
Presence Service nodes.
■
Update the Incoming ACLs (access control lists) and TLS peer context on the IM&P publisher nodes to trust the
Gateway Expressways and the Microsoft servers.
Gateway Expressways and the Microsoft servers.
60
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Appendix 2: Chat / Presence Between Jabber and Microsoft Clients