CISCO-CONTACT-CENTER-APPS-MIB Table View

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.