Appendix A

UM in Microsoft® Exchange Server 2010

Overview

• Planning the UM Infrastructure

• Planning the UM Configuration

• Planning UM Integration with Office Communications Server

Lesson 1: Planning the UM Infrastructure

• UM Architecture and Topology

• Infrastructure Requirements

• Business Requirements

• Planning Considerations

• Planning Considerations for VoIP Gateways

UM Architecture and Topology

• VoIP protocols- such as SIP and RTP-are between Unified Messaging and IP PBX or IP gateways

• Other protocols are between server roles

Directoryserver

Hub Transport

server

Mailbox server

Client Accessserver

Unified Messaging

server

Outlook

Outlook

OutlookWeb

AccessInternet

Microsoft Exchange

ActiveSync

UM IPGateway

IP PBX PBX

PSTN

Internalphone

Externalphone

Internalphone

Internalphone

Firewall

SMTPMAPI RPCHTTPSVoIP

RPC/HTTPSTDMLDAP

Forest

Site

Infrastructure Requirements

Server roles

• Mailbox server

• Hub Transport server

• Client Access server

• Unified Messaging server

Other infrastructure requirements

• VoIP phone

• AD DS

• PBX

• Unified Messaging IP gateway

Business Requirements

• Number of supported users

• Phone and voice mail users

• Storage requirements for users

• Voice mail codec

• Number of simultaneous users

Planning Considerations

• Telephony network and current voice mail system

• Current data network design

• AD DS environment

• IP/VoIP gateways, telephony equipment, and Unified Messaging servers placement • PBXs are networked,

centralized, or located inmultiple locations

• Place PBXs physically closeto IP gateways

• IP gateway and UnifiedMessaging placement

• Exchange Server roles and Unified Messaging Servers

• WAN termination

• Codec

Planning Considerations for VoIP Gateways

• Supported IP/VoIP gateways

• Two configurations for IP/VoIP gateway devices:

• IT/PBX: A single hardware device

• Legacy PBX and an IP/VoIP gateway: Two separate hardware devices

• Multiple IP gateways

• Multiple locations

Lesson 2: Planning the UM Configuration

• Hardware Infrastructure Requirements

• UM Dial Plan Object

• UM Hunt Group Object

• UM Server Object

• UM Mailbox Policy Object

• UM Clients

• Process for Deploying UM

Hardware Infrastructure Requirements

• Processor

• Minimum: 2 processor cores

• Recommended: 8 processor cores

• Maximum: 12 processor cores

• Memory

• Minimum: 4 GB

• Recommended: 2 GB per processor core

• Storage

• Number of users

• Number of language packs

UM Dial Plan Object

A dial plan object:

• Is an Active Directory container object that logically represents sets or groupings of PBXs that share common user extension numbers

• Represents the scope of a voice mail system that Unified Messaging is replacing, generally

A dial plan:

• User can reach all others using a fixed length extension number

• Extension is unique

• May consist of feature transparent PBX networks

• Plus the extension number uniquely identifies each Unified Messaging user

A dial plan object:

• Is an Active Directory container object that logically represents sets or groupings of PBXs that share common user extension numbers

• Generally represents the scope of a voice mail system that Unified Messaging is replacing

A dial plan:

• User can reach all others using a fixed length extension number

• Extension is unique

• May consist of feature-transparent PBX networks

• Extension number uniquely identifies each Unified Messaging user

UM Hunt Group Object

A hunt group:

• Is a group of PBX or IP/PBX resources or extension numbers, that represent a collection of like endpoints

• Is used to distribute calls efficiently into or out of a given business unit

• Is accessed by using a pilot number

Hunt group objects:

• Represent a hunt group configured at the PBX, to direct calls to a VoIP gateway

• Are contained within a Unified Messaging IP gateway object

One or more hunt groups can be associated with a Unified Messaging IP gatewayOne or more hunt groups can be associated with a Unified Messaging IP gateway

UM Server Object

An administrable object used for controlling Unified Messaging properties on an Exchange Server 2010 server running the Unified Messaging server role

An administrable object used for controlling Unified Messaging properties on an Exchange Server 2010 server running the Unified Messaging server role

• Performs directory lookups in AD DS in these scenarios:

• To locate the Mailbox server that hosts the user mailbox

• To locate user’s prerecorded, spoken names from AD DS

• To locate subscriber extensions and other attributes

A default deployment of a Unified Messaging server can support up to 100 concurrent voice mail connections

UM Mailbox Policy Object

Unified Messaging mailbox policies are conceptually similar to traditional voice mail Classes of ServiceUnified Messaging mailbox policies are conceptually similar to traditional voice mail Classes of Service

Unified Messaging mailbox policy properties can include:

• Dial plan (required)

• Maximum greeting length

• Number of unsuccessful login attempts before password reset

• Minimum digits required in a PIN

• Number of days until a new PIN is required

• Number of previous passwords disallowed

• Calling restrictions

UM Clients

Unified Messaging clients include:

• Office Outlook 2007

• Outlook Web Access

• Windows® Mobile andMicrosoft Exchange ActiveSync

• Outlook Voice Access (internal and external phone)

Process for Deploying UM

1. Create a Dial Plan object

2. Create a Unified Messaging IP gateway object, andassociate it with the Dial Plan object (optional)

3. Create a Hunt Group object, and associate it with a Unified Messaging IP gateway object (optional)

4. Enable users, and associate them with a mailbox policy

Lesson 3: Planning the UM Integration with Office Communications Server

• Office Communications Server 2007 R2 Features

• Benefits of UM Integration with Office Communications Server 2007

• Planning the UM and Office Communications Server Integration

Office Communications Server 2007 R2 Features

Office Communications Server 2007 provides:

• Instant messaging

• Presence information

• Web conferencing

• VoIP

Unified Messaging can be integrated with Office Communications Server 2007 to provide access to messaging and voice functionality using both messaging and Office Communications Server clients

Unified Messaging can be integrated with Office Communications Server 2007 to provide access to messaging and voice functionality using both messaging and Office Communications Server clients

Benefits of UM Integration with Office Communications Server 2007

Integration provides these additional benefits:

• Dial plans enable an Office Communications Server 2007 user to call another without dialing that user

• High-fidelity voice messages

• Access to Outlook Voice Access from Office Communicator 2007 without requiring a PIN

• Office Communicator 2007 clients can associate subjects and priorities to voice messages

• Missed call e-mail notification messages using Message Waiting Indicator

• Messages received within the Office Communications Server 2007 environment cannot be forwarded outside the Office Communications Server 2007 environment to preserve the security and privacy of voice mail

Planning the UM and Office Communications Server Integration

• Integration planning considerations

• Bandwidth

• Dial plans

• Number of users

• IP gateway placement

• Fault tolerance