Page History
...
- Amazon Web Services (AWS) subscription
- Ribbon SBC SWe Lite on AWS
- SBC SWe Lite License
- This interop requires the acquisition and application of cloud SIP sessions, as documented at Cloud-Based SBC SWe Lite Deployment Licenses
- Public IP Addresses
- Twilio Elastic SIP Trunk
- Contact Twilio for Domain, IP and Port information
- For more details, visit https://www.twilio.com/docs/sip-trunking or see the “Twilio Elastic SIP Trunk Configuration” section of this document
- TLS Certificates for SBC SWe Lite
- Please refer to Working with Certificates
Product and Device Details
...
The SBC SWe Lite is available for deployment in AWS. It is created as a virtual machine (VM) hosted in AWS. To deploy an SBC SWe Lite instance, refer to Deploying an SBC SWe Lite via Amazon Web Services-AWS. Once SWe Lite instance is successfully created on AWS, retrieve the allocated NAT Public IPs, Ethernet IPs and Management IP. Also ensure Twilio IP addresses are whitelisted on AWS access list. For more details, visit the link given in the References section.
...
For more details on Licenses, refer to Cloud-Based SBC SWe Lite Deployment Licenses.
Import Trusted Root CA Certificates
...
For more details on Certificates, refer to Working with Certificates.
| Info | ||
|---|---|---|
| ||
When the Verify Status field in the Certificate panel indicates Expired or Expiring Soon, replace the Trusted CA Certificate. You must delete the old certificate before importing a new certificate successfully. |
...
| Warning | ||
|---|---|---|
| ||
Most Certificate Vendors sign the SBC Edge certificate with an intermediate certificate authority. There is at least one, but there could be several intermediate CAs in the certificate chain. When importing the Trusted Root CA Certificates, import the root CA certificate and all Intermediate CA certificates. Failure to import all certificates in the chain causes the import of the SBC Edge certificate to fail. Please refer to Unable To Get Local Issuer Certificate for more information. |
View Networking Interfaces
...
Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. They can, for example, convert a public PSTN number into a private extension number, or into a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table, and they are selected from there. In addition, Transformation tables are configurable as a reusable pool that Action sets can reference.
...
| Info | ||
|---|---|---|
| ||
For details on Transformation Table Entry configuration, refer to Creating and Modifying Entries to Transformation Tables. For call digit matching and manipulation through the use of regular expressions, refer to Creating Call Routing Logic with Regular Expressions. |
Configure Call Routing Tables
...
For Microsoft Teams Direct Routing configuration for SBC SWe Lite, refer to the following: Connect SBC Edge to Microsoft Teams Direct Routing
Please check the connectivity for interfacing with Microsoft Teams Direct Routing before making the calls by following the procedure provided at the following link: Working with Connectivity Check - Verifying Service and Port Requirements for CCE and Teams
| Info | ||
|---|---|---|
| ||
This interop was performed with Media-Bypass OFF configuration on Microsoft Teams Direct Routing. |
...
For additional information on Ribbon SBC SWe Lite on AWS, please visit:
Deploying an SBC SWe Lite via Amazon Web Services-AWS
For additional information on Teams, please visit:
Best Practice - Troubleshoot Issues with Microsoft Teams Direct Routing and Connect SBC Edge to Microsoft Teams Direct Routing
For detailed information about Twilio Elastic SIP Trunking and solutions, please visit:
https://www.twilio.com/sip-trunking, https://www.twilio.com/docs/sip-trunking and https://www.twilio.com/docs/sip-trunking/elastic-sip-trunking-solution-blueprints
...
Overview
Content Tools