Network Topology Considerations

Created by Kelly Evans, Modified on Wed, 4 Jun at 6:42 AM by Kelly Evans

The choice of network connectivity to the Peeredge Orchestrator can significantly impact the SIP Trunking design and security options available to you. The Peeredge Orchestrator  supports several different network connectivity options. They include 46 Labs’ software-defined wide area networking (SD-WAN), direct Internet access, IPsec tunnels, or your own transport (BYOT) such as third-party MPLS or SD-WAN. The same or different network topologies can be used to connect to the same Peeredge Orchestrators. 

For example, to provide direct connectivity between an Orchestrator and a customer’s PBXs and their associated end-points (i.e. IP Phones), an MPLS topology might be used. To reach a PSTN Provider, a TLS encrypted Direct Internet connection could be used.  

Each Peeredge SBC needs network connectivity to reach:

The 46 Labs Public Cloud. The Peeredge Orchestrator is, by design, managed in the cloud. The 46 Labs Public Cloud hosts the portal (web based user interface) to manage the configurations of all your Peeredge Orchestrator deployments, as well as a dedicated data warehouse that stores all the Peeredge SBC generated Call Detail Records (CDRs), SIP Traces, and any configured call recordings. 

If the Peeredge Orchestrator is hosted in the 46 Labs Public Cloud, 46 Labs provides and manages this network connectivity.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article