MIB Discovery
1930 modules enregistr├ęs
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 473 (ciscoCcaMIB). 1 (ciscoCcaMIBObjects). 2 (cccaComponents). 1 (cccaInstanceTable)
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoCcaMIB. ciscoCcaMIBObjects. cccaComponents. cccaInstanceTable
DescriptionThe 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.