Cisco Jabber - Requirements
Environment
Software, hardware, and network requirements for using Cisco Jabber for IM&P as well as a voice and video client
Resolution
Windows Software requirements for Cisco Jabber 11.0
| Server | Software |
|---|---|
| Operating systems |
|
Windows Hardware requirements for Cisco Jabber 11.0
| Hardware | Requirement |
|---|---|
| Installed RAM | 2 GB RAM on Microsoft Windows 7 and Windows 8 |
| Free Physical Memory | 128 MB |
| Free Disk Space | 256 MB |
| CPU Speed and Type |
|
| GPU | DirectX11 on Microsoft Windows 7 |
| I/O Ports | USB 2.0 for USB camera and audio devices. |
Mac Software requirements for Cisco Jabber 11.0
| Server | Software |
|---|---|
| Operating systems |
|
Mac Hardware requirements for Cisco Jabber 11.0
| Hardware | Requirement |
|---|---|
| Installed RAM | 2 GB RAM |
| Free Physical Memory | 1GB |
| Free Disk Space | 300 MB |
| CPU Speed and Type | Intel Core 2 Duo or later processors in any of the following Apple hardware:
|
| I/O Ports | USB 2.0 for USB camera and audio devices. |
Third Party Requirements
| Third-Party Software | Requirement |
|---|---|
| Microsoft Internet Explorer | Microsoft Internet Explorer 9 or later |
| Microsoft Office | Microsoft Exchange integrates directly with Cisco Unified Communications Manager. For more information, see the Configuration Guides for the appropriate version of Cisco Unified Communications Manager. |
| Microsoft SharePoint | |
| Microsoft 365 | Cisco Jabber for Windows supports client-side integration with Microsoft Office 365 with the following applications using an on-premises Active Directory (AD) deployment:
|
| Third-party calendars |
|
Network Requirements for Managed Network
Note: Client managed firewall must support DMZ to connect to voice VLAN
| Port | Protocol | Description | ||
|---|---|---|---|---|
| 443 | TCP (Extensible Messaging and Presence Protocol [XMPP] and HTTPS) |
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.
|
||
| 30000 to 39999 | FECC | The client uses this port for far end camera control. | ||
| 389 | UDP/TCP | Lightweight Directory Access Protocol (LDAP) directory server. | ||
| 636 | LDAPS | LDAP directory server (secure). | ||
| 3268 | TCP | Global Catalog server. | ||
| 3269 | LDAPS | Global Catalog server (secure). | ||
| 5222 | TCP (XMPP) |
XMPP traffic to Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence Service. | ||
| 8443 | TCP ( HTTPS ) |
Traffic to Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service. | ||
| 53 | UDP/TCP | Domain Name System (DNS) traffic. | ||
| 37200 | SOCKS5 Bytestreams | Peer-to-peer file transfers. In on-premises deployments, the client also uses this port to send screen captures. |
||
| 5060 | UDP/TCP | Session Initiation Protocol (SIP) call signaling. | ||
| 5061 | TCP | Secure SIP call signaling. | ||
Network Requirements for Cloud registration
Note: The following services are not currently supported via clound registration
CTI Deskphone control
LDAP directory search
Shared desktop from IM (shared desktop from active call, or via WebExis supported)
| Port | Protocol | Description |
|---|---|---|
| 443 | SSL | All traffic for Remote registration for Jabber, Voice, and video traffic and WebEx is encrypted via SSL |