ManagingLast updated August 28, 2020
This topic describes any interoperability issues between third-party manufactured video endpoints and StarLeaf.
|Cisco SX20||TC7.0.2||SW-7830||Occasionally, if the Cisco SX20 participant tries place a call internal to their organization using a 4-digit internal number the Cisco SX20 will become unresponsive, and require a restart. This can happen with 4-digit internal or 9-digit numbers including the organization extension||To avoid this, always dial using the full legacy H.323 address|
|Cisco SX10||CE8.2.0||No interoperability issues||Note that CE8.2.0 is the minimum version to support H.323 calling|
|Cisco EX90||TC6.1.0||No interoperability issues|
|C20||TC4.2.4||SW-8694||BFCP content fails when calling between the C20 and StarLeaf via SIP||This issue only affects older versions of the C20 running TC4.x.x software. Upgrading to TC5.1.13 or later will resolve the issue|
|Cisco T150||L5.1Beta4||No interoperability issues|
|Cisco E20||TE4.1.1||No interoperability issues|
|Cisco 1700MXP||v9.1 PAL||SW9032||MXP 1700 restarts unexpectedly when dialed into a conference over SIP||Use H.323 instead of SIP|
|Lifesize Icon||220.127.116.11||No interoperability issues|
|SW 7527||No video is received by the registered LifeSize Team (H.323) in a Blue Jeans conference. It still sends and receives audio||This participant will only receive audio|
|No interoperability issues|
|No interoperability issues|
|Lifesize Cloud||Lifesize Cloud supports SIP BFCP screen-share, however is not compatible with the StarLeaf platform. This means that StarLeaf users cannot send screen-share when dialed into LS cloud using SIP||If you need to dial in to Lifesize Cloud from any endpoint connected to the StarLeaf platform, use H.323 and not SIP for the call|
|Polycom HDX||3.1.4||HDX “Basic/Diagnostic Mode” causes problems. Also, the HDX can fail to use H.460 on its registrations even when it has been configured on the HDX web interface||Do not use HDX “Basic/Diagnostic Mode” when calling StarLeaf.
If the HDX fails to use H.460 on its registrations, on the HDX web interface uncheck the H.460 option and then re-check the option to ensure that is working
|Polycom VSX||18.104.22.168||No interoperability issues|
|Polycom Group 500||5.1.2||No interoperability issues|
|Polycom Group 500||4.2.0||SW 7505||Some calls might fail due to the Poly selecting an invalid codec for a call||Upgrade to at least version 5.1.2 which has no known issues|
|Polycom RMX||SW 7268||When dialing multiple registered H.323 endpoints into a Polycom RMX unit, screen-sharing may fail to open correctly or fail to be displayed by some endpoints|
|Polycom Realpresence Desktop||SW 1314||Polycom Realpresence Desktop does not display content from StarLeaf endpoints or conferences and is the result of its own device-specific behavior|
|Sony G50||V.02.72||SW 7295||Sharing content with the Sony G50 is unreliable. When sharing content to it, particularly with Breeze, an issue can occur, which causes the G50 to stop outputting video to its screen||Avoid sharing content with Breeze where there is a Sony G50 in the call. Instead, use a StarLeaf video endpoint to share content|
|Sony G50||V.02.72||SW 7293||When joining a scheduled conference, whenever the conference consists of just two members, the video shown on the Sony G50 will freeze||When a third participant joins, the video will unfreeze. More participants joining will continue to work normally. Dropping down to just two participants will freeze the video again|
|Sony G50||V.02.72||SW 7290||When calling StarLeaf using the H.263+ video mode (which is required to share content on the Sony G50), video from StarLeaf is not displayed by the G50||Switch to H.264 video mode on the Sony G50 (found under Communication settings, Video Mode)|
|Scopia XT4300||V 08.03.
|SW 9363||In SIP calls, the Scopia XT4300 does not receive video||Use H.323 instead of SIP|
|Yealink VC120||No interoperability issues|
|Huawei TE10||V500R003C20||No interoperability issues||
The endpoint does not allow a user to control the camera of another user.
The endpoint also does not support plug-and-play content sharing.
For Windows users: to enable content sharing, you need to download AirPresence Client on your PC/mobile device, and connect the endpoint to the PC/mobile through WiFi or Bluetooth
To download the app, navigate to the IP address of the endpoint in-browser, and click “Download AirPresence Client”. Within the client, click “Find devices” and choose the appropriate endpoint from the list
The client prompts you for a username and password. Alternatively, you can connect to the client on the endpoint-side using the remote
|Cisco Codian MCU||4.5(1.55)||SW 7285||When calling to a Cisco Codian MCU via SIP, BFCP will fail, causing any content sharing to use the video channel instead. This is a Cisco Codian MCU issue||Use H.323 instead of SIP|
|Cisco Acano bridge||No interoperability issues|
|H.323||SW 5394||H.323 endpoints cannot dial by domain name, for example dialing “mcu.starleaf.com” does not work||Dial these addresses by IP address instead. To find the IP address, ping the domain address using a command line|
|SIP||SW 7019||Using a SIP device to put a call on hold is not supported and will cause the call to drop either immediately or when the call is resumed|
|SIP||SW-5441||H.263 negotiation is not supported for SIP calls||Use H.323 instead of SIP|
|SIP||SW 2838||Far End Camera Control does not work when communicating over SIP||Use H.323 instead of SIP|