Which are the three minimum components required in a Cisco Unified CVP VXML "standalone" deployment model? (Choose three.)

Question

Options

• ACisco Unified CVP reporting server
• BCisco Unified CVP Call Studio
• CCisco Unified CVP VXML Server
• DVXML virtual voice browser
• EVRU peripheral gateway
• Fegress voice gateway

• A
  4% (1)
• B
  80% (20)
• D
  12% (3)
• E
  4% (1)

Explanation

In the VXML standalone deployment, the voice gateway (F) receives the call and acts as the VXML client - it fetches and renders VXML pages directly from the Cisco Unified CVP VXML Server (C), which hosts and executes the self-service application logic. Call Studio (B) is required because it is the IDE used to author and package the VXML applications that are deployed to the VXML Server; without it, there is nothing to run. Together, these three form a complete, self-contained IVR loop: Studio builds → VXML Server hosts → Voice Gateway executes.

Why the distractors are wrong:

• A (Reporting Server): Purely optional; standalone deployments can run without any reporting infrastructure.
• D (VXML Virtual Voice Browser): Not needed here because the physical voice gateway has a built-in VXML browser; a virtual VVB is an alternative used in other CVP deployment models.
• E (VRU Peripheral Gateway): This is an ICM/Unified CCE component for routing integration - it only appears in comprehensive or Call Director CVP models, not standalone.

Memory tip: Think "SCG" - Studio Creates, Gateway Grabs - Call Studio creates the app, the VXML Server hosts it, and the voice Gateway grabs and plays it to the caller. Any component beyond those three belongs to a more complex deployment model.

No community discussion yet for this question.