Drag and drop the XML snippets onto the AXL request to build a request that sets the cluster-wide Call Park Reversion Timer to 2 minutes. Not all options are used.

Question

Explanation

The options field in your message is empty ({}), so I can't tell you exactly which XML snippets to drag where. That said, I can give you a thorough explanation of the concept so you can answer any variant of this question.

Overall Goal

You're using Cisco's AXL (Administrative XML) API - a SOAP-based web service - to programmatically update a service parameter in Cisco Unified Communications Manager (CUCM). Specifically, you're setting the Call Park Reversion Timer to 2 minutes (120 seconds) across every node in the cluster simultaneously.

Why AXL and Not the GUI?

The GUI (CUCM Admin > System > Service Parameters) works fine for one-off changes, but AXL is used for automation, scripting, and exam simulations that test whether you understand the underlying API structure.

Structure of the Correct AXL Request

<soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:ns="http://www.cisco.com/AXL/API/14.0">
  <soapenv:Header/>
  <soapenv:Body>
    <ns:updateServiceParameter>
      <processNodeName>*</processNodeName>
      <service>Cisco CallManager</service>
      <name>CallParkReversionTimer</name>
      <value>120</value>
    </ns:updateServiceParameter>
  </soapenv:Body>
</soapenv:Envelope>

Step-by-Step Reasoning

1. updateServiceParameter

This is the AXL method that modifies an existing service parameter. You use updateServiceParameter rather than addServiceParameter because the parameter already exists - you're changing its value, not creating it.

Skip this: The request won't map to any AXL operation and returns a SOAP fault.

2. <processNodeName>*</processNodeName>

The asterisk * is the wildcard that means "apply to all nodes in the cluster." This is what makes the change cluster-wide rather than node-specific. If you named a specific node (e.g., CUCM-Pub), the change would only apply there.

Skip or wrong value: The reversion timer would only change on one node, or the request would target the wrong scope - defeating the cluster-wide requirement.

3. <service>Cisco CallManager</service>

This identifies which CUCM service owns the parameter. Call Park is a feature of the Cisco CallManager service, not the TFTP service or others. AXL requires the exact service name to look up the parameter.

Wrong service: AXL returns an error that the parameter doesn't exist under that service.

4. <name>CallParkReversionTimer</name>

This is the exact parameter name as stored internally by CUCM. The name is case-sensitive and must match exactly.

Wrong name: AXL returns a "parameter not found" error.

5. <value>120</value>

CUCM stores this timer in seconds, not minutes. 2 minutes = 120 seconds. Common distractor values: 2 (wrong unit), 60 (1 minute), 180 (3 minutes).

Wrong value: The timer is set incorrectly; calls parked past the wrong duration will revert too early or too late.

What the Distractors Typically Test

Exam distractors often include:

• addServiceParameter instead of updateServiceParameter
• <processNodeName> with a specific hostname instead of *
• <value>2</value> (minutes instead of seconds)
• Wrong service name like Cisco TFTP

Memory Tip

"Update, Star, CallManager, Name, Seconds"

• Update the parameter (not add)
• Star (*) = cluster-wide
• CallManager service owns Call Park
• Name must be exact
• Value is always in seconds (×60 to convert from minutes)

If you paste the actual XML snippet options from the question, I can tell you exactly which ones to place and which are unused distractors.

No community discussion yet for this question.