Which two things can cause the "Send to VRU" to fail within an ICM script for Cisco Unified Customer Voice Portal? (Choose two.)

Question

Options

• ANo network VRU is configured for the routing client.
• BVRU PIM just got out of service.
• CIncorrect media file name.
• DSend to originator is not enabled.
• EPrimary VRU peripheral gateway is out of service.

• A
  71% (17)
• C
  4% (1)
• D
  17% (4)
• E
  8% (2)

Explanation

A and B are correct because "Send to VRU" requires two things to function: a configured destination and an active communication path. If no Network VRU is associated with the routing client (A), ICM has no target to route the call to, causing immediate failure. If the VRU PIM (Peripheral Interface Manager) goes out of service (B), the interface layer between ICM and CVP is broken, severing the connection needed to complete the transfer.

C is wrong because an incorrect media filename affects prompt playback in later nodes (like Run External Script), not the act of sending the call to the VRU - the call still reaches the VRU successfully before any media is involved. D is wrong because "Send to originator" is a separate feature controlling whether calls can be returned to their source, unrelated to sending a call to a VRU. E is wrong because ICM uses redundant Peripheral Gateways - if the primary VRU PG goes out of service, the secondary PG takes over, so the Send to VRU can still succeed; this is different from the PIM process itself going down (B), which has a more direct and immediate impact.

Memory tip: Think "configured + connected" - Send to VRU needs a configured Network VRU (A) and a connected PIM process (B). Everything else (media files, originator settings, PG redundancy) lives outside that basic two-requirement handshake.

No community discussion yet for this question.