You must follow these steps completely and in the order shown. Failure to do so increases the risk of node failure.
Microsoft's Windows Update and Cloud Connector Edition update can be triggered by Microsoft from Office 365. The CCE will not be functional until Windows Updates completes the download and installation..
Windows Update could also restart the ASM.
If no calls can be established (typically the failure is between CCE and O365) but the relevant Signaling Group is up, the following two issues can be expected:
In some instances, an ASM being updated has also closed the SIP Signaling Group.
Technicians can manually stop and disable the Windows Update service, which will re-instantiate as a manual, running process after the ASM is restarted.
In this section...
Prerequisites
A public domain name prepared and mapped with your Office 365 tenant. See Create an Office 365 Tenant. |
An entry on your public domain name that points to the fixed IP address of your Unable to show "metadata-from": No such page "_space_variables" . |
An Office 365 tenant with an E5 license or E3 + Cloud PBX. |
You must have the Skype for Business Administrator role for your O365 tenant account. |
A public certificate authority ready to sign a certificate for the Unable to show "metadata-from": No such page "_space_variables" .Important
Complete the steps outlined in Certificate Requirements at Microsoft Technet. |
A properly configured firewall. See Ports and Protocols at Microsoft Technet. |
Latest System Release SBC Firmware. Important
|
Latest System Release SbcComms Firmware. Important
|
Microsoft Cloud Connector Edition image 1.4.1 on ASM recovery partition. |
The following diagram shows typical CCE deployment scenarios on a PSTN site. The PSTN site is a combination of Cloud Connector instances, deployed at the same location, and with common PSTN gateways pool connected to them. PSTN sites allow you to:
Provide connectivity to gateways closest to your users.
Allow for scalability by deploying multiple Cloud Connector instances within one or more PSTN sites.
Allow for high availability by deploying multiple instances of Cloud Connector within a single PSTN site.
CCE Deployment Scenarios
Scenario 1 and Scenario 2 are covered in Configuring the SBC Edge for a Single CCE. This document contains steps for Scenario 3 and Scenario 4 .
For this best practice, the CCE is deployed in the following network:
Typical Deployments
In this best practice the router/firewall is configured with the following rules:
Firewall Rules Used for This Best Practice
Make sure that CCE FQDN is resolving to the
The following sections describe a clean install of the CCE. If your environment has already deployed with CCE, and you are planning to re-deploy, it is necessary to clean up the site(s) that may already exists in O365. To do so, please follow the steps in CCE Re-Deployment Specific Steps in Re-initializing the ASM.
For best results:
During the initial setup, SBC Edge have to be configured with two IP interfaces, one for internal company network (corporate network), and the second one for DMZ network (Internet network) as shown below:
Pre-configured IP Interfaces
Ensure That the Node's FQDN is Correct
When configuring a secondary
If your ASM has been used previously, reinitialize it following the steps in Re-Initializing the ASM.
Confirm that the ASM is ready to deploy the CCE by following these steps.
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Click the Task tab, and then click Operational Status. |
3 | Verify that:
|
4 | Change the ASM Admin password:
|
Deploying CCE 1.4.1 on the
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of both Unable to show "metadata-from": No such page "_space_variables" . |
2 | Navigate to Tasks > Setup Cloud Connector Edition. |
3 | Click the ASM Config tab and configure/verify the Network and IP settings of your ASM as shown below. |
4 | Click Apply. After receiving the activity status as successfully completed, click the Generate CSR tab. |
Configuring the ASM – CCE-1
Configuring the ASM – CCE-2
This process is required only if you don't have a public certificate for your deployment. If you already have a certificate, proceed to Import Certificate.
Perform these steps on only one of the
Step | Action |
---|---|
1 | Login to the WebUI of one of the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Navigate to Tasks > Setup Cloud Connector Edition > Generate CSR. |
3 | Generate the CSR as shown below with following information. Note: This example uses aepsite1.sonusms01.com and sip.sonusms01.com as common name and SAN To ensure creating a valid CSR for Cloud Connector Edition usage, please see the section "Certificate requirements" on https://technet.microsoft.com/en-us/library/mt605227.aspx .
|
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of both Unable to show "metadata-from": No such page "_space_variables" . |
2 | Navigate to Tasks > Setup Cloud Connector Edition and then click the Import Certificate/Keys tab. |
3 | On SBC-1, click the Action drop-down list and select the appropriate option:
|
4 | Click OK. |
5 |
|
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane. |
3 | Click the Configure CCE tab. |
4 | Configure all necessary information and then click OK.
Configuring the CCE – CCE-1 Configuring the CCE – CCE-2 Note: Enter the ASM's IP address in the HA Master IP Address field. The Slave uses the same root certification as the Master, and this location contains the shared folder that contains the Root CA of the Master. |
5 | After receiving the activity status as successfully completed, click the Prepare CCE tab to continue. |
You must verify (and possibly correct) the CCE Configuration INI File after configuring the CCE.
The CCE deployment internally sets the domain suffix as defined under VirtualMachineDomain attribute. Although your
In addition, when deploying a High Availability (HA) systems, it is important to have Management IP Prefix unique on each HA system. For instance, if your HA Master CCE system has 192.168.213.x as the Management IP Prefix, you need to be sure to configure this attribute differently on HA Slave system. While doing this, also make sure that subnet that you are defining in this field does not conflict in your IP infrastructure.
Perform these steps on both
Follow these steps to verify and correct values in the CCE Configuration INI File.
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Click the Configure CCE tab and then click Click to re-configure CCE application. |
3 | Click OK on the popup dialog box. |
4 | Click the Edit Raw Config button. |
5 | Verify/correct the values in the CCE Configuration INI File and then click OK. |
Perform these steps on both
Step | Action |
---|---|
1 | Login to the WebUI of both Unable to show "metadata-from": No such page "_space_variables" . |
2 | Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane. |
3 | Click the Prepare CCE tab. |
4 | Click the Prepare CCE button, enter the password for Edge Server External Certificate, and then click OK. |
5 | To complete the deployment, continue with Manually Configuring the CCE on the ASM. |
Manually deploying CCE on the ASM requires:
Registering the CCE Appliance
Installing the CCE Appliance
Perform these steps on only one of the
Step | Action |
---|---|
1 | Remote desktop to the ASM of the Unable to show "metadata-from": No such page "_space_variables" System 1. |
2 | Launch PowerShell. |
3 | Execute the following commend for HA Master:
|
4 | Enter the password(s) as prompted for the various users. |
5 | When prompted for the online tenant administrator user name and password, make sure to enter this information correctly. If you make a mistake, refer to Manage Your Office 365 Tenant |
6 | After successful execution, remote desktop to the ASM of the Unable to show "metadata-from": No such page "_space_variables" System 2. |
7 | Launch PowerShell. |
8 | Execute the following commend for the HA Slave, and enter the appropriate password(s) when prompted:
|
Step | Action |
---|---|
1 | Remote desktop to the ASM of the Unable to show "metadata-from": No such page "_space_variables" System 1. |
2 | Launch PowerShell. |
3 | Execute the following command for the HA Master, and enter the appropriate password(s) when prompted:
|
Step | Action |
---|---|
1 | Remote desktop to the ASM of the Unable to show "metadata-from": No such page "_space_variables" System 1. |
2 | Launch PowerShell. |
3 | Execute the following command, and enter the appropriate password(s) when prompted:
|
Step | Action |
---|---|
1 | Remote desktop to the ASM of the Unable to show "metadata-from": No such page "_space_variables" System 2. |
2 | Launch PowerShell. |
3 | Execute the following command for the HA Master, and enter the appropriate password(s) when prompted:
|
After the CCE is deployed, integrate the
SIP Provider (193.168.210.103) – SBC Edge (193.168.210.125) – CCE (mediation Server: 193.168.210.123) – O365 Cloud
Step | Action |
---|---|
1 | Login to the WebUI of Unable to show "metadata-from": No such page "_space_variables" -1. |
2 | Navigate to Tasks > SBC Easy Setup and then click the Easy Configuration Wizard. |
3 | Follow steps 1, 2, and 3 and then click Finish.
The wizard configures the necessary settings for SBC Edge-1 and CCE integration, after which you can see all relevant configuration items in Settings tab.
|
Step | Action |
---|---|
1 | Login to the WebUI of Unable to show "metadata-from": No such page "_space_variables" -2. |
2 | Navigate to Tasks > SBC Easy Setup and then click the Easy Configuration Wizard. |
3 | Follow steps 1, 2, and 3 and then click Finish.
The wizard configures the necessary settings for SBC Edge-2 and CCE integration, after which you can see all relevant configuration items in Settings tab. |
The Mediation Server FQDNs must be added to SIP Server Table and SIP Signaling Group Federated FQDN fields with the following information:
Mediation Server FQDNs
Both ASMs must be re-initialized with the latest image that contains the latest CCE software (in this example it is version 1.4.1).
Step | Action |
---|---|
1 | Login to the WebUI of both Unable to show "metadata-from": No such page "_space_variables" systems. |
2 | Navigate to the Tasks tab and then click Reinitialize. |
3 | Select the appropriate image from the drop-down menu and click Apply.
|
If the CCE was previously deployed, previously installed information must be cleared in O365. To do so, follow the steps below.
Step | Action |
---|---|
1 | Remote desktop to the ASM system. |
2 | Launch PowerShell. |
3 | Execute the following command:
Import-Module skypeonlineconnector $cred = Get-Credential
|
4 | When prompted, enter the credentials for O365 Admin Tenant.
|
5 | Execute the following command:
$Session = New-CsOnlineSession -Credential $cred -Verbose Import-PSSession $session
|
6 | To remove the current appliance, run the following command and copy the Identity into your clipboard:
Get-CsHybridPSTNAppliance
|
7 | Enter the following command to remove the appliance:
Unregister-CsHybridPSTNAppliance -Identity <paste the identity here> -Force |
8 | Enter the following command to verify that the appliance has been removed:
Get-CsHybridPSTNAppliance |
9 | This completes the cleanup. Continue to Configuring the CCE |
Follow these steps if the CCE deployment cannot open the PFX certificate due to a password mismatch.
Step | Action |
---|---|
1 | Re-perform the steps in Preparing the CCE to specify a new Password for the PFX file. |
2 | Use the PowerShell commands Install-CcAppliance -UpdateAllCredentials and Set-CcCredential -AccountType TenantAdmin to reset the credentials. |