- Port Utilization in System Services for Unified CCE for Release 12.5(1)
- Port Utilization in Contact Center Enterprise for Unified CCE for Release 12.5(1)
- Port Utilization in Unified CVP for Unified CCE for Release 12.5(1)
- Port Utilization in Cisco VVB for Unified CCE for Release 12.5(1)
- Port Utilization in Finesse for Unified CCE for Release 12.5(1)
- Port Utilization in Customer Collaboration Platform for Unified CCE for Release 12.5(1)
- Port Utilization in Unified Intelligence Center for Unified CCE for Release 12.5(1)
Port Utilization Table Columns
The columns in the port utilization tables in this document describe the following:
- Listener (Process or Application Protocol)
A value representing the server or application and where applicable, the open or proprietary application protocol.
- Listener Protocol and Port
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.
- Remote Device (Process or Application Protocol)
The remote application or device making a connection to the server or service specified by the protocol.
- Remote Port
The remote port is used to make an outgoing connection to the corresponding listener port.
- Traffic Direction
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. |
Cisco VVB Port Utilization
Table 1. Cisco VVB Port Utilization
Table 2. Cisco VVB Ephemeral Port Utilization
Listener (Process or Application Protocol) | Listener Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
|---|---|---|---|---|---|
VBONINIT | TCP 1504 | External process such as External DB clients (like Squirrel or others for custom reporting) can connect | - | Bidirectional | Cisco VVB database port |
VVB_ Engine | SIP over TCP, SIP over UDP 5060 | SIP | - | Bidirectional | Communicates with SIP gateway |
VVB_ Engine | SIP over TLS 5061 | SIP | - | Bidirectional | Communicates with SIP gateway |
VVB_CVD | TCP 6161 | Internal | 6161 | Bidirectional | Publishes JMS events across JMS network connectors in the cluster |
CVD | TCP 6295 | CVD of other node in cluster | - | Bidirectional | Bootstrap HTTPD service port |
VVB_CVD | TCP 6999 | Engine, Tomcat, CVD, and Editor | - | Bidirectional | RMI Port |
VVB_Engine | TCP 9080 | - | - | Bidirectional | - Clients trying to access HTTP triggers, documents, prompts, or grammars - Tomcat instance used by Cisco VVB engine |
Cisco IP Voice Media Streaming application | UDP 24576 ~ 32767 | - | - | Bidirectional | - Audio media streaming. - Kernel streaming device driver |
Ephemeral (Process or Application Protocol) | Ephemeral Protocol and Port | Remote Device (Process or Application Protocol) | Remote Port | Traffic Direction | Notes |
|---|---|---|---|---|---|
Generic Ports | TCP, UDP 32768 ~ 61000 | - | - | Bidirectional | Generic ephemeral TCP and UDP ports |
| Note | SIP signalling is possible over TCP or TLS. For RTP, underlying protocol is UDP always (not configurable). If TLS is used for SIP signalling, then the same exchanged keys will be used to encrypt and decrypt the RTP packets - for SRTP |
To view the system services for port utilization for Cisco Virtualized Voice Browser, see System Services Port Utilization
Feedback