Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Tools automate an Exchange UM and OCS 2007 integration

Successfully combining Exchange Server 2007 unified messaging with OCS 2007 can be a daunting task without the Exchange UM Integration Utility.

The integration of Exchange UM and OCS 2007 poses some challenges and requires detailed configuration of different utilities and contacts. Performing these tasks manually can be difficult, but certain tools, such as the Exchange UM Integration Utility (OcsUMUtil.exe), can automate the process.

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

RUN OcsUMUtil.exe

The final step to integrating Exchange UM and OCS 2007 is to run the Exchange UM Integration Utility (OcsUMUtil.exe). The default path on the OCS front-end server should be C:\Program Files\Microsoft Office Communications Server 2007\Server\Support (Figure 28).


Figure 28. Running OcsUMUtil is the final step to integrate Exchange UM and OCS 2007.

The Exchange UM Integration Utility performs the following tasks:

  • Creates contact objects for each auto attendant and subscriber access number that Enterprise voice users will need
  • Verifies that the name of each Enterprise Voice location profile matches its corresponding UM dial plan phone context

Double-click on OcsUMUtil.exe and then onto Load Data to get started. Select a UM SIP dial plan on the left-hand side and click Add (Figure 29).

In the Organizational Unit (OU) check box, select an OU and click OK. In the Name box, accept the default dial plan name or type a new user-friendly name for the contact object that you are creating. In the SIP Address box, accept the default SIP address or type a new SIP address. In the Server or Pool drop-down box, select the OCS Pool where the contact object will be enabled.

In the Phone Number box displayed in Figure 29, leave the default option of Use this pilot number from Exchange UM selected. This number should have been configured when the dial plan and the auto attendant were created.

Open this box to load data in the Exchange UM Integration Utility

Figure 29. Open this box to load data in the Exchange UM Integration Utility.

In the Contact Type list, select the contact type that you want to create -- Subscriber Access or Auto Attendant -- and click OK.

Figure 30. Use this tab to create a Subscriber Access contact.

You should create at least one contact for each auto attendant. The utility will display a warning (Figure 31) if there an auto attendant object does not have a corresponding contact.

Auto Attendant warning message

Figure 31. This shows an Auto Attendant warning message.

Create at least one contact for each auto attendant. Figure 32 depicts the two contacts that were created -- Auto Attendant and Subscriber Access.

Auto Attendant and Subscriber Access contacts

Figure 32. The Auto Attendant and Subscriber Access contacts were created.

To verify that the contact objects have been created, open Active Directory Users and Computers and select the OU where the objects were created. Contact objects should appear in the details pane (Figure 33).


Figure 33. A list of the contacts you created in AD appear in the details pane.

Verifying the results

If everything was configured correctly, the Office Communicator client will now display the Call Voice Mail option (Figure 34).

Choices available to you in the Call Voice Mail option in OC

Figure 34. These are the choices that are available to you in the "Call Voice Mail" option in Office Communicator.

The Call Voice Mail option can be used to call Exchange UM with a simple click, as shown in Figure 35.

Figure 35. This is the best way to connect to "Call Voice Mail."

Other features include missed call notifications, which are displayed in Figure 36.

Figure 36. This is what a missed call notification looks like.

Figure 37 shows where to find integrated voice-mail.

Voicemail notification appears

Figure 37. A voicemail notification will appear in this format.

Figure 38 depicts the message waiting indicator, which is the Communicator icon on the notification area of the taskbar flashes.

Message Waiting Indicator icon

Figure 38. Here's where you would see the Message Waiting Indicator icon.

Figure 39 displays the play on phone option, which will use the Communicator SIP URI.

Available voice mail options

Figure 39. These are the available voice mail options.

Allowing Directory Search calls to outside telephone numbers

A cool feature of Exchange UM is Directory Search, which lets you browse the Global Address List to find a contact. If the only UM dial plan that's set up is for OCS, you'll have to configure Dialing Rule Groups to be able to make calls to telephone numbers outside of your company.

An easy way to do this is to edit the dial plan properties. Select the Dialing Group Rules tab, then add two rule groups: countrywide and worldwide. Include "*" as Number Mask and Dialed Number (Figure 40).

Rule groups

Figure 40. Here are where you can find your two rule groups when adding to the dialing restrictions.

These two rule groups must also be added to the Dialing Restrictions of the UM mailbox default policy (Figure 41).

Figure 41. These are the dialing restrictions that are in place.

Reverse number lookup (RNL)

Both OCS and Exchange Server will try to connect a telephone number to a name every time a call is received or when the system sends a missed call notification.

Both Exchange Server and OCS will search Active Directory and personal Outlook contacts using reverse number lookup (RNL). Although they search the same places, the methods they use are somehow different.

OCS (Communicator) normalizes dialed numbers according to defined rules and performs RNL against the generated address book, which, in turn gets its Primary Phone Numbers from the msRTCSIP-line AD attribute and Outlook contacts. It's also important you ensure that personal contacts are normalized.

Exchange 2007 SP1 will perform RNL against other UM-enabled mailboxes in the same UM dial plan, against personal Outlook contacts and finally against the msRTCSIP-line AD attribute (Figure 42). The normalization logic (InternationalNumberFormat) is only applied if the calling number has the same number of digits of the user's dial plan. Otherwise, Exchange will only prepend a "tel:+" to the number.

Example of a msRTCSIP-Line attribute

Figure 42. Here's an example of a msRTCSIP-Line attribute.

What are some OCS limitations?

OCS behaves like a regular IP PBX, so the UM experience is very similar to the same type of PBX or a SIP gateway. The only limitation is fax capabilities. Users who are associated with a SIP URI dial plan cannot receive incoming faxes because incoming voice and fax calls are routed through a Mediation Server computer and the T.38 protocol is not supported.

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

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.

Dig Deeper on Microsoft messaging and collaboration services

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.