Getting Started
- Getting to Know the Ribbon SBC Edge
- Functional Differences Between SBC 1000/2000 and SBC SWe Lite
- Protocols and Functions Supported
- SBC 1000/2000 Performance and Capacity
- SBC SWe Lite Performance and Capacity
- Interoperability Test Results/Best Practices with Third Party Products and Services
- Copyright and Trademarks
- Contacting Ribbon
- First Steps - Run Initial Setup and Install Latest Software/Security Patches
Installing and Commissioning the SBC
Installing SBC 1000/2000
Installing SBC SWe Lite
- SBC SWe Lite Hardware and Software Requirements
- Downloading the SBC SWe Lite Package for On-Premises Deployment
- Installing SBC SWe Lite
- Running Initial Setup on SBC SWe Lite
- Changing vCPU and Increasing Memory/VM Size
- Obtaining and Installing a Permanent SBC SWe Lite Trial License
- Obtaining and Installing an SBC SWe Lite Production License
- Powering Off and Deleting a SWe Lite Instance
- Upgrading SBC SWe Lite - Public Cloud and On-Premises Deployments
- Access Control Lists on SBC SWe Lite
Best Practices
SBC SWe Lite and Microsoft® Azure
- Deploying an SBC SWe Lite from the Azure Marketplace
- Upgrading SBC SWe Lite - Microsoft Azure
- SBC SWe Lite Trial Offer for Microsoft Azure
- Connect SBC SWe Lite to Microsoft Teams Direct Routing Deployed in Azure
- Virtual Machine Requirements - Microsoft Azure
- Change vCPU Size Following Upgrade
SBC Edge and Microsoft® Teams Direct Routing
- Connect SBC SWe Lite to Microsoft Teams Direct Routing Deployed in Azure
- Connect SBC Edge to Microsoft Teams Direct Routing
- Connect SBC Edge to Microsoft Teams Direct Routing to Support Direct Routing Carrier
- Connect SBC Edge to Microsoft Teams Direct Routing for Enterprises with Cloud PBX
- Connect SBC Edge to Microsoft Teams Direct Routing for Enterprises with Skype for Business On-Premises
- Connect SBC Edge to Microsoft Teams Direct Routing to Support Analog Devices
- Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing
- Best Practice - Migrating the SBC Edge from Direct Routing Non Media Bypass to Direct Routing Media Bypass
- Best Practice - Configure SBC Edge for Yealink Teams Client Local Survivability
- Best Practice - Configuring Microsoft Teams Local Media Optimization
- Best Practice - Configure Direct Routing Survivable Branch Appliance (SBA)
- Best Practice - Configure Destination Path Resiliency through Independent Internet Connections
- Configure SIP Trunk with Microsoft Teams
- Configure ISDN PSTN with Microsoft Teams
- Migrate from Skype for Business Online to Microsoft Teams
- Working with Licenses
SBC Edge Features, Call Routing, and Other Topics
- Ribbon SBC Edge Configuration with Zoom BYOC
- Skype/Lync Related Best Practices
- SIP Related Best Practices
- Call Forking Based on Active Directory User Attributes
- Call Routing Based on Active Directory User Attributes
- Packet Capture - Best Practice
- Configuring Calls to Emergency Services on PSTN Lines
- Configuring the SBC Edge for NAT Traversal
- Best Practice - Configuring Time of Day Routing
- Best Practice - Configure SBC Edge with Polycom VVX Local Survivability
- Best Practice - Connecting to Exchange Online Unified Messaging (UM)
- Best Practice - Configure SBC Edge Ethernet Redundancy for Various Scenarios
For a list of all Best Practices, refer to Best Practices.
SBC Releases
Frequently Asked Questions
- How are users authenticated on the SBC Edge?
- Does SBC Edge support advanced SIP matching?
- Is there a compiled list of pages for viewing SBC Edge-related software versions?
- How does SBC Edge process network traffic through its Ethernet Interfaces?
- When installing cumulative updates for Lync SBA, can we skip CUs in between?
- How do I find a logged in user's IP address?
- What user authentication methods does the SBC Edge support?
Overview
Content Tools