Required Ports for Prime Collaboration
From DocWiki
m (→Ports Used by Prime Collaboration Assurance Server, Devices, and Applications) |
m (→Ports Used by Prime Collaboration Assurance Server, Devices, and Applications) |
||
(32 intermediate revisions not shown) | |||
Line 3: | Line 3: | ||
= Ports Used by Prime Collaboration Assurance Server, Devices, and Applications<br> = | = Ports Used by Prime Collaboration Assurance Server, Devices, and Applications<br> = | ||
- | The following tables lists the required ports for the Cisco Prime Collaboration Assurance 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" | ||
|- | |- | ||
| '''Devices/Applications'''<br> | | '''Devices/Applications'''<br> | ||
- | + | | '''From (Sender)'''<br> | |
| '''To (Listener)''' <br> | | '''To (Listener)''' <br> | ||
| '''Destination Port '''<br> | | '''Destination Port '''<br> | ||
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
- | | Cisco | + | | rowspan="3" | Cisco TMS |
- | | | + | | PCA<br> |
- | | | + | | TMS<br> |
- | | | + | | 80:TCP<br> |
- | | To | + | | 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 | + | | rowspan="3" | CTS-Manager (CTSMAN) |
- | | | + | | PCA<br> |
- | | | + | | CTSMAN<br> |
| 80:TCP<br> | | 80:TCP<br> | ||
| To import sessions and to poll health status (HTTP). <br> | | To import sessions and to poll health status (HTTP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CTSMAN<br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CTSMAN<br> |
| 443:TCP<br> | | 443:TCP<br> | ||
| To import sessions and to poll health status (HTTPS).<br> | | To import sessions and to poll health status (HTTPS).<br> | ||
|- | |- | ||
| rowspan="3" | Cisco MCU | | rowspan="3" | Cisco MCU | ||
- | | | + | | PCA<br> |
- | | | + | | MCU<br> |
| 80:TCP<br> | | 80:TCP<br> | ||
| To poll call details and health status (HTTP). <br> | | To poll call details and health status (HTTP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | MCU<br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | MCU<br> |
| 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="3" | Cisco | + | | rowspan="3" | Cisco TP Multipoint Switch (CTMS) |
- | | | + | | PCA<br> |
- | | | + | | CTMS<br> |
| 80:TCP<br> | | 80:TCP<br> | ||
| To poll health status (HTTP). <br> | | To poll health status (HTTP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CTMS<br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CTMS<br> |
| 443:TCP<br> | | 443:TCP<br> | ||
| To poll health status (HTTPS).<br> | | To poll health status (HTTPS).<br> | ||
|- | |- | ||
- | | rowspan=" | + | | rowspan="3" | Cisco TP Server (TPS) |
- | | | + | | PCA <br> |
- | | | + | | TPS <br> |
| 80:TCP<br> | | 80:TCP<br> | ||
| To poll health status (HTTP). <br> | | To poll health status (HTTP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | TPS <br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
- | | | + | | PCA <br> |
- | + | | TPS <br> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | | | + | |
| 443:TCP<br> | | 443:TCP<br> | ||
- | | To | + | | To poll health status (HTTPS). <br> |
|- | |- | ||
| rowspan="3" | Cisco VCS | | rowspan="3" | Cisco VCS | ||
- | | | + | | PCA<br> |
- | | | + | | VCS<br> |
| 80.TCP<br> | | 80.TCP<br> | ||
| To poll call details and health status (HTTP). <br> | | To poll call details and health status (HTTP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | VCS<br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP). <br> | | To poll health status (SNMP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | VCS<br> |
| 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="9" | Cisco Unified CM (CUCM) | |
- | + | | PCA<br> | |
- | + | | CUCM <br> | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | | rowspan="9" | Unified CM | + | |
- | | | + | |
- | | | + | |
| 22:TCP<br> | | 22:TCP<br> | ||
- | | To obtain data from | + | | To obtain data from CUCM using SFTP service (SFTP).<br> |
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 80:TCP<br> | | 80:TCP<br> | ||
- | | To obtain call details from | + | | To obtain call details from CUCM (HTTP).<br> |
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 161:UDP<br> | | 161:UDP<br> | ||
| To poll health status (SNMP). <br> | | To poll health status (SNMP). <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 443:TCP<br> | | 443:TCP<br> | ||
- | | To polls status | + | | To polls status and RTMT information (HTTPS).<br> |
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 2748:TCP <br> | | 2748:TCP <br> | ||
| CTI application server.<br> | | CTI application server.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 2749:TCP<br> | | 2749:TCP<br> | ||
- | | TLS connection between CTI | + | | TLS connection between CTI application (JTAPI/TSP) and CTI manager.<br> |
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 2789:TCP<br> | | 2789:TCP<br> | ||
| JTAPI application server.<br> | | JTAPI application server.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 8080:TCP<br> | | 8080:TCP<br> | ||
- | | To determine whether the | + | | To determine whether the CUCM web service is running (HTTP). <br> |
|- | |- | ||
- | | | + | | PCA<br> |
- | | | + | | CUCM <br> |
| 8443:TCP<br> | | 8443:TCP<br> | ||
- | | To polls status | + | | To polls CUCM status (HTTPS).<br> |
|- | |- | ||
- | | 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> | ||
+ | | TP Endpoints<br> | ||
| 22:TCP<br> | | 22:TCP<br> | ||
- | | To | + | | To access endpoints during troubleshooting (SSH). <br> |
+ | |- | ||
+ | | PCA<br> | ||
+ | | TP Endpoints<br> | ||
+ | | 80:TCP<br> | ||
+ | | To poll device info and status and call quality stats (HTTP). <br> | ||
+ | |- | ||
+ | | PCA<br> | ||
+ | | TP Endpoints<br> | ||
+ | | 161:UDP<br> | ||
+ | | To poll device info and status and call quality stats (SNMP). <br> | ||
+ | |- | ||
+ | | PCA<br> | ||
+ | | TP Endpoints<br> | ||
+ | | 443:TCP<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=" | + | | rowspan="4" | DHCP/DNS/NTP/SMTP Servers |
- | | | + | | PCA<br> |
- | | DHCP | + | | DHCP Server<br> |
| 67,68:TCP<br> | | 67,68:TCP<br> | ||
| DHCP service.<br> | | DHCP service.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | DNS | + | | DNS Server<br> |
| 53:TCP<br> | | 53:TCP<br> | ||
| DNS service.<br> | | DNS service.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
- | | SMTP | + | | NTP Server<br> |
+ | | 123:UDP<br> | ||
+ | | NTP service.<br> | ||
+ | |- | ||
+ | | PCA<br> | ||
+ | | SMTP Server<br> | ||
| 25:TCP<br> | | 25:TCP<br> | ||
| SMTP service.<br> | | SMTP service.<br> | ||
|- | |- | ||
- | | rowspan=" | + | | rowspan="6" | Assurance Server (PCA) |
| Cisco 1040<br> | | Cisco 1040<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> | ||
|- | |- | ||
| Cisco VCS<br> | | Cisco VCS<br> | ||
- | | | + | | PCA<br> |
| 8886:TCP<br> | | 8886:TCP<br> | ||
- | | To receive feedback/notification from Cisco VCS | + | | To receive feedback/notification from Cisco VCS (HTTPS). <br> |
|- | |- | ||
| Cisco VCS<br> | | Cisco VCS<br> | ||
- | | | + | | PCA<br> |
| 8889:TCP<br> | | 8889:TCP<br> | ||
- | | To receive feedback/notification from Cisco VCS | + | | To receive feedback/notification from Cisco VCS (HTTP). <br> |
|- | |- | ||
- | | Network | + | | Network Devices<br> |
- | | | + | | PCA<br> |
| 162:UDP<br> | | 162:UDP<br> | ||
| To receive SNMP traps.<br> | | To receive SNMP traps.<br> | ||
|- | |- | ||
- | | Network | + | | Network Devices<br> |
- | | | + | | PCA<br> |
| 514:UDP<br> | | 514:UDP<br> | ||
| To receive syslogs<br> | | To receive syslogs<br> | ||
|- | |- | ||
- | | Network | + | | Network Devices<br> |
- | | | + | | PCA<br> |
| 9000:UDP<br> | | 9000:UDP<br> | ||
| To receive traps (CSListener) if port 162 is occupied.<br> | | To receive traps (CSListener) if port 162 is occupied.<br> | ||
Line 237: | 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 246: | Line 325: | ||
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
- | | | + | | PCA <br> |
| -<br> | | -<br> | ||
| 1018:TCP<br> | | 1018:TCP<br> | ||
| Poller RMI port.<br> | | Poller RMI port.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 1019:TCP<br> | | 1019:TCP<br> | ||
| Fault RMI port.<br> | | Fault RMI port.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 1024-4999<br> | | 1024-4999<br> | ||
| Ephemeral ports.<br> | | Ephemeral ports.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
- | | 5665- | + | | 5665-5684<br> |
- | | Inter processes communication between user interface and backend processes | + | | Inter processes communication between user interface and backend processes. <br> |
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 9002<br> | | 9002<br> | ||
| DynamID authentication<br> | | DynamID authentication<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> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 9822:TCP<br> | | 9822:TCP<br> | ||
- | | Used for internal communication within the | + | | Used for internal communication within the PCA 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> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 42344<br> | | 42344<br> | ||
| Used by Synthetic Testing web service.<br> | | Used by Synthetic Testing web service.<br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 42350-42353<br> | | 42350-42353<br> | ||
| Used by messaging software. <br> | | Used by messaging software. <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 43445<br> | | 43445<br> | ||
| Used by Alert History database engine. <br> | | Used by Alert History database engine. <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 43446<br> | | 43446<br> | ||
| Used by inventory service database engine. <br> | | Used by inventory service database engine. <br> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 43447<br> | | 43447<br> | ||
| Used by event processing database engine. <br> | | Used by event processing database engine. <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> | ||
|- | |- | ||
- | | | + | | PCA<br> |
| -<br> | | -<br> | ||
| 43459<br> | | 43459<br> | ||
| QOVRdatabase.<br> | | QOVRdatabase.<br> | ||
|- | |- | ||
- | | Client | + | | Client <br> |
- | | | + | | PCA<br> |
- | | | + | | 26:TCP<br> |
- | | To connect to the | + | | To connect to the PCA server from the client machine over SSH. <br> |
|- | |- | ||
| Client browser<br> | | Client browser<br> | ||
- | | | + | | PCA<br> |
| 80:TCP<br> | | 80:TCP<br> | ||
- | | To connect to the | + | | To connect to the PCA server from the client machine over HTTP. <br> |
|- | |- | ||
| Client browser<br> | | Client browser<br> | ||
- | | | + | | PCA<br> |
| 443:UDP<br> | | 443:UDP<br> | ||
- | | To connect to the | + | | 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) |