Cisco Cisco TelePresence Video Communication Server Expressway
Setting
Lync Server zone configuration
SIP UDP/BFCP filter mode
Off
SIP Duo Video filter mode
On
SIP record route address type
Hostname
SIP Proxy-Require header strip list
<blank>
Cluster calls to endpoints not registered using FindMe
This can occur, for example, with MCU calls where MCU is in its own dedicated domain.
n
Lync does not have a way of load balancing calls to a cluster of VCSs.
n
Lync does not support DNS SRV, but it does allow the DNS record to be a Round-Robin record listing all
VCSs in the “Lync gateway” cluster./ Lync seems to continue to use just a single VCS until it loses
connectivity to that VCS. At that time it will choose a different VCS from the Round-Robin DNS record.
VCSs in the “Lync gateway” cluster./ Lync seems to continue to use just a single VCS until it loses
connectivity to that VCS. At that time it will choose a different VCS from the Round-Robin DNS record.
Use of VCS clusters with Lync without B2BUA FindMe registration therefore provides resilience, not extra
capacity / load balancing.
capacity / load balancing.
Lync client reports no audio device
Lync client sometimes complains that it has no audio device configured when selecting resume … follow
Lync client’s instructions to update the audio device and resume will then work.
Lync client’s instructions to update the audio device and resume will then work.
Call forward from Lync to a VCS FindMe or endpoint results in a ‘loop
detected’ call
detected’ call
If a call from VCS is made to a Lync client which has a forward to another VCS registered endpoint or a
FindMe, then VCS sees this as a looped call.
FindMe, then VCS sees this as a looped call.
FindMe Caller ID set to FindMe ID causes calls from Lync client to fail
If all of the following are true:
n
FindMe Caller ID is set to FindMe ID
n
a Lync client’s URI is in the active location of a FindMe
n
a call is made from that Lync client to a SIP destination
the call will fail because Lync does not expect the caller ID (From: header) to be modified.
If the call is interworked on the “Lync gateway” VCS, the call will work as required.
Best practice is that a Lync client should never be included as a FindMe device. Lync clients and video
endpoints are related to one another using B2BUA registration of FindMe IDs where the FindMe URI is the
same as the Lync client URI.
endpoints are related to one another using B2BUA registration of FindMe IDs where the FindMe URI is the
same as the Lync client URI.
Microsoft Lync and Cisco VCS Deployment Guide (X8.1)
Page 65 of 76
Appendix 3: Interoperating capabilities and limitations