Ive created new vlan for Lync phones Polycom CX600 ,in default data vlan phones working fine but on new vlan I have certificate error  I  on network side c can see traffic to new vlan and routing working fine this what I have in phone  logs

Non-Working Phone Logs

0:00:48.082.536 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Aries: 08/17/2015|06:31:49.598 5510002:5520002 INFO  :: CLogOnScreen::OnBootStrapperStatusChanged: BootStrapper Status: 10001

0:00:48.082.931 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Aries: 08/17/2015|06:31:49.598 5510002:5520002 INFO  :: CollaborationApi::CEventQueue::EventCallback: PEFLOG: OCOMEventQueue - OCOM Queue is empty reqlinquishing, hr=0x0. Queue count=0

0:00:48.170.294 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.686 5510002:59A000A INFO  :: Function: DHCP_WORKITEM::ProcessOption43Suboptions

0:00:48.170.638 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.686 5510002:59A000A INFO  :: Function: DHCP_WORKITEM::DecodeOption43

0:00:48.170.877 :  UCD_LOG_ERROR: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.686 5510002:59A000A ERROR :: HRESULT API failed: 80004005 = ProcessOption43Suboptions( pSubOptionBytes, iLen, bType, dhcp43SubOptInfo )

0:00:48.172.039 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.687 5510002:59A000A INFO  :: Function: DHCP_WORKITEM::ProcessOption43Suboptions

0:00:48.172.383 :  UCD_LOG_INFO: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.688 5510002:59A000A INFO  :: Function: DHCP_WORKITEM::DecodeOption43

0:00:48.172.622 :  UCD_LOG_ERROR: 08/17/2015|06:31:49 Uccapi: 08/17/2015|06:31:49.688 5510002:59A000A ERROR :: HRESULT API failed: 80004005 = ProcessOption43Suboptions( pSubOptionBytes, iLen, bType, dhcp43SubOptInfo )

Working Phone log for the same function

0:00:53.943.389 :  UCD_LOG_INFO: 08/17/2015|07:00:56 Aries: 08/17/2015|07:00:56.665 C4000A:54B0002 INFO  :: CLogOnScreen::OnBootStrapperStatusChanged: BootStrapper Status: 10001

0:00:53.943.779 :  UCD_LOG_INFO: 08/17/2015|07:00:56 Aries: 08/17/2015|07:00:56.665 C4000A:54B0002 INFO  :: CollaborationApi::CEventQueue::EventCallback: PEFLOG: OCOMEventQueue - OCOM Queue is empty reqlinquishing, hr=0x0. Queue count=0

0:00:54.041.957 :  UCD_LOG_WARN: 08/17/2015|07:00:56 Aries: 08/17/2015|07:00:56.763 C4000A:54B0002 WARN  :: NModel::CCertificateProvider::HandleQueryOptions: Registrar found (dhcp 120): 1

0:00:54.042.348 :  UCD_LOG_WARN: 08/17/2015|07:00:56 Aries: 08/17/2015|07:00:56.763 C4000A:54B0002 WARN  :: NModel::CCertificateProvider::HandleQueryOptions: DHCP option 43 response:

https://xxxxxxxxxxxx:443/CertProv/CertProvisioningService.svc

Did you run DHCPUtil for the new scope/server/vlan?  I suspect the phone isn't getting the right DHCP options from the logs above.  Check out Jeff Schertz's article for info on running DHCPUtil to get these settings in: http://blog.schertz.name/2010/12/configuring-lync-server-for-phone-edition-devices/

Hi,

Looks like you do not use a Link Layer Discovery Protocol (LLDP)-enabled switch in your environment.

If this is the case, you may manually configure VLAN configuration for Lync Phone Edition on DHCP Server.

You can check the following link:

http://blog.schertz.name/2011/01/manual-vlan-configuration-for-lync-phone-edition/

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Best regards,

Eric

normally is use LLDP but I was  testing now phone is  signed in but I have following error "Registrar FQDN cannot be found" for about 30 sec, and  phone  signe in,

when Im  trying make  a  call  I have about 5-10 seconds time out before proper call but only in new Vlan, in old vlan works fine

Does the VLAN it is connecting to have the DHCP options and use the same DNS servers? 

Does the new VLAN have access to the edge server internal interface on the same ports as the existing VLANs (this may cause the delay).

Hi ,

Im writing to follow up on this thread. Do you have any updates on this issue? Please post back at your convenience.

Best regards,

Eric