Step By Step Cisco IM&P and Microsoft Lync Intradomain Federation Lab (3)

Step By Step Cisco IM&P and Microsoft Lync Intradomain Federation Lab (3)

This is the 3rd post in the Cisco IM&P and MS Lync Intradomain Federation series. We will focus on the MS Lync side of configuration in this blog.

Step By Step Cisco IM&P and Microsoft Lync Intradomain Federation Lab (4)
Step By Step Cisco IM&P and Microsoft Lync Intradomain Federation Lab (2)
Step By Step Cisco IM&P and Microsoft Lync Intradomain Federation Lab (1)

This is the 3rd post in the Cisco IM&P and MS Lync Intradomain Federation series. We will focus on the MS Lync side of configuration in this blog. Other posts in the series include:

  1. Lab overview is available from https://autrunk.com/step-by-step-cisco-imp-and-microsoft-lync-intradomain-federation-lab-1/
  2. Cisco IM&P configuration is available from https://autrunk.com/step-by-step-cisco-imp-and-microsoft-lync-intradomain-federation-lab-2/

2.0 Microsoft Lync Configuration

2.1 Configure Static Route to the Cisco IM&P Server

Lync comes with the following administrative tools:

  • Lync Server Control Panel provides a web GUI interface where administrators can manage Lync operational tasks such as user creation and removal;
  • Lync Server Management Shell is Lync specific PowerShell, providing a command line interface (CLI). It is the most powerful Lync management tool, and some tasks can only be performed via the Lync Server Management Shell. For example, we are going to create the SIP static route on Lync by using Lync Server Management Shell;
  • Lync Server Deployment Wizard is not only utilised when initially set up Lync, but also useful to update Lync Server System, such as update certificates and re-setup Lync node after a major topology change.
  • Lync Server Topology Builder provides a GUI interface to view, modify and publish Lync topology. We will use Lync Server Management Shell to update topology in this lab.

Run ‘Lync Server Management Shell’ as administrator and create a global static route targeting IMP01. Reference 1 provides syntax details on ‘New-CsStaticRoute’.

Verify the new static route has been successfully created by running ‘Get-CsStaticRoutingConfiguration | Select-Object -ExpandProperty Route’. Reference 2 provides Syntax details on ‘Get-CsStaticRoutingConfiguration’. Our lab result is as below:

If the static routing does not work as expected, check each parameter of the command and also whether there is a registrar-specific routing overruling the global static routing.

2.2 Create Cisco IM&P as SIP Federated Provider

We then create Cisco IM&P as an external SIP federated provider in the Lync Server Control Panel. Run the Lync Server Control Panel as administrator, or use the following URL to connect Lync Server Control Panel if the ‘Input URL’ window pops up.

Log into the Lync Server Control Panel with the appropriate AD Lync group permission.

Create the IM&P server as a public SIP Federated Provider as below:

  • Tick ‘Enable communications with this provider’;
  • Provider name: S01E01IMP01;
  • Access Edge service (FQDN): S01E01IMP01.altairx.lan; and
  • Select ‘Allow users to communicate with everyone using this provider’.

2.3 Create Cisco IM&P as Lync Trusted Application
We then need to create Cisco IM&P as a Lync trusted application by using Lync Server Management Shell.

Reference 3 provides syntax details on ‘New-CsTrustedApplicationPool’.

2.4 Publish the Updated Lync Topology

Running the following command to publish Lync topology in Lync Server Management Shell.

We can also verify the trusted pool and application details from the Lync Server Control Panel as below.

Certicates and troubleshooting tools will be covered in the next blog. Thanks for reading 🙂

Reference

    1. New-CsStaticRoute: https://docs.microsoft.com/en-us/powershell/module/skype/new-csstaticroute?view=skype-ps
    2. Get-CsStaticRoutingConfiguration: https://docs.microsoft.com/en-us/powershell/module/skype/get-csstaticroutingconfiguration?view=skype-ps
    3. New-CsTrustedApplicationPool: https://docs.microsoft.com/en-us/powershell/module/skype/new-cstrustedapplicationpool?view=skype-ps

 

COMMENTS

WORDPRESS: 0
DISQUS: 1