These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Mac Release 11.5. 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. Calling Features. Hunt Group—Hunt Groups enable incoming calls to be directed to a group of users. The call route is based on several factors, including first available, longest Idle, broadcast hunting and circular hunting.

You can use Cisco Jabber and deskphones to answer hunt group calls. A hunt group works with route filters and hunt lists to direct calls to specific devices. If a phone or device is ringing and not being answered, then another available number is searched for until the call is answered. A hunt list contains a set of line groups in a specific order. A single line group can appear in multiple hunt lists.

A line group comprises a group of directory numbers in a specific order. The order controls the progress of the search for available directory numbers for incoming calls. Configured using the EnableHuntGroup and the PreventDeclineOnHuntCall parameter.

For more information about these parameters, see the Parameters Reference Guide for Cisco Jabber 11.5. Call Pickup—Call Pickup allows users to pick up incoming calls from their own group. Group Call Pickup and Directed Call Pickup allow users to pick up incoming calls to another group or individual, respectively. You can use Cisco Jabber and deskphones to answer call pickup calls. Directory numbers are assigned to call pickup groups and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number.

Users select Pickup to answer the call. There are four kinds of call pickup that allow users to ensure that incoming phone calls are not missed. Call pickup: Allows users to pick up incoming calls from their own group.

Configured using the EnableCallPickup parameter. Group call pickup: Allows users to pick up incoming calls from another group. Configured using EnableGroupCallPickup parameter. Other group pickup: Allows users to pick up incoming calls from a group that is associated with their group.

You cannot use this option with the hunt group feature. Configured using the EnableOtherGroupPickup parameter. Directed call pickup: Allows users to pick up an incoming call on a directory number.

You cannot use this option with the hunt group feature. For more information about the parameters, see the Parameters Reference Guide for Cisco Jabber 11.5.

Personal Ringtone—Users can select a ringtone for incoming calls from a menu of distinctive ringtones for their client in the Preferences window. Call with Edit—A Call with Edit menu option is available from the main window by right-clicking over a contact's name. When users select a number from this menu option, the call number is copied into the Search or Call field. Users can edit the number before making the call.

No configuration is required to enable this feature. Extend and Connect—Users can use the client to do the following:. Make and receive calls on a non-Cisco IP Phone in the office. Control a non-Cisco IP Phone in the office, such as hold or resume. Control a home or hotel phone when connecting with Expressway for Mobile and Remote Access. Multiple Device Messaging (Cloud)—Users who are signed into multiple devices can now see all sent and received IMs on each device regardless of which device is active. Notifications are synchronized; if an IM is read on one device, it shows as read on other signed-in devices.

This feature is enabled by default, but can be disabled with the DisableMultiDeviceMessage parameter. The following limitations apply:. Clients must be signed-in. Signed-out clients do not display sent or received IMs or notifications. File transfer between multiple devices is not supported—Files are available only on the active devices that sent or received the file. Group chat is not supported.

Multiple device messaging cannot be enabled if AES encryption is required. Applies to cloud deployments only. For more information about the DisableMultiDeviceMessage parameter, see the Parameters Reference Guide for Cisco Jabber 11.5. Broadcast Messages with Rich Text and Emoticons—Broadcast messages allow users to send a single message to multiple contacts.

Users can select multiple contacts or a group of contacts from their contact list and send a broadcast message to all of them at once. Recipients receive broadcast messages in the same way as normal 1:1 chats. In cloud and hybrid deployments, offline contacts do not receive broadcast messages. No configuration is required to enable this feature. Alert when Available—Users can set the client to notify them when a contact becomes available.

Right-click over the user's name to select the Alert When Available option. A message notification is displayed the first time the user becomes available. No configuration is required to enable this feature.

Locations—Create, define, and display locations in the client for your contacts to see. Configure the Locations feature using the LocationEnabled, LocationMode, and LOCATIONMATCHINGMODE parameters. For more information about these parameters, see the Parameters Reference Guide for Cisco Jabber 11.5. Users can define their settings in the Preferences window. Persistent Chat Rooms Persistent Chat Rooms are applicable to on-premises deployments only. Administration and Management—Administrators can now create and delete rooms, manage membership, and moderate rooms.

Define room moderators who can create or remove rooms, add or remove members, and define room types and descriptions. Room discovery and Enrolment—View joined rooms, browse through a list of available rooms, join open rooms, and request membership of members-only rooms. Logout Inactivity Timer—This timer allows you to automatically log users out of the client after a specified amount of time of inactivity. The client will use the following order for configuration settings:. Settings in Cisco WebEx Messenger Administration Tool. Settings in jabber-config.xml file from Cisco WebEx Messenger Administration Tool.

Note Group configuration file settings take priority over the configuration file in Cisco WebEx Messenger Administration Tool. Settings in jabber-config.xml file from the TFTP server. This feature applies to cloud deployments only. Custom Embedded Tabs—Custom tabs can be created in the client. The feature is configured using the AllowUserCustomTabs parameter.

For more information on creating custom tabs, see the Custom Embedded Tabs section of the Features and Options Guide. Port Application Layer Protocol Transport Layer Protocol Description Configuration 6970 HTTP TCP Connect to the TFTP server to download client configuration files.

6972 HTTPS TCP Connects to the TFTP server to download client configuration files securely for Cisco Unified Communications Manager release 11.0 and later. 53 DNS UDP Hostname resolution. 3804 CAPF TCP Issues Locally Significant Certificates (LSC) to IP phones. This port is the listening port for Cisco Unified Communications Manager Certificate Authority Proxy Function (CAPF) enrollment. 8443 HTTPS Traffic to Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service. 8191 SOAP TCP Connects to local port to provide Simple Object Access Protocol (SOAP) web services.

Directory Integration—For LDAP contact resolution one of the following ports are used based on LDAP configuration. 389 LDAP TCP LDAP TCP (UDP) Connects to an LDAP directory service. 3268 LDAP TCP Connects to a Global Catalog server for contact searches.

636 LDAPS TCP LDAPS TCP Connects securely to an LDAP directory service. 3269 LDAPS TCP LDAPS TCP Connects securely to the Global Catalog server. Instant Messaging and Presence 443 XMPP TCP XMPP traffic to the WebEx Messenger service. The client sends XMPP through this port in cloud-based deployments only. If port 443 is blocked, the client falls back to port 5222.

5222 XMPP TCP Connects to Cisco Unified Communications Manager IM and Presence Service for instant messaging and presence. 37200 SOCKS5 Bytestream TCP Peer to Peer file transfer, In on-premises deployments, the client also uses this port to send screen captures. 7336 HTTPS TCP MFT File transfer (On-Premises only).

Hardware Requirements For Cisco Jabber For Mac 11.9 Download

Communication Manager Signaling 2748 CTI TCP Computer Telephony Interface (CTI) used for desk phone control. 5060 SIP TCP Provides Session Initiation Protocol (SIP) call signaling.

5061 SIP over TLS TCP SIP over TCP Provides secure SIP call signaling. (Used if Secure SIP is enabled for device.) 30000 to 39999 FECC TCP Far end camera control (FECC). 5070 to 6070 BFCP UDP Binary Floor Control Protocol (BFCP) for video screen sharing capabilities. Voice or Video Media Exchange 16384 to 32766 RTP UDP Sends RTP media streams for audio or video.

49152 to 65535 RDP TCP IM-only screen share. Applies to Cisco Jabber for Windows only. Unity Connection 7080 HTTP TCP Used for Cisco Unity Connection to receive notifications of voice messages (new message, message update, and message deleted).

7443 HTTPS TCP Used for Cisco Unity Connection to securely receive notifications of voice messages (new message, message update, and message deleted). 443 HTTPS TCP Connects to Cisco Unity Connection for voicemail. Cisco WebEx Meetings 80 HTTP TCP Connects to Cisco WebEx Meeting Center for meetings. 443 HTTPS TCP Connects to Cisco WebEx Meeting Center for meetings.

8443 HTTPS TCP Web access to Cisco Unified Communications Manager and includes connections for the following:. Cisco Unified Communications Manager IP Phone (CCMCIP) server for assigned devices. User Data Service (UDS) for contact resolution. Ports for Other Services and Protocols In addition to the ports listed in this section, review the required ports for all protocols and services in your deployment. You can find the port and protocol requirements for different servers in the following documents:. For Cisco Unified Communications Manager, Cisco Unified Communications Manager IM and Presence Service, see the TCP and UDP Port Usage Guide. For Cisco Unity Connection, see the System Administration Guide.

For Cisco WebEx Meetings Server, see the Administration Guide. For Cisco WebEx services, see the Administrator's Guide. For Expressway for Mobile and Remote Access, refer to Cisco Expressway IP Port Usage for Firewall Traversal. For file transfer port usage, see the Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager. Severity Level Description 1 Catastrophic Reasonably 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 Severe Important functions are unusable and workarounds do not exist. Other functions and the rest of the network is operating normally. 3 Moderate Failures 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 Minor Failures 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 Cosmetic Defects do not cause any detrimental effect on system functionality.

6 Enhancement Requests for new functionality or feature improvements. Identifier Severity Headline 1 Jabber can't start after certain crash type 2 Evaluation of jabber-mac for OpenSSL December 2015 vulnerabilities 2 Jabber client does not allow to enforce STARTTLS as required 2 libxml2 December 2015 parsing vulnerabilities 3 J4M both local and remote ringback heard if SIP 180 is followed by 183. 4 Call window pops when is deskphone mode and show window set to never 4 SSO HTTP Basic Login Dialog Doesn't Allow Copy/Paste 3 CPVE crashed trying to release an object 3 Offline user cannot receive invitation email. Identifier Severity Headline 1 Jabber can't start after certain crash type 2 Evaluation of jabber-mac for OpenSSL December 2015 vulnerabilities 2 Jabber client does not allow to enforce STARTTLS as required 2 libxml2 December 2015 parsing vulnerabilities 3 J4M both local and remote ringback heard if SIP 180 is followed by 183. 4 Call window pops when is deskphone mode and show window set to never 4 SSO HTTP Basic Login Dialog Doesn't Allow Copy/Paste 3 CPVE crashed trying to release an object 3 Offline user cannot receive invitation email.

October 18, 2014 Posted in: Hits: 395 Mac Requirements Resource Requirement Notes Operating System Mac OS X 10.9 Mac OS X 10.8 Mac OS X 10.7 Processor 2 GHz Intel Core 2 Duo or equivalent. Memory 2 GB RAM or more. Microphone All microphones work well with Jabber Video Some cameras have built-in microphones Camera Jabber Video works with most common web cameras PC Requirements Resource Requirement Notes Operating System Windows 7 Windows 8.x On Windows 8.x, only the classic Desktop user interface is supported. Processor 2 GHz Intel Core 2 Duo or equivalent. On computers with limited processing power and/or memory, Jabber Video will use a lot of system resources, and reduced performance can be expected.

Memory Windows 8.x or Windows 7 32-bit: 1 GB RAM or more.Windows 8.x or Windows 7 64-bit: 2 GB RAM or more Graphics card OpenGL version 1.3, or OpenGL version 1.2 with the multitexturing extension. Sound Card Any standard sound card (full-duplex, 16-bit or better) Microphone All microphones work well with Jabber Video Some cameras have built-in microphones Camera Jabber Video works with most common web cameras.