Versions Compared

Old Version 10

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 11

changes.mady.by.user Ribbon Communications

Saved on

Key

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

...

Note

Perform these steps on both

Spacevars
0product
systems.

Note

If you configure TLS and downgrade the system to a release prior to Release 7.0, the Exchange CA Certificate for TLS will be unavailable; you must re-deploy or upgrade to Release 7.0. Along with TLS configuration on the CCE, the TLS capability requires a loaded Root CA certificate and a signed certificate on the SBC.

StepAction
1Login to the WebUI of the SBC Edge.
2Navigate to Tasks  > Office 365 Cloud Connector Edition> Setup.
3Click the Configure CCE tab.
4

Configure all necessary information and then click OK.

 

Caption
0Figure
1Configuring the ASM – CCE-1

Image Removed

Caption
0Figure
1Configuring the ASM – CCE-2

Image Removed

 

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

...

Note

TLS 1.2 is supported; the following fields are required to configure TLS:

  • Primary SBC Transport Protocol. Options: TCP or TLS (supports TLS 1.2).
  • Secondary SBC Transport Protocol (optional). Options: TCP or TLS (supports TLS 1.2).

If TLS is configured as the Primary SBC Transport Protocol, you must run the Synchronize CCE/SBC CA Certificate task to allow a successful TLS handshake between CCE and SBC Edge. However, if TCP is configured as the Primary SBC Transport Protocol the Synchronize CCE/SBC CA Certificate task is not mandatory. See Managing Cloud Connector Edition Private Certificates.

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


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

StepAction
1Login to the WebUI of both the SBC Edge systems.
2Navigate to Tasks  > Office 365 Cloud Connector Edition> Setup.
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. 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.

...

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

Info

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

StepAction
1Login to the WebUI of each both SBC Edge systems.
2Navigate to Tasks  > Office 365 Cloud Connector Edition> Setup.
3Click the Cutomize CCE VMs 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.
6From the Proxy Usage drop down list, select Enabled (enables the Proxy Server on the DMZ facing the internal network) If you select Disable, the Proxy Server is disabled.
7In the Proxy Server IP Address field, enter the server IP address for the Proxy Server in IPv4 format. This field is available only when Proxy Usage is set to Enabled.
8In the Proxy Server Port field, enter the port number for the Proxy Server. Valid entry: 1 - 65535. This field is available only when Proxy Usage is set to Enabled.
9Click Apply.
10Access Tasks> Operational Status to verify Windows Activation. If activation fails, see Troubleshooting.
11

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

 

 

Caption
0Figure
1Activate the CCE

 Image Removed

...

titleIdentify Microsoft Product Key

...

titleActivation - Troubleshooting Tips

...

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

Set CCE Private Certificate

This step synchronizes the CCE and SBC CA Certificate, or Renews the CCE CA or CCE Certificate.

Info

This feature applies to SBCs running ASM with the Office 365 Cloud Connector Edition image.

Note

If you configure TLS and downgrade the system to a release prior to Release 7.0, the Exchange CA Certificate for TLS will be unavailable; you must re-deploy or upgrade to Release 7.0. Along with TLS configuration on the CCE, the TLS capability requires a loaded Root CA certificate and a signed certificate on the SBC.

Note

These instructions assume the SBC Edge already includes a valid Trusted CA (which issues the Sonus SBC Certificate).  For more information, refer to Working with Certificates.

You will not be able to complete Step 4: Synchronize CCE/SBC CA Certificate without a valid Trusted CA in SBC Edge.

...

For SBC-1: three options are available, when needed:

  • Synchronize CCE/SBC CA Certificate. Synchronizes the CCE/SBC CA certificate; certificate information is exchanged between the CCE and SBC CA.
  • Renew CCE CA Certificate. Renews CCE CA certificate.
  • Renew CCE Certificate. Renews the CCE certificate.

Note: The CCE CA and CCE Certificates are valid for two years.

...

For SBC-2: three options are available, when needed:

  • Synchronize CCE/SBC CA Certificate. Synchronizes the CCE/SBC CA certificate; certificate information is exchanged between the CCE and SBC CA.
  • Renew CCE CA Certificate. Renews CCE CA certificate.
  • Renew CCE Certificate. Renews the CCE certificate.

...

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

Click the Prepare CCE tab.
4

Click the Prepare CCE button. Enter the requested password. A confirmation will request you to enter the password again. 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.

Anchor
Activating
Activating
Customizing the CCE VM

This step stores the two Microsoft product keys, and customizes 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.
2Navigate to Tasks  > Office 365 Cloud Connector Edition> Setup.
3Click the Cutomize CCE VMs 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.
6From the Proxy Usage drop down list, select Enabled (enables the Proxy Server on the DMZ facing the internal network) If you select Disable, the Proxy Server is disabled.
7In the Proxy Server IP Address field, enter the server IP address for the Proxy Server in IPv4 format. This field is available only when Proxy Usage is set to Enabled.
8In the Proxy Server Port field, enter the port number for the Proxy Server. Valid entry: 1 - 65535. This field is available only when Proxy Usage is set to Enabled.
9Click Apply.
10Access Tasks> Operational Status to verify Windows Activation. If activation fails, see Troubleshooting.
11

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

See Managing Cloud Connector Edition Private Certificates for the following setup options:

  • Synchronize the CCE and SBC CA Certificate
  • Renew the CCE CA or CCE Certificate

Caption
0Figure
1SBC 1 - CCE Private Certificate

Image Removed 

Caption
0Figure
1SBC 2 - CCE Private Certificate
Image Removed 

Anchor
Manually Configuring the CCE on the ASM
Manually Configuring the CCE on the ASM
Installing the CCE Appliance using Sonus Cloud Link Deployer

...

titleCCE Deployment - Using a Proxy on the ASM Host

CCE on the ASM
Installing the CCE Appliance using Sonus Cloud Link Deployer

 

...

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 $Falsesee Managing Update Schedule and Creating and Modifying PSTN Hybrid Site to configure the PSTN Hybrid Site and configure Auto-Update to false. Replication of the information may take up to 30 minutes.

...

 

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