You may either be using your Lync Server’s inbuilt DHCP server to respond to these INFORM messages, or you might be using a real DHCP server on your phone subnet to respond to these messages.
If you always receive the error “Did not receive any response for the DHCP discovery message.” when testing the PIN number, then it’s likely that there’s no DHCP server capable of responding to INFORM messages in the subnet that your Lync server is on.
Then in the VVX Phone manager you can change the $script: Web Port variable to whatever value you have chosen.If you want to use HTTPS from the tool, set the $script:use HTTPS setting to $true.Or reboot all the VVX handsets on a Lync system with the “Reboot All” button. Test your FTP Configuration server by simply entering the IP address of the FTP server and pressing the “Test FTP” button.The tool will attempt to connect to the FTP server and download information about key files associated with a Polycom configuration server deployment.Below is an example of the DHCP message that the server sends out for this test: This is awesome, but in some ways not a perfect test.
It will depend on how you have set up your DHCP architecture throughout your sites as to the result of this process.
To get around this you can enable a special DCHP INFORM message responder in the Lync server.
If this setting is set to True, the Lync server will respond to INFORM requests it sees broadcast on the subnet.
In most cases this is about the level of detail you can expect from an end user, because to them the fact that the system voice policy is blocking them from dialling out is the same as their phone having caught fire and exploding while they were out at lunch…
The fact is, they can’t make a call, so the phone is “broken”.
However, you can still have access to the web interface of the VVX phones by editing some configuration settings on the devices (usually done via a configuration FTP server).