locked
Unable to get Polycom CX600 Phone to register RRS feed

  • Question

  • Hi, 

    I have a phone where I can get the user to sign in for the life of me.  DHCP is working because the phone is getting an IP address.  I have looked at the device logs on the lync server.  By the way this was no easy process you have to download readlog.exe which is a part of windows CE, then concvert the CLG1 log file to .log file and open and read. These are some of the errors I am getting. 

    I am unable to register by pin or USB with lync. Other phones seem to be fine.  I even swapped the phone out, factory reset, everything.  

    I pulled all the errors out of the worst to read log I have ever seen!

    UCD_LOG_ERROR: 08/28/2013|08:46:51 Aries: 08/28/2013|08:46:51.423 C4000A:5520002 ERROR :: CServerConfigModel::LoadValue: UCCP object is not received yet. groupIndex=0, hr=80ee0061
    :00:22.812.532 : Raw data  144 (char), UCD_LOG_ERROR: 08/28/2013|08:46:51 Aries: 08/28/2013|08:46:51.435 C4000A:5520002 ERROR :: CLoggingManager::InternalEnableRemoteLogAccess: Exit
    :00:23.161.748 : Raw data  176 (char), UCD_LOG_ERROR: 08/28/2013|08:46:53 Aries: 08/28/2013|08:46:53.132 C4000A:5520002 ERROR :: NModel::CLogonCredentialManager::AddManagedCredential: Cred type 3 has 1 credentials

    0:23.164.660 : Raw data  235 (char), UCD_LOG_ERROR: 08/28/2013|08:46:53 Aries: 08/28/2013|08:46:53.135 C4000A:5520002 ERROR :: NModel::CLogonCredentialManager::ReadCredential: Read cred(Microsoft_OC1:uri=mdarnell@lwgconsulting.com:certificate:OCS:1) is default, ignored.

    Raw data  176 (char), UCD_LOG_ERROR: 08/28/2013|08:46:53 Aries: 08/28/2013|08:46:53.141 C4000A:5520002 ERROR :: NModel::CLogonCredentialManager::AddManagedCredential: Cred type 2 has 1 credentials

    :00:23.426.936 : Raw data  212 (wchar), UCD_LOG_ERROR: 08/28/2013|08:46:53 UCDAPI: UCDAutoProxy::DownloadAutoProxyInfo: no response to DHCP query

    :00:23.658.611 : Raw data  207 (char), UCD_LOG_ERROR: 08/28/2013|08:46:53 Aries: 08/28/2013|08:46:53.629 C4000A:5520002 ERROR :: NModel::CManagedCredential::~CManagedCredential: type=3, domainAndUser=, passwordAvail=0, cert=00AAC22C, userCert=0


    Wednesday, August 28, 2013 4:16 PM

Answers

  • I figured it out, if you need something quick don't bother opening an MS ticket by the way.  We ran a snooper and found that it was trying to authenticate to our external domain name instead of the internal so I had to change some SRV/Host A records around to get it working, not sure what happened to cause the change since its been in production over a year. 
    • Marked as answer by pslager Thursday, August 29, 2013 1:43 PM
    Thursday, August 29, 2013 1:43 PM

All replies

  • When I run the phonestrap test it says its having trouble reading vendor information if you look at screenshot 2.  I just rebooted another phone and it also is unable to come online.  

    Wednesday, August 28, 2013 4:32 PM
  • Anyone also a brand new user to lync on teh domain can not sign into the lync client getting some TLS authentication errors.  We have a SRV record for _SIPInternalTLS already and an a record pointing to sipinternaltls to the lync front end.  
    Wednesday, August 28, 2013 5:46 PM
  • anyone this is extremely urgent opened up a ticket with MS but thats going to take forever for them to get back to us.  
    Wednesday, August 28, 2013 5:51 PM
  • Please check you have created DNS A record sip.domain.com in DNS Server and added SAN sip.domain.com in the certificate for Lync Front End Server.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, August 29, 2013 9:49 AM
  • I figured it out, if you need something quick don't bother opening an MS ticket by the way.  We ran a snooper and found that it was trying to authenticate to our external domain name instead of the internal so I had to change some SRV/Host A records around to get it working, not sure what happened to cause the change since its been in production over a year. 
    • Marked as answer by pslager Thursday, August 29, 2013 1:43 PM
    Thursday, August 29, 2013 1:43 PM