|If you are not using Microsoft Exchange Server 2007 Unified Messaging (UM) to provide call answering, Outlook Voice Access, or auto-attendant services for Enterprise Voice (as might be the case, for example, if you deploy Office Communications Server in a PBX coexistence scenario), skip this step and proceed to Step 2. Create Location Profiles.|
The following tools must be available on each server running Exchange Unified Messaging:
- The Exchange Management Shell (also known as PowerShell).
- The script exchucutil.ps1, which performs the following tasks:
- Creates a UM IP gateway for each Office Communications Server
2007 R2 Enterprise Pool.
- Creates a hunt group for each gateway. The pilot identifier of
each hunt group specifies the UM dial plan used by the Enterprise
Pool that is associated with the gateway.
- Grants Office Communications Server permission to read Exchange
UM objects in Active Directory.
- Creates a UM IP gateway for each Office Communications Server 2007 R2 Enterprise Pool.
The script exchucutil.ps1 is by default installed in <exchange_install_directory>\Scripts\.
Requirements and Recommendations
Before you begin:
- Make sure that you have deployed the following Exchange server
roles: Hub Transport, Client Access, Mailbox, and Unified
Messaging. For details about deploying Exchange Server 2007 SP1,
see the Microsoft Exchange Server 2007 product documentation at
Note: You can deploy the Exchange Server roles either in the same or a different forest as Office Communications Server 2007 R2.
- Read Plan for Exchange Server 2007 SP1 Unified Messaging in
Office Communications Server at
http://go.microsoft.com/fwlink/?LinkId=126708. Integrating Exchange Server Unified Messaging and Communications Server requires careful planning and a clear understanding of the technologies involved, the features you want to enable, and important configuration details that you must be aware of to successfully complete your deployment.
Also note the following:
- If Exchange Server Unified Messaging is installed in multiple
forests, the Exchange integration steps must be performed for each
UM forest. In addition, each UM forest must be configured to trust
the forest in which Communications Server is deployed, and the
forest in which Communications Server is deployed must be
configured to trust the each UM forest.
- The integration steps are performed on both the server running
Exchange Server Unified Messaging and the server running
Communications Server. You should perform the Exchange Server
Unified Messaging integration steps before you do the
Communications Server integration steps.
- For an overview of the Exchange 2007 SP1 Unified Messaging
integration process, descriptions of supported topologies, and a
list of planning tasks, see Plan for Exchange Server 2007 SP1
Unified Messaging in Office Communications Server at
http://go.microsoft.com/fwlink/?LinkId=126708. You are strongly urged to read this topic before you begin the following procedures.
Configuring Exchange Server Unified Messaging to work with Enterprise Voice consists of the following tasks:
- Creating one or more UM dial plans, along with their subscriber
access phone numbers as needed, and then creating corresponding
- Using the exchucutil.ps1 script to:
- Create UM IP gateways.
- Create UM hunt groups.
- Grant Communications Server permission to read UM Active
- Create UM IP gateways.
- Creating a UM auto-attendant object.
- Creating a subscriber access object.
- Creating a SIP URI for each user and associating users with a
UM dial plan.