After the AXL query ns:updatePhone is used to upgrade a phone configuration successfully, the phone does not reflect the change. Which other method must be performed for the change to take effect?

Question

Options

• Ans:getPhone
• Bns:restartPhone
• Cns:rebootPhone
• Dns:savePhone

• A
  3% (1)
• B
  78% (29)
• C
  5% (2)
• D
  14% (5)

Explanation

After ns:updatePhone successfully writes the new configuration to the CUCM database, the physical phone is unaware of the change until it re-reads its settings - ns:restartPhone triggers a soft restart (re-registration) that causes the phone to fetch and apply the updated configuration without a full power cycle.

Why the distractors are wrong:

• A. ns:getPhone is a read-only query that retrieves configuration data; it has no ability to push or apply changes to a device.
• C. ns:rebootPhone performs a full hardware-level reset (equivalent to pulling the power cord), which is more disruptive than necessary for a config change - and is a separate, heavier operation.
• D. ns:savePhone is not a valid AXL method; the configuration is already persisted to the database the moment updatePhone returns success.

Memory tip: Think of AXL like editing a config file on a server - updatePhone writes the file, and restartPhone restarts the service to pick it up. Update + Restart = change takes effect.

No community discussion yet for this question.