What ports need to be opened on the firewall for Cisco CUCM monitoring?

[Anon]

Ports required to monitor Cisco Unified Communication Manager servers in the cluster:

• 22 - TCP - SSH port for SFTP to collect Call Detail Records (CDR) and Call Detail Diagnostic Records (CMR) from CUCM 5+ clusters.
• 161 - UDP - SNMP port to collect status information
• 443 or 8443 - TCP - SOAP port to retrieve AXL and Perfmon statistics

Ports required for VG and H323 gateways monitoring:

• 161 - UDP - SNMP port to collect status information

Ports required for TelePresence End points monitoring

• 161 - UDP - SNMP port to collect status information
• 443 or 8443 - TCP - Port to collect call statistics

Ports required for IP phones:

• 80 - TCP - port to poll for QOS and Device information

For more information, see details in online help under: Installation > Important Information > Port Requirements

[GeraldC1]

The UCC Welcome / All PBXs dashboard in Prognosis Client/Web UI has some indicators when there are connectivity issues:

• Contactability "Yes/No/Partial" is referring to the Perfmon / AXL SOAP connection to CUCM publisher and subscribers. "No" means it cannot contact any of the Call Managers meaning Prognosis cannot contact the Publisher CUCM and cannot contact the Subscriber CUCMs.
• Endpoints X of Y:
• Y is an SQL query to the Publisher call manager to get a list of all the phones and which CUCM call manager each endpoint is registered to.
• X is SNMP requests for the phone table from the publisher and subscriber Call managers depending on which call manager the endpoint is registered to. This request obtains the Registered/Not Registered/Unknown status of the phone endpoints;
• Examples: "0 of 46" means that the SQL query to the publisher was successful in getting a list of endpoints, but then the SNMP connectivity to call managers is failing. 
• Vendor field blank:
  • The first SNMP request from Prognosis is to the publisher to obtain the Cisco device type and version. If this is blank then it means that this initial SNMP request is also failing. 
• Also Prognosis is a passive listener for receiving CDRs - Prognosis SFTP daemon listens to receive CDRs from the Cisco publisher for calls data and CMR files for voice quality / quality of service.

*The cluster collector log can provide more  clues to the nature of the problem.

Next steps are to apply/re-apply the current Cisco Admin credentials into the PASSWORDS configuration in Prognosis, or to apply the Community String into the PASSWORDS configuration in Prognosis for SNMP connectivity, and also to check that specific services are up and running on the Cisco call managers, and/or try restarting the services on the Cisco servers.

[GeraldC1]

[GeraldC1]