Connecting Telephony Solutions to Exchange Online UM – Traditional PBXs – Parte 1
Após termos uma introdução de como funciona os certificados, vamos agora ver um pouco sobre PABX.
A Private Branch Exchange (PBX) is a piece of telephony equipment that is connected on the customer’s premises to a set of lines, which in turn are connected to office telephones (sometime called extensions: see Figure 9). To allow users of these phones to call people outside the office system, and vice versa, the PBX is connected to the public telephone network. This kind of connection, which can handle multiple calls simultaneously, is called a telephony trunk.
Many PBXs, especially older ones, do not support voice-over-IP (VoIP) protocols. Instead, they use different varieties of analog or digital protocols to connect to the attached phones or voice mail systems. Internally, these PBXs have a voice switching arrangement that is called time division multiplexing, or TDM.
To connect such PBXs to Exchange UM, the first requirement is to convert TDM protocol data to and from VoIP. For this purpose, devices called VoIP Gateways must be used. Figure 9 shows a VoIP gateway that has been connected to a PBX on the customer’s premises.
The Telephony Advisor for Exchange 2010 content lists the various gateways that have been tested and found to work with traditional PBXs and Exchange UM. For each gateway/PBX combination, there is a link to a configuration note that explains how to connect and configure the PBX and gateway to work with Exchange UM. To establish and verify your PBX’s connection to Exchange Online UM, follow these steps.
1. Verify that the PBX appears in the Exchange 2010 Telephony Advisor content. Note that Microsoft UC Voice Partners or VoIP Gateway vendors may be able to support the configuration and connection of makes and model of PBX that do not appear on this list.
2. Obtain the necessary VoIP gateway and Session Border Controller (SBC). Note that in some cases these may be different parts of the same device.
3. Attach the VoIP gateway and 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. Note that the SBC will need a public address that can be resolved by DNS clients (see step 1 in the certificate notes on page 9).
4. Configure the PBX and VoIP gateway as directed by the relevant configuration note, as if Exchange UM were going to be running on your own premises.
5. Configure the VoIP gateway to send and receive traffic to and from the SBC’s internal network interface (IP address or domain name). If you had been using Exchange UM on your own premises, you would instead have configured traffic from the VoIP gateway directly to the UM server(s), but here the SBC is the portal through which all communication with UM takes place.
6. Configure the SBC to accept traffic arriving (from the VoIP gateway) on its internal interface and forward it to its external interface.
7. 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 VoIP gateway).
Continuamos no proximo post!