|
|
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, MSE 8420, MSE 8510, Cisco TelePresence MCU Series products |
4.2 |
No issues. |
| Advanced Media Gateway, Cisco TelePresence Exchange System |
1.1 |
No issues. |
| Cisco IP Video Phone E20 |
TE4.1.0 |
No issues. |
| Cisco IP Video Phone E20 |
TE4.0.0 |
No issues. |
| Cisco Jabber Video for TelePresence (Movi) |
v4.4 |
No issues. |
| Cisco Jabber Video for TelePresence (Movi) |
v4.3 |
No issues. |
| Cisco Jabber Video for TelePresence (Movi) |
v4 |
No issues. |
| Cisco Jabber Video for TelePresence (Movi) |
v4.2 |
No issues. |
| Cisco TelePresence Conductor |
XC2.0 |
|
| Cisco TelePresence Conductor |
XC2.1 |
No issues found. |
| Cisco TelePresence Conductor |
XC1.2 |
No issues. |
| Cisco TelePresence Content Server |
S5.0 |
Applies to Cisco TelePresence Content Server versions earlier than S5.2.
The SIP Standard registration refresh minimum setting introduced in VCS X7.0 has a default value of 45 seconds.
Devices that request a value lower than the Standard registration refresh minimum setting will result in the registration being rejected with a 423 Interval Too Brief response.
Any SIP devices, such as the Cisco TelePresence Content Server, that do not retry their registration request after receiving a 423 response will fail to register.
The workaround is to set the Standard registration refresh minimum setting on the Cisco VCS to 30 seconds. |
| 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.
No video is seen on a C60 if the following conditions are met:
- A Cisco TelePresence System 500 Series, 1000, 1100, 1300 Series, 3000 Series, 3200 Series, or TX9000 Series calls a C60.
- The products mentioned in Step 1 share a presentation with the C60.
- The C60 places the call on hold, then resumes the call.
Under these conditions, neither the main video nor the presentation is seen by the C60.
|
| Cisco TelePresence Exchange System |
1.2 |
Supported component for Cisco TelePresence Exchange System Release 1.2 |
| Cisco TelePresence IP Gateway |
2.0(1.11) |
No issues. |
| Cisco TelePresence MCU Series products |
4.4 |
- An encrypted H323 to SIP call on the CUCM to VCS path to a CTS endpoint may fail to show video on the CTS if the conference is set to encryption optional (CSCud43073).
|
| Cisco TelePresence Server |
3.0(2.24) |
Increasing resources for a call that leaves the TS as H.323 and is interworked by the VCS to SIP can cause the call to fail. (Issue identifier CSCud64471) |
| 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 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 |
Tested to work if the system running TX software is registered to Cisco Unified Communications Manager Version 9.1(1) or 8.6(2a)SU3.
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 more information about the conditions required for secure calls, see this document:
http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_8/release/notes/cts_1_8_release_notes.html#wp138743
For more information about the Cisco Unified CM script, see this document:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_6_2/cucm-rel_notes-862.html#wp1961382
For more information about configuring Unified CM and VCS to interoperate via a SIP trunk, see Cisco VCS and CUCM Deployment Guide.
For more 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.1 |
No issues. |
| TANDBERG Gatekeeper |
N6.3 |
No issues. |
| TCX for Exchange |
2.2 |
No issues. |
Cisco
| Product(s) |
Software release | Comments |
|---|
| 2811 Router |
15.1(4) |
No issues. |
| Cisco Unified Communications Manager |
8.6.1 |
No issues. |
LifeSize
| Product(s) |
Software release | Comments |
|---|
| Room |
4.6.0 |
An H.323 call routed via Cisco VCS will be disconnected when the H.323 party puts the call on-hold. Lifesize Room (SIP) incorrectly responds to Cisco SDP (media capability) offer. This issue is resolved in Lifesize Room version 4.8.3.
A Movi SIP call routed via Cisco VCS will connect, however no video will be seen on the Lifesize Room. Lifesize Room (SIP) incorrectly responds to Cisco SDP (media capability) offer. This issue is resolved in Lifesize Room version 4.8.3.
A C20 or E20 SIP call routed via Cisco VCS will connect, however no video will be seen on the Lifesize Room. C20 and E20 do not send media to Lifesize after call is connected. This issue is resolved in Lifesize Room version 4.8.3.
A Jabber Video / Movi SIP call routed via Cisco VCS will connect, however no video will be seen on the LifeSize Room system if an HD camera is used and the requested bandwidth is > 1MBps. This issue also exists in Lifesize Room version 4.8.3. |
| Room |
4.10.1 |
No issues. |
Microsoft
| Product(s) |
Software release | Comments |
|---|
| Lync |
2010 |
No issues. |
| OCS |
2007 R2 |
No issues. |
Polycom
| Product(s) |
Software release | Comments |
|---|
| HDX 9000 |
3.0.0.2 |
An H.323 call routed via Cisco VCS will not connect when the destination is Polycom HDX registering using SIP. Polycom HDX does not send a response to a Cisco VCS interworked SIP INVITE request (because it contains a “Session-Expires” header without a “Supported: timer” extension). Polycom have stated that this will be fixed in a future release. |
| HDX 9000 |
3.0.4 |
An H.323 call routed via Cisco VCS will not connect when the destination is Polycom HDX registering using SIP. Polycom HDX does not send a response to a Cisco VCS interworked SIP INVITE request (because it contains a “Session-Expires” header without a “Supported: timer” extension). Polycom have stated that this will be fixed in a future release. |
| ViewStation 512, ViewStation SP, FX |
7.5.4 |
Works with X7.1 and earlier, but does not work with X7.2 due to Polycom FX not supporting the number of H.323 video capabilities presented to it in X7.2.
This issue is fixed in X7.2.1. |
|
Feedback