Cisco TelePresence

Interoperability Database

Warning - In preview mode

Hierarchical Navigation

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 4.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 TelePresence Conductor XC3.0

Tested with version 4.1(1.79).

No issues found.
Cisco TelePresence Content Server S5.3

Tested SIP.

  • Audio only calls to a TCS will not be recorded.
  • Reporting of media packet loss from the TelePresence Server to the TCS may be unreliable.
  • CSCul97025: Video quality will be very poor in calls with a Media 3x0 device at 720p and higher resolutions.
Cisco TelePresence IX5000 and IX5200 8.0

No issues.
Cisco TelePresence Management Suite (TMS) All

On TelePresence Server 4.1 and above in locally managed mode, TMS may experience issue CSCvd62833. i.e. Multiple ringing pop-ups may be seen on an endpoint (whose auto-answer is OFF) in a TS hosted conference.
Cisco TelePresence System EX60 TC7.2.1

Tested SIP.

No issues found.
Cisco TelePresence System EX90 TC7.2.1

Tested VCS and SIP CUCM.

No issues found.
Cisco TelePresence Video Communication Server (VCS) X8.6

No issues
T3 TelePresence TC6.0.1 / TCU4.2.1

Tested H.323 interoperability.

  • PIN entry and layout changing will not function as the T1 and T3 do not support DTMF/ FECC to the TelePresence Server.
  • Note that some T1 and T3 functionality is not supported when the TelePresence Server operates in Remotely Managed mode. For further details, see page 2 of the v3.0 release notes.
  • Note that segment switching mode is not supported on T3s that do not provide positional audio i.e. T3 Custom Edition.
  • CSCus95070 known to affect 4.1(1.79).

Cisco

Product(s) Software releaseComments
Cisco Desktop Collaboration Experience DX650 10-2-2-23

Tested SIP CUCM.

  • Video sent from the TelePresence Server to the DX650 will be cropped due to endpoint limitations.
Cisco Jabber for Android 10.6.0

Tested SIP CUCM.

  • Using Jabber for Android on an unsupported platform can result in a sub-optimal experience.
Cisco Jabber for Mac 10.6.0

Tested SIP CUCM.

  • Reporting of media packet loss from the TelePresence Server to Jabber for Mac may be unreliable.
Cisco Jabber for Windows 10.5.2 Build 45439

Tested SIP CUCM.

No issues found.
Cisco TelePresence IX5000 and IX5200 8.0.1(72)

Tested SIP CUCM.

  • Reporting of media packet loss from the TelePresence Server to multi-screen endpoints may be unreliable.
Cisco TelePresence System TX9000 series TX6.1.5(39) P2

Tested SIP CUCM. ·        

  • Low bandwidth calls to this endpoint are not supported.
  • Reporting of media packet loss from the TelePresence Server to multi-screen endpoints may be unreliable.
Cisco Unified IP Phone 8945 9-4-2-8

Tested SIP CUCM.

No issues found.
Cisco Unified IP Phone 9971 9.4.2.13

Tested SIP CUCM.

  • Icons will not be visible at some resolutions due to video overlapping the screen size.

LifeSize

Product(s) Software releaseComments
Icon 600 LS_RM3_1.3.2(2)

Tested SIP.       

  • We recommend against using this endpoint in standard TelePresence Server deployments.
  • Token stealing is not supported with this endpoint.      
  • SIP calls via Conductor will fail if BFCP is enabled.     
  • Low bandwidth SIP calls will result in frozen video.
  • DTMF from the Icon 600 to Cisco Multiparty platforms will not work due to an endpoint bug.
  • The endpoint will fail to connect to TelePresence Server conferences set to be unencrypted when encryption is set to optional on the endpoint.

Microsoft

Product(s) Software releaseComments
Lync 2013 15.0.4420.1017

Tested SIP. ·        

  • CSCun60010: Icons may appear distorted at some resolutions.
  • CSCus26026: Video from Lync 2013 in an encrypted call to a Media 3x0 TelePresence Server will have a high number of key frames.

Polycom

Product(s) Software releaseComments
OTX 3.1.2-35267

Tested SIP.

  • The Polycom OTX system does not support the media packet loss reporting feature. Media packet loss from the TelePresence Server to the OTX will not be reported on the TelePresence Server.
RealPresence Group 700 4.1.3-111080

Tested SIP.

  • We recommend restricting this endpoint to using 16:9 resolutions as some video artefacts can occur or video can fail while using 4:3 resolutions.

RadVision

Product(s) Software releaseComments
Scopia XT5000 3.2.1.10

Tested SIP. ·         

  • In order to use the H.323 protocol the H.264 high profile option must be disabled on the endpoint.
  • The XT5000 uses TCP BFCP which the TelePresence Server does not support, so the content channel will be displayed in main video.
  • IPv6 calls to the TelePresence Server will not function due to an endpoint bug.