CISCO-CONTACT-CENTER-APPS-MIB: View SNMP OID List / Download MIB

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.

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.

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

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.

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

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

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).

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.

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.

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).

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.

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.

Each instance entry represents a contact center application solution. A solution includes a collection of interconnected functional components, each of which perform a specific, necessary function of the contact center application. At minimum, an instance would include one router component, one logger component and one peripheral gateway component. While each functional component may reside on a separate server, they are identified as being a part of the collective instance by having the same instance name and instance number.

The instance number is a numeric value that uniquely identifies an enterprise contact center application instance. The instance number is a user-defined value configured when the instance is created by the administrator.

The instance name is the configured textual identification for the enterprise contact center application instance.

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.

Each component entry represents a contact center application functional component installed and configured on this server. This table lists these functional components and provides a map to the component resource table.

The component index is a value that uniquely identifies an entry in the component table. This value is arbitrarily assigned by the SNMP agent.

The component type object identifies the type of enterprise contact center application functional component.

The component name is a user-intuitive textual name for the enterprise contact center application functional component. Typically, this name is constructed using the component type text, the letter that indicates which side this component represents of a fault tolerant duplex pair and potentially a configured numeric identifier assigned to the component. For example, a router component might be 'RouterB'; a peripheral gateway might be 'PG3A'. Often, this name is used elsewhere (in contact center application tools) to identify this functional component.

The component status is the last known status of the enterprise contact center application functional component.

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.

Each entry in the component element identifies a single process that is a necessary element of the enterprise contact center functional component. Each entry in the 'hrSWRunTable' and the 'hrSWRunPerfTable' of the HOST-RESOURCES-MIB as well as the 'sysApplElmtRunTable' of the SYSAPPL-MIB maps to a corresponding entry of the component element table. An entry in this table is an operating system process or service.

The component element index is a unique numeric identifier for a system process or service that is a necessary element of an enterprise contact center application functional component. This value is arbitrarily assigned by the SNMP agent.

The component element name is the textual name of the component element, as known by the contact center application. The component element is an operating system process which is a necessary element of the enterprise contact center application functional component. Most often, this name is the host executable file name, without the file extension.

The component element run ID is the actual operating system process ID for the process or service that is an element of this enterprise contact center application functional component. The component element run ID maps directly to the 'hrSWRunIndex' value of 'hrSWRunTable' and 'hrSWRunPerfTable' (which augments 'hrSWRunTable') of the HOST-RESOURCES-MIB and the 'sysApplElmtRunIndex' value of 'sysApplElmtRunTable' of the SYSAPPL-MIB. This object value provides the mechanism for a one-to-one relationship between an entry in the referenced tables of these standard MIBs and an entry in the component element table.

The component element status is the last known status of a system process or service that is a necessary element of an enterprise contact center application functional component.

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.

Each router entry represents an enterprise contact center application router functional component configured on the server. The router component provides intelligent routing of inbound contacts, e.g. voice calls, to contact center agents. The objects in the router entry provide information in three areas: 1) identify which part of the fault tolerant duplex pair this component represents and which server is its duplex pair, 2) provide health instrumentation that indicates the component's status and load and 3) supply a count of NIC subcomponents configured and enabled on this router component.

The router side indicates which of the duplex pair this entry represents of an enterprise contact center application fault tolerant router functional component. The router side value is either 'A' or 'B'. For simplex configurations, the router side value defaults to 'A'.

The router calls per sec object indicates the current inbound call rate; that is, the calculated number of inbound calls per second.

The router agents logged on object represents the number of contact center agents currently managed by the enterprise contact center application. This does not necessarily represent the number of contact center agents that can receive routed calls, but rather the number of agents for which the application is recording statistical information.

The router calls in progress object indicates the current number of active (voice) calls being managed by the enterprise contact center application. The calls will be in various states of treatment.

The router duplex pair name object is the host name of the duplex pair (i.e. the other side) server of an enterprise contact center application fault tolerant router component. If this component is not part of a duplex pair (i.e. simplex), the object value will be the null string.

The router NIC count object is the number of network interface controllers configured and enabled for this enterprise contact center application router functional component. There is an imposed architectural limit of 32 configured NICs per router. This object holds a count of rows in the NIC table (cccaNicTable).

The router PGs enabled count object holds the number of Peripheral Gateways (PGs) that have been enabled for this router; during normal operation, this is the number of PGs that will connect to this router functional component. The application limits the number of configured PGs to a maximum of 250 per deployment.

The router calls in queue object indicates the total number of calls queued in all network Voice Response Units (VRUs), from the router's perspective, including those calls that are in the process of transferring to the VRU for queuing.

The router application gateway enabled object indicates whether an application gateway is configured and a part of this contact center application deployment. An application gateway provides an external interface to business back-end systems that may be used as external input to call scripting logic, or, that logic which controls how a customer call is handled (routed).

The router database worker enabled object indicates whether a database worker process has been configured and is a part of this contact center application deployment. A database worker provides an interface to an external database from which data may be retrieved and used as input to call scripting logic, or, that logic which controls how a customer call is handled (routed).

The router public high address object holds the address of the local high-priority interface of this router functional component to the public network. The 'public' network interface is exposed outside the realm of the ICM or Contact Center application and is used for the transfer of data between this router and other functional components of the contact center deployment. This interface is reserved for high-priority messages; network prioritization is typically configured for this interface to ensure a level of quality of service.

The router public non-high address object holds the address of the local interface of this router functional component to the public network that is used for best effort priority messages. The 'public' network interface is exposed outside the realm of the ICM or Contact Center application and is used for the transfer of data between this router and other functional components of the deployment. This interface is used for normal-priority messages.

The router private high address object holds the address of the local high-priority interface of this router functional component to the private network. The 'private' network interface is used exclusively by the ICM or Contact Center application for the transfer of synchronization data between duplexed pairs and for the transfer of application data from the router to the logger. This interface is reserved for high-priority messages and as much as 90% of the available network bandwidth is allocated to this interface.

The router private non-high address object holds the address of the local interface of this router functional component to the private network that is used for best effort priority messages. The 'private' network is used exclusively by the ICM or Contact Center application for the transfer of synchronization data between duplexed pairs and for the transfer of application data from the router to the logger. This interface is used for normal-priority messages.

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.

Each NIC entry represents an enterprise contact center application network interface controller functional component configured and enabled on the server. The NIC component provides an interface between the enterprise contact center application and a telephony network. The objects in the NIC entry provide the NIC type and the current status of the NIC functional component.

The NIC index is a value that uniquely identifies an entry in the network interface controller table. The value of this object is arbitrarily assigned by the SNMP agent.

The Network Interface Controller (NIC) type indicates which telephony network that this NIC functional component provides an interface. The possible options are: 'generic': Generic NIC (typically only used for testing) 'att': AT&T NIC 'aucsINAP': AT&T Unisource Capability Set Intelligent Network Application Protocol NIC 'cain': Nortel Carrier Advanced Intelligent Network NIC 'crsp': Call Routing Service Protocol NIC 'cwc': Cable & Wireless Communications NIC 'gktmp': Gatekeeper Transaction Message Protocol NIC 'incrp': Intelligent Network Call Routing Protocol NIC 'mci': MCI NIC 'nortel': Nortel NIC 'ntl': ntl Group Ltd. NIC 'sprint': Sprint NIC 'ss7in': Signaling System 7 Intelligent Network NIC 'stentor': Stentor NIC 'timINAP': Telecom Italia Mobile Intelligent Network Application Protocol NIC Enumeration: 'gktmp': 7, 'mci': 9, 'incrp': 8, 'generic': 1, 'aucsINAP': 3, 'nortel': 10, 'ss7in': 13, 'crsp': 5, 'att': 2, 'stentor': 14, 'ntl': 11, 'cain': 4, 'cwc': 6, 'sprint': 12, 'timINAP': 15.

The NIC status is the last known status of the enterprise contact center application network interface controller functional component.

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.

Each logger entry represents an enterprise contact center application logger functional component configured and enabled on the server. The logger component maintains the enterprise contact center solution configuration and real-time data store. The objects in each logger entry provide configuration and component status information.

The logger side indicates which of the duplex pair this entry represents of an enterprise contact center application fault tolerant logger functional component. The logger side value is either 'A' or 'B'. For simplex configurations, the logger side value defaults to 'A'.

The logger type object indicates which type of enterprise contact center application logger is installed on this server. The logger type varies based on the configuration of the contact center solution. 'standard': The default logger type configured for an enterprise contact center solution. 'nam': The network application manager (NAM) logger type is installed at a telephony service provider and supports the routing of inbound voice calls to a customer intelligent contact management application solution. 'cicm': The customer intelligent contact manager (CICM) logger type is installed as part of a customer instance of an enterprise contact center application solution. The CICM component manages contacts routed by the NAM component, distributing contacts to customer premise peripheral devices or contact center agents. Enumeration: 'cicm': 3, 'nam': 2, 'standard': 1.

The router side A name object holds the host name of the side 'A' router that this enterprise contact center application logger functional component is associated. The logger component must be connected to a router that is part of the same instance. The logger connects to the router via a 'private' interface -- a closed subnet that guarantees a quality of service level that will not impact the performance of the contact center application. This private subnet is not accessible by the management station. _____ | | | NMS | |_____| | Visible Subnet =======+===+==========+================+=============+======= | | | | ____|____ ___|__ ___|__ ____|____ | | | | | | | | | RouterA | | PG1A | | PG1B | | RouterB | |_________| |______| |______| |_________| | |____private_____| | | | =======+=======+=============================+=======+======= | Private Subnet | ____|____ ____|____ | | | | | LoggerA | | LoggerB | |_________| |_________|

The router side B name object holds the host name of the side 'B' router that this enterprise contact center application logger functional component is associated. The logger component must be connected to a router that is part of the same instance. The logger connects to the router via a 'private' interface -- a closed subnet that guarantees a quality of service level that will not impact the performance of the contact center application. This private subnet is not accessible by the management station. _____ | | | NMS | |_____| | Visible Subnet =======+===+==========+================+=============+======= | | | | ____|____ ___|__ ___|__ ____|____ | | | | | | | | | RouterA | | PG1A | | PG1B | | RouterB | |_________| |______| |______| |_________| | |____private_____| | | | =======+=======+=============================+=======+======= | Private Subnet | ____|____ ____|____ | | | | | LoggerA | | LoggerB | |_________| |_________|

The logger duplex pair name object is the host name of the duplex pair (i.e. the other side) server of an enterprise contact center application fault tolerant logger component. If this component is not part of a duplex pair (i.e. simplex), the object value will be the null string. The logger connects to its duplex pair via a 'private' interface -- a closed subnet that guarantees a quality of service level that will not impact the performance of the contact center application. This private subnet is not accessible by the management station.

The logger HDS replication Boolean object indicates whether the logger component will be replicating data to a distributor AW Historical Data Server (HDS). If 'true', the logger feeds historical data at regular intervals to the HDS for long-term storage. In this configuration, administrator reports are generated by accessing data from the HDS rather than the logger in order to remove the performance impact of reporting on the logger.

The logger average database write time expresses the average amount of time, in 100 nanosecond units, required to write data to a table in the central controller database. This value represents the average time per write of the last 100 write operations. This object is a good indicator of contention for database access.

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.

Each distributor administrator workstation (AW) (also known as the administration and data server) entry represents an enterprise contact center application distributor AW functional component configured on this server. The distributor AW component maintains a configuration, historical and 'detail data' database that serves one or more reporting clients or provides a data feed to data archival or aggregation components. The objects in each distributor AW entry provide configuration and component status information.

The distributor administrator workstation (AW) (also known as the administration and data server) side indicates which of the duplex pair this entry represents of an enterprise contact center application distributor AW functional component. The Distributor Admin Workstation implements an N+1 fault tolerance model vs. the 1+1 model implemented by the Router and Peripheral Gateways. As such, this object has been deprecated since it is inconsistent with the Dist AW fault tolerance model.

The distributor administrator workstation (AW) (also known as the administration and data server) type object indicates which type of enterprise contact center application distributor AW is installed on this server. The distributor AW type varies based on the size and configuration of the contact center solution. 'standard': The default distributor AW type configured for an enterprise contact center solution. 'nam': The network application manager (NAM) distributor AW type is installed at a telephony service provider. 'cicm': The customer intelligent contact manager (CICM) distributor AW type is installed as part of a customer instance of an enterprise contact center hosted application solution. Enumeration: 'cicm': 2, 'nam': 1, 'standard': 0.

The distributor administrator workstation (AW) (also known as the administration and data server) administrative site name is a user-defined textual name that uniquely identifies the location or the configuration of the distributor AW component.

The distributor administrator workstation (AW) (also known as the administration and data server) router side A name object holds the host name of the side 'A' router that this enterprise contact center application distributor AW functional component is associated. The distributor AW component must be connected to a router that is part of the same instance. If the side B router is the active router and a failure occurs, the side A router then immediately assumes the role. In this case, the distributor AW will lose its connection to the side B router and thus use this object value to connect to the side A router.

The distributor administrator workstation (AW) (also known as the administration and data server) router side B name object holds the host name of the side 'B' router that this enterprise contact center distributor AW functional component is associated. The distributor AW component must be connected to a router that is part of the same instance. If the side A router is the active router and a failure occurs, the side B router then immediately assumes the role. In this case, the distributor AW will lose its connection to the side A router and thus use this object value to connect to the side B router.

The distributor administrator workstation (AW) (also known as the administration and data server) logger side A name object holds the host name of the side 'A' logger that this enterprise contact center application distributor AW functional component is associated. The distributor AW component must be connected to a logger that is part of the same instance. If the side B logger is the active logger and a failure occurs, the side A logger then immediately assumes the role. In this case, the distributor AW will lose its connection to the side B logger and thus use this object value to connect to the side A logger.

The distributor administrator workstation (AW) (also known as the administration and data server) logger side B name object holds the host name of the side 'B' logger that this enterprise contact center application distributor AW functional component is associated. The distributor AW component must be connected to a logger that is part of the same instance. If the side A logger is the active logger and a failure occurs, the side B logger then immediately assumes the role. In this case, the distributor AW will lose its connection to the side A logger and thus use this object value to connect to the side B logger.

The distributor administrator workstation (AW) (also known as the administration and data server) duplex pair name object is the host name of the duplex pair (i.e. the other side) server of an enterprise contact center application distributor AW component. If this component is not part of a duplex pair (i.e. simplex), the object value will be the null string. The Distributor Admin Workstation implements an N+1 fault tolerance model vs. the 1+1 model implemented by the Router and Peripheral Gateways. As such, this object has been deprecated since it is inconsistent with the Dist AW fault tolerance model.

The distributor administrator workstation (AW) (also known as the administration and data server) HDS enabled Boolean object indicates whether this enterprise contact center application distributor AW has a historical database server (HDS) configured and enabled. If so, this distributor AW will receive replicated data from the logger at periodic intervals and add the data to the HDS. Administration clients will generate reports based on the data in this HDS.

The distributor administrator workstation (AW) (also known as the administration and data server) WebView enabled Boolean object indicates whether this enterprise contact center application distributor AW has a web-based reporting server (WebView) configured and enabled. Having WebView configured and enabled does not imply that a historical database is also present on this server; the data may be accessed by the WebView server from a database on a different host.

The distributor administrator workstation (AW) (also known as the administration and data server) WebView server name object holds the server (universal naming convention (UNC)) name of the server where the enterprise contact center application database resides. The WebView server accesses this database to serve WebView client reports.

The distributor administrator workstation (AW) (also known as the administration and data server) web reskilling URL object holds the URL for the contact center application web reskilling tool. The web reskilling tool allows contact center administrators and supervisors to reskill agents (reassign contact center agents to different skill groups allowing them to take calls of a different topic).

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.

Each PG entry represents an enterprise contact center application peripheral gateway functional component configured on the server. The peripheral gateway component provides an interface to one or more peripheral devices such as a private branch exchange (PBX) or a voice response unit (VRU). The objects in each PG entry provide configuration and component status information as well as a count of peripheral interface manager (PIM) subcomponents that have been configured and enabled.

The PG number is a user-defined numeric identifier for this enterprise contact center application peripheral gateway. The value is limited by the contact center application to a value between 1 and 80; 80 is the maximum number of peripheral gateways supported by the application. This object has been deprecated since its range is now inappropriate; the number of peripheral gateways supported in a deployment increased to 150 in ICM/CC version 7.5 and again up to 250 in ICM/CC version 8.0.

The PG side indicates which of the duplex pair this entry represents of an enterprise contact center application fault tolerant peripheral gateway functional component. The PG side value is either 'A' or 'B'. For simplex configurations, the PG side value defaults to 'A'.

The PG router side A name object holds the host name of the side A router that this enterprise contact center application peripheral gateway functional component is associated. The peripheral gateway component must be connected to a router that is part of the same instance. If the side B router is the active router and a failure occurs, the side A router then immediately assumes the role. In this case, the peripheral gateway will lose its connection to the side B router and thus use this object value to connect to the side A router.

The PG router side B name object holds the host name of the side B router that this enterprise contact center application peripheral gateway functional component is associated. The peripheral gateway component must be connected to a router that is part of the same instance. If the side A router is the active router and a failure occurs, the side B router then immediately assumes the role. In this case, the peripheral gateway will lose its connection to the side A router and thus use this object value to connect to the side B router.

The PG duplex pair name object is the host name of the duplex pair (i.e. the other side) server of an enterprise contact center application fault tolerant peripheral gateway component. If this component is not part of a duplex pair (i.e. simplex), the object value will be the null string.

The PG PIM count object indicates the number of peripheral interface managers configured and enabled for this enterprise contact center application peripheral gateway functional component. This value is limited to 32 - this is the maximum number of PIMs supported on a single peripheral gateway.

The calls in progress object shows the number of calls that are currently active and being managed/monitored by this peripheral gateway.

The agents logged On object shows the number of agents associated with this peripheral gateway that are currently logged on and are being managed/monitored by this peripheral gateway.

The agents ready object shows the number of agents associated with this peripheral gateway that are currently logged on and in a 'Ready' state, i.e., ready to receive calls.

The agents talking object shows the number of agents associated with this peripheral gateway that are currently logged on and taking a call (in a 'Talking' state.

The PG number is a unique numeric identifier for this enterprise contact center application peripheral gateway. The identifier is assigned by the contact center application.

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.

Each PIM entry represents an enterprise contact center application peripheral interface manager functional component configured on the server. The PIM component provides an interface between the enterprise contact center application and a telephony switch: a private branch exchange (PBX), an automatic call distributor (ACD) or a voice response unit (VRU). The objects in each PIM entry provide PIM type information, the current status of the PIM functional component and the host name of the telephony switch it interfaces.

The PIM number is the numeric identifier for this enterprise contact center application PIM. This object value is a user-defined numeric value and is limited to a maximum of 32 since this is the maximum number of PIMs supported on a single peripheral gateway.

The PIM peripheral name is the user-defined textual name of the enterprise contact center application PIM. This name uniquely identifies the PIM.

The PIM peripheral type object specifies the type of the enterprise contact center application PIM, e.g. the brand name and/or model of the automatic call distributor (ACD), private branch exchange (PBX) or voice response unit (VRU).

The PIM status object holds the last known status of the enterprise contact center application peripheral interface manager functional component.

The PIM peripheral host name object holds the host name or IP address of the peripheral (the PBX, ACD or VRU) that the enterprise contact center application PIM will be connected. If there are multiple interfaces to the peripheral, each host name or IP address will be separated by a comma.

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.

Each CG entry represents an enterprise contact center application CTI gateway functional component configured and enabled on the server. The CTI gateway is the solution integration point for desktop CTI clients. The objects in each CG entry provide configuration and component status information.

The CG number is a numeric identifier for this enterprise contact center application CTI gateway. This is a user- defined numeric value and may not be identical to the table index. The value is limited by the contact center application to a value between 1 and 80 as this is the maximum number of CTI gateways supported by the application. This object has been deprecated since its range is now inappropriate; the number of CTI gateways supported in a deployment increased to 150 in ICM/CC version 7.5 and again up to 250 in ICM/CC version 8.0.

The CG side indicates which of the duplex pair this entry represents of an enterprise contact center application fault tolerant CTI gateway functional component. The CG side value is either 'A' or 'B'. For simplex configurations, the CG side value defaults to 'A'.

The CG PG side A name object holds the host name of the side A peripheral gateway (PG) that this enterprise contact center application CTI gateway (CG) functional component is associated. The CG component must be connected to a PG that is part of the same instance. If the side B PG is the active PG and a failure occurs, the side A PG then immediately assumes the role. In this case, the CG will lose its connection to the side B PG and thus use this object value to connect to the side A PG.

The CG PG side B name object holds the host name of the side 'B' peripheral gateway (PG) that this enterprise contact center application CTI gateway (CG) functional component is associated. The CG component must be connected to a PG that is part of the same instance. If the side A PG is the active PG and a failure occurs, the side B PG then immediately assumes the role. In this case, the CG will lose its connection to the side A PG and thus use this object value to connect to the side B PG.

The CG duplex pair name object is the host name of the duplex pair (i.e. the other side) server of an enterprise contact center application fault tolerant CTI gateway component. If this component is not part of a duplex pair (i.e. simplex), the object value will be the null string.

The CG open sessions object indicates the number of sessions (connections) that have been established between the CTI Gateway and CTI clients. These are active sessions that are functioning normally.

The CG other sessions object indicates the total number of sessions (connections) between the CTI Gateway and CTI clients that are not normal, open/active sessions. This includes sessions that are 'opening' (not yet established and initialized), session that are 'closing' (connections being torn down) as well as sessions that are in an 'unknown' state and sessions that have failed. While this object value will fluctuate from time to time, during normal operation, it will stabilize. A steadily increasing value indicates a problem that should be investigated.

The CG number is a unique numeric identifier for this enterprise contact center application CTI gateway. The identifier is assigned by the contact center application.

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.

Each CTI OS entry represents an enterprise contact center application CTI object server functional component configured on the server. The CTI object server, 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. The objects in each CTI OS entry provide configuration and component status information.

The CTI OS server name object specifies the user-defined textual name assigned to this enterprise contact center application CTI OS component to uniquely identify it.

The CTI OS peripheral name is the unique identifier for the peripheral that the enterprise contact center application CTI OS component is associated. This association links the CTI desktop clients with a particular peripheral PBX.

The CTI OS peripheral type object indicates the peripheral type that the enterprise contact center application CTI OS is associated. This also then identifies the peripheral PBX type that the CTI desktop clients are associated.

The CTI OS CG side A name object holds the host name of the side A CTI gateway (CG) that this enterprise contact center application CTI object server (CTI OS) functional component is associated. The CTI OS component must be connected to a CG that is part of the same instance. If the side B CG is the active CG and a failure occurs, the side A CG then immediately assumes the role. In this case, CTI OS will lose its connection to the side B CG and thus use this object value to connect to the side A CG.

The CTI OS CG side B name object holds the host name of the side B CTI gateway (CG) that this enterprise contact center application CTI object server (CTI OS) functional component is associated. The CTI OS component must be connected to a CG that is part of the same instance. If the side A CG is the active CG and a failure occurs, the side B CG then immediately assumes the role. In this case, CTI OS will lose its connection to the side A CG and thus use this object value to connect to the side B CG.

The CTI OS peer name object is the host name of the peer server of an enterprise contact center application CTI object server functional component. If this component does not have a peer, the object value will be the null string. Note that the CTI OS component implements fault tolerance slightly differently than other components of the contact center solution. CTI OS maintains two active peer object servers to serve client desktop CTI applications. If a failure occurs on one of the two servers, its clients will connect to the peer server.

The active clients object holds the number of CTI OS active client mode desktop connections. This value indicates the total number of desktops connected to the CTI OS server. The number of desktops connected to the A and B side of CTI OS determine the total desktops connected through this instance of CTI OS server.

The active monitors object holds the number of CTI OS active monitor mode desktop connections. CTI OS only supports two monitor mode connections per each CTI OS server. This value indicates how many monitor mode connections are in use. Once there are two in use further monitor mode connection attempts are rejected.

The calls in progress object indicates the total number of active calls being tracked by CTI OS. This value shows how many calls are currently being handled by CTI OS. This value should go up and down based on the call arrival rate and the agent call completion rate.

The calls failed object holds the total number of calls that failed via a failure event being reported to CTI OS. If this count begins to rise, the log file should be captured to gather more specific information on the failure events.

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.

Each campaign manager entry represents an enterprise contact center application Outbound Option Campaign Manager server functional component configured on this server. The campaign manager component, which resides on the ICM/CC logger (side A), is responsible for: - Managing when a campaign runs. - Maintaining system and dialer configurations. - Making decisions about which contact records to retrieve from a campaign based upon configurable query rules and then delivering those contact records to dialers. - Distributing configuration data to the import process and all available dialers in the system. - Collecting real-time and historical data and sending it to the Router for subsequent storage and distribution. - Managing the Do Not Call list, ensuring no numbers on it are sent to the Dialers. The objects in each campaign manager entry provide configuration, performance and component status information.

The campaign manager and import processes share a private database on the side A logger. The campaign manager database utilization object shows what percentage of allocated space in the database is currently utilized. An administrator should start paying attention when this value exceeds 80 percent.

The campaign manager is a multithreaded process. There is one main dispatch thread that is involved in most processing. The queue depth object indicates how many messages are queued to this internal dispatch thread. By default, the campaign manager will deliberately restart when this value exceeds 10,000 messages in queue as a self-defense mechanism; the administrator must then investigate the reason for this performance bottleneck.

The campaign manager is a multithreaded process; however, there is one main dispatch thread that is involved in most message processing. The average queue time object shows the average amount of time a message spends in the main dispatch thread queue awaiting processing (in milliseconds).

The campaign manager process feeds several dialer components which manage the dialing of customers for outbound campaigns. The active dialers counter indicates how many dialers are currently registered to this campaign manager.

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.

Each dialer entry represents an enterprise contact center application Outbound Option Dialer functional component configured on the server. The dialer component maximizes the resources in a contact center by dialing several customers per agent. The dialer component resides on the peripheral gateway (PG) server, where it does the following: - Dials customers - Reserves agents - Performs call classification - Calculates agent availability - Keeps outbound dialing at a level where the abandon rate is below the maximum allowed abandon rate The objects in the dialer entry provide information about dependent components, performance metrics and port usage.

The dialer campaign manager name object holds the host name or IP address of the Outbound Option Campaign Manager to which this dialer is associated. The dialer connects to the campaign manager to exchange data related to an outbound dialing campaign.

The dialer campaign manager status indicates the current connection status between this dialer and the Outbound Option Campaign Manager component which is co-resident with the logger (side A).

The dialer CTI server A name object holds the host name or IP address of the contact center application CTI Server side A functional component which this dialer is dependent upon. The dialer connects to the CTI Server to monitor skill group statistics (to choose an agent) and execute call control once an available agent is selected.

The dialer CTI server B name object holds the host name or IP address of the contact center application CTI server side B functional component which this dialer is dependent upon. The dialer connects to the CTI server to monitor skill group statistics (to choose an agent) and execute call control once an available agent is selected.

The dialer CTI server status indicates the current connection status between this dialer and the active CTI server component.

The dialer media router status indicates the current connection status between this dialer and the Media Routing (MR) Peripheral Interface Manager (PIM) component. The dialer uses the MR PIM interface to reserve an available agent as a recipient for a dialed customer call.

The dialer is a multithreaded process which communicates between threads using inter-thread messaging. The queue depth object indicates how many messages are currently queued for the main dispatch thread. When this object is used in combination with the average queue time object, message processing performance can be gauged. By default, the dialer process will deliberately restart when this value exceeds 10,000 messages.

The dialer is a multithreaded process that communicates between threads using messaging. There is one main dispatch thread that is involved in most message processing. The average queue time shows the average amount of time (in milliseconds) that a message spent in the queue before being de-queued for processing. When this object used in combination with the queue depth object, message processing performance can be gauged.

For an agent campaign, the dialer places calls to customers and transfers those customer calls to agents. The talking agents object indicates how many agents are currently talking in the monitored campaign skill group.

The call attempts per second object tracks how many calls the dialer is placing per second, rounded to the nearest integer. If the dialing rate is too high, it can result in network congestion on the voice network which can result in inefficient dialing.

The dialer configured ports object is a count of the total number of ports that have been configured for placing calls to customers and for transferring calls to agents during outbound calling campaigns. During normal operation, the dialer configured ports object value is equal to a sum of busy and idle ports.

The dialer busy customer ports object is a count of the number of ports currently in use for customer calls. The port is the unit on the dialer that places calls to reserve agents and to contact customers.

The dialer busy reservation ports object tracks how many ports are currently busy reserving agents. The port is the unit on the dialer that places calls to reserve agents and to contact customers.

The dialer idle ports object is a count of the number of ports that are currently idle, i.e. there are no calls to customers or to agents using these ports and they are available to the dialer for placing new calls.

The dialer blocked ports object is a count of the number of ports that are currently unusable for placing calls. A blocked port may be an impaired or inoperable port or one that has a 'stuck' call that has not been dropped. A 'stuck' call is a call that has been identified by the application as exceeding a duration threshold.

The event component ID specifies a unique identifier used to correlate multiple notifications generated by a single enterprise contact center application functional component or subcomponent. A functional component constructs its unique identifier based upon configured parameters; all notifications by that component will include this event component ID.

The event state object identifies the state (not to be confused with severity) of the notification and potentially the current state of the functional component that generated the notification. The possible states are: 'clear': The clear state indicates that the condition which generated a previous raise notification has been resolved. 'applicationError': The application error state alerts the recipient that an error exists in the enterprise contact center application but that the error does not affect the operational status of the functional component. 'raise': A raise state identifies a notification received as a result of a health-impacting condition, such as a process failure. A subsequent clear state notification will follow when the error condition is resolved. 'singleStateRaise': The single state raise state indicates that a health-impacting error has occurred and that a subsequent clear state notification will not be forthcoming. An example of a single state raise condition is an application configuration error that requires the system to be stopped and the problem resolved by an administrator before the affected component will function properly. Enumeration: 'applicationError': 2, 'clear': 0, 'raise': 4, 'singleStateRaise': 9.

The event message ID is the unique notification message identifier (value) that was assigned by the enterprise contact center application. This identifier is unique for each different notification but consistent for each instance of the same notification.

The event originating node objects specifies the application- defined name of the enterprise contact center application functional component that generated this notification. This name will vary, both in content and in format, based on the component that generated the notification. For example, the name for a router component may be 'RouterA', a combination of the component identification and the 'side' identifier, while the name 'PG1A' is a combination of the peripheral gateway acronym followed by the peripheral gateway number and the 'side' identifier.

The event originating node type indicates the type of enterprise contact center application functional component or subcomponent that generated this notification. The node types are: 'unknown': The notification originates from an unknown source. 'router': The notification was generated by the router functional component. 'pg': The notification was generated by the peripheral gateway functional component. 'nic': The notification was generated by the network interface controller functional component. 'aw': The notification was generated by the administrator workstation functional component. 'logger': The notification was generated by the logger functional component. 'listener': The notification was generated by the listener functional component. The listener is an enterprise contact center application process that collects event messages from the logger for display in a Cisco proprietary event management application that is part of the Remote Management Suite (RMS). 'cg': The notification was generated by the CTI gateway functional component. 'ba': The notification was generated by the Blended Agent functional component. Blended Agent is an enterprise contact center 'outbound option' functional component that manages campaigns of outbound dialing. Enumeration: 'ba': 8, 'unknown': 0, 'cg': 7, 'listener': 6, 'pg': 2, 'aw': 4, 'nic': 3, 'router': 1, 'logger': 5.

Each enterprise contact center application functional component includes one or more operating system processes, each of which performs a specific function. The event originating process object identifies the name of the application process that generated this notification.

The event originating side object specifies the enterprise contact center application functional component fault tolerant side (either 'A' or 'B') that generated this notification.

The Device Management Protocol (DMP) is a session layer protocol used for network communication between enterprise contact center application functional components. The DMP ID uniquely identifies the session layer addresses of an application functional component. A single component may have multiple DMP IDs since a functional component will communicate with other functional components (or its duplex pair) via multiple physical network interfaces and maintain multiple DMP session connections on each interface. Should a communications failure occur, the event DMP ID identifies the physical and logical address that the error occurred.

The event severity object indicates the severity level of this notification. The severity levels are: 'informational': The notification contains important health or operational state information that is valuable to an administrator, however, the event itself does not indicate a failure or impairment condition. 'warning': The notification contains serious health or operational state information that could be a precursor to system impairment or eventual failure. 'error': The notification contains critical health or operational state information and indicates that the system has experienced an impairment and/or a functional failure. Enumeration: 'warning': 2, 'informational': 1, 'error': 3.

The event time stamp object specifies the date and time that the notification was generated on the originating node. All notification timestamps are in Greenwich Mean Time (GMT).

The event text is the full text of the notification. This text includes a description of the event that was generated, component state information and potentially a brief description of administrative action that may be necessary to correct the condition that caused the event to occur.

This object is the compliance statement for entities which implement the Cisco Contact Center Applications MIB.

This object is the compliance statement for entities which implement the Cisco Contact Center Applications MIB.

The general info group defines the general enterprise contact center application information objects. All application servers will populate these objects.

The instance table group defines the enterprise contact center application instance table objects.

The component table group defines the enterprise contact center application functional component table objects.

The component element table group defines the enterprise contact center application functional component element table objects.

The router table group defines the enterprise contact center application router table objects.

The NIC table group defines the enterprise contact center application network interface controller table objects.

The logger table group defines the enterprise contact center application logger table objects.

The distributor AW table group defines the enterprise contact center application distributor admin workstation table objects.

The PG table group defines the enterprise contact center application peripheral gateway table objects.

The PIM table group defines the enterprise contact center application peripheral interface manager table objects.

The CG table group defines the enterprise contact center application CTI gateway table objects.

The CTI OS table group defines the enterprise contact center application CTI object server table objects.

The ICM notification info group defines the enterprise contact center application 'Cisco Unified Intelligent Contact Management' and 'Cisco Unified Contact Center' (Enterprise and Hosted) notification objects.

The ICM events group defines the notification types identified in this MIB.

The Campaign Managers table group defines the enterprise contact center application Outbound Option Campaign Manager table objects.

The Dialer table group defines the enterprise contact center application Outbound Option Dialer table objects.

The general info group sup1 objects supplement the general info group, which defines the general enterprise contact center application information objects. All application servers will populate these objects.

The router table group sup1 objects supplement the router table group, which defines the enterprise contact center application router table objects.

The logger table group sup1 object supplements the logger table group, which defines the enterprise contact center application logger table objects.

The distributor admin workstation table group sup1 object supplements the distributor admin workstation table group, which defines the enterprise contact center application distributor admin workstation table objects.

The PG table group sup1 objects supplement the PG table group, which defines the enterprise contact center application peripheral gateway table objects.

The CG table group sup1 objects supplement the CG table group, which defines the enterprise contact center application CTI gateway table objects.

The CTI OS table group sup1 objects supplement the CTI OS table group, which defines the enterprise contact center application CTI object server table objects.