Release Notes
Interoperability
Cisco TelePresence Server Software Release Notes 3.1(1.95) Page 18 of 31
Firefox 14 is not supported for use with the Cisco TelePresence Server
We strongly recommend that you do not use Firefox 14 to access the TelePresence Server’s web interface.
This version of the browser causes an issue that was not present in previous Firefox versions and has been
fixed in Firefox 15. This issue also affected previous versions of the TelePresence Server software.
TIP calls and encryption required conferences
TIP calls can only join conferences with the Encryption setting configured to Required when TLS encrypted
signaling is used throughout the call signaling path. This ensures that the call is fully secure.
Recommended VCS version X7.2 or later
On calls to CTS endpoints in certain network configurations, calls may fail or become audio-only with earlier
versions of VCS. In order to avoid this, upgrade VCS to X7.2. If using a custom zone profile on VCS for the
Cisco Unified Communications Manager zone, ensure that SIP UPDATE strip mode is disabled on this
zone.
Interoperability
The interoperability test results for this product are posted to http://www.cisco.com/go/tp-interop, where you
can also find interoperability test results for other Cisco TelePresence products.
We endeavor to make our Cisco TelePresence products interoperable with all relevant standards-based
equipment. Although it is not possible to test all scenarios, the testing on which this data is based covers
most common functions of the listed endpoints and infrastructure.
About the interoperability section
The interoperability section describes the equipment and software revisions that were tested for
interoperability with TelePresence Server 3.1. The absence of a device or revision from this section does not
imply a lack of interoperability.
Interoperability testing often requires interworking from one signaling/call control protocol to another. The
following table lists phrases that are used to briefly describe the call paths that were tested for each
interoperability scenario. The explicit call paths in the table place the endpoint first and the TelePresence
Server last as a general convention. References to ‘TS’ mean either TelePresence Server behind Cisco
TelePresence Conductor or TelePresence Server on its own.
Call path phrase Explicit call path description
SIP Endpoint ← SIP → TelePresence Server
H.323 Endpoint ← H.323 → TelePresence Server
H.323 to SIPinterworking Endpoint ← H.323 → Cisco VCS ← SIP → TelePresence Server
SIPto H.323 interworking Endpoint ← SIP → Cisco VCS ← H.323 → TelePresence Server
CUCMto VCSH.323 interworking Endpoint ← SIP → Cisco Unified CM ← SIP → Cisco VCS ← H.323 →
TelePresence Server
CUCMto VCS/Conductor SIP Endpoint ← SIP → Cisco Unified CM ← SIP → Cisco
VCS/TelePresence Conductor ← SIP → TelePresence Server