nerdexam
Cisco

500-440 · Question #50

When using microapps, which core components are required for calls that originate from Cisco Unified Communications Manager to Cisco Unified CVP using Comprehensive mode?

The correct answer is C. CUCM: CTI Route Point and SIP Trunk, ICM: CVP Type 10 VRU and Network VRU labels, VXML. Option C is correct because Comprehensive mode with microapps requires a CTI Route Point (a virtual CUCM device that accepts inbound routing calls) paired with a SIP Trunk to connect CUCM to CVP, while ICM must be configured with a Type 10 VRU - the Network VRU type…

Design Considerations for Cisco Unified CVP

Question

When using microapps, which core components are required for calls that originate from Cisco Unified Communications Manager to Cisco Unified CVP using Comprehensive mode?

Options

  • ACUCM: CTI Route Port, SIP Trunk, ICM: CVP Type 2 VRU, CUBE, VXML Gateway
  • BCUCM: CTI Route Point and SIP Trunk, ICM: CVP Type 2 VRU and Network VRU labels, VXML
  • CCUCM: CTI Route Point and SIP Trunk, ICM: CVP Type 10 VRU and Network VRU labels, VXML
  • DCUCM: CTI Route Port and SIP Trunk, ICM: CVP Type 10 VRU and Network VRU labels, VXML

How the community answered

(28 responses)
  • A
    7% (2)
  • B
    7% (2)
  • C
    82% (23)
  • D
    4% (1)

Explanation

Option C is correct because Comprehensive mode with microapps requires a CTI Route Point (a virtual CUCM device that accepts inbound routing calls) paired with a SIP Trunk to connect CUCM to CVP, while ICM must be configured with a Type 10 VRU - the Network VRU type specifically designed for CVP Comprehensive deployments - along with Network VRU Labels so ICM knows how to pass the call back to CVP, and a VXML Gateway to execute the microapp scripts.

Why the distractors fail:

  • A & D both say "CTI Route Port," which is wrong - a CTI Route Port is a physical/logical port on a CTI device, not the routing endpoint; you need a CTI Route Point for call ingestion.
  • B uses the correct "CTI Route Point" terminology but specifies a Type 2 VRU, which is an older, non-CVP VRU classification; CVP Comprehensive mode mandates Type 10.
  • A also incorrectly includes CUBE, which is a session border element used in specific topologies but is not a core required component for this call flow.

Memory tip: Think "10-Point Comprehensive" - Type 10 VRU goes with Comprehensive mode, and you need a Route Point (not Port). If you see "Type 2" or "Route Port," eliminate that option immediately.

Topics

#Microapps#CVP Type 10 VRU#CUCM-CVP Integration#Comprehensive Mode

Community Discussion

No community discussion yet for this question.

Full 500-440 Practice