hi! I've a small sites of about 5 staffs that i want to deploy a few common phone (polycom cx500). This branch has a wan link (<40ms) connection back to the main office where all the Lync front end server and pool are hosted. The end clients (pc,laptop) are assigned by the DHCP server in the main office.

I noticed that when i plug in a polycom phone in the branch office, i can see that the IP address has been assigned in the DHCP server to the phone, but when i try to ping the IP address. It's not reachable (i tried the same port with a laptop, it's getting the ip address, and i can ping the ip address of my pc). The dhcp in the main office has all the configuration required to support the polycom phone, we've at least 100 polycom phone running on Lync in the main office.

When the polycom phone powered on, i can see that it's trying to connect to the time server/Lync server (seems to go through) after i keyed in the extension number, but it will always stop at a page with the message "Certificate web service cannot be found. Please contact your support team" (I've the required dhcp option setup. I've over 100 functioning polycom phones using the same dhcp server), and ask me to key in my extension again.

Any idea what's the issue here? Thanks.

Hello,

Check that DHCP Inform message can be handle on your branch site.

Hi dave_12,

Have you tried to install the latest cumulative update for Lync Phone Edition for CX500 ?

You may receive this error message if the CX500 is running on a previous version of Lync Phone Edition.

http://support.microsoft.com/en-us/kb/2861335

In addition, you can use Wireshark to capture the packet and check what was happening.

Best regards,

Eric

hi! How do i check that?

hi! The phone was brought over from the main office. It was working at the main office. So i guess the software shd be fine. If it works at the main site, it shd work at the branch office too, right?

Thx.

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 17 hours 6 minutes ago

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 Thursday, April 02, 2015 2:15 PM

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 Thursday, April 02, 2015 2:15 PM

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 Thursday, April 02, 2015 2:15 PM

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 Thursday, April 02, 2015 2:15 PM

Issue resolved. For some reason the issue only happens to a particular segment. I tried on another scope and it was working well.

• Marked as answer by dave_12 Thursday, April 02, 2015 2:15 PM