Cisco Cisco TelePresence Video Communication Server Expressway
Problems with Certificates
If a non-Lync application is used to create certificates to load onto VCS for use with Lync (for example when
purchased from a certificate authority) it is vital that the Subject name and Subject Alternate Name contain the same
details as they would if the certificates were created by Lync.
purchased from a certificate authority) it is vital that the Subject name and Subject Alternate Name contain the same
details as they would if the certificates were created by Lync.
Specifically, if both Subject name and Subject Alternate Name are used, then the name entered in the Subject name
must also appear in the Subject Alternative Name list.
must also appear in the Subject Alternative Name list.
.
Problems Connecting VCS Control Local Calls
Look at search history to check the applied transforms
1.
In VCS, go to Status > Search history.
Search history entries report on any searches initiated from a SETUP/ARQ /LRQ in H323 and from an
INVITE/OPTIONS in SIP. The summary shows the source and destination call aliases, and whether the
destination alias was found.
INVITE/OPTIONS in SIP. The summary shows the source and destination call aliases, and whether the
destination alias was found.
2.
Select the relevant search attempt. The search history for that search attempt shows:
—
the incoming call’s details
—
any transforms applied by pre-search transforms or CPL or FindMe
—
in priority order, zones which matched the required (transformed) destination, reporting on:
•
any transforms the zone may apply
•
found or not found status
•
if not found, the error code as seen in the zone’s search response
repeated until a zone is found that can accept the call, or all matches have been attempted
(The search may be ‘not found’ due to lack of bandwidth or because the search from the zone resulted in an
H.323 rejection reason or a non 2xx response to a SIP request.)
H.323 rejection reason or a non 2xx response to a SIP request.)
3.
If the search indicates:
—
Found: False
—
Reason: 480 Temporarily Not Available
this could be because the VCS’s zone links are not correctly set up. From the command line execute:
xcommand DefaultLinksAdd
to set up the links for the default zones. Also check that the links for other zones that have been created.
Note that each H.323 call will have 2 entries in the search history:
■
An ARQ to see if the endpoint can be found.
■
The SETUP to actually route the call.
The ARQ search does not worry about links or link bandwidth, and so if links do not exist or link bandwidth is
insufficient it may still pass, even though the SETUP search will subsequently fail.
insufficient it may still pass, even though the SETUP search will subsequently fail.
Each SIP call will usually only have a single search history entry for the SIP INVITE.
Look at ‘Call History’ to check how the call progressed
1.
Go to Status > Calls > History.
The summary shows the source and destination call aliases, the call duration and whether the call is a SIP,
H.323 or SIP< -- >H.323 interworking call.
H.323 or SIP< -- >H.323 interworking call.
51
Cisco VCS and Microsoft Lync Deployment Guide