These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Mac Release 11.6. These release notes are updated for every maintenance release but not for patches or hot fixes. Note that each maintenance release includes the features, requirements, restrictions, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Mac, we recommend that you review this document for information about issues that may affect your system. When your users are enabled for logging instant message history, they can do the following:.Users can choose if the chats are stored locally and also where the chats are stored. This is configured using the EnableAutosave parameter, for more information see the Parameters Reference Guide for Cisco Jabber 11.6.Users can save chats to file.

Release Notes for Cisco Jabber for Mac 12.8 26/Mar/2020 Updated; Release Notes for Cisco Jabber for Mac 12.7 14/Jan/2020; Release Notes for Cisco Jabber for Mac 12.6 14/Jan/2020; Release Notes for Cisco Jabber for Mac 12.5 29/Jan/2019; Release Notes for Cisco Jabber for Mac 12.1 27/Sep/2018. 1 Cisco Jabber does not handle the first call after reconnecting to the network. Disconnect network when call is active. Wait for calls to get end. Connect the network back and let Cisco Jabber regain its status. Make an incoming or outgoing call. After accepting the call, call control through headset is not possible.

This is configured using the EnableSaveChatToFile parameter, for more information see the Parameters Reference Guide for Cisco Jabber 11.6For more information on allowing clients to log instant message history, see the Feature Configuration for Cisco Jabber 11.6 guide. IPv6Cisco Jabber 11.6 is fully IPv6 ready, it works as normal in pure IPv6 and hybrid networks with the limitations listed in the Requirements chapter of 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 don't currently support HTTPS in pure IPv6 networks.This feature is configured in Jabber using the IPMode parameter to set the protocol to IPv4, IPv6, or dual stack. Dual stack is the default setting. The IPMode parameter can be included in the jabber-config.xml file, the bootstrap for Windows, and the URL configuration for Mac and Mobile clients.

For more information, see the Parameters Reference Guide for Cisco Jabber 11.6.The network IP protocol used by Jabber when connecting to services is determined by the following factors:.The jabber-config.xml IPMode 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 IPMode 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. Find license keys on computer system. The following table lists the expected Jabber connections given the various settings, this list assumes that the DNS records for IPv4 and IPv6 are both configured.When you use Jabber in IPv6only 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. Ports for Other Services and ProtocolsIn addition to the ports listed in this section, review therequired ports for all protocols and services in your deployment. Severity LevelDescription1 CatastrophicReasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. No workarounds exist.2 SevereImportant functions are unusable and workarounds do not exist.

Other functions and the rest of the network is operating normally.3 ModerateFailures occur in unusual circumstances, or minor features do not work at all, or other failures occur but low-impact workarounds exist.This is the highest level for documentation bugs.4 MinorFailures occur under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds and performance impact is tolerable.5 CosmeticDefects do not cause any detrimental effect on system functionality.6 EnhancementRequests for new functionality or feature improvements.

Check the release notes on our website for changelogs and important information about this app: over audio, video and web from your iPad and iPhone whenever ideas spark. Join the conversation in a space from wherever you are and with whomever you like.Spaces are virtual meeting rooms only radically better. Meet your project team in a space and see your notes and agenda from last time you visited.

Check in anytime, the space is always available.Enter Your spaceIf your company has Cisco Meeting Server, access your space by downloading the client and logging in. Choose the space you want to join and simply press the green button.Invite AnyoneOnce you have entered a space, you can invite others with a directory search.

To invite someone outside of your organization, email the weblink found at space Info. The invited can securely join a video call using their browser.Features.Use the Cisco Meeting App on both the iPad and iPhone.Join a call using video, audio or by sharing content over web.Move seamlessly between devices while on a call, or use them at the same time.

For example use your phone for voice privacy and your iPad for video.Send chat messages during a call, leave notes in the space.Calls can be ad hoc or scheduled. ToddDaytona, Not good enoughThis app could fill a very useful purpose, but sadly, it is too flawed to serve as a real business tool. The major flaw which I can’t get past is that when I’m in the middle of a conference call, if my phone screen locks, which it does automatically due to corporate policies, the app disconnects me from the call. This is obviously not ideal when I am the one hosting the call. I have to reconnect quickly and then try to remember to keep my screen active since the phone won’t lock.Also, there needs to be a way for me to identify the people who call regularly to my conference line.

Instead, you can only see their phone numbers. It would be very simple for Cisco to allow us to save each participant with a nickname so that we can easily see who is connected and who is speaking.