Requirements

Hardware Requirements for Cisco Jabber for Mac

Installed RAM

  • 2 GB RAM

Free Physical Memory

  • 1 GB

Free Disk Space

  • 300 MB

CPU Speed and Type

  • Intel Core 2 Duo or later processors in any of the following Apple hardware:

  • Mac Pro

  • MacBook Pro (including Retina Display model)

  • MacBook

  • MacBook Air

  • iMac

  • Mac Mini

I/O Ports

  • USB 2.0 for USB camera and audio devices.

Software Requirements

For successful deployment, ensure that client workstations meet the software requirements.

Operating Systems for Cisco Jabber for Mac

You can install Cisco Jabber for Mac on the following operating systems:

  • Apple OS X Yosemite 10.10 (or later)

  • Apple OS X Mavericks 10.9 (or later)

  • Apple OS X Mountain Lion 10.8.1 (or later)

On-Premises Servers for Cisco Jabber for Windows and Cisco Jabber for Mac

Cisco Jabber uses domain name system (DNS) servers during startup. DNS servers are mandatory for Cisco Jabber.

Cisco Jabber supports the following on-premises servers:

  • Cisco Unified Communications Manager, release 8.6(2) or later

  • Cisco Unified Presence, release 8.6(2) or later

  • Cisco Unity Connection, release 8.6(2) or later

  • Cisco WebEx Meetings Server, version 1.5 or later (Windows only)

  • Cisco WebEx Meetings Server, version 2.0 or later (Mac only)

  • Cisco Expressway Series for Cisco Unified Communications Manager

    • Cisco Expressway-E, version 8.1.1 or later

    • Cisco Expressway-C, version 8.1.1 or later

  • Cisco TelePresence Video Communications Server

    • Cisco VCS Expressway, version 8.1.1 or later

    • Cisco VCS Control, version 8.1.1 or later

Cisco Jabber supports the following features with Cisco Unified Survivable Remote Site Telephony, Version 8.5:

  • Basic call functionality

  • Ability to hold and resume calls

Refer to the Cisco Unified SCCP and SIP SRST System Administrator Guide for information about configuring Cisco Unified Survivable Remote Site Telephony at: http:/​/​www.cisco.com/​en/​US/​docs/​voice_ip_comm/​cusrst/​admin/​sccp_sip_srst/​configuration/​guide/​SCCP_​and_​SIP_​SRST_​Admin_​Guide.html.

For Cisco Unified Communications Manager Express support details, refer to the Cisco Unified CME documentation: http:/​/​www.cisco.com/​en/​US/​products/​sw/​voicesw/​ps4625/​products_​device_​support_​tables_​list.html

Cloud-Based Servers

Cisco Jabber supports integration with the following hosted servers:

  • Cisco WebEx Messenger service

  • Cisco WebEx Meeting Center, minimum supported versions WBS27 or later

Directory Servers

You can use the following directory servers with Cisco Jabber:

Note

Cisco Jabber for Windows, Cisco Jabber for Mac, Cisco Jabber for iPhone and iPad, and Cisco Jabber for Android support the LDAPv3 standard for directory integration. Any directory server that supports this standard should be compatible with these clients.

  • Active Directory Domain Services for Windows Server 2012 R2

  • Active Directory Domain Services for Windows Server 2008 R2

  • Cisco Unified Communications Manager User Data Server (UDS)

    Cisco Jabber supports UDS with Cisco Unified Communications Manager, version 9.1(2) with the Cisco Options Package (COP) file: cmterm-cucm-uds-912-3.cop.sgn.

  • OpenLDAP

Restriction:

Directory integration with OpenLDAP requires that you define specific parameters in a Cisco Jabber configuration file.

Computer Telephony Integration Servitude

Cisco Jabber for Windows and Cisco Jabber for Mac support CTI servitude of Cisco Jabber from a third party application.

Computer Telephony Integration (CTI) enables you to use computer-processing functions while making, receiving, and managing telephone calls. A CTI application can allow you to retrieve customer information from a database on the basis of information that caller ID provides and can enable you to use information that an interactive voice response (IVR) system captures.

For more information on CTI servitude, see the CTI sections in the appropriate release of the Cisco Unified Communications Manager System Guide. Or you can see the following sites on the Cisco Developer Network for information about creating applications for CTI control through Cisco Unified Communications Manager APIs:

Ports and Protocols

The client uses the ports and protocols listed in the following tables:

Inbound

Port Protocol Description
16384 to 32766 UDP Real-Time Transport Protocol (RTP) media streams for audio and video

Outbound

Port Protocol Description
69 UDP Trivial File Transfer Protocol (TFTP) service
6970 HTTP TFTP service to download client configuration
80 TCP

(HTTP)

Cisco Unified Communications Manager administrator and user web pages

389 UDP / TCP LDAP directory server
636 LDAPS LDAP directory server (secure)
3268 TCP Global Catalog server
3269 LDAPS Global Catalog server (secure)
2748 TCP CTI gateway
5060 UDP / TCP Session Initiation Protocol (SIP) call signaling
5061 TCP Secure SIP call signaling
5070 UDP Binary Floor Control Protocol (BFCP) for video desktop sharing
5222 TCP

(XMPP)

Cisco Unified Presence or Cisco Unified Communications IM and Presence in on-premise deployments

8443 HTTPS 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)

16384 to 32766 UDP RTP media streams for audio and video
53 UDP / TCP Domain Name System (DNS) traffic
1080 SOCKS5 Bytestreams Peer to peer file transfers

If port 1080 is in use, the client attempts to use the next available port in the range from 1081 to 1089.

In on-premise deployments, the client also uses port 1080 to send screen captures.

Note   

If port 1080 is blocked, the client uses the following port range: 37200 to 37209.

CTI Supported Devices

To view the list of Computer Telephony Integration (CTI) supported devices: From Cisco Unified Reporting, select Unified CM Phone Feature List. From the Feature drop-down list, select CTI controlled.

Supported Codecs for Cisco Jabber for Windows and Cisco Jabber for Mac

Supported Audio Codecs

  • G.722

  • G.722.1—32k and 24k. G.722.1 is supported on Cisco Unified Communications Manager 8.6.1 or later.

  • G.711—a-law and u-law

  • G.729a

Supported Video Codec

  • H.264/AVC

COP Files for Cisco Jabber for Windows and Cisco Jabber for Mac

In certain cases, you might need to apply COP files to Cisco Unified Communications Manager.

You can download the following COP files from the Cisco Jabber administration package on Cisco.com:
COP File Description Cisco Unified Communications Manager Versions
ciscocm.installcsfdevicetype.cop.sgn Adds the CSF device type to Cisco Unified Communications Manager.

For more information, see Software Requirements.

7.1.3
cmterm-bfcp-e.8-6-2.cop.sgn Enables CSF devices to support BFCP video desktop sharing.

For more information, see Apply COP File for BFCP Capabilities.

8.6.2 only
ciscocm.addcsfsupportfield.cop.sgn Adds the CSF Support Field field for group configuration files.

For more information, see Create Group Configurations.

8.6.1 and earlier
cmterm-cupc-dialrule-wizard-0.1.cop.sgn Publishes application dial rules and directory lookup rules to Cisco Jabber.

For more information, see Publish Dial Rules.

8.6.1 and earlier

VPN Support

Cisco Jabber for Mac supports the following software VPN clients.

  • Cisco AnyConnect release 3.0.5, and 3.1

  • Cisco AnyConnect releases 2.2, 2.3, and 2.4

  • Cisco VPN client release 5.0

  • Cisco VPN client release 4.9.01