Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-02-20

You must configure the IP gateway devices correctly when you deploy Microsoft Exchange Server 2010 Unified Messaging (UM) for your organization. To do this, you need to configure the interface of the IP gateways to communicate with the Unified Messaging server.

When you perform administrative tasks on the IP gateway using a Web browser, the HTTP requests sent over the network when you configure an IP gateway device are not encrypted. To increase the level of security for the IP gateways on your network, use Internet Protocol security (IPsec) or Secure Sockets Layer (SSL) to help protect the administrative credentials and data transmitted over the network. We also recommend that you use a strong authentication mechanism and complex administrative passwords to protect the administrative credentials for the device.

IP Gateway Interface

There are several types of ports or interfaces that you must configure to enable communication between a Private Branch eXchange (PBX), IP gateway, and Unified Messaging servers on your network. When you configure an IP gateway, you must consider whether the IP gateway device is analog, digital, or analog and digital. If the IP gateway interface that connects to a PBX is analog, you must correctly configure the appropriate settings to enable the IP gateway to communicate with your Unified Messaging servers on your network. For your Unified Messaging servers to communicate with the IP gateways on your network, you must configure the interfaces to communicate with your PBXs, and you must configure the Local Area Network (LAN) connection or network interface for the device.

The following is a list of suggested resources that contain information that can help you correctly configure your IP gateway interfaces and the network interface:

We also recommend that all customers who plan to deploy Exchange 2010 Unified Messaging obtain the assistance of a Unified Messaging specialist. A Unified Messaging specialist helps make sure that there is a smooth transition to Exchange 2010 Unified Messaging from a legacy voice mail system. Performing a new deployment or upgrading a legacy voice mail system requires significant knowledge about PBXs and Exchange 2010 Unified Messaging. For more information about how to contact a Unified Messaging specialist, see the Microsoft Exchange Server 2007 Unified Messaging (UM) Specialists Web site.

After you configure the IP gateway IP interface, you must create and configure a UM IP gateway. For more information about how to create a UM IP gateway, see Create a UM IP Gateway.

After you install the IP gateway, you must create an UM IP gateway object to represent the IP gateway. After you create a UM IP gateway object, the Unified Messaging server associated with the UM IP gateway sends a SIP OPTIONS request to the IP gateway to make sure that the IP gateway is responsive. If the IP gateway doesn't respond to the SIP OPTIONS request from the Unified Messaging server, the Unified Messaging server will log an event with ID 1088 stating that the request failed. To resolve this issue, make sure the IP gateway is available and online and the Unified Messaging configuration is correct.

A Unified Messaging server will communicate only with IP gateways or IP PBXs that are listed as a trusted Session Initiation Protocol (SIP) peer. An event with ID 1175 will be logged when multiple DNS hosts share the same IP address. This event may occur if you've configured you DNS zones with a fully qualified domain names (FQDN) for the IP gateways on your network. Unified Messaging protects against unauthorized requests by retrieving the internal URL of the Unified Messaging Web Services Virtual Directory that is located on the server that has the Client Access role installed and then uses the URL to build the list of FQDNs for the trusted SIP peers. After two FQDNs are resolved to the same IP address, this event will be logged.

You must restart the Microsoft Exchange Unified Messaging service if an IP gateway is configured to have an FQDN and the IP gateway's DNS record is changed after the service has been started. If you don't restart the service, the Unified Messaging server won't be able to locate the IP gateway. This occurs because a Unified Messaging server maintains a cache for all IP gateways in memory, and DNS resolution is performed only when the service is restarted or when an IP gateway's configuration has changed.

For More Information