Cisco Jabber 11.6 is fully IPv6 ready, it works as normal in pure IPv6 and hybrid networks, subject to a number of limitations (for more information see the Planning Guide for Cisco Jabber 11.6. Cisco Collaboration solutions does not currently fully support IPv6. For example, Cisco VCS Expressway for Mobile and Remote Access has limitations in pure IPv6 networks that require NAT64/DNS64 to be deployed in mobile carrier networks. Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service don't currently support HTTPS in pure IPv6 networks.
IPv6 is configured using the IP_Mode parameter to set the protocol to IPv4, IPv6, or dual stack. Dual stack is the default setting. The IP_Mode parameter can be included in the jabber-config.xml file, the bootstrap for Windows, and the URL configuration for Mac and Mobile clients.
The network IP protocol used by Jabber when connecting to services is determined by the following factors:
The jabber-config.xml IP_Mode parameter.
The client operating system IP capabilities.
The server operating system IP capabilities.
The availability of a DNS record for IPv4 and IPv6.
Cisco Unified Communications Manager SIP setting for softphone devices configuration for IPv4, IPv6, or both. The SIP connection setting for softphone devices must match the Jabber IP_Mode parameter setting to make a successful connection.
Underlying network IP capabilities.
On Cisco Unified Communications Manager, the IP capability is determined by generic server settings and device-specific settings.
When you use Jabber in IPv6_only mode, NAT64/DNS64 is required to connect to an IPv4 infrastructure. For example, when connecting to Cisco WebEx Messenger service, Cisco VCS Expressway for Mobile and Remote Access, and Cisco Spark.
For more information about the IP_Mode parameter, see the Parameters Reference Guide for Cisco Jabber 11.6. For more information about IPv6 support, see the Planning Guide for Cisco Jabber 11.6.
Cisco Jabber Diagnostics Tool
To access the Cisco Jabber Diagnostics window, users must bring the hub window into focus and enter Ctrl + Shift + D. Users can update the data by clicking the Reload button. Users can also save the information to an HTML file by clicking the Save button.
The Cisco Jabber Diagnostics Tool is available by default. To disable this tool, set the DIAGNOSTICS_TOOL_ENABLED installation parameter to FALSE. For more information about this installation parameter, see On-Premise Deployment for Cisco Jabber 11.6, or Cloud and Hybrid Deployments for Cisco Jabber 11.6, depending on your setup.
New Configuration for Meeting Notifications
The DisableNonAcceptMeetingReminder parameter determines whether the Cisco Jabber popup meeting notification is displayed for nonaccepted WebEx Meetings. The default value is false, which means that the Jabber popup meeting notification displays for nonaccepted WebEx Meetings.
For more information about this parameter, see the Parameters Reference Guide for Cisco Jabber 11.6.
User Interface Updates
Presence pills and avatars have been redesigned and now have a round shape. Accessibility icons have also been redesigned. For more information about accessibility icons, see the Cisco Jabber for Windows 11.6 User Guide.
Copyright © 2016, Cisco Systems, Inc. All rights reserved.