Versions Compared

Old Version 18

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.

...

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHSYM-2433127627
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}

Excerpt Include
UXDOC61:Not_for_SWe
UXDOC61: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.

Panel

In this section...

Table of Contents
maxLevel2

Note

SBC Edge now supports a new deployment with CCE 2.1.0 in release 7.0.1.

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

  • To rerun the step “Transfer Credential from SBC”, it will require 7.0.1.

shown. Failure to do so increases the risk of node failure.

Panel

In this section...

Table of Contents
maxLevel2

Info

For details on troubleshooting, see Troubleshooting Cloud Connector.

...

 

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

Image Modified

Image Modified
 

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.

...

Note

Perform these steps on both

Spacevars
0product
systems.

 
StepAction 
1

Login to the WebUI of each SBC Edge.

 
2

Navigate to Tasks  > Office 365 Cloud Connector Edition> Setup.

 
3

Click the ASM Config tab and configure/verify the Network and IP settings of your ASM as shown below.

4From the Remote Desktop Enabled drop down list, select Yes (to enable Remote Desktop) or No (to disable Remote Desktop). 
5From the Windows Firewall Enabled drop down list, select Yes (to enable Windows Firewall) or No (to disable Windows Firewall). 
6From the Proxy Enabled drop down list, Enables use of the Proxy Server on the ASM. Select from the drop down list: Yes (enables Proxy Server on the ASM) or No (disables Proxy Server). 
7From the Proxy Address drop down list, select Yes (to enable the IP address for the Proxy Server in IPv4 format). This field is available only when Proxy Enabled is set to Yes. 
8From the Proxy Port drop down list, select Yes (to enable the port in which the Proxy Server connects). Valid entry: Valid entry: 1 - 65000. This field is available only when Proxy Enabled is set to Yes. 
9Configure/verify the Network and IP settings of your ASM. 
10

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


 

 
Caption
0Figure
1Configuring the ASM – CCE-1

Image Modified

Caption
0Figure
1Configuring the ASM – CCE-2

Image Modified

Generating the CSR

...

Caption
0Figure
1Generate CSR

Image Modified 

Set CCE Public Certificate

...

Caption
0Figure
1SBC 1 - CCE Public Certificate

Image Added
Image Removed 

Caption
0Figure
1SBC 2 - CCE Public Certificate

Image RemovedImage Added

 

Anchor
Configuring the CCE
Configuring the CCE
Configuring the CCE

...

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

Any changes to the Configure CCE tab requires the CCE to be redeployed.

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.

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 RemovedImage Added

Caption
0Figure
1Configuring the ASM – CCE-2

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

5

To increase Fast Failover (which shortens the time where certain ported numbers have a long delay from ITSP PSTN provider) configure Trunk Information:

Refer Support. Indicates whether Gateways support Refer for a Call Transfer scenario. Valid entries: Enable (the Gateway(s) supports Refer which can handle call transfer) or Disable (the Gateway does not support Refer and the Mediation Server handles call transfer).

Fast Failover Timer. Determines whether outbound calls that are not answered by the gateway within ten seconds will be routed to the next available trunk; if there are no additional trunks, the call will automatically be dropped. Valid entries: Enable or Disable.

Forward Call History. Indicates whether call history information is forwarded through the trunk. Valid entries: Enable or Disable.

Forward PAI. Indicates whether the P-Asserted-Identity (PAI) header will be forwarded along with the call. Valid entries: Enable or Disable.

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

...

 

Caption
0Figure
1Activate the CCE

 Image RemovedImage 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

...

Step

Action

1

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

2

Launch the

Spacevars
0company
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

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

Install-CcAppliance on the HA Master Node

Step

Action

1

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

2Launch the
Spacevars
0company
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.

...

0Figure
1Install CcAppliance on HA Master Node
  • HA Master.
4Click Apply.

...

 

Install-CcAppliance on the HA Slave Node

StepAction
1

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

2Launch the
Spacevars
0company
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.

...

0Figure
1Install CcAppliance on the HA Slave Node

...

 

Integrating SBC Edge With CCE

...

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 Removed

 

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.

 

...

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

On Remote desktop, start the

Spacevars
0company
Cloud Link Deployer, and check Transfer Password from SBC to reset the credentials.