Drag and Drop Question An administrator configures the Cisco Unity Connection call routing table to ensure that Unity Connection plays a legal disclaimer to all direct callers. Drag and drop the…

Question

Exhibit

Answer Area

Explanation

To configure a legal disclaimer for direct calls in Cisco Unity Unity Connection, the process begins with creating a call handler, recording and enabling the alternate greeting, and then configuring it to play entirely without interruption.

Approach. The scenario requires configuring Cisco Unity Connection to play a legal disclaimer to all direct callers, ensuring the message plays entirely before the call proceeds. The steps must be logically ordered to achieve this goal.

1. Step 1: Create a new call handler. This is the foundational step. Before any specific greetings or routing logic can be applied, a dedicated call handler object must be created in Unity Connection to house these configurations.
2. Step 2: Record the message as the alternate greeting. Once the call handler exists, the actual legal disclaimer message needs to be recorded. Assigning it as an 'alternate greeting' within the newly created call handler is a standard practice for special announcements.
3. Step 3: Enable the alternate greeting. A recorded greeting will not play unless it is explicitly enabled within the call handler's greeting settings. This step activates the disclaimer message.
4. Step 4: Configure the alternate greeting to ignore caller input during the greeting. This is a critical step to fulfill the requirement that callers 'hear the message entirely.' By configuring the greeting to ignore caller input, the caller cannot press a key (like # or a digit) to prematurely skip the disclaimer and proceed to the next step in the call handler's menu. This ensures the message plays to completion.

The 'Add a new direct call routing rule...' would be the logical fifth step, applied after the call handler and its greeting are fully configured, to actually direct direct calls to this new disclaimer handler. The question asks for the 'start of the process' with four steps, focusing on the setup of the disclaimer handler itself.

Common mistakes.

• common_mistake. Common mistakes often involve incorrect sequencing or selecting irrelevant options:
• Incorrect order of greeting steps: For example, placing 'Enable the alternate greeting' before 'Record the message as the alternate greeting' is illogical, as you cannot enable a message that has not yet been recorded.
• Omitting 'Configure the alternate greeting to ignore caller input': This choice is crucial. Without this configuration, callers could use DTMF input to bypass the disclaimer message before it finishes, failing to meet the requirement that the message plays 'entirely.'
• Including 'Add a new direct call routing rule to send all direct calls to the new call handler' within the first four steps while omitting a critical configuration step: While this routing rule is essential for the overall solution, it is typically the final step that applies the configured call handler. The first four steps should focus on creating and fully configuring the call handler and its disclaimer greeting. If only four steps are required for the 'start of the process,' the core configuration of the handler and greeting take precedence over the final routing application.
• Selecting 'Add a new forwarded call routing rule': This option is specifically for forwarded calls. The scenario explicitly states the disclaimer should be played to 'all direct callers,' making forwarded call routing rules irrelevant to the primary problem.

Concept tested. Cisco Unity Connection call handler configuration, greeting management (including alternate greetings), greeting behavior settings (e.g., ignoring caller input), and call routing logic for direct calls.

No community discussion yet for this question.