Integrating Exchange unified messaging with OCS 2007

Exchange Server 2007 and OCS 2007 may be part of the same unified communications strategy, but each has separate and defined roles. When integrated together, they can enhance an enterprise's unified messaging experience. This guide gives you all the steps needed to configure Exchange UM and OCS 2007.

This Content Component encountered an error
Exchange Server 2007 and Office Communications Server (OCS) 2007 are the core products of Microsoft's unified communications (UC) strategy. Although these products work best when integrated, they both, have very separate and well-defined roles. Exchange Server 2007 handles all asynchronous communications: email, voicemail and fax. OCS deals with synchronous communications: presence, instant messaging, voice and video.


Related links:
Plan for Exchange Server 2007 SP1 Unified Messaging in Office Communications Server

TechNet Webcast: Configuring Office Communications Server 2007 and Exchange Server 2007 Unified Messaging Interoperability (Level 300)

Office Communications Server 2007 Document: Enterprise Voice Planning and Deployment Guide

Quick Start Guide for Outlook Voice Access 2007

Microsoft has a "better together" story for several products. In this particular case, OCS can leverage the entire unified messaging (UM) experience, which includes:

  • Play-on-phone support.
  • External Subscriber Access and Auto-Attendant for calls routed through OCS.
  • Missed call and voicemail notifications for calls routed through OCS.
  • Message waiting indication for OCS clients, which gives a visual notification of available voicemail messages.
  • OCS uses the out-of-office (OOF) message text users set in Exchange Server 2007.

Here are the steps you will need to take to configure Exchange UM and OCS:

  1. On the OCS front-end server, create the location profile (the name matches the Exchange UM dialplan.FQDN.
  2. Enable users for Enterprise Voice.
  3. On the Exchange UM server, ceate a Session Initiation Protocol (SIP) dial plan based on your specific deployment requirements. An Enterprise Voice location profile should be created to match the dial plan FQDN.
  4. Run the exchucutil.ps1 script.
  5. Obtain a certificate for your Exchange UM server from a trusted root certificate authority(CA).
  6. Enable users for unified messaging and associate them with the appropriate SIP dial plan.
  7. On the OCS front-end server, run the Exchange UM Integration Utility (OcsUMUtil.exe) to create contact objects for subscriber access and auto-attendant.

Office Communicator (OC) will not display the Call Voice Mail shortcut (Figure 1) unless OCS 2007 and Exchange UM are configured to work together. By the end of this article, the link will appear.

Office Communicator without the Call Voice Mail link

Figure 1. Here's an example of Office Communicator without the "Call Voice Mail" link visible.

Solution topology

A production environment with OCS 2007 and Exchange Server 2007 would look something like that in Figure 2.

Architecture of OCS 2007 and Exchange 2007

Figure 2. A detailed production environment architecture of OCS 2007 and Exchange 2007.

For demonstration purposes, you don't need such a complex environment. Figure 3 shows the environment installed on my test lab using the servers outlined in Table 1.

Solution

Figure 3. Solution topology of OCS 2007 and Exchange 2007 in a lab.

Name Role Software
E2K7
Domain Controller (GC)
Client Access
Hub Transport
Mailbox
Unified Messaging
Windows Server 2003 R2 SP2 x86
Exchange Server 2007 SP1 RU5
OCS 2007
OCS front end Windows Server 2003 R2 SP2 x86
Exchange Server 2007 SP1 RU5
VISTA-x86
Client Windows Vista Enterprise SP1
Office Communicator 2007 (2.0.6362.97)
Office Outlook 2007

Table 1. Servers used in an OCS 2007 and Exchange 2007 lab environment.

The first step is to create an OCS Location Profile. The name of the location profile must match the name of the Exchange UM dial plan in FQDN format. Open the Office Communications Server 2007 management console and right-click on Forest. Then point to Properties and then Voice Properties (Figure 4).

TheOCS Forest Voice Properties are in the OCS management console

Figure 4. The OCS Forest Voice Properties can be found in the OCS management console.

Click Add on the Add Location Profile window and type the FQDN of the corresponding Exchange UM dial plan. Next, click Add to create a normalization rule (Figure 5).

Location Profile

Figure 5. This is how to create the Location Profile.

In the Phone Number Normalization Rule dialog box, type a name that describes the number pattern to be normalized, for example "4Digit."

In the phone pattern regular expression box, use .NET Framework regular expressions to describe a phone number pattern. For example, you can use ^(\d{4})$ to describe a phone number pattern containing four digits. For additional information, see Microsoft's Office Communications Server 2007 Document: Enterprise Voice Planning and Deployment guide.

In the Translation pattern regular expression box, use .NET Framework regular expressions to describe the E.164 phone number that corresponds to the number entered in the Phone pattern regular expression box.

In the Sample dialed number box, type a phone number to test whether the number translation works properly. If the number matches the phone pattern, the translation will appear in the Translated number box (Figure 6). Click OK to accept.

Translation will appear in your Normalization Rule

Figure 6. Translation will appear in the Translate number box of your Normalization Rule.

The next step is to assign a default location profile to the OCS Pool.

Create as many normalization rules as your location profile requires. When you are done, click OK.

If you are configuring a Standard Edition server, expand Standard Edition Servers, right-click the Standard Edition pool that you want to configure, point to Properties and then click Front End Properties.

On the Voice tab, select the default location profile for the pool (Figure 7). If you are configuring an Enterprise Edition Pool, expand Enterprise pools, expand the pool that you want to configure, right-click Front Ends, and click Properties.

Default Location Profile of the OCS Pool

Figure 7. This is the default Location Profile of the OCS Pool.

Enable users for Enterprise Voice

Users should be enabled for OCS Enterprise Voice before you enable them for UM. This way, they will have a valid proxy address.

Expand the pool or server where your users reside and click the Users node.

In the right pane, right-click on one or more users to configure, then click Configure users. You can configure individually or as a group. Make sure the Enable Enterprise Voice is selected and that a valid line uniform resource identifier (URI) is configured (Figure 8).

Enable Enterprise Voice

Figure 8. You can now enable Enterprise Voice.

By this step, event 44028 may be logged on the Office Communications Server Event Log (Figure 9). This occurs because we haven't configured the Exchange integration yet.

Example of a warning event

Figure 9. This is an example of a warning event.


Integrating Exchange unified messaging with OCS 2007
  Part 1: Integrating Exchange unified messaging with OCS 2007
  Part 2: Configuring Exchange unified messaging with OCS 2007
  Part 3: Tools automate an Exchange UM and OCS 2007 integration

ABOUT THE AUTHOR:   
Rui Silva, Microsoft Exchange MVP
Rui Silva is a Technology Solution Professional (Unified Communications) at Microsoft Portugal. Silva is MCITP/MCDBA/MCSA/MCSE:Messaging+Security certified and has been recognized as a Microsoft MVP for Exchange Server from 2005 to 2008, due to his contribution to the technical community. Silva spent the last 11 years working with all kinds of Microsoft technologies, with particular emphasis on Microsoft Exchange Server and Office Communications Server.
This was first published in February 2010

Dig deeper on Instant Messaging and Unified Messaging

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchWindowsServer

SearchEnterpriseDesktop

SearchCloudComputing

SearchSQLServer

Close