Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
top
top

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSYM-2261822269
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6REV3REV1

 

UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c87d0111, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

 

title

Warning
Warning
titleREAD BEFORE BEGINNING

You must follow these steps completely and in the order shown. Failure to do so increases the risk of node failure.

Section
Column
width40%
Panel
Table of Contents
Table of Contents
Column
Info
title
About this Page

The intent of this article to provide a step-by-step procedure for CCE High Availability Deployment on SBC Edge.

CCE Deployment Scenarios

Following diagram displays the typical CCE Deployment Scenarios:

Image Removed

 

Prerequisites

  1. A public domain name prepared and mapped with your Office 365 tenant.See: Create an Office 365 tenant

  2. An Office 365 tenant with some E5 license or E3 + Cloud PBX. See:  Create an Office 365 tenant.

  3. Have an O365 tenant account with ADMIN privileges that will be used during CCERe-DeploymentSpecificSteps.

  4. A public certificate authority ready to sign a certificate for EDGE FQDN. See  https://technet.microsoft.com/en-us/library/mt605227.aspx,  Information you need to gather before deployment \  Certificate requirements.

  5. A properly configured firewall. See: https://technet.microsoft.com/en-us/library/mt605227.aspx. See https://technet.microsoft.com/en-us/library/mt605227.aspx,  Information you need to gather before deployment \ \ Ports and protocols.

  6. Latest System Release 6.1.0 SBC Firmtware.

  7. Latest System Release 6.1.0 SbcComms Firmware.

  8. MSFT CCE image 1.4.0 on ASM recovery partition.
  9. SBC Edge is already configured with two IP interfaces, one for internal / corporate network, and the second one for external / internet network as shown below:

 

Caption
0Figure
1Pre-configured IP Interfaces

Image Removed

Info

Optionally, if you want to configure a secondary

Spacevars
0product
in your environment, make sure to have the secondary
Spacevars
0product
 network interface is configured accordingly to be able to reach out to CCE's internal / corporate network.

Network Settings

Important Note Regarding the CCE and Microsoft Windows Updates

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 an O365 client >> CCE >> SBC >> ISDN call scenario, INVITE is not reaching the CCE.
  • In an ISDN >> SBC >> CCE >> O365 client call scenario, the CCE Mediation Server returns 503 Proxy INVITE failed. Error: Unable to establish a connection to SBC.

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.

Panel

In this section...

Table of Contents

Before You Start

Prerequisites

  1. A public domain name prepared and mapped with your Office 365 tenant.See Create an Office 365 Tenant.

  2. An entry on your public domain name that points to the fixed IP address of your
    Spacevars
    0product
    .

  3. An Office 365 tenant with an E5 license or E3 + Cloud PBX.

  4. You must have the Global administrator role for your O365 tenant account.

  5. A public certificate authority ready to sign a certificate for the

    Spacevars
    0product
    . See Certificate Requirements at Microsoft Technet.

  6. A properly configured firewall. See Ports and Protocols at Microsoft Technet.

  7. Latest SBC Firmware.

  8. Latest SbcComms Firmware.

  9. Microsoft Cloud Connector Edition image 1.4.1 on the ASM recovery partition.

CCE Deployment Scenarios

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.

 

Caption
0Figure
1CCE Deployment Scenarios

000_Scenarios.png.pngImage Added

 

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 .

 

Noprint

Back to Top

Network Settings

For this best practice, the CCE is deployed For this best practice, CCE deployment is completed in the following network:

Caption
0Figure
1Typical Deployments

Image Modified

 

Image Modified 

Firewall Settings

The In this best practice the router/firewall is configured with the following rules are applied:

Caption
0Table
1Firewall Rules

d Firewall Rules fufw.pngImage Removed

 

Prerequisites

Microsoft defines the multi-site CCE deployment in https://technet.microsoft.com/en-us/library/mt740650.aspx. Based on this article, we will use the following information in our best practice example:

CCE Site FQDNAepsite1.sonusms01.com
CCE-1: Edge Server External IP192.168.211.86 CCE-2 Edge Server External IP192.168.211.81
CCE-1: Edge Server Public IP12.8.245.86 CCE-2: Edge Server Public IP12.8.245.81
CCE-1: Domain Controller IP192.168.210.115 CCE-2: Domain Controller IP192.168.210.121
CCE-1: Central Management Store IP192.168.210.116 CCE-2: Central Management Store IP192.168.210.122
CCE-1: Mediation Server IP192.168.210.117 CCE-2: Mediation Server IP192.168.210.123
CCE-1: Edge Server Internal IP192.168.210.118 CCE-2: Edge Server Internal IP192.168.210.124
SBC-1 FQDN and IP

sbc1.sonusms01.com

192.168.210.113

 SBC-2 FQDN and IP

sbc2.sonusms01.com

192.168.210.125

DNS Settings

Based on above table entries and on our deployment scenario, make sure that CCE FQDN is resolving to both Edge Server PublicIP addresses. To do so, login to your DNS server and create the relevant entries as shown below:

Image Removed

Warning

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 Best Practice for CCE Deployment on SBC Edge.

Re-Initialization of ASM

Both ASMs must be re-initialized with the latest image that contains the latest CCE software (in this example it is 1.4.1 version).

To do so:

  1. login to WebUI of both SBC Edge systems
  2. Under Task (tab), click on Reinitialize (in navigation pane)
  3. Select the appropriate image from the drop-down menu and click Apply as shown below:
ASM-1ASM-2
Image RemovedImage Removed

Upgrade of SBCcomms

Both ASM's must be re-initialized with the latest image that contains the latest CCE software (in this example it is 1.4.1 version).

To do so:

  1. login to WebUI of both SBC Edge systems
  2. Under Task (tab), click on Install ASM Update (in navigation pane)
  3. Using the Choose File button, browse to the latest SBCcomms firmware and click Apply as shown below:
ASM-1ASM-2
Image RemovedImage Removed

ASM Admin Password

Change the Admin Password on both ASM:

  1. login to WebUI of both SBC Edge systems
  2. Under Task (tab), click on Change Admin Password (in navigation pane)
  3. Enter the desired Admin Password twice and click OK as shown below:
ASM-1ASM-2
Image RemovedImage Removed

Node FQDN

  1. login to WebUI of both SBC Edge systems
  2. Under Settings (tab), click on Node-Level Settings (in navigation pane)
  3. Make sure to have host and domain names of the SBCs are configured correctly as shown below:
SBC-1SBC-2
Image RemovedImage Removed

CCE Deployment

ASM Config

  1. login to WebUI of both SBC Edge systems
  2. Under Tasks (tab), click on Setup Cloud Connector Edition (in navigation pane)
  3. Click on ASM Config (tab)
  4. Fill in the IP information as shown below (accordingly with your environment) as shown below:
CCE-1CCE-2
Image RemovedImage Removed

Generate CSR

  1. login to WebUI of one of your SBC Edge systems.
  2. Under Tasks (tab), click on Setup Cloud Connector Edition (in navigation pane)
  3. Click on Generate CSR (tab)
  4. Generate the CSR as shown below with following information. Please note that in this example we are using aepsite1.sonusms01.com and sip.sonusms01.com as common name and SAN as shown below:

Image Removed

Import Certificate Keys

  1. login to WebUI of both SBC Edge systems
  2. Under Tasks (tab), click on Setup Cloud Connector Edition (in navigation pane)
  3. Click on Import Certificate Keys (tab)
  4. Select the certificate Action (in this example we are using Import PKCS12 Certificate and Key selection), enter the password, select the relevant certificate file using Choose File button and click OK as shown below:
CCE-1CCE-2
Image RemovedImage Removed

Configure CCE

  1. ogon to WbUI of both SBC Edge systems
  2. Under Tasks (tab), click on Setup Cloud Connector Edition (in navigation pane
  3. Click on Configure CCE (tab)
  4. Configure all necessary information and click OK as shown below:
CCE-1CCE-2
Image RemovedImage Removed

CCE Configuration.INI file verification and Update

After the step above, several checks and (if needed) corrections are needed in the INI file.

The CCE deployment internally sets the domain suffix as defined under VirtualMachineDomain attribute. Although your SBC may have an FQDN that can be reached from your corporate network, it is important to setup the SBC's Gateway FQDN parameter accordingly with the VirtualMachineDomain value, so that CCE can communicate with SBC without a problem.

In addition, when deploying a High Availability systems, it is important to have Management IP Prefix to be 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.

To verify these values or correct them in Configuration.INI file, follow the steps as shown below:

  1. ON both SBC-1 and SBC-2 webUI > under Configure CCE (tab) click on Click to re-configure CCE application button
  2. Click on OK on the popup
  3. Click on Edit Raw Config button
  4. In CCE Configuration INI File (raw file), verify/correct the values and click OK as shown below:

Image Removed 

Verification of Shared Site Directory on HA Master CCE

Above step creates a shared site directory that both CCE-1 and CCE-2 will use on SBC Edge-1 ASM. To verify that this particular directory is successfully created proceed with the following steps:

  1. Remote Desktop to ASM of the SBC Edge-1 system
  2. Launch the PowerShell
  3. Execute Get-CcSiteDirectory command.
  4. Then using the windows explorer verify that relevant directory exists as shown below:

Image Removed

Prepare CCE

  1. Login to WebUI of both SBC Edge systems
  2. Under Tasks (tab), click on Setup Cloud Connector Edition (in navigation pane)
  3. Click on Prepare CCE (tab)
  4. Click on Prepare CCE button, enter the password for Edge Server External Certificate, and click OK as shown below:
CCE-1CCE-2
Image RemovedImage Removed

Register-CcAppliance

  1. Remote Desktop to ASM of the SBC Edge-1 system
  2. Launch the PowerShell
  3. Execute Register-CcAppliance command for HA Master.
  4. Once the command is executed successfully,  Remote Desktop to ASM of the SBC Edge-2 system
  5. Launch the PowerShell
  6. Execute Register-CcAppliance command again for HA Slave.
ASM-1ASM-2
Image RemovedImage Removed

Verification of Appliances after successful Registration

While on ASM > PoweShell, you may verify the appliances registration by using the O365 Tenant user with Admin privileges (by running series of commands on PowerShell:)

  • Import-Module skypeonlineconnector
  • $cred = Get-Credential

enter the credentials for O365 Admin Tenant

  • $Session = New-CsOnlineSession -Credential $cred -Verbose

Once the login is successful, execute Get-CsHybridPSTNAppliance command on PowerShell as shown below:

Image Removed

Install-CcAppliance on HA Master Node

  1. Remote Desktop to ASM of the SBC Edge-1 system
  2. Launch the PowerShell
  3. Execute Install-CcAppliance command for HA Master as shown below:

Image Removed

Tip

Please note that due to a possible certificate issue, this step may fail! Relevant workaround for this is already covered in:
Best Practice for CCE Deployment on SBC Edge section Best Practice for CCE Deployment on SBC Edge

after fixing the certificate issue, starting the Edge Server Services, and fixing the Virtual Machine Network adapter settings, CCE High Availability Master Node settings completes. Now you need to publish the CcAppliance to proceed with CcAppliance installation on HA Slave Node.

Publish-CcAppliance

  1. Remote Desktop to ASM of the SBC Edge-1 system
  2. Launch the PowerShell
  3. Execute Publish-CcAppliance command as shown below:

Image Removed

Install-CcAppliance on HA Slave Node

  1. Remote Desktop to ASM of the SBC Edge-2 system
  2. Launch the PowerShell
  3. Execute Install-CcAppliance command for HA Slave as shown below:

Image Removed

Tip

Similarly, due to a possible certificate issue, this step may fail as well. Relevant workaround for this is already covered in:
Best Practice for CCE Deployment on SBC Edge section Best Practice for CCE Deployment on SBC Edge

after fixing the certificate issue, starting the Edge Server Services, and fixing the Virtual Machine Network adapter settings, CCE High Availability Slave Node settings completes.

Integration of SBC Edge

Integration of SBC Edge-1 with CCE

  1. login to WebUI of SBC Edge-1 systems
  2. Under Tasks (tab), click on SBC Easy Setup > Easy Config Wizard (in navigation pane)
  3. Follow the steps 1, 2, and 3 as shown below and click Finish
  4. Click OK on the next two popups to complete the setup as shown below:

Image Removed

Above wizard run configures the necessary settings for SBC Edge-1 and CCE integration, which you can see all relevant configuration items in Settings tab as shown below:

Image Removed

Integration of SBC Edge-2 with CCE

  1. login to WebUI of SBC Edge-2 systems
  2. Under Tasks (tab), click on SBC Easy Setup > Easy Config Wizard (in navigation pane)
  3. Follow the steps 1, 2, and 3 as shown below and click Finish
  4. Click OK on the next two popups to complete the setup as shown below:

Image Removed

Above wizard run configures the necessary settings for SBC Edge-2 and CCE integration, which you can see all relevant configuration items in Settings tab as shown below:

Image Removed

Adding Split-DNS entries

To allow SIP communication between the CCE Mediation Server and SBC-Edge, Split DNS entries need to be added on each SBC-Edge systems with the following information:

  1. On SBC-Edge 1, add an entry with DNS Server IP Address as the IP address of CCE-1 AD Virtual Machine's Internal (corporate) IP address and the Domain Name as the the VirtualMachineDomain attribute
  2. On SBC-Edge 2, add an entry with DNS Server IP Address as the IP address of CCE-2 AD Virtual Machine's Internal (corporate) IP address and the Domain Name as the the VirtualMachineDomain attribute

as shown below:

SBCE Edge-1SBCE Edge-2
Image RemovedImage Removed

Adding Mediation Server FQDN entries

Lastly, the Mediation Server FQDNs MUST be added to SIP Server Table and SIP Signaling Group Federated FQDN fields with the following information:

  1. On SBC-Edge 1, add the CCE-2's Mediation Server FQDN into SIP Server Table as well as into SIP Signaling Group Federated IP/FQDN list as shown below:
  2. On SBC-Edge 2, add the CCE-1's Mediation Server FQDN into SIP Server Table as well as into SIP Signaling Group Federated IP/FQDN list as shown below:
SBCE Edge-1SBCE Edge-2
Image RemovedImage Removed

 

 

Used for This Best Practice
Image Added

DNS Settings

Make sure that CCE FQDN is resolving to the

Spacevars
0product
Public IP address. To do so, login to your DNS server and create the appropriate entries.

 

Warning

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.

Noprint

Back to Top

Preparing Your Node

Initial Setup

Tip

For best results:

  • Update the SBC firmware to the latest version.
  • Start with an empty, clean configuration.
Note

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:

Caption
0Figure
1Pre-configured IP Interfaces

Image Added

Caption
0Figure
1Ensure That the Node's FQDN is Correct

nls1.pngImage Added nls2.pngImage Added

Info
titleOptional

When configuring a secondary

Spacevars
0product
in your environment, make sure to have the secondary
Spacevars
0product
network interface is configured accordingly to be able to reach out to CCE's internal/corporate network.

Preparing the ASM

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.

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of the
Spacevars
0product
.
2Click the Task tab, and then click Opreational Status.
3

Verify that:

  • The ASM Board Status is Up
  • The appropriate Service Status is Running
  • The Service is the latest version. If the service version (SBC Communications Service) is not the latest, update it by following the steps in Installing an ASM Package.

 

Caption
0Figure
1Operational Status

002_Opstat.pngImage Added

4

Change the ASM Admin password:

    1. Login to WebUIof both SBC Edge systems
    2. Click the Task tab and then click Change Admin Password.
    3. Enter the desired password twice and then click OK.

 

Caption
0Figure
1Change Admin Password

ASM-1 and ASM-2

pwdchange.pngImage Added

Noprint

Back to Top

Deploying the CCE

Deploying CCE 1.4.1 on the

Spacevars
0product
consists of two steps:

  1. Setup CCE using the
    Spacevars
    0product
    WebUI.
  2. Excute PowerShell commands/run tasks on the
    Spacevars
    0product
    ASM.

 

Note
titleImportant!
  • If this is a re-deployment of a CCE deployment, complete the steps in Redeploying the CCE to clean up previously entered data in O365 before proceeding with the following section.

 

Anchor
Configuring the CCE Through the WebUI
Configuring the CCE Through the WebUI
Configuring the CCE Through the WebUI

Configuring the ASM

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1

Login to the WebUI of both

Spacevars
0product
.

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.

 

CCE-1

Image Added

 

CCE-2

Image Added

4

Click Apply. After receiving the activity status as successfully completed, click the Generate CSR tab.

Generating the CSR

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.

 

Note

Perform these steps on only one of the

Spacevars
0product
systems.

Step Action
1Login to the WebUI of one of the
Spacevars
0product
.
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 .

 

Caption
0Figure
1Generate CSR

Image Added


Noprint

Back to Top

Importing Certificate/Keys

Note

Perform these steps on both

Spacevars
0product
systems.

Step Action
1Login to the WebUI of both
Spacevars
0product
.
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:

  • If you generated a Certificate Request (CSR) in the previous section, select the Import X.509 Signed Certificate option using the Choose File button
  • If you prepare your certificate by yourself, select the Import PKCS12 Certificate and Key option using the Choose File button

 

CCE-1

Image Added

 

CCE-2

Image Added

4Click OK.
5
  • On SBC-1, select the certificate Action, use Export PKCS12 Certificate and Key, enter the password, and then click OK.
  • On SBC-2, select the certificate Action, use Import PKCS12 Certificate and Key to import the pkcs certificate you exported on SBC-1, enter the password, select the relevant certificate file using the Choose File button and then click OK.

 

Anchor
Configuring the CCE
Configuring the CCE
Configuring the CCE

 

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of the
Spacevars
0product
.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Configure CCE tab.
4

Configure all necessary information and then click OK as shown below:

CCE-1

Image Added

 

CCE-2

Image Added

5 After receiving the activity status as successfully completed, click the Prepare CCE tab to continue.

 

 

Warning

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 SBC Edge fqdn for this site before proceeding.

Noprint

Back to Top

Verifying and Updating the  CCE Configuration INI File 

You must verify (and possibly correct) the CCE Configuration INI File after configuring the CCE.

Info

The CCE deployment internally sets the domain suffix as defined under VirtualMachineDomain attribute. Although your

Spacevars
0product
may have an FQDN that can be reached from your corporate network, it is important to set up the SBC's Gateway fqdn parameter accordingly with the VirtualMachineDomain value, so that the CCE can communicate with the 
Spacevars
0product
without a problem.

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.

Note

Perform these steps on both

Spacevars
0product
systems.


Follow these steps to verify and correct values in the  CCE Configuration INI File.


Note

Perform these steps on both

Spacevars
0product
systems.


StepAction
1Login to the WebUI of the
Spacevars
0product
.
2Click the Configure CCE tab and then click Click to re-configure CCE application.
3Click OK on the popup dialog box.
4Click the Edit Raw Config button.
5

Verify/correct the values in the CCE Configuration INI File and then click OK.

Caption
0Figure
1CCE Configuration.INI File Verification and Update

Image Added



Preparing the CCE

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of both
Spacevars
0product
.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Prepare CCE tab.
4

Click the Prepare CCE button, enter the password for Edge Server External Certificate, and then click OK:

CCE-1

Image Added

 

CCE-2

Image Added

5

To complete the deployment, continue with Manually Configuring the CCE on the ASM.

Noprint

Back to Top

Anchor
Manually Configuring the CCE on the ASM
Manually Configuring the CCE on the ASM
Manually Configuring the CCE on the ASM

 

Manually deploying CCE on the ASM requires:

  • Registering the CCE Appliance

  • Installing the CCE Appliance

 

Registering the CCE Appliance

 

Note

Perform these steps on only one of the

Spacevars
0product
systems.

Step

Action

1

Remote desktop to the ASM of the

Spacevars
0product
System 1.

2

Launch PowerShell.

3

Execute the following commend for HA Master:

Register-CcAppliance

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

Spacevars
0product
System 2.

7

Launch PowerShell.

8

Execute the following commend for the HA Slave, and enter the appropriate password(s) when prompted:

Register-CcAppliance


ASM-1

Image Added

 

 

ASM-2

Image Added

Noprint

Back to Top

Install-CcAppliance on the HA Master Node

 

Step

Action

1

Remote desktop to the ASM of the

Spacevars
0product
System 1.

2

Launch PowerShell.

3

Execute the following command for the HA Master, and enter the appropriate password(s) when prompted:

Install-CcAppliance

Publish-CcAppliance

StepAction
1Remote desktop to the ASM of the
Spacevars
0product
System 1.
2Launch PowerShell.
3

Execute the following command, and enter the appropriate password(s) when prompted:

Publish-CcAppliance

 

016_PUBLISH -cCaPPLIANCE.pngImage Added

 

Install-CcAppliance on the HA Slave Node

StepAction
1

Remote desktop to the ASM of the

Spacevars
0product
System 2.

2Launch PowerShell.
3

Execute the following command for the HA Master, and enter the appropriate password(s) when prompted:

Install-CcAppliance

 

Image Added

 

Integrating SBC Edge With CCE

After the CCE is deployed, integrate the

Spacevars
0product
and allow calls from/to O365 clients. In this example, the following steps will set up the 
Spacevars
0product
for:

 

SIP Provider (193.168.210.103) – SBC Edge (193.168.210.125)  – CCE (mediation Server: 193.168.210.123) – O365 Cloud

Building Your SBC Edge-1 Configuration

StepAction
1Login to the WebUI of
Spacevars
0product
-1.
2Navigate to Tasks > SBC Easy Setup and then click the Easy Configuration Wizard.
3

Follow steps 1, 2, and 3 as shown in the following figure and then click Finish.

 

Caption
0Figure
1Easy Configuration Steps 1-3

ec1.pngImage Added

 

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 as shown below:

 

Caption
0Figure
1Post-Wizard Configuration

settinsg1.pngImage Added

Noprint

Back to Top

Building Your SBC Edge-2 Configuration

 

StepAction
1Login to the WebUI of
Spacevars
0product
-2.
2Navigate to Tasks > SBC Easy Setup and then click the Easy Configuration Wizard.
3

Follow steps 1, 2, and 3 as shown in the following figure and then click Finish.

 

Caption
0Figure
1Easy Configuration Steps 1-3

ec2.pngImage Added

 

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 as shown below:

 

Caption
0Figure
1Post-Wizard Configuration

settinsg2.pngImage Added

 

Adding Mediation Server FQDN Entries

The Mediation Server FQDNs must be added to SIP Server Table and SIP Signaling Group Federated FQDN fields with the following information:

  1. On SBC-Edge 1, add the CCE-2's Mediation Server FQDN into SIP Server Table as well as into SIP Signaling Group Federated IP/FQDN list as shown below:
  2. On SBC-Edge 2, add the CCE-1's Mediation Server FQDN into SIP Server Table as well as into SIP Signaling Group Federated IP/FQDN list as shown below:

 

Caption
0Figure
1Mediation Server FQDNs

Image Added


MediationServerFQDNentries2.pngImage Added

Noprint

Back to Top

O365 Known Issue and Workarounds for CCE

Redeploying the CCE

Re-Initializing the ASM

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).

 

StepAction
1Login to the WebUI of both
Spacevars
0product
systems.
2Navigate to the Tasks tab and then click Reinitialize.
3

Select the appropriate image from the drop-down menu and click Apply as shown below:

 

Caption
0Figure
1Tasks

reinit.pngImage Added

 

reinit.pngImage Added

 

 

Clean the Office 365 Tenant

If the CCE was previously deployed, previously installed information must be cleared in O365. To do so, follow the steps below.

 

StepAction
1

Remote desktop to the ASM system.

2Launch PowerShell.
3

Execute the following command:

 

Import-Module skypeonlineconnector
$cred = Get-Credential

 

4

 When prompted, enter the credentials for O365 Admin Tenant.

 

Caption
0Figure
1O365 Admin Tenant

Image Added

5

Execute the following command:

 

$Session = New-CsOnlineSession -Credential $cred -Verbose
Import-PSSession $session

 

Caption
0Figure
1Sessions

Image Added

 

Image Added

6

To remove the current appliance, run the following command and copy the Identity into your clipboard:

 

Get-CsHybridPSTNAppliance

 

Caption
0Figure
1Remove Appliance

Image Added

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
9This completes the cleanup. Continue to Configuring the CCE 

Noprint

Back to Top

...