FIXED: Host is not a tftp server

[hckeith]

Just a quick update.

I've been reading up on the TFTP protocol, and it's not firewall friendly. The issue appears to be firewall related.

Rather than using TFTP, I'm trying out provisioning via other protocols. HTTP provisioning is working fine (ultimately will use HTTPS and/or authentication).

So, the phone responding with 'Host is not a TFTP server', appears to be the error you get when no response is received by the phone from the TFTP server. The way I'd try and explain this is, if your phones are behind a firewall, they request a TFTP connection on UDP 69, but the file transfer can then take place on a random (but dynamically negotiated) UDP port. You'd have to NAT all UDP ports through to your phone for TFTP provisioning to work.
Indeed, I did test this by NAT'ing all UDP traffic from the server to the phone, and it did actually provision via TFTP. Obviously unless you only have one phone on your internal network, with an internal static IP, NAT'ing traffic from one server to multiple phones is not possible, so in the scenario where your TFTP server is on a separate network to your phones with a firewall inbetween, an alternative provisioning protocol (that uses only a single port for everything - FTP probably wouldn't work either), is the way to go.

I'll mark this as 'fixed' as the issue wasn't really phone related (but the error in the logs didn't make much sense at the time). Hopefully this will help someone else out who's stuck.

Perhaps a more meaningful error in the logs such as 'no reply from TFTP server' would be appropriate?