Which two situations can cause the "Send to VRU" to fail within an ICM script for Cisco CVP? (Choose two.)

Question

Options

• AVRU PIM just got out of service.
• BNo network VRU is configured for the routing client.
• CSend to originator is not enabled.
• DIncorrect media file name.
• EPrimary VRU peripheral gateway is out of service.

• A
  78% (29)
• C
  14% (5)
• D
  3% (1)
• E
  5% (2)

Explanation

Options A and B are correct because "Send to VRU" in an ICM script requires two fundamental prerequisites: an active communication path to the VRU and a defined destination. The VRU PIM (Peripheral Interface Manager) is the process that maintains the link between ICM and the VRU peripheral - if it goes out of service, ICM loses the ability to hand off the call, causing immediate failure. A Network VRU must also be configured for the routing client; without it, ICM has no mapped destination and the node fails before any call is even dispatched.

Why the distractors are wrong:

• C (Send to originator not enabled) - This setting governs returning a call back to the originating routing client, not the outbound send; it's unrelated to "Send to VRU" execution.
• D (Incorrect media file name) - A bad filename causes a playback failure inside the VRU application after the call arrives; the "Send to VRU" node itself succeeds.
• E (Primary VRU PG out of service) - ICM uses redundant Peripheral Gateways; if the primary is down, the secondary PG takes over, so this alone does not cause the node to fail.

Memory tip: Think of "Send to VRU" needing a working pipe (PIM in service) and a valid address (Network VRU configured). If either is missing, the call has nowhere to go and no way to get there - everything else is a downstream problem.

No community discussion yet for this question.