The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The columns in the port utilization tables in this document describe the following:
A value representing the server or application and where applicable, the open or proprietary application protocol.
An identifier for the TCP or UDP port that the server or application is listening on, along with the IP address for incoming connection requests when acting as a server.
The remote application or device making a connection to the server or service specified by the protocol; or listening on the remote protocol and port.
The identifier for the TCP or UDP port that the remote service or application is listening on, along with the IP address for incoming connection requests when acting as the server.
The direction that traffic flows through the port: Inbound, Bidirectional, Outbound.
Note | The operating system dynamically assigns the source port that the local application or service uses to connect to the destination port of a remote device. In most cases, this port is assigned randomly above TCP/UDP 1024. |
Listener (Process or Application Protocol) |
Listener Protocol and Port |
Remote Device (Process or Application Protocol) |
Remote Protocol and Port |
Traffic Direction |
Note |
---|---|---|---|---|---|
HTTPS |
TCP 443, 8443 |
Web browser |
Any |
Used by Administration, serviceability |
|
HTTPS |
TCP 8440 |
Client application |
Any |
Used by API access |
|
HTTPS |
TCP 9443 |
Client application |
Any |
Used by media service to redirect authenticated requests. |
|
HTTPS |
TCP 8446 |
Web browser, API client |
Any |
Used by Call control service. |
|
HTTPS |
TCP 9081 |
Client application |
Any |
Used by media service to redirect authenticated requests. |
|
HTTP |
TCP 80, 8080 |
Web browser |
Any |
Used by Administration, serviceability |
|
HTTP |
TCP 8081 |
Web browser, API client |
Any |
Used by Call control service |
|
HTTP |
TCP 8085 |
Another CMS node |
Any |
Used by Call control service |
|
HTTP |
TCP 8087 |
CMS cluster nodes only |
Any |
Used by System service |
|
HTTP |
TCP 8088 |
CMS cluster nodes only |
Any |
Used by Configuration service |
|
RTSP |
TCP 554, 8554 |
RTSP media player |
Any |
Used by SM agent |
|
RTSP |
TCP 9554 |
Client application or media player |
Any |
Used by media service to redirect authenticated requests. |
|
SIP |
TCP 5060 UDP 5060 |
Unified Communications Manager or Unified Border Element |
TCP 5060 UDP 5060 |
Call control service. |
|
TCP/IP |
TCP 1543 |
CMS cluster nodes only |
Any |
Used by Informix ER to make connections between primary server and secondary servers. Used by API service or configuration service to make JDBC connections with Informix. |
|
Keep-alive heartbeats |
UDP 8091 |
CMS cluster nodes only |
UDP 8091 |
Used by a call control service to detect availability of other call control services. |
|
JMS |
TCP 61610 |
CMS cluster nodes only |
Any |
Used by API service |
|
JMS |
TCP 61612 |
CMS cluster nodes only |
Any |
Used by Call control service |
|
JMS |
TCP 61616 |
CMS cluster nodes only |
Any |
Used by SM agent |
|
Ephemeral port range |
UDP 32768 - 61000 |
Phone or gateway that sends RTP media streams. |
Any |
Range of ports used by media service to receive RTP media streams. |