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

Compare with Current View Page History

« Previous Version 3 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...

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

 

CCE Deployment Scenarios

000_Scenarios.png.png
 

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 .

 

Back to Top

Network Settings

For this best practice, the CCE is deployed in the following network:

Typical Deployments

 

Firewall Settings

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

Firewall Rules Used for This Best Practice

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

 

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

For best results:

  • Update the SBC firmware to the latest version.
  • Start with an empty, clean configuration.

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:

Pre-configured IP Interfaces

Ensure That the Node's FQDN is Correct

nls1.png nls2.png

Optional

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

Perform these steps on both

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

StepAction
1Login to the WebUI of the
Unable to show "metadata-from": No such page "_space_variables"
.
2Click the Task tab, and then click Opreational 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

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

  1. Setup CCE using the
    Unable to show "metadata-from": No such page "_space_variables"
    WebUI.
  2. Excute PowerShell commands/run tasks on the
    Unable to show "metadata-from": No such page "_space_variables"
    ASM.

 

Important!
  • 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 CCE Through the WebUI

Configuring the ASM

Perform these steps on both

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

StepAction
1

Login to the WebUI of both

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 as shown below.

4

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

CCE-1

 

CCE-2

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.

 

Perform these steps on only one of the

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

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

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 .

 

 

Importing Certificate/Keys

Perform these steps on both

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

Step Action
1Login to the WebUI of both
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

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.

 

Configuring the CCE

 

Perform these steps on both

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

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 .

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

 

 

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.

The CCE deployment internally sets the domain suffix as defined under VirtualMachineDomain attribute. Although your

Unable to show "metadata-from": No such page "_space_variables"
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 
Unable to show "metadata-from": No such page "_space_variables"
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.

Perform these steps on both

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


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


Perform these steps on both

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


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


Preparing the CCE

Perform these steps on both

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

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

5

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

 

Manually Configuring the CCE on the ASM

 

Manually deploying CCE on the ASM requires:

  • Registering the CCE Appliance

  • Installing the CCE Appliance

 

Registering the CCE Appliance

 

Perform these steps on only one of the

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

Step

Action

1

Remote desktop to the ASM of the

Unable to show "metadata-from": No such page "_space_variables"
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

Unable to show "metadata-from": No such page "_space_variables"
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

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

2

Launch PowerShell.

3

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

Install-CcAppliance

Publish-CcAppliance

StepAction
1Remote desktop to the ASM of the
Unable to show "metadata-from": No such page "_space_variables"
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

Unable to show "metadata-from": No such page "_space_variables"
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

Unable to show "metadata-from": No such page "_space_variables"
and allow calls from/to O365 clients. In this example, the following steps will set up the 
Unable to show "metadata-from": No such page "_space_variables"
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
Unable to show "metadata-from": No such page "_space_variables"
-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.

 

Back to Top

Building Your SBC Edge-2 Configuration

 

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

 

Mediation Server FQDNs


MediationServerFQDNentries2.png

 

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
Unable to show "metadata-from": No such page "_space_variables"
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 

 

 

  • No labels