Connecting Telephony Solutions to Exchange Online UM – Traditional PBXs – IP PBXs
Finalizando nossa serie de posts sobre Voice Mail no Office 365, vamos finalizar falando de IP PBXs.
Many newer PBXs build in support for VoIP protocols. In this case, it may be possible to use VoIP directly to interface the IP PBX to Exchange UM. In other words, no intermediate VoIP gateway may be needed. However, differences in the way that IP PBXs use VoIP mean that this is not always the case. A list of IP PBXs with which UM has been tested to work directly over IP is included in the Telephony Advisor for Exchange 2010
Figure 20 shows a simplified picture of an arrangement where a customer has an IP PBX on their premises, and connects it to Exchange Online UM. Note that, unlike Figure 9, there is no VoIP gateway. However, there is still a requirement for the customer to provide a Session Border Controller. IP PBXs are generally designed to work in a private network.
The Telephony Advisor for Exchange 2010 content lists the various IP PBXs that have been tested and found to work with Exchange UM. For each IP PBX, there is a link to a configuration note that explains how to connect and configure the IP PBX to work with Exchange UM.
To establish and verify your IP PBX’s connection to Exchange Online UM, follow these steps:
1. Verify that the IP PBX appears in the Exchange 2010 Telephony Advisor content. Note that Microsoft Voice Partners may be able to support the configuration and connection of makes and model of PBX that do not appear on this list. If a VoIP gateway is required to make the IP PBX interoperate with Exchange UM, obtain the necessary gateway and proceed as for Traditional PBXs (page 10).
2. Obtain a Session Border Controller (SBC) that is interoperable with Exchange Online UM.
3. Attach the SBC to your internal IP network. Note that the SBC has (at least) two network interfaces, (at least) one of which is for internal networking, and one of which is intended to be connected to the public IP network.
4. Configure the IP PBX as directed by the relevant configuration note (see above), as if Exchange UM were going to be running on your own premises.
5. Configure the SBC to accept traffic arriving (from the IP PBX) on its internal interface and forward it to its external interface.
6. Configure the SBC’s routing so that traffic arriving (from Exchange Online UM) at the external interface is forwarded to the internal interface (and thus to the IP PBX).
7. In Exchange Control Panel (ECP), create a new UM Dial Plan to represent extensions on your IP PBX that are used by users who will be enabled for Exchange Online UM. See Figure 10, Figure 11, Figure 12, Figure 13 and Figure 14.
8. In ECP, create a new UM IP Gateway. To UM, this will represent your SBC. When you create the UM IP Gateway, it will automatically be assigned a Forwarding Address. See Figure 15, Figure 16, Figure 17, Figure 18 and Figure 19.
9. Configure the SBC so that traffic arriving (from the VoIP gateway) at the internal interface is forwarded (via the external interface) to the Forwarding Address obtained in step 9.
10. In Exchange Control Panel, enable a test user for Unified Messaging.
11. Configure your IP PBX to forward unanswered calls for this user to a hunt group that terminates on the VoIP gateway.
14. From another phone, place a call to the test user’s extension. Allow the call to be forwarded to ‘voice mail’. You should hear Exchange Online UM answer with: “PLEASE LEAVE A VOICE MESSAGE FOR <USER NAME>”, followed by a BEEP. Record a voice message and ensure that it is delivered to the user’s Inbox. You can also use the UM Troubleshooting Tool to verify that user’s Unified Messaging functionality is working.