210-060 · Question #315
While trying to register to Cisco UCM, a Cisco IP phone reports TFTP authorization failure. Which cause of this issue is true?
The correct answer is A. DHCP option 150 has the incorrect TFTP address configured. A Cisco IP phone reports a TFTP authorization failure when DHCP option 150 contains the wrong TFTP server address, preventing the phone from locating its configuration file.
Question
While trying to register to Cisco UCM, a Cisco IP phone reports TFTP authorization failure. Which cause of this issue is true?
Options
- ADHCP option 150 has the incorrect TFTP address configured.
- BThe phone has a cabling issue.
- CThe TFTP address for the phone is not in the CTL file.
- DA firewall in the network is blocking access.
How the community answered
(20 responses)- A75% (15)
- B5% (1)
- C5% (1)
- D15% (3)
Why each option
A Cisco IP phone reports a TFTP authorization failure when DHCP option 150 contains the wrong TFTP server address, preventing the phone from locating its configuration file.
DHCP option 150 is the mechanism by which a Cisco IP phone receives the IP address of its TFTP server. If this option is misconfigured with an incorrect address, the phone cannot contact the correct TFTP server and fails to download its configuration, producing a TFTP authorization failure during the registration process.
A cabling issue would result in a complete loss of network connectivity, not a specific TFTP authorization failure message.
The CTL (Certificate Trust List) file governs trusted server certificates in secure mode and does not determine basic TFTP server reachability for non-secure phone registration.
A firewall blocking access would produce a connection timeout or refused connection, not a TFTP authorization failure.
Concept tested: DHCP option 150 TFTP server address assignment
Source: https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/200510-Cisco-IP-Phone-Registration-Process-in.html
Topics
Community Discussion
No community discussion yet for this question.