IT Consultant Everyday Notes

Just some problems/solutions storage

Category Archives: Lync

Lync: Device Update


Microsoft issued updates for Lync Phone Edition (both 2010 and 2013).  While installing them I found a nice script wrote by Pat Richard to facilitate firmware installation for multiple device types.

Lync 2012: Federation failed with error “SIP/2.0 504 Server time-out”

I recently helped one of our Consultants to troubleshoot a Lync Federation issue.


Issue: When a Client tries to add a user from a Federated domain it gets “

When contacting your support team, reference error ID 504 (source ID 239).

Troubleshooting information is available online, including best practices for using Lync.” message.


Resolution: Edge Server log shows:

TL_ERROR(TF_CONNECTION) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab3fee (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
LogType: connection
Severity: error
Text: Receive operation on the connection failed
Local-IP: 69.10.XXX.XXX:54814
Peer-IP: 209.205.XXX.XXX:5061
Peer-FQDN: My-Edge-FQDN
Peer-Name: Partner-Edge_FQDN
Connection-ID: 0x13703
Transport: M-TLS
Result-Code: 0x80072746 WSAECONNRESET
Data: fqdn=”Partner-Edge_FQDN“;peer-type=”FederatedPartner”;winsock-code=”10054″


TL_ERROR(TF_DIAG) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab4024 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(143))$$begin_record
LogType: diagnostic
Severity: error
Text: Message was not sent because the connection was closed
SIP-Start-Line: SUBSCRIBE sip:username@Partner-DOMAIN SIP/2.0
SIP-Call-ID: 495169bf05e041e39222905f46236f31
Peer: Partner-Edge_FQDN:5061

TL_INFO(TF_PROTOCOL) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab4333 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 1484110210
Instance-Id: 0000567F
Direction: outgoing;source=”local”;destination=”internal edge”
<Private information here >

Call-ID: 495169bf05e041e39222905f46236f31
Via: SIP/2.0/TLS 10.10.XXX.XXX:59199;branch=z9hG4bK9558ABE4.49ED0FF1C7027493;branched=FALSE;ms-received-port=59199;ms-received-cid=600
Via: SIP/2.0/TLS 192.168.XXX.XXX:54768;branch=z9hG4bK54197F18.D4F20C41F31B0497;branched=FALSE;ms-received-port=54768;ms-received-cid=33DD500
Via: SIP/2.0/TLS 192.168.XXX.XXX:65137;received=99.228.XXX.XXX;ms-received-port=65137;ms-received-cid=12800
ms-diagnostics: 1047;reason=”Failed to complete TLS negotiation with a federated peer server”;WinsockFailureCode=”10054(WSAECONNRESET)”;WinsockFailureDescription=”The peer forced closure of the connection”;Peer=”Partner-Edge_FQDN“;Port=”5061″;source=”My-Edge-FQDN
Server: RTC/4.0
Content-Length: 0
ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=My-Edge-Internal-FQDN;ms-source-verified-user=verified
Message-Body: –

Even though we are using Entrust certificate on our Edge the Partner’s Edge does not trust it!

I sent our Entrust certificate chain to Partner to install on Edge and it fixed the issue.

Audiocodes: MediaPack 1xx–connected phones cannot call each other

I am configuring Lync 2013 to communicate with AudioCodes MediaPack 118 Enhanced Voice Gateway (the device is not certified for Lync 2013).

Listening port on Lync: TCP 5068

Listening port on Audiocodes: TCP 5060

Audiocodes FXS line 1: 2001

                           line 2: 2002

Lync – Phones traffic flows without problem.

Issue: When I tried to call between phones connected to MP-118 I got a busy signal. Phone call does not pass.

Resolution: In Protocol Configuration – Protocol Definition – SIP General Parameters I had SIP destination port set to 5068 (port on my Lync 2013). It looks like Audiocodes used this port by default for all SIP connection (including connection from connected phone to Audiocodes SIP server itself).

So I added port 5060 to my routing rule describing route for phone-phone calls (switch to  Advanced Parameter list):


Lync 2010: LS Response Group Service logs Event ID 31196 every 2 minutes

Issue: my Lync 2010 Front-End server logs

Log Name:      Lync Server
Source:        LS Response Group Service
Date:          1/29/2013 12:44:08 PM
Event ID:      31196
Task Category: (2001)
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      <front-end server>
Collaboration platform has failed to provision the data.

Collaboration platform has failed to provision the data because of the following exception:
Exception: Microsoft.Rtc.Collaboration.ProvisioningFailureException:Cannot read contacts from Active Directory: Active Directory server "DC Server Name" is not available. Try again later. …

Resolution: Restart Lync Service Response Group service.

found here

Lync 2013: Control Panel HTTP Error 401.1

I am working with Lync/OCS –> Lync 2013 upgrade project. I installed Lync 2013 on my Windows Server 2012.

Issue: When I try to access Lync 2013 Server Control Panel from the Front-End Server I get “Http Error 401.1” after three unsuccessful logon attempts. I can connect to the Control PAnel from other machines though (with the same credentials set)

Resolution: Fortunately I found this thread and followed Lync MCM Jeroen Reijling advice:

Logon on to the Front-End Server with an account that is member of the local admins group

  1. Start “regedit”
  2. Go to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa”
  3. Right-click the Lsa registry subkey, point to New, and then click DWORD Value
  4. Type DisableLoopbackCheck, and then press ENTER
  5. Right-click DisableLoopbackCheck, and then click Modify
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor, and then restart the server.

Now Control Panel is accessible:


Lync: CU7 (December 2012) for Phone Edition

Microsoft published a CU7 for Lync Phone Edition:


One of new features is Music on Hold. That post helps to set it up.

Lync 2013: Prepare Current Forest task failed


I am installing Lync 2013 in AD where I already have Lync 2010 installed. Lync 2010 security groups are in a dedicated OU.


Forest Preparation failed with the following error:

Error: Existing universal groups were found in "OU=Lync,OU=Demo Security Groups,DC=XXX,DC=XXX,DC=XXX,DC=com". Specify where to create new Lync Server universal groups explicitly at the command line with the GroupDomain parameter.


Move Lync security groups to a default “Users” container in AD.

the resolution is found here:

Lync 2010: User activity report failed with “An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset ‘CallList’. (rsErrorExecutingCommand)”

Issue: User Activity report failed with “

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for dataset ‘CallList’. (rsErrorExecutingCommand)

For more information about this error navigate to the report server on the local server machine, or enable remote errors.”



1. It happens after CU installation. For me – after CU7, some people report it happens after CU6 too.

2. Read instructions in CU KB – you must update database! using something like :Install-CsDatabase -Update -ConfiguredDatabases –SqlServerFqdn <SQL Server without instance> –UseDefaultSqlPaths

In my case SQl FQDN did not work – I put NETBIOS name. I guess the main idea is to put how it is displayed in your Topology Builder.

3. Start Lync 2010 Deployment Wizard and redeploy Monitoring Reports. I did it from Front-End Server.

4. Above mentioned KB does not instruct you to update Monitoring Database – this is from other KB Winking smile

my command looks like: Install-CsDatabase -DatabaseType Monitoring -Update –SqlServerFqdn <Monitoring Server Name>

in my case, again, server name was just a NETBIOS name and I ran it from a Front-End server.

Lync: Phone Edition LG-8540 –Firmware Update

I recently found an old LG-Nortel 8540 and decided to put it to my Lync 2010 environment (all other phones are almost all Aastra).

The device had an old OCS 2007 RTM firmware: 1.0.522.101 (1.23). Apparently I am lucky – people with older firmware must to install OCS 2007 RTM in order to update the device firmware to this version ( Smile

Issue: My device successfully connected to Lync (with old firmware) but did not want to upgrade it to a recent one – 4.0.7577.410


1. I installed OCS 2007 R2 Std in my Lab. One server.

2. Updated it with the latest CU. UPDATE DATABASE FIRST! (

3. Download the latest firmware for LG 8540 for OCS 2007 R2 (3.5.6907.222 (1.23)) (

4. Install the update and approved it as described here:

5. Start the device and logged in as “\username” not just domain\username here is why:

7. Nothing happened – no updates!  Sad smile

8. tried to get update using IE /DeviceUpdateFiles_Int/UCPhone/LG-Nortel/IP8540/A/ENU/3.5.6907.0/CPE/CPE.nbt">http://<OCS FQDN>/DeviceUpdateFiles_Int/UCPhone/LG-Nortel/IP8540/A/ENU/
– got a blank page instead of the file.

8.1. Static Content feature was missed from IIS installation – installed it. Still nothing

8.2 Removed <mimeMap fileExtension=".cat" mimeType="binary/octet-stream" />  from c:\windows\system32\inetsrv\configuration\applicationHost.config and rebooted the server (just iisreset did not help)– I can download file successfully now. The solution was found here:

9. So do the device – successfully got the update.

10. I can monitor it in log files (I am using CMTRACE.exe from SCCM to see logs “live”)




11.As soon as the device was updated to 3.5.6907.222 I plugged the phone to my production network hoping it will accept 4.0.7555.4066 I have downloaded and approved for Lync as described in a nice Jeff’s article. Unfortunately it did not happened Sad smile

12. Some research leaded me to that thread and I realized I am not alone. It looks like due to cert issue LG 8540 cannot get the latest and greatest firmware (CU6, June 2012) and need to be upgraded to a previous (CU5, March 2012). The problem is the patch is not available anymore! All links point to CU6 even from CU5 KB. Luckily  Lync15 posted a link to his SkyDrive where he uploaded the old CU5. Whole thread is here direct link is here. Problem in details is described by Jeff here. Thank you guys!

13. I removed the latest firmware for LG 8540 from my Lync and published CU5 instead:


14. Restarted the phone and it successfully got 4.0.7577.4066 from Lync.

15. Now we can add CU6 Lync Device Updater and LG 8540 accepts it.


Reference: Jeff on Lync Phone Troubleshooting:

Lync: CU7 (October 2012) is available