Cisco TelePresence

Interoperability Database

Warning - In preview mode

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 Server software version 3.1

Show data for version: 4.44.34.2(4.23)4.2(3.x)4.24.1 4.14.14.03.13.0(2.48)3.0(2.24)3.02.3(1.55)2.32.2(1.54)2.2(1.48)2.1(1.18)


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 SIP interworking  Endpoint < H.323 > Cisco VCS < SIP > TelePresence Server 
SIP to H.323 interworking Endpoint < SIP > Cisco VCS < H.323 > TelePresence Server
CUCM to VCS H.323 interworking Endpoint < SIP > Cisco Unified CM < SIP > Cisco VCS < H.323 > TelePresence Server
CUCM to VCS/Conductor SIP  Endpoint < SIP > Cisco Unified CM < SIP > Cisco VCS/TelePresence Conductor < SIP > TelePresence Server
TIP Endpoint < SIP > Cisco Unified CM < SIP > Cisco VCS/TelePresence Conductor < SIP > TelePresence Server with TIP negotiation (requires TIP-compatible endpoint)


Cisco TelePresence

Product(s) Software releaseComments
Cisco IP Video Phone E20 TE4.1.2.299752

Tested H.323 and SIP:

  • Using hold/resume functionality on a Cisco IP Video Phone E20 stops the endpoint from receiving content from the Cisco TelePresence MCU or Cisco TelePresence Server. The endpoint receives content in the main video. (Issue identifier CSCty98376)
Cisco Jabber for iPad 9.2

Tested SIP and SIP to H.323 interworking:

  • Transition from video to content or content to video may lead to transient video issues. (Issue identifier: CSCud64312)
  • Video may occasionally fail when a call that is experiencing packet loss and has FEC protection enabled is optimized from 1080p down to 720p. Pressing the multifunction sleep/wake/on/off button and then pressing it again may work around this issue

 

Cisco Jabber for Windows 9.2.1

Tested CUCM to VCS/Conductor SIP and CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended
Cisco Jabber Video for TelePresence (Mac OSX) 4.6(17194)

Tested SIP and SIP to H.323 interworking:

  • Video to and from this endpoint can have incorrect aspect ratio when using H.263 or H.263+ (these are not the default codecs)
Cisco Jabber Video for TelePresence (Movi) 4.6.3.17194

Tested SIP and SIP to H.323 interworking:

  • In some cases increasing resources for a call will result in low frame rate from the endpoint. (Issue identifier CSCud79739)
Cisco TelePresence Codec C40 TC6.1.1

Tested H.323 and SIP:

  • No issues found
Cisco TelePresence Conductor XC2.3

Tested with 3.1(1.95): No issues found.

Tested TelePresence Server on Virtual Machine with 3.1(1.82): There is an issue with the TelePresence Server on Virtual Machine XMLRPC interface resulting in "Connection disconnected unexpectantly" errors in the Conductor log. This issue was fixed in release 3.1.(1.96).

Cisco TelePresence Conductor XC2.2

No issues found.

Cisco TelePresence Content Server S5.3

Tested H.323 and SIP:

  • In low bandwidth H.323 calls, an incorrect aspect ratio may be chosen
  • Changing the display settings during the call may cause streaming and podcast output to fail
  • DTMF is not supported in Conductor-based deployments
  • Audio only calls to a TCS will not be recorded
Cisco TelePresence C Series, Cisco TelePresence MX Series, Cisco TelePresence System EX Series, Cisco TelePresence SX20 Quick Set TC5.1.7

Tested SIP:

  • The endpoint does not respond to normal keyframe requests when it receives incorrect timestamps in ClearPath messages. The issue can manifest as a loss of video from the endpoint. (Issue identifier CSCui34688). This issue can be worked around by disabling ClearPath on the endpoint. The issue is resolved by upgrading the endpoint software.
Cisco TelePresence Management Suite (TMS) 14.4

Tested Cisco Multiparty Media 310/320, Cisco TelePresence Server 7010 / MSE 8710 and Cisco TelePresence Server on Virtual Machine.

No major issues found in testing.

Cisco TelePresence SX20 Quick Set TC5.1

Video from this endpoint on this software version is not decoded when ClearPath has been negotiated with the TelePresence Server and there is high packet loss. Upgrading the endpoint software resolves this issue.

Cisco TelePresence SX20 Quick Set TC6.1.1

Tested H.323, SIP, CUCM to VCS/Conductor SIP, and CUCM to VCS H.323 interworking:

  • No issues found
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.3

Tested TIP:

  • No issues found

Tested CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended

We recommend that you your TX systems be running a minimum TX version of 6.0.3 with TelePresence Server software 3.1.

Cisco TelePresence System 500-37 1.10.1

Tested TIP:

  • Under rare circumstances video artefacts may be seen when leaving the lobby screen in 720p calls. (Issue identifier CSCuh92519)
  • Calls can connect at the wrong bandwidth when SIP UPDATE messages are disabled the call path, for example, when the call is routed via Conductor. (Issue identifier CSCuh97074)
  • If the conference security state changes to insecure, and then changes back to secure, the security indicator on this endpoint still (incorrectly) indicates that the conference is insecure

Tested CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended
Cisco TelePresence System 500-37, 1000, 1100, 1300-65, 3000, 3010, 3200, and 3210 1.10.2

A minimum CTS software version of 1.10.2 is required for use with TelePresence Servers running version 3.1 software.

Cisco TelePresence System 1700 MXP F9.3.1

Tested H.323 and SIP:

  • Automatic content handover does not work if MXP tries to present immediately after another endpoint sends content. (Issue identifier CSCud64503)
  • Under rare circumstances, corruption may be seen when the MXP transmits content in main video. (Issue identifier CSCuh93850)
  • Under some circumstances, continuous presence panes are cropped off the bottom of the screen when this endpoint is receiving CIF/4CIF resolutions. (Issue identifier CSCuh93846)
  • High motion video to the MXP 1700 can result in repeated transient corruption. This issue is only seen with Media 310/320 platforms, and when the resolution sent to the endpoint is w576p or above
Cisco TelePresence System EX60 TC6.1.1

Tested H.323 and SIP:

  • A flicker is seen when the video from a participant changes from a continuous presence pane into the main pane. Seen when active speaker changes or when making a participant important. (Issue identifier CSCuh92611)
Cisco TelePresence System EX90 TC6.1.1

Tested H.323, SIP, and CUCM to VCS/Conductor SIP:

  • A flicker is seen when the video from a participant changes from a continuous presence pane into the main pane. Seen when active speaker changes or when making a participant important. (Issue identifier CSCuh92611)

Tested CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended
Cisco TelePresence System TX1300 47 TX6.0.2

Tested TIP:

  • In some circumstances, content video sent to the TX1300 47 may show artefacts
  • If the conference security state changes to insecure, and then changes back to secure, the security indicator on the TX1300 47 still (incorrectly) indicates that the conference is insecure

Tested CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended
Cisco TelePresence System TX9000 TX6.0.2

Tested TIP:

  • In some circumstances, content video sent to the TX9000 may show artefacts
  • If the conference security state changes to insecure, and then changes back to secure, the security indicator on this endpoint still (incorrectly) indicates that the conference is insecure

Tested CUCM to VCS H.323 interworking:

  • Interworking calls from this endpoint is not recommended
Cisco TelePresence Video Communication Server (VCS) X7.2.2
  • Ensure that the "SIP SDP attribute line limit mode" is set to "Off" on zones used by TelePresence Server calls if they are configured with a custom zone profile
  • Increasing resources for a call that leaves the TelePresence Server as H.323 and is interworked by the VCS to SIP can cause the call to fail. (Issue identifier CSCud64471)
T3 TelePresence, T1 TelePresence TC6.0.1

Tested version TC6.0.1/TCU4.2.1 in remotely managed mode.

Tested H.323:

  • PIN entry and layout changing will not function as the T1 and T3 do not support DTMF/ FECC to theTelePresence Server
  • Note that some T1 and T3 functionality is not supported when the TS operates in Remotely Managed mode
  • T3 systems will prefer 1600x1200 resolution when XGAp60 should be shown

Tested H.323 to SIP interworking:

  • No issues found 

Cisco

Product(s) Software releaseComments
Cisco Desktop Collaboration Experience DX650 10-0-1-110

Tested CUCM to VCS/Conductor SIP and CUCM to VCS H.323 interworking:

  • No issues found
Cisco Unified Communications Manager 9.0.1.10000-37

If the iX protocol is enabled on the TelePresence Server (for ActiveControl), then call hold may fail. (Issue identifier CSCug89748)

Cisco Unified Communications Manager 9.1.1.10000-11

If the iX protocol is enabled on the TelePresence Server (for ActiveControl), then call hold may fail. (Issue identifier CSCug89748)

Cisco Unified Communications Manager 9.1.2

No issues found.

Cisco Unified Communications Manager 8.6.2.21900-5

If the iX protocol is enabled on the TelePresence Server (for ActiveControl), then calls will fail. To work around this, either disable iX on the TelePresence Server or route calls through a newer version of Unifed CM with iX disabled on the relevant trunk.

Cisco Unified IP Phone 9971 9.3.2 SR1

Tested CUCM to VCS/Conductor SIP and CUCM to VCS H.323 interworking:

  • Video calls connect as audio-only if call bandwidth is below 280 kbps

Huawei

Product(s) Software releaseComments
ViewPoint 9039 VCT V100R011C02B013SP40

Tested H.323 and SIP:

  • Although this endpoint is interoperable in certain scenarios, it is not recommended with prefered Cisco TelePresence deployments

LifeSize

Product(s) Software releaseComments
Express 220 4.11.13

Tested H.323 and SIP:

  • Although this endpoint is interoperable in certain scenarios, it is not recommended with prefered Cisco TelePresence deployments
Icon 600 LS_RM3_1.1.1 (7)

Tested SIP:

  • Although this endpoint is interoperable in certain scenarios, it is not recommended with prefered Cisco TelePresence deployments

Microsoft

Product(s) Software releaseComments
Lync 2010 (without AMGW) 4.0.7577.4103

Tested SIP and SIP to H.323 interworking:

  • This endpoint may display incorrect aspect ratio during low bandwidth calls
  • Hold/resume works incorrectly if initiated while the TS is sending a reINVITE
  • DTMF fails after the TS sends a reINVITE

 

Microsoft Lync 2010 through Cisco TelePresence Advanced Media Gateway 4.0.7

Tested SIP and SIP to H.323 interworking. Tested with AMGW 10.1(1.34):

  • This endpoint may display incorrect aspect ratio during low bandwidth calls
  • Under rare circumstances, the unencrypted icon can display when the call is encrypted
  • In some circumstances, optimization may not result in an increase in video quality, but will not adversely affect call quality

Polycom

Product(s) Software releaseComments
HDX 8000 3.1.1.3-36019

Tested H.323 and SIP:

  • HDX does not support redial missed/rejected calls due to an endpoint limitation
  • If the endpoint and TelePresence Server are registered to different peers of a VCS cluster, call bandwidth may be limited to 64 kbps. This issue only occurs with H.323 calls
  • Media quality may be unreliable when using H.261 or H.263 (these are not the default codecs). Use the default codec to avoid this issue
HDX 9006 3.1.0-23277

Tested H.323 and SIP:

  • HDX does not support redial missed/rejected calls due to an endpoint limitation
  • If the endpoint and TelePresence Server are registered to different peers of a VCS cluster, call bandwidth may be limited to 64 kbps. This issue only occurs with H.323 calls
  • Media quality may be unreliable when using H.261 or H.263 (these are not the default codecs). Use the default codec to avoid this issue
OTX 300 3.1.0-23277

Tested H.323 and TIP:

  • OTX does not support redial missed/rejected calls due to an endpoint limitation
  • If the endpoint and TelePresence Server are registered to different peers of a VCS cluster, call bandwidth may be limited to 64 kbps. This issue only occurs with H.323 calls
  • 4:3 content sent to OTX may be displayed as 16:9 due to endpoint limitation
  • Encryption is not supported in TIP call architecture
  • DTMF tones are not suppressed
RealPresence Group 500 4.0.2-40451

Tested H.323 and SIP:

  • Siren14 and H.263 codecs are not supported due to endpoint limitations.
  • Low bandwidth H.323 calls do not support encryption
  • FECC does not work over SIP when the call is via CUCM
  • Endpoint may continue to use higher bandwidth after optimization
  • SIP calls to this endpoint may fail if TIP support is enabled on the endpoint. Work around this issue by adding it as a legacy TIP endpoint on the TelePresence Server (if in locally managed mode), or using the "force TIP" option via the API (if in remotely managed mode)

 

RadVision

Product(s) Software releaseComments
Radvision XT5000 3.0

Tested H.323 and SIP:

  • 60fps video is not supported in calls with this endpoint
  • The TelePresence Server only supports H.264 to this endpoint (default codec)
  • Encryption and the G.722.1 audio codec are not supported in SIP calls 
  • We recommend disabling HiP/TSVC on this endpoint, when using it with the TelePresence Server, because it can cause video to fail during calls
  • 1080p content is not supported due to an endpoint limitation

Sony

Product(s) Software releaseComments
PCS-G50 2.72

Tested H.323 and H.323 to SIP interworking:

  • At low bandwidths, in H.323 to SIP interworked calls, this endpoint may not handle audio properly. You can mitigate this by disabling AAC codec for this endpoint
  • Video to this endpoint may fail if the TelePresence Server is in remotely managed mode, because the default aspect ratio in that mode is 16:9. Work around this issue by setting the TelePresence Server to allow all resolutions.