An administrator has configured Cisco Unity Connection Port Monitor in order to monitor connections. Soon after, users begin reporting performance problems with Cisco Unity Connection.

Which of the following is most like the cause?

A. Port Monitor is not the correct tool for Cisco Unity Connection.
B. The administrator selected an incorrect node.
C. The Display Status field is not Idle.

D. The polling rate is too low.

Explanation:

Most likely, the polling rate is too low if users are reporting performance problems after an administrator has configured Cisco Unity Connection Port Monitor. The Cisco Unity Connection Port Monitor is a Cisco Unified Communications Manager (UCM) Real-Time Monitoring Tool (RTMT) option that can be used to monitor activity on each Cisco Unity Connection port in real time. The polling rate determines how many seconds elapse before Port Monitor gathers and updates data. If the polling rate is too low, Port Monitor can drag down performance of a Cisco Unity Connection system.

Port Monitor is the correct tool forCisco Unity Connection. You can access Port Monitor by using UCM RTMT, navigating to Unity Connection, and clicking Port Monitor.

Although the administrator might have selected an incorrect node, the selection of an incorrect node is not as likely to cause a performance problem as configuring a low polling rate. You can choose the node you want to monitor from the Node dropdown box in the Port Monitor window.

Although it is possible that the Display Status field would display a value other than Idle, thisis not likely the cause of a performance problem. The Port Monitor Window’s Display Status field is used to display the action that is currently being performed in a conversation. The Idle value indicates that the given port is not currently handling a call.

Reference:
Cisco: Using Cisco Unity Connection Port Monitor (PDF)