Home/Catalog/CISCO-CONTACT-CENTER-APPS-MIB

CISCO-CONTACT-CENTER-APPS-MIB

AI MIB Summary

The CISCO-CONTACT-CENTER-APPS-MIB provides SNMP instrumentation for monitoring the operational status, configuration parameters, and fault-tolerant topology of Cisco Unified Contact Center Enterprise components, including the Router, Logger, Peripheral Gateway, CTI Gateway, and Outbound Option. It exposes static tables containing dependent host addresses, unique functional identifiers, and duplex/simplex state indicators to enable centralized management of distributed contact routing and multi-media session handling across the IP infrastructure.

The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for applications that deliver enterprise-wide intelligent contact routing, call treatment, network-to- desktop computer telephony integration (CTI), and multi-media (e.g. voice, email, chat) contact management over an IP infrastructure. Cisco enterprise contact center applications are distributed, fault-tolerant, contact routing and management solutions that encompass multiple, dependent host servers. Each host is capable of implementing one or more functions of the application. How many functions a single host is capable of providing is dependent upon capacity and/or performance limitations. However, the architecture supports virtually any combination. The main functional components of Cisco enterprise contact center applications are: 1. Router: The router component provides intelligent routing of inbound contacts, e.g. voice calls, emails, chat sessions, to contact center agents. A subcomponent of the router is the Network Interface Controller (NIC). A NIC, in the context of a Cisco enterprise contact center application, is a gateway to a voice telephony network. (A NIC here should not be confused with a network interface card on a host computer.) A router component can have one or more NIC subcomponents. 2. Logger: The logger component maintains the enterprise contact center solution configuration and real-time data store. 3. Administration and Data Server: The administration and data server provides access to configuration, historical and detailed data, serving one or more reporting clients or data archival or aggregation components. Note that this component was previously known as the Administrator Workstation (AW) (specifically, the Distributor AW). 4. Peripheral Gateway (PG): The PG provides an interface to one or more peripheral devices such as a private branch exchange (PBX), an automatic call distributor (ACD) or a voice response unit (VRU). A subcomponent of the PG is the Peripheral Interface Manager or 'PIM'. A PIM acts as a gateway between the PG and a single PBX or VRU. A PG may have multiple PIMs. 5. Computer Telephony Integration (CTI) Gateway (CG): The CTI gateway is the solution integration point for desktop CTI clients. The CTI client application exposes contact data served by the CG to the agent (via 'screen pops') and allows the agent to control the contact state, e.g. answer/hang-up or transfer voice calls, respond to emails or chat with contacts. 6. CTI Object Server (CTIOS): CTIOS, as compared to the CTI gateway, is a more intelligent and more scalable server for desktop CTI clients and offers a higher-level interface to those client applications. 7. Outbound Option (OO): Outbound Option is an optional, add-on product having two primary runtime components: the Campaign Manager and the Dialer. The Campaign Manager is deployed co-resident with the Logger while the Dialer is deployed co-resident with a Peripheral Gateway. No more than one instance of an Outbound Option component may be installed on a server. Each server of the enterprise contact center solution, regardless of its specific function, implements the contact center applications MIB, however, it only populates those tables that are appropriate for its specific function. Implementing the same MIB on all hosts simplifies the acquisition of management instrumentation from the entire contact center solution. The instrumentation in each table of this MIB provides three types of data: 1) dependent host addresses (for topology building), 2) critical configuration information that uniquely identifies the functional component and, 3) operational status instrumentation. The quantity of entries (i.e. rows) in the tables of this MIB is static while the application is running on the host; rows cannot be added or deleted at runtime by the management station. Glossary of acronyms and terms: ACD Automatic Call Distributor BA Blended Agent (now called Outbound Option) CCE (Cisco Unified) Contact Center Enterprise CCH (Cisco Unified) Contact Center Hosted CG CTI Gateway CICM Customer Intelligent Contact Manager CTI Computer Telephony Integration CTIOS CTI Object Server DMP Device Management Protocol ICM (Cisco Unified) Intelligent Contact Management ICME (Cisco Unified) Intelligent Contact Management Enterprise ICMH (Cisco Unified) Intelligent Contact Management Hosted IPCC (Cisco) IP Contact Center - Old name, replaced by Cisco Unified Contact Center IVR Interactive Voice Response NAM Network Application Manager NIC Network Interface Controller OO Outbound Option PBX Private Branch Exchange PG Peripheral Gateway PIM Peripheral Interface Manager VRU Voice Response Unit duplex A term used herein to indicate that the functional component is fault tolerant. The component is installed on two separate servers (a side A and a side B); one side is active while the other is on hot standby. Should a failure occur on one side, the other side will immediately activate and continue its function with virtually no loss in functionality. instance A collection of enterprise contact center application functional components that encompass a complete solution. simplex A term used herein to indicate that the functional component is not fault tolerant. The component is installed on a single server; if the component fails, the system will then be impaired or entirely non-functional.
Main OID:
ciscoCcaMIB.1.3.6.1.4.1.9.9.473
156
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

156 total
Object Name
ciscoCcaMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.473
ciscoCcaMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.473.0
cccaIcmEvent
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.473.0.1
ciscoCcaMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.473.1
cccaGeneralInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.473.1.1
cccaNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.1.1
cccaDescriptionro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.1.2
cccaVersionro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.1.3
cccaTimeZoneNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.1.4
cccaTimeZoneOffsetHoursro
Integer32 (-12..12)
.1.3.6.1.4.1.9.9.473.1.1.5
cccaTimeZoneOffsetMinutesro
Integer32 (-59..59)
.1.3.6.1.4.1.9.9.473.1.1.6
cccaSupportToolsURLro
CiscoURLString (CISCO-TC)
.1.3.6.1.4.1.9.9.473.1.1.7
cccaWebSetupURLro
CiscoURLString (CISCO-TC)
.1.3.6.1.4.1.9.9.473.1.1.8
cccaNotificationsEnabledrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.1.9
cccaComponents
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.473.1.2
cccaInstanceTable
SEQUENCE OF CccaInstanceEntry
.1.3.6.1.4.1.9.9.473.1.2.1
cccaInstanceEntry
CccaInstanceEntry
.1.3.6.1.4.1.9.9.473.1.2.1.1
cccaInstanceNumber
Unsigned32
.1.3.6.1.4.1.9.9.473.1.2.1.1.1
cccaInstanceNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.2.1.1.2
cccaComponentTable
SEQUENCE OF CccaComponentEntry
.1.3.6.1.4.1.9.9.473.1.2.2
cccaComponentEntry
CccaComponentEntry
.1.3.6.1.4.1.9.9.473.1.2.2.1
cccaComponentIndex
CcaIndex
.1.3.6.1.4.1.9.9.473.1.2.2.1.1
cccaComponentTypero
CcaComponentType
.1.3.6.1.4.1.9.9.473.1.2.2.1.2
cccaComponentNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.2.2.1.3
cccaComponentStatusro
CcaComponentStatus
.1.3.6.1.4.1.9.9.473.1.2.2.1.4
cccaComponentElmtTable
SEQUENCE OF CccaComponentElmtEntry
.1.3.6.1.4.1.9.9.473.1.2.3
cccaComponentElmtEntry
CccaComponentElmtEntry
.1.3.6.1.4.1.9.9.473.1.2.3.1
cccaComponentElmtIndex
Unsigned32 (1..'FFFFFFFF'H)
.1.3.6.1.4.1.9.9.473.1.2.3.1.1
cccaComponentElmtNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.2.3.1.2
cccaComponentElmtRunIDro
Unsigned32 (0..'FFFFFFFF'H)
.1.3.6.1.4.1.9.9.473.1.2.3.1.3
cccaComponentElmtStatusro
CcaComponentStatus
.1.3.6.1.4.1.9.9.473.1.2.3.1.4
cccaComponentInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.473.1.3
cccaRouterTable
SEQUENCE OF CccaRouterEntry
.1.3.6.1.4.1.9.9.473.1.3.1
cccaRouterEntry
CccaRouterEntry
.1.3.6.1.4.1.9.9.473.1.3.1.1
cccaRouterSidero
CcaComponentSide
.1.3.6.1.4.1.9.9.473.1.3.1.1.1
cccaRouterCallsPerSecro
Gauge32 UNITS "calls"
.1.3.6.1.4.1.9.9.473.1.3.1.1.2
cccaRouterAgentsLoggedOnro
Gauge32 UNITS "agents"
.1.3.6.1.4.1.9.9.473.1.3.1.1.3
cccaRouterCallsInProgressro
Gauge32 UNITS "calls"
.1.3.6.1.4.1.9.9.473.1.3.1.1.4
cccaRouterDuplexPairNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.1.1.5
cccaRouterNicCountro
Gauge32
.1.3.6.1.4.1.9.9.473.1.3.1.1.6
cccaRouterPGsEnabledCountro
Gauge32
.1.3.6.1.4.1.9.9.473.1.3.1.1.7
cccaRouterCallsInQueuero
Gauge32 UNITS "calls"
.1.3.6.1.4.1.9.9.473.1.3.1.1.8
cccaRouterAppGwEnabledro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.3.1.1.9
cccaRouterDBWorkerEnabledro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.3.1.1.10
cccaRouterPublicHighAddrro
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.1.1.11
cccaRouterPublicNonHighAddrro
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.1.1.12
cccaRouterPrivateHighAddrro
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.1.1.13
cccaRouterPrivateNonHighAddrro
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.1.1.14
cccaNicTable
SEQUENCE OF CccaNicEntry
.1.3.6.1.4.1.9.9.473.1.3.2
cccaNicEntry
CccaNicEntry
.1.3.6.1.4.1.9.9.473.1.3.2.1
cccaNicIndex
CcaIndex
.1.3.6.1.4.1.9.9.473.1.3.2.1.1
cccaNicTypero
Enumeration
.1.3.6.1.4.1.9.9.473.1.3.2.1.2
cccaNicStatusro
CcaComponentStatus
.1.3.6.1.4.1.9.9.473.1.3.2.1.3
cccaLoggerTable
SEQUENCE OF CccaLoggerEntry
.1.3.6.1.4.1.9.9.473.1.3.3
cccaLoggerEntry
CccaLoggerEntry
.1.3.6.1.4.1.9.9.473.1.3.3.1
cccaLoggerSidero
CcaComponentSide
.1.3.6.1.4.1.9.9.473.1.3.3.1.1
cccaLoggerTypero
Enumeration
.1.3.6.1.4.1.9.9.473.1.3.3.1.2
cccaLoggerRouterSideANamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.3.1.3
cccaLoggerRouterSideBNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.3.1.4
cccaLoggerDuplexPairNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.3.1.5
cccaLoggerHDSReplicationro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.3.3.1.6
cccaLoggerAvgDBWriteTimero
Unsigned32 UNITS "hundred nanoseconds"
.1.3.6.1.4.1.9.9.473.1.3.3.1.7
cccaDistAwTable
SEQUENCE OF CccaDistAwEntry
.1.3.6.1.4.1.9.9.473.1.3.4
cccaDistAwEntry
CccaDistAwEntry
.1.3.6.1.4.1.9.9.473.1.3.4.1
cccaDistAwSiderodeprecated
CcaComponentSide
.1.3.6.1.4.1.9.9.473.1.3.4.1.1
cccaDistAwTypero
Enumeration
.1.3.6.1.4.1.9.9.473.1.3.4.1.2
cccaDistAwAdminSiteNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.3
cccaDistAwRouterSideANamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.4
cccaDistAwRouterSideBNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.5
cccaDistAwLoggerSideANamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.6
cccaDistAwLoggerSideBNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.7
cccaDistAwDuplexPairNamerodeprecated
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.8
cccaDistAwHDSEnabledro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.3.4.1.9
cccaDistAwWebViewEnabledro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.473.1.3.4.1.10
cccaDistAwWebViewServerNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.11
cccaDistAwWebReskillingURLro
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.3.4.1.12
cccaPgTable
SEQUENCE OF CccaPgEntry
.1.3.6.1.4.1.9.9.473.1.3.5
cccaPgEntry
CccaPgEntry
.1.3.6.1.4.1.9.9.473.1.3.5.1
cccaPgNumberrodeprecated
Unsigned32
.1.3.6.1.4.1.9.9.473.1.3.5.1.1
cccaPgSidero
CcaComponentSide
.1.3.6.1.4.1.9.9.473.1.3.5.1.2
cccaPgRouterSideANamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.5.1.3
cccaPgRouterSideBNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.5.1.4
cccaPgDuplexPairNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.5.1.5
cccaPgPimCountro
Gauge32
.1.3.6.1.4.1.9.9.473.1.3.5.1.6
cccaPgCallsInProgressro
Gauge32 UNITS "calls"
.1.3.6.1.4.1.9.9.473.1.3.5.1.7
cccaPgAgentsLoggedOnro
Gauge32 UNITS "agents"
.1.3.6.1.4.1.9.9.473.1.3.5.1.8
cccaPgAgentsReadyro
Gauge32 UNITS "agents"
.1.3.6.1.4.1.9.9.473.1.3.5.1.9
cccaPgAgentsTalkingro
Gauge32 UNITS "agents"
.1.3.6.1.4.1.9.9.473.1.3.5.1.10
cccaPgIDro
Unsigned32
.1.3.6.1.4.1.9.9.473.1.3.5.1.11
cccaPimTable
SEQUENCE OF CccaPimEntry
.1.3.6.1.4.1.9.9.473.1.3.6
cccaPimEntry
CccaPimEntry
.1.3.6.1.4.1.9.9.473.1.3.6.1
cccaPimNumber
Unsigned32
.1.3.6.1.4.1.9.9.473.1.3.6.1.1
cccaPimPeripheralNamero
SnmpAdminString (SNMP-FRAMEWORK-MIB)
.1.3.6.1.4.1.9.9.473.1.3.6.1.2
cccaPimPeripheralTypero
CcaPeripheralType
.1.3.6.1.4.1.9.9.473.1.3.6.1.3
cccaPimStatusro
CcaComponentStatus
.1.3.6.1.4.1.9.9.473.1.3.6.1.4
cccaPimPeripheralHostNamero
InetAddressDNS (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.473.1.3.6.1.5
cccaCgTable
SEQUENCE OF CccaCgEntry
.1.3.6.1.4.1.9.9.473.1.3.7
cccaCgEntry
CccaCgEntry
.1.3.6.1.4.1.9.9.473.1.3.7.1
cccaCgNumberrodeprecated
Unsigned32
.1.3.6.1.4.1.9.9.473.1.3.7.1.1
cccaCgSidero
CcaComponentSide
.1.3.6.1.4.1.9.9.473.1.3.7.1.2
Showing 100 of 156 OID objects

CISCO-CONTACT-CENTER-APPS-MIB Technical Reference Overview

The CISCO-CONTACT-CENTER-APPS-MIB SNMP MIB module published by Cisco defines 156 managed OID objects, including 119 scalar/column metrics, 13 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.473. Key tabular structures include cccaInstanceTable, cccaComponentTable, cccaComponentElmtTable, cccaRouterTable, cccaNicTable, cccaLoggerTable. Monitored SNMP traps/notifications include cccaIcmEvent.

Key OID Definitions in CISCO-CONTACT-CENTER-APPS-MIB

ciscoCcaMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.473

The Cisco Contact Center Applications (CCCA) Management Information Base (MIB) module defines management instrumentation for applications that deliver enterprise-wide intelligent contact routing, call treatment, network-to- desktop computer telephony integration (CTI), and multi-media (e.g. voice, email, chat) contact management over an IP infrastructure. Cisco enterprise contact center applications are distributed, fault-tolerant, contact routing and management solutions that encompass multiple, dependent host servers. Each host is capable of implementing one or more functions of the application. How many functions a single host is capable of providing is dependent upon capacity and/or performance limitations. However, the architecture supports virtually any combination. The main functional components of Cisco enterprise contact center applications are: 1. Router: The router component provides intelligent routing of inbound contacts, e.g. voice calls, emails, chat sessions, to contact center agents. A subcomponent of the router is the Network Interface Controller (NIC). A NIC, in the context of a Cisco enterprise contact center application, is a gateway to a voice telephony network. (A NIC here should not be confused with a network interface card on a host computer.) A router component can have one or more NIC subcomponents. 2. Logger: The logger component maintains the enterprise contact center solution configuration and real-time data store. 3. Administration and Data Server: The administration and data server provides access to configuration, historical and detailed data, serving one or more reporting clients or data archival or aggregation components. Note that this component was previously known as the Administrator Workstation (AW) (specifically, the Distributor AW). 4. Peripheral Gateway (PG): The PG provides an interface to one or more peripheral devices such as a private branch exchange (PBX), an automatic call distributor (ACD) or a voice response unit (VRU). A subcomponent of the PG is the Peripheral Interface Manager or 'PIM'. A PIM acts as a gateway between the PG and a single PBX or VRU. A PG may have multiple PIMs. 5. Computer Telephony Integration (CTI) Gateway (CG): The CTI gateway is the solution integration point for desktop CTI clients. The CTI client application exposes contact data served by the CG to the agent (via 'screen pops') and allows the agent to control the contact state, e.g. answer/hang-up or transfer voice calls, respond to emails or chat with contacts. 6. CTI Object Server (CTIOS): CTIOS, as compared to the CTI gateway, is a more intelligent and more scalable server for desktop CTI clients and offers a higher-level interface to those client applications. 7. Outbound Option (OO): Outbound Option is an optional, add-on product having two primary runtime components: the Campaign Manager and the Dialer. The Campaign Manager is deployed co-resident with the Logger while the Dialer is deployed co-resident with a Peripheral Gateway. No more than one instance of an Outbound Option component may be installed on a server. Each server of the enterprise contact center solution, regardless of its specific function, implements the contact center applications MIB, however, it only populates those tables that are appropriate for its specific function. Implementing the same MIB on all hosts simplifies the acquisition of management instrumentation from the entire contact center solution. The instrumentation in each table of this MIB provides three types of data: 1) dependent host addresses (for topology building), 2) critical configuration information that uniquely identifies the functional component and, 3) operational status instrumentation. The quantity of entries (i.e. rows) in the tables of this MIB is static while the application is running on the host; rows cannot be added or deleted at runtime by the management station. Glossary of acronyms and terms: ACD Automatic Call Distributor BA Blended Agent (now called Outbound Option) CCE (Cisco Unified) Contact Center Enterprise CCH (Cisco Unified) Contact Center Hosted CG CTI Gateway CICM Customer Intelligent Contact Manager CTI Computer Telephony Integration CTIOS CTI Object Server DMP Device Management Protocol ICM (Cisco Unified) Intelligent Contact Management ICME (Cisco Unified) Intelligent Contact Management Enterprise ICMH (Cisco Unified) Intelligent Contact Management Hosted IPCC (Cisco) IP Contact Center - Old name, replaced by Cisco Unified Contact Center IVR Interactive Voice Response NAM Network Application Manager NIC Network Interface Controller OO Outbound Option PBX Private Branch Exchange PG Peripheral Gateway PIM Peripheral Interface Manager VRU Voice Response Unit duplex A term used herein to indicate that the functional component is fault tolerant. The component is installed on two separate servers (a side A and a side B); one side is active while the other is on hot standby. Should a failure occur on one side, the other side will immediately activate and continue its function with virtually no loss in functionality. instance A collection of enterprise contact center application functional components that encompass a complete solution. simplex A term used herein to indicate that the functional component is not fault tolerant. The component is installed on a single server; if the component fails, the system will then be impaired or entirely non-functional.

cccaInstanceTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.2.1

The instance table is a list of enterprise contact center application instances. Each instance represents a contact center application solution. A solution includes a collection of interconnected functional components (e.g. a router, a logger and a peripheral gateway), each of which perform a specific, necessary function of the contact center application. A single server is permitted to have multiple functional components of a different type, but also multiple components of the same type, each of which may be part of a different instance. A perfect example of the latter is in a telephony service provider environment where a single server could have ten router components, each assigned to a different 'customer' instance. All ten are concurrently functional but route contacts only within the context of the instance that they are assigned. In this scenario, the instance table would have ten entries. The instance table is not directly dependent upon any other table, however, the other functional component tables are dependent upon the instance table. The instance table index serves as a primary index for all other functional component tables in order to properly relate the functional components to the appropriate instance. The SNMP agent constructs the instance table at startup. Since instances can only be configured while the enterprise contact center application is stopped, instance table entries cannot be added to or deleted from the table nor can object values be modified either by the agent or the management station. All objects in this table are read-only.

cccaComponentTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.2.2

The component table is a list of enterprise contact center application functional components. A contact center application solution includes a collection of interconnected functional components (e.g. a router, a logger and a peripheral gateway), each of which perform a specific, necessary function of the contact center application. This table enumerates and lists all contact center application functional components installed and configured on this server. A single server is permitted to have multiple functional components of a different type, but also multiple components of the same type. This table has an expansion relationship with the instance table; there will be one or many entries in this table that relate to a single entry in the instance table. The component table is indexed by two different values: the primary index is the instance index; the secondary index is a unique identifier for each functional component. This component index is arbitrarily assigned by the SNMP agent. These same index values are used in the individual component information tables, thus, the individual component information tables have a sparse dependency relationship with this table. The SNMP agent constructs the component table at startup. Since components can only be configured while the enterprise contact center application is stopped, component table entries cannot be added to or deleted from the table. Object values can be modified by the agent but not the management station. All objects in this table are read-only to the management station.

cccaComponentElmtTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.2.3

The component element table provides a list of component (operating system) services or processes that are elements of an enterprise contact center application functional component. Each entry identifies a single process that is a necessary element of the functional component. This table also provides a one-to-one mapping of entries to a corresponding entry in IETF standard host and application MIB tables. The HOST-RESOURCES and SYSAPPL MIBs expose tables that provide additional instrumentation for software and applications and for the processes that make up that software or those applications. The HOST-RESOURCES-MIB entries in 'hrSWRunTable' and 'hrSWRunPerfTable' and the SYSAPPL-MIB entries in 'sysApplElmtRunTable' have a one-to-one relationship to entries in the component element table. The entries in these standard MIB tables are solely or partially indexed by the operating system process identifier (ID). The process ID is an integer value that uniquely identifies a single process that is currently running on the host. Entries in the component element table maintain its process ID; this value is used to relate the entry to a corresponding entry in the referenced tables of HOST-RESOURCES-MIB and SYSAPPL-MIB. Entries in these tables of the HOST-RESOURCES and SYSAPPL MIBs expose similar information about each process; in some cases, objects are duplicated. However, while the HOST-RESOURCES-MIB lists processes with no further relationship, the SYSAPPL-MIB relates these same processes to installed software packages and the elements that make up those packages. Entries in the component element table cannot be similarly indexed as the referenced standard MIB tables because, should the process terminate (expectedly or unexpectedly), the entry would need to be removed from the table since its index or process ID is thus unknown. This behavior diminishes the agent's ability to express a component element's current status since the entry no longer exists. However, to relate this table to the referenced standard MIB tables, entries in the component element table maintain the current process ID of the element. This provides the one-to-one relationship that allows the management station to drill down further on each functional component and present instrumentation related to each element of that component from these standard MIB tables. This table has a expansion relationship with the component table; there will be one or many entries in this table that relate to a single entry in the component table. Because the set of elements of a contact center functional component are finite and static, this table is constructed by the SNMP agent at startup; entries cannot be added or deleted at run time. The object values of each element entry may change periodically if the run state of the process changes. The SNMP agent will alter the RunID and Status object values to reflect the correct process ID and run status of that process. All objects in this table are read-only to the management station.

cccaRouterTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.1

The router table lists each enterprise contact center application router component configured on this server. Each entry in the table defines a separate router functional component; a single server is permitted to have multiple router components. The router table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the router table in order to properly relate a router component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the router table at startup. Since routers can only be configured while the enterprise contact center application is stopped, router table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update router entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaNicTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.2

The NIC table lists the enterprise contact center application network interface controllers enabled on this router functional component. The NIC table has an expansion dependent relationship with the router table. There may be one or more NIC entries associated with a single router entry. The instance index acts as the primary index and the component index a secondary index. This indexing method ensures that NIC entries are properly related to its parent router and to the appropriate instance. The SNMP agent arbitrarily assigns the NIC index when each NIC table entry is created. The SNMP agent constructs the NIC table at startup. Since NICs can only be configured while the enterprise contact center application is stopped, NIC table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update NIC entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaLoggerTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.3

The logger table lists the enterprise contact center application logger functional components installed and enabled on this server. The logger table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the logger table in order to properly relate a logger component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the logger table at startup. Since loggers can only be configured while the enterprise contact center application is stopped, logger table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update the values of logger entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaDistAwTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.4

The distributor administrator workstation (AW) (also known as the administration and data server) table lists the enterprise contact center application distributor AW functional components installed and enabled on this server. The distributor AW table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the distributor AW table in order to properly relate a distributor AW component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the distributor AW table at startup. Since distributor AWs can only be configured while the enterprise contact center application is stopped, distributor AW table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update the values of distributor AW entry objects as their values change when the application is running. All objects in this table are read- only to the management station.

cccaPgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.5

The PG table lists the enterprise contact center application peripheral gateway functional components installed and enabled on this server. The peripheral gateway table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the peripheral gateway table in order to properly relate a peripheral gateway component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the peripheral gateway table at startup. Since peripheral gateways can only be configured while the enterprise contact center application is stopped, peripheral gateway table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update the values of peripheral gateway entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaPimTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.6

The PIM table lists the enterprise contact center application peripheral interface managers (PIM) configured and enabled on this peripheral gateway functional component. The PIM table is dependent upon both the instance table and the PG table; the instance index acts as the primary index and the PG index a secondary index. This indexing method ensures that PIM entries are properly related to its parent peripheral gateway and to the appropriate instance. The PIM table has an expansion dependent relationship with the peripheral gateway table. There may be one or more PIM entries associated with a single peripheral gateway entry. The instance index acts as the primary index and the component index a secondary index. This indexing method ensures that PIM entries are properly related to its parent peripheral gateway and to the appropriate instance. The SNMP agent assigns the PIM number, based upon the configuration, when each PIM table entry is created. The SNMP agent constructs the PIM table at startup. Since PIMs can only be configured while the enterprise contact center application is stopped, PIM table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update PIM entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaCgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.7

The CG table lists the enterprise contact center application computer telephony integration (CTI) gateway functional components installed and enabled on this server. The CTI gateway table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the CTI gateway table in order to properly relate a CTI gateway component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the CTI gateway table at startup. Since CTI gateways can only be configured while the enterprise contact center application is stopped, CTI gateway table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update the values of CTI gateway entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaCtiOsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.8

The CTI OS table lists the enterprise contact center application computer telephony integration object server (CTI OS) functional components installed and enabled on this server. The CTI OS table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the CTI OS table in order to properly relate a CTI OS component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the CTI OS table at startup. Since CTI OS components can only be configured while the enterprise contact center application is stopped, CTI OS table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update the values of CTI OS entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaCampaignMgrTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.9

The campaign manager table lists each enterprise contact center application Outbound Option Campaign Manager component configured on this server. Each entry in the table defines a separate campaign manager functional component. The campaign manager table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the campaign manager table in order to properly relate a campaign manager component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the campaign manager table at startup. Since campaign managers can only be configured while the enterprise contact center application is stopped, campaign manager table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update campaign manager entry objects as their values change when the application is running. All objects in this table are read- only to the management station.

cccaDialerTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.473.1.3.10

The Dialer table lists each enterprise contact center application Outbound Option Dialer component configured on this server. Each entry in the table defines a separate Dialer functional component. The Dialer table has a sparse dependent relationship with the component table. The instance number acts as the primary index for the Dialer table in order to properly relate a Dialer component entry to the appropriate instance entry. The component index acts as the secondary index, relating the entry to the corresponding entry in the component table. The SNMP agent constructs the Dialer table at startup. Since a Dialer can only be configured while the enterprise contact center application is stopped, Dialer table entries cannot be added to or deleted from the table either by the agent or the management station when the application is running. The agent will update Dialer entry objects as their values change when the application is running. All objects in this table are read-only to the management station.

cccaIcmEventNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.473.0.1

An ICM event is a notification that is sent by a functional component of the Cisco Unified Intelligent Contact Management and the Cisco Unified Contact Center, Enterprise and Hosted applications.

cccaNameInetAddressDNSread-only
.1.3.6.1.4.1.9.9.473.1.1.1

The name is the fully-qualified domain name of the enterprise contact center application server.

cccaDescriptionSnmpAdminStringread-only
.1.3.6.1.4.1.9.9.473.1.1.2

The description object holds a textual description of the enterprise contact center application installed on this server. This is typically the full name of the application.

cccaVersionSnmpAdminStringread-only
.1.3.6.1.4.1.9.9.473.1.1.3

The version object identifies the version number of the enterprise contact center application software installed on this server.

cccaTimeZoneNameSnmpAdminStringread-only
.1.3.6.1.4.1.9.9.473.1.1.4

The time zone name object specifies the name of the time zone where the enterprise contact center application server is physically located.

cccaTimeZoneOffsetHoursInteger32read-only
.1.3.6.1.4.1.9.9.473.1.1.5

The time zone offset hours object represents the number of hours that the local time, in the time zone where the enterprise contact center application server is physically located, differs from Greenwich Mean Time (GMT).

cccaTimeZoneOffsetMinutesInteger32read-only
.1.3.6.1.4.1.9.9.473.1.1.6

The time zone offset minutes object represents the number of minutes that the local time, in the time zone where the enterprise contact center application server is physically located, differs from Greenwich Mean Time (GMT). This object is combined with cccaTimeZoneOffsetHours object to represent the local time zone's total offset from GMT.

cccaSupportToolsURLCiscoURLStringread-only
.1.3.6.1.4.1.9.9.473.1.1.7

The support tools URL object holds the URL for the enterprise contact center application support tools application server. The support tools application server is an optional component of the solution and offers a centralized server for diagnostic and troubleshooting tools. This application server resides on a dedicated server or may be co-resident with a Client Administrator Workstation application component. This object offers a navigation point from the management station (assuming a web interface) whereby a user can quickly access the support tools application server.

cccaWebSetupURLCiscoURLStringread-only
.1.3.6.1.4.1.9.9.473.1.1.8

The Web setup URL object holds the URL for the enterprise contact center application setup web service. The setup web service is a component of every Cisco Unified ICM and Contact Center Enterprise/Hosted server and allows for an administrator to configure parameters of the contact center application as it relates to the installation of the product itself (not to be confused with provisioning).

cccaNotificationsEnabledTruthValueread-write
.1.3.6.1.4.1.9.9.473.1.1.9

The notifications enabled object allows a management station to disable, during run time, all outgoing contact center application notifications. This is typically done during a maintenance window where many application components are frequently stopped, reconfigured and restarted, which can generate periodic floods of notifications that are not desireable during that maintenance period. Please note that this setting is persistent even after a restart of the agent; the management station must explicitly reset this object value to 'true' to re-enable outgoing application notifications.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→