Which option best describes the issue with a call failing at the Send to VRU node in a comprehensive Cisco CVP deployment?

Question

Options

• ACall type is not mapped to the ICM script.
• BVRU label in the CVP dial plan does not match the dial peer on the VXML gateway.
• CCVP server is running on temporary licenses.
• DVXML application is not deployed to the CVP servers.

• A
  5% (1)
• B
  74% (14)
• C
  5% (1)
• D
  16% (3)

Explanation

When the "Send to VRU" node executes in Cisco ICM, it sends a VRU label (a dialed number string) back to the routing client to transfer the call to CVP. If that label doesn't match a configured dial peer on the VXML gateway, the gateway has no rule to accept and route the call - causing the transfer to fail at exactly this point in the script.

Why the distractors are wrong:

• A - A missing call type-to-script mapping would fail the call before the script ever runs, never reaching the Send to VRU node.
• C - Temporary/grace-period licenses allow CVP to operate; they don't cause node-level transfer failures.
• D - A missing VXML application causes failure after the call reaches the gateway (when it tries to fetch the app), not during the Send to VRU handoff itself.

Memory tip: Think of the VRU label as a street address and the dial peer as the mailbox number - if they don't match exactly, the call gets "returned to sender" right at the Send to VRU handoff. When troubleshooting this node, always verify label ↔ dial peer alignment first.

No community discussion yet for this question.