/mcpKeys and NULL Option Data Type Description Name NOT NULL DBINT The peripheral to whose agents the Agent Targeting Rule applies. This is applicable only for an Unified CCE PG or a Cisco Communication Manager PG. PeripheralID NOT NULL DBINT Defines the Agent Targeting Rule type to be used. Agent Targeting Rule Types • Type 1 - Agent ID Each agent is identified by an ID which is in the PreCall and Connect messages. No label is needed, but the agent's extension is included as the label. (This rule is already in use for non-voice routing.) This rule is implicit for System PG integrations (ARS, Unified CCE) when the requesting routing client is associated with the same peripheral on which the targeted agent resides. • Type 2 - Simple Substitution Label An expression must be supplied which contains a series of exclamation points, such as 978497!!!!. The exclamation points are replaced with the agent's extension. If necessary, leading zeroes are supplied, or leading digits deleted, so that length of the extension matches the number of exclamation points. • Type 3 - Translation Route A translation route is used to move the call. This is potentially a very powerful feature, as it allows pre-routing of calls directly to an agent without requiring Direct Inward Dialing (DID) to all agents. Translation routes require the generation of a second label, used to target the agent from the peripheral local routing client. The rule mechanism is applied recursively to generate this label. This means the CallRouter generates a label that allows the call to be translation routed to the PG. The CallRouter also generates a label for the PG to target the agent. If a rule is not found, or if the rule involves a translation route, Rule Type 1 is used. RuleType Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 75 All Tables Agent_Targeting_Rule