Quantcast
Channel: Lync 2010 and OCS - Lync Clients and Devices forum
Viewing all articles
Browse latest Browse all 3260

Polycom CX600 Cannot Sign In

$
0
0

Hi all.

I am having issues with getting a Polycom CX600 device to sign in to Lync (either via USB, or PIN).

I have followed Jeff Schertz's guide at http://blog.schertz.name/2010/12/configuring-lync-server-for-phone-edition-devices/#idc-cover and believe all steps have been completed, but am still having issues.

Ideally I would prefer to use PIN authentication.

When signing in with a 3 digit PIN and password, the phone displays the following:

-Contacting time server

-Connecting to lync server

-Cannot sign in. Please verify your sign in address, domain\user name and password, and try again. Please verify that the domain entered is correct.

The device is obviously able to connect to the lync server, as entering an invalid extension returns an "invalid number" message, and entering an incorrect PIN for a correct extension returns "The PIN does not match the phone number and extension".

Running the Test-CsPhoneBootstrap test on the lync server returns with success after a few seconds.

I can see in the system information that the device has a valid IP, subnet, gateway and DNS server, so I don't believe there are any issues there.

Other topics I have seen on the same issue have suggested re-issuing the SSL certificate for the internal server with additional or wildcard domains in the SAN of the certificate. I have tried this too, without any change.

When attempting to sign in with USB, the prompt is presented in Lync. When completed, the device returns the error "Cannot sign in. Please verify your sign in address, domain\user name and password, and try again. Please verify that the domain entered (my username, without FQDN) is correct."

The only thing that I cannot understand is that the device itself has a time which is 8 hours behind the current time (accurate to the minute) which suggests that the clock is not being set by our internal time server, and maybe via time.microsoft.com instead? In the Jeff Schertz blog post he said that this should not be an issue, but its the only thing "wrong" that I can no identify.

So please, does anyone have any suggestions?

Thanks in advance for your help.


Viewing all articles
Browse latest Browse all 3260

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>