Required Ports for Prime Collaboration
From DocWiki
m (1 revision: Final version - PC 9.0) |
|||
| (3 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | The following tables lists the required ports for the Cisco Prime Collaboration Assurance and Cisco Prime Collaboration Provisioning servers to communicate with the devices.<br> | + | The following tables lists the required ports for the Cisco Prime Collaboration Assurance and Cisco Prime Collaboration Provisioning servers to communicate with the devices.<br> |
| - | = 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 to communicate with the devices and applications.<br> |
| - | {| | + | {| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable" |
|- | |- | ||
| - | | '''Devices/Applications'''<br> | + | | '''Devices/Applications'''<br> |
| - | | width="150" | '''From (Sender)'''<br> | + | | width="150" | '''From (Sender)'''<br> |
| - | | '''To (Listener)''' <br> | + | | '''To (Listener)''' <br> |
| - | | '''Destination Port '''<br> | + | | '''Destination Port '''<br> |
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
| All Managed Devices | | All Managed Devices | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | All managed devices<br> | + | | All managed devices<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll SNMP MIBs.<br> | | To poll SNMP MIBs.<br> | ||
|- | |- | ||
| Cisco 1040 Sensor | | Cisco 1040 Sensor | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco 1040 sensor<br> | + | | Cisco 1040 sensor<br> |
| - | | 2000<br> | + | | 2000<br> |
| To communicate with Cisco 1040 server using SCCP.<br> | | To communicate with Cisco 1040 server using SCCP.<br> | ||
|- | |- | ||
| - | | rowspan="3" |CTS-Manager | + | | rowspan="3" | CTS-Manager |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | CTS-Manager<br> | + | | CTS-Manager<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> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | CTS-Manager<br> | + | | CTS-Manager<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | CTS-Manager<br> | + | | CTS-Manager<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 | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco MCU<br> | + | | Cisco 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> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco MCU<br> | + | | Cisco MCU<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco MCU<br> | + | | Cisco 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="2" | Cisco TelePresence Multipoint Switch | | rowspan="2" | Cisco TelePresence Multipoint Switch | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco TelePresence Multipoint Switch<br> | + | | Cisco TelePresence Multipoint Switch<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco TelePresence Multipoint Switch<br> | + | | Cisco TelePresence Multipoint Switch<br> |
| - | | 443:TCP<br> | + | | 443:TCP<br> |
| To poll health status (HTTPS).<br> | | To poll health status (HTTPS).<br> | ||
|- | |- | ||
| rowspan="2" | Cisco TelePresence system | | rowspan="2" | Cisco TelePresence system | ||
| Assurance server | | Assurance server | ||
| - | | Cisco Telepresence system <br> | + | | Cisco Telepresence system <br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| To poll health status (HTTP). <br> | | To poll health status (HTTP). <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco Telepresence system <br> | + | | Cisco Telepresence system <br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
| - | | rowspan="3"| Cisco TMS | + | | rowspan="3" | Cisco TMS |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco TMS<br> | + | | Cisco TMS<br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| To import sessions and health status (HTTP).<br> | | To import sessions and health status (HTTP).<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco TMS<br> | + | | Cisco TMS<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| To poll health status (SNMP).<br> | | To poll health status (SNMP).<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco TMS<br> | + | | Cisco TMS<br> |
| - | | 443:TCP<br> | + | | 443:TCP<br> |
| To import sessions and health status (HTTP).<br> | | To import sessions and health status (HTTP).<br> | ||
|- | |- | ||
| - | | rowspan="3"|Cisco VCS | + | | rowspan="3" | Cisco VCS |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco VCS<br> | + | | Cisco 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> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco VCS<br> | + | | Cisco VCS<br> |
| - | | 161:UDP<br> | + | | 161:UDP<br> |
| - | | To health status (SNMP). <br> | + | | To poll health status (SNMP). <br> |
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Cisco VCS<br> | + | | Cisco 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> | ||
|- | |- | ||
| - | | IP Phones<br> | + | | IP Phones<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | IP phones<br> | + | | IP phones<br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| To obtain XML-based data (serial numbers and load ID) from phones during discovery.<br> | | To obtain XML-based data (serial numbers and load ID) from phones during discovery.<br> | ||
|- | |- | ||
| - | | rowspan="2"|Network Devices | + | | rowspan="2" | Network Devices |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Network devices<br> | + | | Network devices<br> |
| - | | 23:TCP<br> | + | | 23:TCP<br> |
| To initiate the Telnet connection to medianet-enabled devices during the troubleshooting process.<br> | | To initiate the Telnet connection to medianet-enabled devices during the troubleshooting process.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Network devices<br> | + | | Network devices<br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| To initiate HTTP connection to the medianet-enabled devices during the troubleshooting process. <br> | | To initiate HTTP connection to the medianet-enabled devices during the troubleshooting process. <br> | ||
|- | |- | ||
| Real Time Monitoring Tool (RTMT) | | Real Time Monitoring Tool (RTMT) | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Real Time Monitoring Tool (RTMT)<br> | + | | Real Time Monitoring Tool (RTMT)<br> |
| - | | 443:TCP<br> | + | | 443:TCP<br> |
| To initiate the HTTPS connection.<br> | | To initiate the HTTPS connection.<br> | ||
|- | |- | ||
| - | | rowspan=" | + | | rowspan="9" | Unified CM |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 22:TCP<br> | + | | 22:TCP<br> |
| To obtain data from Unified CM using SFTP service.<br> | | To obtain data from Unified CM using SFTP service.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| - | | To obtain call details from Unified CM.<br> | + | | To obtain call details from Unified CM (HTTP).<br> |
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 443:TCP<br> | + | | 161:UDP<br> |
| + | | To poll health status (SNMP). <br> | ||
| + | |- | ||
| + | | Assurance server<br> | ||
| + | | Unified CM<br> | ||
| + | | 443:TCP<br> | ||
| To polls status over HTTPS.<br> | | To polls status over HTTPS.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 2748:TCP <br> | + | | 2748:TCP <br> |
| CTI application server.<br> | | CTI application server.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 2789:TCP<br> | + | | 2749:TCP<br> |
| + | | TLS connection between CTI applications (JTAPI/TSP) and CTI manager.<br> | ||
| + | |- | ||
| + | | Assurance server<br> | ||
| + | | Unified CM<br> | ||
| + | | 2789:TCP<br> | ||
| JTAPI application server.<br> | | JTAPI application server.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 8080<br> | + | | 8080:TCP<br> |
| - | | To determine whether the Cisco Prime Unified Communications Manager web service is running. <br> | + | | To determine whether the Cisco Prime Unified Communications Manager web service is running (HTTP). <br> |
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Unified CM | + | | Unified CM<br> |
| - | | | + | | 8443:TCP<br> |
| - | | | + | | To polls status over HTTPS.<br> |
|- | |- | ||
| Video Endpoints | | Video Endpoints | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | Video endpoints<br> | + | | Video endpoints<br> |
| - | | 22:TCP<br> | + | | 22:TCP<br> |
| To initiate SSH connection to endpoints during the troubleshooting process. | | To initiate SSH connection to endpoints during the troubleshooting process. | ||
|- | |- | ||
| - | | rowspan="3" |DHCP, DNS, and SMTP Servers | + | | rowspan="3" | DHCP, DNS, and SMTP Servers |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | DHCP server<br> | + | | DHCP server<br> |
| - | | 67,68:TCP<br> | + | | 67,68:TCP<br> |
| DHCP service.<br> | | DHCP service.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | DNS server<br> | + | | DNS server<br> |
| - | | 53:TCP<br> | + | | 53:TCP<br> |
| DNS service.<br> | | DNS service.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | SMTP server<br> | + | | SMTP server<br> |
| - | | 25:TCP<br> | + | | 25:TCP<br> |
| SMTP service.<br> | | SMTP service.<br> | ||
|- | |- | ||
| - | | rowspan="7"|Assurance Server | + | | rowspan="7" | Assurance Server |
| - | | Cisco 1040<br> | + | | Cisco 1040<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 5666<br> | + | | 5666<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> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 8886:TCP<br> | + | | 8886:TCP<br> |
| To receive feedback/notification from Cisco VCS over HTTPS. <br> | | To receive feedback/notification from Cisco VCS over HTTPS. <br> | ||
|- | |- | ||
| - | | Cisco VCS<br> | + | | Cisco VCS<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 8889:TCP<br> | + | | 8889:TCP<br> |
| To receive feedback/notification from Cisco VCS over HTTP. <br> | | To receive feedback/notification from Cisco VCS over HTTP. <br> | ||
|- | |- | ||
| - | | Network devices<br> | + | | Network devices<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 162:UDP<br> | + | | 162:UDP<br> |
| To receive SNMP traps.<br> | | To receive SNMP traps.<br> | ||
|- | |- | ||
| - | | Network devices<br> | + | | Network devices<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 514:UDP<br> | + | | 514:UDP<br> |
| To receive syslogs<br> | | To receive syslogs<br> | ||
|- | |- | ||
| - | | Network devices<br> | + | | Network devices<br> |
| - | | Assurance server<br> | + | | Assurance server<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> | ||
|} | |} | ||
| - | <br> | + | <br> |
| - | = 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 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" |
|- | |- | ||
| - | | '''From (Sender)'''<br> | + | | '''From (Sender)'''<br> |
| - | | '''To (Listener)'''<br> | + | | '''To (Listener)'''<br> |
| - | | '''Destination Port'''<br> | + | | '''Destination Port'''<br> |
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 1018:TCP<br> | + | | 1018:TCP<br> |
| Poller RMI port.<br> | | Poller RMI port.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 1019:TCP<br> | + | | 1019:TCP<br> |
| Fault RMI port.<br> | | Fault RMI port.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 1024-4999<br> | + | | 1024-4999<br> |
| Ephemeral ports.<br> | | Ephemeral ports.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 5665-5680<br> | + | | 5665-5680<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. These ports must be free. <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 9002<br> | + | | 9002<br> |
| DynamID authentication<br> | | DynamID authentication<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<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> | + | | Assurance server<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 Prime Collaboration Assurance server<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<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> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 42344<br> | + | | 42344<br> |
| Used by Synthetic Testing web service.<br> | | Used by Synthetic Testing web service.<br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 42350-42353<br> | + | | 42350-42353<br> |
| Used by messaging software. <br> | | Used by messaging software. <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 43445<br> | + | | 43445<br> |
| Used by Alert History database engine. <br> | | Used by Alert History database engine. <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 43446<br> | + | | 43446<br> |
| Used by inventory service database engine. <br> | | Used by inventory service database engine. <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 43447<br> | + | | 43447<br> |
| Used by event processing database engine. <br> | | Used by event processing database engine. <br> | ||
|- | |- | ||
| - | | Assurance server<br> | + | | Assurance server<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> | + | | Assurance server<br> |
| - | | -<br> | + | | -<br> |
| - | | 43459<br> | + | | 43459<br> |
| QOVRdatabase.<br> | | QOVRdatabase.<br> | ||
|- | |- | ||
| - | | Client browser<br> | + | | Client browser<br> |
| - | | Assurance server<br> | + | | Assurance server<br> |
| - | | 22:TCP<br> | + | | 22:TCP<br> |
| To connect to the Prime Collaboration server from the client machine. <br> | | To connect to the Prime Collaboration server from the client machine. <br> | ||
|- | |- | ||
| - | | Client browser<br> | + | | Client browser<br> |
| - | | Assurance server<br> | + | | Assurance server<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 Prime Collaboration server from the client machine over HTTP. <br> | ||
|- | |- | ||
| - | | Client browser<br> | + | | Client browser<br> |
| - | | Assurance server<br> | + | | Assurance server<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 Prime Collaboration 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> = |
| - | The following tables lists the required ports for the Cisco Prime Collaboration Provisioning server to communicate with the devices and applications.<br> | + | The following tables lists the required ports for the Cisco Prime Collaboration Provisioning server to communicate with the devices and applications.<br> |
| - | {| | + | {| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable sortable" |
|- | |- | ||
| - | | '''From (Sender)'''<br> | + | | '''From (Sender)'''<br> |
| - | | '''To (Listener)'''<br> | + | | '''To (Listener)'''<br> |
| - | | '''Destination Port '''<br> | + | | '''Destination Port '''<br> |
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Cisco Unified Presence<br> | + | | Cisco Unified Presence<br> |
| - | | 8443:TCP<br> | + | | 8443:TCP<br> |
| To communicate over HTTPS.<br> | | To communicate over HTTPS.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Cisco Unity Connection<br> | + | | Cisco Unity Connection<br> |
| - | | 8443:TCP<br> | + | | 8443:TCP<br> |
| To communicate over HTTPS.<br> | | To communicate over HTTPS.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Cisco Unity Express<br> | + | | Cisco Unity Express<br> |
| - | | 22:TCP<br> | + | | 22:TCP<br> |
| To communicate using SSH service.<br> | | To communicate using SSH service.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Cisco Unity Express<br> | + | | Cisco Unity Express<br> |
| - | | 23:TCP<br> | + | | 23:TCP<br> |
| To communicate using Telnet service.<br> | | To communicate using Telnet service.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Cisco Unity<br> | + | | Cisco Unity<br> |
| - | | 1433 <br> | + | | 1433 <br> |
| JDBC<br> | | JDBC<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Unified CM<br> | + | | Unified CM<br> |
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| HTTP/Apache Web Server<br> | | HTTP/Apache Web Server<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Unified CM <br> | + | | Unified CM <br> |
| - | | 8443:TCP<br> | + | | 8443:TCP<br> |
| To communicate over HTTPS.<br> | | To communicate over HTTPS.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Unified CM Express<br> | + | | Unified CM Express<br> |
| - | | 22:TCP<br> | + | | 22:TCP<br> |
| To communicate using SSH service.<br> | | To communicate using SSH service.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Unified CM Express<br> | + | | Unified CM Express<br> |
| - | | 23:TCP<br> | + | | 23:TCP<br> |
| To communicate using Telnet service.<br> | | To communicate using Telnet service.<br> | ||
|} | |} | ||
| - | <br> | + | <br> |
| - | = Internal Ports used by Prime Collaboration Provisioning Server<br> = | + | = Internal Ports used by Prime Collaboration Provisioning Server<br> = |
| - | The following ports are used by the Prime Collaboration Provisioning servers to communicate either with the client machine or for the internal use.<br> | + | The following ports are used by the Prime Collaboration Provisioning servers to communicate either with the client machine or for the internal use.<br> |
| - | {| | + | {| width="900" cellspacing="0" cellpadding="5" border="1" class="wikitable sortable" |
|- | |- | ||
| - | | '''From (Sender)'''<br> | + | | '''From (Sender)'''<br> |
| - | | '''To (Listener)'''<br> | + | | '''To (Listener)'''<br> |
| - | | '''Destination Port'''<br> | + | | '''Destination Port'''<br> |
| '''Purpose'''<br> | | '''Purpose'''<br> | ||
|- | |- | ||
| - | | Client browser <br> | + | | Client browser <br> |
| Provisioning server | | Provisioning server | ||
| - | | 80:TCP<br> | + | | 80:TCP<br> |
| To communicate with the client machine over HTTP. | | To communicate with the client machine over HTTP. | ||
|- | |- | ||
| - | | Client browser<br> | + | | Client browser<br> |
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | 46443:TCP<br> | + | | 46443:TCP<br> |
| To communicate with the client machine over HTTPS.<br> | | To communicate with the client machine over HTTPS.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | Database<br> | + | | Database<br> |
| - | | 5432 (JDBC)<br> | + | | 5432 (JDBC)<br> |
| 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.<br> | | 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.<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46001<br> | + | | 46001<br> |
| CUPM NICE Engine (RMI)<br> | | CUPM NICE Engine (RMI)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46008<br> | + | | 46008<br> |
| Jboss Application Server (HTTP)<br> | | Jboss Application Server (HTTP)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46009<br> | + | | 46009<br> |
| Jboss Application Server (AJP)<br> | | Jboss Application Server (AJP)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46083<br> | + | | 46083<br> |
| Jboss Application Server (web services)<br> | | Jboss Application Server (web services)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46098<br> | + | | 46098<br> |
| Jboss Application Server (RMI)<br> | | Jboss Application Server (RMI)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46099<br> | + | | 46099<br> |
| Jboss Application Server (JNP service)<br> | | Jboss Application Server (JNP service)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46444<br> | + | | 46444<br> |
| Jboss Application Server (JRMP)<br> | | Jboss Application Server (JRMP)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46445<br> | + | | 46445<br> |
| Jboss Application Server (Transaction Manager)<br> | | Jboss Application Server (Transaction Manager)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46446<br> | + | | 46446<br> |
| Jboss Application Server (Remote server)<br> | | Jboss Application Server (Remote server)<br> | ||
|- | |- | ||
| - | | Provisioning server<br> | + | | Provisioning server<br> |
| - | | -<br> | + | | -<br> |
| - | | 46457<br> | + | | 46457<br> |
| Jboss Application Server (Bisocket Transport)<br> | | Jboss Application Server (Bisocket Transport)<br> | ||
|} | |} | ||
| - | <br> | + | <br> |
| - | <br> | + | <br> |
| - | [[Category: | + | [[Category:Cisco_Prime_Collaboration_9_0]] |
Revision as of 23:07, 24 January 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 to communicate with the devices and applications.
| Devices/Applications | From (Sender) | To (Listener) | Destination Port | Purpose |
| All Managed Devices | Assurance server | All managed devices | 161:UDP | To poll SNMP MIBs. |
| Cisco 1040 Sensor | Assurance server | Cisco 1040 sensor | 2000 | To communicate with Cisco 1040 server using SCCP. |
| CTS-Manager | Assurance server | CTS-Manager | 80:TCP | To import sessions and to poll health status (HTTP). |
| Assurance server | CTS-Manager | 161:UDP | To poll health status (SNMP). | |
| Assurance server | CTS-Manager | 443:TCP | To import sessions and to poll health status (HTTPS). | |
| Cisco MCU | Assurance server | Cisco MCU | 80:TCP | To poll call details and health status (HTTP). |
| Assurance server | Cisco MCU | 161:UDP | To poll health status (SNMP). | |
| Assurance server | Cisco MCU | 443:TCP | To poll call details and health status (HTTPS) | |
| Cisco TelePresence Multipoint Switch | Assurance server | Cisco TelePresence Multipoint Switch | 161:UDP | To poll health status (SNMP). |
| Assurance server | Cisco TelePresence Multipoint Switch | 443:TCP | To poll health status (HTTPS). | |
| Cisco TelePresence system | Assurance server | Cisco Telepresence system | 80:TCP | To poll health status (HTTP). |
| Assurance server | Cisco Telepresence system | 161:UDP | To poll health status (SNMP). | |
| Cisco TMS | Assurance server | Cisco TMS | 80:TCP | To import sessions and health status (HTTP). |
| Assurance server | Cisco TMS | 161:UDP | To poll health status (SNMP). | |
| Assurance server | Cisco TMS | 443:TCP | To import sessions and health status (HTTP). | |
| Cisco VCS | Assurance server | Cisco VCS | 80.TCP | To poll call details and health status (HTTP). |
| Assurance server | Cisco VCS | 161:UDP | To poll health status (SNMP). | |
| Assurance server | Cisco VCS | 443:TCP | To poll call details and health status (HTTPS). | |
| IP Phones | Assurance server | IP phones | 80:TCP | To obtain XML-based data (serial numbers and load ID) from phones during discovery. |
| Network Devices | Assurance server | Network devices | 23:TCP | To initiate the Telnet connection to medianet-enabled devices during the troubleshooting process. |
| Assurance server | Network devices | 80:TCP | To initiate HTTP connection to the medianet-enabled devices during the troubleshooting process. | |
| Real Time Monitoring Tool (RTMT) | Assurance server | Real Time Monitoring Tool (RTMT) | 443:TCP | To initiate the HTTPS connection. |
| Unified CM | Assurance server | Unified CM | 22:TCP | To obtain data from Unified CM using SFTP service. |
| Assurance server | Unified CM | 80:TCP | To obtain call details from Unified CM (HTTP). | |
| Assurance server | Unified CM | 161:UDP | To poll health status (SNMP). | |
| Assurance server | Unified CM | 443:TCP | To polls status over HTTPS. | |
| Assurance server | Unified CM | 2748:TCP | CTI application server. | |
| Assurance server | Unified CM | 2749:TCP | TLS connection between CTI applications (JTAPI/TSP) and CTI manager. | |
| Assurance server | Unified CM | 2789:TCP | JTAPI application server. | |
| Assurance server | Unified CM | 8080:TCP | To determine whether the Cisco Prime Unified Communications Manager web service is running (HTTP). | |
| Assurance server | Unified CM | 8443:TCP | To polls status over HTTPS. | |
| Video Endpoints | Assurance server | Video endpoints | 22:TCP | To initiate SSH connection to endpoints during the troubleshooting process. |
| DHCP, DNS, and SMTP Servers | Assurance server | DHCP server | 67,68:TCP | DHCP service. |
| Assurance server | DNS server | 53:TCP | DNS service. | |
| Assurance server | SMTP server | 25:TCP | SMTP service. | |
| Assurance Server | Cisco 1040 | Assurance server | 5666 | To receive syslog messages from Cisco 1040 sensors. |
| Cisco VCS | Assurance server | 8886:TCP | To receive feedback/notification from Cisco VCS over HTTPS. | |
| Cisco VCS | Assurance server | 8889:TCP | To receive feedback/notification from Cisco VCS over HTTP. | |
| Network devices | Assurance server | 162:UDP | To receive SNMP traps. | |
| Network devices | Assurance server | 514:UDP | To receive syslogs | |
| Network devices | Assurance server | 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 server to communicate either with the client machine or for the internal use.
| From (Sender) | To (Listener) | Destination Port | Purpose |
| Assurance server | - | 1018:TCP | Poller RMI port. |
| Assurance server | - | 1019:TCP | Fault RMI port. |
| Assurance server | - | 1024-4999 | Ephemeral ports. |
| Assurance server | - | 5665-5680 | Inter processes communication between user interface and backend processes. These ports must be free. |
| Assurance server | - | 9002 | DynamID authentication |
| Assurance server | - | 9009 | Default port number used by the IP telephony server for receiving traps from the device fault server. |
| Assurance server | - | 9822:TCP | Used for internal communication within the Prime Collaboration Assurance server |
| Assurance server | - | 40000-41000 | Used by Common Transport Mechanism for internal application messaging. |
| Assurance server | - | 42344 | Used by Synthetic Testing web service. |
| Assurance server | - | 42350-42353 | Used by messaging software. |
| Assurance server | - | 43445 | Used by Alert History database engine. |
| Assurance server | - | 43446 | Used by inventory service database engine. |
| Assurance server | - | 43447 | Used by event processing database engine. |
| Assurance server | - | 43449 | Used by IP Phone Information Facility database engine. |
| Assurance server | - | 43459 | QOVRdatabase. |
| Client browser | Assurance server | 22:TCP | To connect to the Prime Collaboration server from the client machine. |
| Client browser | Assurance server | 80:TCP | To connect to the Prime Collaboration server from the client machine over HTTP. |
| Client browser | Assurance server | 443:UDP | To connect to the Prime Collaboration 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) |