This table describes CM instances configured on this Device. The
Contact Manager (CM) service is responsible for the handling of
call requests and maintaining contact state. Instances may load
share as well as support different types of contacts. This
service is a critical funnel point to the rest of the system. CM
uses BRE to help direct call flow decision making. The CM must
be able to transparently scale and provide for fault tolerance.
This is best modeled as the CM receiving work from a virtual
queue.
The CM only participates within a single routing domain, and
therefore only talks to a single Work Assigner. Each CM is also
tied to a single MPA. The BRE used by the CM can be shared
among components (both CMs and RMs).
This table has a sparse dependent relationship with the
cmmcaServiceTable and hence uses its index.
Parsed from file CISCO-MMODAL-CONTACT-APPS-MIB.mib
Module: CISCO-MMODAL-CONTACT-APPS-MIB
This table describes CM instances configured on this Device. The
Contact Manager (CM) service is responsible for the handling of
call requests and maintaining contact state. Instances may load
share as well as support different types of contacts. This
service is a critical funnel point to the rest of the system. CM
uses BRE to help direct call flow decision making. The CM must
be able to transparently scale and provide for fault tolerance.
This is best modeled as the CM receiving work from a virtual
queue.
The CM only participates within a single routing domain, and
therefore only talks to a single Work Assigner. Each CM is also
tied to a single MPA. The BRE used by the CM can be shared
among components (both CMs and RMs).
This table has a sparse dependent relationship with the
cmmcaServiceTable and hence uses its index.
This table describes CM instances configured on this Device. The
Contact Manager (CM) service is responsible for the handling of
call requests and maintaining contact state. Instances may load
share as well as support different types of contacts. This
service is a critical funnel point to the rest of the system. CM
uses BRE to help direct call flow decision making. The CM must
be able to transparently scale and provide for fault tolerance.
This is best modeled as the CM receiving work from a virtual
queue.
The CM only participates within a single routing domain, and
therefore only talks to a single Work Assigner. Each CM is also
tied to a single MPA. The BRE used by the CM can be shared
among components (both CMs and RMs).
This table has a sparse dependent relationship with the
cmmcaServiceTable and hence uses its index.
Parsed from file CISCO-MMODAL-CONTACT-APPS-MIB.my.txt
Company: None
Module: CISCO-MMODAL-CONTACT-APPS-MIB
This table describes CM instances configured on this Device. The
Contact Manager (CM) service is responsible for the handling of
call requests and maintaining contact state. Instances may load
share as well as support different types of contacts. This
service is a critical funnel point to the rest of the system. CM
uses BRE to help direct call flow decision making. The CM must
be able to transparently scale and provide for fault tolerance.
This is best modeled as the CM receiving work from a virtual
queue.
The CM only participates within a single routing domain, and
therefore only talks to a single Work Assigner. Each CM is also
tied to a single MPA. The BRE used by the CM can be shared
among components (both CMs and RMs).
This table has a sparse dependent relationship with the
cmmcaServiceTable and hence uses its index.
cmmcaCmTable OBJECT-TYPE SYNTAX SEQUENCE OF CmmcaCmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes CM instances configured on this Device. The Contact Manager (CM) service is responsible for the handling of call requests and maintaining contact state. Instances may load share as well as support different types of contacts. This service is a critical funnel point to the rest of the system. CM uses BRE to help direct call flow decision making. The CM must be able to transparently scale and provide for fault tolerance. This is best modeled as the CM receiving work from a virtual queue. The CM only participates within a single routing domain, and therefore only talks to a single Work Assigner. Each CM is also tied to a single MPA. The BRE used by the CM can be shared among components (both CMs and RMs). This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses its index." ::= { cmmcaServiceInfo 2 }
cmmcaCmTable OBJECT-TYPE SYNTAX SEQUENCE OF CmmcaCmEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table describes CM instances configured on this Device. The Contact Manager (CM) service is responsible for the handling of call requests and maintaining contact state. Instances may load share as well as support different types of contacts. This service is a critical funnel point to the rest of the system. CM uses BRE to help direct call flow decision making. The CM must be able to transparently scale and provide for fault tolerance. This is best modeled as the CM receiving work from a virtual queue. The CM only participates within a single routing domain, and therefore only talks to a single Work Assigner. Each CM is also tied to a single MPA. The BRE used by the CM can be shared among components (both CMs and RMs). This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses its index." ::= { cmmcaServiceInfo 2 }
Vendor: Cisco
Module: CISCO-MMODAL-CONTACT-APPS-MIB
[Automatically extracted from oidview.com]
cmmcaCmTable OBJECT-TYPE SYNTAX SEQUENCE OF CmmcaCmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes CM instances configured on this Device. The Contact Manager (CM) service is responsible for the handling of call requests and maintaining contact state. Instances may load share as well as support different types of contacts. This service is a critical funnel point to the rest of the system. CM uses BRE to help direct call flow decision making. The CM must be able to transparently scale and provide for fault tolerance. This is best modeled as the CM receiving work from a virtual queue. The CM only participates within a single routing domain, and therefore only talks to a single Work Assigner. Each CM is also tied to a single MPA. The BRE used by the CM can be shared among components (both CMs and RMs). This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses its index." ::= { cmmcaServiceInfo 2 }
cmmcaCmTable OBJECT-TYPE SYNTAX SEQUENCE OF CmmcaCmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table describes CM instances configured on this Device. The Contact Manager (CM) service is responsible for the handling of call requests and maintaining contact state. Instances may load share as well as support different types of contacts. This service is a critical funnel point to the rest of the system. CM uses BRE to help direct call flow decision making. The CM must be able to transparently scale and provide for fault tolerance. This is best modeled as the CM receiving work from a virtual queue. The CM only participates within a single routing domain, and therefore only talks to a single Work Assigner. Each CM is also tied to a single MPA. The BRE used by the CM can be shared among components (both CMs and RMs). This table has a sparse dependent relationship with the cmmcaServiceTable and hence uses its index." ::= { cmmcaServiceInfo 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.664.1.6.2.1 | cmmcaCmEntry | 27 | 27 | Each Entry represents a configured CM service. The index in cmmcaServiceTable indexes each entry. |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.664.1.6.1 | cmmcaRmTable | 1 | 13 | This table describes the Resource Manager (RM) Service instances configured on this Device. The Resource Manager (RM) is responsi… |
| 1.3.6.1.4.1.9.9.664.1.6.3 | cmmcaRdaTable | 1 | 10 | This table lists all Resource Desktop Adapter services configured on this Device. The Resource Desktop Adapter (RDA) is used by … |
| 1.3.6.1.4.1.9.9.664.1.6.4 | cmmcaBreTable | 1 | 29 | This table describes the Business Rules Engine (BRE) services configured on this Device. The Business Rules Engine in MMCA allows… |
| 1.3.6.1.4.1.9.9.664.1.6.5 | cmmcaWaTable | 1 | 36 | This table lists the Work Assigner(WA) Service instances configured on this Device. The Work Assigner is responsible for matching… |
| 1.3.6.1.4.1.9.9.664.1.6.6 | cmmcaMpaTable | 1 | 26 | This table describes MPA services configured on this Device. The Media Platform Adapter is a media platform for SIP calls: - SI… |
| 1.3.6.1.4.1.9.9.664.1.6.7 | cmmcaRaTable | 1 | 17 | This table describes Reporting Adapter (RA) services configured on this Device. Reporting adapters listen to event stream that a… |
| 1.3.6.1.4.1.9.9.664.1.6.8 | cmmcaRsTable | 1 | 27 | This table describes Reporting Subsystem(RS) services configured on this Device. Reporting Subsystem (RS) receives reporting mes… |
| 1.3.6.1.4.1.9.9.664.1.6.9 | cmmcaIcmgwTable | 1 | 19 | This table describes ICM Gateway(ICMGW) services configured on this Device. The ICM Gateway talks to the ERS PG of ICM over the G… |