Required Ports for Prime Collaboration

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (→Ports Used by Prime Collaboration Assurance Server, Devices, and Applications)
m (→Ports Used by Prime Collaboration Assurance Server, Devices, and Applications)
(23 intermediate revisions not shown)
Line 4: Line 4:
The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.<br>  
The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.<br>  
 +
 +
Note1: SNMP v3 AuthPriv is not supported. <br>
 +
Note2: ICMP ping is required for all devices for checking reachability. <br>
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable"
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable"
Line 13: Line 16:
| '''Purpose'''<br>
| '''Purpose'''<br>
|-
|-
-
| Cisco 1040 Sensor
+
| rowspan="3" | Cisco TMS
| PCA<br>  
| PCA<br>  
-
| 1040 Sensor<br>  
+
| TMS<br>  
-
| 2000<br>  
+
| 80:TCP<br>  
-
| To communicate with Cisco 1040 server using SCCP.<br>
+
| To import sessions and health status (HTTP).<br>
 +
|-
 +
| PCA<br>
 +
| TMS<br>
 +
| 161:UDP<br>
 +
| To poll health status (SNMP).<br>
 +
|-
 +
| PCA<br>
 +
| TMS<br>
 +
| 443:TCP<br>
 +
| To import sessions and health status (HTTPS).<br>
|-
|-
| rowspan="3" | CTS-Manager (CTSMAN)
| rowspan="3" | CTS-Manager (CTSMAN)
Line 51: Line 64:
| To poll call details and health status (HTTPS)<br>
| To poll call details and health status (HTTPS)<br>
|-
|-
-
| rowspan="3" | Cisco TelePresence Multipoint Switch (CTMS)
+
| rowspan="3" | Cisco TP Multipoint Switch (CTMS)
| PCA<br>  
| PCA<br>  
| CTMS<br>  
| CTMS<br>  
Line 67: Line 80:
| To poll health status (HTTPS).<br>
| To poll health status (HTTPS).<br>
|-
|-
-
| rowspan="3" | Cisco TelePresence Server (TPS)  
+
| rowspan="3" | Cisco TP Server (TPS)  
-
| PCA  
+
| PCA <br>
| TPS <br>  
| TPS <br>  
| 80:TCP<br>  
| 80:TCP<br>  
Line 78: Line 91:
| To poll health status (SNMP).<br>
| To poll health status (SNMP).<br>
|-
|-
-
| PCA  
+
| PCA <br>
| TPS <br>  
| TPS <br>  
| 443:TCP<br>  
| 443:TCP<br>  
| To poll health status (HTTPS). <br>
| To poll health status (HTTPS). <br>
-
|-
 
-
| rowspan="3" | Cisco TMS
 
-
| PCA<br>
 
-
| TMS<br>
 
-
| 80:TCP<br>
 
-
| To import sessions and health status (HTTP).<br>
 
-
|-
 
-
| PCA<br>
 
-
| TMS<br>
 
-
| 161:UDP<br>
 
-
| To poll health status (SNMP).<br>
 
-
|-
 
-
| PCA<br>
 
-
| TMS<br>
 
-
| 443:TCP<br>
 
-
| To import sessions and health status (HTTPS).<br>
 
|-
|-
| rowspan="3" | Cisco VCS  
| rowspan="3" | Cisco VCS  
Line 114: Line 111:
| 443:TCP<br>  
| 443:TCP<br>  
| To poll call details and health status (HTTPS).<br>
| To poll call details and health status (HTTPS).<br>
-
|-
 
-
| rowspan="2" | IP Phones<br>
 
-
| PCA<br>
 
-
| IP Phones<br>
 
-
| 80:TCP<br>
 
-
| To obtain XML-based data (serial numbers and load ID) from phones during discovery (HTTP).<br>
 
-
|-
 
-
| PCA<br>
 
-
| IP Phones<br>
 
-
| 443:TCP<br>
 
-
| To obtain XML-based data (serial numbers and load ID) from phones during discovery (HTTPS).<br>
 
-
|-
 
-
| rowspan="2" | Network Devices
 
-
| PCA<br>
 
-
| Network Devices<br>
 
-
| 23:TCP<br>
 
-
| To initiate the Telnet connection to medianet-enabled devices during the troubleshooting process (Telnet).<br>
 
-
|-
 
-
| PCA<br>
 
-
| Network Devices<br>
 
-
| 80:TCP<br>
 
-
| To initiate HTTP connection to the medianet-enabled devices during the troubleshooting process (HTTP). <br>
 
|-
|-
| rowspan="9" | Cisco Unified CM (CUCM)
| rowspan="9" | Cisco Unified CM (CUCM)
Line 141: Line 116:
| CUCM <br>  
| CUCM <br>  
| 22:TCP<br>  
| 22:TCP<br>  
-
| To obtain data from Unified CM using SFTP service (SFTP).<br>
+
| To obtain data from CUCM using SFTP service (SFTP).<br>
|-
|-
| PCA<br>  
| PCA<br>  
| CUCM <br>  
| CUCM <br>  
| 80:TCP<br>  
| 80:TCP<br>  
-
| To obtain call details from Unified CM (HTTP).<br>
+
| To obtain call details from CUCM (HTTP).<br>
|-
|-
| PCA<br>  
| PCA<br>  
Line 156: Line 131:
| CUCM <br>  
| CUCM <br>  
| 443:TCP<br>  
| 443:TCP<br>  
-
| To polls status over HTTPS; RTMT information.<br>
+
| To polls status and RTMT information (HTTPS).<br>
|-
|-
| PCA<br>  
| PCA<br>  
Line 166: Line 141:
| CUCM <br>  
| CUCM <br>  
| 2749:TCP<br>  
| 2749:TCP<br>  
-
| TLS connection between CTI applications (JTAPI/TSP) and CTI manager.<br>
+
| TLS connection between CTI application (JTAPI/TSP) and CTI manager.<br>
|-
|-
| PCA<br>  
| PCA<br>  
Line 176: Line 151:
| CUCM <br>  
| CUCM <br>  
| 8080:TCP<br>  
| 8080:TCP<br>  
-
| To determine whether the Cisco Prime Unified Communications Manager web service is running (HTTP). <br>
+
| To determine whether the CUCM web service is running (HTTP). <br>
|-
|-
| PCA<br>  
| PCA<br>  
| CUCM <br>  
| CUCM <br>  
| 8443:TCP<br>  
| 8443:TCP<br>  
-
| To polls status over HTTPS.<br>
+
| To polls CUCM status (HTTPS).<br>
|-
|-
-
| rowspan="4" | TP/Video Endpoints  
+
| rowspan="3" | Cisco Unity Connection (CUC)
 +
| PCA<br>
 +
| CUC<br>
 +
| 80.TCP<br>
 +
| To poll health status (HTTP). <br>
 +
|-
 +
| PCA<br>
 +
| CUC<br>
 +
| 161:UDP<br>
 +
| To poll health status (SNMP). <br>
 +
|-
 +
| PCA<br>
 +
| CUC<br>
 +
| 443:TCP<br>
 +
| To poll health status (HTTPS).<br>
 +
|-
 +
| rowspan="3" | Cisco Unified Presence Server (CUPS)
 +
| PCA<br>
 +
| CUPS<br>
 +
| 80.TCP<br>
 +
| To poll health status (HTTP). <br>
 +
|-
 +
| PCA<br>
 +
| CUPS<br>
 +
| 161:UDP<br>
 +
| To poll health status (SNMP). <br>
 +
|-
 +
| PCA<br>
 +
| CUPS<br>
 +
| 443:TCP<br>
 +
| To poll health status (HTTPS).<br>
 +
|-
 +
| rowspan="4" | TelePresence/Video Endpoints  
| PCA<br>  
| PCA<br>  
| TP Endpoints<br>  
| TP Endpoints<br>  
| 22:TCP<br>  
| 22:TCP<br>  
-
| To initiate SSH connection to endpoints during the troubleshooting process.
+
| To access endpoints during troubleshooting (SSH). <br>
|-
|-
| PCA<br>  
| PCA<br>  
| TP Endpoints<br>  
| TP Endpoints<br>  
| 80:TCP<br>  
| 80:TCP<br>  
-
| To poll device status, health information, and quality stats (HTTP). <br>
+
| To poll device info and status and call quality stats (HTTP). <br>
|-
|-
| PCA<br>  
| PCA<br>  
| TP Endpoints<br>  
| TP Endpoints<br>  
| 161:UDP<br>  
| 161:UDP<br>  
-
| To poll device status, health information, and quality stats (SNMP). <br>
+
| To poll device info and status and call quality stats (SNMP). <br>
|-
|-
| PCA<br>  
| PCA<br>  
| TP Endpoints<br>  
| TP Endpoints<br>  
| 443:TCP<br>  
| 443:TCP<br>  
-
| To poll device status, health information, and quality stats (HTTPS). <br>
+
| To poll device info and status and call quality stats (HTTPS). <br>
 +
|-
 +
| rowspan="3" | IP Phones
 +
| PCA<br>
 +
| IP Phones<br>
 +
| 80:TCP<br>
 +
| To obtain Serial Number and Load ID during discovery (HTTP).<br>
 +
|-
 +
| PCA<br>
 +
| IP Phones<br>
 +
| 443:TCP<br>
 +
| To obtain Serial Number and Load ID during discovery (HTTPS).<br>
 +
|-
 +
| PCA<br>
 +
| IP Phones<br>
 +
| 16384-32767:UDP<br>
 +
| To perform phone diagnostics testing.<br>
 +
|-
 +
| Cisco 1040 Sensor
 +
| PCA<br>
 +
| 1040 Sensor<br>
 +
| 2000:TCP<br>
 +
| To communicate with Cisco 1040 server using SCCP.<br>
 +
|-
 +
| rowspan="5" | Network Devices
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 22:TCP<br>
 +
| To access Mediatrace initiator during troubleshooting (SSH).<br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 23:TCP<br>
 +
| To access Mediatrace initiator during troubleshooting (Telnet).<br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 80:TCP<br>
 +
| To access Mediatrace initiator during troubleshooting (HTTP). <br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 161:UDP<br>
 +
| To poll device and Medianet information (SNMP). <br>
 +
|-
 +
| PCA<br>
 +
| Network Devices<br>
 +
| 443:TCP<br>
 +
| To access Medianet initiator during troubleshooting (HTTPS).<br>
|-
|-
-
| rowspan="3" | DHCP/DNS/SMTP Servers  
+
| rowspan="4" | DHCP/DNS/NTP/SMTP Servers  
| PCA<br>  
| PCA<br>  
| DHCP Server<br>  
| DHCP Server<br>  
| 67,68:TCP<br>  
| 67,68:TCP<br>  
-
| DHCP Service.<br>
+
| DHCP service.<br>
|-
|-
| PCA<br>  
| PCA<br>  
| DNS Server<br>  
| DNS Server<br>  
| 53:TCP<br>  
| 53:TCP<br>  
-
| DNS Service.<br>
+
| DNS service.<br>
 +
|-
 +
| PCA<br>
 +
| NTP Server<br>
 +
| 123:UDP<br>
 +
| NTP service.<br>
|-
|-
| PCA<br>  
| PCA<br>  
| SMTP Server<br>  
| SMTP Server<br>  
| 25:TCP<br>  
| 25:TCP<br>  
-
| SMTP Service.<br>
+
| SMTP service.<br>
|-
|-
| rowspan="6" | Assurance Server (PCA)  
| rowspan="6" | Assurance Server (PCA)  
| Cisco 1040<br>  
| Cisco 1040<br>  
| PCA<br>  
| PCA<br>  
-
| 5666<br>  
+
| 5666:UDP<br>  
| To receive syslog messages from Cisco 1040 sensors.<br>
| To receive syslog messages from Cisco 1040 sensors.<br>
|-
|-
Line 229: Line 289:
| PCA<br>  
| PCA<br>  
| 8886:TCP<br>  
| 8886:TCP<br>  
-
| To receive feedback/notification from Cisco VCS over HTTPS. <br>
+
| To receive feedback/notification from Cisco VCS (HTTPS). <br>
|-
|-
| Cisco VCS<br>  
| Cisco VCS<br>  
| PCA<br>  
| PCA<br>  
| 8889:TCP<br>  
| 8889:TCP<br>  
-
| To receive feedback/notification from Cisco VCS over HTTP. <br>
+
| To receive feedback/notification from Cisco VCS (HTTP). <br>
|-
|-
| Network Devices<br>  
| Network Devices<br>  
Line 256: Line 316:
= Internal Ports used by Prime Collaboration Assurance Server<br>  =
= Internal Ports used by Prime Collaboration Assurance Server<br>  =
-
The following ports are used by the Prime Collaboration Assurance server to communicate either with the client machine or for the internal use.<br>  
+
The following ports are used by the Prime Collaboration Assurance (PCA) server to communicate either with the client machine or for the internal use.<br>  
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable sortable"
{| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable sortable"
Line 265: Line 325:
| '''Purpose'''<br>
| '''Purpose'''<br>
|-
|-
-
| Assurance server<br>  
+
| PCA <br>  
| -<br>  
| -<br>  
| 1018:TCP<br>  
| 1018:TCP<br>  
| Poller RMI port.<br>
| Poller RMI port.<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 1019:TCP<br>  
| 1019:TCP<br>  
| Fault RMI port.<br>
| Fault RMI port.<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 1024-4999<br>  
| 1024-4999<br>  
| Ephemeral ports.<br>
| Ephemeral ports.<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
-
| 5665-5680<br>  
+
| 5665-5684<br>  
-
| Inter processes communication between user interface and backend processes. These ports must be free. <br>
+
| Inter processes communication between user interface and backend processes. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 9002<br>  
| 9002<br>  
| DynamID authentication<br>
| DynamID authentication<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 9009<br>  
| 9009<br>  
| Default port number used by the IP telephony server for receiving traps from the device fault server. <br>
| Default port number used by the IP telephony server for receiving traps from the device fault server. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 9822:TCP<br>  
| 9822:TCP<br>  
-
| Used for internal communication within the Prime Collaboration Assurance server<br>
+
| Used for internal communication within the PCA server<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 40000-41000<br>  
| 40000-41000<br>  
| Used by Common Transport Mechanism for internal application messaging. <br>
| Used by Common Transport Mechanism for internal application messaging. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 42344<br>  
| 42344<br>  
| Used by Synthetic Testing web service.<br>
| Used by Synthetic Testing web service.<br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 42350-42353<br>  
| 42350-42353<br>  
| Used by messaging software. <br>
| Used by messaging software. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 43445<br>  
| 43445<br>  
| Used by Alert History database engine. <br>
| Used by Alert History database engine. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 43446<br>  
| 43446<br>  
| Used by inventory service database engine. <br>
| Used by inventory service database engine. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 43447<br>  
| 43447<br>  
| Used by event processing database engine. <br>
| Used by event processing database engine. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 43449<br>  
| 43449<br>  
| Used by IP Phone Information Facility database engine. <br>
| Used by IP Phone Information Facility database engine. <br>
|-
|-
-
| Assurance server<br>  
+
| PCA<br>  
| -<br>  
| -<br>  
| 43459<br>  
| 43459<br>  
| QOVRdatabase.<br>
| QOVRdatabase.<br>
|-
|-
-
| Client browser<br>  
+
| Client <br>  
-
| Assurance server<br>  
+
| PCA<br>  
-
| 22:TCP<br>  
+
| 26:TCP<br>  
-
| To connect to the Prime Collaboration server from the client machine. <br>
+
| To connect to the PCA server from the client machine over SSH. <br>
|-
|-
| Client browser<br>  
| Client browser<br>  
-
| Assurance server<br>  
+
| PCA<br>  
| 80:TCP<br>  
| 80:TCP<br>  
-
| To connect to the Prime Collaboration server from the client machine over HTTP. <br>
+
| To connect to the PCA server from the client machine over HTTP. <br>
|-
|-
| Client browser<br>  
| Client browser<br>  
-
| Assurance server<br>  
+
| PCA<br>  
| 443:UDP<br>  
| 443:UDP<br>  
-
| To connect to the Prime Collaboration server from the client machine over HTTPS. <br>
+
| To connect to the PCA server from the client machine over HTTPS. <br>
|}
|}
-
<br>  
+
<br>
= Ports Used by Prime Collaboration Provisioning Server, Devices, and Applications<br>  =
= Ports Used by Prime Collaboration Provisioning Server, Devices, and Applications<br>  =

Revision as of 03:17, 26 March 2013

The following tables lists the required ports for the Cisco Prime Collaboration Assurance and Cisco Prime Collaboration Provisioning servers to communicate with the devices.

Contents

Ports Used by Prime Collaboration Assurance Server, Devices, and Applications

The following tables lists the required ports for the Cisco Prime Collaboration Assurance (PCA) to communicate with the devices and applications.

Note1: SNMP v3 AuthPriv is not supported.
Note2: ICMP ping is required for all devices for checking reachability.

Devices/Applications
 From (Sender)
 To (Listener)
Destination Port
Purpose
Cisco TMS PCA
 TMS
 80:TCP
 To import sessions and health status (HTTP).
PCA
 TMS
 161:UDP
 To poll health status (SNMP).
PCA
 TMS
 443:TCP
 To import sessions and health status (HTTPS).
CTS-Manager (CTSMAN) PCA
 CTSMAN
 80:TCP
 To import sessions and to poll health status (HTTP).
PCA
 CTSMAN
 161:UDP
 To poll health status (SNMP).
PCA
 CTSMAN
 443:TCP
 To import sessions and to poll health status (HTTPS).
Cisco MCU PCA
 MCU
 80:TCP
 To poll call details and health status (HTTP).
PCA
 MCU
 161:UDP
 To poll health status (SNMP).
PCA
 MCU
 443:TCP
 To poll call details and health status (HTTPS)
Cisco TP Multipoint Switch (CTMS) PCA
 CTMS
 80:TCP
 To poll health status (HTTP).
PCA
 CTMS
 161:UDP
 To poll health status (SNMP).
PCA
 CTMS
 443:TCP
 To poll health status (HTTPS).
Cisco TP Server (TPS) PCA
TPS
80:TCP
 To poll health status (HTTP).
PCA
 TPS
161:UDP
 To poll health status (SNMP).
PCA
TPS
443:TCP
 To poll health status (HTTPS).
Cisco VCS PCA
 VCS
 80.TCP
 To poll call details and health status (HTTP).
PCA
 VCS
 161:UDP
 To poll health status (SNMP).
PCA
 VCS
 443:TCP
 To poll call details and health status (HTTPS).
Cisco Unified CM (CUCM) PCA
 CUCM
22:TCP
 To obtain data from CUCM using SFTP service (SFTP).
PCA
 CUCM
80:TCP
 To obtain call details from CUCM (HTTP).
PCA
 CUCM
161:UDP
 To poll health status (SNMP).
PCA
 CUCM
443:TCP
 To polls status and RTMT information (HTTPS).
PCA
 CUCM
2748:TCP
CTI application server.
PCA
 CUCM
2749:TCP
 TLS connection between CTI application (JTAPI/TSP) and CTI manager.
PCA
 CUCM
2789:TCP
 JTAPI application server.
PCA
 CUCM
8080:TCP
 To determine whether the CUCM web service is running (HTTP).
PCA
 CUCM
8443:TCP
 To polls CUCM status (HTTPS).
Cisco Unity Connection (CUC) PCA
 CUC
 80.TCP
 To poll health status (HTTP).
PCA
 CUC
 161:UDP
 To poll health status (SNMP).
PCA
 CUC
 443:TCP
 To poll health status (HTTPS).
Cisco Unified Presence Server (CUPS) PCA
 CUPS
 80.TCP
 To poll health status (HTTP).
PCA
 CUPS
 161:UDP
 To poll health status (SNMP).
PCA
 CUPS
 443:TCP
 To poll health status (HTTPS).
TelePresence/Video Endpoints PCA
 TP Endpoints
 22:TCP
 To access endpoints during troubleshooting (SSH).
PCA
 TP Endpoints
 80:TCP
 To poll device info and status and call quality stats (HTTP).
PCA
 TP Endpoints
 161:UDP
 To poll device info and status and call quality stats (SNMP).
PCA
 TP Endpoints
 443:TCP
 To poll device info and status and call quality stats (HTTPS).
IP Phones PCA
 IP Phones
 80:TCP
 To obtain Serial Number and Load ID during discovery (HTTP).
PCA
 IP Phones
 443:TCP
 To obtain Serial Number and Load ID during discovery (HTTPS).
PCA
 IP Phones
 16384-32767:UDP
 To perform phone diagnostics testing.
Cisco 1040 Sensor PCA
 1040 Sensor
 2000:TCP
 To communicate with Cisco 1040 server using SCCP.
Network Devices PCA
 Network Devices
 22:TCP
 To access Mediatrace initiator during troubleshooting (SSH).
PCA
 Network Devices
 23:TCP
 To access Mediatrace initiator during troubleshooting (Telnet).
PCA
 Network Devices
 80:TCP
 To access Mediatrace initiator during troubleshooting (HTTP).
PCA
 Network Devices
 161:UDP
 To poll device and Medianet information (SNMP).
PCA
 Network Devices
 443:TCP
 To access Medianet initiator during troubleshooting (HTTPS).
DHCP/DNS/NTP/SMTP Servers PCA
 DHCP Server
 67,68:TCP
 DHCP service.
PCA
 DNS Server
 53:TCP
 DNS service.
PCA
 NTP Server
 123:UDP
 NTP service.
PCA
 SMTP Server
 25:TCP
 SMTP service.
Assurance Server (PCA) Cisco 1040
 PCA
 5666:UDP
 To receive syslog messages from Cisco 1040 sensors.
Cisco VCS
 PCA
 8886:TCP
 To receive feedback/notification from Cisco VCS (HTTPS).
Cisco VCS
 PCA
 8889:TCP
 To receive feedback/notification from Cisco VCS (HTTP).
Network Devices
 PCA
 162:UDP
 To receive SNMP traps.
Network Devices
 PCA
 514:UDP
 To receive syslogs
Network Devices
 PCA
 9000:UDP
 To receive traps (CSListener) if port 162 is occupied.


Internal Ports used by Prime Collaboration Assurance Server

The following ports are used by the Prime Collaboration Assurance (PCA) server to communicate either with the client machine or for the internal use.

From (Sender)
 To (Listener)
 Destination Port
 Purpose
PCA
-
 1018:TCP
 Poller RMI port.
PCA
 -
 1019:TCP
 Fault RMI port.
PCA
 -
 1024-4999
 Ephemeral ports.
PCA
 -
 5665-5684
 Inter processes communication between user interface and backend processes.
PCA
 -
 9002
 DynamID authentication
PCA
 -
 9009
 Default port number used by the IP telephony server for receiving traps from the device fault server.
PCA
 -
 9822:TCP
 Used for internal communication within the PCA server
PCA
 -
 40000-41000
 Used by Common Transport Mechanism for internal application messaging.
PCA
 -
 42344
 Used by Synthetic Testing web service.
PCA
 -
 42350-42353
 Used by messaging software.
PCA
 -
 43445
 Used by Alert History database engine.
PCA
 -
 43446
 Used by inventory service database engine.
PCA
 -
 43447
 Used by event processing database engine.
PCA
 -
 43449
 Used by IP Phone Information Facility database engine.
PCA
 -
 43459
 QOVRdatabase.
Client
PCA
 26:TCP
 To connect to the PCA server from the client machine over SSH.
Client browser
 PCA
 80:TCP
 To connect to the PCA server from the client machine over HTTP.
Client browser
 PCA
 443:UDP
 To connect to the PCA server from the client machine over HTTPS.


Ports Used by Prime Collaboration Provisioning Server, Devices, and Applications

The following tables lists the required ports for the Cisco Prime Collaboration Provisioning server to communicate with the devices and applications.

From (Sender)
 To (Listener)
 Destination Port
Purpose
Provisioning server
 Cisco Unified Presence
 8443:TCP
 To communicate over HTTPS.
Provisioning server
 Cisco Unity Connection
 8443:TCP
 To communicate over HTTPS.
Provisioning server
 Cisco Unity Express
 22:TCP
 To communicate using SSH service.
Provisioning server
 Cisco Unity Express
 23:TCP
 To communicate using Telnet service.
Provisioning server
 Cisco Unity
 1433
JDBC
Provisioning server
 Unified CM
 80:TCP
 HTTP/Apache Web Server
Provisioning server
 Unified CM
8443:TCP
 To communicate over HTTPS.
Provisioning server
 Unified CM Express
 22:TCP
 To communicate using SSH service.
Provisioning server
 Unified CM Express
 23:TCP
 To communicate using Telnet service.


Internal Ports used by Prime Collaboration Provisioning Server

The following ports are used by the Prime Collaboration Provisioning servers to communicate either with the client machine or for the internal use.

From (Sender)
 To (Listener)
 Destination Port
 Purpose
Client browser
Provisioning server 80:TCP
 To communicate with the client machine over HTTP.
Client browser
 Provisioning server
 46443:TCP
 To communicate with the client machine over HTTPS.
Provisioning server
 Database
 5432 (JDBC)
 Used by the Postgres database. If you are performing a distributed installation (where the application and database are on separate server), this port must be open for inbound communication on the Provisioning Manager database server. For the Prime Collaboration Provisioning single server installation, this port is not used and should not be open for external access.
Provisioning server
 -
 46001
 CUPM NICE Engine (RMI)
Provisioning server
 -
 46008
 Jboss Application Server (HTTP)
Provisioning server
 -
 46009
 Jboss Application Server (AJP)
Provisioning server
 -
 46083
 Jboss Application Server (web services)
Provisioning server
 -
 46098
 Jboss Application Server (RMI)
Provisioning server
 -
 46099
 Jboss Application Server (JNP service)
Provisioning server
 -
 46444
 Jboss Application Server (JRMP)
Provisioning server
 -
 46445
 Jboss Application Server (Transaction Manager)
Provisioning server
 -
 46446
 Jboss Application Server  (Remote server)
Provisioning server
 -
 46457
 Jboss Application Server (Bisocket Transport)



Rating: 4.8/5 (5 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Required_Ports_for_Prime_Collaboration"
Personal tools