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....
This page provides a step-by-step procedure for CCE High Availability Deployment on SBC Edge.
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 that are 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.
Scenario 3 and Scenario 4 are covered in Configuring the SBC Edge for Two CCEs. This document contains steps for Scenario 1 and Scenario 2 deployments.
For this best practice, Cloud Connector Edition deployment follows the cabling shown below:
For this best practice, the Router/Firewall is configured using the following rules:
Make sure that CCE FQDN is resolving to the
Update the
Sonus recommends starting with a clean and empty configuration. During the initial setup,
Optionally, if you want to configure a secondary
If your ASM have been used before, you should re-Initialize it now. Refer to Re-Initializing the ASM for details.
Confirm that the ASM is ready to deploy the Cloud Connector Edition. To do so:
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 select Operational Status. |
3 | Verify the following:
|
After you update the ASM, change its Admin Password.
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 Change Admin Password. |
3 | Enter and confirm your new password and then click OK. |
Deploying CCE 1.4.1 on the
Step | Action |
---|---|
1 | Login to the WebUI of the 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. |
4 | Click Apply. After receiving the activity status as successfully completed, click the Generate CSR tab. |
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.
Step | Action |
---|---|
1 | Login to the WebUI 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. 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 . |
4 | Copy the CSR from the lower pane of the Generate CSR page and save it as a .txt file. |
5 | After the CSR is signed by the Certificate Authority and you receive the PKCS12 Certificate and Key file (i.e.: certicate.pfx file), continue the wizard by clicking on Import Certificate tab. |
Step | Action |
---|---|
1 | Login to the WebUI of the 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 | Click the Action drop-down list and select the appropriate option:
|
4 | Select the relevant certificate file using the Choose File button and then click OK. |
5 | Select the file by browsing to it using Select File. |
6 | Click OK. |
7 | After receiving the activity status as successfully completed, click on Configure CCE tab. |
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 as shown below. If the deployment environment consists of multiple-site with a single certificate or a wild card certificate, ensure the CCE Site Name matches your public edge fqdn for this site before proceeding |
5 | After receiving the activity status as successfully completed, click the Prepare CCE tab to continue. |
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 Prepare CCE tab. |
4 | Click the Prepare CCE button, enter the password for Edge Server External Certificate, and then click OK as shown below. |
5 | To complete the deployment, continue with Manually Configuring the CCE on the ASM. |
Manually deploying CCE on the ASM requires:
If you plan to use a proxy on the ASM Host to reach Office 365, you must add the Management network (192.168.213.0) into the exclusion list.
Step | Action |
---|---|
1 | Remote desktop to the ASM system. |
2 | Launch PowerShell. |
3 | Execute the following commend:
|
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. In case of mistake, refer to: Manage your Office 365 tenant. |
Step | Action |
---|---|
1 | Remote Desktop to the ASM system. |
2 | Launch PowerShell. |
3 | Execute the following commend:
Note: This step does not require interactive input and can run unattended. It will take nearly two hours to execute. |
4 | This completes the CCE deployment. At this point, AD, CMS, Edge, and Mediation Server Virtual Machines should be up and running. |
After configuring the
After the CCE is deployed, integrate the Sonus Sbc Edge and allow calls from/to O365 clients. In this example, the following steps will set up the Sonus Sbc Edge for:
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 the Unable to show "metadata-from": No such page "_space_variables" . |
2 | Click the Tasks tab, and then click SBC Easy Setup > Easy Config Wizard in the navigation pane. |
3 | Follow steps 1, 2, and 3 as shown below and then click Finish.
|
4 | Click OK on the next two popups to complete the setup. |
5 | The wizard configures the necessary settings for the single Unable to show "metadata-from": No such page "_space_variables" and CCE integration. Relevant configuration items are shown in the Settings tab below:
|
Step | Action |
---|---|
1 | Login to the WebUI of the Secondary Unable to show "metadata-from": No such page "_space_variables" . |
2 | Click the Tasks tab and then run the Easy Config. |
3 | The preceding step will configure the Secondary |
4 | Add the FQDNs of the Mediation Server and the pool to the host table (pointing out to Mediation Server's IP address) to allow calls to O365. |
With the preceding settings, an endpoint from the SIP provider side can dial the number of a Skype For Business (O365) client and reach out to it over
Similarly, a Skype For Business (O365) client can dial the number of an endpoint off of ITSP and reach out to it over
The ASM must be re-initialized with the image that contains the latest CCE software. To do so:
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 Reinitialize in the navigation pane. |
3 | Select the appropriate image from the drop-down list and then 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:
|
7 | Execute the following command to remove the appliance:
|
8 | Execute the following command to verify that the appliance has been removed:
|
9 | This completes the cleanup. Continue to Configuring the CCE Through the WebUI |
Step | Action |
---|---|
1. | After receiving the activity status completion message, click the Click to re-configure CCE application button. |
2. | Click OK on the popup. |
3. | Click the Raw (INI) Config button and then click Edit.. |
4. | Edit any required field In the INI file with the appropriate value for your environment. Note: The example uses AEPSITE2 for the these attributes. |
5. | After verifying this information, click OK:. |
Step | Action |
---|---|
1 | After receiving the activity status completion message, click the Click to re-configure CCE application button. |
2 | Click OK on the popup. |
3 | Click the Raw (INI) Config button and then click Export or Import. |
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. |