Cisco Cisco TelePresence Video Communication Server Expressway
2.
Select the relevant call attempt.
The entry shows the incoming and outgoing call leg details, the call’s status and the zones that the VCS
Control used to route the call.
Control used to route the call.
Presence Not Observed as Expected
Presence Server status
■
Go to Status > Applications > Presence > Publishers to check who is providing presence information to the
VCS Presence Server.
VCS Presence Server.
■
Go to Status > Applications > Presence > Presentities to check whose presence is being watched for (on
domains handled by VCS Presence Server).
domains handled by VCS Presence Server).
■
Go to Status > Applications > Presence > Subscribers to check who is watching for presence (of one or
more entities in domains handled by VCS Presence Server):
more entities in domains handled by VCS Presence Server):
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.)
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.
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.
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
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:
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.
that should be receiving the incoming SIP messages.
2.
Reconfigure Lync Server to send calls to the B2BUA IP port.
Lync Cannot Open a TLS Connection to VCS
Lync Debug says Lync Fails to Open a Connection to VCS, even though the TLS neighbor zone to Lync Server is
active and messaging is sent from VCS to Lync Server.
active and messaging is sent from VCS to Lync Server.
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.
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.
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:
header in the SIP INVITE only contains the IP address of the endpoint, e.g. “From:
48
Cisco VCS and Microsoft Lync Deployment Guide
Appendix 1: Troubleshooting