The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Tomcat Hypertext Transport Protocol (HTTP) and HTTP Secure (HTTPS) Connector object provides information about Tomcat connectors.
A Tomcat HTTP connector represents an endpoint that receives requests and sends responses. The connector handles HTTP/HTTPS requests and sends HTTP/HTTPS responses that occur when application web pages are accessed. The Secure Socket Layer (SSL) status of web application URLs provides the basis for the instance name for each Tomcat HTTP Connector. For example, https://<IP Address>:8443 for SSL or http://<IP Address>:8080 for non-SSL.
The Cisco Tomcat Java Virtual Machine (JVM) object provides information about the pool of common resource memory used by web applications such as Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and Cisco Unity Connection Administration. The dynamic memory block stores all objects that Tomcat and its web applications create.
The Cisco Tomcat Web Application object provides information about how to run web applications.
The URLs for the web application provide the basis for the instance name for each Tomcat Web Application, as explained in the following examples:
Cisco Unified Communications Manager Administration (https://<IP Address>:8443/ccmadmin) is identified by ccmadmin.
Cisco Unified Serviceability (https://<IP Address>:8443/ccmservice) is identified by ccmservice.
Cisco Unified Communications Manager User Options (https://<IP Address>:8443/ccmuser) is identified by ccmuser.
Cisco Unity Connection Administration (https://<IP Address>:8443/cuadmin) is identified by cuadmin.
URLs that do not have an extension, such as https://<IP Address>:8443 or http://<IP Address>:8080), are identified by _root.
The Database Change Notification Subscription object displays the names of tables where the client receives Change Notifications.
The SubscribedTable object displays the table with the service or servlet that receives change notifications. Because the counter does not increment, this display occurs for informational purposes only.
The DB User Host Information object provides information about DB User Host.
The DB:User:Host Instance object displays the number of connections that are present for each instance of DB:User:Host.
The Enterprise Replication Perfmon Counter object provides information about the various replication counters.
The ServerName:ReplicationQueueDepth counter displays the server name followed by the replication queue depth.
Displays the system physical memory utilization as a percentage. The value of this counter is calculated as follows: Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes) / Total KBytes This value also corresponds to the Used KBytes/Total KBytes |
|
Displays the system virtual memory utilization as a percentage. The value of this counter is calculated as follows: Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes) / (Total KBytes + Total Swap KBytes) This value also corresponds to Used VM KBytes/Total VM KBytes. |
|
The total amount of memory that is available in your system in kilobytes. |
|
The amount of free swap space that is available in your system in kilobytes. |
|
The amount of free memory in the high region. The Linux kernel splits the virtual memory address space into memory regions. The high memory is memory above a certain physical address, and its amount depends on the total memory and the type of kernel on the system. For the Cisco Unified Communications Manager system with 4 GB memory, the high memory is roughly in the address of 896M to 4096M. |
|
The total amount of memory in the high region. The Linux kernel splits the virtual memory address space into memory regions. The high memory is memory above a certain physical address, and its amount depends on the total memory and the type of kernel on the system. For the Cisco Unified Communications Manager system with 4 GB memory, the high memory is roughly in the address of 896M to 4096M. |
|
The number of page faults (both major and minor) that the system makes per second (post 2.5 kernels only). This reading does not necessarily represent a count of page faults that generate input and output (I/O) because some page faults can get resolved without I/O. |
|
The number of major faults that the system makes per second that require a memory page from the disk (post 2.5 kernels only). |
|
The number of pages that the system pages in from the disk, plus the number of pages that the system pages out to the disk. |
|
The total number of kilobytes that the system pages in from the disk per second. |
|
The total number of kilobytes that the system pages out to the disk per second. |
|
The memory used by created slabcaches by various kernel components, as a macroscopic counter representing the sum of all the individual entries in the proc's slabinfo. |
|
The amount of Swap used as cache memory. Memory that once was swapped out, is swapped back in, but is still in the swapfile. |
|
The total amount of system physical and memory and swap space (Total Kbytes + Total Swap Kbytes) that is in use in your system in kilobytes. |
|
The amount of in-use physical memory. The value of the Used KBytes counter is calculated as follows: Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes. The Used KBytes value differs from the Linux term that displays in the top or free command output. The Used value that displays in the top or free command output equals the difference in Total KBytes - Free KBytes and also includes the sum of Buffers KBytes and Cached KBytes. |
|
This counter represents the amount of swap space that is in use on your system in kilobytes. |
|
This counter represents the system physical memory and the amount of swap space that is in use on your system in kilobytes. The value is calculated as follows: Total KBytes - Free KBytes - Buffers KBytes - Cached KBytes + Shared KBytes + Used Swap KBytes This value corresponds to Used Mem KBytes + Used Swap KBytes. |
The number of bytes, including framing characters, that are received on this interface. |
|
The number of inbound packets that are chosen to be discarded even though no errors have been detected. This action prevents the packet from being delivered to a higher-layer protocol. Discarding packets also frees up buffer space. |
|
The number of inbound packets (packet-oriented interfaces) and the number of inbound transmission units (character-oriented or fixed-length interfaces) that contain errors that prevented them from being delivered to a higher-layer protocol. |
|
The number of multicast packets that are received on this interface. |
|
The number of packets that this sublayer delivered to a higher sublayer. This situation does not include the packets that are addressed to a multicast or broadcast address at this sublayer. |
|
The total number of received (Rx) bytes and transmitted (Tx) bytes. |
|
The total number of octets, including framing characters, that are transmitted out from the interface. |
|
The number of outbound packets that are chosen to be discarded even though no errors are detected. This action prevents the packet from being delivered to a higher layer protocol. Discarding a packet also frees up buffer space. |
|
The number of outbound packets (packet-oriented interfaces) and the number of outbound transmission units (character-oriented or fixed-length interfaces) that are transmitted because of errors. |
|
The total number of packets that the higher-level protocols requested for transmission, including those that are discarded or not sent. This situation does not include packets that are addressed to a multicast or broadcast address at this sublayer. |
|
The number of replicates that are created by Informix for the DB tables. This counter displays information during Replication Setup. |
|
The state of replication. The following list provides possible values:
|
The percentage of CPU time that is dedicated to handling IO requests that were issued to the disk. |
|
The percentage of disk space that is in use on this file system. |
|
Not Used. The Await Read Time counter replaces this counter. This counter is no longer valid with the counter value -1. |
|
Not Used. The Await Write Time counter replaces this counter. This counter is no longer valid with the counter value -1. |
|
The average time measured in milliseconds for read requests that are issued to the device to be served. |
|
The average time measured in milliseconds for input and output (I/O) requests that are issued to the device to be served. This reading includes the time spent by the requests in queue and the time spent servicing them. |
|
The average time measured in milliseconds for write requests that are issued to the device to be served. |
|
The average queue length for the requests that are issued to the disk. |
|
The amount of data in bytes per second that is read from the disk. |
|
The amount of total disk space in megabytes that is on this file system. |
|
The amount of disk space in megabytes that is in use on this file system. |
|
The amount of data that is written to the disk in bytes per second. |
This counter, which is expressed as a percentage of total central processing unit (CPU) time, represents the tasks share of the elapsed CPU time since the last update. |
|||
This counter represents the percentage of physical memory that a task is currently using. |
|||
This counter represents the stack size for task memory status. |
|||
|
|||
This counter represents the number of major page faults that a task encounters that requires the data to be loaded into memory. |
|||
This counter displays the task-unique process ID. The ID periodically wraps, but the value never equals zero. |
|||
This counter displays the process status:
|
|||
This counter displays the amount of shared memory in kilobytes (KB) that a task is using. Other processes could potentially share the same memory. |
|||
This counter displays the system time (STime), measured in jiffies, that this process has scheduled in kernel mode. A jiffy corresponds to a unit of CPU time and is used as a base of measurement. One second comprises 100 jiffies. |
|||
This counter displays the number of threads that are currently grouped with a task. A negative value (-1) indicates that this counter is currently not available. This situation happens when thread statistics (which include all performance counters in the Thread object as well as the Thread Count counter in the Process object) are turned off because the system total processes and threads exceed the default threshold value. |
|||
This counter displays the total CPU time in jiffies that the task used in user mode and kernel mode since the task started. |
|||
This counter displays the time, measured in jiffies, that a task has scheduled in user mode. |
|||
This counter displays the virtual memory usage of the heap for the task in KB. |
|||
This counter displays the virtual memory (Vm) resident set size (RSS) that is currently in physical memory in KB. This reading includes the code, data, and stack. |
|||
This counter displays the total virtual memory usage for a task in KB. This reading includes all code, data, shared libraries, and pages that have been swapped out. Virtual Image = swapped size + resident size |
|||
This counter displays the channel (system call) in which the process is waiting. |
This counter displays the processors share of the elapsed central processing unit (CPU) time, excluding idle time, since the last update. This share is expressed as a percentage of total CPU time. |
|
This counter displays the percentage of time that the processor is in the idle state and does not have an outstanding disk input and output (I/O) request. |
|
This counter represents the percentage of time that the processor is in the idle state while the system had an outstanding disk I/O request. |
|
This counter represents the percentage of time that the processor spends executing the interrupt request that is assigned to devices, including the time that the processor spends sending a signal to the computer. |
|
This counter displays the percentage of time that the processor spends executing at the user level with nice priority. |
|
This counter represents the percentage of time that the processor spends executing the soft IRQ and deferring task switching to get better CPU performance. |
|
This counter displays the percentage of time that the processor is executing processes at the system (kernel) level. |
|
This counter displays the percentage of time that the processor is executing normal processes at the user (application) level. |
The System object provides information about file descriptors on your system.
The number of file descriptors that are currently in use in the system. |
|
The number of allocated file descriptors on the system that are freed. |
|
The number of input and output (I/O) operations on all disk partitions per second on this server. If you experience a system performance issue, use the information in this counter to measure the impact of the aggregate I/O operations on this server. |
|
The number of read requests merged per second that are queued to all devices on this server. |
|
The number of write requests merged per second that are queued to all devices on this server. |
|
The number of read requests per second that are issued to all devices on this server. |
|
The number of write requests per second that are issued to all devices on this server. |
|
The number of sectors read per second from all devices on this server. |
|
The number of sectors written per second to all devices on this server. |
|
The number of KBytes read per second from all devices on this server. |
|
The number of KBytes written per second to all devices on this server. |
|
The average size in sectors of the requests that are issued to all devices on this server. |
|
The average queue length of the requests that are issued to all devices on this server. |
|
The average time in milliseconds for I/O requests that are issued to all devices to be served. This reading includes the time spent by the requests in queue and the time spent servicing the requests. |
|
The average service time in milliseconds for I/O requests that are issued to all devices on this server. |
|
The percentage of CPU time during which I/O requests are issued to the device (bandwidth utilization for the device) on this server. |
|
The maximum number of file descriptors that are allowed on the system. |
|
The total time in jiffies that the system has been up and running. |
|
The TCP object provides information on the TCP statistics on your system.
This counter displays the number of times that the TCP connections make a direct transition to the SYN-SENT state from the CLOSED state. |
|
This counter displays the number of times that the TCP connections make a direct transition to the CLOSED state from either the SYN-RCVD state or the SYN-RCVD state. The counter also displays the number of times TCP connections make a direct transition to the LISTEN state from the SYS-RCVD state. |
|
This counter displays the number of TCP connections with a current state of ESTABLISHED or CLOSE- WAIT. |
|
This counter displays the number of times that the TCP connections make a direct transition to the CLOSED state from the ESTABLISHED state or the CLOSE-WAIT state. |
|
This counter displays the total number of segments that are received, including those that are received in error. This count only includes segments that are received on currently established connections. |
|
This counter displays the total number of segments that are sent and the total number of segments that are received. |
|
This counter displays the total number of segments that are sent. This count only includes segments that are sent on currently established connections, but excludes retransmitted octets. |
|
This counter displays the number of times that TCP connections make a direct transition to the SYN-RCVD state from the LISTEN state. |
|
This counter displays the total number of segments that are retransmitted because the segment contains one or more previously transmitted octets. |
The Thread object provides a list of running threads on your system.
This counter displays the threads share of the elapsed CPU time since the last update. This counter expresses the share as a percentage of the total CPU time. |
|
The AXL Web Service object provides information about the AXL Web Service running on your system. The following table contains information about the AXL Web Service counters.
This counter represents the number of times Administrative XML Layer (AXL) throttling has been engaged since the last restart of the Cisco AXL Web Service. Throttling occurs when the AXL service receives more change requests than it is able to process. |
|
This counter represents whether Administrative XML Layer (AXL) throttling is currently active (throttling is engaged). A value of 1 in this counter indicates that throttling is currently engaged, which means that any application attempting to send a write request to Cisco Unified Communications Manager through AXL will be denied due to AXL throttling. Read requests will continue to be allowed and processed while AXL throttling is engaged. A value of zero indicates that throttling is not occurring at this time and all read and write requests will be processed. |
The Ramfs object provides information about the ram file system. The following table contains information on the Ramfs counters.
This counter represents the total number of files in the ram-based file system (ramfs). |
|
This counter represents the amount of free data blocks in the ram-based file system (ramfs). A block is a uniformly sized unit of data storage for a filesystem. The block size specifies the size that the file system will use to read and write data. On the Cisco Unified Communications Manager system, the block size is 4096 bytes. |
|
This counter represents the amount of used data blocks in the ram-based filesystem (ramfs). A block is a uniformly sized unit of data storage for a file system. The block size specifies the size that the file system will use to read and write data. On the Cisco Unified Communications Manager system, the block size is 4096 bytes. |
The Cisco Analog Access object provides information about registered Cisco Analog Access gateways. The following table contains information about Cisco Analog Access counters.
This counter represents the total number of times that Cisco Unified Communications Manager attempts a call through the analog access gateway when all ports were busy. |
|
This counter represents the number of ports that are currently in use (active). A port appears active when a call is in progress on that port. |
|
This counter represents the number of ports that are currently out of service. Counter applies only to loop-start and ground-start trunks. |
The Cisco Annunciator Device object provides information about registered Cisco annunciator devices. The following table contains information about Cisco Annunciator counters.
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate an annunciator resource from an annunciator device and failed; for example, because all resources were already in use. |
|
This counter represents the total number of annunciator resources that are currently active (in use) for an annunciator device. |
|
This counter represents the total number of resources that are not active and are still available to be used at the current time for the annunciator device. |
|
This counter represents the total number of annunciator resources that are configured for an annunciator device. |
The Cisco Call Restriction object provides information about the number of failures that result due to logical partitioning policy restrictions. The following table contains information about Cisco Call Restriction counters.
This counter represents the number of attempts that failed to add a participant to an Ad Hoc Conference because the call path between the geolocation of the devices already in conference and the device being invited to the conference was restricted due to a logical partition policy. |
|
This counter represents the number of basic calls that have failed because of logical partition policy restrictions between the geolocations of the called and calling parties. A basic call is any call that does not utilize supplementary services such as transfer, forward, and so on. |
|
This counter represents the number of attempts to forward an incoming call which failed because of a logical partition policy restriction between the geolocations of the two parties involved. |
|
This counter represents the total number of call attempts that have failed because of a restriction of calls between geolocations of the calling and called parties. This includes the number of failures for Transfer, Ad Hoc Conference, Meet-Me Conference, PickUp, Call Park, Shared Lines and Basic Calls. |
|
This counter represents the number of attempts that failed to add a participant to a Meet-Me conference because the call path between the geolocation of the devices already in conference and the device attempting to join the conference was restricted due to a logical partition policy. |
|
This counter represents the number of calls that have failed because of a restriction between the geolocations of the called or connected parties after the initial policy check. |
|
This counter represents the number of attempts to perform a Call Park operation that failed because the device that was attempting to retrieve the call had a logical partition policy restriction with the geolocation of the parked party. |
|
This counter represents the number of attempts to perform a PickUp operation that failed because the device on which the pickup was being attempted had a logical partition policy restriction with the geolocation of the calling device. |
|
This counter represents the number of attempts to use a shared line which failed because the caller or callee has a logical partition policy restriction with the geolocation of the devices having the shared lines. |
|
This counter represents the number of call transfer attempts that failed due to restriction of calls between the geolocation of the transferred party and the transferred destination. |
The Cisco CallManager object provides information about calls, applications, and devices that are registered with the Cisco Unified Communications Manager. The following table contains information about Cisco CallManager counters.
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate an annunciator resource from those that are registered to a Cisco Unified Communications Manager when none were available. |
|
This counter represents the total number of annunciator resources that are currently in use on all annunciator devices that are registered with a Cisco Unified Communications Manager. |
|
This counter represents the total number of annunciator resources that are not active and are currently available. |
|
This counter represents the total number of annunciator resources that are provided by all annunciator devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the number of authenticated calls that are currently active (in use) on Cisco Unified Communications Manager. An authenticated call designates one in which all the endpoints that are participating in the call are authenticated. An authenticated phone uses the Transport Layer Security (TLS) authenticated Skinny protocol signaling with Cisco Unified Communications Manager. |
|
This counter represents the number of authenticated calls that connected and subsequently disconnected through Cisco Unified Communications Manager. An authenticated call designates one in which all the endpoints that are participating in the call are authenticated. An authenticated phone uses the TLS authenticated Skinny protocol signaling with Cisco Unified Communications Manager. |
|
This counter represents the number of partially registered, authenticated SIP phones. |
|
This counter represents the total number of authenticated phones that are registered to Cisco Unified Communications Manager. An authenticated phone uses the TLS authenticated Skinny protocol signaling with Cisco Unified Communications Manager. |
|
This counter represents the number of BRI voice channels that are currently in an active call on this Cisco Unified Communications Manager. |
|
This counter represents the number of BRI spans that are currently available for use. |
|
This counter represents the heartbeat of Cisco Unified Communications Manager. This incremental count indicates that Cisco Unified Communications Manager is up and running. If the count does not increment, that indicates that Cisco Unified Communications Manager is down. |
|
This counter represents the number of voice or video streaming connections that are currently in use (active); in other words, the number of calls that actually have a voice path that is connected on Cisco Unified Communications Manager. |
|
This counter represents the total number of attempted calls. An attempted call occurs any time that a phone goes off hook and back on hook, regardless of whether any digits were dialed, or whether it connected to a destination. The system considers some call attempts during feature operations (such as transfer and conference) to be attempted calls. |
|
This counter represents the number of calls that were actually connected (a voice path or video stream was established) through Cisco Unified Communications Manager. This number increases when the call terminates. |
|
This counter represents the number of voice or video calls that are currently in progress on Cisco Unified Communications Manager, including all active calls. When a phone that is registered with Skinny Client Control Protocol (SCCP) goes off hook, the CallsInProgress progress counter increments. until it goes back on hook. For Cisco Unified IP Phones 7902, 7905, 7912, 7940, and 7960 that register with SIP, the CallsInProgress counter increments when the dial softkey is pressed. For all other phones that are running SIP, the CallsInProgress counter increments when the first digit is pressed. When all voice or video calls that are in progress are connected, the number of CallsInProgress represents the number of CallsActive. The counter decreases by one when a phone goes back on hook. |
|
This counter represents the total number of media termination point (MTP) resource requests that have been denied due to throttling (a resource from this MTP was not allocated because, as specified by the Cisco CallManager service parameter, MTP and Transcoder Resource Throttling Percentage, the MTP was being utilized beyond the configured throttle percentage). This counter increments each time a request for an MTP on this Cisco Unified Communications Manager node is requested and denied due to MTP throttling and reflects a running total since the start of the Cisco CallManager Service. |
|
This counter represents the total number of transcoder resource requests that have been denied due to throttling (a resource from this transcoder was not allocated because, as specified by the Cisco CallManager service parameter MTP and Transcoder Resource Throttling Percentage, the transcoder was being utilized beyond the configured throttle percentage). This counter increments each time a request for a transcoder on this Cisco Unified Communications Manager node is requested and denied due to transcoder throttling and reflects a running total since the start of the Cisco CallManager Service |
|
This counter represents the number of encrypted calls that are currently active (in use) on this Cisco Unified Communications Manager. An encrypted call represents one in which all the endpoints that are participating in the call are encrypted. |
|
This counter represents the number of encrypted calls that were connected and subsequently disconnected through this Cisco Unified Communications Manager. An encrypted call represents one in which all the endpoints that are participating in the call are encrypted. |
|
This counter represents the number of partially registered, encrypted SIP phones. |
|
This counter represents the total number of encrypted phones that are registered on this Cisco Unified Communications Manager. |
|
This counter represents the number of FXO ports that are currently in use (active) on a Cisco Unified Communications Manager. |
|
This counter represents the number of FXO ports that are currently available for use in the system. |
|
This counter represents the number of FXS ports that are currently in use (active) on a Cisco Unified Communications Manager. |
|
This counter represents the number of FXS ports that are currently available for use in the system. |
|
This counter represents the number of hunt lists that are currently in service on Cisco Unified Communications Manager. |
|
This counter represents the total number of hardware conference resources that are provided by all hardware conference bridge devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of conferences that used a hardware conference bridge (hardware-based conference devices such as Cisco Catalyst 6000, Cisco Catalyst 4000, Cisco VG200, Cisco series 26xx and 36xx) that is allocated from Cisco Unified Communications Manager and that have completed, which means that the conference bridge has been allocated and released. A conference activates when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate a hardware conference resource from those that are registered to a Cisco Unified Communications Manager when none was available. |
|
This counter represents the total number of conference resources that are in use on all hardware conference devices (such as Cisco Catalyst 6000, Catalyst 4000, Cisco VG200, Cisco series 26xx and 36xx) that are registered with Cisco Unified Communications Manager. System considers conference to be active when one or more calls are connected to a bridge. |
|
This counter represents the number of hardware conference resources that are not in use and that are available to be allocated on all hardware conference devices (such as Cisco Catalyst 6000, Cisco Catalyst 4000, Cisco VG200, Cisco series 26xx and 36xx) that are allocated fromCisco Unified Communications Manager and that have been completed, which means that the conference bridge has been allocated and released. A conference activates when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the number of active conferences on all hardware conference devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the current initialization state of Cisco Unified Communications Manager. Cisco Unified Communications Manager includes the following initialization state values: 1-Database, 2-Regions, 3-Locations, 4-QoS Policy, 5-Time Of Day, 6-AAR Neighborhoods, 7-Digit Analysis, 8-Route Plan, 9-Call Control, 10-RSVP Session Manager, 11-Supplementary Services, 12-Directory, 13-SDL Link, 14-Device, 100-Initialization Complete. Not all states display when this counter is used. This display does not indicate that an error occurred; this display simply indicates that the states initialized and completed within the refresh period of the performance monitor. |
|
This counter represents the total number of times that a call through Locations failed due to the lack of bandwidth. |
|
This counter represents the total number of active conferences on all Cisco TelePresence MCU conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of conferences that used a Cisco TelePresence MCU conference bridge allocated from Cisco Unified Communications Manager and completed, implying that the conference bridge was allocated and released. A conference is activated when the first call is connected to the bridge. The conference is completed when the last call is disconnected from the bridge. |
|
This counter represents the total number of times Cisco Unified Communications Manager attempted to create HTTP connections to Cisco TelePresence MCU conference bridge device, and failed due to connection errors on the Cisco TelePresence MCU conference bridge side. |
|
This counter represents the total number of times Cisco Unified Communications Manager received a non 200 OK HTTP Response from Cisco TelePresence MCU conference bridge, for any HTTP query sent. |
|
This counter represents the total number of times Cisco Unified Communications Manager attempted to allocate a conference resource from Cisco TelePresence MCU conference bridge device and failed. For example, the attempt to allocate a conference resource fails, if all the resources are already in use. |
|
This counter represents the total number of multicast Music On Hold (MOH) resources that are currently in use (active) on all MOH servers that are registered with a Cisco Unified Communications Manager. |
|
This counter represents the total number of active multicast MOH connections that are not being used on all MOH servers that are registered with a Cisco Unified Communications Manager. |
|
This counter represents the total number of times that the Media Resource Manager attempted to allocate an MOH resource when all available resources on all MOH servers that are registered with a Cisco Unified Communications Manager were already active. |
|
This counter represents the total number of multicast MOH resources or connections that are provided by all MOH servers that are currently registered with a Cisco Unified Communications Manager. |
|
This counter represents the total number of unicast MOH resources or streams that are provided by all MOH servers that are currently registered with Cisco Unified Communications Manager. Each MOH unicast resource uses one stream. |
|
This counter represents the total number of unicast MOH resources that are currently in use (active) on all MOH servers that are registered with Cisco Unified Communications Manager. Each MOH unicast resource uses one stream. |
|
This counter represents the total number of unicast MOH resources that are currently available on all MOH servers that are registered with Cisco Unified Communications Manager. Each MOH unicast resource uses one stream. |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted but failed to allocate a media termination point (MTP) resource from one MTP device that is registered with Cisco Unified Communications Manager. This also means that no transcoders were available to act as MTPs. |
|
This counter represents the total number of MTP resources that are currently in use (active) on all MTP devices that are registered with a Cisco Unified Communications Manager. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call. |
|
This counter represents the total number of MTP resources that are not in use and are available to be allocated on all MTP devices that are registered with Cisco Unified Communications Manager. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call. |
|
This counter represents the total number of MTP resources that are provided by all MTP devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of MTP resource requests that have been denied due to throttling (a resource from this MTP was not allocated because, as specified by the Cisco CallManager service parameter MTP and Transcoder Resource Throttling Percentage, the MTP was being utilized beyond the configured throttle percentage). This counter increments each time a resource is requested from this MTP and is denied due to throttling. This counter reflects a running total since the MTP device registered with the Cisco CallManager Service. |
|
This counter represents the number of partially registered phones that are running SIP. |
|
This counter represents the number of PRI voice channels that are in an active call on a Cisco Unified Communications Manager. |
|
This counter represents the number of PRI spans that are currently available for use. |
|
This counter represents the number of registered Cisco analog access gateways that are registered with system. The count does not include the number of Cisco analog access ports. |
|
This counter represents the number of Cisco hardware IP phones (for example, Cisco Unified IP Phones 7960, 7940, 7910, and so on.) that are currently registered in the system. |
|
This counter represents the number of MGCP gateways that are currently registered in the system. |
|
This counter represents the number of station devices other than Cisco hardware IP phones that are currently registered in the system (for example, Cisco IP SoftPhone, CTI port, CTI route point, Cisco voicemail port). |
|
This counter represents the number of authentication challenges for incoming SIP requests that the Cisco Unified Communications Manager server issued to phones that are running SIP. An authentication challenge occurs when a phone that is running SIP with Digest Authentication enabled sends a SIP line request to Cisco Unified Communications Manager. |
|
This counter represents the number of authentication challenge failures for incoming SIP requests from SIP phones to the Cisco Unified Communications Manager server. An authentication failure occurs when a SIP phone with Digest Authentication enabled sends a SIP line request with bad credentials to Cisco Unified Communications Manager. |
|
This counter represents the number of application-level authorization checks for incoming SIP requests that Cisco Unified Communications Manager has issued to SIP trunks. An application-level authorization check occurs when Cisco Unified Communications Manager compares an incoming SIP request to the application-level settings on the SIP Trunk Security Profile Configuration window in Cisco Unified Communications Manager Administration. |
|
This counter represents the number of application-level authorization failures for incoming SIP requests that have occurred on Cisco Unified Communications Manager SIP trunks. An application-level authorization failure occurs when Cisco Unified Communications Manager compares an incoming SIP request to the application-level authorization settings on the SIP Trunk Security Profile Configuration window in Cisco Unified Communications Manager Administration and finds that authorization for one or more of the SIP features on that window is not allowed. |
|
This counter represents the number of authentication challenges for incoming SIP requests that Cisco Unified Communications Manager issued to SIP trunks. An authentication challenge occurs when a SIP trunk with Digest Authentication enabled sends a SIP request to Cisco Unified Communications Manager. |
|
This counter represents the number of authentication challenge failures that occurred for incoming SIP requests from SIP trunks to Cisco Unified Communications Manager. An authentication failure occurs when a SIP trunk with Digest Authentication enabled sends a SIP request with bad credentials to Cisco Unified Communications Manager. |
|
This counter represents the number of active conferences on all software conference devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of conferences that used a software conference bridge that was allocated from a Cisco Unified Communications Manager and that have been completed, which means that the conference bridge has been allocated and released. A conference activates when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate a software conference resource from those that are registered to Cisco Unified Communications Manager when none were available. Counter includes failed attempts to add a new participant to an existing conference. |
|
This counter represents the total number of conference resources that are in use on all software conference devices that are registered with Cisco Unified Communications Manager. The system considers a conference to be active when one or more calls connect to a bridge. One resource equals one stream. |
|
This counter represents the number of new software-based conferences that can be started at the same time, for Cisco Unified Communications Manager. You must have a minimum of three streams available for each new conference. One resource equals one stream. |
|
This counter represents the total number of software conference resources that are provided by all software conference bridge devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of server-originated calls and attempted calls to the Unity message waiting indicator (MWI). |
|
This counter represents the number of T1 CAS voice channels that are in an active call on a Cisco Unified Communications Manager. |
|
This counter represents the number of T1 CAS spans that are currently available for use. |
|
This counter represents the number of SIP trunks that are configured and connected through Transport Layer Security (TLS). |
|
This counter represents the number of WSM Connectors that is configured and connected to Motorola WSM through Transport Layer Security (TLS). |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate a transcoder resource from a transcoder device that is registered to a Cisco Unified Communications Manager when none was available. |
|
This counter represents the total number of transcoders that are in use on all transcoder devices that are registered with Cisco Unified Communications Manager. A transcoder in use represents one transcoder resource that has been allocated for use in a call. Each transcoder resource uses two streams. |
|
This counter represents the total number of transcoders that are not in use and that are available to be allocated on all transcoder devices that are registered with Cisco Unified Communications Manager. Each transcoder resource uses two streams. |
|
This counter represents the total number of transcoder resources that are provided by all transcoder devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of active video conferences on all video conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of new video conferences on all video conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of video conferences that used a video conference bridge that are allocated from Cisco Unified Communications Manager and that have been completed, which means that the conference bridge has been allocated and released. A conference activates when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the total number of video conferences that are supported on all video conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate a video conference resource from those that are registered to Cisco Unified Communications Manager when none was available. |
|
This counter represents the total number of failed new video conference requests. A conference request can fail because, for example, the configured number of conferences is already in use. |
|
This counter represents the total number of video conference resources that are currently in use on all video conference devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of video conference resources that are not active and are currently available. |
|
This counter represents the total number of video conference resources that are provided by all video conference bridge devices that are currently registered with Cisco Unified Communications Manager. |
|
This counter represents the number of active video calls with active video streaming connections on all video conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the number of video calls that were actually connected with video streams and then released. |
|
This counter represents the total number of times that Cisco Unified Communications Manager attempted to allocate a video-streaming resource from one of the video conference bridge devices that is registered to Cisco Unified Communications Manager when none was available. |
|
This counter represents the total number of transcoder resource requests that have been denied due to throttling (a resource from this transcoder was not allocated because, as specified by the Cisco CallManager service parameter MTP and Transcoder Resource Throttling Percentage, the transcoder was being utilized beyond the configured throttle percentage). This counter increments each time a resource is requested from this transcoder and is denied due to throttling. This counter reflects a running total since the transcoder device registered with the Cisco CallManager Service. |
The Cisco CallManager System Performance object provides system performance information about Cisco Unified Communications Manager. The following table contains information about Cisco CallManager system performance counters.
This counter represents the current average expected delay before any incoming message gets handled. |
|
This counter represents the total number of calls that were rejected since the start of Cisco CallManager service due to Intercluster Trunk (ICT) call throttling. When the threshold limit of 140 calls per 5 seconds is met, the ICT will start throttling (rejecting) new calls. One cause for ICT call throttling occurs when calls across an ICT enter a route loop condition. |
|
This counter represents a generic counter that is used for call-throttling purpose. |
|
This counter indicates whether Cisco Unified Communications Manager has entered or exited a Code state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry). |
|
This counter indicates whether Cisco Unified Communications Manager has entered or exited a Code Yellow state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry). |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
This counter indicates the number of high-priority signals in the Cisco Unified Communications Manager queue. High-priority signals include timeout events, internal Cisco Unified Communications Manager keepalives, certain gatekeeper events, and internal process creation, among other events. A large number of high-priority events will cause degraded performance on Cisco Unified Communications Manager and result in slow call connection or loss of dial tone. Use this counter in conjunction with the QueueSignalsProcessed 1-High counter to determine the processing delay on Cisco Unified Communications Manager. |
|
This counter indicates the number of normal-priority signals in the Cisco Unified Communications Manager queue. Normal-priority signals include call-processing functions, key presses, on-hook and off-hook notifications, among other events. A large number of normal-priority events will cause degraded performance on Cisco Unified Communications Manager, sometimes resulting in delayed dial tone, slow call connection, or loss of dial tone. Use this counter in conjunction with the QueueSignalsProcessed 2-Normal counter to determine the call-processing delay on Cisco Unified Communications Manager. Remember that high-priority signals must complete before normal-priority signals begin to process, so check the high-priority counters as well to get an accurate picture of the potential delay. |
|
This counter indicates the number of low-priority signals in the Cisco Unified Communications Manager queue. Low-priority signals include station device registration (except the initial station registration request message), among other events. A large number of signals in this queue could result in delayed device registration, among other events. |
|
This counter indicates the number of lowest priority signals in the Cisco Unified Communications Manager queue. Lowest priority signals include the initial station registration request message during device registration, among other events. A large number of signals in this queue could result in delayed device registration, among other events. |
|
This counter indicates the number of high-priority signals that Cisco Unified Communications Manager processes for each 1-second interval. Use this counter in conjunction with the QueueSignalsPresent 1-High counter to determine the processing delay on this queue. |
|
This counter indicates the number of normal-priority signals that Cisco Unified Communications Manager processes for each 1-second interval. Use this counter in conjunction with the QueueSignalsPresent 2-Normal counter to determine the processing delay on this queue. Remember that high-priority signals get processed before normal-priority signals. |
|
This counter indicates the number of low-priority signals that Cisco Unified Communications Manager processes for each 1-second interval. Use this counter in conjunction with the QueueSignalsPresent 3-Low counter to determine the processing delay on this queue. The number of signals processed gives an indication of how much device registration activity is being processed in this time interval. |
|
This counter indicates the number of lowest priority signals that Cisco Unified Communications Manager processes for each 1-second interval. Use this counter in conjunction with the QueueSignalsPresent 4-Lowest counter to determine the processing delay on this queue. The number of signals that are processed gives an indication of how many devices began the Cisco Unified Communications Manager registration process in this time interval. |
|
This counter provides a sum total of all queue signals that Cisco Unified Communications Manager processes for each 1-second period for all queue levels: high, normal, low, and lowest. |
|
This counter represents the total number of Skinny devices that are being throttled. A Skinny device gets throttled (asked to shut down and reregister) when the total number of events that the Skinny device generated exceeds the configured maximum threshold value (default value specifies 2000 events) within a 5-second interval. |
|
This counter indicates how many samples, out of the configured sample size, have non-zero averageExpectedDelay values. This counter resets when any sample has an averageExpectedDelay value of zero. This process repeats for each batch of samples. A batch represents the configured sample size. |
|
This counter indicates the number of times that Cisco Unified Communications Manager call processing enters the code yellow state. This counter remains cumulative from the start of the Cisco Unified Communications Manager process. |
The Cisco CTI Manager object provides information about Cisco CTI Manager. The following table contains information about Cisco CTIManager counters.
This counter represents the total number of active Cisco Unified Communications Manager links. CTI Manager maintains links to all active servers in a cluster, if applicable. |
|
This counter represents the total number of CTI clients that are currently connected to the CTIManager. This counter increases by one when new connection is established and decreases by one when a connection is released. The CTIManager service parameter MaxCTIConnections determines the maximum number of active connections. |
|
This counter represents the total number of devices that are configured in Cisco Unified Communications Manager that CTI applications control and/or monitor. Devices include hardware IP phones, CTI ports, CTI route points, and so on. |
|
This counter represents the total number of lines that are configured in Cisco Unified Communications Manager that control and/or monitor CTI applications. |
|
This counter represents the version number of the Quick Buffer Encoding (QBE) interface that the CTIManager uses. |
The Cisco Dual-Mode Mobility object provides information about the dual-mode mobility application on Cisco Unified Communications Manager. The following table contains information about Cisco Dual-Mode Mobility counters.
This counter represents the number of calls that are placed or received on dual-mode phones that are anchored in Cisco Unified Communications Manager. The counter increments when a call is received from or placed to a dual-mode phone. The counter increments twice if a dual-mode phone calls another dual-mode phone. |
|
This counter represents the number of Dual-mode Mobile Station (DMMS) subscribers that are registered in the wireless LAN (WLAN). |
|
This counter represents the number of failed follow-me operations. |
|
This counter represents the number of follow-me operations that Cisco Unified Communications Manager attempted. The counter increments when a SIP 302 - Moved Temporarily message is received from the Wireless Service Manager (WSM) and Cisco Unified Communications Manager redirects the call to the DMMS in WLAN. |
|
This counter represents the number of follow-me operations that were successfully completed. The counter increments when the DMMS in WLAN answers the call and the media (voice path) is successfully established with the calling device. |
|
This counter represents the number of follow-me operations that are currently in progress. The counter increments when a follow-me is attempted, and it decrements when the follow-me operation is aborted or completed. |
|
This counter represents the number of H1 hand-out operations that dual-mode phones attempt. The counter increments when Cisco Unified Communications Manager processes a call to the H1 number from a DMMS. |
|
This counter represents the number of successfully completed H1 hand-out operations The counter increments when the DMMS in WLAN successfully reestablishes a media (voice path). |
|
This counter represents the number of successfully completed H2 hand-out operations. The counter increments when the DMMS in WLAN successfully reestablishes a media (voice path). |
|
This counter represents the number of H2 hand-out operations that dual-mode phones attempt. The counter increments when Cisco Unified Communications Manager receives a call to the H2 number from a DMMS. |
|
This counter represents the number of hand-in operations that failed. |
|
This counter represents the number of hand-in operations that dual-mode phones attempt. |
|
This counter represents the number of successfully completed hand-in operations. The counter increments when the DMMS in WLAN successfully reestablishes a media (voice path). |
|
This counter represents the number of hand-in operations that are currently in progress. The counter increments when a hand-in is attempted, and the counter decrements when the hand-in is aborted or completed. |
|
This counter represents the number of hand-out operations that failed. |
|
This counter represents the number of H1 and H2 hand-out operations that are currently in progress. The counter increments when a H1 or H2 hand-out is attempted, and it decrements when the hand-out is aborted or completed. |
The Cisco Extension Mobility object provides information about the extension mobility application. The following table contains information about Cisco Extension Mobility counters.
This counter represents the total number of HTTP requests that the extension mobility application handled since the last restart of the Cisco CallManager service. A typical login would constitute two HTTP requests: one to query the initial login state of the device and another to log in the user on a device. Similarly, a typical logout also results in two HTTP requests. |
|
This counter represents the number of HTTP requests that the extension mobility application currently is handling. A typical login would constitute two HTTP requests: one to query the initial login state of the device and another to log in the user on a device. Similarly, a typical logout also results in two HTTP requests. |
|
This counter represents the total number of Login/Logout Requests that failed due to throttling. |
|
This counter represents the total number of successful login requests that were completed through EM Service. |
|
This counter represents the total number of successful logout requests that were completed through EM Service |
|
This counter represents the total number of Login and Logout requests that were attempted through this EM Service. This number includes both successful and unsuccessful attempts. |
The Cisco Gatekeeper object provides information about registered Cisco gatekeeper devices. The following table contains information about Cisco gatekeeper device counters.
This counter represents the total number of RAS Admission Confirm messages that are received from the configured gatekeeper and its alternate gatekeepers. |
|
This counter represents the total number of RAS Admission Request messages that are attempted by using the configured gatekeeper and its alternate gatekeepers. |
|
This counter represents the number of retries due to loss or delay of all RAS acknowledgement messages on the configured gatekeeper and its alternate gatekeepers. |
|
This counter represents the total number of video-stream requests to the configured gatekeeper or its alternate gatekeepers that failed, most likely due to lack of bandwidth. |
The Cisco H.323 object provides information about registered Cisco H.323 devices. The following table contains information about Cisco H.323 device counters.
This counter represents the number of streaming connections that are currently active (in use) on the configured H.323 device; in other words, the number of calls that actually have a voice path that is connected. |
|
This counter represents the total number of calls that have been attempted on a device, including both successful and unsuccessful call attempts. |
|
This counter represents the total number of successful calls that were made from a device. |
|
This counter represents the number of calls that are currently in progress on a device. |
|
This counter represents the total number of calls rejected due to Intercluster Trunk (ICT) call throttling since the start of the Cisco CallManager service. When the system reaches a threshold limit of 140 calls per 5 seconds, ICT will start throttling (rejecting) new calls. One cause for ICT call throttling occurs when calls across an ICT enter a route loop condition. |
|
This counter represents the number of video calls with video streaming connections that are currently active (in use) on all H.323 trunks that are registered with a Cisco Unified Communications Manager; in other words, the number of calls that actually have video-streaming connections on a Cisco Unified Communications Manager. |
|
This counter represents the number of video calls that were actually connected with video streams for all H.323 trunks that were registered with a Cisco Unified Communications Manager. This number increases when the call terminates. |
The Cisco Hunt Lists object provides information about the hunt lists that are defined in Cisco Unified Communications Manager Administration. The following table contains information about Cisco hunt list counters.
This counter represents the number of abandoned calls that occurred through a hunt list. An abandoned call represents one in which a caller hangs up before the call is answered. |
|
This counter represents the number of calls that are currently active (in use) that occurred through a hunt list. An active call represents one that gets distributed and answered, and to which a voice path connects. |
|
This counter represents the number of times that calls through a hunt list were attempted when all members of the line and/or route groups were busy. |
|
This counter represents the number of calls that are currently in progress through a hunt list. A call in progress represents one that the call distributor is attempting to extend to a member of a line or route group and that has not yet been answered. Examples of a hunt list member include a line, a station device, a trunk device, or a port/channel of a trunk device. |
|
This counter represents the total number of calls through a hunt list that rang but that called parties did not answer. |
|
This counter specifies whether the particular hunt list is currently in service. A value of 0 indicates that the hunt list is out of service; a value of 1 indicates that the hunt list is in service. Reasons that a hunt list could be out of service include the hunt list is not running on a primary Cisco Unified Communications Manager based on its Cisco Unified Communications Manager Group or the hunt list has been disabled in Cisco Unified Communications Manager Administration. |
|
This counter represents the total number of available or idle members of line and route groups that belong to an in-service hunt list. An available member currently handles a call and will accept a new call. An idle member does not handle any call and will accept a new call. A hunt list member can comprise a route group, line group, or a combination. A member of a line group represents a directory number of a line on an IP phone or a voice-mail port. A member of a route group represents a station gateway, a trunk gateway, or port/channel of a trunk gateway. |
The Cisco HW Conference Bridge Device object provides information about registered Cisco hardware conference bridge devices. The following table contains information about Cisco hardware conference bridge device counters.
This counter represents the number of conferences that are currently active (in use) on a HW conference bridge device. One resource represents one stream. |
|
This counter represents the total number of conferences that have been allocated and released on a HW conference device. A conference starts when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the total number of times that an attempt was made to allocate a conference resource from a HW conference device and failed, for example, because all resources were already in use. |
|
This counter represents the number of resources that are currently in use (active) for this HW conference device. One resource represents one stream. |
|
This counter represents the total number of resources that are not active and are still available to be used now for a HW conference device. One resource represents one stream. |
|
This counter represents the total number of resources for a HW conference bridge device. This counter equals the sum of the counters ResourceAvailable and ResourceActive. One resource represents one stream. |
The Cisco IP Manager Assistant (IPMA) Service object provides information about the Cisco Unified Communications Manager Assistant application. The following table contains information on Cisco IPMA counters.
This counter represents the number of assistant consoles that are currently active. An active assistant console exists when an assistant is logged in from the assistant console desktop application. |
|
This counter represents the number of phone lines that the Cisco Unified Communications Manager Assistant application opened. An open phone line exists when the application assumes line control from CTI. |
|
This counter represents the current number of managers that the Cisco IPMA is servicing. |
|
This counter represents the total number of managers assistants that are currently using the Cisco Unified Communications Manager Assistant application. Each manager and each assistant constitute an active session; so, for one manager/assistant pair, this counter would reflect two sessions. |
The Cisco LBM service object provides information about LBM service that is defined in Cisco Unified Communications Manager. The following table contains information on Cisco LBM service counters.
This counter represents the state of Location Bandwidth Manager. Spoke state is represented by 0 and hub state with a value of 1. |
|
LocalHubNodesConnected |
This counter represents the number of local hub nodes connected. |
This counter represents the number of local spoke nodes connected. |
|
This counter represents the number of insecure remote hub nodes connected. |
|
RemoteHubNodesConnectedSecure |
This counter represents the number of secure remote hub nodes connected. |
The Cisco Lines object represents the number of Cisco lines (directory numbers) that can dial and connect to a device. Lines represent all directory numbers that terminate on an endpoint. The directory number that is assigned to it identifies the line. The Cisco Lines object does not include directory numbers that include wildcards such as a pattern for a Digital or Analog Access gateway.
The Active counter represents the state of the line, either active or not active. A zero indicates that the line is not in use. When the number is greater than zero, this indicates that the line is active, and the number represents the number of calls that are currently in progress on that line. If more than one call is active, this indicates that the call is on hold either because of being placed on hold specifically (user hold) or because of a network hold operation (for example, a transfer is in progress, and it is on transfer hold). This applies to all directory numbers that are assigned to any device.
The Cisco Location LBM object provides information about locations that are defined in Cisco Unified Communications Manager clusters. The following table contains information on Cisco location counters.
This counter represents the current audio bandwidth in a location or a link between two locations. A value of 0 indicates that no audio bandwidth is available. |
|
This counter represents the maximum audio bandwidth that is available in a location or a link between two locations. A value of 0 indicates that no audio bandwidth is available. |
|
BandwidthOversubscription |
This represents the current oversubscribed audio bandwidth in a location or link between two locations. A value of zero indicates no bandwidth oversubscription. |
This counter represents the number of calls that are currently in progress on a particular Cisco Location Bandwidth Manager. |
|
This represents the total number of failed immersive video call bandwidth reservations associated with a location or a link between two locations due to lack of immersive video bandwidth. |
|
ImmersiveVideoBandwidthAvailable |
This counter represents the maximum bandwidth that is available for video in a location or a link between two locations. A value of 0 indicates that no bandwidth is allocated for video. |
ImmersiveVideoBandwidthMaximum |
This counter represents the bandwidth that is currently available for video in a location or a link between two locations. A value of 0 indicates that no bandwidth is available. |
ImmersiveVideoBandwidthOversubscription |
This represents the current immersive video oversubscribed bandwidth in a location or link between two locations. A value of zero indicates no bandwidth oversubscription. |
This counter represents the total number of failed audio call bandwidth reservations associated with a given location or a link between two locations due to lack of audio bandwidth. |
|
This counter represents the bandwidth that is currently available for video in a location or a link between two locations. A value of 0 indicates that no bandwidth is available. |
|
This counter represents the maximum bandwidth that is available for video in a location and a link between two locations. A value of 0 indicates that no bandwidth is allocated for video. |
|
VideoOversubscription |
This represents the current video oversubscribed bandwidth amount in a location and a link between two locations. A value of zero indicates no bandwidth oversubscription. |
This counter represents the total number of failed video call bandwidth reservations associated with a given location or a link between two locations due to lack of video bandwidth. |
The Cisco Location RSVP object provides information about RSVP that is defined in Cisco Unified Communications Manager. The following table contains information on Cisco location RSVP counters.
This counter represents the number of RSVP reservation errors in the audio stream. |
|
This counter represents the number of connections with mandatory RSVP that are in progress. |
|
This counter represents the number of connections with optional RSVP that are in progress. |
|
This counter represents the number of total calls that failed due to a RSVP reservation failure. |
|
This counter represents the number of video calls that failed due to a RSVP reservation failure. |
|
This counter represents the number of RSVP reservation errors in the video stream |
The Cisco IP Voice Media Streaming Application object provides information about the registered MTPs, MOH servers, conference bridge servers, and annunciators. The following table contains information on Cisco IP Voice Media Streaming Application counters.
Note | One object exists for each Cisco Unified Communications Manager in the Cisco Unified Communications Manager group that is associated with the device pool that the annunciator device is configured to use. |
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco Unified Communications Manager connection was lost. |
|
For each Cisco Unified Communications Manager that is associated with an annunciator, this counter represents the current registration state to Cisco Unified Communications Manager; 0 indicates no registration to Cisco Unified Communications Manager; 1 indicates registration to the primary Cisco Unified Communications Manager; 2 indicates connection to the secondary Cisco Unified Communications Manager (connected to Cisco Unified Communications Manager but not registered until the primary Cisco Unified Communications Manager connection fails). |
|
This counter represents the total number of annunciator instances that have been started since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the number of actively playing (currently in use) announcements. |
|
This counter represents the total number of currently active simplex (one direction) streams for all connections. Each stream direction counts as one stream. One internal stream provides the audio input and another output stream to the endpoint device. |
|
This counter represents the remaining number of streams that are allocated for the annunciator device that are available for use. This counter starts as 2 multiplied by the number of configured connections (defined in the Cisco IP Voice Media Streaming App service parameter for the Annunciator, Call Count) and is reduced by one for each active stream that started. |
|
This counter represents the total number of simplex (one direction) streams that connected to the annunciator device since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the number of active (currently in use) conferences. |
|
This counter represents the total number of conferences that started since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco Unified Communications Manager connection was lost. |
|
For each Cisco Unified Communications Manager that is associated with a SW Conference Bridge, this counter represents the current registration state to Cisco Unified Communications Manager; 0 indicates no registration to Cisco Unified Communications Manager; 1 indicates registration to the primary Cisco Unified Communications Manager; 2 indicates connection to the secondary Cisco Unified Communications Manager (connected to Cisco Unified Communications Manager but not registered until the primary Cisco Unified Communications Manager connection fails). |
|
This counter represents the total number of currently active simplex (one direction) streams for all conferences. Each stream direction counts as one stream. In a three-party conference, the number of active streams equals 6. |
|
This counter represents the remaining number of streams that are allocated for the conference bridge that are available for use. This counter starts as 2 multiplied by the number of configured connections (defined in the Cisco IP Voice Media Streaming App service parameter for Conference Bridge, Call Count) and is reduced by one for each active stream started. |
|
This counter represents the total number of simplex (one direction) streams that connected to the conference bridge since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the number of active (currently in use) audio sources for this MOH server. Some of these audio sources may not be actively streaming audio data if no devices are listening. The exception exists for multicast audio sources, which will always be streaming audio. When an audio source is in use, even after the listener has disconnected, this counter will always have one input stream for each configured MOH codec. For unicast streams, the stream may exist in a suspended state where no audio data is received until a device connects to listen to the stream. Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if the default audio source is configured for multicast, G.711 mu-law and wideband codecs, then two streams get used (default audio source + G.711 mu-law and default audio source + wideband). |
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco Unified Communications Manager connection was lost. |
|
For each Cisco Unified Communications Manager that is associated with an MOH, this counter represents the current registration state to Cisco Unified Communications Manager; 0 indicates no registration to Cisco Unified Communications Manager; 1 indicates registration to the primary Cisco Unified Communications Manager; 2 indicates connection to the secondary Cisco Unified Communications Manager (connected to Cisco Unified Communications Manager but not registered until the primary Cisco Unified Communications Manager connection fails). |
|
This counter represents the total number of active (currently in use) simplex (one direction) streams for all connections. One output stream exists for each device that is listening to a unicast audio source, and one input stream exists for each active audio source, multiplied by the number of MOH codecs. When an audio source has been used once, it will always have one input stream for each configured MOH codec. For unicast streams, the stream may exist in a suspended state where no audio data is received until a device connects to listen to the stream. Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if the default audio source is configured for multicast, G.711 mu-law and wideband codecs, then two streams get used (default audio source + G.711 mu-law and default audio source + wideband). |
|
This counter represents the remaining number of streams that are allocated for the MOH device that are available for use. This counter starts as 408 plus the number of configured half-duplex unicast connections and is reduced by 1 for each active stream that started. The counter gets reduced by 2 for each multicast audio source, multiplied by the number of MOH codecs that are configured. The counter gets reduced by 1 for each unicast audio source, multiplied by the number of MOH codecs configured. |
|
This counter represents the total number of simplex (one direction) streams that have connected to the MOH server since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Streaming Application that a Cisco Unified Communications Manager connection was lost. |
|
For each Cisco Unified Communications Manager that is associated with an MTP, this counter represents the current registration state to Cisco Unified Communications Manager; 0 indicates no registration to Cisco Unified Communications Manager; 1 indicates registration to the primary Cisco Unified Communications Manager; 2 indicates connection to the secondary Cisco Unified Communications Manager (connected to Cisco Unified Communications Manager but not registered until the primary Cisco Unified Communications Manager connection fails). |
|
This counter represents the total number of MTP instances that have been started since the Cisco IP Voice Media Streaming Application service started. |
|
This counter represents the number of active (currently in use) instances of MTP. |
|
This counter represents the total number of currently active simplex (one direction) streams for all connections. Each stream direction counts as one stream. |
|
This counter represents the remaining number of streams that are allocated for the MTP device that are available for use. This counter starts as 2 multiplied by the number of configured connections (defined in the Cisco IP Voice Media Streaming App service parameter for MTP, Call Count) and is reduced by one for each active stream started. |
|
This counter represents the total number of simplex (one direction) streams that connected to the MTP device since the Cisco IP Voice Media Streaming Application service started. |
The Cisco Messaging Interface object provides information about the Cisco Messaging Interface (CMI) service. The following table contains information on Cisco Messaging Interface (CMI) counters.
This counter represents the heartbeat of the CMI service. This incremental count indicates that the CMI service is up and running. If the count does not increase (increment), the CMI service is down. |
|
This counter represents the running count of inbound SMDI messages since the last restart of the CMI service. |
|
This counter represents the rolling count of inbound SMDI messages in the last 24 hours. |
|
This counter represents the running count of outbound SMDI messages since the last restart of the CMI service. |
|
This counter represents the rolling count of outbound SMDI messages in the last 24 hours. |
|
This counter represents the time in milliseconds when the CMI service started. The real-time clock in the computer, which simply acts as a reference point that indicates the current time and the time that has elapsed, in milliseconds, since the service started, provides the basis for this time. The reference point specifies midnight, January 1, 1970. |
The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object provides information about registered Cisco MGCP BRI devices. The following table contains information on Cisco MGCP BRI device counters.
This counter represents the total number of successful calls that were made from this MGCP Basic Rate Interface (BRI) device |
|
This counter represents the status of the indicated B-Channel that is associated with the MGCP BRI device. Possible values: 0 (Unknown) indicates the status of the channel could not be determined; 1 (Out of service) indicates that this channel is not available for use; 2 (Idle) indicates that this channel has no active call and is ready for use; 3 (Busy) indicates an active call on this channel; 4 (Reserved) indicates that this channel has been reserved for use as a D-channel or for use as a Synch-Channel for BRI. |
|
This counter represents the status of the indicated B-Channel that is associated with the MGCP BRI device. Possible values: 0 (Unknown) indicates the status of the channel could not be determined; 1 (Out of service) indicates that this channel is not available for use; 2 (Idle) indicates that this channel has no active call and is ready for use; 3 (Busy) indicates an active call on this channel; 4 (Reserved) indicates that this channel has been reserved for use as a D-channel or for use as a Synch-Channel for BRI. |
|
This counter represents the state of the Data Link (D-Channel) on the corresponding digital access gateway. This value will get set to 1 (one) if the Data Link is up (in service) or 0 (zero) if the Data Link is down (out of service). |
|
This counter represents the total number of times that a call through this MGCP BRI device was attempted when no voice channels are available. |
The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object provides information about registered Cisco MGCP FXO devices. The following table contains information on Cisco MGCP FXO device counters.
This counter represents the total number of successful calls that were made from the port on an MGCP FXO device. |
|
This counter represents the total number of times that a call through the port on this MGCP FXO device was attempted when no voice channels were available. |
|
This counter represents the status of the FXO port associated with this MGCP FXO device. |
The Cisco MGCP Foreign Exchange Station (FXS) Device object provides information about registered Cisco MGCP FXS devices. One instance of this object gets created for each port on a Cisco Catalyst 6000 24 port FXS Analog Interface Module gateway. For example, a fully configured Catalyst 6000 Analog Interface Module would represent 24 separate instances of this object. The following table contains information on Cisco MGCP FXS device counters.
This counter represents the total number of successful calls that were made from this port on the MGCP FXS device. |
|
This counter represents the total number of times that a call through this port on the MGCP FXS device was attempted when no voice channels were available. |
|
This counter represents the status of the FXS port that is associated with a MGCP FXS device. |
The Cisco MGCP Gateways object provides information about registered MGCP gateways. The following table contains information on Cisco MGCP gateway counters.
This counter represents the number of BRI voice channels that are currently active in a call in the gateway |
|
This counter represents the number of BRI spans that are currently available for use in the gateway. |
|
This counter represents the number of FXO ports that are currently active in a call in the gateway. |
|
This counter represents the number of FXO ports that are currently available for use in the gateway. |
|
This counter represents the number of FXS ports that are currently active in a call in the gateway. |
|
This counter represents the number of FXS ports that are currently available for use in the gateway. |
|
This counter represents the number of PRI voice channels that are currently active in a call in the gateway. |
|
This counter represents the number of PRI spans that are currently available for use in the gateway. |
|
This counter represents the number of T1 CAS voice channels that are currently active in a call in the gateway. |
|
This counter represents the number of T1 CAS spans that are currently available for use in the gateway. |
The Cisco MGCP Primary Rate Interface (PRI) Device object provides information about registered Cisco MGCP PRI devices. The following table contains information on Cisco MGCP PRI device counters.
This counter represents the number of calls that are currently active (in use) on this MGCP PRI device. |
|
This counter represents the total number of successful calls that were made from this MGCP PRI device. |
|
Channel 1 Status through Channel 15 Status (consecutively numbered) |
This counter represents the status of the indicated B-Channel that is associated with a MGCP PRI device. Possible values: 0 (Unknown) indicates that the status of the channel could not be determined; 1 (Out of service) indicates that this channel is not available for use; 2 (Idle) indicates that this channel has no active call and is ready for use; 3 (Busy) indicates that an active call exists on this channel; 4 (Reserved) indicates that this channel has been reserved for use as a D-Channel or for use as a Synch-Channel for E-1. |
This counter represents the status of the indicated B-Channel that is associated with a MGCP PRI Device. Possible values: 0-Unknown, 1-Out of service, 2-Idle, 3-Busy, 4-Reserved, for an E1 PRI Interface, this channel is reserved for use as a D-Channel. |
|
Channel 17 Status through Channel 31 Status (consecutively numbered) |
This counter represents the status of the indicated B-Channel that is associated with the MGCP PRI Device. 0-Unknown, 1-Out of service, 2-Idle, 3-Busy, 4-Reserved. |
This counter represents the state of the Data Link (D-Channel) on the corresponding digital access gateway. This value will be set to 1 (one) if the Data Link is up (in service) or 0 (zero) if the Data Link is down (out of service). |
|
This counter represents the total number of times that a call through an MGCP PRI device was attempted when no voice channels were available. |
The Cisco MGCP T1 Channel Associated Signaling (CAS) Device object provides information about registered Cisco MGCP T1 CAS devices. The following table contains information on Cisco MGCP TI CAS device counters.
This counter represents the number of calls that are currently active (in use) on this MGCP T1 CAS device. |
|
This counter represents the total number of successful calls that were made from this MGCP T1 CAS device. |
|
Channel 1 Status through Channel 24 Status (consecutively numbered) |
This counter represents the status of the indicated B-Channel that is associated with an MGCP T1 CAS device. Possible values: 0 (Unknown) indicates the status of the channel could not be determined; 1 (Out of service) indicates that this channel is not available for use; 2 (Idle) indicates that this channel has no active call and is ready for use; 3 (Busy) indicates that an active call exists on this channel; 4 (Reserved) indicates that this channel has been reserved for use as a D-Channel or for use as a Synch-Channel for E-1. |
This counter represents the total number of times that a call through the MGCP T1 CAS device was attempted when no voice channels were available. |
The Cisco Mobility Manager object provides information on registered Cisco Unified Mobility Manager devices. The following table contains information on Cisco Unified Mobility Manager device counters.
This counter represents the total number of paths that are associated with single-mode/dual-mode phone call that is currently anchored on a Cisco Unified Communications Manager. Call anchoring occurs when a call enters an enterprise gateway and connects to a mobility application that then uses redirection to send the call back out an enterprise gateway. For example, this counter increments twice for a dual-mode phone-to-dual-mode phone call: once for the originating call and once for the terminating call. When the call terminates, this counter decrements accordingly. |
|
This counter represents the total number of aborted handins. |
|
This counter represents the total number of handins that were completed by dual-mode phones. A completed handin occurs when the call successfully connects in the enterprise network and the phone moves from WAN to WLAN. |
|
This counter represents the total number of handins (calls on mobile devices that move from cellular to the wireless network) that failed. |
|
This counter represents the total number of aborted handouts. |
|
This counter represents the total number of handouts (calls on mobile devices that move from the enterprise WLAN network to the cellular network) that were completed. A completed handout occurs when the call successfully connects. |
|
This counter represents the total number of handouts (calls on mobile devices that move from cellular to the wireless network) that failed. |
|
This counter represents the total number of follow-me calls that were attempted. |
|
This counter represents the total number of follow-me calls that were ignored before the AnswerTooSoon timer went off. |
|
This counter represents the total number of attempted IVR calls. |
|
This counter represents the total number of failed IVR calls. |
|
This counter represents the total number of successful IVR calls. |
|
This counter represents the total number of dual-mode SCCP devices that are registered. |
|
This counter represents the total number of dual-mode SIP devices that are registered. |
The Cisco Music On Hold (MOH) Device object provides information about registered Cisco MOH devices. The following table contains information on Cisco MOH device counters.
This counter represents the largest number of simultaneously active MOH connections for an MOH server. This number includes both multicast and unicast connections. |
|
This counter represents the number of currently active multicast connections to multicast addresses that are served by an MOH server. Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if the default audio source is configured for multicast, G.711 mu-law and wideband codecs, two streams get used (default audio source + G.711 mu-law and default audio source + wideband). |
|
This counter represents the number of multicast MOH connections to multicast addresses that are served by an MOH server that are not active and are still available to be used now for the MOH server. Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if the default audio source is configured for multicast, G.711 mu-law and wideband codecs, two streams get used (default audio source + G.711 mu-law and default audio source + wideband). |
|
This counter represents the total number of times that the Media Resource Manager attempted to allocate an MOH resource when all available resources on all MOH servers that are registered with a Cisco Unified Communications Manager were already active. |
|
This counter represents the total number of multicast MOH connections that are allowed to multicast addresses that are served by an MOH server. Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if the default audio source is configured for multicast, G.711 mu-law and wideband codecs, two streams get used (default audio source + G.711 mu-law and default audio source + wideband). |
|
This counter represents the total number of unicast MOH connections that are allowed by an MOH server. |
|
This counter represents the number of active unicast MOH connections to an MOH server. |
|
This counter represents the number of unicast MOH connections that are not active and are still available to be used now for an MOH server. |
The Cisco Media Termination Point (MTP) Device object provides information about registered Cisco MTP devices. The following table contains information on Cisco MTP device counters.
This counter represents the total number of times that an attempt was made to allocate an MTP resource from an MTP device and failed; for example, because all resources were already in use. |
|
This counter represents the number of MTP resources that are currently in use (active) for an MTP device. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call. |
|
This counter represents the total number of MTP resources that are not active and are still available to be used now for an MTP device. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call. |
|
This counter represents the total number of MTP resources that an MTP device provides. This counter equals the sum of the counters ResourceAvailable and ResourceActive. |
The Cisco Phones object provides information about the number of registered Cisco Unified IP Phones, including both hardware-based and other station devices.
The CallsAttempted counter represents the number of calls that have been attempted from this phone. This number increases each time that the phone goes off hook and on hook.
The Cisco Presence object provides information about presence subscriptions, such as statistics that are related to the speed dial or call list Busy Lamp Field (BLF) subscriptions. The following table contains information on Cisco Presence feature.
This counter represents the active presence subscriptions for the call list feature as well as presence subscriptions through SIP trunk. |
|
This counter represents all active incoming and outgoing presence subscriptions. |
|
This counter represents the cumulative number of rejected call list and trunk side presence subscriptions due to throttling for the call list feature. |
|
This counter represents the cumulative number of presence subscriptions that were received on the line side. |
|
This counter represents the cumulative number of presence subscriptions that were received on the trunk side. |
|
This counter represents the cumulative number of presence subscriptions that were sent on the trunk side. |
The Cisco QSIG Feature object provides information about the operation of various QSIG features, such as call diversion and path replacement. The following table contains information about the Cisco QSIG feature counters.
This counter represents the number of successful calls that has been forwarded by rerouting. Call forward by rerouting enables the path for a forwarded call to be optimized (minimizes the number of B-Channels in use) from the originator perspective. This counter resets when the Cisco CallManager service parameter Call Forward by Reroute Enabled is enabled or disabled, or when the Cisco CallManager Service restarts. |
|
This counter represents the number of successful path replacements that have occurred. Path replacement in a QSIG network optimizes the path between two edge PINX (PBXs) that are involved in a call. This counter resets when the Cisco CallManager service parameter Path Replacement Enabled is enabled or disabled, or when the Cisco CallManager Service restarts. |
The Cisco Signaling Performance object provides call-signaling data on transport communications on Cisco Unified Communications Manager. The following table contains information about the Cisco Signaling Performance counter.
This counter represents the total number of incoming UDP packets that were throttled (dropped) because they exceeded the threshold for the number of incoming packets per second that is allowed from a single IP address. Configure the threshold via the SIP Station UDP Port Throttle Threshold and SIP Trunk UDP Port Throttle Threshold service parameters in Cisco Unified Communications Manager Administration. This counter increments for every throttled UDP packet that was received since the last restart of the Cisco CallManager Service. |
The Cisco Session Initiation Protocol (SIP) object provides information about configured SIP devices. The following table contains information on the Cisco SIP counters.
This counter represents the number of calls that are currently active (in use) on this SIP device. |
|
This counter represents the number of calls that have been attempted on this SIP device, including the successful and unsuccessful call attempts. |
|
This counter represents the number of calls that were actually connected (a voice path was established) from a SIP device. This number increments when the call is terminated. |
|
This counter represents the number of calls that are currently in progress on a SIP device, including all active calls. When all calls that are in progress are connected, the number of CallsInProgress equals the number of CallsActive. |
|
This counter represents the number of video calls with streaming video connections that are currently active (in use) on this SIP device. |
|
This counter represents the number of video calls that were actually connected with video streams for this SIP device. This number increments when the call is terminated. |
The Cisco SIP line normalization performance object contains counters that allow you to monitor aspects of the normalization script for SIP lines, including initialization errors, runtime errors, and script status. For SIP lines, each script has only one set of performance counters. This is true even if two endpoints share the same script. The following table contains information about the Cisco SIP line normalization counters.
Display Names |
Description |
---|---|
DeviceResetAutomatically |
This counter indicates the number of times that Cisco Unified Communications Manager automatically resets the device (SIP phone). Automatic resets occur only if the value specified in Script Execution Error Recovery Action or System Resource Error Recovery Action field is set to Reset Device. This counter increments each time Unified Communications Manager automatically resets a device (SIP phone) due to an error. The count is restarted when the script is reset following a change to the script configuration. |
ErrorExecution |
This counter indicates the number of execution errors that occur while the script executes. Execution errors can occur while a message handler executes. Execution errors can be caused by problems such as resource errors or an argument mismatch in a function call. When an execution error occurs, Unified Communications Manager performs the following actions:
Check the SIPNormalizationScriptError alarm for details, including the line number in the script that failed. Correct the script problem, upload the corrected script as needed, and reset the script by clicking the Reset button at the top of the script configuration page. The counter increments for each execution error since the last time the script was reset following a change to the script configuration. Both a script configuration change and a script reset must occur to restart the counter. If the counter continues to increment after you fix the script problem, examine the script again. |
ErrorInit |
This counter indicates the number of times a script error occurred after the script was successfully loaded into memory but failed to initialize in Unified Communications Manager. A script can fail to initialize due to resource errors, an argument mismatch in a function call, and so on. Check the SIPNormalizationScriptError alarm for details, including the line number in the script that failed. Correct the script problem, upload the corrected script if needed, and reset the script by clicking the Reset button at the top of the script configuration page. The counter for the script instance increments every time an initialization error occurs. This counter provides a count from the most recent script reset that was accompanied by a change to the script configuration. Both a script configuration change and a script reset must occur to restart the counter. If the counter continues to increment after you fix the script problem, examine the script again. When the error occurs during initialization, Unified Communications Manager automatically disables the script. |
ErrorInternal |
This counter indicates the number of internal errors that have occurred while the script executed. Internal errors are extremely rare. If the value in this counter is higher than zero, there is a defect in the system not related to the script content or execution. Collect SDI traces and contact the Technical Assistance Center (TAC). |
ErrorLoad |
This counter indicates the number of times that a script error occurred while the script loaded into memory in Unified Communications Manager. A script can fail to load due to memory issues or syntax errors; check the SIPNormalizationScriptError alarm for details such as the script line number where the syntax error exists, check the script for syntax errors, upload a corrected script if needed and reset the script by clicking the Reset button at the top of the script configuration page. The counter for the script instance increments for each load error since the last time the script was reset following a change to the script configuration. Both a script configuration change and a script reset must have occurred to restart the counter. If the counter continues to increment after you believe you have fixed the script problem, examine the script again. |
ErrorResource |
This counter indicates whether or not the script encountered a resource error. There are two kinds of resource errors: exceeding the value configured in the Memory Threshold field or exceeding the value configured in the Lua Instruction Threshold field. Both fields display in the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration. If either condition occurs, Unified Communications Manager immediately closes the script and issues the SIPNormalizationScriptError alarm. If a resource error occurs while the script loads or initializes, the script is disabled. If a resource error occurs during execution, the configured system resource error recovery action is taken as configured in the System Resource Error Recovery Action field on the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration. |
MemoryUsage |
This counter indicates the amount of memory, in bytes, that the script consumes based on the accumulation for all SIP phones using this script. This counter increases and decreases to match the amount of memory being utilized by the script. The count gets cleared when the script is closed (because a closed script consumes no memory) and restarts when the script is opened (enabled). A high number in this counter could indicate a resource problem. Check the MemoryUsagePercentage counter and check for a SIPNormalizationResourceWarning alarm, which occurs when the resource consumption exceeds an internally set threshold. |
MemoryUsagePercentage |
This counter indicates the percentage of the total amount of memory the script consumes based on the accumulation for all SIP phones using this script. The value in this counter is derived by dividing the value in the MemoryUsage counter by the value in the Memory Threshold field (in the SIP Normalization Script Configuration window) and multiplying that result by 100 to arrive at a percentage value. This counter increases and decreases in accordance with the MemoryUsage counter. This count is cleared when the script is closed (because closed scripts consume no memory) and restarts when the script is opened (enabled). When this counter reaches the internally controlled resource threshold, the SIPNormalizationResourceWarning alarm is issued. |
MessageRollback |
This counter indicates the number of times a message was not modified by the script due to an error while the script executes. This can occur only if the value in the Script Execution Error Recovery Action field is set to Message Rollback Only. When an execution error occurs, Unified Communications Manager automatically restores the message to the original contents prior to applying additional error-handling actions. If error handling specifies Rollback Only, no further action is taken beyond rolling back to the original message prior to the normalization attempt. For the other possible Script Execution Error Recovery Action settings, the action specified occurs after the message restores to the original contents. |
msgAddContentBody |
This counter indicates the number of times that the script adds a content body to the message. Assuming your message variable name is “msg”, if you are using the msg:addContentBody API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgAddHeader |
This counter indicates the number of times that the script adds a SIP header to the message. Assuming your message variable name is “msg”, if you are using the msg:addHeader API in the script, this counter increases each time this API executes successfully. If the counter behavior is unexpected, examine the script logic for errors. |
msgAddHeaderUriParameter |
This counter indicates the number of times that the script adds a SIP header URI parameter to a SIP header in the message. Assuming your message variable name is “msg”, if you are using the msg:addHeaderUriParameter API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgAddHeaderValueParameter |
This counter indicates the number of times that the script adds a SIP header value parameter to a SIP header in the message. Assuming your message variable name is “msg”, if you are using the msg:addHeaderValueParameter API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgApplyNumberMask |
This counter indicates the number of times that the script applies a number mask to a SIP header in the message. Assuming your message variable name is “msg”, if you are using the msg:applyNumberMask API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgBlock |
This counter indicates the number of times that the script blocks a message. Assuming your message variable name is “msg”, if you are using the msg:block API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgConvertDiversiontoHl |
This counter indicates the number of times that the script converts Diversion headers into History-Info headers in the message. Assuming your message variable name is “msg”, if you are using the msg:convertDiversionToHI API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgConvertHlToDiverion |
This counter indicates the number of times that the script converts History-Info headers into Diversion headers in the message. Assuming your message variable name is “msg”, if you are using the msg:convertHIToDiversion API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgModifyHeader |
This counter indicates the number of times that the script modifies a SIP header in the message. Assuming your message variable name is “msg”, if you are using the msg:modifyHeader API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgRemoveContentBody |
This counter indicates the number of times that the script removes a content body from the message. Assuming your message variable name is “msg”, if you are using the msg:removeContentBody API in the script, this counter increases each time this API successfully executed. If the counter behavior is unexpected, examine the script logic for errors. |
msgRemoveHeader |
This counter indicates the number of times that the script removes a SIP header from the message. Assuming your message variable name is “msg”, if you are using the msg:removeHeader API in the script, this counter increases each time this API is successfully executed. If the counter behavior is unexpected, examine the script logic for errors. |
msgRemoveHeaderValue |
This counter indicates the number of times that the script removes a SIP header value from the message. Assuming your message variable name is “msg”, if you are using the msg:removeHeaderValue API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgRemoveUnreliableSdp |
This counter indicates the number of times that the script removes SDP body from an unreliable 18x SIP message. Assuming your message variable name is “msg”, if you are using the msg:removeUnreliableSDP API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgSetRequestUri |
This counter indicates the number of times that the script modifies the request URI in the message. Assuming your message variable name is “msg”, if you are using the msg:setRequestUri API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgSetResponseCode |
This counter indicates the number of times that the script modifies the response code or response phrase in the message. Assuming your message variable name is “msg”, if you are using the msg:setResponseCode API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
msgSetSdp |
This counter indicates the number of times that the script sets the SDP in the message. Assuming your message variable name is “msg”, if you are using the msg:setSdp API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ptAddContentBody |
This counter indicates the number of times that the script adds a content body to the PassThrough object. Assuming your PassThrough object name is “pt”, if you are using the pt:addContentBody API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ptAddHeader |
This counter indicates the number of times that the script adds a SIP header to the PassThrough object. Assuming your PassThrough object name is "pt", if you are using the pt:addHeader API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ptAddHeaderUriParameter |
This counter indicates the number of times that the script adds a SIP header URI parameter to the PassThrough object. Assuming your PassThrough object name is "pt", if you are using the pt:addHeaderUriParameter API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ptAddHeaderValueParameter |
This counter indicates the number of times that the script adds a SIP header value parameter to the PassThrough object. Assuming your PassThrough object name is "pt", if you are using the pt:addHeaderValueParameter API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ptAddRequestUriParameter |
This counter indicates the number of times that the script adds a request URI parameter to the PassThrough object. Assuming your PassThrough object name is "pt", if you are using the pt:addRequestUriParameter API in the script, this counter increases each time this API successfully executes. If the counter behavior is unexpected, examine the script logic for errors. |
ScriptActive | This counter indicates whether the script is currently active (running on SIP phones). A value of 0 indicates that the script is closed (disabled). A value of 1 indicates that the script is open and operational. To open the script that should be running, check for any alarms that might indicate why the script is not open, correct any errors, upload a new script if necessary, and reset the script. |
ScriptClosed | This counter indicates the number of times that Unified Communications Manager closes the script. When the script closes on one SIP phone, it can still be enabled on other SIP phones. Unified Communications Manager closes the script because the last SIP phone using this script was either reset manually, reset automatically (due to an error), or deleted. This count restarts when the script resets following a change to the script configuration and when Cisco CallManager restarts. |
ScriptDisabledAutomatically | This counter indicates the number of times that the system automatically disables the script. The values that are specified in the Execution Error Recovery Action or System Resource Error Recovery Action field in the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration determine whether the script is disabled. Automatic script disable occurs if either of these fields are set to Disable Script. The script also gets disabled as a result of script error conditions that are encountered during loading and initialization. This counter provides a count from the most recent manual device reset that involves a script configuration change (a device reset alone does not restart the count; the script must also have changed before the reset occurs). The counter increments each time Unified Communications Manager automatically disables a script due because of script errors. If the number in this counter is higher than expected, perform the following steps: |
ScriptOpened | This counter indicates the number of times that Unified Communications Manager attempts to open the script. For the script to open, it must load into memory in Unified Communications Manager, initialize, and be operational. A number greater than 1 in this counter means that Unified Communications Manager has made more than one attempt to open this script either for an expected reason or due to an error during loading or initialization. The error can occur due to execution errors or resource errors or invalid syntax in the script. Expect this counter to be greater than 1 if the ScriptResetAutomatically counter increments. If the number in this counter is higher than expected, perform the following steps:
This count restarts when the script resets after a script configuration change and when Unified Communications Manager restarts. |
ScriptResetAutomatically | This counter indicates the number of times that the system automatically resets the script. The script resets based on the values that are specified in the Script Execution Error Recovery Action and System Resource Error Recovery Action fields in the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration. Automatic resets can occur if the value in either of these fields is Reset Script. This counter specifies the number of times that the system automatically resets the script following the last time the script is reset after a change to the script configuration. The counter increments each time Unified Communications Manager automatically resets a script because of script errors. If the number in this counter is higher than expected, perform the following steps: |
ScriptResetManually | This counter indicates the number of times that the script manually resets in Cisco Unified Communications Manager Administration or by other methods, such as AXL, or a reset on the last SIP phone that used the script. This counter increments when a script is reset due to configuration changes. This counter restarts when the script is deleted, or when Cisco CallManager restarts. |
The Cisco SIP Normalization performance object contains counters that allow you to monitor aspects of the normalization script, including initialization errors, runtime errors, and script status. Each device that has an associated script causes a new instance of these counters to be created. The following table contains Unified Communications Manager the Cisco SIP Normalization counters.
This counter indicates the number of times that Cisco Unified Communications Manager automatically resets the device (SIP trunk). The device reset is based on the values that are specified in the Script Execution Error Recovery Action and System Resource Error Recovery Action fields on the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration. When the device (SIP trunk) is reset due to script errors, the counter value increments. This count restarts when the device is reset manually. |
|
This counter indicates the number of times that the device (SIP trunk) is reset manually in Cisco Unified Communications Manager Administration or by other methods, such as AXL. When the device associated with a script is reset due to configuration changes, the counter value increments. |
|
This counter represents the number of execution errors that occurred while the script executed. Execution errors can occur while a message handler executes. Execution errors can be caused by resource errors, an argument mismatch in a function call, and so on. When an execution error occurs, Unified Communications Manager performs the following actions:
Check the SIPNormalizationScriptError alarm for details, including the line number in the script that failed. Correct the script problem, upload the corrected script as needed, and reset the trunk. This counter increments every time an execution error occurs. This counter provides a count from the most recent trunk reset that involved a script configuration change. (A device reset alone does not restart the count; the script configuration must also change before the reset occurs.) If the counter continues to increment after you fix the script problem, examine the script again. |
|
This counter represents the number of times a script error occurred after the script successfully loaded into memory, but failed to initialize in Unified Communications Manager. A script can fail to initialize due to resource errors, an argument mismatch in a function call, the expected table was not returned, and so on. Check the SIPNormalizationScriptError alarm for details, including the line number in the script that failed. Correct the script problem, upload the corrected script as needed, and reset the trunk. This counter increments every time an initialization error occurs. This counter provides a count from the most recent trunk reset that was accompanied by a script configuration change. (A device reset alone does not restart the count; the script configuration must also change before the reset occurs.) If the counter continues to increment after you fix the script problem, examine the script again. When the error occurs during initialization, Unified Communications Manager automatically disables the script. |
|
This counter indicates the number of internal errors that occurred while the script executed. Internal errors are very rare. If the value in this counter is higher than zero, a defect exists in the system that is not related to the script content or execution. Collect SDI traces and contact the Technical Assistance Center (TAC). |
|
This counter represents the number of times a script error occurred when the script loaded into memory in Cisco Unified Communications Manager. A script can fail to load due to memory issues or syntax errors. Check the SIPNormalizationScriptError alarm for details. Check the script syntax for errors, upload the corrected script as needed, and reset the trunk. This counter increments every time a load error occurs. This counter provides a count from the most recent trunk reset that was accompanied by a script configuration change. (A device reset alone will not restart the count; the script configuration must also change before the reset occurs.) If the counter continues to increment even after you fix the script problem, examine the script again. |
|
This counter indicates whether the script encountered a resource error. Two kinds of resource errors exist: exceeding the value in the Memory Threshold field and exceeding the value in the Lua Instruction Threshold field. (Both fields display on the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration.) If either condition occurs, Cisco Unified Communications Manager immediately closes the script and issues the SIPNormalizationScriptError alarm. If a resource error occurs while the script loads or initializes, the script is disabled. If a resource error occurs during execution, the configured system resource error recovery action is taken. (The setting of the System Resource Error Recovery Action field on the SIP Normalization Script Configuration window in Cisco Unified Communications Manager Administration defines this action.) |
|
This counter specifies the amount of memory, in bytes, that the script consumes. This counter increases and decreases to match the amount of memory that the script uses. This count gets cleared when the script closes (because a closed script does not consume memory) and restarts when the script opens (gets enabled). A high number in this counter indicates a resource problem. Check the MemoryUsagePercentage counter and the SIPNormalizationResourceWarning alarm, which occur when the resource consumption exceeds an internally set threshold. |
|
This counter specifies the percentage of the total amount of memory that the script consumes. The value in this counter is derived by dividing the value in the MemoryUsage counter by the value in the Memory Threshold field (in the SIP Normalization Script Configuration window) and multiplying the result by 100 to arrive at a percentage. This counter increases and decreases in accordance with the MemoryUsage counter. This count gets cleared when the script closes (because closed scripts do not consume memory) and restarts when the script opens (gets enabled). When this counter reaches the internally controlled resource threshold, the SIPNormalizationResourceWarning alarm is issued. |
|
This counter indicates the number of times that the system automatically rolled back a message. The system rolls back the message by using the error handling that is specified in the Script Execution Error Recovery Action field in the SIP Normalization Script Configuration window in Cisco Cisco Unified Communications Manager Administration. When an execution error occurs, Unified Communications Manager automatically restores the message to the original content before applying additional error handling actions. If error handling specifies Rollback only, no further action is taken beyond rolling back to the original message before the normalization attempt. For the other possible Script Execution Error Recovery Actions, message rollback always occurs first, followed by the specified action, such as disabling the script, resetting the script automatically, or resetting the trunk automatically. |
|
This counter represents the number of times that the script added a content body to the message. If you are using the msg:addContentBody API in the script, this counter increases each time that the msg:addContentBody API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header to the message. If you are using the msg:addHeader API in the script, this counter increases each time that the msg:addHeader API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header URI parameter to a SIP header in the message. If you are using the msg:addHeaderUriParameter API in the script, this counter increases each time that the msg:addHeaderUriParameter API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header value parameter to a SIP header in the message. If you are using the msg:addHeaderValueParameter API in the script, this counter increases each time that the msg:addHeaderValueParameter API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script applied a number mask to a SIP header in the message. If you are using the msg:applyNumberMask API in the script, this counter increases each time that the msg:applyNumberMask API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script blocked a message. If you are using the msg:block API in the script, this counter increases each time that the msg:block API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script converted Diversion headers into History-Info headers in the message. If you are using the msg:convertDiversionToHI API in the script, this counter increases each time that the msg:convertDiversionToHI API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script converted Diversion headers into History-Info headers in the message. If you are using the msg:convertDiversionToHI API in the script, this counter increases each time that the msg:convertDiversionToHI API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script modified a SIP header in the message. If you are using the msg:modifyHeader API in the script, this counter increases each time that the msg:modifyHeader API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script removed a content body from the message. If you are using the msg:removeContentBody API in the script, this counter increases each time that the msg:removeContentBody API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script removed a SIP header from the message. If you are using the msg:removeHeader API in the script, this counter increases each time that the msg:removeHeader API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script removed a SIP header value from the message. If you are using the msg:removeHeaderValue API in the script, this counter increases each time that the msg:removeHeaderValue API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script modified the request URI in the message. If you are using the msg:setRequestUri API in the script, this counter increases each time that the msg:setRequestUri API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script modified the response code and/or response phrase in the message. If you are using the msg:setResponseCode API in the script, this counter increases each time that the msg:setResponseCode API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script set the SDP in the message. If you are using the msg:setSdp API in the script, this counter increases each time that the msg:setSdp API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a content body to the PassThrough (pt) object. If you are using the pt:addContentBody API in the script, this counter increases each time that the pt:addContentBody API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header to the PassThrough (pt) object. If you are using the pt:addHeader API in the script, this counter increases each time that the pt:addHeader API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header URI parameter to the PassThrough (pt) object. If you are using the pt:addHeaderUriParameter API in the script, this counter increases each time that the pt:addHeaderUriParameter API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a SIP header value parameter to the PassThrough (pt) object. If you are using the pt:addHeaderValueParameter API in the script, this counter increases each time that the pt:addHeaderValueParameter API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter represents the number of times that the script added a request URI parameter to the PassThrough (pt) object. If you are using the pt:addRequestUriParameter API in the script, this counter increases each time that the pt:addRequestUriParameter API executes successfully. If the counter behavior is not as expected, examine the script logic for errors. |
|
This counter indicates whether the script is currently active (running on the trunk). The following values display for the counter:
To open the script that should be running on this trunk, perform the following actions: |
|
This counter indicates the number of times that Cisco Unified Communications Manager has closed the script. When the script is closed, it is not enabled on this device. Unified Communications Manager closes the script under one of the following conditions:
This count restarts when the SIP trunk is reset after a change to the script configuration and when Unified Communications Manager restarts. |
|
This counter indicates the number of times that the system automatically disabled the script. The values that are specified in the Script Execution Error Recovery Action and System Resource Error Recovery Action fields in the SIP Normalization Script Configuration window in Cisco Cisco Unified Communications Manager Administration determine whether the script is disabled. The script also gets disabled as a result of script error conditions that are encountered during loading and initialization. This counter provides a count from the most recent manual device reset that involved a script configuration change (a device reset alone does not restart the count; the script must also have changed before the reset occurs). This counter increments every time Unified Communications Manager automatically disables a script due to script errors. If the number in this counter is higher than expected, perform the following actions: |
|
This counter indicates the number of times that the Unified Communications Manager attempted to open the script. For the a script to open, it must load into memory in Unified Communications Manager, initialize, and be operational. A number greater than one in this counter means that Unified Communications Manager has made more than one attempt to open the script on this SIP trunk, either for an expected reason or due to an error during loading or initialization. The error can occur due to execution errors or resource errors or invalid syntax in the script. Expect this counter to be greater than one if any of these counters increment: DeviceResetManually, DeviceResetAutomatically, or ScriptResetAutomatically. The DeviceResetManually counter increments when an expected event, such as a maintenance window on the SIP trunk, causes the script to close. If the number in this counter is high for an unexpected reason, perform the following actions:
This count restarts when the SIP trunk resets after a script configuration change and when Unified Communications Manager restarts. |
|
This counter indicates the number of times that the system automatically reset the script. The script resets based on the values that are specified in the Script Execution Error Recovery Action and System Resource Error Recovery Action fields in the SIP Normalization Script Configuration window in Cisco Cisco Unified Communications Manager Administration. This counter specifies a count of the number of automatic script resets after the last manual device reset; this counter increments every time the Unified Communications Manager automatically resets a script due to script errors. If the number in this counter is higher than expected, perform the following actions: |
The Cisco SIP Stack object provides information about Session Initiation Protocol (SIP) stack statistics that are generated or used by SIP devices such as SIP Proxy, SIP Redirect Server, SIP Registrar, and SIP User Agent. The following table contains information on Cisco SIP Stack counters.
This counter represents the total number of ACK requests that the SIP device received. |
|
This counter represents the total number of ACK requests that the SIP device sent. |
|
This counter represents the total number of BYE requests that the SIP device received. This number includes retransmission. |
|
This counter represents the total number of BYE requests that the SIP device sent. This number includes retransmission. |
|
This counter represents the total number of CANCEL requests that the SIP device received. This number includes retransmission. |
|
This counter represents the total number of CANCEL requests that the SIP device sent. This number includes retransmission. |
|
This counter represents the number of Call Control Blocks (CCB) that are currently in use by the SIP stack. Each active SIP dialog uses one CCB. |
|
This counter represents the total number of 6xx class SIP responses that the SIP device has received. This number includes retransmission. This class of responses indicates that a SIP device, that is providing a client function, received a failure response message. Generally, the responses indicate that a server had definitive information on a particular called party and not just the particular instance in the Request-URI. |
|
This counter represents the total number of 6xx class SIP responses that the SIP device sent. This number includes retransmission. This class of responses indicates that a SIP device, that is providing a server function, received a failure response message. Generally, the responses indicate that a server had definitive information on a particular called party and not just the particular instance in the Request-URI. |
|
This counter represents the total number of 1xx class SIP responses that the SIP device received. This includes retransmission. This class of responses provides information on the progress of a SIP request. |
|
This counter represents the total number of 1xx class SIP responses that the SIP device sent. This includes retransmission. This class of responses provides information on the progress of processing a SIP request. |
|
This counter represents the total number of INFO requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of INFO requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of INVITE requests that the SIP device received. This number includes retransmission. |
|
This counter represents the total number of INVITE requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of NOTIFY requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of NOTIFY requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of OPTIONS requests that the SIP device received. This number includes retransmission. |
|
This counter represents the total number of OPTIONS requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of PRACK requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of PRACK requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of PUBLISH requests that the SIP device received. This number includes retransmissions. |
|
This counter represents the total number of PUBLISH requests that the SIP device has sent. This number includes retransmission |
|
This counter represents the total number of 3xx class SIP responses that the SIP device has received. This number includes retransmission. This class of responses provides information about redirections to addresses where the callee may be reachable. |
|
This counter represents the total number of 3xx class SIP responses that the SIP device has sent. This number includes retransmission. This class of responses provides information about redirections to addresses where the callee may be reachable. |
|
This counter represents the total number of REFER requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of REFER requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of REGISTER requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of REGISTER requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of 4xx class SIP responses that the SIP device has received. This number includes retransmission. This class of responses indicates a request failure by a SIP device that is providing a client function. |
|
This counter represents the total number of 4xx class SIP responses that the SIP device has sent. This number includes retransmission. This class of responses indicates a request failure by a SIP device that is providing a server function. |
|
This counter represents the total number of BYE retries that the SIP device has sent. To determine the number of first BYE attempts, subtract the value of this counter from the value of the sipStatsByeOuts counter. |
|
This counter represents the total number of CANCEL retries that the SIP device has sent. To determine the number of first CANCEL attempts, subtract the value of this counter from the value of the sipStatsCancelOuts counter. |
|
This counter represents the total number of INFO retries that the SIP device has sent. To determine the number of first INFO attempts, subtract the value of this counter from the value of the sipStatsInfoOuts counter. |
|
This counter represents the total number of INVITE retries that the SIP device has sent. To determine the number of first INVITE attempts, subtract the value of this counter from the value of the sipStatsInviteOuts counter. |
|
This counter represents the total number of NOTIFY retries that the SIP device has sent. To determine the number of first NOTIFY attempts, subtract the value of this counter from the value of the sipStatsNotifyOuts counter. |
|
This counter represents the total number of PRACK retries that the SIP device has sent. To determine the number of first PRACK attempts, subtract the value of this counter from the value of the sipStatsPRAckOuts counter. |
|
This counter represents the total number of PUBLISH retries that the SIP device has been sent. To determine the number of first PUBLISHs attempts, subtract the value of this counter from the value of the sipStatsPublishOuts counter. |
|
This counter represents the total number of REFER retries that the SIP device has sent. To determine the number of first REFER attempts, subtract the value of this counter from the value of the sipStatsReferOuts counter. |
|
This counter represents the total number of REGISTER retries that the SIP device has sent. To determine the number of first REGISTER attempts, subtract the value of this counter from the value of the sipStatsRegisterOuts counter. |
|
This counter represents the total number of Reliable 1xx retries that the SIP device has sent. |
|
This counter represents the total number of Request retries that the SIP device has sent. |
|
This counter represents the total number of Final Response retries that the SIP device has sent. |
|
This counter represents the total number of non-Final Response retries that the SIP device has sent. |
|
This counter represents the total number of SUBSCRIBE retries that the SIP device has sent. To determine the number of first SUBSCRIBE attempts, subtract the value of this counter from the value of the sipStatsSubscribeOuts counter. |
|
This counter represents the total number of UPDATE retries that the SIP device has sent. To determine the number of first UPDATE attempts, subtract the value of this counter from the value of the sipStatsUpdateOuts counter. |
|
This counter represents the number of Subscription Control Blocks (SCB) that are currently in use by the SIP stack. Each subscription uses one SCB. |
|
This counter represents the total number of 5xx class SIP responses that the SIP device has received. This number includes retransmission. This class of responses indicates that failure responses were received by a SIP device that is providing a client function. |
|
This counter represents the total number of 5xx class SIP responses that the SIP device has sent. This number includes retransmission. This class of responses indicates that failure responses were received by a SIP device that is providing a server function. |
|
Do not use this counter unless directed to do so by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed to do so by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed to do so by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
Do not use this counter unless directed to do so by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes. |
|
This counter represents the number of SDL signals that are currently on the four SDL priority queues of the SIPHandler component. The SIPHandler component contains the SIP stack. |
|
This counter represents the total number of 1xx response messages, including retransmission, that the SIP device has received. This count includes the following 1xx responses: |
|
This counter represents the total number of 1xx response messages, including retransmission, that the SIP device has sent. This count includes the following 1xx responses: |
|
This counter represents the total number of 2xx response messages, including retransmission, that the SIP device has received. This count includes the following 2xx responses: |
|
This counter represents the total number of 2xx response messages, including retransmission, that the SIP device has sent. This count includes the following 2xx responses: |
|
This counter represents the total number of 3xx response messages, including retransmission, that the SIP device has received. This count includes the following 3xx responses: |
|
This counter represents the total number of 302 Moved Temporarily response messages, including retransmission, that the SIP device has sent. |
|
This counter represents the total number of 4xx response messages, including retransmission, that the SIP device has received. This count includes the following 4xx responses:
|
|
This counter represents the total number of 4xx response messages, including retransmission, that the SIP device has sent. This count includes the following 4xx responses:
|
|
This counter represents the total number of 5xx response messages, including retransmission, that the SIP device has received. This count includes the following 5xx responses: |
|
This counter represents the total number of 5xx response messages, including retransmission, that the SIP device has sent. This count includes the following 5xx responses: |
|
This counter represents the total number of 6xx response messages, including retransmission, that the SIP device has received. This count includes the following 6xx responses: |
|
This counter represents the total number of 6xx response messages, including retransmission, that the SIP device has sent. This count includes the following 6xx responses: |
|
This counter represents the total number of SUBSCRIBE requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of SUBSCRIBE requests that the SIP device has sent. This number includes retransmission. |
|
This counter represents the total number of 2xx class SIP responses that the SIP device has received. This includes retransmission. This class of responses provides information on the successful completion of a SIP request. |
|
This counter represents the total number of 2xx class SIP responses that the SIP device has sent. This includes retransmission. This class of responses provides information on the successful completion of a SIP request. |
|
This counter represents the total number of SIP request messages that have been received by the SIP device. This number includes retransmissions. |
|
This counter represents the total number of SIP request messages that the device sent. This number includes messages that originate on the device and messages that are being relayed by the device. When a particular message gets sent more than once, each transmission gets counted separately; for example, a message that is re-sent as a retransmission or as a result of forking. |
|
This counter represents the total number of SIP response messages that the SIP device received. This number includes retransmission. |
|
This counter represents the total number of SIP response messages that the SIP device sent (originated and relayed). This number includes retransmission. |
|
This counter represents the total number of UPDATE requests that the SIP device has received. This number includes retransmission. |
|
This counter represents the total number of UPDATE requests that the SIP device has sent. This number includes retransmission. |
The Cisco SIP Station object provides information about SIP line-side devices. The following table contains information about the Cisco SIP Station counters.
This counter represents the number of times that a phone that is running SIP was persistently unable to register due to a configuration version mismatch between the TFTP server and Cisco Unified Communications Manager since the last restart of the Cisco Unified Communications Manager. This counter increments each time that Cisco Unified Communications Manager cannot resolve the mismatch and manual intervention is required (such as a configuration update or device reset). |
|
This counter represents the number of times that a phone that is running SIP was temporarily unable to register due to a configuration version mismatch between the TFTP server and Cisco Unified Communications Manager since the last restart of the Cisco CallManager Service. This counter increments each time Cisco Unified Communications Manager is able to resolve the mismatch automatically. |
|
This counter represents the number of new registrations that failed because a timeout occurred while the system was attempting to retrieve the device configuration from the database. |
|
This counter represents the total number of new REGISTRATION requests that have been removed from the NewRegistration queue and processed since the last restart of the Cisco CallManager Service. |
|
This counter represents the number of REGISTRATION requests that are currently on the NewRegistration queue. The system places REGISTRATION requests that are received from devices that are not currently registered on this queue before they are processed. |
|
This counter represents the total number of new REGISTRATION requests that were rejected with a 486 Busy Here response and not placed on the NewRegistration queue since the last restart of the Cisco CallManager Service. The system rejects REGISTRATION requests if the NewRegistration queue exceeds a programmed size. |
|
This counter represents the total number of token requests that have been granted since the last Cisco Communications Manager restart. Cisco Unified Communications Manager grants tokens as long as the number of outstanding tokens remains below the number that is specified in the Cisco CallManager service parameter Maximum Phone Fallback Queue Depth. |
|
This counter represents the number of devices that have been granted a token but have not yet registered. The system requires that devices that are reconnecting to a higher priority Cisco Unified Communications Manager server be granted a token before registering. Tokens protect Cisco Unified Communications Manager from being overloaded with registration requests when it comes back online after a failover situation. |
|
This counter represents the total number of token requests that have been rejected since the last Cisco Unified Communications Manager restart. Cisco Unified Communications Manager will reject token request if the number of outstanding tokens is greater than the number that is specified in the Cisco CallManager service parameter Maximum Phone Fallback Queue Depth. |
The Cisco SW Conference Bridge Device object provides information about registered Cisco software conference bridge devices. The following table contains information on the Cisco software conference bridge device counters.
This counter represents the total number of times that an attempt was made to allocate a conference resource from a SW conference device and failed because all resources were already in use. |
|
This counter represents the number of resources that are currently in use (active) for a SW conference device. One resource represents one stream. |
|
This counter represents the total number of resources that are not active and are still available to be used now for a SW conference device. One resource represents one stream. |
|
This counter represents the total number of conference resources that a SW conference device provides. One resource represents one stream.This counter equals the sum of the ResourceAvailable and ResourceActive counters. |
|
This counter represents the number of software-based conferences that are currently active (in use) on a SW conference device. |
|
This counter represents the total number of conferences that have been allocated and released on a SW conference device. A conference starts when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
The Cisco Telepresence MCU Conference Bridge Device provides information about registered MCU conference bridge devices. The following table contains information about the Cisco Telepresence MCU Conference Bridge Device counters.
This counter represents the total number of active conferences on all Cisco Telepresence MCU conference bridge devices that are registered with Cisco Unified Communications Manager. |
|
This counter represents the total number of conferences that used a Cisco Telepresence MCU conference bridge allocated from Cisco Unified Communications Manager and completed, implying that the conference bridge was allocated and released. A conference is activated when the first call is connected to the bridge. The conference is completed when the last call is disconnected from the bridge. |
|
This counter represents the total number of times Cisco Unified Communications Manager attempted to create HTTP connections to Cisco Telepresence MCU conference bridge device, and failed due to connection errors on the Cisco Telepresence MCU conference bridge side. |
|
This counter represents the total number of times Cisco Unified Communications Manager received a non 200 OK HTTP Response from Cisco Telepresence MCU conference bridge, for any HTTP query sent. |
|
This counter represents the total number of times Cisco Unified Communications Manager attempted to allocate a conference resource from Cisco Telepresence MCU conference bridge device and failed. For example, the attempt to allocate a conference resource fails, if all the resources are already in use. |
The Cisco Trivial File Transfer Protocol (TFTP) Server object provides information about the Cisco TFTP server. The following table contains information about Cisco TFTP server counters.
This counter represents the number of times that the build process aborted when it received a Build all request. This counter increases when building of device/unit/softkey/dial rules gets aborted as a result of group level change notifications. |
|
This counter represents the number of times since the TFTP service started that the TFTP server has built all the configuration files in response to a database change notification that affects all devices. This counter increases by one every time the TFTP server performs a new build of all the configuration files. |
|
This counter represents the number of devices that were processed in the last build of all the configuration files. This counter also updates while processing device change notifications. The counter increases when a new device is added and decreases when an existing device is deleted. |
|
This counter represents the number of dial rules that were processed in the last build of the configuration files. This counter also updates while processing dial rule change notifications. The counter increases when a new dial rule is added and decreases when an existing dial rule is deleted. |
|
This counter represents the time in seconds that it took to build the last configuration files. |
|
This counter represents the number of security-enabled phone devices for which the configuration file was digitally signed with the Cisco Unified Communications Manager server key in the last build of all the configuration files. This counter also updates while processing security-enabled phone device change notifications. |
|
This counter represents the number of softkeys that were processed in the last build of the configuration files. This counter increments when a new softkey is added and decrements when an existing softkey is deleted. |
|
This counter represents the number of gateways that were processed in the last build of all the configuration files. This counter also updates while processing unit change notifications. The counter increases when a new gateway is added and decreases when an existing gateway is deleted. |
|
This counter represents the total number of all the Cisco Unified Communications Manager database change notifications that the TFTP server received. Each time that a device configuration is updated in Cisco Unified Communications Manager Administration, the TFTP server gets sent a database change notification to rebuild the XML file for the updated device. |
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete configuration files for devices. |
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete configuration files for dial rules. |
|
This counter represents the number of configuration files that were encrypted. This counter gets updated each time a configuration file is successfully encrypted |
|
This counter represents the number of GK files that were found in the cache. This counter gets updated each time a GK file is found in the cache |
|
This counter represents the number of GK files that were not found in the cache. This counter gets updated each time a request to get a GK file results in the cache not finding it |
|
This counter represents the heartbeat of the TFTP server. This incremental count indicates that the TFTP server is up and running. If the count does not increase, this means that the TFTP server is down. |
|
This counter represents the number of clients that are currently requesting the HTTP GET file request. |
|
This counter represents the total number of file requests (such as requests for XML configuration files, phone firmware files, audio files, and so on.) that the HTTP server handled. This counter represents the sum total of the following counters since the HTTP service started: RequestsProcessed, RequestsNotFound, RequestsOverflow, RequestsAborted, and RequestsInProgress. |
|
This counter represents the total number of HTTP requests that the HTTP server. canceled (aborted) unexpectedly. Requests could get aborted if the requesting device cannot be reached (for instance, the device lost power) or if the file transfer was interrupted due to network connectivity problems. |
|
This counter represents the total number of HTTP requests where the requested file was not found. When the HTTP server does not find the requested file, a message gets sent to the requesting device. |
|
This counter represents the total number of HTTP requests that were rejected when the maximum number of allowable client connections was reached. The requests may have arrived while the TFTP server was building the configuration files or because of some other resource limitation. The Cisco TFTP advanced service parameter, Maximum Serving Count, sets the maximum number of allowable connections. |
|
This counter represents the total number of HTTP requests that the HTTP server. successfully processed. |
|
This counters represents the number of requests that the HTTP server completed with the files that are on disk and not cached in memory. |
|
This counter represents the number of LD files that were found in the cache. This counter gets updated each time a LD file is found in cache memory. |
|
This counter represents the number of LD files that were not found in cache memory. This counter gets updated each time a request to get an LD file results in the cache not finding it. |
|
This counter represents the maximum number of client connections that the TFTP can serve simultaneously. The Cisco TFTP advanced service parameter, Maximum Serving Count, sets this value. |
|
This counter represents the total number of file requests (such as requests for XML configuration files, phone firmware files, audio files, and so on.) that the TFTP server handles. This counter represents the sum total of the following counters since the TFTP service started: RequestsProcessed, RequestsNotFound, RequestsOverflow, RequestsAborted, and RequestsInProgress. |
|
This counter represents the total number of TFTP requests that the TFTP server canceled (aborted) unexpectedly. Requests could be aborted if the requesting device cannot be reached (for instance, the device lost power) or if the file transfer was interrupted due to network connectivity problems. |
|
This counter represents the number of file requests that the TFTP server currently is processing. This counter increases for each new file request and decreases for each file request that is completed. This counter indicates the current load of the TFTP server. |
|
This counter represents the total number of TFTP requests for which the requested file was not found. When the TFTP server does not find the requested file, a message gets sent to the requesting device. If this counter increments in a cluster that is configured as secure, this event usually indicates an error condition. If, however, the cluster is configured as non-secure, it is normal for the CTL file to be absent (not found), which results in a message being sent to the requesting device and a corresponding increment in this counter. For non-secure clusters, then, this normal occurrence does not represent an error condition. |
|
This counter represents the total number of TFTP requests that were rejected because the maximum number of allowable client connections was exceeded, because requests arrived while the TFTP server was building the configuration files, or because of some other resource limitation. The Cisco TFTP advanced service parameter, Maximum Serving Count, sets the maximum number of allowable connections. |
|
This counter represents the total number of TFTP requests that the TFTP server successfully processed. |
|
This counter represents the total number of data segments that the client devices acknowledged. Files get sent to the requesting device in data segments of 512 bytes, and for each 512-byte segment, the device sends the TFTP server an acknowledgment message. Each additional data segment gets sent upon receipt of the acknowledgment for the previous data segment until the complete file successfully gets transmitted to the requesting device. |
|
This counter represents the number of data segments that the TFTP server reads from the files on disk, while serving files. |
|
This counter represents the total number of data segments that the TFTP server sent. Files get sent to the requesting device in data segments of 512 bytes. |
|
This counter represents the number of SEP files that were successfully found in the cache. This counter gets updated each time that a SEP file is found in the cache. |
|
This counter represents the number of SEP files that were not found in the cache. This counter gets updated each time that a request to get a SEP file produces a not found in cache memory result. |
|
This counter represents the number of SIP files that were successfully found in the cache. This counter gets updated each time that a SIP file is found in the cache |
|
This counter represents the number of SIP files that were not found in the cache. This counter gets updated each time that a request to get a SIP file produces a not found in cache memory result. |
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete configuration files for softkeys. |
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete gateway-related configuration files. |
The Cisco Transcode Device object provides information about registered Cisco transcoding devices. The following table contains information on Cisco transcoder device counters.
This counter represents the total number of times that an attempt was made to allocate a transcoder resource from a transcoder device and failed; for example, because all resources were already in use. |
|
This counter represents the number of transcoder resources that are currently in use (active) for a transcoder device. |
|
This counter represents the total number of resources that are not active and are still available to be used now for a transcoder device. |
|
This counter represents the total number of transcoder resources that a transcoder device provided. This counter equals the sum of the counters ResourceActive and ResourceAvailable. |
The Cisco Video Conference Bridge object provides information about registered Cisco video conference bridge devices. The following table contains information on Cisco video conference bridge device counters.
This counter represents the total number of video conferences that are currently active (in use) on a video conference bridge device. The system specifies a conference as active when the first call connects to the bridge. |
|
This counter represents the number of video conferences that are not active and are still available on a video conference device. |
|
This counter represents the total number of video conferences that have been allocated and released on a video conference device. A conference starts when the first call connects to the bridge. The conference completes when the last call disconnects from the bridge. |
|
This counter represents the total number of video conferences that are configured for a video conference device. |
|
This counter represents the total number of times that an attempt was made to initiate a video conference from a video conference device and failed because the device already had the maximum number of active conferences that is allowed (as specified by the TotalConferences counter). |
|
This counter represents the total number of times that an attempt was made to allocate a conference resource from a video conference device and failed, for example, because all resources were already in use. |
|
This counter represents the total number of resources that are currently active (in use) on a video conference bridge device. One resource gets used per participant. |
|
This counter represents the total number of resources that are not active and are still available on a device to handle additional participants for a video conference bridge device. |
|
This counter represents the total number of resources that are configured on a video conference bridge device. One resource gets used per participant. |
The Cisco Web Dialer object provides information about the Cisco Web Dialer application and the Redirector servlet. The following table contains information on the Cisco Web Dialer counters.
This counter represents the number of Make Call and End Call requests that the Cisco Web Dialer application successfully completed. |
|
This counter represents the number of Make Call and End Call requests that were unsuccessful. |
|
This counter represents the total number of HTTP sessions that the Redirector servlet handled since the last service startup. |
|
This counter represents the number of HTTP sessions that are currently being serviced by the Redirector servlet. |
|
This counter represents the number of Make Call and End Call requests that the Web Dialer servlet has successfully completed. |
|
This counter represents the number of Make Call and End Call requests that failed. |
|
This counter represents the total number of CTI sessions that the Cisco Web Dialer servlet handled since the last service startup. |
|
This counter represents the number of CTI sessions that the Cisco Web Dialer servlet is currently servicing. |
The WSM object provides information on WSMConnectors that are configured on Cisco Unified Communications Manager. Each WSMConnector represents a physical Motorola WSM device. The following table contains information on the Cisco WSM Connector counters.
This counter represents the number of calls that are currently active (in use) on the WSMConnector device. |
|
This counter represents the number of calls that have been attempted on the WSMConnector device, including both successful and unsuccessful call attempts. |
|
This counter represents the number of calls that are connected (a voice path was established) through the WSMConnector device. The counter increments when the call terminates. |
|
This counter represents the number of calls that are currently in progress on the WSMConnector device. This includes all active calls. When the number of CallsInProgress equals the number of CallsActive, this indicates that all calls are connected. |
|
This counter represents the number of DMMS subscribers that are registered to the WSM. |
The IME Client object provides information about the Cisco IME client on the Cisco Unified Communications Manager server. The following table contains information on the Cisco IME client counters.
This counter indicates the number of Cisco IME calls that the Cisco Unified Communications Manager received successfully and that the called party answered, resulting in an IP call. |
|
This counter indicates the number of calls that the Cisco Unified Communications Manager received through Cisco IME. This number includes accepted calls, failed calls, and busy, no-answer calls. The counter increments each time that Cisco Unified Communications Manager receives a call through Cisco IME. |
|
This counter indicates the number of calls that Cisco Unified Communications Manager receives through Cisco IME. This number includes accepted calls, failed calls, and busy, no-answer calls. The counter increments on call initiation. |
|
This counter indicates the number of Cisco IME calls that Cisco Unified Communications Manager placed successfully and that the remote party answered, resulting in an IP call. |
|
This counter indicates the number of unique domain names of peer enterprises that the Cisco IME client discovered. The counter serves as an indicator of overall system usage. |
|
This counter indicates the total number of failed fallback attempts. |
|
This counter indicates the total number of Cisco IME calls that have fallen back to the PSTN mid-call due to a quality problem. The counter includes calls initiated and calls received by this Cisco Unified Communications Manager. |
|
This counter indicates the total number of call attempts for which a Cisco IME route was available but that were set up through the PSTN due to a failure to connect to the target over the IP network. |
|
This counter indicates the total number of distinct phone numbers that the Cisco IME has learned and that are present as routes in the Cisco Unified Communications Manager routing tables. If this number grows too large, the server may exceed the per-cluster limit, and you may need to add additional servers to your cluster. |
|
This counter indicates the total number of DIDs that were published successfully into the IME distributed cache across all Cisco IME client instances. The counter provides a dynamic measurement that gives you an indication of your own provisioned usage and a sense of how successful the system has been in storing the DIDs in the network. |
|
This counter indicates the number of learned routes that were rejected because the the administrator blacklisted the number or domain. This counter provides an indication of the number of cases where a VoIP call cannot happen in the future because of the blocked validation. |
|
This counter indicates the number of voice call record (VCR) upload requests that the Cisco Unified Communications Manager has sent to the Cisco IME server to be stored in the IME distributed cache. |
The IME Client Instance object provides information about the Cisco IME client instance on the Cisco Unified Communications Manager server. The following table contains information on the Cisco IME client instance counters.
This counter indicates the overall health of the connection to the Cisco IME services for a particular Cisco IME client instance (Cisco Unified Communications Manager). The following values may display for the counter:
|
Counter |
Counter description |
---|---|
SAML_REQUESTS |
This counter represents the total number of SAML requests sent to the configured Identity Provider. |
SAML_RESPONSES |
This counter represents the total number of SAML responses received from the configured Identity Provider. |
This object provides information about the Cisco Client Profile (SOAP) interface.
This counter represents the number of login requests received by the Cisco SOAP interface which were redirected to a node in a peer cluster. |
|
This counter represents the number of failed login requests received by the Cisco SOAP interface. |
|
This counter represents the number of login requests received by the Cisco SOAP interface which were redirected to another node. |
The Cisco Presence Engine object provides information about the SIP messages that the Presence Engine receives and sends.
This counter represents the number of SUBSCRIBE messages received by the Presence Engine, including initial subscribes, refreshes, fetches & unsubscribes. |
|
This counter represents the total number of SUBSCRIBE messages sent from the Presence Engine. |
|
This counter represents the number of SUBSCRIBE messages received by the Presence Engine with an event type of presence. |
|
This counter represents the number of SUBSCRIBE messages received by the Presence Engine with an event type of profileconfig. |
|
This counter represents the number of initial non-calendar SUBSCRIBE messages received. |
|
This counter represents the number of non-calendar refresh SUBSCRIBE messages received. |
|
This counter represents the number of non-calendar fetch SUBSCRIBE messages received. |
|
This counter represents the number of non-calendar remove SUBSCRIBE messages received. |
|
This counter represents the number of non-calendar subscriptions that are currently active. |
|
This counter represents the number of SUBSCRIBE messages redirected with a 3xx response. |
|
This counter represents the number of SUBSCRIBE messages rejected with a 4xx response. |
|
This counter represents the number of SUBSCRIBE messages rejected with a 5xx response. |
|
This counter represents the number of SUBSCRIBE messages rejected with a 6xx response. |
|
This counter represents the number of SUBSCRIBE messages rejected with a 503 responses. |
|
This counter represents the number of active subscriptions sent by the Presence Engine to a foreign domain. |
|
This counter represents the number of active subscriptions received by the Presence Engine from a foreign domain. |
|
This counter represents the number of watcher-info presence subscriptions. |
|
This counter represents the n.umber of calendar subscriptions that are currently active. |
|
This counter represents the number of initial SUBSCRIBE messages sent by the Presence Engine to the calendar server. |
|
This counter represents the number of refresh SUBSCRIBE messages sent by the Presence Engine to the calendar server. |
|
This counter represents the number of retry SUBSCRIBE messages sent by the Presence Engine to the calendar server. |
|
This counter represents the number of SUBSCRIBE messages received by the Presence Engine with an event type of calendar. |
|
This counter represents the number of NOTIFY messages by the Presence Engine with an event type of calendar. |
|
This counter represents the number of NOTIFY messages sent from the Presence Engine with an event type of calendar. |
|
This counter represents the number of meetings that were started through calendar integration. |
|
This counter represents the number of meetings that were ended through calendar integration. |
|
This counter represents the number of successful publications processed by the Presence Engine. |
|
This counter represents the number of initial PUBLISH messages received. |
|
This counter represents the number of refresh PUBLISH messages received. |
|
This counter represents the number of modify PUBLISH messages received. |
|
This counter represents the number of remove PUBLISH messages received. |
|
This counter represents the number of the existing number of outgoing NOTIFY messages queued by the Presence Engine. |
|
This counter represents the number of successful NOTIFY messages sent out by the Presence Engine. |
|
This counter represents the number of NOTIFY messages received by the Presence Engine from backend subscriptions. |
|
This counter represents the number of NOTIFY messages sent from the Presence Engine with an event type of presence. |
|
This counter represents the number of NOTIFY messages sent from the Presence Engine with an event type of profileconfig. |
|
This counter represents the number of NOTIFY messages sent that were retried. |
|
This counter represents the number of NOTIFY messages that timed out. |
|
This counter represents the number of NOTIFY messages rejected with a 3xx response. |
|
This counter represents the number of NOTIFY messages rejected with a 4xx response. |
|
This counter represents the number of NOTIFY messages rejected with a 5xx response. |
|
This counter represents the number of NOTIFY messages rejected with a 503 response. |
|
This counter represents the number of NOTIFY messages rejected with a 6xx response. |
|
This counter represents the number of watcher-info presence notifications. |
|
This counter represents the number of watcher-info presence subscriptions. |
|
This counter represents the number of times the load high water mark has been reached. |
|
This counter represents the number of Active Views in the Presence Engine. |
|
This counter represents the number of active resources in the Presence Engine. |
|
This counter represents the number of client emulation sessions between the Presence Engine and JSM. |
|
This counter represents the number of XMPP presence packets received. |
|
This counter represents the number of XMPP presence packets received that were filtered. |
|
This counter represents the number of composed presence updates sent to JSM. |
|
This counter represents the number of XMPP Instant Message packets received by the Presence Engine. |
|
This counter represents the number of XMPP Instant Message packets sent by the Presence Engine. |
|
This counter represents the number of XMPP TC Invites rejected by the Presence Engine. |
|
This counter represents the number of XMPP Instant Message packets received for unregistered SIP resources. |
|
This counter represents the number of XMPP Instant Message packets dropped by the Presence Engine. |
|
This counter represents the number of gone messages sent to the RFI on presence events. |
|
This counter represents the number of errors when sending XMPP messages to the RFI layer. |
|
This counter represents the current number of XMPP Messages that are queued as the RFI is PAUSED. |
|
This counter represents the number of SIP Instant Message packets received by the Presence Engine. |
|
This counter represents the number of SIP Instant Message packets sent by the Presence Engine. |
|
This counter represents the number of gone messages sent to the Proxy on presence events. |
|
This counter represents the number of SIP Instant Message resent to the Proxy. |
|
This counter represents the number of SIP Instant Message packets that timed out when sending to the Proxy. |
|
This counter represents the number of 3xx errors when attempting to send SIP Instant Message packets to the Proxy. |
|
This counter represents the number of 4xx errors when attempting to send SIP Instant Message packets to the Proxy. |
|
This counter represents the number of 5xx errors when attempting to send SIP Instant Message packets to the Proxy. |
|
This counter represents the number of 6xx errors when attempting to send SIP Instant Message packets to the Proxy. |
|
This counter represents the number of Active Instant Message sessions between SIP and XMPP. |
|
This counter represents the number of successful add buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed add buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of successful update buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed update buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of successful delete buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed delete buddy requests processed by the Roster Sync Agent. |
|
This counter represents the number of successful subscribe requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed subscribe requests processed by the Roster Sync Agent. |
|
This counter represents the number of successful unsubscribe requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed unsubscribe requests processed by the Roster Sync Agent. |
|
This counter represents the number of privacy policy update sent to XCP. |
|
This counter represents the number of privacy policy update received from XCP. |
|
This counter represents the number of successful unsubscribed requests processed by the Roster Sync Agent. |
|
This counter represents the number of failed unsubscribed requests processed by the Roster Sync Agent. |
The following table contains information about Cisco SIP Proxy counters.
This counter represents the number of conference call requests received by CTIGW. |
|
This counter represents the number of inbound calls received by CTIGW. |
|
This counter represents the number of LineOpen requests received by CTIGW. |
|
This counter represents the number of MakeCall requests received by CTIGW. |
|
This counter represents the number of INVITE Refreshes received by the IM and Presence server that are sent from the MOC client. |
|
This counter represents the number of retrieve call requests received by CTIGW. |
|
This counter represents the number of SIP 4XX response sent by CTIGW. |
|
This counter represents the number of SIP 5XX response sent by CTIGW. |
|
This counter represents the number of single step transfer call requests received by CTIGW. |
|
This counter represents the number of users authorized by CTIGW. |
|
This counter represents the number of users currently logged into MOC client for Remote Call Control. |
|
This counter represents the number of transfer call requests received by CTIGW. |
|
This counter represents the number of HTTP requests processed. |
|
This counter represents the current number of active federated IM sessions. |
|
This counter represents the current number of active SIP XMPP IM gateway sessions being maintained by the proxy. |
|
This counter represents the current number of SIP Messages sent to SIP client from the XMPP IM gateway. |
|
This counter represents the current number of SIP Messages received from the local PE by the XMPP IM gateway. |
|
This counter represents the current number of SIP Messages sent to the local PE for the XMPP IM gateway. |
|
This counter represents the number of IPC requests from the TCP process. |
|
This counter represents the number of idle sipd worker processes at a current instance. |
|
This counter represents the number of sipd worker processes at a current instance. |
|
This counter represents the number of past-due timer events that were queued. |
|
This counter represents the number of Application User login requests received by the Presence Web Service Module. |
|
This counter represents the number of Application User logout requests received by the Presence Web Service Module. |
|
This counter represents the number of subscriptions that expire before been refreshed. |
|
This counter represents the number of Endpoint refresh requests received by the Presence Web Service Module. |
|
This counter represents the number of End User login requests received by the Presence Web Service Module. |
|
This counter represents the number of End User logout requests received by the Presence Web Service Module. |
|
This counter represents the number of GetPolledPresence requests received by the Presence Web Service Module. |
|
This counter represents the number of GetSubscribedPresence requests received by the Presence Web Service Module. |
|
This counter represents the number of Presence Notifications sent by the Presence Web Service Module. |
|
This counter represents the number of Register Endpoint requests received by the Presence Web Service Module. |
|
This counter represents the number of SetPresence requests received by the Presence Web Service Module. |
|
This counter represents the number of SIP Notifies received by the Presence Web Service Module. |
|
This counter represents the number of SIP Publish requests sent by the Presence Web Service Module. |
|
This counter represents the number of SIP Subscribe requests sent by the Presence Web Service Module. |
|
This counter represents the number of SIP Unpublish requests sent by the Presence Web Service Module. |
|
This counter represents the number of SIP Unsubscribe requests sent by the Presence Web Service Module. |
|
This counter represents the number of endpoint registrations that expire before been refreshed. |
|
This counter represents the number of Subscribe refresh requests received by the Presence Web Service Module. |
|
This counter represents the number of Subscribe requests received by the Presence Web Service Module. |
|
This counter represents the number of Unregister Endpoint requests received by the Presence Web Service Module. |
|
This counter represents the number of Unsubscribe requests received by the Presence Web Service Module. |
|
This counter represents the Server load status on scale of 0 (idle) to 3 (swamped). |
|
This counter represents the number of SIP Client Instant Messages received by the proxy. |
|
This counter represents the number of SIP Client REGISTER requests received by the proxy. |
|
This counter represents the number of failed SIP Client REGISTER requests received by the proxy. |
|
This counter represents the number of sip requests received over tcp transport. |
|
This counter represents the number of sip requests received over udp transport. |
|
This counter represents the number of INVITE requests received by the proxy. |
|
This counter represents the current number of INVITE requests received by the proxy across the enterprise boundary. |
|
This counter represents the number of INVITE requests sent by the proxy. |
|
This counter represents the current number of INVITE requests sent by the proxy across the enterprise boundary. |
|
This counter represents the number of MESSAGE requests received by proxy. |
|
This counter represents the current number of MESSAGE requests received by the proxy across the enterprise boundary. |
|
This counter represents the current number of MESSAGE requests sent by the proxy across the enterprise boundary. |
|
This counter represents the number of NOTIFY requests received by the proxy. |
|
This counter represents the current number of NOTIFY requests received by the proxy across the enterprise boundary. |
|
This counter represents the current number of NOTIFY requests sent by the proxy across the enterprise boundary. |
|
This counter represents the number of REGISTER requests received by the proxy. |
|
This counter represents the current number of requests received directly by the proxy across the enterprise boundary. |
|
This counter represents the current number of requests sent directly by proxy across the enterprise boundary. |
|
This counter represents the number of retransmits executed by the proxy. |
|
This counter represents the number of SUBSCRIBE requests received by the proxy. |
|
This counter represents the current number of SUBSCRIBE requests received by the proxy across the enterprise boundary. |
|
This counter represents the current number of SUBSCRIBE requests sent by the proxy across the enterprise boundary. |
Counter |
Counter Description |
---|---|
NumberOfSyncErrors |
This counter displays the number of errors that occur during synchronization. The counter resets to 0 when the Cisco sync agent is restarted. This counter is always 0 on the subscriber node. |
Counter description |
|
---|---|
This counter represents the total number of successful SASL plain authentication attempts. |
|
This counter represents the total number of failed SASL plain authentication attempts. |
|
This counter represents the number of successful vtg-token authentication attempts. |
|
This counter represents the number of failed vtg-token authentication attempts. |
|
This counter represents the total number of failed authentication attempts due to no license. |
|
This counter represents the total failed SASL plain authentication attempts due to invalid username and password. |
|
This counter represents the total failed vtg-token authentication attempts due to invalid username and password. |
Counter Description |
|
---|---|
This counter represents the number of connected sockets in the Web Connection Manager component. |
|
This counter represents the total number of failed connection requests. |
Counter description |
|
---|---|
This counter represents the number of bytes sent on a per-component basis. |
|
This counter represents the number of bytes received on a per-component basis. |
|
This counter represents the number of errors sent on a per-component basis. |
|
This counter represents the number of errors received on a per-component basis. |
|
This counter represents the number of packets dropped on a per-component basis. |
|
This counter represents the number of stanzas sent on a per-component basis. |
|
This counter represents the number of stanzas received on a per-component basis. |
|
This counter represents the number of message packets sent on a per-component basis. |
|
This counter represents the number of message packets received on a per-component basis. |
|
This counter represents the number of presence packets sent on a per-component basis. |
|
This counter represents the number of presence packets received on a per-component basis. |
|
This counter represents the number of IQ packets received on a per-component basis. |
|
This counter represents the number of IQ packets sent on a per-component basis. |
Counter description |
|
---|---|
This counter represents the total number of successful LDAP searches. |
|
This counter represents the total number of failed LDAP searches. |
|
This counter represents the number of invalid LDAP search requests rejected by Cisco XCP JDS and not sent to LDAP. |
Counter description |
|
---|---|
This counter represents the number of message stanzas received by the JSM component. |
|
This counter represents the number of message stanzas sent by the JSM component. |
|
This component represents the number of presence stanzas received by the JSM component. |
|
This component represents the number of presence stanzas sent by the JSM component. |
|
This counter represents the total number of active JSM sessions on the IM and Presence service. On IM and Presence, the Presence Engine creates a JSM client emulation session for every licensed user at startup time. Additional JSM sessions are also created while users are signed in on their clients. Users may be signed in on multiple clients simultaneously resulting in multiple additional JSM sessions per user. |
|
This counter represents the number of users with one or more JSM sessions. On IM and Presence, the Presence Engine creates a JSM client emulation session for every licensed user. The value of this counter should therefore match the value of the Presence Engine ActiveJsmSessions counter. |
|
This counter represents the current login rate being tracked by the JSM component. |
|
This counter represents the total number of successful logins. |
|
This counter is always 0 on IM and Presence. For details on failed login attempts, see the Cisco XCP Auth Component counters. |
|
This counter represents the total message packets processed by the JSM component. |
|
This counter represents the total presence packets processed by the JSM component. |
|
This counter represents the total number of IQ packets processed by the JSM. |
|
This counter represents the total messages processed by the JSM component in last time slice. |
|
This counter represents the average message size processed by the JSM component. |
|
This counter is always set to 0 on IM and Presence and is reserved for future use. |
|
This counter is always set to 0 on IM and Presence and is reserved for future use. |
|
This counter is always set to 0 on IM and Presence and is reserved for future use. |
Counter description |
|
---|---|
This counter represents the number of IQ packets handles on a per-namespace basis. |
Counter description |
|
---|---|
This counter represents IQ packets received by JSM on a per-session basis. |
|
This counter represents IQ packets sent by JSM on a per-session basis. |
|
This counter represents message packets received by JSM on a per-session basis. |
|
This counter represents message packets sent by JSM on a per-session basis. |
|
This counter represents presence packets received by JSM on a per-session basis. |
|
This counter represents presence packets sent by JSM on a per-session basis. |
|
This counter represents the size of the user’s roster on a per-session basis. |
Counter description |
|
---|---|
This counter represents the total number of packets received by IM and Presence and archived by the Message Archiver component. |
|
This counter represents the total number of packets sent from IM and Presence and archived by the Message Archiver component. |
|
This counter represents the confirmed IMs records written to the Database. |
|
This counter represents the failed attempts to write to the Database. |
|
This counter represents the number of packets Message Archiver receives but are not written to the Database, for example, isTyping packets. |
|
This counter represents the number of packets that Message Archiver has queued pending write to Database. |
Counter description |
|
---|---|
This counter represents the total number of normal packets handled by the Cisco XCP router. |
|
This counter represents the total number of xdb packets handled by the Cisco XCP router. |
|
This counter represents the total number of route packets handled by the Cisco XCP router. |
|
This counter represents the total number of log packets handled by the Cisco XCP router. |
Counter description |
|
---|---|
This counter represents the total foreign domains with incoming subscriptions. |
|
This counter represents the total foreign domains with outgoing subscriptions. |
|
This counter represents the total active SIP outgoing subscriptions. |
|
This counter represents the total active SIP incoming subscriptions. |
|
This counter represents the total pending SIP outgoing subscriptions. |
|
This counter represents the total SIP NOTIFY messages received. |
|
This counter represents the total SIP MESSAGE messages received. |
|
This counter represents the total SIP MESSAGE messages sent. |
|
Counter description |
|
---|---|
This counter represents the total foreign domains with incoming subscriptions. |
|
This counter represents the total foreign domains with outgoing subscriptions. |
|
This counter represents the total failed incoming dialback attempts. |
|
This counter represents the total failed outgoing dialback attempts. |
Counter description |
|
---|---|
This counter represents the total number of all types of text chat rooms. |
|
This counter represents the total number of ad hoc text chat rooms. |
|
This counter represents the total number of permanent text chat rooms. |
|
This counter represents the total number of created text chat rooms. |
|
This counter represents the total number of deleted text chat rooms. |
|
This counter represents the total number of group chat messages received. |
|
This counter represents the total number of group chat messages sent. |
|
This counter represents the total number of private and invite messages received. |
|
This counter represents the total number of messages archived to the external database. |
|
This counter represents the total number of messages not archived to the external database. |
Counter description |
|
---|---|
This counter represents the number of occupants on a per-chat room basis. |
|
This counter represents the number of bytes sent on a per-chat room basis. |
|
This counter represents the number of bytes received on a per-chat room basis. |
|
This counter represents the number of stanzas sent on a per-chat room basis |
|
This counter represents the number of stanzas received on a per-chat room basis. |
|
This counter represents the number of messages sent on a per-chat room basis. |
|
This counter represents the number of messages received on a per-chat room basis. |
|
This counter represents the number of presence packets sent on a per-chat room basis. |
|
This counter represents the number of presence packets received on a per-chat room basis. |
|
This counter represents the number of IQ packets sent on a per-chat room basis. |
|
This counter represents the number of iq packets received on a per-chat room basis. |
Counter description |
|
---|---|
This counter represents the cumulative total number of connected XMPP client sessions. |
|
This counter represents the total number of failed connection requests. |
The CUC Data Store object provides information about registered database usage by Cisco Unity Connection. The following table contains information about CUC Data Store counters.
Amount of database server virtual-address space [in kilobytes]. |
|
Total number of disk read operations for all data chunks (rows) in the last 30 seconds. |
|
Number of write operations to the disk in the last 30 seconds. |
|
Amount of database server shared memory used [in kilobytes]. |
The CUC Data: Databases object provides information about the databases that Cisco Unity Connection uses.
The amount of free space available [in kilobytes] in the selected data chunk. |
|
The CUC Digital Notifications object provides information about the total number of SMS and SMTP notifications. The following table contains information about CUC Digital Notification counters.
The total number of SMS notifications sent to subscribers by Cisco Unity Connection. |
|
The total number of SMTP notifications that Cisco Unity Connection sent to subscribers. |
|
HTML Notifications with Summary of voice messages |
The counter to maintain count of summary notifications. |
HTML Notifications with Summary of voice messages in Last One Minute |
The counter to maintain count of summary notifications sent in last one minute. |
Scheduled Notifications Total |
The counter to maintain count of scheduled summary notifications sent. |
Scheduled Notifications in Last One Minute |
The counter to maintain count of scheduled summary notifications sent in last minute. |
Scheduled Notifications dropped due to Parent Schedule off |
The counter to maintain count of scheduled summary notifications dropped (not sent) because the parent schedule was turned off. |
Scheduled Notifications dropped due to Parent Schedule off in Last One Minute |
The counter to maintain count of scheduled summary notifications dropped (not sent) in last one minute because the parent schedule was turned off. |
Missed Call Notifications Total |
The total number of missed call notifications sent fromCisco Unity Connection. |
The CUC Directory Services object provides information about the performance of the directory services that Cisco Unity Connection uses.
The Directory Search Duration Average [s] counter represents the average time [in seconds] to complete a directory search request for the Cisco Unity Connection server.
The CUC Feeder object keeps a count of total requests processed by the Feeder. The following table contains information about CUC Feeder counters.
Counters |
Counter Descriptions |
---|---|
Total objects requests processed |
The total number of HTTP[S]/CCI objects requests processed by Feeder. |
Objects requests processed in last 15 minutes |
The total number of HTTP[S]/CCI objects requests processed by Feeder in last 15 minutes. |
Total object requests processed |
The total number of HTTP[S]/CCI object requests processed by Feeder. |
Object requests processed in last 15 minutes |
The total number of HTTP[S]/CCI object requests processed by Feeder in last 15 minutes. |
The Mailbox Sync service synchronizes messages between Unity Connection and Exchange.
Counters | Counter Description |
---|---|
Active thread count |
Cisco Unity Connection maintains threads for synchronization of voicemail from Cisco Unity Connection to Exchange server and vice-versa. At any moment, this counter specifies the number of threads that are actively in use for voicemail synchronization. |
Background queue size |
Mailbox sync has three types of priority queues: Background, Normal, and Time-Sensitive. Background queue is the lowest priority queue. This queue has items that are scheduled because of background re-synchronization of each mailbox hourly. |
Normal queue size |
Normal queue has moderate priority. This queue has items that are scheduled because of messaging operation (such as message CREATE, READ, UNREAD, DELETE) performed by user or any configuration update by administrator on Unified Messaging page on Cisco Unity Connection Administration. |
Time sensitive queue size |
Time sensitive queue has highest priority. This queue has such items that are scheduled because of keep-alive message sent by Cisco Unity Connection to Exchange server to keep subscription alive. This is applicable for 2003 Exchange server only. |
Total connection errors |
It specifies the number of times the CuMbxSync process fails to retrieve or update some data from database. |
Total Mailbox Adds |
It specifies the number of times a user mailbox has been setup for subscription. Any communication error between Unity Connection and Exchange, results in user mailbox remove and re-add. |
Total Mailbox Removes |
It specifies the number of times a user mailbox has been setup for un-subscription. Any communication error between Unity Connection and Exchange, results in user mailbox remove and re-add. |
Total Resyncs |
It specifies the total number of times user mailbox is resynchronized with Exchange server. Cisco Unity Connection does background resynchronization for all the user mailboxes hourly. |
Total Retries |
Whenever there is a communication failure between Cisco Unity connection and Exchange server, Unity Connection does mailbox synchronization retry for particular user mailbox. This counter specifies the count of such occurrences. |
Total Work Items |
It specifies number of times any messaging operation, such as CREATE, READ, UNREAD, and DELETE, has been performed on any user mailbox. |
The CUC Message Store object provides information about the performance of the Cisco Unity Connection message store. The following table contains information about CUC Message Store counters.
Total number of messages sent to the Bad Mail folder since the last restart of the MTA server. |
|
Total number of delivery receipts since the last restart of the MTA server. |
|
Number of incoming requests to recall local copies of messages initiated by remote senders on other network locations. |
|
Total number of intersite messages delivered since the last restart of the MTA server. |
|
Total number of intersite messages received since the last restart of the MTA server. |
|
Total number of intersite messages that have been delivered and received since the last restart of the MTA server. |
|
Number of message recalls initiated by local senders on this server. |
|
Total number of messages delivered since the last restart of the MTA server. |
|
Messages Received Per Minute |
Total number of messages received Per Minute by MTA. |
Total number of messages received since the last restart of the MTA server. |
|
Total number of non-delivery receipts since the last restart of the MTA server. |
|
Total number of message recalls. This number includes each individual copy of a message that was sent to multiple recipients, so this number could be much larger than the Total Recalls, Local and Remote performance counter. |
|
Total number of read receipts since the last restart of the MTA server. |
|
Total number of retries since the last restart of the MTA server. |
|
Total number of dispatch messages that have been delivered to individual user mailboxes since the MTA started. This number includes a count of each individual copy of a message sent to multiple recipients. |
|
Total number of dispatch messages that have been accepted since the last restart of the MTA server |
|
Total number of dispatch messages that have been delivered since the MTA started. This number includes each message just once, regardless of the number of recipients. |
|
Total number of individual copies of dispatch messages that have been declined since the last restart of the MTA server. |
|
Total number of dispatch messages that have been removed from user mailboxes due to the message being accepted by another user since the last restart of the MTA server |
|
Total number of message recalls initiated by local and remote senders. This number should be equal to the total of Incoming Recalls and Local Recalls performance counters. |
|
The average time [in seconds] to decode voice messages in MIME format to the original format. |
|
The average time [in seconds] to encode voice messages to MIME format. |
|
The number of VPIM messages that the Cisco Unity Connection Messages Store delivered within a minute. |
|
The total number of VPIM messages that the Cisco Unity Connection Messages Store delivered. |
|
The number of VPIM messages that the Cisco Unity Connection Messages Store received per minute. |
|
The total number of VPIM messages that the Cisco Unity Connection Messages Store received. |
|
The total number of VPIM messages that the Cisco Unity Connection Message Store processed. |
|
Messages Undelivered Mailbox Quota Full Notification Total |
The total number of missed call notification sent when mailbox quota is full. |
Video Messages Delivered Total |
The total number of video messages delivered since the last restart of the MTA server. |
Video Messages Delivered Per Minute |
The total number of video messages delivered per minute since the last restart of the MTA server. |
Video Messages Processed by MTA Total |
The total number of video messages processed (both successful and unsuccessful) by the MTA server since the last restart of the server. |
Video Messages Processed by MTA Per Minute |
The total number of video messages processed (both successful and unsuccessful) by the MTA server per minute since the last restart of the server. |
The CUC Message Store: Databases object provides information about the message store database that Cisco Unity Connection uses.
The Messages Delivered Per Message Store counter represents the total number of messages that were delivered per message store since the last restart of the MTA server.
The CUC Personal Call Transfer Rules object provides information about the numbers and usage of the personal call transfer rules (PCTR). The following table contains information about CUC Personal Call Transfer Rules counters.
Personal call transfer rule (PCTR) call resulted in rule processing, and an applicable transfer rule is found. |
|
Number of destinations tried while transfer rules were applied. |
|
Calls that are subject to personal call transfer rule (PCTR) processing: user assigned COS is enabled for PCTR, user is a Cisco Unified Communications Manager user, user has not disabled PCTR. |
|
Number of rules that are evaluated during rule processing in a personal call transfer rule (PCTR) call. |
|
Number of times that a subscriber was reached while transfer rules were applied. |
|
Number of times that Cisco Unity Connection fails to transfer a call to a destination while personal call transfer rules were applied. Transfer failures include all conditions except when the called destination is connected, busy, or RNA or times out. A caller hanging up during a transfer gets considered a transfer failure. |
|
Number of times that voice mail was reached while transfer rules were applied. |
The CUC Phone System object provides information about the performance of the phone system integration. The following table contains information about CUC Phone System counters.
The current number of incoming and outgoing calls to the Cisco Unity Connection server. |
|
The total number of incoming and outgoing calls to the Cisco Unity Connection server. |
|
The average duration [in seconds] of incoming and outgoing calls from the Cisco Unity Connection server. |
|
The total duration [in seconds] of incoming and outgoing calls from the Cisco Unity Connection server. |
|
The total number of unanswered calls on the Cisco Unity Connection server. |
|
The current number of incoming calls that were received as Call Forward Busy. |
|
The total number of incoming calls that were received as Call Forward Busy. |
|
The current number of incoming calls that were received as Call Forward No Answer. |
|
The total number of incoming calls that were received as Call Forward No Answer. |
|
The current number of incoming calls that were received as direct calls. |
|
The total number of incoming calls that were received as direct calls. |
|
The average duration [in seconds] of all incoming calls to the Cisco Unity Connection server. |
|
The total duration [in seconds] of all incoming calls to the Cisco Unity Connection server. |
|
The total number of incoming calls without integration information. |
|
The average time [in seconds] to complete all message notifications from the Cisco Unity Connection server. |
|
The total time [in seconds] to complete all message notifications from the Cisco Unity Connection server. |
|
The total number of message notifications that failed to connect to a destination number. |
|
The total number of message notifications that Cisco Unity Connection sent to subscribers. |
|
The average duration [in milliseconds] of all MWI requests from the Cisco Unity Connection server. |
|
The total duration [in milliseconds] of all MWI requests from the Cisco Unity Connection server. |
|
The total number of MWI requests that failed to connect to a destination number or complete MWI operation. |
|
The total number of MWI requests that Cisco Unity Connection sent. |
|
The average duration [in seconds] of all outgoing calls from the Cisco Unity Connection server. |
|
The total duration [in seconds] of all outgoing calls from the Cisco Unity Connection server. |
|
The number of completed release transfers from the Cisco Unity Connection server. |
|
The number of release transfers from the Cisco Unity Connection server that failed to connect to a destination number. |
|
The total number of release transfers that were attempted from the Cisco Unity Connection server. |
|
The number of completed supervised transfers from the Cisco Unity Connection server. |
|
The number of supervised transfers from the Cisco Unity Connection server that were dropped while in progress. |
|
The number of supervised transfers from the Cisco Unity Connection server that failed to connect to a destination number. |
|
The total number of supervised transfers from the Cisco Unity Connection server. |
|
The total number of release and supervised transfers that Cisco Unity Connection attempted. |
|
The average time [in seconds] to complete all pager notifications from the Cisco Unity Connection server. |
|
The total time [in seconds] to complete all pager notifications from the Cisco Unity Connection server. |
|
The total number of pager notifications that failed to connect to a destination number. |
|
The total number of pager notifications that Cisco Unity Connection sent to subscribers. |
|
The total time [in seconds] that any port remains idle between incoming calls to the Cisco Unity Connection server. |
|
The average time [in seconds] that any port remains idle between incoming calls to the Cisco Unity Connection server. |
|
The current number of integration ports that are not in use by the Cisco Unity Connection server. |
|
The current number of integration ports that are in use by the Cisco Unity Connection server. |
|
The current count of the ports that no longer respond or are otherwise unusable by Cisco Unity Connection. |
|
Missed Call Total |
The total number of missed call notifications triggered by theCisco Unity Connection server. |
The CUC Phone System: Ports object provides information about the voice messaging ports on Cisco Unity Connection. The following table contains information about CUC Phone System: Ports counters.
The total number of calls that were received on this port since the Cisco Unity Connection server was last restarted. This includes all types of calls: Incoming calls, MWI dialouts, Notification dialouts, TRAP dialouts, and VPIM dialouts. |
|
The distribution percentage of idle ports on the Cisco Unity Connection server. |
|
The average time [in seconds] that a port has been actively processing calls. |
|
The total time [in seconds] that a port has been actively processing calls. |
|
The distribution percentage of calls into ports on the Cisco Unity Connection server. |
The CUC Replication object provides information about the replication for Cisco Unity Connection redundancy. The following table contains information about CUC Replication counters.
The CUC Replicator: Remote Connection Locations object provides information about replication with remote Connection locations. The following table contains information about CUC Replicator: Remote Connection Locations counters.
The number of replication dependencies requested received from the Connection location. |
|
The number of replication dependencies requests sent to the Connection location. |
|
The number of replication messages from this Connection location that were not received because of failures. |
|
The number of replication messages to the Connection location that were not sent because of failures. |
|
The number of replication messages received from the Connection location. |
|
The number of replication messages sent to the Connection location. |
|
The number of replication NDR messages received from the Connection location. |
|
The number of USN request received from the Connection location. This usually indicates that a USN timeout occurred on the remote node. |
The CUC Sessions: Calendar Access object provides information about the Cisco Unity Connection calendar integration. The following contains information about CUC Sessions: Calendar Access counters.
The CUC Sessions: E-mail Access object provides information about e-mail voice sessions. The following table contains information about CUC Sessions: E-mail Access counters.
The total number of e-mail messages that were read since the last restart of Cisco Unity Connection. |
|
The average duration [in milliseconds] of all e-mail sessions as measured on a per-call basis. |
|
The total duration [in milliseconds] of all e-mail sessions as measured on a per-call basis. |
|
The total number of e-mail voice sessions since the last restart of Cisco Unity Connection. |
The CUC Sessions: IMAP Server object provides information about the IMAP server. The following table contains information about CUC Sessions: IMAP Server counters.
The average duration [in seconds] of the connections to the IMAP server in the previous minute. |
|
The total number of IMAP errors that the IMAP server returned since the last restart of the IMAP server. |
|
The total number of EXAMINE requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of failed LOGIN requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of FETCH requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of LOGIN requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of LOGOUT requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of IMAP FETCH commands that have returned the body of the a message since the IMAP was last restarted. |
|
The number of IMAP FETCH commands in the previous hour that returned the body of a message. |
|
Average number of messages that the IMAP FETCH command returned. |
|
The total number of NOOP requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of SEARCH requests to the IMAP server since the last restart of the IMAP server. |
|
The total number of socket connections that have been made to the IMAP server since it was last restarted. |
|
The total number of STARTTLS requests to the IMAP server since the last restart of the IMAP server. This counter also increments when clients connect to the IMAP SSL port directly. |
|
The total number of STATUS requests to the IMAP server since the last restart of the IMAP server. |
|
The number of active Transport Layer Security connections to the IMAP server. |
|
The total number of failed TLS connections to the IMAP server since the last restart of the IMAP server. |
|
Average Unsolicited Notify Response Time [in milliseconds] for the IMAP server. |
|
Total number of Unsolicited Notify Responses that the IMAP server made since it was last restarted. |
The CUC Sessions: RSS object provides information about RSS sessions. The following table contains information about CUC Sessions: RSS counters.
The total number of RSS messages that were offered for streaming. |
|
The total number of RSS messages that the Cisco Unity Connection server streamed. |
|
The CUC Sessions: SMTP Server object provides information about SMTP server sessions. The following table contains information about CUC Sessions: SMTP Server counters.
The number of SMTP messages that were delivered since the start of the system. |
|
The number of SMTP messages delivered or received since the start of the system. |
|
The number of SMTP messages that were received since the start of the system. |
The CUC Sessions: SpeechView Processor object provides information about the SpeechView Processor service. The following table contains information about CUC Sessions: SpeechView Processor counters.
The average time it takes to receive successful transcriptions from the external service. |
|
The total number of failed transcriptions since the last restart of the SpeechView Processor service. |
|
The total number transcriptions that timed out since the last restart of the SpeechView Processor service. |
|
The total number successful transcriptions since the last restart of the SpeechView Processor service. |
The CUC Sessions: TRaP object provides information about telephone record and playback (TRaP) sessions. The following table contains information about CUC Sessions: TRaP counters.
The average duration [in seconds] of all reverse TRaP sessions. |
|
The total duration [in seconds] of all reverse TRaP sessions. |
|
The total number of reverse TRaP sessions since the last start of Cisco Unity Connection. |
|
The total number of TRaP sessions since the last start of Cisco Unity Connection. |
The CUC Sessions: TTS object provides information about text-to-speech (TTS) sessions. The following table contains information about CUC Sessions: TTS counters.
The total number of TTS voice sessions since the last start of Cisco Unity Connection. |
The CUC Sessions: Unified Client object provides information about the Unified Client for Cisco Unity Connection.
The Connections Total counter represents the total number of Unified Client IMAP requests.
CUC Sessions Video: Video session object provides information about video sessions with video server. The following table contains information about CUC Sessions: Video
Counters |
Counter Descriptions |
---|---|
Audio calls Negotiated Total |
The total number of Audio calls negotiated despite video offer. |
Audio Calls Negotiated In Last One Minute |
The total number of audio calls negotiated despite video offer in last one minute. |
Outgoing Video calls Release Transfer |
The total number of outgoing video calls transferred as Release to Switch. |
Supervise Transfer Calls Total |
The total number of Supervise transfers initiated from video calls since the last restart of Cisco Unity Connection. |
Video calls downgraded to Audio Total |
The total number of video calls downgraded to audio since the last restart of Unity Connection. |
Video calls downgraded to Audio In Last One Minute |
The total number of video calls downgraded to audio in last one minute. |
Video calls downgraded with prompt total |
Total number of video calls downgraded with prompt "Video services are not available using audio only for duration of this call". |
Video calls downgraded with prompt in Last One Minute |
Total number of video calls downgraded with prompt "Video services are not available using audio only for duration of this call" in last minute. |
Video Sessions Total |
The total number of video session requests sent from Unity Connection to Video Server. |
Video Sessions Current |
The total number of current video session requests sent from Unity Connection to Video Server. |
Video Session Playbacks Total |
The total number of video session playbacks since the last restart of Cisco Unity Connection. |
Video Session Playbacks Current |
The total number of current video session playbacks. |
Video Media File Playbacks Total |
The total number of image playbacks from video server since the last restart of Unity Connection. |
Video Media File Playbacks Current |
The current number of Video Media File playbacks from video server. |
Video Recordings Total |
The total number of Video Recordings saved at video server since the last restart of Unity Connection. |
Video Recordings Current |
The current number of Video Recordings saved at video server. |
Video Playback Completed Events from MS Total |
The total number of Video Playback completed events from video server since the last restart of Unity Connection. |
Video Playback Completed Events from MS In Last One Minute |
The total number of Video Playback completed events from video server since last one minute. |
Video Keep Alive Total |
The total number of Keep Alive sent by Unity Connection to video server since the last restart of Unity Connection. |
Video Keep Alive In Last One Minute |
The total number of Keep Alive sent by Unity Connection to video server since last one minute. |
Video Get Media Capabilities Total |
The total number of GetMediaCapabilities sent by Unity Connection to video server since the last restart of Unity Connection. |
Video Get Media Capabilities In Last One Minute |
The total number of GetMediaCapabilities sent by Unity Connection to video server since last one minute. |
Video SignIn Total |
The total number of SignIn request sent by Unity Connection to video server since the last restart of Unity Connection. |
Video SignIn Total In Last One Minute |
The total number of SignIn sent by Unity Connection to video server since last one minute. |
KeyFrame Request sent Total |
The total number of KeyFrame requests sent during video recording to EndPoint since the last restart of Cisco Unity Connection. |
KeyFrame Request sent In Last One Minute |
The total number of KeyFrame requests sent during video recording to EndPoint since the last restart of Cisco Unity Connection. |
Video Record Successful Total |
The total number of successful Video Recordings since the last restart of Cisco Unity Connection. |
Video Sessions Failed Total |
The total number of video sessions failed since the last restart of Cisco Unity Connection. |
Video Session Failed In Last One Minute |
The total number of video sessions failed in last one minute. |
Media Sense Timeout Total |
The total number of connection timeout errors while connecting to MediaSense server since the last restart of Cisco Unity Connection. This counter is applicable for the following events: |
Video Play Failed Total |
The total number of video messages that are played as audio messages since the last restart of Cisco Unity Connection. |
The CUC Sessions: Voice object provides information about voice sessions. The following table contains information on CUC Sessions: Voice counters.
The delay [in milliseconds] that a caller experienced when the caller attempted to search through the directory. This counter measures the time between the entered search criteria and the return results. |
|
The delay [in milliseconds] that a caller experienced before any audio was received. This counter measures the time between the system receiving a call and the time audio begins streaming to the caller. |
|
The delay [in milliseconds] that a Cisco Unity Connection subscriber experienced when the subscriber attempted to delete a message. This counter measures the time between the last delete message prompt and the confirmation of the deletion. |
|
The delay [in milliseconds] that a Cisco Unity Connection subscriber experienced due to authentication. |
|
The delay [in milliseconds] that a Cisco Unity Connection subscriber experienced during message counting in the subscriber message box. |
|
The delay [in milliseconds] that a caller experienced while Cisco Unity Connection is gathering message header information. |
|
The total number of times that the failsafe conversation has been played. |
|
The total number of active G.711 (a-law) voice sessions since the last restart of Cisco Unity Connection. |
|
The total number of active G.711 (u-law) voice sessions since the last restart of Cisco Unity Connection. |
|
The total number of active G.722 voice sessions since the last restart of Cisco Unity Connection. |
|
The total number of active G.729 voice sessions since the last restart of Cisco Unity Connection. |
|
The total number of active iLBC voice sessions since the last restart of Cisco Unity Connection. |
|
The delay [in milliseconds] that a Cisco Unity Connection subscriber experienced due to looking up meetings. |
|
The total number of voice messages that were deleted through the TUI from the time Cisco Unity Connection was last restarted. |
|
The total number of voice messages that were forwarded through the TUI from the time Cisco Unity Connection was last restarted. |
|
The total number of voice messages that were read through the TUI from the time Cisco Unity Connection was last restarted. |
|
The total number of voice messages that received replies through the TUI from the time Cisco Unity Connection was last restarted. |
|
The total number of voice messages that were sent through the TUI from the time Cisco Unity Connection was last restarted. |
|
The delay [in milliseconds] between an MRCP define-grammar request and its response. |
|
The average delay [in milliseconds] between an MRCP define-grammar request and its response. |
|
The maximum delay [in milliseconds] between an MRCP define-grammar request and its response. |
|
The delay [in milliseconds] between an MRCP request and its response. |
|
The average delay [in milliseconds] between an MRCP request and its response. |
|
The maximum delay [in milliseconds] between an MRCP request and its response. |
|
The current number of all active voice sessions for any codec. |
|
The total number of voice sessions for any codec - G.711 mu-law and G.729 - since the last restart of Cisco Unity Connection. |
|
The delay [in milliseconds] that a Cisco Unity Connection subscriber experienced due to finding and loading a subscriber by DTMF ID. |
The CUC Sessions: VUI object provides information about the voice user interface (VUI). The following table contains information on CUC Sessions: VUI counters.
The delay [in milliseconds] that a user when experienced when the user attempted to access a message. This counter measures the time between the voice command of intending to listen to a message and the actual playback of the message. |
|
The total number of messages that were read through the VUI from the time that Cisco Unity Connection was last restarted. |
|
The average duration [in seconds] of a VUI session as measured on a per-call basis. |
|
The CUC Sessions: Web object provides information about the Cisco Personal Communications Assistant (Cisco PCA) and Cisco Unity Connection Administration sessions. The following table contains information on CUC Sessions: Web counters.
The maximum delay [in seconds] in authentication to a user Inbox or Assistant. |
|
The total number of CPCA pages that the Cisco Unity Connection server served. |
|
The number of requests in CPCA queue waiting to be processed. |
|
The total number of server busy pages that the Cisco Unity Connection server returned. |
|
The maximum delay [in seconds] in authentication to the System Administrator window. |
|
The maximum time [in milliseconds] for the Tomcat server to respond to any given request. |
The CUC Sessions: Web E-mail Access object provides information about web e-mail access sessions (IMAP). The following table contains information about CUC Sessions: Web E-mail Access counters.
The total number of e-mail messages that were read since the last restart of Cisco Unity Connection. |
|
The average duration [in milliseconds] of all e-mail sessions as measured on a per-call basis. |
|
The total duration [in milliseconds] of all e-mail sessions as measured on a per-call basis. |
|
The total number of e-mail voice sessions since the last restart of Cisco Unity Connection. |
The CUC System Agent object records the information about the periodic system tasks. The following table contains information about CUC System Agent counters.
Counters |
Counter Descriptions |
---|---|
Message Related Files Shredded Total |
The total number of messaging related files that have been shredded. |
Message Related Files Shredded Failed |
The total number of messaging related files that have failed to shred. |
Total Number of Requests sent by HTTP[S]/CCI Link |
The cumulative number of HTTP(S) requests sent by the Reader. |
Total Number of successful response of HTTP[S]/CCI Requests |
The cumulative number of HTTP(S) requests that were successfully processed by the Feeder. |
Total Number of failure response of HTTP[S]/CCI Requests |
The cumulative number of HTTP(S) requests that were not successfully processed by the Feeder. |
Total Number of Directory Objects Successfully Processed |
The cumulative number of Directory Objects that were successfully processed. |
Directory Objects Processed Successfully In Last One Minute |
Directory objects successfully processed per minute. |
Delete Request sent to Media Sense Total |
The total number of delete requests sent to MediaSense server since the last restart of Unity Connection. |
Media Sense Timeout While Delete Total |
The total number of connection timeouts in response to the delete requests sent to MediaSense server since the last restart of Unity Connection. |
Authentication validates the user ID and password that are submitted during log in. An alarm gets raised when an invalid user ID and/or the password gets used.
Number of AuthenticationFailed events exceeds: 1 time in the last 1 minute |
|
This alert occurs when the DRF backup or restore process encounters errors.
Trigger alert when following condition met: CiscoDRFFailure event generated |
|
This alert occurs when the CoreDumpFileFound event gets generated. This indicates that a core dump file exists in the system.
Trigger alert when following condition met: CoreDumpFileFound event generated |
|
CPU usage gets monitored based on configured thresholds. If the usage goes above the configured threshold, this alert gets generated.
Trigger alert when following condition met: 99% |
|
Trigger alert only when value constantly below or over threshold for 60 seconds |
|
The CriticalServiceDown alert gets generated when the service status equals down (not for other states).
Trigger alert when following condition met: Service status is DOWN |
|
This alert occurs when the Cisco Database Notification Service experiences problems and might stop. This condition indicates change notification requests that are queued in the database got stuck and changes made to the system will not take effect. Ensure that the Cisco Database Layer Monitor is running on the node where the alert exists. If it is, restart the service. If that does not return this alert to safe range, collect the output of show tech notify and show tech dbstateinfo and contact TAC for information about how to proceed.
Trigger alert when following condition met: DBChangeNotify queue delay over 2 minutes |
|
This alarm indicates a failure in IDS replication and requires database administrator intervention.
Note | Be aware that DBReplicationFailure is based on the replication status perfmon counter (instead of DBReplicationFailure alarm as was previously the case). This alert gets triggered whenever the corresponding replication status perfmon counter specifies a value of 3 (Bad Replication) or 4 (Replication Setup Not Successful). |
Trigger alert when following condition met: DBReplicationFailure occurred |
|
Trigger alert when following condition met: IDSReplicationFailure event with alarm number 888 generated. |
|
This alert occurs when a hardware failure event (disk drive failure, power supply failure, and others) has occurred.
Trigger alert when following condition met: HardwareFailure event generated |
|
This alert occurs when the LogFileSearchStringFound event gets generated. This indicates that the search string was found in the log file.
Trigger alert when following condition met: LogFileSearchStringFound event generated |
|
This alert occurs when the percentage of used disk space in the log partition exceeds the configured high water mark. When this alert gets generated, LPM deletes files in the log partition (down to low water mark) to avoid running out of disk space.
Note | LPM may delete files that you want to keep. You should act immediately when you receive the LogPartitionLowWaterMarkExceeded alert. |
Trigger alert when following condition met: Log Partition Used Disk Space Exceeds High Water Mark (95%) |
|
This alert occurs when the LogPartitionLowWaterMarkExceeded event gets generated. This indicates that the percentage of used disk space in the log partition has exceeded the configured low water mark.
Note | Be aware that this alert is an early warning. The administrator should start freeing up disk space. Using RTMT/TLC, you can collect trace/log files and delete them from the server. The administrator should adjust the number of trace files that are kept to avoid hitting the low water mark again. |
Trigger alert when following condition met: Log Partition Used Disk Space Exceeds Low Water Mark (90%) |
|
This alert occurs when the percentage of available disk space on the active partition is lower than the configured value.
Trigger alert when following condition met: Active Partition available diskspace below (4%) |
|
RTMT monitors virtual memory usage. When memory runs low, a LowAvailableVirtualMemory alert is generated.
Trigger alert when following condition met: Available virtual memory below (30%) |
|
This alert occurs when the percentage of available disk space of the inactive partition equals less than the configured value.
Trigger alert when following condition met: Inactive Partition available disk space below (4%) |
|
This alert indicates that the available disk space on the swap partition is low.
Note | The swap partition is part of virtual memory, so low available swap partition disk space means low virtual memory as well. |
Trigger alert when following condition met: Swap Partition available disk space below (10%) |
|
This alert occurs when a remote node cannot be reached.
Note | Unified Communications Manager and IM and Presence Service: The ServerDown alert is generated when the currently active AMC (primary AMC or the backup AMC, if the primary is not available) cannot reach another server in a cluster. This alert identifies network connectivity issues in addition to a server down condition. |
Trigger alert when following condition met: ServerDown occurred |
|
This alert occurs when the SparePartitionHighWaterMarkExceeded event gets generated. This indicates that the percentage of used disk space in the spare partition exceeds the configured high water mark.
Trigger alert when following condition met: Spare Partition Used Disk Space Exceeds High Water Mark (95%) |
|
This alert occurs when the SparePartitionLowWaterMarkExceeded event gets generated. This indicates that the percentage of used disk space in the spare partition has exceeded the low water mark threshold.
Trigger alert when following condition met: Spare Partition Used Disk Space Exceeds Low Water Mark (90%) |
|
This alert occurs when the SyslogSeverityMatchFound event gets generated. This indicates that a syslog message with the matching severity level exists.
Trigger alert when following condition met: SyslogSeverityMatchFound event generated |
|
This alert occurs when the SyslogStringMatchFound event gets generated. The alert indicates that a syslog message with the matching search string exists.
Trigger alert when following condition met: SyslogStringMatchFound event generated |
|
Trigger alert when following condition met: SystemVersionMismatched occurred |
|
This alert occurs when the TotalProcessesAndThreadsExceededThreshold event gets generated. The alert indicates that the current total number of processes and threads exceeds the maximum number of tasks that are configured for the Cisco RIS Data Collector Service Parameter. This situation could indicate that a process is leaking or that a process has thread leaking.
Trigger alert when following condition met: TotalProcessesAndThreadsExceededThreshold event generated |
|
This alert occurs when the BeginThrottlingCallListBLFSubscriptions event gets generated. This indicates that the Cisco Unified Communications Manager initiated a throttling of the CallList BLF Subscriptions to prevent a system overload.
Trigger alert when following condition met: BeginThrottlingCallListBLFSubscriptions event generated |
|
Trigger alert when following condition met: CallAttemptBlockedByPolicy event(s) generated. |
|
This alert occurs when the percentage of CPU load on a call processing server exceeds the configured percentage for the configured time.
If the administrator takes no action, high CPU pegging can lead to a Cisco Unified Communications Manager crash, especially in CallManager service. The CallProcessingNodeCpuPegging alert gives you time to work proactively to avoid a crash.
During CPU usage spikes, other alarms that may be issued in addition to the CallProcessingNodeCpuPegging alert include: CoreDumpFound, CriticalServiceDown, SDLLinkOutOfService, and NumberOfRegisteredPhonesDropped alarms.
Note | Cisco Unified Communications Manager VMware installations can experience high CPU usage spikes while performing tasks such as DRF backups and Bulk Administration Tool exports. The processes that are commonly responsible for CPU usage spikes are gzip and DRFLocal. If your system is generating CallProcessingNodeCpuPegging alarms, add an additional vCPU for the support of 7500 Cisco Unified Communications Manager users following the Open Virtualization Archives (OVA) template specifications for your system. |
Trigger alert when following condition met: Processor load over (90%) |
|
Trigger alert only when value constantly below or over threshold for 60 seconds |
|
Trigger alert when following condition met: CARSchedulerJobFailed event generated. |
|
Trigger alert when following condition met: CARIDSEngineCritical event generated. |
|
Trigger alert when following condition met: CARIDSEngineFailure event generated. |
|
This alert gets raised when the CDR Agent cannot send CDR files from a Cisco Unified Communications Manager node to a CDR repository node within the Cisco Unified Communications Manager cluster.
Trigger alert when following condition met: CDRAgentSendFileFailed event generated |
|
This alert gets raised when FTP delivery of CDR files to the outside billing server fails.
Trigger alert when following condition met: CDRFileDeliveryFailed event generated |
|
This alert gets raised when the high water mark for CDR files gets exceeded. It also indicates that some successfully delivered CDR files got deleted.
Trigger alert when following condition met: CDRHighWaterMarkExceeded event generated |
|
This alarm gets raised when the CDR files disk usage exceeds the maximum disk allocation. It also indicates that some undelivered files got deleted.
Trigger alert when following condition met: CDRMaximumDiskSpaceExceeded event generated |
|
Trigger alert when following condition met: CiscoElmNotConnected event generated. |
|
Trigger alert when following condition met: CiscoGraceTimeLeft event generated. |
|
Trigger alert when following condition met: CiscoNoProvisionTimeout event generated. |
|
Trigger alert when following condition met: CiscoSystemInDemo event generated. |
|
Trigger alert when following condition met: CiscoSystemInOverage event generated. |
|
Trigger alert when following condition met: CiscoSystemSecurityMismatch event generated. |
|
The AverageExpectedDelay counter represents the current average expected delay to handle any incoming message. If the value exceeds the value that is specified in Code Yellow Entry Latency service parameter, the CodeYellow alarm gets generated. You can configure the CodeYellow alert to download trace files for troubleshooting purposes.
Trigger alert when following condition met: Cisco CallManager CodeYellowEntry event generated |
|
This alert gets triggered when the IDSReplicationFailure alarm with alarm number 31 occurs, which invokes a proactive procedure to avoid denial of service. This procedure does not impact call processing; you can ignore replication alarms during this process.
The procedure takes up to 60 minutes to finish. Check that RTMT replication status equals 2 on each node to make sure that the procedure is complete. Do not perform a system reboot during this process.
Trigger alert when following condition met: IDSReplicationFailure alarm with alarm number 31 generated |
|
This alert gets triggered when the IDSReplicationFailure alarm with alarm number 32 occurs. An auto recover procedure runs in the background and no action is needed.
The procedure takes about 15 minutes to finish. Check that RTMT replication status equals 2 on each node to make sure the procedure is complete.
Trigger alert when following condition met: IDSReplicationFailure alarm with alarm number 32 generated |
|
Trigger alert when following condition met: EMCCFailedInLocalCluster event(s) generated. |
|
Trigger alert when following condition met: EMCCFailedInRemoteCluster event(s) generated. |
|
This alert gets generated when the number of QRT problems that are reported during the configured time interval exceed the configured value. The default threshold specifies 0 within 60 minutes.
Trigger alert when following condition met: Number of quality reports exceeds 0 times within the last 60 minutes |
|
Trigger alert when following condition met: A connection to the remote ILS server could not be established. |
|
Trigger alert when following condition met: Password Authentication Failure with ILS at remote cluster. |
|
Trigger alert when following condition met: TLS Failure to ILS at remote cluster. |
|
This alarm gets generated when a Cisco Unified Communications Manager attempts to connect to the Cisco IME server, but the IME distributed cache is not currently active.
Ensure that the certificate for the Cisco IME server is provisioned and that the IME distributed cache has been activated through the CLI.
Trigger alert when following condition met: Inactive IME Distributed Cache |
|
This alert indicates that the Cisco Unified Communications Manager servers that use this Cisco IME service have exceed the quota for published direct inward dialing numbers (DIDs) to the IME distributed cache. The alert includes the name of the Cisco IME server as well as the current and target quota values.
Ensure that you have correctly provisioned the DID prefixes on all of the Cisco Unified Communications Manager servers that use this Cisco IME service.
If you have provisioned the prefixes correctly, you have exceeded the capacity of your Cisco IME service, and you need to configure another service and divide the DID prefixes across the Cisco IME client instances (Cisco Unified Communications Managers) on different Cisco IME services.
Trigger alert when following condition met: VAP over quota |
|
This alert gets generated when Cisco Unified Communications Manager determines that a substantial number of Cisco IME calls fail back to PSTN or fail to be set up due to IP network quality problems. Two types of events trigger this alert:
A large number of the currently active Cisco IME calls have all requested fallback or have fallen back to the PSTN.
A large number of the recent call attempts have gone to the PSTN and not been made over IP.
When you receive this alert, check your IP connectivity. If no problems exist with the IP connectivity, you may need to review the CDRs, CMRs, and logs from the firewalls to determine why calls have fallen back to the PSTN or have not been made over IP.
This alert gets generated when too many Cisco IME calls that are currently in progress use the same fallback DID and no more DTMF digit sequences exist to allocate to a new Cisco IME call that Cisco Unified Communications Manager is processing. The new call continues, but the call cannot fallback to the PSTN if voice-quality deteriorates.
If this alert gets generated, note the fallback profile that associates with this call. Check that profile in Cisco Unified Communications Manager Administration, and examine the current setting for the "Fallback Number of Correlation DTMF Digits" field. Increase the value of that field by one, and check whether the new value eliminates these alerts. In general, this parameter should be large enough so that the number of simultaneous Cisco IME calls that are made to enrolled numbers that associate with that profile is always substantially less than 10 raised to the power of this number. For example, if you always have fewer than 10,000 simultaneous Cisco IME calls for the patterns that associate with this fallback profile, setting this value to 5 (10 to the power of 5 equals 100,000) should keep Cisco Unified Communications Manager from generating this alert.
However, increasing this value results in a small increase in the amount of time it takes to perform the fallback. As such, you should set the "Fallback Number of Correlation DTMF Digits" field to a value just large enough to prevent this alert from getting generated.
Instead of increasing the value of the DTMF digits field, you can add another fallback profile with a different fallback DID and associate that fallback profile with a smaller number of enrolled patterns. If you use this method, you can use a smaller number of digits.
Trigger alert when following condition met: Cannot allocate fallback identifier |
|
This alert indicates the overall health of the connection to the Cisco IME services for a particular Cisco IME client instance (Cisco Unified Communications Manager). The alert indicates the following states:
0—Unknown. Likely indicates that the Cisco IME service has not been activated.
1—Healthy. Indicates that the Cisco Unified Communications Manager has successfully established a connection to its primary and backup servers for the Cisco IME client instance, if configured.
2—Unhealthy. Indicates that the Cisco IME has been activated but has not successfully completed handshake procedures with the Cisco IME server. Note that this counter reflects the handshake status of both the primary and the secondary IME servers.
Trigger alert when following condition met: VAP Connection Problem |
|
The alert indicates that the Cisco Unified Communications Manager cannot connect to the Cisco IME server because the username and/or password configured on Cisco Unified Communications Manager do not match those configured on the Cisco IME server.
The alert includes the username and password that were used to connect to the Cisco IME server as well as the IP address and name of the target Cisco IME server. To resolve this alert, log into the Cisco IME server and check that the configured username and password match the username and password that are configured in Cisco Unified Communications Manager.
This alert occurs when the number of LocationOutOfResource events exceeds the configure threshold during the configured time interval. This indicates that one or all of audio or video or immersive bandwidth for a location or link is used up.
Trigger alert when following condition met: LocationOutOfResource event generated 5 times within 60 seconds |
|
This indicates that a malicious call exists in Cisco Unified Communications Manager. The malicious call identification (MCID) feature gets invoked.
Trigger alert when following condition met: Malicious call trace generated |
|
This alert occurs when the number of MediaListExhausted events exceeds the configured threshold during the configured time interval. This indicates that all available media resources that are defined in the media list are busy. The default specifies 0 within 60 minutes.
Trigger alert when following condition met: Number of MediaListExhausted events exceeds 0 times within the last 60 minutes |
|
This alert gets triggered when the BRI D-Channel remains out of service.
Trigger alert when following condition met: MGCP DChannel is out-of-service |
|
This alert occurs when the NumberOfRegisteredDevicesExceeded event gets generated.
Trigger alert when following condition met: NumberOfRegisteredDevicesExceeded event generated |
|
This alert occurs when the number of registered gateways in a cluster decreases between consecutive polls.
Trigger alert when following condition met: Number of registered gateway decreased |
|
This alert occurs when the number of registered gateways in the cluster increased between consecutive polls.
Trigger alert when following condition met: Number of registered gateways increased |
|
This alert occurs when the number of registered media devices in a cluster decreases between consecutive polls.
Trigger alert when following condition met: Number of registered media devices decreased |
|
This alert occurs when the number of registered media devices in a cluster increases between consecutive polls.
Trigger alert when following condition met: Number of registered media devices increased |
|
This alert occurs when the number of registered phones in a cluster drops more than the configured percentage between consecutive polls.
Trigger alert when following condition met: Number of registered phones in the cluster drops (10%) |
|
Trigger alert when following condition met: RecordingCallSetupFail event(s) generated |
|
Trigger alert when following condition met: RecordingGatewayRegistrationRejected event(s) generated. |
|
Trigger alert when following condition met: RecordingGatewayRegistrationTimeout event(s) generated. |
|
Trigger alert when following condition met: RecordingGatewaySessionFailed event(s) generated. |
|
Trigger alert when following condition met: RecordingGatewayRegistrationTimeout event(s) generated. |
|
Trigger alert when following condition met: RecordingCallSetupFail event(s) generated. |
|
Trigger alert when following condition met: When number of ast session is more than 250. |
|
This alert occurs when the number of RouteListExhausted events exceeds the configured threshold during the configured time interval. This indicates that all available channels that are defined in the route list are busy. The default specifies 0 within 60 minutes.
Trigger alert when following condition met: Number of RouteListExhausted exceeds 0 times within the last 60 minutes |
|
This alert occurs when the SDLLinkOutOfService event gets generated. This event indicates that the local Cisco Unified Communications Manager cannot communicate with the remote Cisco Unified Communications Manager This event usually indicates network errors or a non-running remote Cisco Unified Communications Manager.
Trigger alert when following condition met: SDLLinkOutOfService event generated |
|
This alert occurs when Cisco Unified Communications Manager cannot establish a TCP connection to a Cisco IME server. This alert typically occurs when the IP address and port of the Cisco IME server are misconfigured in Cisco Unified Communications Manager Administration or when an Intranet connectivity problem exists and prevents the connection from being set up.
Ensure that the IP address and port of the Cisco IME server in the alert are valid. If the problem persists, test the connectivity between the Cisco Unified Communications Manager servers and the Cisco IME server.
This alert occurs when a TLS connection to the Cisco IME service could not be established because the certificate presented by the Cisco IME service has expired or is not in the Cisco Unified Communications Manager CTL.
Ensure that the Cisco IME service certificate has been configured into the Cisco Unified Communications Manager.
Trigger alert when following condition met: UserInputFailure event(s) generated. |
|
This alert indicates that synchronization between the IM and Presence database and the Cisco Presence Engine and a database service has failed (Cisco Login Datastore, Cisco Route Datastore, Cisco Presence Datastore, and Cisco SIP Registration Datastore).
Restart the Cisco Presence Engine service when convenient. See associated error message and log files and consult Cisco TAC if the problem persists.
This alert indicates that the Cisco XCP Config Manager failed to successfully update XCP configuration.
See the Cisco XCP Config Manager logs for the root cause. Contact Cisco TAC for assistance.
This alert indicates that the Cisco XCP Config Manager has regenerated XCP XML files after system halt due to buffer size. The Cisco XCP Router must now be restarted to apply changes.
When it is convenient to do so, restart the Cisco XCP Router.
This alert indicates that the Cisco XCP Config Manager was unable to encrypt the password that is associated with an Inter-cluster Router-to-Router configuration.
When it is convenient to do so, restart the Cisco XCP Config Manager and then restart the Cisco XCP Router.
This alert indicates that the maximum supported concurrent SIP Federation subscriptions or SIP Federation IM sessions has been reached, and the Cisco XCP SIP Federation Connection Manager does not have the resources that are required to handle any addition subscriptions or IM sessions.
Increase the Pre-allocated SIP stack memory Service Parameter for the Cisco XCP SIP Federation Connection Manager. Note: If you are changing this setting, make sure that you have the memory available. If you do not have enough memory, you may have reached the limit of your hardware capability.
This alert indicates that network administrators have banned this Cisco IME server from the network (IME distributed cache ring), making this Cisco IME service fully or partly inoperative. Network administrators rarely ban servers but do so if they detect that the server is being used to launch malicious attacks into the network. If you receive this alert in error, contact TAC immediately.
This alert indicates the number of days that remain until the certificate that is used for the IME distributed cache expires. You must replace the certificate prior to expiration.
Trigger alert when following condition met: Cisco IME distributed cache certificate about to expire. 14 days. |
|
This alert indicates the health of the IME distributed cache. A value of zero (red) means that the IME distributed cache is suffering from a significant problem such as one of the following conditions:
The Cisco IME cannot resolve issues after the network was partitioned. In this case, validation attempts may fail.
The Cisco IME service is not connected to the network at all and is unable to reach the bootstrap servers.
A value of one (yellow) indicates that the Cisco IME network is experiencing minor issues, such as connectivity between bootstrap servers or other Cisco IME network issues. Check for any alarms that may indicate why this counter is 1. A value of two indicates that IME distributed cache is functioning normally and the system is considered healthy.
Trigger alert when following condition met: IME distributed cache failure in states 1: network experience minor issues 0: network in trouble |
|
This alert indicates that the Cisco IME service has lost communication with Cisco IME Config Manager services, such as the Cisco AMC Service or the Cisco CallManager Service.
This alert usually indicates that one of these services has gone down (either intentionally, for maintenance; or unintentionally, due to a service failure or connectivity failure).
Trigger alert when following condition met: SDLLinkOOS event generated |
|
This alert indicates that the administrator enabled the IME distributed cache on the Cisco IME server but omitted the configuration of a valid certificate or configured an incorrect certificate.
Trigger alert when following condition met: Invalid certificate configured |
|
The alert indicates that the Cisco Unified Communications Manager cannot connect to the Cisco IME server, because the username and password that are configured on Cisco Unified Communications Manager do not match those configured on the Cisco IME server.
The alert includes the username and password that were used to connect to the Cisco IME server as well as the IP address and name of the target Cisco IME server. To resolve this alert, log into the Cisco IME server and check that the username and password that are configured match those configured in Cisco Unified Communications Manager.
Trigger alert when following condition met: Invalid or mismatched credentials. |
|
The Cisco IME service generates this alert when the administrators of the Cisco IME network have a message for you.
Trigger alert when following condition met: Message from network administrators |
|
The Cisco IME server generates this alert when a new version of the Cisco IME server software is required. This alert repeats until you perform the upgrade. To obtain more information about the software update, go to the Cisco website. You should install critical updates within days of receiving this alert.
These upgrades address security vulnerabilities or key functional outages. In some cases, if you do not apply a critical upgrade immediately, the Cisco IME server may become unable to connect to the network.
Trigger alert when following condition met: Software update required |
|
The Cisco IME server generates this alert when the administrator changes the password that is used to generate the validation tickets.
Verify that an authorized administrator changed the password. Unauthorized changes may indicate compromise to the administrative interfaces on the Cisco IME service. If you determine that unauthorized changes have been made, change the administrative passwords on the Cisco IME server immediately to prevent further unauthorized access. To change the administrative password, type set password admin in the Cisco IME server CLI.
Trigger alert when following condition met: Ticket password changed |
|
This alert indicates the number of pending validations on the Cisco IME server. This number provides an indicator of the backlog of work on the Cisco IME server.
(Cisco Unity Connection cluster configuration) This alert is generated when the servers of a Cisco Unity Connection cluster cannot communicate with each other (for example, when the network connection is lost).
Trigger alert when following condition met: NoConnectionToPeer event generated |
|
(Cisco Unity Connection cluster configuration) This alert is generated in the following conditions:
When the server with the Secondary status automatically changes its status to Primary (for example, when a critical failure occurs on the server with the Primary status) and assumes responsibility for handling the voice messaging functions and database for the cluster. This alert signals that the following events occurred:
When the server that stopped functioning (described above) is brought back online and the server status automatically changes so that both servers resume sharing responsibility for handling the voice messaging functions and replication.
Trigger alert when following condition met: AutoFailoverSucceeded event generated |
|
(Cisco Unity Connection cluster configuration) This alert is generated in the following conditions:
When the server with the Secondary status attempts to automatically change its status to Primary (for example, when a critical failure occurs on the server with the Primary status), but the automatic server status change fails so that the server with the Secondary status keeps the Secondary status.
When a server that has stopped functioning (for example, a critical failure occurred) is not brought back online. Only one server in the cluster is functioning.
Trigger alert when following condition met: AutoFailoverFailed event generated |
|
(Cisco Unity Connection cluster configuration) This alert is generated when the problem that caused the server with the Primary status to stop functioning (causing the server with the Secondary status to change its status to Primary) is resolved and both servers are again online. Then, the servers automatically change status so that the server that had stopped functioning has the Primary status and the other server has the Secondary status.
Trigger alert when following condition met: AutoFailbackSucceeded event generated |
|
(Cisco Unity Connection cluster configuration): This alert occurs when the publisher node is not online and the server with the Primary status fails to automatically change status.
Trigger alert when following condition met: AutoFailbackFailed event generated |
|
When a Cisco Unity Connection cluster is configured, if two servers cannot communicate with each other, they will both have the Primary status at the same time (a "split brain" condition), handle voice messaging functions, save messages to their own message stores, but not perform any replication. Users can retrieve their messages, but only one server knows that these messages have been retrieved.
When both servers are able to communicate with each other, they resolve this split brain condition by determining the correct contents and state of each user mailbox:
Whether new messages that have been received.
Whether MWIs for new messages have already been sent.
Which messages have been listened to.
Which messages have been deleted.
If the resolution of the split brain condition fails, this alert occurs.
Trigger alert when following condition met: SbrFailed event generated |
|
This alert is generated when the hard disk usage on the Cisco Unity Connection server reaches ten percent below the percentage limit that the window in Cisco Unity Connection Administration specifies. For example, with a capacity threshold limit of 95 percent, the alert gets triggered when usage reaches at least 85 percent.
Trigger alert when following condition met: DiskConsumptionCloseToCapacityThreshold event generated |
|
This alert is generated when the hard disk usage on the Cisco Unity Connection server meets or exceeds the percentage limit that the window in Cisco Unity Connection Administration specifies.
Trigger alert when following condition met: DiskConsumptionExceedsCapacityThreshold event generated |
|
Cisco Unity Connection licenses several features, including users and ports. The system enforces these licenses. If a customer uses a time-limited license to sample a feature, this license includes an expiration date. Before the license expiration date is reached, the system sends a message, and this alert occurs. The log indicates how many days remain until the license expires.
Trigger alert when following condition met: LicenseExpirationWarning event generated |
|
Cisco Unity Connection licenses several features, including users and ports. The system enforces these licenses. If a customer uses a time-limited license to sample a feature, this license includes an expiration date. When the license expiration date is reached, the license becomes invalid, and this alert occurs.
Trigger alert when following condition met: LicenseExpired event generated |
|