The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Including:
Feature alignment with Cisco Jabber Guest for iOS 10.5, with the exception of HD support
Support for Android 5.0, Lollipop
SDK documentation and sample apps
In Cisco Jabber Guest Administration, use the Android-related fields that appear on the page to set up Android support.
In earlier releases, Cisco Jabber Guest was able to dial devices registered to Cisco Unified Communications Manager, as well as TelePresence Servers and multipoint control units (MCUs). The capability to dial devices registered to Cisco VCS was added in this release.
For devices that are registered with Cisco VCS, the call path must include Cisco Unified Communications Manager.
The Cisco TelePresence Systems (CTS) noted as unsupported in the Cisco Jabber Guest10.0 Release Notes are now supported.
Chrome will be removing support for Netscape Plug-in Application Programming Interface (NPAPI) plug-ins in early 2015. Cisco Jabber Guest will continue Chrome support by using a Cisco Jabber Guest Add-on and a Cisco Jabber Guest Extension to deliver a nearly identical user experience from the web.
Note | Throughout the Cisco Jabber Guest documentation we use the term plug-in to refer to the Cisco Jabber Guest Plug-in, Cisco Jabber Guest Add-on, and Cisco Jabber Guest Extension. |
Cisco Jabber Guest 10.5 adds support for Chrome 64-bit for Mac and Chrome 64-bit for Windows.