In the previous blog post, we prepared our host server for CCE1.4.1 installation with the necessary hardware and software pre-requisites and customized the CloudConnector.ini file. In this post, we will start building the VMs which will actually download the necessary software bits from the internet as well and downloading and installing updates, while leveraging the base OS iso image on the host server. After that, we will configure the CCE components to work with our Office365 E5 tenant. As mentioned, we are using an Asterisk IP-PBX to emulate a PSTN Gateway. One additional point that I did not mention in the previous post is that we are using pure Azure AD user accounts for CCE, as opposed to on-premise AD synchronized user accounts required by PSTN Connectivity via an on-premise instance of Skype4B.
This is the continuation of the post Deploying Polycom phones for Cloud PBX with on-premise PSTN Connectivity. Here we are ready to move on-premise Skype for Business Enterprise Voice enabled accounts to Office365 E5 Cloud PBX. As shown in the previous post, we have already used two on-premise Enterprise Voice accounts to sign in on two different Polycom devices: a VVX600 and a Trio8800. Below is the status of these two devices as seen on from the web admin Lync Status page:
Last week at Enterprise Connect 2016, Polycom and Microsoft made joint announcements which has had profound impact across the entire UC industry. Never before has 2 companies partnered together so closely to bring about a whole new level of innovation and technology for meeting room spaces and collaboration focused built purposefully for the cloud. While there are already several great blog posts on the announcements such as the one from Network World by Zeus Kerravala, this blog posts focuses on what those announcements really mean for customers in practical terms.
Ensuring Pool Quorum and Routing Group Quorum
HA in the Skype4B Front-End pool is the ability of the server pool to continue servicing users in the event of a failure of 1 or more servers within the pool. Front-End pool HA is based on clustering via HLB and DNS load balancing built into the servers to automatically distribute groups of users across the various front end servers in a pool. During startup, 85% of all servers in the pool must be started in order for the entire pool to be functional. This is known as achieving Routing Group level Quorum. After the pool is operational, then only 50% of the servers in the pool must be running in order for the pool to remain functional. This is called achieving Pool Level Quorum and is not to be confused with Routing Group Level Quorum. The table below shows the numbers for these two quorum types:
In the previous blog article, we discussed the capabilities of Lync 2013 LBR that was introduced in CU1. This allows the prevention of PSTN Toll By-pass which is prohibited by government regulations in countries such as India. For example, Lync user A in Delhi can make a call to a local Delhi PSTN number using the PSTN Gateway in Delhi. But when the same user travels to Mumbai and tries to make a call back to a local Delhi PSTN number, LBR will not allow this user to use the same PSTN Gateway in Delhi via the Mumbai-Delhi WAN link. While this covers the Peer-2-Peer calling restrictions, it does not address conferencing scenarios. For example, Lync user A in Delhi first makes a call to a local Delhi PSTN number using the PSTN Gateway in Delhi, then adds Lync user B in Mumbai to create a 3 party AVMCU conference. If the conference is allowed, then User B is effectively using PSTN Toll-Bypass, and TRAI regulations also prohibit the mixing of VOIP and PSTN calls. To address this scenario, we need to configure and enable Conferencing LBR, which was introduced in Lync 2013 CU2. In this article we explore the configuration of Conferencing LBR and testing with Polycom CX600 phones. Below is the diagram of the test scenario:
In this lab, we use a standard edition Lync server configured with an Asterisk PBX to simulate a PSTN connection. The diagram of this setup is shown below: