Table Of Contents
Performance Objects and Counters
Cisco ACB Device
Cisco Analog Access
Cisco Annunciator Device
Cisco CallManager
Cisco CallManager System Performance
Cisco CTI Manager
Cisco Extension Mobility
Cisco Gatekeeper
Cisco H.323
Cisco Hunt Lists
Cisco HW Conference Bridge Device
Cisco IP Manager Assistant Service
Cisco Lines
Cisco Locations
Cisco Media Streaming Application
Cisco Messaging Interface
Cisco MGCP BRI Device
Cisco MGCP FXO Device
Cisco MGCP FXS Device
Cisco MGCP Gateways
Cisco MGCP PRI Device
Cisco MGCP T1 CAS Device
Cisco MOH Device
Cisco MTP Device
Cisco Phones
Cisco QSIG Features
Cisco SIP
Cisco SW Conf Bridge Device
Cisco TcdSrv
Cisco TFTP Server
Cisco Transcode Device
Cisco Video Conference Bridge
Cisco WebDialer
Where to Find More Information
Performance Objects and Counters
This appendix comprises a complete list, including descriptions, of the performance objects and their associated counters that are used in the Cisco CallManager bundled applet, Real-Time Monitoring Tool (RTMT), and in the Microsoft Performance (also known as PerfMon) application. For more detailed about objects and counters, see the "Performance Objects and Counters" section on page 2-1 and "Microsoft Performance" section on page 12-1.
The following sections provide tables that comprise the performance objects and their associated counters, including descriptions, that are used in Cisco CallManager Serviceability and Microsoft Performance:
•
Cisco ACB Device
•Cisco Analog Access
•Cisco Annunciator Device
•Cisco CallManager
•Cisco CallManager System Performance
•Cisco CTI Manager
•Cisco Extension Mobility
•Cisco Gatekeeper
•Cisco H.323
•Cisco Hunt Lists
•Cisco HW Conference Bridge Device
•Cisco IP Manager Assistant Service
•Cisco Lines
•Cisco Locations
•Cisco Media Streaming Application
•Cisco Messaging Interface
•Cisco MGCP BRI Device
•Cisco MGCP FXS Device
•Cisco MGCP Gateways
•Cisco MGCP PRI Device
•Cisco MGCP T1 CAS Device
•Cisco MOH Device
•Cisco MTP Device
•Cisco Phones
•Cisco SIP
•Cisco SW Conf Bridge Device
•Cisco TcdSrv
•Cisco TFTP Server
•Cisco Transcode Device
•Cisco Video Conference Bridge
•Cisco WebDialer
•Where to Find More Information
Cisco ACB Device
The Cisco Application-Controlled Bridge (ACB) Device object provides information about registered Cisco application-controlled bridge devices.
Table C-1 Cisco ACB Device
Counters
|
Counter Descriptions
|
ConferencesActive
|
This counter represents the number of currently active conferences for application-controlled bridge device. This counter increases when the application requests that Cisco CallManager initiate a conference, not when the first call is connected to bridge.
|
ConferencesCompleted
|
This counter represents the number of conferences that have been allocated and released on application-controlled bridge device. A conference starts when the application requests that Cisco CallManager initiate a conference. The conference completes when the application requests that Cisco CallManager terminate a conference.
|
IVRSessionsActive
|
This counter represents the number of currently active (in use) interactive voice response (IVR) sessions on application-controlled bridge device. Each IVR session uses one resource.
|
IVRSessionsCompleted
|
This counter represents the number of IVR sessions that have been allocated and released (completed) on application-controlled bridge device.
|
ResourceActive
|
This counter represents the number of resources that are currently active (in use) for application-controlled bridge device.
|
ResourceAvailable
|
This counter represents the number of resources that are not active and are still available to be used at the current time for application-controlled bridge device.
|
ResourceReserved
|
This counter represents the number of resources that have been reserved for application-controlled bridge device. A reserved resource represents one that the application has dedicated to a particular ongoing conference.
|
ResourceTotal
|
This counter represents the total number of resources that are configured for application-controlled bridge device. The total number of resources equals the sum of the ResourceAvailable and ResourceReserved counters.
|
Cisco Analog Access
The Cisco Analog Access object provides information about registered Cisco Analog Access gateways.
Table C-2 Cisco Analog Access
Counters
|
Counter Descriptions
|
OutboundBusyAttempts
|
This counter represents the total number of times that Cisco CallManager attempts a call through the Analog Access gateway when all ports were busy.
|
PortsActive
|
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.
|
PortsOutOfService
|
This counter represents the number of ports that are currently out of service. Counter applies only to loop-start and ground-start trunks.
|
Cisco Annunciator Device
The Cisco Annunciator Device object provides information about registered Cisco annunciator devices.
Table C-3 Cisco Annunciator Device
Counters
|
Counter Descriptions
|
OutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate an annunciator resource from an annunciator device and failed; for example, because all resources were already in use.
|
ResourceActive
|
This counter represents the total number of annunciator resources that are currently active (in use) for an annunciator device.
|
ResourceAvailable
|
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.
|
ResourceTotal
|
This counter represents the total number of annunciator resources that are configured for an annunciator device.
|
Cisco CallManager
The Cisco CallManager object provides information about calls, applications, and devices that are registered with the Cisco CallManager.
Table C-4 Cisco CallManager
Counters
|
Counter Descriptions
|
ACBConferencesActive
|
This counter represents the total number of active conferences on all ACB devices that are registered with a Cisco CallManager. This counter increases when the application requests that Cisco CallManager initiate a conference (not when the first call connects to bridge).
|
ACBConferenceCompleted
|
This counter represents the total number of conferences that have been allocated and released on all ACB devices that are registered with a Cisco CallManager. A conference starts when the application requests that Cisco CallManager initiate a conference. The conference completes when the application requests that Cisco CallManager terminate a conference.
|
ACBIVRSessionsActive
|
This counter represents the total number of active (in use) IVR sessions on all ACB devices that are registered with a Cisco CallManager.
|
ACBIVRSessionsCompleted
|
This counter represents the total number of IVR sessions that have been allocated and released (completed) on all ACB devices. An IVR session designates a temporary, one-party conference before the participant joins a regular conference.
|
ACBResourceActive
|
This counter represents the total number of resources that are currently active (in use) on all ACB devices that are registered with a Cisco CallManager.
|
ACBResourceAvailable
|
This counter represents the total number of resources that are not in use and are available to be allocated on all ACB devices that are registered with a Cisco CallManager.
|
ACBResourceReserved
|
This counter represents the total number of reserved resources for all ongoing conferences on all ACB devices that are registered with a Cisco CallManager. A reserved resource designates one that the application has dedicated to a particular ongoing conference. The sum of the counters ACBResourceReserved and ACBResourceAvailable equal the value for the ACBResourceTotal counter.
|
ACBResourceTotal
|
This counter represents the total number of resources that are provided by all ACB devices registered with a Cisco CallManager. The total number of resources equals the sum of the ACBResourceAvailable and the ACBResourceReserved counters.
|
AnnunciatorOutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate an annunciator resource from those that are registered to a Cisco CallManager when none were available.
|
AnnunciatorResourceActive
|
This counter represents the total number of annunciator resources that are currently in use on all annunciator devices that are registered with a Cisco CallManager.
|
AnnunciatorResourceAvailable
|
This counter represents the total number of annunciator resources that are not active and are currently available.
|
AnnunciatorResourceTotal
|
This counter represents the total number of annunciator resources that are provided by all annunciator devices that are currently registered with Cisco CallManager.
|
AuthenticatedCallsActive
|
This counter represents the number of authenticated calls that are currently active (in use) on Cisco CallManager. 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 CallManager.
|
AuthenticatedCallsCompleted
|
This counter represents the number of authenticated calls that connected and subsequently disconnected through Cisco CallManager. 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 CallManager.
|
AuthenticatedRegisteredPhones
|
This counter represents the total number of authenticated phones that are registered to Cisco CallManager. An authenticated phone uses the TLS authenticated Skinny protocol signaling with Cisco CallManager.
|
BRIChannelsActive
|
This counter represents the number of BRI voice channels that are in an active call on this Cisco CallManager.
|
BRISpansInService
|
This counter represents the number of BRI spans that are currently available for use.
|
CallManagerHeartBeat
|
This counter represents the heartbeat of Cisco CallManager. This incremental count indicates that Cisco CallManager is up and running. If the count does not increment, that indicates that Cisco CallManager is down.
|
CallsActive
|
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 CallManager.
|
CallsAttempted
|
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. Some call attempts during feature operations (such as transfer and conference) that are considered attempted calls.
|
CallsCompleted
|
This counter represents the number of calls that were actually connected (a voice path or video stream was established) through Cisco CallManager. This number increases when the call terminates.
|
CallsInProgress
|
This counter represents the number of voice or video calls that are currently in progress on Cisco CallManager, including all active calls. When a phone goes off hook, this action creates a call in progress until it goes back on hook. When all voice or video calls that are in progress are connected, the number of CallsInProgress equate the number of CallsActive.
|
FXOPortsActive
|
This counter represents the number of FXO ports that are currently in use (active) on a Cisco CallManager.
|
FXOPortsInService
|
This counter represents the number of FXO ports that are currently available for use in the system.
|
FXSPortsActive
|
This counter represents the number of FXS ports that are currently in use (active) on a Cisco CallManager.
|
FXSPortsInService
|
This counter represents the number of FXS ports that are currently available for use in the system.
|
HuntListsInService
|
This counter represents the number of hunt lists that are currently in service on Cisco CallManager.
|
HWConferenceActive
|
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 CallManager.
|
HWConferenceCompleted
|
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 CallManager 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.
|
HWConferenceOutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate a hardware conference resource from those that are registered to a Cisco CallManager when none were available.
|
HWConferenceResourceActive
|
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 CallManager. System considers conference to be active when one or more calls are connected to a bridge.
|
HWConferenceResourceAvailable
|
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 registered with this Cisco CallManager. Each conference resource represents the availability of three available full-duplex streams on this Cisco CallManager. One resource equals one stream.
|
HWConferenceResourceTotal
|
This counter represents the number of active conferences on all hardware conference devices that are registered with Cisco CallManager.
|
InitializationState
|
This counter represents the current state of the Cisco CallManager initialization. The following values specify initialization states: 1-Database; 2-Regions; 3-Locations; 4-Calling Search Space; 5-Time Of Day; 6-AAR Neighborhoods; 7-Digit Analysis; 8-Route Plan; 9-Call Control; 10-Supplementary Services; 11-Directory; 12-SDL Link; 13-Device; 100-Initialization Complete. Not all states display using this counter. This is not an error; it simply indicates that the state(s) were processed to completion within the refresh period of the performance monitor.
|
MOHTotalMulticastResources
|
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 CallManager.
|
MOHMulticastResourceActive
|
This counter represents the total number of multicast MOH resources that are currently in use (active) on all MOH servers that are registered with a Cisco CallManager.
|
MOHMulticastResourceAvailable
|
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 CallManager.
|
MOHOutOfResources
|
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 CallManager were already active.
|
MOHTotalUnicastResources
|
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 CallManager. Each MOH unicast resource uses one stream.
|
MOHUnicastResourceActive
|
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 CallManager. Each MOH unicast resource uses one stream.
|
MOHUnicastResourceAvailable
|
This counter represents the total number of unicast MOH resources that are currently available on all MOH servers that are registered with Cisco CallManager. Each MOH unicast resource uses one stream.
|
MTPOutOfResources
|
This counter represents the total number of times Cisco CallManager attempted but failed to allocate an MTP resource from one MTP device that is registered with Cisco CallManager. This also means that no transcoders were available to act as MTPs.
|
MTPResourceActive
|
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 CallManager. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call.
|
MTPResourceAvailable
|
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 CallManager. Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call.
|
MTPResourceTotal
|
This counter represents the total number of media termination point (MTP) resources that are provided by all MTP devices that are currently registered with Cisco CallManager.
|
PRIChannelsActive
|
This counter represents the number of PRI voice channels that are in an active call on a Cisco CallManager.
|
PRISpansInService
|
This counter represents the number of PRI spans that are currently available for use.
|
RegisteredAnalogAccess
|
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.
|
RegisteredHardwarePhones
|
This counter represents the number of Cisco hardware IP phones (for example, models Cisco IP Phone 7960, 7940, 7910, and so on.) that are currently registered in the system.
|
RegisteredMGCPGateway
|
This counter represents the number of MGCP gateways that are currently registered in the system.
|
RegisteredOtherStationDevices
|
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 voice-mail port).
|
SWConferenceActive
|
This counter represents the number of active conferences on all software conference devices that are registered with Cisco CallManager.
|
SWConferenceCompleted
|
This counter represents the total number of conferences that used a software conference bridge that was allocated from a Cisco CallManager 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.
|
SWConferenceOutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate a software conference resource from those that are registered to Cisco CallManager when none were available. Counter includes failed attempts to add a new participant to an existing conference.
|
SWConferenceResourceActive
|
This counter represents the total number of conference resources that are in use on all software conference devices that are registered with Cisco CallManager. The system considers a conference to be active when one or more calls connect to a bridge.
|
SWConferenceResourceAvailable
|
This counter represents the number of new software-based conferences that can be started at the same time, for Cisco CallManager. You must have a minimum of three streams available for each new conference.
|
SWConferenceResourceTotal
|
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 CallManager.
|
T1SpansInService
|
This counter represents the number of T1 CAS spans that are currently available for use.
|
T1ChannelsActive
|
This counter represents the number of T1 CAS voice channels that are in an active call on a Cisco CallManager.
|
TranscoderOutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate a transcoder resource from a transcoder device that is registered to a Cisco CallManager when none were available.
|
TranscoderResourceActive
|
This counter represents the total number of transcoders that are in use on all transcoder devices that are registered with Cisco CallManager. A transcoder in use represents one transcoder resource that has been allocated for use in a call. Each transcoder resource uses two streams.
|
TranscoderResourceAvailable
|
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 CallManager. Each transcoder resource uses two streams.
|
TranscoderResourceTotal
|
This counter represents the total number of transcoder resources that are provided by all transcoder devices that are currently registered with Cisco CallManager.
|
VCBConferencesActive
|
This counter represents the total number of active video conferences on all video conference bridge devices that are registered with Cisco CallManager.
|
VCBConferencesAvailable
|
This counter represents the total number of new video conferences on all video conference bridge devices that are registered with Cisco CallManager.
|
VCBConferencesCompleted
|
This counter represents the total number of video conferences that used a video conference bridge that are allocated from Cisco CallManager 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.
|
VCBConferencesTotal
|
This counter represents the total number of video conferences that are supported on all video conference bridge devices that are registered with Cisco CallManager.
|
VCBOutOfResources
|
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.
|
VCBOutOfConferences
|
This counter represents the total number of times that Cisco CallManager attempted to allocate a video conference resource from those that are registered to Cisco CallManager when none were available.
|
VCBResourceActive
|
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 CallManager.
|
VCBResourceAvailable
|
This counter represents the total number of video conference resources that are not active and are currently available.
|
VCBResourceTotal
|
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 CallManager.
|
VideoCallsActive
|
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 CallManager.
|
VideoCallsCompleted
|
This represents the number of video calls that were actually connected with video streams and then released.
|
VideoOutOfResources
|
This counter represents the total number of times that Cisco CallManager attempted to allocate a video-streaming resource from one of the video conference bridge devices that is registered to Cisco CallManager when none were available.
|
Cisco CallManager System Performance
The Cisco CallManager System Performance object provides system performance information about Cisco CallManager.
Table C-5 Cisco CallManager System Performance
Counters
|
Counter Descriptions
|
AverageExpectedDelay
|
This counter represents the current average expected delay before any incoming message gets handled.
|
CallsRejectedDueToCallThrottling
|
This counter represents the total number of calls that were rejected since the start of service due to call throttling.
|
CallThrottlingGenericCounter1
|
This counter represents a generic counter that is used for call-throttling purpose.
|
CallThrottlingGenericCounter2
|
This counter represents a generic counter that is used for call-throttling purpose.
|
CallThrottlingGenericCounter3
|
This counter represents a generic counter that is used for call-throttling purpose.
|
CodeRedEntryExit
|
This counter indicates whether Cisco CallManager has entered or exited a Code Red state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry).
|
CodeYellowEntryExit
|
This counter indicates whether Cisco CallManager has entered or exited a Code Yellow state (call-throttling mode). Valid values include 0 (Exit) and 1 (Entry).
|
EngineeringCounter1
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter2
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter3
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter4
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter5
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter6
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter7
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
EngineeringCounter8
|
Do not use this counter unless directed by a Cisco Engineering Special build. Cisco uses information in this counter for diagnostic purposes.
|
QueueSignalsPresent 1-High
|
This counter indicates the number of high-priority signals in the Cisco CallManager queue. High priority signals include timeout events, internal Cisco CallManager KeepAlives, certain gatekeeper events, and internal process creation, among other events. A large number of high priority events will cause degraded performance on Cisco CallManager, result in slow call connection or loss of dial tone. Use this counter in conjuction with the QueueSignalsProcessed 1-High counter to determine the processing delay on Cisco CallManager.
|
QueueSignalsPresent 2-Normal
|
This counter indicates the number of normal-priority signals in the Cisco CallManager 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 CallManager, 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 CallManager. 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.
|
QueueSignalsPresent 3-Low
|
This counter indicates the number of low-priority signals in the Cisco CallManager 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.
|
QueueSignalsPresent 4-Lowest
|
This counter indicates the number of lowest priority signals in the Cisco CallManager 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.
|
QueueSignalsProcessed 1-High
|
This counter indicates the number of high-priority signals that are processed by Cisco CallManager for each 1-second interval. Use this counter in conjuction with the QueueSignalsPresent 1-High counter to determine the processing delay on this queue.
|
QueueSignalsProcessed 2-Normal
|
This counter indicates the number of normal-priority signals that are processed by Cisco CallManager for each 1-second interval. Use this counter in conjuction 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.
|
QueueSignalsProcessed 3-Low
|
This counter indicates the number of low-priority signals that are processed by Cisco CallManager for each 1-second interval. Use this counter in conjuction 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.
|
QueueSignalsProcessed 4-Lowest
|
This counter indicates the number of lowest priority signals that are processed by Cisco CallManager for each 1-second interval. Use this counter in conjuction with the QueueSignalsPresent 4-Lowest counter to determine the processing delay on this queue. The number of signals processed gives an indication of how many devices began the Cisco CallManager registration process in this time interval.
|
QueueSignalsProcessed Total
|
This counter provides a sum total of all queue signals that are processed by Cisco CallManager for each 1-second period for all queue levels: high, normal, low, and lowest.
|
SkinnyDevicesThrottled
|
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 time.
|
Cisco CTI Manager
The Cisco CTI Manager object provides information about Cisco CTI Manager.
Table C-6 Cisco CTI Manager
Counters
|
Counter Descriptions
|
CcmLinkActive
|
This counter represents the total number of active Cisco CallManager links. CTI Manager maintains links to all active Cisco CallManagers in the cluster.
|
CTIConnectionActive
|
This counter represents the total number of CTI clients that are currently connected to the CTI Manager. This counter increases by one when new connection is established and decreases by one when a connection is released.The CTI Manager service parameter MaxCTIConnections determines the maximum number of active connections.
|
DevicesOpen
|
This counter represents the total number of devices that are configured in Cisco CallManager that CTI applications control and/or monitor. Devices include hardware IP phones, CTI ports, CTI route points, and so on.
|
LinesOpen
|
This counter represents the total number of lines that are configured in Cisco CallManager that control and/or monitor CTI applications.
|
QbeVersion
|
This counter represents the version number of the Quick Buffer Encoding (QBE) interface that the CTI Manager uses.
|
Cisco Extension Mobility
The Cisco Extension Mobility object provides information about the extension mobility application.
Table C-7 Cisco Extension Mobility Application
Counters
|
Counter Descriptions
|
RequestsHandled
Note Prior to Cisco CallManager Release 4.0, this counter was called Num. of requests handled.
|
This counter represents the total number of HTTP requests that the extension mobility 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.
|
RequestsInProgress
Note Prior to Cisco CallManager Release 4.0, this counter was called Current Sessions.
|
This counter represents the number of HTTP requests that are currently being handled by the extension mobility. 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 typcial logout also results in two HTTP requests.
|
Cisco Gatekeeper
The Cisco Gatekeeper object provides information about registered Cisco gatekeeper devices.
Table C-8 Cisco Gatekeeper
Counters
|
Counter Descriptions
|
ACFsReceived
|
This counter represents the total number of RAS Admission Confirm messages that are received from the configured gatekeeper and its alternate gatekeepers.
|
ARQsAttempted
|
This counter represents the total number of RAS Admission Request messages that are attempted by using the configured gatekeeper and its alternate gatekeepers.
|
RasRetries
|
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.
|
VideoOutOfResources
|
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.
|
Cisco H.323
The Cisco H.323 object provides information about registered Cisco H.323 devices.
Table C-9 Cisco H.323
Counters
|
Counter Descriptions
|
CallsActive
|
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 connected.
|
CallsAttempted
|
This counter represents the total number of calls that have been attempted on a device, including both successful and unsuccessful call attempts.
|
CallsCompleted
|
This counter represents the total number of successful calls that were made from a device.
|
CallsInProgress
|
This counter represents the number of calls that are currently in progress on a device.
|
VideoCallsActive
|
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 CallManager; in other words, the number of calls that actually have video-streaming connections on a Cisco CallManager.
|
VideoCallsCompleted
|
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 CallManager. This number increases when the call terminates.
|
Cisco Hunt Lists
The Cisco Hunt Lists object provides information about the hunt lists that are defined in Cisco CallManager administration.
Table C-10 Cisco Hunt Lists
Counters
|
Counter Descriptions
|
CallsAbandoned
|
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.
|
CallsActive
|
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 andanswered, and to which a voice path connects.
|
CallsBusyAttempts
|
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.
|
CallsInProgress
|
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 andthat 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.
|
CallsRingNoAnswer
|
This counter represents the total number of calls through a hunt list that rang but that called parties did not answer.
|
HuntListInService
|
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. A hunt list could be out of service because the hunt list is not running on a primary Cisco CallManager based on its Cisco CallManager Group or because the hunt list has been disabled in Cisco CallManager Administration.
|
MembersAvailable
|
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 be 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.
|
Cisco HW Conference Bridge Device
The Cisco HW Conference Bridge Device object provides information about registered Cisco hardware conference bridge devices.
Note The HWConferenceActiveParticipants counter has been deleted.
Table C-11 Cisco HW Conference Bridge Device
Counters
|
Counter Descriptions
|
HWConferenceActive
|
This counter represents the number of conferences that are currently active (in use) on a HW conference bridge device.
|
HWConferenceCompleted
|
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.
|
OutOfResources
|
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.
|
ResourceActive
|
This counter represents the number of resources that are currently in use (active) for this HW conference device.
|
ResourceAvailable
|
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.
|
ResourceTotal
|
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.
|
Cisco IP Manager Assistant Service
The Cisco IP Manager Assistant (IPMA) Service object provides information about the Cisco IP Manager Assistant application.
Table C-12 Cisco IP Manager Assistant Service
Counters
|
Counter Descriptions
|
AssistantsActive
Note This counter was formerly called Assistants active.
|
This counter represents the number of assistant consoles that are currently active. An active assistant console exists when an assistant is logged in from his or her assistant console desktop application.
|
LinesOpen
Note This counter was formerly called Num. of lines open.
|
This counter represents the number of phone lines that the Cisco IPMA application opened. An open phone line exists when the IPMA application assumes line control from CTI.
|
ManagersActive
Note This counter was formerly called Managers active.
|
This counter represents the current number of managers that the Cisco IPMA is servicing.
|
SessionsCurrent
Note This counter was formerly called Current session.
|
This counter represents the total number of managers assistants that are currently using the Cisco IPMA application. Each manager and each assistant constitutes an active session, so for one manager/assistant pair, this counter would reflect two sessions.
|
Cisco Lines
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.
Table C-13 Cisco Lines
Counters
|
Counter Descriptions
|
Active
|
This counter represents the state of the line, either active or not active. A zero indicates 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 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.
|
Cisco Locations
The Cisco Location object provides information about locations that are defined in Cisco CallManager.
Table C-14 Cisco Locations
Counters
|
Counter Descriptions
|
BandwidthAvailable
|
This counter represents the current bandwidth in a given location. A value of 0 indicates that no bandwidth is available.
|
BandwidthMaximum
|
This counter represents the maximum bandwidth that is available in a given location. A value of 0 indicates that infinite bandwidth is available.
|
CallsInProgress
|
This counter represents the number of calls currently in progress on a particular Cisco CallManager.
|
OutOfResources
|
This counter represents the total number of times that a call on a particular Cisco CallManager through the location failed due to lack of bandwidth.
|
VideoBandwidthAvailable
|
This counter represents the bandwidth that is currently available for video in the location where the person who initiated the video conference resides. A value of 0 indicates that no bandwidth is available.
|
VideoBandwidthMaximum
|
This counter represents the maximum bandwidth that is available for video in the location where the person who initiated the video conference resides. A value of 0 indicates that no bandwidth is allocated for video.
|
VideoOutOfResources
|
This counter represents the total number of failed video-stream requests (most likely due to lack of bandwidth) in the location where the person who initiated the video conference resides.
|
Cisco Media Streaming Application
The Cisco Media Streaming Application object provides information about the registered MTPs, MOH servers, conference bridge servers, and annunciators.
Note There will be one object for each Cisco CallManager in the Cisco CallManager group associated with the device pool that the annunciator device is configured to use.
Table C-15 Cisco Media Streaming Application
Counter
|
Counter Descriptions
|
ANNConnectionsLost
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco CallManager connection was lost.
|
ANNConnectionState
|
For each Cisco CallManager associated with an annunciator, this counter represents the current registration state to Cisco CallManager; 0 indicates no registration to Cisco CallManager; 1 indicates registration to the primary Cisco CallManager; 2 indicates connection to the secondary Cisco CallManager (connected to Cisco CallManager but not registered until the primary Cisco CallManager connection fails).
|
ANNConnectionsTotal
|
This counter represents the total number of annunciator instances that have been started since the Cisco IP Voice Media Streaming Application service started.
|
ANNInstancesActive
|
This counter represents the number of actively playing (currently in use) announcements .
|
ANNStreamsActive
|
This counter represents the total number of currently active simplex (one direction) streams for all connections. Each stream direction counts as one stream. There is one internal stream providing the audio input and another output stream to the endpoint device.
|
ANNStreamsAvailable
|
This counter represents the remaining number of streams 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 started.
|
ANNStreamsTotal
|
This counter represents the total number of simplex (one direction) streams that have been connected to the annunciator device since the Cisco IP Voice Media Streaming Application service started.
|
CFBConferencesActive
|
This counter represenst the number of active (currently in use) conferences.
|
CFBConferencesTotal
|
This counter represents the total number of conferences that have been started since the Cisco IP Voice Media Streaming Application service started.
|
CFBConnectionsLost
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco CallManager connection was lost.
|
CFBConnectionState
|
For each Cisco CallManager associated with a SW Conference Bridge, this counter represents the current registration state to Cisco CallManager; 0 indicates no registrationto Cisco CallManager; 1 indicates registration to the primary Cisco CallManager; 2 indicates connection to the secondary Cisco CallManager (connected to Cisco CallManager but not registered until the primary Cisco CallManager connection fails).
|
CFBStreamsActive
|
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 is 6.
|
CFBStreamsAvailable
|
This counter represents the remaining number of streams 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.
|
CFBStreamsTotal
|
This counter represents the total number of simplex (one direction) streams that have been connected to the conference bridge since the Cisco IP Voice Media Streaming Application service started.
|
MOHAudioSourcesActive
|
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 there are no devices listening. The exception is for multicast audio sources, which will always be streaming audio.
Note Current behavior for this counter is such that 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 be 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 you have configured the default audio source for multicast, G.711 mu-law and wideband codecs, then two streams are used (default audio source + G.711 mu-law and default audio source + wideband).
|
MOHConnectionsLost
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Media Streaming Application that a Cisco CallManager connection was lost.
|
MOHConnectionState
|
For each Cisco CallManager associated with an MOH, this counter represents the current registration state to Cisco CallManager; 0 indicates no registration to Cisco CallManager; 1 indicates registration to the primary Cisco CallManager; 2 indicates connection to the secondary Cisco CallManager (connected to Cisco CallManager but not registered until the primary Cisco CallManager connection fails).
|
MOHStreamsActive
|
This counter represents the total number of active (currently in use) simplex (one direction) streams for all connections. There is one output stream for each device listening to a unicast audio source and one input stream for each active audio source, multiplied by the number of MOH codecs.
Note Current behavior for this counter is such that 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 be 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 you have configured the default audio source for multicast, G.711 mu-law and wideband codecs, then two streams are used (default audio source + G.711 mu-law and default audio source + wideband).
|
MOHStreamsAvailable
|
This counter represents the remaining number of streams 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 started. The counter is reduced by 2 for each multicast audio source, mulitipled by the number of MOH codecs configured. The counter is reduced by 1 for each unicast audio source, multiplied by the number of MOH codecs configured.
|
MOHStreamsTotal
|
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.
|
MTPConnectionsLost
|
This counter represents the total number of times since the last restart of the Cisco IP Voice Streaming Application that a Cisco CallManager connection was lost.
|
MTPConnectionState
|
For each Cisco CallManager associated with an MTP, this counter represents the current registration state to Cisco CallManager; 0 indicates no registration to Cisco CallManager; 1 indicates registration to the primary Cisco CallManager; 2 indicates connection to the secondary Cisco CallManager (connected to Cisco CallManager but not registered until the primary Cisco CallManager connection fails.
|
MTPConnectionsTotal
|
This counter represents the total number of MTP instances that have been started since the Cisco IP Voice Media Streaming Application service started.
|
MTPInstancesActive
|
This counter represents the number of active (currently in use) instances of MTP.
|
MTPStreamsActive
|
This counter represents the total number of currently active simplex (one direction) streams for all connections. Each stream direction counts as one stream.
|
MTPStreamsAvailable
|
This counter represents the remaining number of streams allocated for the MTP device that are available for use. This counter starts as 2 mulitplied 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.
|
MTPStreamsTotal
|
This counter represents the total number of simplex (one direction) streams that have been connected to the MTP device since the Cisco IP Voice Media Streaming Application service started.
|
Cisco Messaging Interface
The Cisco Messaging Interface object provides information about the Cisco Messaging Interface (CMI) service.
Table C-16 Cisco Messaging Interface
Counters
|
Counter Descriptions
|
HeartBeat
|
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), it means that the CMI service is down.
|
SMDIMessageCountInbound
|
This counter represents the running count of inbound SMDI messages since the last restart of the CMI service.
|
SMDIMessageCountInbound24Hour
|
This counter represents the rolling count of inbound SMDI messages in the last 24 hours.
|
SMDIMessageCountOutbound
|
This counter represents the running count of outbound SMDI messages since the last restart of the CMI service.
|
SMDIMessageCountOutbound24Hour
|
This counter represents the rolling count of outbound SMDI messages in the last 24 hours.
|
StartTime
|
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 length of time that has elapsed, in milliseconds, since the service started provides the basis for this time. The reference point specifies midnight, January 1, 1970.
|
Cisco MGCP BRI Device
The Cisco Media Gateway Control Protocol (MGCP) Basic Rate Interface (BRI) Device object provides information about registered Cisco MGCP BRI devices.
Table C-17 Cisco MGCP BRI Device
Counters
|
Counter Descriptions
|
Channel 1 Status
|
This counter represents the status of the indicated B-Channel 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.
|
Channel 2 Status
|
This counter represents the status of the indicated B-Channel 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.
|
CallsCompleted
|
This counter represents the total number of successful calls made from this MGCP BRI device.
|
OutboundBusyAttempts
|
This counter represents the total number of times a call through this MGCP BRI device was attempted when there were no voice channels available.
|
DatalinkInService
|
This counter represents the state of the Data Link (D-Channel) on the corresponding Digital Access. It 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).
|
Cisco MGCP FXO Device
The Cisco Media Gateway Control Protocol (MGCP) Foreign Exchange Office (FXO) Device object provides information about registered Cisco MGCP FXO devices.
Table C-18 Cisco MGCP FXO Device
Counters
|
Counter Descriptions
|
CallsCompleted
|
This counter represents the total number of successful calls that were made from the port on an MGCP FXO device.
|
OutboundBusyAttempts
|
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.
|
PortStatus
|
This counter represents the status of the FXO port associated with this MGCP FXO device.
|
Cisco MGCP FXS 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, for a fully configured Catalyst 6000 Analog Interface Module would represent 24 separate instances of this object.
Table C-19 Cisco MGCP FXS Device
Counters
|
Counter Descriptions
|
CallsCompleted
|
This counter represents the total number of successful calls that were made from this port on the MGCP FXS device.
|
OutboundBusyAttempts
|
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.
|
PortStatus
|
This counter represents the status of the FXS port that is associated with a MGCP FXS device.
|
Cisco MGCP Gateways
The Cisco MGCP Gateways object provides information about registered MGCP gateways.
Table C-20 Cisco MGCP Gateways
Counters
|
Counter Descriptions
|
BRISpansInService
|
This counter represents the number of BRI spans that are currently available for use in the gateway.
|
BRIChannelsActive
|
This counter represents the number of BRI voice channels that are currently active in a call in the gateway.
|
FXOPortsActive
|
This counter represents the number of FXO ports that are currently active in a call in the gateway.
|
FXOPortsInService
|
This counter represents the number of FXO ports that are currently available for use in the gateway.
|
FXSPortsActive
|
This counter represents the number of FXS ports that are currently active in a call in the gateway.
|
FXSPortsInService
|
This counter represents the number of FXS ports that are currently available for use in the gateway.
|
PRIChannelsActive
|
This counter represents the number of PRI voice channels that are currently active in a call in the gateway.
|
PRISpansInService
|
This counter represents the number of PRI spans that are currently available for use in the gateway.
|
T1ChannelsActive
|
This counter represents the number of T1 CAS voice channels that are currently active in a call in the gateway.
|
T1SpansInService
|
This counter represents the number of T1 CAS spans that are currently available for use in the gateway.
|
Cisco MGCP PRI Device
The Cisco MGCP Primary Rate Interface (PRI) Device object provides information about registered Cisco MGCP PRI devices.
Table C-21 Cisco MGCP PRI Device
Counters
|
Counter Descriptions
|
CallsCompleted
|
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.
|
Channel 16 Status
|
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.
|
DatalinkInService
|
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).
|
OutboundBusyAttempts
|
This counter represents the total number of times a call through an MGCP PRI device was attempted when there were no voice channels available.
|
Cisco MGCP T1 CAS Device
The Cisco MGCP T1 Channel Associated Signaling (CAS) Device object provides information about registered Cisco MGCP T1 CAS devices.
Table C-22 Cisco MGCP T1 CAS Device
Counters
|
Counter Descriptions
|
CallsCompleted
|
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.
|
OutboundBusyAttempts
|
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.
|
Cisco MOH Device
The Cisco Music On Hold (MOH) Device object provides information about registered Cisco MOH devices.
Table C-23 Cisco MOH Device
Counters
|
Counter Descriptions
|
MOHMulticastResourceActive
|
This counter represents the number of currently active multicast connections to multicast addresses that are served by an MOH server.
Note Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if you have configured the default audio source for multicast, G.711 mu-law and wideband codecs, two streams are used (default audio source + G.711 mu-law and default audio source + wideband).
|
MOHMulticastResourceAvailable
|
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.
Note Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if you have configured the default audio source for multicast, G.711 mu-law and wideband codecs, two streams are used (default audio source + G.711 mu-law and default audio source + wideband).
|
MOHTotalMulticastResources
|
This counter represents the total number of multicast MOH connections that are allowed to multicast addresses that are served by an MOH server.
Note Each MOH multicast resource uses one stream for each audio source and codec combination. For example, if you have configured the default audio source for multicast, G.711 mu-law and wideband codecs, two streams are used (default audio source + G.711 mu-law and default audio source + wideband).
|
MOHTotalUnicastResources
|
This counter represents the total number of unicast MOH connections that are allowed by an MOH server.
Note Each MOH unicast resource uses one stream.
|
MOHUnicastResourceActive
|
This counter represents the number of active unicast MOH connections to an MOH server.
Note Each MOH unicast resource uses one stream.
|
MOHUnicastResourceAvailable
|
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.
Note Each MOH unicast resource uses one stream.
|
MOHHighestActiveResources
|
This counter represents the largest number of simultaneously active MOH connections for an MOH server. This includes both multicast and unicast connections.
|
MOHOutOfResources
|
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 CallManager were already active.
|
Cisco MTP Device
The Cisco Media Termination Point (MTP) Device object provides information about registered Cisco MTP devices.
Table C-24 Cisco MTP Device
Counters
|
Counter Descriptions
|
OutOfResources
|
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.
|
ResourceActive
|
This counter represents the number of MTP resources that are currently in use (active) for an MTP device.
Note Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call.
|
ResourceAvailable
|
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.
Note Each MTP resource uses two streams. An MTP in use represents one MTP resource that has been allocated for use in a call.
|
ResourceTotal
|
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.
|
Cisco Phones
The Cisco Phones object provides information about the number of registered Cisco IP Phones, including both hardware-based and other station devices.
Table C-25 Cisco Phones
Counters
|
Counter Descriptions
|
CallsAttempted
|
This 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.
|
Cisco QSIG Features
The Cisco QSIG features object provides information regarding the operation of various Q.SIG features, such as call diversion and path replacement.
Table C-26 Cisco Phones
Counters
|
Counter Descriptions
|
PathReplacementCompleted
|
This counter represents the number of successful path replacements that have occurred. Path replacement is used in a QSIG network to optimize the path between two edge PINX (PBXs) 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.
|
CallDiversionByRereouteCompleted
|
This counter represents the number of successful call diversion by reroutes that have occurred. Call diversion by reroute enables the path for a forwarded call to be as optimal (minimize the number of B-Channels in use) as possible from the originator's perspective. This counter resets when the Cisco CallManager service parameter Call Diversion by Reroute Enabled is enabled or disabled, or when the Cisco CallManager service restarts.
|
Cisco SIP
The Cisco Session Initiation Protocol (SIP) object provides information about configured SIP devices.
Table C-27 Cisco SIP
Counters
|
Counter Descriptions
|
CallsActive
|
This counter represents the number of calls that are currently active (in use) on this SIP device.
|
CallsAttempted
|
This counter represents the number of calls that have been attempted on this SIP device, including both successful and unsuccessful call attempts.
|
CallsCompleted
|
This counter represents the number of calls that were actually connected (a voice path was established) from a SIP device. This number increases when the call terminates.
|
CallsInProgress
|
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.
|
Cisco SW Conf Bridge Device
The Cisco SW Conference Bridge Device object provides information about registered Cisco software conference bridge devices.
Table C-28 Cisco SW Conf Bridge Device
Counters
|
Counter Descriptions
|
OutOfResources
|
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; for example, because all resources were already in use.
|
ResourceActive
|
This counter represents the number of resources that are currently in use (active) for a SW conference device.
|
ResourceAvailable
|
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.
|
ResourceTotal
|
This counter represents the total number of conference resources that a SW conference device provides. This counter equals the sum of the ResourceAvailable and ResourceActive counters.
|
SWConferenceActive
|
This counter represents the number of software-based conferences that are currently active (in use) on a SW conference device.
|
SWConferenceCompleted
|
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.
|
Cisco TcdSrv
The Cisco TcdSrv (Telephony Call Dispatcher service) object provides information about the Cisco CallManager Attendant Console.
Table C-29 Cisco TcdSrv
Counters
|
Counter Descriptions
|
CallsActive
|
Note Do not use this counter. Information in this counter may not accurately reflect the total number of active calls.
|
CallsRedirected
|
This counter represents the total number of redirected calls for a TCD service. This number increases every time that a pilot point receives a call and redirects the call to a member of its hunt group.
|
CallsTotal
|
This counter represents the total number of all calls that have been made since the TCD service started.
|
CcmLineLinkState
|
This counter represents the line state. Values include 0, 1, 10, or 11. A value of 0 indicates that the TCD service has not registered or has not received line link state information from Cisco CallManager; 1 indicates that the TCD service has registered and is receiving line link state information from Cisco CallManager; 10 indicates that the TCD service has logged into CTI but has not registered or has not received line link state information from Cisco CallManager; 11 indicates that the TCD service has logged into CTI and has registered and is receiving line link state information.
|
ClientsRegistered
|
This counter represents the total number of registered clients for a TCD service. This number increases by one for each new registration of a Cisco CallManager attendant console client when the client application logs in.
|
ClientsOnline
|
This counter represents the total number of Cisco CallManager attendant console clients that are currently online. Attendant Console clients include all users configured in the attendant console User Configuration screen in Cisco CallManager Adminstration that are currently online. This number increases by one for each client that goes online and decreases by one for each client that goes offline.
|
ClientsTotal
|
This counter represents the total number of Cisco CallManager Attendant Console clients that are currently registered with the TCD service. Attendant console clients represent all users that are configured in the Attendant Console User Configuration screen in Cisco CallManager Administration.
|
HeartBeat
|
This counter represents the heartbeat of the TCD service. This incremental count indicates that TCD service is up and running. If the count does not increase, this means that the service is down.
|
LinesActive
|
Note Do not use this counter. Information in this counter may not accurately reflect the total number of active lines.
|
LinesIdle
|
Note Do not use this counter. Information in this counter may not accurately reflect the total number of idle lines.
|
LinesTotal
|
Note Do not use this counter. Information in this counter may not accurately reflect the total number of lines.
|
PilotPointsTotal
|
This counter represents the total number of pilot points that are configured in Cisco CallManager.
|
StartTime
|
This counter represents the time in milliseconds since the TCD service started. The real-time clock in the computer, which is simply 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 is midnight, January 1, 1970.
|
Version
|
This counter represents the version of the TCD service.
|
Cisco TFTP Server
The Cisco Trivial File Transfer Protocol (TFTP) Server object provides information about the Cisco TFTP server.
Table C-30 Cisco TFTP Server
Counters
|
Counter Descriptions
|
BuildCount
|
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.
|
BuildDeviceCount
|
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.
|
BuildDuration
|
This counter represents the time in seconds that it took to build the last of all the configuration files.
|
BuildSignCount
|
This counter represents the number of security-enabled phone devices for which the configuration file was digitally signed with the Cisco CallManager server key in the last build of all the configuration files. This counter also updates while processing security-enabled phone device change notifications.
|
BuildUnitCount
|
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.
|
ChangeNotifications
|
This counter represents the total number of all the Cisco CallManager database change notifications that the TFTP server received. Each time that a device configuration is updated in Cisco CallManager Administration, the TFTP server gets sent a database change notification to rebuild the XML file for the updated device.
|
DeviceChangeNotifications
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete configuration files for devices.
|
HeartBeat
|
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.
|
Requests
Note This counter was formerly called TFTPRequests.
|
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.
|
RequestsAborted
Note This counter was formerly called TFTPRequestsAborted.
|
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.
|
RequestsInProgress
|
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.
|
RequestsNotFound
Note This counter was formerly called TFTPRequestsNotFound.
|
This counter represents the total number of TFTP requests where the requested file was not found. When the TFTP server does not find the requested file, an error message gets sent to the requesting device.
|
RequestsOverflow
Note This counter was formerly called TFTPRequestsOverflow.
|
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.
|
RequestsProcessed
Note This counter was formerly called TFTPRequestsProcessed.
|
This counter represents the total number of TFTP requests that the TFTP server successfully processed.
|
SegmentsAcknowledged
|
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 is successfully transmitted to the requesting device.
|
SegmentSent
|
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.
|
UnitChangeNotifications
|
This counter represents the number of times that the TFTP server received database change notification to create, update, or delete gateway-related configuration files.
|
Cisco Transcode Device
The Cisco Transcode Device object provides information about registered Cisco transcoding devices.
Table C-31 Cisco Transcode Device
Counters
|
Counter Descriptions
|
OutOfResources
|
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.
|
ResourceActive
|
This counter represents the number of transcoder resources that are currently in use (active) for a transcoder device.
Note Each transcoder resource uses two streams.
|
ResourceAvailable
|
This counter represents the total number of resources that are not active and are still available to be used now for a transcoder device.
Note Each transcoder resource uses two streams.
|
ResourceTotal
|
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.
|
Cisco Video Conference Bridge
The Cisco Video Conference Bridge object provides information about registered Cisco video conference bridge devices.
Table C-32 Cisco Video Conference Bridge
Counters
|
Counter Descriptions
|
ConferenceActive
|
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.
|
ConferenceAvailable
|
This counter represents the number of video conferences that are not active and are still available on a video conference device.
|
ConferenceCompleted
|
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.
|
ConferenceTotal
|
This counter represents the total number of video conferences that are configured for a video conference device.
|
OutOfConferences
|
This counter represents the total number of times 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 allowed (as specified by the TotalConferences counter).
|
OutOfResources
|
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.
|
ResourceActive
|
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.
|
ResourceAvailable
|
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.
|
ResourceTotal
|
This counter represents the total number of resources that are configured on a video conference bridge device. One resource gets used per participant.
|
Cisco WebDialer
The Cisco WebDialer object provides information about the Cisco WebDialer application and the Redirector servlet.
Table C-33 Cisco WebDialer
Counters
|
Counter Descriptions
|
CallsCompleted
|
This counter represents the number of Make Call and End Call requests that the Cisco WebDialer application successfully completed.
|
CallsFailed
|
This counter represents the number of Make Call and End Call requests that were unsuccessful.
|
RedirectorSessionsHandled
|
This counter represents the total number of HTTP sessions that the Redirector servlet handled since the last service startup.
|
RedirectorSessionsInProgress
|
This counter represents the number of HTTP sessions that are currently being serviced by the Redirector servlet.
|
SessionsHandled
|
This counter represents the total number of CTI sessions that the Cisco WebDialer servlet handled since the last service startup.
|
SessionsInProgress
|
This counter represents the number of CTI sessions that are currently being serviced by the Cisco WebDialer servlet.
|
Where to Find More Information
Related Topics
•Chapter 1, "Introduction"
•Chapter 2, "Performance Objects and Counters"
•Chapter 9, "Real-Time Monitoring Tool"
•Chapter 12, "Microsoft Performance"
•"Real-Time Monitoring Configuration," Cisco CallManager Serviceability Administration Guide
•"Microsoft Performance," Cisco CallManager Serviceability Administration Guide
Feedback
