Page History
...
- Ribbon SBC Edge 1000
- Ribbon SBC Edge 1000 license
- This interop requires the acquisition and application of SIP sessions, as documented at Working with Licenses
- Requires the license for DSI and FXI ports (ISDN ports).
- Public IP addresses
- TLS certificates for SBC Edge 1000
- For more details, please visit Working with Certificates
- Google Workspace and Domain
- Google Voice Premier license for the users
- For more details, contact Google support
...
To deploy the Ribbon SBC Edge 1000 instance, refer to Installing SBC 1000/2000
Ribbon SBC Edge 1000 Configuration
...
Click Enter and log in with a valid User ID and Password.
License and TLS Certificates
...
For more details on Licenses, refer to Working with Licenses.
SBC Certificate
From the Settings tab, navigate to Security > SBC Certificates > Generate SBC Edge Certificates.
...
| 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. |
Networking Interfaces
...
Navigate to Node Interfaces > Logical Interfaces.
Ethernet 1 IP
Ethernet 1 IP is assigned an IP address used for transporting all the VOIP media packets (for example, RTP, SRTP) and all protocol packets (for example, SIP, RTCP, TLS). DNS servers of the customer's network should map the SBC Edge 1000 system hostname to this IP address. In the default software, Ethernet 1 IP is enabled and an IPv4 address is acquired via a connected DHCP server. This IP address is used for performing Initial Setup on the SBC Edge 1000.
Ethernet 2 IP
After initial configuration, you may configure this logical interface using the Settings or Tasks tabs in the WebUI or you can use the IP address configured during Initial Setup.
Configure Static Routes
...
Call Routing allows calls to be carried between Signaling Groups, thus allowing calls to be carried between ports and between protocols (such as ISDN to SIP). Routes are defined by Call Routing Tables, which allow flexible configuration of how calls are to be carried and how they are translated. These tables are the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists, and the Signaling Groups.
...
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. They are the entity to which calls are routed, as well as the location from which Call Routes are selected. They are also the location from which Tone Tables and Action Sets are selected.
From the Settings tab, navigate to Signaling Groups. Click Add SIP SG.
...
TLS Profiles are used by SIP Signaling Groups when the TLS transport type is selected for incoming and outgoing SIP trunks (Listen Ports), and in SIP Server Tables when TLS is selected as the Server Host protocol.
...
Overview
Content Tools