The tftp process has supported that since 4.x days (it was used for the proxy tftp feature). Endpoints have been preferring it since the Cius days, when phone loads started getting so big traditional TFTP just wouldn’t work.
These days the TFTP process can take requests using tftp on UDP:69, HTTP on tcp:6970, and HTTPS on tls:6971 and tls:6972. The HTTPS ports use different server certs, Tomcat for Jabber clients and CallManager for phones. No, you cannot get rid of TFTP option 150 just yet, that’s still how the phones learn the IP address to use for configuration files. I would imagine it gets replaced by DNS SRV records at some point. - Ryan From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of Scott Voll <svoll.v...@gmail.com> Date: Thursday, November 14, 2019 at 4:53 PM To: cisco-voip list <cisco-voip@puck.nether.net> Subject: [cisco-voip] When did tftp go out the door? I'm looking at a phone register and I see no tftp traffic. All http over 6970. when did this happen? I'm on 12.5 if this is the new norm, then can I get rid of tftp option in dhcp? Scott
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
