Understanding Unified Messaging IP Gateways
Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-07-17
The Unified Messaging (UM) IP gateway is a container object that logically represents a physical IP gateway hardware device. Before the IP gateway can be used to process Unified Messaging calls, the IP gateway must be represented by an object in the Active Directory directory service.
Traditionally, "gateway" is a term that describes a physical device that connects two incompatible networks. With Microsoft Exchange Server 2007 Unified Messaging and other unified messaging solutions, the IP gateway is used to translate between the Public Switched Telephone Network (PSTN)/Time Division Multiplex (TDM) or circuit-switched based telephony network and an Internet Protocol (IP) or packet-switched data network.
|A packet-switched network is a network in which packets (messages or fragments of messages) are individually routed between nodes that may be shared by many other nodes. This contrasts with a circuit-switched network that sets up a dedicated connection between the two nodes for their exclusive use for the duration of the communication.|
Exchange 2007 Unified Messaging relies on the ability of the IP gateway to translate TDM or telephony circuit-switched based protocols, such as Integrated Services Digital Network (ISDN) or QSIG, from a Private Branch eXchange (PBX) to protocols based on VoIP or IP, such as Session Initiation Protocol (SIP), Realtime Transport Protocol (RTP), or T.38 for real-time facsimile transport.
Although there are many types and manufacturers of PBXs, IP gateways, and IP PBXs, there are basically two types of IP gateway component configurations:
IP PBX A single device
PBX (legacy) and an IP gateway Two separate components
To support Exchange 2007 Unified Messaging, one or both types of IP/VoIP device configurations are used when connecting a telephony network infrastructure to a data network infrastructure.
The UM IP gateway is an Active Directory container object that contains one or more Active Directory UM hunt groups and other UM IP gateway configuration settings. UM IP gateways are created within Active Directory to logically represent a physical hardware device called an IP gateway. The UM IP gateway can represent either an IP gateway or an IP PBX. The combination of the UM IP gateway object and a UM hunt group object establishes a logical link between an IP gateway hardware device and a UM dial plan.
After the UM IP gateway is created, the IP gateway can be linked to or associated with a single or multiple UM hunt groups and UM dial plans. The UM hunt group provides a link between the UM IP gateway and a UM dial plan. By creating multiple UM hunt groups, you can associate a single UM IP gateway with multiple UM dial plans.
After you have created a UM IP gateway object, the Unified Messaging server associated with the UM IP gateway will send a SIP OPTIONS request to the IP gateway to ensure that the IP gateway is responsive. If the IP gateway does not 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, ensure that the IP/VoIP is available and online and that the Unified Messaging configuration is correct.
|Before an IP gateway can be used to process calls, a UM IP gateway must be associated with at least one UM dial plan. Also, at least one UM server must be associated with at least one UM dial plan.|
By default, IP gateways are left in an enabled state after they are created. However, the UM IP gateway can be enabled or disabled. If you disable a UM IP gateway, it can be in one of two disabled modes. The first disabled mode forces all associated UM servers to drop existing calls. The second disabled mode forces the UM server associated with the UM IP gateway to stop handling any new calls presented by the IP gateway.
|If a Unified Messaging IP gateway is deleted, the UM servers associated with the IP gateway will no longer be able accept or process new call requests from the IP gateway.|
For more information about Unified Messaging Active Directory objects, see Overview of Unified Messaging Active Directory Objects.
For more information about how to manage Unified Messaging objects, see Managing Unified Messaging Objects.