Integration with Exchange Server Unified Messaging

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2016-12-01

If you want to integrate Exchange Unified Messaging with Office Communications Server, you must perform the following tasks:

  • Deploy the following Exchange Server 2007 with SP1 server roles in either the same or a different forest as Office Communications Server 2007 R2: Unified Messaging, Hub Transport, Client Access, and Mailbox. For details about the supported topologies, see Enterprise Voice Server-Side Components. For details about deploying Exchange Server 2007, see the Exchange Server 2007 product documentation at https://go.microsoft.com/fwlink/?LinkID=139372.

  • On the Exchange Unified Messaging server:

    • Create a SIP dial plan based on your specific deployment requirements (for details, see your Exchange documentation). A location profile should be created on Office Communications Server that matches the FQDN of the SIP dial plan.

    • Associate users with the appropriate SIP dial plan.

  • Also on the Exchange Unified Messaging server, open the Exchange Management Shell and run the exchucutil.ps1 script, which:

    • Creates a Unified Messaging IP gateway object in Active Directory Domain Services (AD DS) for each Office Communications Server Enterprise pool or Standard Edition server that hosts users who are enabled for Enterprise Voice.

    • Creates an Exchange UM hunt group for each gateway. The hunt group pilot identifier will be the name of the dial plan that is associated with the corresponding gateway.

    • Grants Office Communications Server permission to read Exchange UM Active Directory objects, specifically, the SIP dial plans created in the previous task.

  • On the Office Communications Server, run Exchange UM Integration Utility, which:

    • Creates contact objects for subscriber access and auto attendant.

    • Validates that there is a location profile name whose name matches the Exchange UM dialplan.FQDN.

Note

For details about the supported domain topologies for Office Communications Server and integrated Exchange Unified Messaging, see Environmental Requirements in the Supported Topologies and Infrastructure Requirements documentation.

Additionally, you must complete the following tasks:

  • Work with Exchange administrators, if necessary, to verify the tasks that each of you will perform to assure a smooth, successful integration.

  • Deploy the Exchange Mailbox, HubTransport, ClientAccess, and UnifiedMessaging roles in each forest where Exchange Unified Messaging is deployed. For details about installing Exchange server roles, see your Exchange 2007 documentation.

  • Obtain a certificate for each Exchange Unified Messaging server from a trusted root CA. The certificates are required for mutual TLS (MTLS) between the servers running Exchange Unified Messaging and Office Communications Server. For details about configuring certificates on servers running Exchange Unified Messaging, see Configuring Certificates on the Server Running Microsoft Exchange Server 2007 Unified Messaging in Deploying Enterprise Voice in the Deployment documentation.

    Important

    When Exchange 2007 SP1 Unified Messsaging is installed, it is configured to use a self-signed certificate (to view the certificate, type Get-ExchangeCertificate | fl run from the Exchange Management Console on the Exchange 2007 SP1 Unified Messaging server).
    Do not delete the self-signed certificate. Without it, Exchange 2007 Unified Messaging cannot communicate with other Exchange 2007 server roles including the Hub Transport Server, which sends voice mail notifications.
    The self-signed certificate, however, does not enable Office Communications Server and Exchange 2007 Unified Messaging to trust each other, which is why it is necessary to request a separate certificate from a CA that both trust.

  • If Office Communications Server and Exchange Unified Messaging are installed in different forests, configure each Exchange forest to trust the Office Communications Server forest.

  • If necessary, install the Exchange Management Console on each Unified Messaging server.

  • Deploy a Microsoft Office Communications Server 2007 R2 Standard Edition server (minimum requirement) or Enterprise pool. For details about installation information, see Office Communications Server 2007 R2 Enterprise Voice Deployment Guide in the Deployment documentation.

  • Obtain valid phone numbers for Outlook Voice Access and auto attendant.

  • Coordinate names for Exchange UM dial plans and Enterprise Voice location profiles.

  • For each Exchange UM dial plan, select the SIP gateway.