Versions Compared

Old Version 5

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Automatic update to correct links

...

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSYM-2226924215
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c87d0111, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

 

Excerpt Include
Not_for_SWe
Not_for_SWe
nopaneltrue

 

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.

info
Panel

In this section...

Table of Contents
maxLevel

3

titleImportant 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 Skype for Business 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

Image Removed

 

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 in the following network:

Caption
0Figure
1Typical Deployments

Image Removed

 

Image Removed

Firewall Settings

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

Caption
0Table
1Firewall Rules Used for This Best Practice
Image Removed

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.

 

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 Removed

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

Image Removed

Image Removed
 

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

 

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.

 

 

Deploying the CCE

Deploying CCE 1.4.1 on the

Spacevars
0product
consists of two steps:

...

Spacevars
0product

...

Spacevars
0product

...

 

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.

 

...

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.

4

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

CCE-1

Image Removed

 

CCE-2

Image Removed

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.

...

Spacevars
0product

...

Navigate to Tasks > Setup Cloud Connector Edition > Generate CSR.

...

Note

SBC Edge supports new deployment with CCE 2.1.0 in Release 6.1.5.

Before this release, if your CCE auto-updates to CCE 2.1.0:

  • To rerun the step “Transfer Credential from SBC”, it will require Release 6.1.5.
  • To rerun the step “Register Appliance”, you need to install .NET4.6.2 using Windows Update.
Info

For details on troubleshooting, see Troubleshooting Cloud Connector 6.1.2.

Multiexcerpt include
MultiExcerptNameBeforeYouStart
PageWithExcerptConfiguring the SBC Edge for a Single CCE

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 .

Multiexcerpt include
MultiExcerptNamePreRequisites
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Network Settings

Note

We recommend deploying both Appliances on the same subnet with a resilient connection.

For the purposes of this document, the CCE is deployed in the following network:

Caption
0Figure
1Typical Deploments

Image Added 

 

Image Added

 

Firewall Settings

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

Caption
0Table
1Internal Firewall Rules for CCE

Source IP

Destination IP

Source Port

Destination Port

Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117

Internal clients

TCP 49 152 – 57 500*

TCP 50,000-50,019 (Optional)

Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117

Internal clients

UDP 49 152 – 57 500*

UDP 50,000-50,019

Internal clients

Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117

TCP 50,000-50,019

TCP 49 152 – 57 500*

Internal clients

Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117

UDP 50,000-50,019

UDP 49 152 -57 500*



Caption
0Table
1External Firewall Rules for CCE

Source IP

Destination IP

Source Port

Destination Port

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

Any

TCP 5061

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

Any

TCP 80

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

Any

UDP 53

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

Any

TCP 53

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

TCP 50,000-59,999

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

UDP 3478

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

UDP 50,000-59,999

Any

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

TCP 5061

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

TCP 443

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

TCP 50,000-59,999

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

UDP 3478

Any

Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86

Any

UDP 50,000 - 59,99



Caption
0Table
1Host Firewall Rules - Internal or External Access
Source IP Destination IPSource PortDestination Port
ASMAnyAnyTCP 53
ASMAnyAnyTCP 80
ASMAnyAnyTCP 443
Multiexcerpt include
MultiExcerptNameDNSSettings
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Preparing Your Node

Preparing the SBC Edge for Initial Setup

Update the SBC Edge firmware to the latest release version.

Note
  • Ensure the Node FQDN is definitive. Changing this information requires the CCE to be redeployed.
  • Ensure that an NTP server is configured.

Sonus recommends starting with a clean and empty configuration.

 

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

Image Added

Image 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 SBC Edge.
2Click the Task tab, and then click Operational 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.

 

4

Change the ASM Admin password:

    1. Login to WebUI of 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.

 

Deploying the CCE

Deploying the CCE on the

Spacevars
0product
consists of two steps:

  1. Prepare the CCE deployment on the SBC Edge using the section below.
  2. Using Sonus Cloud Link Deployer via Remote Desktop on the ASM Module:
    1. Register all the CCE appliances.
    2. Install and publish the CCE Appliance Master.
    3. Install the CCE Appliance Slave.
Note
  • 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 each SBC Edge.

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.

Caption
0Figure
1Configuring the ASM – CCE-1

Image Added

Caption
0Figure
1Configuring the ASM – CCE-2

Image Added

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

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 .

 

 

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

 

...

 

Note

Perform these steps on both

Spacevars
0product
systems.

.Open the Tasks tab and click in the navigation pane
StepAction Action
1Login to the WebUI of one of the SBC Edge systems.
2
Spacevars
0product
2

Navigate to Tasks >

Setup Cloud Connector Edition

 > Generate CSR.

3Click the Configure CCE tab.
4

Configure all necessary information and then click OK.

CCE-1

Image Removed

 

CCE-2

Image Removed

 

5After 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.

 

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.

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
 

Importing Certificate/Keys

Note

Perform these steps on both

Spacevars
0product
systems.

Step Action
1Login to the WebUI of each SBC Edge.
2

Navigate to Tasks > Setup Cloud Connector Edition and then click the Certificate and Key tab.

3

On SBC-1, click the Action drop-down list and select the appropriate option:

  • Import X.509 Signed Certificate. If you generated a Certificate Request (CSR) on the previous step, select the Import X.509 Signed Certificate option, and paste the BASE64 certificate in the text box.
  • Import PKCS12 Certificate and Key. If you prepare your certificate by yourself, select the Import PKCS12 Certificate and Key option, enter a password and select the relevant certificate file.
  • Export PKCS12 Certificate and Key. To export a certificate, select ExportPKCS12 Certificate and Key and enter a password.
  • Import PKCS7 Certificate Chain. Select the Import PKCS7 Certificate Chain option, and select a file.

On SBC-2 select the certificate action applicable. For example, use Import PKCS12 Certificate and Key to import the pkcs certificate you exported on SBC-1, enter the password, select the relevant certificate file.

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 each SBC Edge.
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.

 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Added

 

Caption
0Figure
1Configuring the ASM – CCE-2

Image Added

 

 

 

Note: Enterthe 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.

5After 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 and the Edge Server Public Hostname are correct before proceeding.

Verifying and Updating the CCE Configuration INI File 

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

Info

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.

StepAction
1Login to the WebUI of each SBC Edge.
2Click the Configure CCE tab and then click Click to re-configure CCE application.
3Click OK on the popup dialog box.
4

Click the Raw (INI) Config drop-down list, and select an option:

  • Edit. Configurable fields are displayed for editing. Modifications to the CCE configuration requires redeployment of the CCE VM, and this action takes approximately two hours.
  • Export. Exports the .ini file.
  • Import. Imports the .ini file.
5

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


Preparing the CCE 
Anchor
Preparing the CCE
Preparing the CCE

Note

Perform these steps on both

Spacevars
0product
systems.

StepAction
1Login to the WebUI of each SBC Edge.
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. A confirmation will request you to enter the password again for the new password. Only the Tenant credentials are already existing. The same password should be used on all Appliances in the site. Click OK as shown below.

5

To complete the deployment, continue with Activating the CCE.

Info

If you receive this error message:

Code Block
Additional Information: Got an exception deploying CCE: Certificate Chain is broken. Root and Intermediate Certificate needs to be imported on ASM Operating System: A certificate chain could not be built to a trusted root authority.

...refer to Manually Loading the Root and Intermediate Certificates on the CCE

 

Activating the CCE

This step stores the Microsoft product keys, and activates the CCE VM (which is not yet activated)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.

...

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.

5

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

 

...

systems.

Info

Each CCE requires four VMs; each Microsoft Product Key activates two VMs.

StepAction
1Login to the WebUI of each SBC Edge.
2Open the Tasks tab and click Setup Cloud Connector Edition in the navigation pane.
3Click the Activate CCE tab.
4

In Domain Controller and Central Management Store VM > Windows Product Key 1, enter the first Microsoft Product Key. To identify the Product Key, see Identify Microsoft Product Key.

5In Under Mediation Server and Edge Server VM > Windows Product Key 2, enter the second Microsoft Product Key. To identify the Product Key, see Identify Microsoft Product Key.
6Click Activate.
7Access Tasks> Operational Status to verify Windows Activation.
8

To complete the deployment, continue with installing the Installing the CCE Appliance using Sonus Cloud Link Deployer.

Caption
0Figure
1Activate the CCE

 Image Added

Info
titleIdentify Microsoft Product Key

Anchor
ProductKey
ProductKey
To identify the Microsoft Product Key:

  1. Access the bottom of the SBC unit and locate the two Microsoft Certificate of Authenticity stickers.
  2. Locate the Microsoft Product Key for each.

    Sample Microsoft Certificate of Authenticity Sticker
    Image Added
Info
titleActivation - Troubleshooting Tips

Anchor
Troubleshooting
Troubleshooting
If activation fails, check the following:

  • If access to the Microsoft Server fails, verify IP and Firewall configuration. 
  • Verify each Product Key has not reached the allowed limit of 15 activations.
  • Verify correct entry of the Product Key.

Anchor
InstallingtheCCEAppliance
InstallingtheCCEAppliance
Installing the CCE Appliance using Sonus Cloud Link Deployer

Note
titleCCE Deployment - Using a Proxy on the ASM Host

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 and specify proxy settings per machine rather than per user.

Note
titleCCE Deployment - What to Expect
  • The CCE deployment may exceed two hours.
  • The CCE deployment status is visible only on the Remote Desktop to the ASM. The WebUI indicates that the CCE is running while the deployment process is in progress.
  • While the CCE deployment is running, you should not perform any actions on the ASM via the WebUI (i.e., Shut Down/Reset/Reboot/Reinitialize/Install etc.).
  • If the Office 365 PSTN Site already exists in your tenant, ensure the other Appliance is removed, and the CCE Auto-Update time window is properly configured. If you are in a time window dedicated to the Auto-Update, you should use the command Set-CsHybridPSTNSite to set EnableAutoUpdate to $False. Replication of the information may take up to 30 minutes.

Using Sonus Cloud Link Deployer via Remote Desktop on the ASM Module:

  1. Register all the CCE Appliance.
  2. Install and publish the CCE Appliance Master.
  3. Install the CCE Appliance Slave.

Registering the CCE Appliance

Note

Perform these steps on only one of the

Spacevars
0product
systems.

 

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

 

Install-CcAppliance on the HA Master Node

...

Step

Action

1

Remote desktop to the ASM of the

Spacevars
0product
SBC Edge System 1.

2

Launch PowerShellthe Sonus Cloud Link Deployer from icon on the desktop.

3

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

Install-CcAppliance

Publish-CcAppliance

Check the first two actions:

  • Transfer Password from SBC: This step imports the password that has been set during the Preparing the CCE.
  • Register Appliance: This step registers this new appliance on your Ofiice365 tenant.
4Click Apply.
5

After successful execution, remote

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

 

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

 

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

...

2.

6

Launch the Sonus Cloud Link Deployer from icon on the desktop.

7

Check the first two action.

  • Transfer Password from SBC: This step imports the password that has been set during the Preparing the CCE.
  • Register Appliance: This step registers this new appliance on your Ofiice365 tenant.
8Click Apply.

Caption
0Figure
1Registering the CCE Appliance - Master

 Image Added

Caption
0Figure
1Registering the CCE Appliance - Slave

Image Added
 

 

Install-CcAppliance on the HA Master Node

Step

Action

1Login

Remote desktop to the

WebUI of
Spacevars
0product
-

ASM of the SBC Edge System 1.

2Navigate 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.

 

Noprint

Back to Top

Building Your SBC Edge-2 Configuration

Launch the Sonus Cloud Link Deployer from icon on the desktop.
3

Check the last two actions:

  • Install Appliance: This step deploys the CCE.
  • Publish Appliance (HA Only): This will extract the required information from the HA Master
4Click Apply.

Caption
0Figure
1Install CcAppliance on HA Master Node


 Image Added

 

Install-CcAppliance on the HA Slave Node

...

StepAction
1Login

Remote desktop to the

WebUI of
Spacevars
0product
-

ASM of the SBC Edge System 2.

2Navigate 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.

 

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:

...

0Figure
1Mediation Server FQDNs
Launch the Sonus Cloud Link Deployer from icon on the desktop.
3

Check the third action:

  • Install Appliance: This step deploys the CCE.
4Click Apply. The Installation time depends on the bandwidth between the Master and the Slave.
5After configuring the SBC Edge for CCE, refer to Managing Your Office 365 Tenant to configure CCE update time and user.

Caption
0Figure
1Install CcAppliance on the HA Slave Node

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 SBC Edge-1.
2Navigate 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.

Caption
0Figure
1Building your SBC Edge-1 Configuration

Image Added

 

Building Your SBC Edge-2 Configuration

StepAction
1Login to the WebUI of SBC Edge-2.
2Navigate 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.

 

 

Caption
0Figure
1Building your SBC Edge-2 Configuration

Image Added

 

Multiexcerpt include
MultiExcerptNameBasicCallVerification
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Multiexcerpt include
MultiExcerptNameO365KnownIssues
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Image Removed

MediationServerFQDNentries2.pngImage Removed

...

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.

 

 

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.

 

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

 

Updating the CCE Password

Follow these steps if the CCE deployment cannot open the PFX certificate due to a password mismatchyou need to update the O365 tenant admin password or account.

Use the PowerShell commands Install-CcAppliance -UpdateAllCredentials and Set-CcCredential -AccountType TenantAdmin
StepAction
1

Re-perform the steps in Preparing the CCE to specify a new Password for the PFX file.

On the WebUI, click Tasks and select the Prepare CCE tab (see Preparing the CCE).
2Click Prepare CCE.
3From the Password Setting drop down list, select Change Password. Keep the same passwords for the Edge Server, CCE Service and CA Backup File, but change the passwords for Tenant Account User and Tenant Account Password.
4

On Remote desktop, start the Sonus Cloud Link Deployer, and check Transfer Password from SBC

2

to reset the credentials.