Results for “cct_ivr_mon_services”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CCT_IVR_MON_SERVICES table is a core configuration and runtime-monitoring object within the CCT — Telephony Manager product family in Oracle E-Business Suite. It holds the definitions that the Interactive Voice Response (IVR) monitoring subsystem uses to track, throttle, and health-check the telephony servers participating in an IVR deployment. In EBS 12.1.1 and 12.2.2, this table is owned by the CCT schema and is documented as VALID, containing 37 physical columns. Its purpose is to describe how monitoring should contact each IVR/CTI server, how incoming message traffic is parsed, and what thresholds trigger alerts or intervention.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the object behaves as an independent configuration reference (effectively a hub-like or standalone reference set) rather than a transaction link or a historized satellite. Its only documented outbound foreign key points to FND_SECURITY_GROUPS, indicating that records are segregated by security group — consistent with a multi-org/multi-tenant reference table rather than a pure transactional entity.

Key Information Stored

The table mixes server-identification attributes with monitoring behavior parameters. Among the most significant columns:

• IVRSERVERNAME, MONSERVERNAME, and CTISERVERNAME — logical names of the IVR, monitoring, and CTI servers respectively.
• CTILOGICALID and CTINETWORKTYPE — the CTI logical identifier and network transport type used to reach the telephony layer.
• MONTCPIPDLLNAME and MONCTIDLLNAME — the DLL/interface names the monitor loads for TCP/IP and CTI connectivity.
• MONAPPHOSTNAME, MONAPPPORT, and MONLISTENPORT — the application host and the listening/application ports the monitor binds to.
• MONACTIVETHRESHOLD, MONTRANSLOWTHRESHOLD, MONTRANSHIGHTHRESHOLD, and MONFINISHTHRESHOLD — the activity and transaction-count thresholds that determine health and alerting.
• MONMAXMESSAGEDELAY, MONMSGCLTIME, MONCONSTIME, MONRESTARTTIME, and MONPERIODICALCLEANUPTIME — timing parameters for message delay, cleanup, connection, and restart cycles.
• MONRETRYLIMIT, MAXIVR, MONVERSAPBXTYPE, MONPBXTYPE, USEUUID — retry limits, maximum IVR instances, PBX type designators, and UUID usage flag.
• SECURITY_GROUP_ID — the security partition key referenced from FND_SECURITY_GROUPS.

No surrogate single-column primary key is documented in the provided metadata; the table is best treated as a business-keyed reference set, with IVRSERVERNAME/MONSERVERNAME/SECURITY_GROUP_ID acting as candidate unique keys within a given security group. The physical row identity is therefore inferred from the combination of server naming and security scoping rather than an exposed rowid surrogate.

Common Use Cases and Queries

Typical uses include verifying monitoring coverage, tuning thresholds, and auditing which servers belong to which security group.

• Listing all monitored IVR servers and their ports: SELECT IVRSERVERNAME, MONSERVERNAME, MONLISTENPORT, MONAPPPORT FROM CCT.CCT_IVR_MON_SERVICES;
• Identifying servers with aggressive retry settings: SELECT MONSERVERNAME, MONRETRYLIMIT, MONMAXMESSAGEDELAY FROM CCT.CCT_IVR_MON_SERVICES WHERE MONRETRYLIMIT > 0;
• Security-group scoped reporting: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve group names.
• Threshold tuning reviews comparing MONTRANSLOWTHRESHOLD and MONTRANSHIGHTHRESHOLD against MONACTIVETHRESHOLD.

Related Objects

Key dependencies and joins include:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID, the sole documented foreign key.
• CCT_IVR_MON_SERVICES columns such as IVRSERVERNAME/CTISERVERNAME are referenced by IVR registration and CTI server configuration tables in the CCT schema.
• Telephony Manager concurrent programs and monitoring APIs that consume MONLISTENPORT, MONAPPPORT, and threshold columns at runtime.
• CTI network/DLL configuration objects sharing CTILOGICALID and CTINETWORKTYPE semantics.