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

Question

Options

• ACisco Unified CVP Call Studio
• BCisco Unified CVP VXML Server
• CCisco Unified CVP reporting server
• Dload balancer
• Eingress voice gateway
• Fegress voice gateway
• GVRU peripheral gateway

• A
  74% (28)
• C
  3% (1)
• D
  16% (6)
• F
  5% (2)
• G
  3% (1)

Explanation

In a Cisco Unified CVP VXML standalone deployment, the model is designed for self-service IVR without full contact center integration. Call Studio (A) is the authoring tool used to build the VXML applications, VXML Server (B) is the core engine that serves those applications, and the ingress voice gateway (E) acts as the VXML browser - it receives inbound calls and fetches/executes VXML pages from the server. These three components form the complete loop: author → serve → execute.

Why the distractors are wrong:

• C (Reporting server): Optional add-on for analytics; not required for basic operation.
• D (Load balancer): Only needed when scaling to multiple VXML servers for redundancy.
• F (Egress voice gateway): Used for transferring calls out to the PSTN or agents, which is a feature of fuller CVP deployments, not standalone.
• G (VRU PG): A Unified CCE/ICM component for contact center routing; standalone bypasses the contact center entirely.

Memory tip: Think "SAVe" - Studio builds it, A VXML server serves it, Voice gateway (executes it via ingress). The standalone model is purely self-service IVR, so anything related to reporting, scaling, or agent routing is out of scope.

No community discussion yet for this question.