You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

 

READ BEFORE BEGINNING

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

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.

 

 

In this section....

This page provides a step-by-step procedure for CCE High Availability Deployment on SBC Edge.

Before You Start

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

 

CCE Deployment Scenarios


 

Scenario 3 and Scenario 4 are covered in Configuring the SBC Edge for Two CCEs. This document contains steps for Scenario 1 and Scenario 2 deployments.

Prerequisites

Prerequisites

1A public domain name prepared and mapped with your Office 365 tenant. See Create an Office 365 Tenant.
2An entry on your public domain name that points to the fixed IP address of your
Unable to show "metadata-from": No such page "_space_variables"
.
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

Unable to show "metadata-from": No such page "_space_variables"
.

Important

 Complete the steps outlined in Certificate Requirements at Microsoft Technet.

6

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

7

Latest System Release SBC Firmware.

Important
  • Refer to the SBC Edge Release Information page for instructions on obtaining the latest firmware.
  • Failure to update to the latest firmware could lead to deployment failure.
  • Make sure to use the latest sustaining release (use X.X.459 rather than X.X.0, for example).
8

Latest System Release SbcComms Firmware.

Important
  • Refer to the SBC Edge Release Information page for instructions on obtaining the latest firmware.
  • Failure to update to the latest firmware could lead to deployment failure.
  • Make sure to use the latest release (use X.X.459 rather than X.X.0, for example).


9

Microsoft Cloud Connector Edition image 1.4.1 on ASM recovery partition.

Network Settings

For this best practice, Cloud Connector Edition deployment follows the cabling shown below: 

 

Typical Deployments




 

Firewall Settings

For this best practice, the Router/Firewall is configured using the following rules: 

Firewall Rules


DNS Settings

Make sure that CCE FQDN is resolving to the

Unable to show "metadata-from": No such page "_space_variables"
Public IP address. To do so, login to your DNS server and create the relevant entries.

Preparing Your Node

Preparing the
Unable to show "metadata-from": No such page "_space_variables"
for Initial Setup

Update the

Unable to show "metadata-from": No such page "_space_variables"
firmware to the latest released version.

Sonus recommends starting with a clean and empty configuration. During the initial setup, 

Unable to show "metadata-from": No such page "_space_variables"
must be configured with two IP interfaces: one for the internal company network (corporate network), and the second one for the DMZ network (Internet network).

 

IP Interfaces

Ethernet Port IDSBC1000SBC2000
Port 1  
Port 2  
Port 3  
Port 4  


 

Ensure That the Node FQDN is Correct

Optionally, if you want to configure a secondary 

Unable to show "metadata-from": No such page "_space_variables"
in your environment, make sure to have the secondary 
Unable to show "metadata-from": No such page "_space_variables"
network interface configured accordingly to be able to reach out to the internal company network (corporate network).

Preparing the ASM

If your ASM have been used before, you should re-Initialize it now. Refer to Re-Initializing the ASM for details.

Confirm that the ASM is ready to deploy the Cloud Connector Edition. To do so:

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Task tab and then select Operational Status.
3Verify the following:
  • ASM board Status is Up.

  • Service Status is Running.

  • The service version (SBC Communications Service) is the most recent version. If it is not, update it by following the steps in Installing an ASM Package.

Operational Status

 

After you update the ASM, change its Admin Password.

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Task tab and then click Change Admin Password.
3

Enter and confirm your new password and then click OK.

New Admin Password

Deploying the CCE

Deploying CCE 1.4.1 on the

Unable to show "metadata-from": No such page "_space_variables"
consists of two steps:

  1. Unable to show "metadata-from": No such page "_space_variables"
    WebUI - Setup Cloud Connector Edition task.
  2. Microsoft PowerShell tasks running on 
    Unable to show "metadata-from": No such page "_space_variables"
    ASM by executing CCE specific Microsoft commands.

 

Configuring the CCE Through the WebUI

ASM Config

StepAction
1

Login to the WebUI of the

Unable to show "metadata-from": No such page "_space_variables"
.

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.

4

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

ASM Config

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.

 

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2

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

3

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 .

4Copy the CSR from the lower pane of the Generate CSR page and save it as a .txt file.
5After the CSR is signed by the Certificate Authority and you receive the PKCS12 Certificate and Key file (i.e.:  certicate.pfx file), continue the wizard by clicking on Import Certificate tab.

 

Importing Certificate/Keys

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2

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

3

Click the Action drop-down list and select the appropriate option:

  • If you generated a Certificate Request (CSR) on the previous step, select the Import X.509 Signed Certificate option,
  • If you prepare your certificate by yourself, select the Import PKCS12 Certificate and Key option. Enter the password for the certificate.
4

Select the relevant certificate file using the Choose File button and then click OK.

5

Select the file by browsing to it using Select File.

6

Click OK.

7

After receiving the activity status as successfully completed, click on Configure CCE tab.

Configuring the CCE

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
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.

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 edge fqdn for this site before proceeding

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


Configure CCE


Preparing the CCE

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
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 as shown below.

5

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


 

Prepare the CCE

 

Manually Configuring the CCE on the ASM

Manually deploying CCE on the ASM requires:

  • Registering the CCE Appliance with PowerShell
  • Installing the CCE Appliance with PowerShell

Registering the CCE Appliance with PowerShell

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.

StepAction
1Remote desktop to the ASM system.
2Launch PowerShell.
3

Execute the following commend:

Register-CcAppliance

4Enter 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. In case of mistake, refer to: Manage your Office 365 tenant.

 

Installing the CCE With PowerShell

StepAction
1Remote Desktop to the ASM system.
2Launch PowerShell.
3

Execute the following commend:

Install-CcAppliance

 

Note: This step does not require interactive input and can run unattended. It will take nearly two hours to execute. 

4This completes the CCE deployment. At this point, AD, CMS, Edge, and Mediation Server Virtual Machines should be up and running.

After configuring the

Unable to show "metadata-from": No such page "_space_variables"
for CCE, refer to Managing Your Office 365 Tenant to configure CCE update time and user.

Integrating the SBC Edge With Cloud Connector Edition

After the CCE is deployed, integrate the  Sonus Sbc Edge and allow calls from/to O365 clients. In this example, the following steps will set up the Sonus Sbc Edge for:

 

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

 

Build your SBC configuration

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Tasks tab, and then click SBC Easy Setup > Easy Config Wizard in the navigation pane.
3

Follow steps 1, 2, and 3 as shown below and then click Finish.

 

4

 Click OK on the next two popups to complete the setup.

5

 The wizard configures the necessary settings for the single

Unable to show "metadata-from": No such page "_space_variables"
and CCE integration. Relevant configuration items are shown in the Settings tab below:

 

 

Build your Second SBC Configuration (Optional)

StepAction
1Login to the WebUI of the Secondary
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Tasks tab and then run the Easy Config.
3

The preceding step will configure the Secondary

Unable to show "metadata-from": No such page "_space_variables"
with the appropriate configuration items.

4

Add the FQDNs of the Mediation Server and the pool to the host table (pointing out to Mediation Server's IP address) to allow calls to O365.

This completes deployment and integration of the CCE with the

Unable to show "metadata-from": No such page "_space_variables"
.

 


Basic Call Verification after CCE Deployment and
Unable to show "metadata-from": No such page "_space_variables"
Integration

With the preceding settings, an endpoint from the SIP provider side can dial the number of a Skype For Business (O365) client and reach out to it over

Unable to show "metadata-from": No such page "_space_variables"
. The call flow for this call is shown below:

 

Call Flow


Similarly, a Skype For Business (O365) client can dial the number of an endpoint off of ITSP and reach out to it over

Unable to show "metadata-from": No such page "_space_variables"
. The call flow for this call is shown below:

 

Call Flow


O365 Known Issue and Workarounds for CCE

Redeploying the CCE

Re-Initializing of the ASM

The ASM must be re-initialized with the image that contains the latest CCE software. To do so:

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Task tab, and then click Reinitialize in the navigation pane.
3

Select the appropriate image from the drop-down list and then click Apply.

 

Clean 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
1Remote Desktop to the ASM system
2Launch PowerShell.
3

Execute the following command:

 

Import-Module skypeonlineconnector
$cred = Get-Credential
4When 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

Execute the following command to remove the appliance:

Unregister-CsHybridPSTNAppliance -Identity <paste the identity here> -Force

8

Execute the following command to verify that the appliance has been removed:

Get-CsHybridPSTNAppliance

9

This completes the cleanup. Continue to Configuring the CCE Through the WebUI

 

Manually Managing the CCE Configuration File

Editing the CCE Configuration File

Step
Action
1.

After receiving the activity status completion message, click the Click to re-configure CCE application button.

2.

Click OK on the popup.

3.

Click the Raw (INI) Config button and then click Edit..

4.

Edit any required field In the INI file with the appropriate value for your environment.

 

Note: The example uses AEPSITE2 for the these attributes.

5.

After verifying this information, click OK:.

Exporting and Importing the CCE Configuration File

StepAction
1After receiving the activity status completion message, click the Click to re-configure CCE application button.
2Click OK on the popup.
3Click the Raw (INI) Config button and then click Export or Import.


Updating the CCE Password

Follow these steps if the CCE deployment cannot open the PFX certificate due to a password mismatch.

 

StepAction
1

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

2Use the PowerShell commands Install-CcAppliance -UpdateAllCredentials and Set-CcCredential -AccountType TenantAdmin to reset the credentials.

 

 

  • No labels