FCSDK Release Notes
FCSDK Release Notes
Updated: 2023-07-03
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation
in the United States and/or other countries.
iOS and iPadOS is a trademark or registered trademark of Cisco in the U.S. and other countries
and is used under license by Apple Inc. Apple is a trademark of Apple Inc.
All other trademarks mentioned in this document are the property of their respective owners.
Contact Information
Related Documentation
Make and receive voice and video calls directly from a Web browser to telephones and
other browsers, without employing web plugins.
New Features
Release ID Features
CBALA-
3.4.11 Increase media idle timeout during upgrade from 10s to 30s
578
CBALA-
Generate jsdoc for the FCSDK web api
568
CBALA-
Restore lockout feature on FAS login
524
CBALA-
Install CLI plugins in product install directory
519
CBALA-
WebRTC version upgrade FCSDK Windows
195
CBALA-
3.4.7.1 Updated Log4j to version 2.x
497
CBALA-
Added Flexfec-03 as a banned codec
497
CBALA-
3.4.4 GLKit Framework Deprecated on iOS
135
CBALA-
No Controller.log and event.log for media broker
294
CBALA-
Android SDK / Torch and Auto-Focus Features
252
CBALA- FCSDK Android Missing Self View When Open Camera to take
3.3.22
214 picture and come back to app
CBALA- When the client mute the audio and then change the camera, the
170 audio becomes unmuted
CBALA-
3.3.21 FCSDK iOS bitcode support
17
CBALA-
FCSDK Android Picture in Picture support
90
CBALA-
3.3.20 Support H.264 on phones with MediaTek chipset
33
The sample app has a new checkbox on the login page “Supports
renegotiation”. This is an additional setter method on the SDK. The
CBALA-
3.3.18 customer will need to change their Android app to enable the new
117
functionality. They can either do this for all use cases or make it
conditional on the make/model of phone
CBALA-
Explicitly close websocket connection on FCSDK JS SDK
50
Video quality may drop on calls that last over an hour due to an issue with dynamic
bandwidth values dropping to configured floor value
When sharing content with a TPS, resuming from hold on the browser does not recover the
content stream
When building an iOS application, you may need to add the following libraries:
GLKit.framework
The Android SDK only comes with native libraries for the ARM architecture. The application
will run slowly on devices running on x86 architectures.
In current versions of Safari, ringtones and dialtones do not play unless the user selects
Allow All Autoplay for the currently open site.
FCSDK bundles the Jackson libraries. These have been updated to version 2.9.4 to avoid
any risk from the Jackson vulnerability (CVE-2017-7525).
FCSDK does not use the Jackson libraries in the way that allows exploitation of this vulnerability,
so earlier versions of FCSDK are safe, and do not need to be upgraded or patched immediately.
G722
iLBC
CN
isac
g7221
MP4A-LATM
See the FCSDK Administration Guide for details on how to make these changes.
Please be aware that future release of Fusion Application Server may be made available
which fix issues in this version. The definitive version to use is the one made available on the
download server alongside this release of Fusion Client SDK.
Web Browser
You can use Fusion Client SDK to develop applications that take advantage of the latest
browser technologies with no additional client or plug-in. These applications are supported by the
following browsers:
Co-
Browser Version WebRTC Plugin Audio Video
browse
Google Chrome, Mozilla Firefox, Microsoft Edge (Chromium) – Please check supported
builds of Windows 10. See https://support.microsoft.com/en-us/help/13853/windows-
Google Chrome for Android - H.264 codec support for mobile devices are available only
for a limited number of devices.
Desktop
Minimum CPU and memory equivalent to an Intel Core 2 Duo with 2 GB of RAM and 2 MP front
facing camera - Intel Core i3/i5/i7 2nd generation or newer (Sandy Bridge) preferred.
iOS
CPU and memory equivalent to the iPhone 8 or better, as in the following devices:
iPad mini, iPad mini with Retina display;iPad mini 3, iPad mini 4
Users of the iOS sample application on iOS 15 will experience some issues with the UI, however
the application remains fully functional.
Applications developed with Fusion Client SDK are compatible with devices running iOS 12 and
later; iOS versions earlier than v13 are not supported.
Due to hardware restrictions Fusion Client SDK only supports iPhone 8 and above, and iPad 2
and above.
Android
Minimum CPU and memory equivalent to a Samsung Galaxy S4 (1.9 GHz Quad-core
Snapdragon GS4, 4G or Wi-Fi a/b/g/n/ac and 2 MP front facing camera), as in the following
devices:
The minimum version of the Android API that Fusion Client SDK supports is Lollipop v9.0 (API
v28).
H264 codec support is available to following chipset only and Huawei Kirin is not supported.
Qualcom
EXYNOS
MediaTek
SAMSUNG-SGH-I337(Galaxy S4), Google Nexus 7 and Google Nexus 4 don’t support H264
because of its poor H264 support. please use vp8 or vp9 instead.
Windows
The Windows SDK and the .NET SDK target the x86 architecture only; they are compatible with
Windows 10 (32 and 64 bit).
BFCP
Java
Java Packages:
OpenJDK
Each hardware platform hosting the Fusion Application Server requires the Oracle Java SE
Development Kit (JDK)or Java Runtime Environment (JRE) or OpenJDK. Ensure that you install
the version of Java with the applicable word size for your operating system.
Unless they are required for a particular reason, it is recommended that you remove any older
versions of Java, and obtain the new installation packages from your chosen deployment-
platform manufacturer.
If you install Java from the platform manufacturer, ensure that the distribution is the standard
JDK/JRE, and is one of the supported versions listed above.
If you must add a later version of the JDK or JRE alongside an existing Java installation, ensure
that all paths to the new Java installation are correctly altered in the startup files; in addition,
ensure that you use an appropriate RPM file.
It is recommended that you do not change the existing paths to the older Java package because
this may adversely affect other platform-resident applications that depend on the earlier version
of Java.
CBALA-
4.2.3 iOS: Back camera preview video mirrored
734
CBALA-
3.4.11.2 Media Broker installation failure bug fix
624
CBALA-
Android only; FCSDK Android SDK reconnect issue
551
CBALA- Android only; Javadocs are not being produced for the
567 Android SDK
CBALA-
3.4.7.1 Set preffered audio input re-added to Safari
521
CBALA- iPhone 11 Pro - FCSDK 3.3.21 iOS, one way video issue
3.3.23.1
221 (No video from jabber to iOS)
CBALA-
3.3.23 Security scan vulnerabilities FCSDK(Android)
242
CBALA-
3.3.23 FCSDK Android Custom Audio Device Manager Crash
225
CBALA-
3.3.22 VP8 and VP9 not included in SDP from iOS client
253
CBALA-
3.3.21 Getting issue if don’t use the UC.setHostNameVerifier
193
CBALA-
3.3.21 Partiallyvideo of the previewView becomes double
192
CBALA-
3.3.21 Android, all calls are failing from web to Android SDK
190
CBALA-
3.3.21 cli.sh is not working on FCSDK-3.3.12
71
CBALA-
3.3.20.1 Android, all calls are failing from web to Android SDK
190
CBALA-
3.3.20.1 Xiaomi Mi A1 one way video
188
CBALA-
3.3.20 Crash on Nokia 4.2
94
CBALA-
3.3.20 NPE thrown from Tomcat MimeHeaders class
130
CBALA-
3.3.19 Andoid SDK does not support HTTP websocket
134
CBALA-
3.3.19 Android 11 problem switching the camera in call
118
CBALA-
3.3.19 Remove Plan-B support from MB
65
CBALA-
3.3.17 iOS 13.3+ crashes mainly apps using SWIFT
59
CBALA- The image on the video from agent doesn’t fit the size of
3.3.17
70 the container
CBALA-
3.3.16 FCSDK for Android SDK error handling
14
CBALA-
3.3.16 Call issue on iOS Safari browser
3
CBALA-
3.3.12 Camera is not released even after call is terminated
2
CBALA-
3.3.12 Safari on iOS freeze
3
CBALA-
3.3.12 Android – SDK Error handling adjustment
14
CBALA-
3.3.12 Chrome 86 unable to make call/ hold/unhold issue
36
CBALA-
3.3.12 NQI not working in FireFox
21
Known Issues
The following known issues are present in this release:
Bug ID Description
When iOS or MacOS Safari is receiving a call whilst they have their video
CBALA-
disabled, there is no audio on the Safari Callee side.
490
(3.4.5
Workaround: Please use 3.4.4 or wait for fixes version if you are using Audio
only)
only call.
iPhone - FCSDK 3.3.21 iOS, one way video (No video from Cisco jabber to
CBALA- iOS)
221
(3.3.21) Workaround: Please upgrade iOS 14.7 or higher. Most of iPhones is OK but
iPhone11 Pro is not working.
Calling from Chrome with Local Video set to On, media error if camera is not
9209
attached
iOS and Android: Console error on call hold. Call from device to browser—
8695
when call is held at browser, cannot resume, and browser crashes.
Invoking hold then resume immediately results in both endpoints being placed
on hold. When two FCSDK clients are in a call, invoking hold() on the UC call
object and then immediately invoking resume() before the hold operation has
completed results in both endpoints being placed on hold, without any way of
resuming the held calls.
8439
Workaround: Do not allow the user to trigger resume() from the UI for a few
seconds (for example, 5 seconds) after they trigger hold(); similarly do not
allow the user to trigger hold() from the UI for a few seconds after they trigger
resume().
Workaround: Wait for about five minutes before making the second call; or
click the camera button before making the second call.
8069 Safari ‘Plugin Failure’ when number not found, or number busy (call rejected)
7194 iOS Sample Application no longer builds against the iOS 6 SDK
Certain video endpoints cannot render 720x1280 video (that is, 720p in portrait
mode, for example from a mobile device).
6700 Workaround: Either ensure the video stream from the mobile device cannot
be rotated into portrait mode or update the Video Resolution Configuration
section of the Media Configuration through the Admin UI or CLI to restrict the
possible dimensions of the image.
If Video Scaling Mode is set to NONE for the first participant dialing into a
TPS, that participant will not see any video.
5961
Workaround: Ensure Scaling Mode is set to STRETCH (the default) when
using FCSDK to dial into a conference
Audio codec offer from iOS causes SDP failure in media broker.
5242
Workaround: Add G722 to the set of banned codecs.