Network Requirements for Cisco Jabber for Windows 11.5

Document created by Cisco Documentation Team on Dec 10, 2015Last modified by Shona O'Flaherty on Oct 27, 2016
Version 2Show Document
  • View in full screen mode

Ports and Protocols

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.

Note   
Cisco Jabber can also use this port for:
  • HTTPS traffic to Cisco Unity Connection and Cisco WebEx Meetings Server.

  • Saving chats to the Microsoft Exchange server.

30000 to 39999

UDP

The client uses this port for far end camera control.

33434-33598 and 8000-8100

UDP/TCP

Range of media ports used for RTP/SRTP for video calling. The port 33434 is used to enable video calling.

389

UDP/TCP

Lightweight Directory Access Protocol (LDAP) directory server.

636

LDAPS

LDAP directory server (secure).

2748

TCP

Computer Telephony Interface (CTI) used for desk phone control.

3268

TCP

Global Catalog server.

3269

LDAPS

Global Catalog server (secure).

5070 to 6070

UDP

Binary Floor Control Protocol (BFCP) for video desktop sharing capabilities.

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.

7080

TCP

( HTTPS )

Cisco Unity Connection for notifications of voice messages (new message, message update, and message deletion).

53

UDP/TCP

Domain Name System (DNS) traffic.

80

HTTP

Saving chats to Microsoft Exchange server.

Depending on your server configuration on Microsoft Exchange, use either port 80 or 443, but not both.

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.

49152 to 65535

TCP

IM-only screen share.

The client randomly selects a port from the range.

The actual range may vary. To find the real range, enter the netsh interface ipv4 show dynamicportrange tcp command.

You can use the SharePortRangeStart and SharePortRangeSize parameters to narrow the range used for IM screen share. For more information on these parameters, see the section on Common Policies parameters in the Deployment and Installation Guide.




Attachments

    Outcomes