Lync – Skype federation seems to be working

After upgrading to the latest Windows 7 Skype version (6.3.0.105) and having Lync Server 2013 with CU1 at the company, I managed to send IM and call my Skype endpoint using my Lync 2013 client.

The trick was to sign in Skype using my old Windows Live account. That account I’ve previously added to my existing Skype account.

These functions seem to work:

  • Peer to peer IM.
  • Peer to pee audio.

Doesn’t work (yet?):

  • Contact information in Skype about the Lync user and vice versa. Except the Messenger mood message (not the Skype!) is visible in Lync. Actually I don’t know how to change that mood message.
  • Peer to peer video, and sharing sessions in any direction,
  • Adding Skype user to Lync meeting.
  • Transferring Skype caller to other Lync user, or phone number or parking the call.
  • Using Skype on Android will show unknown caller and produce strange call history records.

Some screenshot

Skype conversation window while having a Skype - Lync call.

Skype conversation window while having a Skype – Lync call.

Skype - Lync call on Android phone

Skype – Lync call on Android phone

Skype - Lync call on Android phone

Skype – Lync call on Android phone

 

 

 

 

Share

Lync 2013 Centralized Logging Service (CLS) Scenarios

Since Centralized Logging is completely new concept in  Lync 2013, the available material on MSFT websites and all around the Internet is not very extensive.

This is how it works

  • The ClsAgent runs on each Lync 2013 servers and waits for command to start, stop and search the traces according to a scenario. Also it delivers the results to the CLS controller. See this article.
  • Scenarios define which Lync components (providers) at which Level and Flags will capture traces.
  • There are default scenarios and custom scenarios. See this article for more details about the default scenarios.
  • Custom scenarios can be created with the command New-CsClsScenario.
  • To create a scenario, provider configurations have to be created and added to the scenario: New-CsClsProvider
  • To create a provider configuration you need to know what components are available for tracing. To get the list of them you need to see the file “c:\Program Files\Common Files\Microsoft Lync Server 2013\Tracing\default.xml
    Here is a little PowerShell script to list those providers:

    [xml]$providers = Get-Content "$env:ProgramFiles\Common Files\Microsoft Lync Server 2013\Tracing\default.xml"
    $providers.ComponentInfo.Components.Component
  • Save the script as get-LyncLogProviders.ps1 and run it to list the component names:
    .\get-LyncLogProviders.ps1 | Select-Object name
  • If you want to see the available trace levels and flags for a certain provider/component (here Autodiscover) :
    .\get-LyncLogProviders.ps1 | Where-Object {$_.Name -eq "Autodiscover"} | Select-Object -ExpandProperty Levels | Select-Object -ExpandProperty Level
    .\get-LyncLogProviders.ps1 | Where-Object {$_.Name -eq "Autodiscover"} | Select-Object -ExpandProperty Flags | Select-Object -ExpandProperty Flag
  • Now you know the provider name and what levels you can or should set up for the new CLS trace provider. Now you can create a new trace provider configuration and a new scenario.:
    $provider = New-CsClsProvider -Name "AutoDiscover" -Type "WPP" -Level "Verbose" -Flags "TF_COMPONENT"
    New-CsClsScenario -Identity "global/AutoDiscover_by_Attila" -Provider $provider
  • It’s time to start tracing with the new scenario. You can sync the traces to write the captured trace to the files on the servers, you can also stop the trace if you don’t need it anymore. You can start tracing on a specific server or pool, see the Technet article.
    Start-CsClsLogging -Scenario "AutoDiscover_by_Attila"
    Sync-CsClsLogging
    Stop-CsClsLogging -Scenario "AutoDiscover_by_Attila"
  •  Now you probably have what you wanted to capture, but you need to collect those from the Lync servers and save it to a file. If you only want to see the trace of a component, you have to specify it in your search query. E.g.
    Search-CsClsLogging -Components "AutoDiscover" -OutputFilePath "C:\temp\logfile.log"

I’m not sure if the mentioned .xml file is the proper source of available providers/components. If you have better idea, please share it with me.

Share

Lync Mediation Server CANCEL problem

You may encounter with the Mediation Server SIP CANCEL problem when your SIP trunk operator doesn’t send the “Session Progress” or “Ringing”  status messages quick enough. According to my measures it tends to be 6 seconds available for the operator to send back something useful. If they are too slow, Mediation Server will just CANCEL the call.

To solve this problem you have to fine-tune the OutboundRouting.exe application:

Continue reading

Share

Exam 74-322: Microsoft Lync Server 2010—Advanced Design and Deployment Beta Exam is available

The beta of the new Lync exam 74-322 is available to be taken at no cost for the selected Microsoft partners. The exam will be required for Lync gold competency level by October 2012. To read more about the exam requirements and topics covered, check out the blog post: http://beluxpartnerblog.wordpress.com/2012/02/07/dive-into-the-fundamentals-of-a-lync-system/

Continue reading

Share