...
| Add_workflow_for_techpubs |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| JIRAIDAUTH | SYM-2302223193 |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c98a00a02355cd1c2f0155cd26c87d0111, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
|---|
|
...
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.
| Multiexcerpt |
|---|
| MultiExcerptName | PreRequisites |
|---|
|
Prerequisites| Caption |
|---|
| | A public domain name prepared and mapped with your Office 365 tenant (for example, "mydomain.com"). See Create an Office 365 Tenant. | An entry on your public domain name that points to the fixed IP address of your SBC Edge (for example, myccesite1.mydomain.com" with an IP address of "nn.nn.mm.nn").
| An Office 365 tenant with an E5 license or E3 + Cloud PBX. | You must have the Global Administrator role for your O365 tenant account. | A public certificate authority ready to sign a certificate for the SBC Edge. Important! Read the steps outlined in Certificate Requirements at Microsoft Technet. | A properly configured firewall. See Ports and Protocols at Microsoft Technet. | | Note |
|---|
| 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 6.1.2 3 rather than X.X.0, for example).
|
| | Note |
|---|
| 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 sustaining release (use 6.1.2 3 rather than X.X.0, for example).
|
| | Microsoft Cloud Connector Edition image on ASM recovery partition. |
|
|
...
| Step | Action |
|---|
| 1 | Login to the WebUI of the SBC Edge. |
| 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 . |
| 4 | Copy the CSR from the lower pane of the Generate CSR page and save it as a .txt file. |
| 5 | After the CSR is signed by the Certificate Authority and you receive the PKCS7 Certificate file, continue the wizard by clicking on Import Certificate tab. |
| Caption |
|---|
|
 Image Added
|
| Anchor |
|---|
| ImportCertificate |
|---|
| ImportCertificate |
|---|
|
Importing Certificate/Keys
...
| Caption |
|---|
|
 Image Removed Image Added
|
Preparing the CCE
| Anchor |
|---|
| Preparing the CCE |
|---|
| Preparing the CCE |
|---|
|
...
| Caption |
|---|
|
 Image Modified |
Installing the CCE Appliance using Sonus Cloud Link Deployer
...
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Sonus Cloud Link Deployer |
|---|
|
 Image Added
 Image Removed |
Integrating the SBC Edge With Cloud Connector Edition
...