Versions Compared

Old Version 12

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=8a00a0c85b2726c2015b58aa779d00038a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSYM-2302224215
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d00038a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c98a00a02355cd1c2f0155cd26c87d0111, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

...

Panel

In this section...

Table of Contents
maxLevel23

Note

SBC Edge supports new deployment with CCE 2.1.0 in Release

Info

For details on troubleshooting, see Troubleshooting Cloud Connector 6.1.25.

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
Multiexcerpt include
MultiExcerptNameBeforeYouStart
PageWithExcerptConfiguring the SBC Edge for a Single CCE

...

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.

...

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:

...

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.

...

StepAction
1

Login to the WebUI of both 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 RemovedImage Added

Caption
0Figure
1Configuring the ASM – CCE-2

Image RemovedImage Added

Generating the CSR

...

Step Action
1Login to the WebUI of one of the SBC Edge systems.
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
 

Importing Certificate/Keys

...

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

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

35

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) in on the previous sectionstep, select the Import X.509 Signed Certificate option using the Choose File button., 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 using the Choose File button.
4Click OK.
  • , enter a password and select the relevant certificate file.
  • On SBC-1, select the certificate Action, use Export PKCS12 Certificate and Key. To export a certificate, enter the password, and then click OK.On SBC-2, select the certificate Actionselect 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

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, using the Choose File button 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 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 Modified

 

Caption
0Figure
1Configuring the ASM – CCE-2

Image Modified

 

 

 

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  the CCE Configuration INI File 

...

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

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

...

StepAction
1Login to the WebUI of both each SBC Edge systems.
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 requested password. 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 Manually Configuring the CCE on the ASM.

 

...

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

Note

Perform these steps on both

Spacevars
0product
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 your 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. You should be outside of a maintenance time window for the installationIf 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:

...

Step

Action

1

Remote desktop to the ASM of the SBC Edge System 1.

2

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

3

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 desktop to the ASM of the

Spacevars
0product
System 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
Image Removed 

 

Install-CcAppliance on the HA Master Node

...

Caption
0Figure
1Install CcAppliance on HA Master Node


 Image RemovedImage Added

 

Install-CcAppliance on the HA Slave Node

StepAction
1

Remote desktop to the ASM of the SBC Edge System 2.

2Launch 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
Image Removed 

 

Integrating SBC Edge With CCE

...

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

 

Multiexcerpt include
MultiExcerptNameBasicCallVerification
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Multiexcerpt include
MultiExcerptNameO365KnownIssues
PageWithExcerptConfiguring the SBC Edge for a Single CCE

Updating the CCE Password

Follow these steps if you need to update the O365 tenant admin password or account.

StepAction
1On 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 the WebUI, run Preparing the CCE to specify a new Password. Select the existing password and enter the new password. Only the O365 should be modified for a running instance of CCE.2

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