Connecting to Exchange Online Unified Messaging in Office 365 – Intruduction
No Office365 teremos a opção de Voice Mail, vamos entender melhor como funciona o processo.
Exchange Online Unified Messaging (UM) provides voice mail services to Office 365 customers. UM is not a Private Branch Exchange (PBX): it does not provide voice call switching or numbering service. Each customer is required to provide “dial tone” to UM from a suitable telephony solution.
Figure 1 shows a simplified view of a typical arrangement. The customer has a telephony solution on their premises. This is shown as a black box to indicate that the internal details have been omitted for generality. In practice, the black box represents Microsoft Lync Server 2010 or one of the PBXs with which Exchange Unified Messaging works.
Exchange Unified Messaging requires the use of voice-over-IP (VoIP) protocols. If a customer’s PBX does not use VoIP, they must connect it to UM through a suitable VoIP gateway. The VoIP gateway converts the PBX’s native protocols to VoIP (and vice versa).
The list of PBXs and VoIP gateways that have been tested with Exchange UM is available online as the Telephony Advisor for Exchange 2010.
Figure 1 also shows that the communication between the customer’s telephony solution and Exchange UM Online takes place over a public IP network. As with other Office 365 services, customers use shared network resources when connecting to UM Online. To keep the VoIP network traffic between the customer’s premises and Office 365 private, even though the network is shared, UM Online encrypts all the data that it sends, and requires that the equipment on the customer’s premises do the same.
Figure 1 also shows Voice-over-IP network border elements. These are devices that are positioned at the boundaries between the private IP networks (customer’s premises and Microsoft datacenter) and the public IP network between the customer and the datacenter.
The purpose of these border elements is to provide security for the private networks. Although it is essential to protect the VoIP data that travels between the private networks, this does not guarantee that the private networks themselves are protected. In particular, the VoIP data must enter and leave the customer’s private network. This defines a public network interface that the customer will use to access Exchange Online UM services. Because it is a public interface, other people may also try to access it, even if they have no good reason to do so. Malicious behavior (denial of service attacks, attempts to discover and steal data, and so on) is common on the Internet. Therefore, any network interface that the customer exposes to the world must be protected. The types of voice-over-IP network border element that must be used by Office 365 customers connecting to Exchange Online UM will depend on the type of telephony solution that the customer possesses. Customers who run Microsoft Lync Server 2010 must use the Lync Edge Server role. Customers who run other telephony solutions (PBXs and IP-PBXs), must use devices called Session Border Controllers (SBCs). These may be sold separately, or combined with VoIP gateways into a single product. At the time of writing, the Session Border Controllers that have been tested successfully for interoperability with Exchange Online UM are as follows:
The remainder of this document outlines how to set up the equipment on customer premises, and how to configure Exchange Online UM, to connect the telephone system to the Office 365 voice mail services. It is not a complete configuration guide. Details of SBC configuration vary by make and model. You should consult the relevant documentation for specific details.
No proximo post veremos como conectar o Lync Server 2010 ao Exchange Online do Office365.