Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


CSS Stylesheet

.wiki-content h1 {
border-top: 1px solid rgb(145,150,153);
}
h1, h2, {font-size: 18pt !important;}
h3 {font-size: 16pt !important;}
h4 {font-size: 14pt !important;}
h5 {font-size: 14pt !important;}
 CSS Stylesheet

 Section

 Column
width40%
Table of Contents
 Panel
 Table of Contents
maxLevel4


 Column
width5%


 Column
width55%

 Noprint
 Add_workflow_for_appnotes
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cec00c5c, userName='null'}
JIRAIDAUTHIOT-606
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb220566, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV4UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8a10148, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'}


...
...
SBC Core should be configured for Teams Direct Routing and PSTN with the below link:
https://doc.rbbn.com/display/ALLDOC/SBC+8.2+-+Configure+SBC+for+MS+Teams

 Info
Follow the section from Common SBC Configuration till Configure SBC for MS Teams Media Bypass.

 Info
  • When using media bypass, the media between the Teams client and the SBC is using the SBC external (public) interface.
  • This solution is to allow calls to/from the SIP trunk/PSTN, when connectivity to Microsoft Teams is lost – survivability mode.
...
SBC Core has an Embedded Routing Engine (ERE). It can be configured as mentioned in the link below:
https://doc.rbbn.com/display/ALLDOC/SBC+8.2+-+Configure+ERE+for+MS+Teams

 Note
Once the above 2 sections are configured, proceed with the below mentioned sections.
...
 Note
Attach the TLS Profile created earlier in Configure SBC for TLS.

 Warning
There are a few areas that result in a TLS negotiation issue. One area involves assigning the incorrect port. Ensure the following are accomplished: 
  • SBA listens on port number 5061 (default setting).
  • Configure port number 5060 on the SBC IP-Peer, since Ribbon SBC Core increments the port by 1 when the transport protocol is TLS.
...
Create a SIP Trunk Group towards the SBA and assign the corresponding profiles such as PSP and IPSP which were created in earlier steps.
...
 Note
Attach the TLS Profile created earlier in Configure SBC for TLS.

 Warning
There are a few areas that result in a TLS negotiation issue. One area involves assigning the incorrect port. Ensure the following are accomplished: 
  • SBA listens on port number 5061 (default setting).
  • Configure port number 5060 on the SBC IP-Peer, since Ribbon SBC Core increments the port by 1 when the transport protocol is TLS.
...
Create a SIP Trunk Group towards the SBA2 and assign corresponding profiles such as PSP and IPSP which were created in earlier steps.
...
For Prerequisites on Direct routing SBA, refer to the following link:
https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Prerequisites
 Anchor
Installation
Installation
Installation
For Installation on Direct routing SBA refer to Step 1 in the following link:
https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Step1:InstallVirtualSBASoftware
 Anchor
Configuration
Configuration
Configuration
For Configuring on Direct routing SBA refer to Step 2 in the following link:
https://doc.rbbn.com/display/UXDOC110/Best+Practice+-+Configure+Direct+Routing+Virtual+Survivable+Branch+Appliance#BestPracticeConfigureDirectRoutingVirtualSurvivableBranchAppliance-Step2:SetuptheOffice365DirectRoutingvSBA
 Info
...
 Warning
As SWe Core would be interacting with Virtual Survivable Branch Appliance (vSBA) in the current deployment scenario, configuring Step 3: Configure SBC SWe Edge is not required, as this step is strictly for deployment scenarios involving Ribbon SWe Edge and vSBA.
...