All, I am looking to have ONE virtual server to host my TFTP server so that my IP phones can use it for thier settings file, easy enough right? Option 176 is configured in our network.. the issue is that ALL phones for ANY site will try to hone in on the TFTP server configured in that option string... I can set that option string to hone in on different virtual servers that host different TFTP server's IP addresses based on subnet, however I don't want to have to manage several different virtual servers whose only purpose in life is to host a subnet specific TFTP server.
My thought is to find a TFTP server that can upload a settings file based on the subnet the request comes from. For instance:
Phone A is in subnet ending in .101, it boots up, sees that the option string 176 is configured, and routes the request for settings to look at a server at 192.168.1.10, it requests the 46xx settings file, and the tftp server looks at the subnet and responds with the file specific to subnets ending in .101 as that settings file has a call server addressed as 192.168.10.101
Phone B is in subnet ending in .102, it boots up, sees that the option string 176 is configured, and routes the request for settings to look at a server at 192.168.1.10, it requests the 46xx settings file, and the tftp server looks at the subnet and responds with the file specific to subnets ending in .102 as that settings file has a call server addressed as 192.168.10.102
Same name on the settings file (as configured by Avaya) so I cannot change that (that would be TOO EASY), so it seems either I find a TFTP server capable of the above (loading the file based not on different name, but on requesting subnet) OR I get stuck with multiple virtual machines I have to go in and maunally update the settings file on each....
Anyone have any suggestions???
My thought is to find a TFTP server that can upload a settings file based on the subnet the request comes from. For instance:
Phone A is in subnet ending in .101, it boots up, sees that the option string 176 is configured, and routes the request for settings to look at a server at 192.168.1.10, it requests the 46xx settings file, and the tftp server looks at the subnet and responds with the file specific to subnets ending in .101 as that settings file has a call server addressed as 192.168.10.101
Phone B is in subnet ending in .102, it boots up, sees that the option string 176 is configured, and routes the request for settings to look at a server at 192.168.1.10, it requests the 46xx settings file, and the tftp server looks at the subnet and responds with the file specific to subnets ending in .102 as that settings file has a call server addressed as 192.168.10.102
Same name on the settings file (as configured by Avaya) so I cannot change that (that would be TOO EASY), so it seems either I find a TFTP server capable of the above (loading the file based not on different name, but on requesting subnet) OR I get stuck with multiple virtual machines I have to go in and maunally update the settings file on each....
Anyone have any suggestions???