I am using the Distro Endpoint Manager to provision Polycom phones. The phones obtain the TFTP server address from DHCP Option 66. All is well and it works perfectly.
I am now trying to provision Linksys SPA 2102’s and it seems that the ATA is not responding to the option 66 data. Using wireshark I don’t see anything coming from the ATA on bootup, however, if I give the ATA the full TFTP server path under Provisioning/Configuration Profile/Profile Rule provisioning takes place without trouble and wireshark shows the download taking place.
Still does not work with Option 150 set with tftp server address. Have searched extensively but can’t find any information on 2102 auto provisioning setup. Can anyone point me to something.
I am continuing on my learning curve with the endpoint manager and have now moved on to the GXP1450 which is not picking up the configuration file. I can see the config file has been generated and is stored in /tftpboot and I can see that the phone has picked up the tftp server url from option66.
This is what is happening during the boot process (using tshark):
It seems that the phone makes a tftp request for a file language.txt which is not present and continues to boot when told the file is not there, the phone then attempts to contact the Grandstream provisioning server. My understanding from the Grandstream documentation is that when the Grandstream server does not respond after several attempts the phone should try the option 66 server. That does not appear to be happening and things go no further.
I do not think this is an endpoint manager problem but something to do with the phone. Has anyone any experience of this sort of thing?
I had similar trouble though with a different phone… have you entered the “/tftpboot/” parameter in the phone programming? If yes, try removing it (that worked for me). If no, then try adding it. Sorry if this answer seems elementary but it worked for me and I happened across this post so I thought I’d toss in my $.02
Whoops, ignore my question above. Our DHCP server was just configured improperly as it was sending the wrong IP for the TFTP Server once I fixed that it worked right away after reboot using factory settings.