|
|
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.
The following pages describe the software releases that were tested for
interoperability with Cisco TelePresence products. The results are grouped by
product range. It is not possible to guarantee that all the models listed in the
Product(s) column have been tested with the specified software release, although
to the best of our knowledge we believe that all such models are interoperable
with the associated software release. The absence of a device or release does
not imply a lack of interoperability.
Cisco TelePresence
| Product(s) |
Software release | Comments |
|---|
| 4200 series, 4500 series, 8000 series, Cisco TelePresence MCU Series products |
4.3 |
- If a call is made between an endpoint and an MCU, with the endpoint using SIP and the MCU using H.323, and a second endpoint joins the conference and sends a content stream (any protocol) to the MCU, the first endpoint display will freeze or go black when the second endpoint stops streaming content. This is because the first endpoint is not aware that streaming has ended and is expecting to receive further content.
- An endpoint, for example CTS, may end up in a half encrypted call where the call leg from CTS > CUCM > VCS is unencrypted and the call leg from VCS > MCU is encrypted.
|
| Cisco TelePresence Conductor |
XC1.2 |
No issues. |
| Cisco TelePresence Conductor |
XC2.0 |
|
| Cisco TelePresence C Series, Cisco TelePresence MX Series, Cisco TelePresence SX20 Quick Set, Cisco TelePresence System EX Series, Cisco TelePresence System Integrator C Series |
TC6.0.0 |
If you configure a trunk towards CUCM 8.6 or 9.0, you must create a custom SIP trunk that does not remove BFCP lines towards CUCM. If you choose CUCM as profile in the VCS, BFCP will be removed and dual stream (BFCP) will not be possible between CUCM and VCS. |
| Cisco TelePresence Server |
2.3(1.55) |
No issues found. |
| Cisco TelePresence System 500-37 |
1.10.1 |
We recommend that you install and assign the Cisco Unified CM "vcs-interop" SIP Normalization script to make secure calls between CTS endpoints and endpoints and devices registered to VCS.
|
| Cisco TelePresence System Quick Set C20, Cisco TelePresence Codec C40, Cisco TelePresence Codec C60, Cisco TelePresence Codec C90, Cisco TelePresence System EX60, Cisco TelePresence System EX90, Cisco TelePresence MX200, Cisco TelePresence MX300, Cisco TelePresence SX20 Quick Set, Cisco TelePresence System Integrator C Series , Cisco TelePresence System EX Series, Cisco TelePresence MX Series |
TC5.1.4 |
SIP and H.323
Both Assent and H.460.18/.19 traversal technologies are supported
SIP
If you configure a trunk towards CUCM 8.6, you must create a custom SIP trunk that does not remove BFCP lines towards CUCM. If you choose CUCM as profile in the VCS, BFCP will be removed and dual stream (BFCP) will not be possible between CUCM and VCS. |
| Cisco TelePresence System TX 1300 47, Cisco TelePresence System 500-32, Cisco TelePresence System TX1300 47, Cisco TelePresence System TX1310 65, Cisco TelePresence System TX9000, Cisco TelePresence System TX9200 |
TX6.0.0 |
We recommend that you install and assign the Cisco Unified CM "vcs-interop" SIP Normalization script to make secure calls between CTS endpoints and endpoints and devices registered to VCS.
For additional information about products that are compatible with systems running TX6.0, refer to the Cisco TelePresence TX System Software Version Compatibility and Interoperability with Other Devices—6.0.x Releases document at the following URL: http://www.cisco.com/en/US/docs/telepresence/tx_sw/6_0/compatibility/tx_sw_compatibility_6_0.html |
| Cisco TelePresence Video Communication Server (VCS) |
X7.2 |
No issues. |
|
Feedback