...
Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | SYM-2433127627 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'} |
---|
|
Excerpt Include |
---|
| UXDOC61:Not_for_SWe |
---|
| UXDOC61:Not_for_SWe |
---|
nopanel | true |
---|
|
Warning |
---|
title | READ 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... |
Note |
---|
SBC Edge will support a new deployment with CCE 2.1.0 in release 7.0.1.If your CCE auto-updates to CCE 2.1.0: - To rerun the step “Transfer Credential from SBC”, it will require 7.0.1.
. |
Info |
---|
For details on troubleshooting, see Troubleshooting Cloud Connector 6.1.2. |
Multiexcerpt include |
---|
MultiExcerptName | BeforeYouStart |
---|
PageWithExcerpt | Configuring the SBC Edge for a Single CCE |
---|
|
...
In this best practice the router/firewall is configured with the following rules:
Caption |
---|
0 | Table |
---|
1 | Internal Firewall Rules for CCE |
---|
|
Source IP | Destination IP | Source Port | Destination Port |
---|
Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117 | Internal clients | TCP 49 152 – 57 500* | TCP 50,000-50,019 (Optional) | Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117 | Internal clients | UDP 49 152 – 57 500* | UDP 50,000-50,019 | Internal clients | Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117 | TCP 50,000-50,019 | TCP 49 152 – 57 500* | Internal clients | Cloud Connector Mediation component – 192.168.210.123 & 192.168.210.117 | UDP 50,000-50,019 | UDP 49 152 -57 500* |
|
Caption |
---|
0 | Table |
---|
1 | External Firewall Rules for CCE |
---|
|
Source IP | Destination IP | Source Port | Destination Port |
---|
Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | Any | TCP 5061 | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | Any | TCP 80 | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | Any | UDP 53 | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | Any | TCP 53 | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | TCP 50,000-59,999 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | UDP 3478 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | UDP 50,000-59,999 | Any | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | TCP 5061 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | TCP 443 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | TCP 50,000-59,999 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.86 | Any | UDP 3478 | Any | Cloud Connector Edge External Interface – 192.168.211.81 & 192.168.211.81 & 192.168.211.86 | Any | UDP 50,000 - 59,999 |
.86 | Any | UDP 50,000 - 59,999 |
|
Caption |
---|
0 | Table |
---|
1 | Host Firewall Rules - Internal or External Access |
---|
|
Source IP | Destination IP | Source Port | Destination Port |
---|
ASM | Any | Any | TCP 53 | ASM | Any | Any | TCP 80 | ASM | Any | Any | TCP 443 |
|
Multiexcerpt include |
---|
MultiExcerptName | DNSSettings |
---|
PageWithExcerpt | Configuring the SBC Edge for a Single CCE |
---|
|
...
Note |
---|
- Ensure the Node FQDN is definitive. Changing this information requires the CCE to be redeployed.
- Ensure that an NTP server is configured.
|
Sonus recommends starting with a clean and empty configuration.
Caption |
---|
0 | Figure |
---|
1 | Ensure That the Node's FQDN is Correct |
---|
|
Image Modified Image Modified |
Info |
---|
|
When configuring a secondary in your environment, make sure to have the secondary network interface is configured accordingly to be able to reach out to CCE's internal/corporate network. |
...
- Prepare the CCE deployment on the SBC Edge using the section below.
- Using Sonus Cloud Link Deployer via Remote Desktop on the ASM Module:
- Register all the CCE appliances.
- Install and publish the CCE Appliance Master.
- Install the CCE Appliance Slave.
...
Note |
---|
Perform these steps on both systems. |
Step | Action |
---|
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. | |
4 | From the Remote Desktop Enabled drop down list, select Yes (to enable Remote Desktop) or No (to disable Remote Desktop). | |
5 | From the Windows Firewall Enabled drop down list, select Yes (to enable Windows Firewall) or No (to disable Windows Firewall). |
6 | From 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). | |
7 | From 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. |
8 | From 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. |
9 | Configure/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 |
---|
0 | Figure |
---|
1 | Configuring the ASM – CCE-1 |
---|
|
Image Modified |
Caption |
---|
0 | Figure |
---|
1 | Configuring the ASM – CCE-2 |
---|
|
Image Modified |
Generating the CSR
...
Caption |
---|
|
Image Modified |
Set CCE Public Certificate
...
Caption |
---|
0 | Figure |
---|
1 | SBC 1 - CCE Public Certificate |
---|
|
Image RemovedImage Added |
Caption |
---|
0 | Figure |
---|
1 | SBC 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. |
Step | Action |
---|
1 | Login to the WebUI of the SBC Edge. |
2 | Navigate to Tasks > Office 365 Cloud Connector Edition> Setup. |
3 | Click 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 |
---|
0 | Figure |
---|
1 | Configuring the ASM – CCE-1 |
---|
| Image RemovedImage Added |
Caption |
---|
0 | Figure |
---|
1 | Configuring 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. |
6 | After receiving the activity status as successfully completed, click the Prepare CCE tab to continue. |
...
Step | Action |
---|
1 | Login to the WebUI of each SBC Edge. |
2 | Navigate to Tasks > Office 365 Cloud Connector Edition> Setup. |
3 | Click 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. |
5 | In 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. |
6 | From 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. |
7 | In 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. |
8 | In 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. |
9 | Click Apply. |
10 | Access Tasks> Operational Status to verify Windows Activation. |
11 | |
Caption |
---|
|
Image RemovedImage Added |
Info |
---|
title | Identify Microsoft Product Key |
---|
|
To identify the Microsoft Product Key:- Access the bottom of the SBC unit and locate the two Microsoft Certificate of Authenticity stickers.
- Locate the Microsoft Product Key for each.
Sample Microsoft Certificate of Authenticity Sticker
|
...
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
|
...
...
Appliance using Ribbon Cloud Link Deployer | | Installing the CCE Appliance using Ribbon Cloud Link Deployer |
---|
|
...
Installing the CCE Appliance using ...
Ribbon Cloud Link Deployer
Note |
---|
title | CCE 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, see 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.30 minutes.
|
Using
Using Sonus Cloud Link Deployer via Remote Desktop on the ASM Module:
...
Step | Action |
---|
1 | Remote desktop to the ASM of the SBC Edge System 1. |
2 | Launch the Sonus 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.
|
4 | Click Apply. |
5 | After successful execution, remote desktop to the ASM of the System 2. |
6 | Launch the Sonus 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.
|
8 | Click Apply. |
...
1 | Registering 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. |
2 | Launch the Sonus 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.
|
4 | Click Apply. |
Caption |
---|
0 | Figure |
---|
1 | Install CcAppliance on HA Master Node |
---|
|
Image Removed Install-CcAppliance on the HA Slave Node
Step | Action |
---|
1 | Remote desktop to the ASM of the SBC Edge System 2. |
2 | Launch the Sonus Cloud Link Deployer from icon on the desktop. |
3 | Check the third action: - Install Appliance: This step deploys the CCE.
|
4 | Click Apply. The Installation time depends on the bandwidth between the Master and the Slave. |
5 | After configuring the SBC Edge for CCE, refer to Managing Your Office 365 Tenant to configure CCE update time and user. |
...
Image Removed
Integrating SBC Edge With CCE
...
Step | Action |
---|
1 | Login to the WebUI of SBC Edge-1. |
2 | Navigate 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. |
...
Building your SBC Edge-1 Configuration | Image Removed |
Building Your SBC Edge-2 Configuration
Step | Action |
---|
1 | Login to the WebUI of SBC Edge-2. |
2 | Navigate 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. |
...
Caption |
0
Figure | 1 | Building your SBC Edge-2 Configuration |
---|
Image Removed |
Multiexcerpt include |
---|
MultiExcerptName | BasicCallVerification |
---|
PageWithExcerpt | Configuring the SBC Edge for a Single CCE |
---|
|
Multiexcerpt include |
---|
MultiExcerptName | O365KnownIssues |
---|
PageWithExcerpt | Configuring 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.
Step | Action |
---|
1 | On the WebUI, click Tasks and select the Prepare CCE tab (see Preparing the CCE). |
2 | Click Prepare CCE. |
3 | From 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 Sonus Cloud Link Deployer, and check Transfer Password from SBC to reset the credentials. |