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?
Click on the arrows to vote for the correct answer
A. B. C. D.B.
After successfully using the AXL query ns:updatePhone to upgrade a phone configuration in Cisco Collaboration Solutions, it is possible that the phone may not immediately reflect the change. In such a scenario, another method needs to be performed for the changes to take effect.
The correct answer is option C: ns:rebootPhone.
Explanation: The ns:updatePhone AXL API is used to update phone configuration, but it does not initiate the changes immediately. Instead, the phone will fetch the updated configuration during its next registration with the Unified Communications Manager (UCM).
To expedite the changes, the phone needs to be rebooted manually. This can be achieved by using the ns:rebootPhone AXL API or by restarting the phone using the phone's web interface. Once the phone reboots, it will fetch the updated configuration from UCM and the changes will take effect.
Option A: ns:getPhone is used to retrieve a phone's configuration but does not initiate any changes on the phone.
Option B: ns:restartPhone will restart the phone, but it will not force the phone to fetch the updated configuration from UCM. Therefore, this option is not suitable for resolving the issue described in the question.
Option D: ns:savePhone is used to save the configuration of a phone to the UCM database, but it does not initiate any changes on the phone.
In conclusion, to ensure that updated phone configuration takes effect, the phone must be rebooted using the ns:rebootPhone AXL API or via the phone's web interface.