Cisco Cisco Expressway
The directory Expressway uses a license as it processes each call and it then holds on to the license until
it times out, which takes 5 seconds. Thus, 10 rich media session licenses will allow up to 120 calls per
minute (10 x 60 seconds / 5).
it times out, which takes 5 seconds. Thus, 10 rich media session licenses will allow up to 120 calls per
minute (10 x 60 seconds / 5).
2. Configure a SIP neighbor zone that has a Peer 1 address set to the Lync Front End server.
3. Set Call signaling optimization to On (
Configuration > Call routing
) so that it removes itself from the
signaling path.
4. Set Call Policy mode to Local CPL (
Configuration > Call Policy > Configuration
) and upload some
CPL based on the example CPL below.
Example CPL
Here is an example of the CPL that you would load on to the directory Expressway:
<?xml version="1.0" encoding="UTF-8"?>
<cpl xmlns="urn:ietf:params:xml:ns:cpl" xmlns:taa="http://www.tandberg.net/cpl-
extensions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:cpl cpl.xsd">
<taa:routed>
<taa:rule-switch>
<!-- Route IM & presence messages SUBSCRIBE and PUBLISH direct to CUP -->
<taa:rule originating-zone="
<To Lync Zone>" destination="(?!CUP_.+)(.*)" message-
regex="((SUBSCRIBE|PUBLISH)(.*Event:(\s)*presence.*))|((.*m=message.*))">
<!-- Add CUP_ as a header to identify all messages destined for CUP. Strip CUP_ in search
rule -->
<taa:location clear="yes" regex="(.*)" replace="CUP_\1">
<proxy />
</taa:location>
</taa:rule>
</taa:rule-switch>
</taa:routed>
</cpl>
The <To Lync Zone> element should be replaced by the name of the neighbor zone that you have created on
the directory Expressway that is pointed at Lync.
the directory Expressway that is pointed at Lync.
Modifying the Lync static route configuration
As the SDP messages coming from the Lync environment have to be analyzed by the directory Expressway,
all the traffic coming from Lync must be directed to that Expressway. Therefore the static route configured on
the Lync Server that routes calls to the address of the “Lync gateway” Expressway has to be modified to
route calls to the address of the the directory Expressway instead.
all the traffic coming from Lync must be directed to that Expressway. Therefore the static route configured on
the Lync Server that routes calls to the address of the “Lync gateway” Expressway has to be modified to
route calls to the address of the the directory Expressway instead.
Microsoft Lync and Cisco Expressway Deployment Guide (X8.2)
Page 49 of 67
Appendix 1: Federation