Versions Compared

Old Version 2

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 3

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1ghoppe
JIRAIDAUTHSYM-2226922707
REV5ghoppe
REV6ghoppe
REV3plessisahgezer
REV1plessisa

 

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.

 

Before You Start

CCE Deployment Scenarios

Info
titleImportant Note Regarding the CCE and Microsoft Windows Updates

Microsoft's Windows Update service is active on the ASM. During a Windows download and update, the CCE will stop. And SBC Edge with 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.

 

Caption
0Figure
1CCE Deployment Scenarios

000_Scenarios.png.pngImage Added

Span

 

The following diagram shows typical CCE deployment scenarios. Determine which scenario applies to your deployment, and then click the appropriate link in the list that follows.

Image Removed

 

.

Children Display

After configuring the

Spacevars
0product
for CCE, refer to Managing Your Office 365 Tenant for more information.

Info
titleImportant Note Regarding the CCE and Microsoft Windows Updates

Microsoft's Windows Update service is active on the ASM. During a Windows download and update, the CCE will stop. And SBC Edge with 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.

 

 

 children