Cisco Cisco TelePresence Video Communication Server Expressway
No presence being observed
Check that there is no transform that may be inadvertently corrupting the presence Publication, Subscription
or Notify, for example that there is no transform modifying the presence URI. (Notifies are sent to the
subscription contact ID, typically <name>@<IP address>:<IP port>;transport=xxx. Any transforms that
modify this are likely to stop the presence Notify being routed appropriately.)
or Notify, for example that there is no transform modifying the presence URI. (Notifies are sent to the
subscription contact ID, typically <name>@<IP address>:<IP port>;transport=xxx. Any transforms that
modify this are likely to stop the presence Notify being routed appropriately.)
Lync client fails to update status information
If a Lync client is started before the Presence Server is enabled, the Lync client may need to be signed out
and signed back in again before it will display the correct presence information.
and signed back in again before it will display the correct presence information.
Check for errors
Checking for presence problems should be carried out in the same way as checking for errors with calls:
check the Event Log and the logging facilities mentioned in the ‘Check for errors’ section above.
check the Event Log and the logging facilities mentioned in the ‘Check for errors’ section above.
Video endpoint reports that it does not support the Lync
client SDP
client SDP
If a video endpoint reports that it does not support the Lync client SDP, for example by responding “400
Unable to decode SDP” to a SIP INVITE message containing the Lync multi-part mime SDP sent to it:
Unable to decode SDP” to a SIP INVITE message containing the Lync multi-part mime SDP sent to it:
1. Check whether the Lync Server is sending calls to the VCS incoming IP port, rather than the B2BUA IP
port that should be receiving the incoming SIP messages.
2. Reconfigure Lync Server to send calls to the B2BUA IP port.
TLS neighbor zone to Lync Server is active and messaging is
sent from VCS to Lync Server, but Lync debug says Lync
fails to open a connection to VCS
sent from VCS to Lync Server, but Lync debug says Lync
fails to open a connection to VCS
The local host name and domain name fields must be configured in the VCS
System > DNS
page so that
VCS can use its hostname (rather than IP address) in communications. Lync requires the use of VCS
hostname so that it can open a TLS connection to the VCS.
hostname so that it can open a TLS connection to the VCS.
Lync client initiated call fails to connect
If a call fails to connect, check that the endpoint, IP Gateway, MCU or ISDN Gateway is NOT in Microsoft
mode; ensure that it is in Standard or Auto mode. (From a H.323/SIP trace, an indication that the device is in
Microsoft mode is the presence of a “proxy=replace” field in the contact header of the 200 OK from the
device.)
mode; ensure that it is in Standard or Auto mode. (From a H.323/SIP trace, an indication that the device is in
Microsoft mode is the presence of a “proxy=replace” field in the contact header of the 200 OK from the
device.)
Lync responds to INVITE with ‘488 Not acceptable here’
There can be two causes for this message:
From IP address
This is normally seen if the B2BUA forwards an INVITE from a standards-based video endpoint where the
‘From’ header in the SIP INVITE only contains the IP address of the endpoint, e.g. “From:
‘From’ header in the SIP INVITE only contains the IP address of the endpoint, e.g. “From:
Microsoft Lync and Cisco VCS Deployment Guide (X8.1)
Page 56 of 76
Appendix 1: Troubleshooting