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. Distributor Administrator Workstation (AW): The
Distributor AW is a historical database server that serves
one or more reporting clients.
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.
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
AW Administrator Workstation
CG CTI Gateway
CICM Customer Intelligent Contact Manager
CTI Computer Telephony Integration
CTIOS CTI Object Server
DMP Device Management Protocol
ICM Cisco Intelligent Contact Management
IPCC Cisco IP Contact Center
IVR Interactive Voice Response
NAM Network Application Manager
NIC Network Interface Controller
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.
Parsed from file CISCO-CONTACT-CENTER-APPS-MIB.mib
Module: CISCO-CONTACT-CENTER-APPS-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.
Parsed from file CISCO-CONTACT-CENTER-APPS-MIB.my.txt
Company: None
Module: CISCO-CONTACT-CENTER-APPS-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.
ciscoCcaMIB MODULE-IDENTITY LAST-UPDATED "200504051700Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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. Distributor Administrator Workstation (AW): The Distributor AW is a historical database server that serves one or more reporting clients. 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. 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 AW Administrator Workstation CG CTI Gateway CICM Customer Intelligent Contact Manager CTI Computer Telephony Integration CTIOS CTI Object Server DMP Device Management Protocol ICM Cisco Intelligent Contact Management IPCC Cisco IP Contact Center IVR Interactive Voice Response NAM Network Application Manager NIC Network Interface Controller 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. " REVISION "200504051700Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 473 }
ciscoCcaMIB OBJECT IDENTIFIER ::= { ciscoMgmt 473 }
Vendor: Cisco
Module: CISCO-CONTACT-CENTER-APPS-MIB
[Automatically extracted from oidview.com]
ciscoCcaMIB MODULE-IDENTITY LAST-UPDATED "200905061700Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "200905061700Z" DESCRIPTION "This is the second version of this MIB module; this revision aligns with release 8.0 of Cisco Unified Intelligent Contact Management and Contact Center Enterprise and Hosted products." REVISION "200504051700Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 473 }
ciscoCcaMIB MODULE-IDENTITY LAST-UPDATED "200905061700Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "200905061700Z" DESCRIPTION "This is the second version of this MIB module; this revision aligns with release 8.0 of Cisco Unified Intelligent Contact Management and Contact Center Enterprise and Hosted products." REVISION "200504051700Z" DESCRIPTION "This is the initial version of this MIB module." ::= { ciscoMgmt 473 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.473.0 | ciscoCcaMIBNotifs | 1 | 1 | None |
| 1.3.6.1.4.1.9.9.473.1 | ciscoCcaMIBObjects | 4 | 169 | None |
| 1.3.6.1.4.1.9.9.473.2 | ciscoCcaMIBConform | 2 | 27 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.423 | ciscoIkeConfigMIB | 3 | 93 | This is a MIB Module for configuring and viewing IKE parameters and policies. Acronyms The following acronyms are used in this do… |
| 1.3.6.1.4.1.9.9.424 | ciscoCableMeteringMIB | 3 | 53 | This is the MIB module for Usage Based Metering for the DOCSIS-compliant Cable Modem Termination Systems (CMTS). Usage Based Mete… |
| 1.3.6.1.4.1.9.9.426 | ciscoLinkErrorMonitorMIB | 3 | 34 | The MIB module for managing Link Error Monitoring Feature on devices. Link Error Monitoring Feature provides a mechanism to monito… |
| 1.3.6.1.4.1.9.9.427 | ciscoZsExtMIB | 3 | 33 | The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the … |
| 1.3.6.1.4.1.9.9.428 | ciscoIkeFlowExtMIB | 3 | 18 | This MIB module is an extension to CISCO-IKE-FLOW-MIB and contains Cisco Specific extensions for monitoring IKE. It is for monito… |
| 1.3.6.1.4.1.9.9.429 | ciscoIkeFlowMIB | 3 | 80 | This is a MIB module for monitoring the structures and status of IPsec control flows based on Internet Key Exchange protocol. The… |
| 1.3.6.1.4.1.9.9.430 | ciscoFcDeviceAliasMIB | 3 | 14 | The MIB module for the management of Device Aliases in a Fibre Channel Fabric. A Fibre Channel fabric consists of devices such as… |
| 1.3.6.1.4.1.9.9.431 | ciscoIPsecProvisioningMIB | 3 | 98 | IPSec is the next-generation network layer crypto framework described in RFC2401-2411. This MIB defines the IPsec configurations.… |
| 1.3.6.1.4.1.9.9.432 | ciscoEnhancedIpsecFlowMIB | 3 | 330 | This is a MIB Module for monitoring the structures and status of IPSec-based networks. The MIB has been designed to be adopted as… |
| 1.3.6.1.4.1.9.9.433 | ciscoCFSMIB | 3 | 102 | This MIB applies to one or more of a set of devices which have connectivity through some kind of 'fabric'. Many features which ru… |
| 1.3.6.1.4.1.9.9.434 | ciscoIpNetworkDiscoveryMIB, ciscoIsnsIpNetDiscoveryMIB | 3 | 58 | MIB to provide the information about the disjoint IP networks connected to the various gigabit ethernet interfaces in the 'Fabric… |
| 1.3.6.1.4.1.9.9.435 | ciscoFcMulticastMIB | 3 | 14 | MIB module for monitoring and configuring Fibre Channel Multicast feature. |
| 1.3.6.1.4.1.9.9.436 | ciscoDNSClientMIB | 3 | 28 | The MIB module for entities implementing the client side of the Domain Name System (DNS) protocol. |
| 1.3.6.1.4.1.9.9.437 | ciscoPortTrackMIB | 2 | 18 | A MIB to configure the Port-Track feature. When a link goes down, all the services which depend on the link are notified of the o… |
| 1.3.6.1.4.1.9.9.438 | ciscoIPsecSignalingMIB | 3 | 140 | This MIB Module models status, performance and failures of a protocol with the generic characteristics of signalling protocols us… |
| 1.3.6.1.4.1.9.9.439 | ciscoCcmeMIB | 3 | 338 | This MIB allows management of Cisco CallManager Express (CCME) feature in Cisco IOS. CCME is optional software feature that enabl… |
| 1.3.6.1.4.1.9.9.441 | ciscoSrstMIB | 3 | 149 | This MIB allows management of Cisco Survivable Remote Site Telephony (SRST) feature in Cisco IOS. SRST is an optional software fe… |
| 1.3.6.1.4.1.9.9.443 | ciscoCommonMgmtMIB | 3 | 37 | MIB module for integrating different elements of managing a device. For example, different device access methods like SNMP, CLI, … |
| 1.3.6.1.4.1.9.9.445 | ciscoQinqVlanMIB | 3 | 25 | This MIB defines configuration and monitoring capabilities relating to 802.1QinQ interfaces. QinQ interfaces are capable of term… |
| 1.3.6.1.4.1.9.9.447 | ciscoScsiFlowMIB | 3 | 99 | A SCSI Flow is described as a SCSI Initiator SCSI Target combination. This MIB is used to configure and monitor SCSI Flows. Gloss… |
| 1.3.6.1.4.1.9.9.448 | ciscoSsmProvMIB | 2 | 26 | This MIB is used to provision features on a Data Path Processor (DPP) of a Storage Service Module (SSM). A DPP is assigned to a c… |
| 1.3.6.1.4.1.9.9.449 | ciscoEigrpMIB | 3 | 103 | Enhanced Interior Gateway Protocol (EIGRP) is a Cisco proprietary distance vector routing protocol. It is based on the Diffusin… |
| 1.3.6.1.4.1.9.9.450 | ciscoCableAdmCtrlMIB | 3 | 123 | This MIB module defines the managed objects enabling the management of Cable Modem Termination System (CMTS) admission control. CM… |
| 1.3.6.1.4.1.9.9.451 | ciscoIpUrpfMIB | 3 | 47 | Unicast Reverse Path Forwarding (URPF) is a function that checks the validity of the source address of IP packets received on an … |
| 1.3.6.1.4.1.9.9.454 | ciscoDot11LbsMIB | 3 | 23 | This MIB module supports network management for Location Based Services on IEEE 802.11 wireless LAN devices. Location Based Serv… |
| 1.3.6.1.4.1.9.9.455 | ciscoImageTc | 0 | 0 | This MIB module defines the textual conventions used in the enhanced image MIB. Glossary: Base Image Essential part of the operatin… |
| 1.3.6.1.4.1.9.9.456 | ciscoDot11WidsMIB | 3 | 50 | This MIB is intended to be implemented on the following IOS based network entities for the purpose of providing network managemen… |
| 1.3.6.1.4.1.9.9.457 | ciscoWdsIdsMIB | 2 | 18 | This MIB is intended to be implemented on all IOS based network entities that provide Wireless Domain Services, for the purpose o… |
| 1.3.6.1.4.1.9.9.458 | ciscoApplianceRedundancyMIB | 3 | 47 | This mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management applia… |
| 1.3.6.1.4.1.9.9.459 | ciscoBitsClockMIB | 3 | 21 | This MIB provides information on Building Integrated Timing Supply(BITS) clocking sources and modes of operations. It is used to… |
| 1.3.6.1.4.1.9.9.460 | ciscoTpcMIB | 3 | 24 | The MIB module for Third Party Copy(TPC): Third Party Copy derives its name from the fact that there are three entities involved … |
| 1.3.6.1.4.1.9.9.461 | ciscoEtherCfmMIB | 3 | 39 | This MIB module defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM). CFM is an end-to-e… |
| 1.3.6.1.4.1.9.9.463 | ciscoSanTapMIB | 3 | 30 | MIB module to provide information about the SanTap service configuration. SanTap is a fibre channel switch based capability that p… |
| 1.3.6.1.4.1.9.9.466 | ciscoEthernetAccessMIB | 2 | 20 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to an edge dev… |
| 1.3.6.1.4.1.9.9.467 | ciscoCryptoAcceleratorMIB | 3 | 107 | The MIB module for monitoring the identity, status, activity and faults of crypto accelerator (CA) modules used in devices implem… |
| 1.3.6.1.4.1.9.9.468 | ciscoContextMappingMIB | 2 | 35 | A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple… |
| 1.3.6.1.4.1.9.9.470 | ciscoEnhancedSlbMIB | 3 | 106 | The MIB for managing Server Load Balancing Manager(s), and products supporting Server Load Balancing(SLB) features. This MIB exten… |
| 1.3.6.1.4.1.9.9.471 | ciscoFlexLinksMIB | 3 | 36 | This MIB module is for configuration and status query of Flex Links feature on the Cisco device. Flex Links are a pair of Layer 2… |
| 1.3.6.1.4.1.9.9.472 | ciscoModuleVirtualizationMIB | 3 | 35 | This MIB provides a way to create virtual contexts, and managing them. A virtual context is logical partition of a physical devi… |
| 1.3.6.1.4.1.9.9.474 | ciscoFilterGroupMIB | 3 | 55 | The MIB module is for creating and configuring object groups to support packet filtering and access control on IP and other proto… |
| 1.3.6.1.4.1.9.9.479 | ciscoCableWidebandMIB | 3 | 77 | This is the MIB module for the support of Channel Bonding Protocol for the Cable Modem Termination System (CMTS). Wideband DOCSIS… |
| 1.3.6.1.4.1.9.9.480 | ciscoL4L7moduleResourceLimitMIB | 4 | 100 | The MIB module for managing resource classes and configuring limits(max/min) to different resources. The resource referenced in … |
| 1.3.6.1.4.1.9.9.482 | ciscoInterfaceTopNExtMIB | 3 | 16 | This MIB module is an extension to INTERFACETOPN-MIB. It provides additional management information for sorting device interfaces. |
| 1.3.6.1.4.1.9.9.483 | ciscoIpRanBackHaulMIB | 3 | 248 | This MIB provides information on the IP-RAN traffic from cell site to aggregation site in the following situations. In an GSM en… |
| 1.3.6.1.4.1.9.9.484 | ciscoNacNadMIB | 3 | 157 | This MIB module is for the configuration of a Network Access Device (NAD) on the Cisco Network Admission Control (NAC) system. End… |
| 1.3.6.1.4.1.9.9.485 | ciscoRttMonTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and CISCO-RTTMON-ICMP-MIB, but they are not … |
| 1.3.6.1.4.1.9.9.486 | ciscoRttMonIcmpMIB | 3 | 7 | An extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics such a… |
| 1.3.6.1.4.1.9.9.487 | ciscoRttMonRtpMIB | 3 | 8 | An extension to the CISCO-RTTMON-MIB for Cisco IP SLA RTP operation, Real-Time Transport Protocol(RFC 1889). This operation provi… |
| 1.3.6.1.4.1.9.9.488 | ciscoFirewallTc | 0 | 0 | This MIB module defines textual conventions that are commonly used in modeling management information pertaining to configuration… |
| 1.3.6.1.4.1.9.9.490 | ciscoNetintMIB | 3 | 11 | This MIB module is for Network Interrupt information on Cisco device. |
| 1.3.6.1.4.1.9.9.491 | ciscoUnifiedFirewallMIB | 3 | 235 | Overview of Cisco Firewall MIB ============================== This MIB Module models status and performance statistics pertaining … |
| 1.3.6.1.4.1.9.9.492 | ciscoCefMIB | 3 | 192 | Cisco Express Forwarding (CEF) describes a high speed switching mechanism that a router uses to forward packets from the inbound … |
| 1.3.6.1.4.1.9.9.493 | ciscoCefTextualConventions | 0 | 0 | ciscoCeftextualConventions |
| 1.3.6.1.4.1.9.9.494 | ciscoEntityRedunTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Entity Redundancy MIBs. |
| 1.3.6.1.4.1.9.9.495 | ciscoPsdClientMIB | 3 | 44 | This MIB module manages the client side functionality of the Persistent Storage Device(PSD). This MIB instrumentation is for conf… |
| 1.3.6.1.4.1.9.9.497 | cGgsnSAMIB | 3 | 247 | This MIB module manages the service-aware feature of Gateway GPRS Support Node (GGSN). This MIB is an enhancement of the CISCO-GG… |
| 1.3.6.1.4.1.9.9.498 | ciscoEntityRedunMIB | 3 | 93 | This management information module supports configuration, control and monitoring of redundancy protection for various kinds of c… |
| 1.3.6.1.4.1.9.9.500 | ciscoStackWiseMIB | 3 | 111 | This MIB module contain a collection of managed objects that apply to network devices supporting the Cisco StackWise(TM) technolo… |
| 1.3.6.1.4.1.9.9.504 | ciscoSwitchMulticastMIB | 3 | 108 | This MIB module defines management objects for the Multicast Switching features on Cisco Layer 2/3 devices. Definition of some of … |
| 1.3.6.1.4.1.9.9.505 | cpkiMIB | 3 | 44 | A networking device may provide several security services and protocols like SSL, SSH, IPSec/IKE etc. which need identities … |
| 1.3.6.1.4.1.9.9.507 | ciscoPolicyGroupMIB | 3 | 35 | The MIB module is for configuration of policy and policy group. A policy group can be described as a set of entities identified b… |
| 1.3.6.1.4.1.9.9.508 | ciscoSlbHealthMonMIB | 3 | 62 | An extension to the CISCO-SLB-EXT-MIB for SLB health monitoring probes. SLB: Server Load Balancing. Server load balancing provides… |
| 1.3.6.1.4.1.9.9.509 | ciscoWdsInfoMIB | 3 | 141 | This MIB is intended to be implemented on all Cisco network entities that provide Wireless Domain Services (WDS). The WDS provide… |
| 1.3.6.1.4.1.9.9.510 | ciscoErmMIB, ciscoVoiceLmrMIB | 3 | 176 | This MIB module provides management of voice tone signal as static injected tone for Land Mobile Radio The tone signal includes … |
| 1.3.6.1.4.1.9.9.511 | ciscoCbpTargetTCMIB | 0 | 0 | This MIB module defines Textual Conventions for representing targets which have class based policy mappings. A target can be any … |
| 1.3.6.1.4.1.9.9.512 | ciscoLwappWlanMIB | 3 | 249 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weigh… |
| 1.3.6.1.4.1.9.9.513 | ciscoLwappApMIB | 4 | 386 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.514 | ciscoLwappTextualConventions | 0 | 0 | This module defines textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Controlle… |
| 1.3.6.1.4.1.9.9.515 | ciscoLwappWebAuthMIB | 4 | 43 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.516 | ciscoLwappLinkTestMIB | 3 | 57 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.517 | ciscoLwappReapMIB | 3 | 63 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.518 | ciscoLwappMfpMIB | 4 | 64 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.519 | ciscoLwappIdsMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.520 | ciscoLwappCcxRmMIB | 3 | 45 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.521 | ciscoLwappWlanSecurityMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.522 | ciscoLwappDot11ClientCalibMIB | 3 | 50 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.523 | ciscoLwappClRoamMIB | 3 | 61 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| ... | ||||