Intelligent Message Filter, Content Filter, can do more...

WinDeveloper IMF Tune
WinDeveloper IMF Tune
  • Home
  • General
  • Integrating Lync 2010 with Exchange 2010 - Part 3

Integrating Lync 2010 with Exchange 2010 - Part 3

Paul Roman [MVP for Exchange, MCSE, MCSA, MCST, MCITP]

Paul Roman [MVP for Exchange, MCSE, MCSA, MCST, MCITP] Photo

Paul is a Microsoft Certified System Engineer since 1999. His experience covers a large number of Microsoft Exchange implementations starting from small infrastructures and going to large hosting infrastructures for thousands of users. Starting with April 1st, 2010, Paul is MVP for Exchange.

Cast your Vote
Poor Excellent

Exchange 2010 Unified Messaging brings voice and e-mail messaging into one place. Integrating Lync with Exchange we get a voice solution that replaces and is dramatically better than standard PBX solutions.

In Integrating Lync 2010 with Exchange 2010 – Part 1 we started our discussion focusing on integrating the Outlook Client interface. In Integrating Lync 2010 with Exchange 2010 – Part 2 we turned our attention to the Outlook Web App and saw how to provide users with Lync functionality through it. Today we conclude this series by integrating the Exchange 2010 Unified Messaging Server with Lync.

Exchange 2010 and Lync 2010 Voice Integration

Exchange Server 2010 Unified Messaging helps you get voice messaging and e-mail messaging into one place, accessible from a normal phone or a computer. Integrating Lync Server 2010 with Exchange we get a voice solution that replaces and is dramatically better than standard PBX solutions. Here are the steps needed to achieve this integration.

  1. Install Exchange UM Role - I will not cover this aspect here. This is well documented at the Microsoft site, check:
    Install the Exchange 2010 Unified Messaging Server Role

  2. Configure certificates - Make sure that you have digital certificates installed and configured on each UM server. The certificates have to be issued by a root CA trusted by the Exchange and Lync servers.

    • To find out if a certificate is in use for UM, from the Exchange Management Shell run:
      Get-ExchangeCertificate

      UM Certifcate

      The one that has U as service is the one that you need.

    • If no certificate is selected for the UM role, at the Exchange Management Shell on the server(s) that have the UM role installed, run:
      Enable-ExchangeCertificate -thumbprint <CertificateThumbprint> -Services UM

      <CertificateThumbprint> is the thumbprint of the certificate that will be used for this service.

  3. Create and configure an Exchange UM SIP dial plan.

    You need to create a SIP dial plan on the Exchange UM server and then associate the Unified Messaging servers to it.

    • On the Exchange UM server, using the Exchange Management Shell run:
      New-UMDialPlan -Name UMDialPlan
      -NumberOfDigitsInExtension 5
      -URIType SipName
      -VoIPSecurity Secured
      -CountryOrRegionCode 44

      This will create a new Dial Plan with the following settings:
      UMDialPlan - the name of the new dial plan
      5 - the number of digits available in the extension number
      SipName - means that this dial plan will support SIP URIs
      Secured - means that the traffic will be encrypted using mutual Transport Layer Security (TLS).
      44 - is the region code for UK.

    • Next using the Exchange Management Shell run:
      Set-UMServer -Identity UMExch -DialPlans UMDialPlan -UMStartupMode TLS

      This will configure the server UMExch to use the UMDialPlan just created and to start the UM service in TLS mode.

    • Restart the Exchange UM service

  4. On the Exchange UM server create and configure a new AutoAttendant.

    The UM auto attendant enables the Unified Messaging server to answer incoming calls.

    Using the Exchange Management Shell run:
    New-UMAutoAttendant -Name UMAutoAttendant
    -UMDialPlan UMDialPlan
    -SpeechEnabled $true
    -PilotIdentifierList +4400000
    -Status Enabled

    This will create a new auto attendant named UMAutoAttendant that will be speech enabled and answers to the +4400000 number

  5. On the Exchange UM server run the exchucutil.ps1 script

    From the scripts folder on the Exchange UM server (usually C:\Program Files\Microsoft\Exchange Server\v14\Scripts) using the Exchange Management Shell, run the exchucutil.ps1 script.

    This will perform the following tasks:

    • Grant permission to Lync Server to read Exchange UM AD objects like the SIP dial plans created in the previous task

    • Creates a UM IP gateway object for each Lync Server Enterprise Edition pool or Standard Edition server

    • Creates an Exchange UM hunt group for each gateway

    Before running this script you need to make sure that all the AD replication has completed and that the Dial plan you created in 3 (Create and configure an Exchange UM SIP dial plan) was replicated.

  6. Configure Lync Server dial plans

    For Exchange Server 2010 RTM the Enterprise Voice dial plan has to have a name that matches the Exchange UM dial plan FQDN.

    For Exchange Server 2010 SP1 or later, the Lync Server dial plan and Exchange UM SIP dial plan names do not need to match.

    On the Lync Server run the Exchange UM Integration tool, ocsumutil.exe (C:\Program Files\Common Files\Microsoft Lync Server 2010\Support\OcsUmUtil.exe).

    Exchange UM Integration Utility

    This tool will create Subscriber Access and Auto Attendant contact objects. It will also validate that there is an Enterprise Voice dial plan with a name that matches the Exchange UMdialplan FQDN. If you are running Exchange Server 2010 SP1, the dial plan names do not need to match, and you can ignore the tool's warning about this.

    • Click Load Data to get the information from Active Directory. This will bring you a screen like this:

      SIP Dial Plans

    • Click Add to add a Subscriber Access contact

      Exchange UM Subscriber

    • Click Add to add an Auto-Attendant contact

      Exchange UM AutoAttendant

    • Finally you should get a screen like this. You can safely ignore the warning if you are using Exchange 2010 SP1 or later

      Completed Dial Plan

  7. Enable Enterprise Voice users for Exchange UM

    The last step that you need to do is to enable Voice users to be able to use the Exchange UM. To do that, run the following Exchange Management Shell cmdlet:
    Enable-UMMailbox -Identity testuser@testdomain.com -UMMailboxPolicy UMPolicy -Extensions 12345 -SIPResourceIdentifier testuser@testdomain.com -Pin 23753465 -PinExpired $true

    This will enable testuser@testdomain.com for ExchangeUM.

    To find out more about this command check the TechNet documentation for Enable-UMMailbox.

Conclusion

This completes our journey in the integration of Exchange 2010 and Lync 2010. Once you are a little bit familiar with both products, getting this to work is fairly easy.

Integration pays dividends in terms of productivity as users are able to employ both products through the same interfaces they work with every day. So it is definitely worth the effort. Integration should indeed be at the top of your priority list once these two products are deployed.

References

Integrating Lync 2010 with Exchange 2010 – Part 1

Integrating Lync 2010 with Exchange 2010 – Part 2

Lync 2010 Integration

Configure Outlook Web App and Lync Server 2010 Integration

Setting Lync 2010 policies (OCS Group Policy) with PowerShell

Lync and Exchange UM Integration

Deployment Process for Integrating On-Premises Unified Messaging and Lync Server 2010

Copyright © 2005 - 2014 All rights reserved. ExchangeInbox.com is not affiliated with Microsoft Corporation