
Understanding Exchange 2007 Unified Messaging
From an architectural perspective, Exchange Server 2007 has been significantly enhanced from Exchange Server 2003. Exchange Server 2007 is a modular system that includes five server roles—Edge Transport, Hub Transport, Mailbox, Client Access, and Unified Messaging—that perform specific operations in an Exchange organization. Except for Edge Transport, which must sit in the perimeter network, all roles can be run on a single server, or broken up onto multiple servers based on the size and requirements of the organization. The following roles participate in delivering Unified Messaging services to end users:
-
The Unified Messaging server role communicates with both the telephony and e-mail components of the messaging infrastructure to accept and route calls, record and play back voice messages, receive faxes, and route messages to subscribers' mailboxes. This role also provides the Outlook Voice Access service and hosts any auto attendants that the organization might have configured.
-
The Mailbox server role contains the user mailboxes, where voice mail and fax messages are stored, together with the other information types such as e-mail, calendar, and contacts.
-
The Client Access server role lets clients such as Exchange ActiveSync, Outlook, and Outlook Web Access communicate with the Mailbox server role.
-
The Hub Transport server role moves messages between the other server roles, while enabling policies to be applied in transit.
Understanding the Unified Messaging Server Role
The Unified Messaging server role handles interaction between telephone calls and the rest of the messaging system. The Unified Messaging server accepts call requests from the PBX, offers call answering for voice mail and fax calls, delivers Outlook Voice Access services to subscribers, records and plays back voice messages, receives faxes, and hosts the auto attendant. To understand how Exchange 2007 supports unified messaging and how it can be deployed to deliver the benefits described in this article, you must under the Unified Messaging server.
Understanding PBX Hardware and IP Gateways
The Exchange 2007 Unified Messaging server role can communicate with two types of PBX hardware devices. Some PBX hardware devices, known as IP PBXs, directly implement Voice over IP (VoIP) capability. However, most PBXs do not directly provide VoIP services. Instead, they use legacy, proprietary, circuit-switched protocols to transport telephone traffic. For example, Time Division Multiplexing (TDM) is a circuit-switched method of transporting telephone traffic. These legacy PBXs require an IP gateway that translates between circuit-switched protocols and packet-based Internet protocols compatible with the VoIP network stack that exists in Exchange 2007 Unified Messaging.
When the PBX receives an inbound call, it is responsible for ringing the selected extension. If the call is not answered, the PBX uses its own call coverage configuration to determine where the call should go next. Assuming that the coverage configuration specifies transfer to Exchange 2007 Unified Messaging, the PBX routes the call from the original destination extension to the hunt group that is configured to point to Exchange 2007 Unified Messaging. For an IP PBX, the call is directly connected without a gateway. For legacy PBXs, the PBX reaches Exchange 2007 Unified Messaging through an IP gateway.
The IP gateway is responsible for converting the call data from circuit-switched to packet-switched protocols. Exchange 2007 Unified Messaging uses Session Initiation Protocol (SIP) for call setup and signaling, the Real-time Transport Protocol (RTP) for voice sessions, and the T.38 (fax over IP) protocol for fax data. Exchange supports (but does not require) using the Transport Layer Security (TLS) protocol to help secure and authenticate communications between the PBX or gateway and the Exchange Unified Messaging server.
Intel and AudioCodes offer gateway products that link Exchange Unified Messaging servers together with legacy PBX systems. For the latest information about the availability of IP gateways that are certified to work with Exchange Server 2007, see the Telephony Advisor for Exchange Server 2007 Web site.
Understanding Call Processing in Exchange 2007
You should understand what occurs when someone calls an Exchange Server 2007 Unified Messaging subscriber. The process is fairly straightforward, and the following section describes what actions the Unified Messaging server performs and also how it interacts with other components of the telephone and messaging systems.
Voice Calls
When a caller places a call, which is routed to the recipient's telephone by using the Public Switched Telephone Network (PSTN) or the organization's internal telephone lines, the call circuit is established. If the called number is a direct inward dial (DID) extension, the PBX will either ring the intended extension, or, if the dialed party is already on the telephone, the PBX will transfer the call to the pilot number of the Exchange Unified Messaging server. The protocol that is used to perform this transfer will depend on the type of PBX, as follows:
-
If the PBX is an IP PBX, it establishes a session with the Unified Messaging server by using SIP. As soon as the session is set up, the live voice traffic is transferred by using RTP.
-
If the PBX uses an IP gateway, the circuit-switched call data is sent to the IP gateway, which establishes a session with the Unified Messaging server by using SIP, and then translates the call and forwards the live voice data to the UM server by using RTP.
The original called party information is maintained as part of the supplementary signaling information when the call is transferred. When the call arrives at the Unified Messaging server, the called party information and the PBX source of the call are used to look up the user in Active Directory and retrieve their mailbox greeting. This is possible because each UM-enabled user has an associated extension. The Unified Messaging server retrieves the user’s welcome greeting, plays it, and records any message that the caller might want to leave.
Fax Messages
Fax message handling works in a similar method to voice call answering. By default, all users are enabled for fax. An organization can provide one fax number for all users, or an individual number for each user. Dedicated numbers will not actually ring any telephones. When a fax is sent to a dedicated number, the PBX transfers the call directly to the Unified Messaging hunt group. You can also set up a central fax number with a central fax Inbox for your whole organization.
Exchange 2007 Outlook Voice Access
When they access Outlook Voice Access, subscribers call the hunt group of the Unified Messaging system directly. There is no called party information in this case because the call was not redirected by the PBX from another called party. The Unified Messaging server answers these calls with the main menu, which asks the user to identify their mailbox number and lets them log on.
Auto Attendants in Exchange 2007 Unified Messaging
In telephony or Unified Messaging environments, an automated attendant or auto attendant menu system transfers callers to the extension of a user or department without the intervention of a receptionist or an operator. In many auto attendant systems, a receptionist or operator can be reached by pressing or saying zero. UM auto attendants are configured like voice users. In the PBX, a dedicated number is given to the auto attendant. This number is set up in the PBX to always redirect to Unified Messaging. When an incoming call arrives at the Unified Messaging server, the called party information is used by Unified Messaging to determine that the call is addressed to a particular auto attendant object. The greetings and menus of that auto attendant are then played to the caller.
Understanding How Voice and Fax Messages Reach the Inbox
When a caller leaves a message, the Unified Messaging server records the message. The server creates a new MIME-formatted SMTP message, with the audio message attached, and then sends it to the subscriber's mailbox. In practice, that means that the message is first sent to the Hub Transport server. The Hub Transport server can apply rules to the message to make sure that it complies with organizational policies. The Hub Transport server can store the message for later delivery if network problems prevent immediate delivery to the Mailbox server.
Messages are recorded by using the audio codec specified by the Exchange Unified Messaging server administrator. Exchange 2007 Unified Messaging supports the following three methods of encoding received audio:
-
Uncompressed (16KB/sec) by using the G.711 PCM codec
-
Compressed by using the industry-standard GSM 06.10 codec (approximately 1.6KB/sec)
-
Compressed by using the built-in Windows Media (WMA) voice codec (approximately 1.1KB/sec)
WMA provides the best overall storage efficiency. Because a typical voice mail message size is around 30 seconds, Windows Media encoding is specified as the default audio codec. This is ideal, because voice data compressed by using the Windows Media codec can be played back on any computer that has an up-to-date version of Windows Media Player installed.
As soon as a voice mail message is delivered to the user's Inbox, the user can access the voice message by using a client such as Outlook 2007, Outlook Web Access for Exchange 2007, or Outlook Voice Access.
This same process is used for incoming faxes. However, the T.38 protocol is used to route the fax information to the Unified Message server. Additionally, the message in the user's Inbox will contains a Tagged Image File Format (TIFF) image of the fax contents.
Understanding Outlook Voice Access
Outlook Voice Access consists of the following two related interfaces:
-
The Voice User Interface (VUI) enables subscribers to control Unified Messaging activities by using voice input.
-
The Telephone User Interface (TUI) enables subscribers to control Unified Messaging actions by using dual tone multi-frequency (DTMF), also known as touch-tone input.
For Exchange 2007, the VUI is supported in English (United States, United Kingdom, and Australia) and the TUI is available in English (United States), English (United Kingdom), French (France), French (Canada), German, Japanese, Italian, Spanish (Spain), Spanish (Latin America), Portuguese (Brazil), Korean, Mandarin (China), Mandarin (Taiwan), Dutch, and English (Australia).
When a subscriber calls the Outlook Voice Access number, their call is routed by the PBX to Exchange Unified Messaging. As soon as the subscriber is connected to the Unified Messaging server, the subscriber authenticates by using DTMF. Outlook Voice Access enables the subscriber to listen to voice messages, play e-mail messages, listen to calendar appointments, accept or reject meeting requests, send "I’ll be late" messages to meeting participants, retrieve contact information, connect to contacts, or search the directory.
Exchange 2007 Unified Messaging protects a user's voice mail access by using PINs. Every UM-enabled mailbox has a PIN that is separate from the user’s Active Directory account password. The Unified Messaging PIN is stored as an encrypted attribute of the user’s Active Directory account object.
When a user mailbox is enabled for Unified Messaging, the administrator specifies a PIN. Users can reset their own PINs through Outlook Web Access or through the Outlook Voice Access interface. Administrators can set policies for PIN length and expiration and different PIN policies can be applied to different groups of users.