Cisco Cisco Expressway
A VCS (or an Expressway) uses CPL to direct SIP SIMPLE SUBSCRIBE and PUBLISH messages towards IM and
Presence Service. Other messages are processed by the Gateway Expressway and calls are routed on to the Cisco
call control (could be VCS or CUCM).
Presence Service. Other messages are processed by the Gateway Expressway and calls are routed on to the Cisco
call control (could be VCS or CUCM).
This deployment scenario stopped working in X8.6 when the Expressway SDP parser was rewritten. You can read
about it in Microsoft Lync and Cisco Expressway Deployment Guide (X8.5).
about it in Microsoft Lync and Cisco Expressway Deployment Guide (X8.5).
Scenario 3 Migration Overview
■
Replace the static route from Microsoft infrastructure to the directory Expressway with a static route to the
Gateway Expressway instead.
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 CUCM IM&P nodes to trust the
Gateway Expressways and the Microsoft FE Servers.
Gateway Expressways and the Microsoft FE Servers.
■
Remove the directory Expressway entry from the incoming ACL list and TLS peer context, then decommission
the Expressway.
the Expressway.
Common Configuration
Before you start: Get the addresses of the IM and Presence Service nodes that you’re using for this integration.
Check what port they are expecting for messaging and presence. The transport must be TLS.
Check what port they are expecting for messaging and presence. The transport must be TLS.
Configure the SIP Broker
1.
Log on to the Gateway Expressway. If it is a cluster, log on to the primary peer.
2.
Go to Applications > B2BUA > Microsoft interoperability > Configuration.
3.
Change Enable broker for inbound SIP to Yes.
4.
Enter the IP addresses, hostnames, or FQDNs of the destination IM and Presence Service nodes.
If you use hostnames, the Expressway will append the domain from System > DNS > Domain name.
5.
Change the port number if the IM and Presence Service nodes are listening on a different port.
Note:
There is no transport protocol selection in this configuration. The Expressway sends the traffic out on the
same transport protocol that carried the inbound traffic from the Microsoft server (TLS by default). Changing
the port number will not change the transport.
the port number will not change the transport.
For example, entering
5060
will not force the Expressway to interwork inbound TLS to outbound TCP towards
IM and Presence Service. The IM and Presence Service does not allow TCP chat federation anyway.
6.
Save the configuration.
Create a Static Route From IM&P To Microsoft FE Server
Use the Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager
Configuration Guide, for your version of IM and Presence Service, to configure a static route to the Microsoft
FE server. Here is
Configuration Guide, for your version of IM and Presence Service, to configure a static route to the Microsoft
FE server. Here is
.
You need the static route towards the Microsoft Server because the outgoing messaging from IM&P goes directly to
the Microsoft server.
the Microsoft server.
The difference between this document and the guide cited above is that the incoming messaging / presence does not
come directly from the Microsoft Server: it comes from the Gateway Expressway, so you don't need the reverse static
route from Microsoft Servers to IM&P nodes.
come directly from the Microsoft Server: it comes from the Gateway Expressway, so you don't need the reverse static
route from Microsoft Servers to IM&P nodes.
62
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Appendix 2: Chat / Presence Between Jabber and Microsoft Clients