Where to Deploy your Peeredge Orchestrators?

Created by Kelly Evans, Modified on Thu, 30 Jan at 4:47 PM by Kelly Evans

The first consideration, and one of the most important, is where to physically deploy the Peeredge Orchestrators. The Peeredge Orchestrator needs network connectivity to all customer PBXs or SBCs, all Vendors (PSTN Providers), and the 46 Labs cloud. The Network Topologies available to you, your security requirements, and your overall business requirements impact the deployment choice.

For Service Provider Deployments, the typical choices are:

46 Labs hosted data centers, or
your hosted data centers, which is where you have NNI (MPLS, SD-WAN, etc.) connections to your customer's networks

For Enterprise Customers Deployments, the typical choices are:

46 Labs hosted data centers
Enterprise data center(s), which is where your PBXs, SBCs, or TDM/Analog gateways are deployed
Headquarters locations
Any customer location, when taking advantage of the SD-WAN features of the Peeredge Orchestrator.

Network Topology Considerations

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 connect to 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 Orchestrator needs network connectivity to reach:

1. The 46 Labs Public Cloud. The Peeredge Orchestrator is, by design, managed in the cloud. The 46 Labs Public Cloud hosts your dedicated portal to manage the configurations of all your Peeredge Orchestrators, as well as a dedicated data warehouse that stores all the Peeredge Orchestrator 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.

2. The PSTN Provider(s)

Most enterprise customers choose to connect their Orchestrators to the 46 Labs ECO platform for PSTN connectivity. The ECO platform, hosted in the 46 Labs Cloud with direct connections to over two dozen PSTN providers, typically provides significant cost savings as compared to customer provided connectivity to PSTN providers.

3. The customer(s) Sip Signaling and Media Endpoints.

If all customer end-points have network connectivity to the Peeredge Orchestrator, then anchor media can be disabled on the Peeredge Trunk Groups. This approach is well suited to Orchestrators deploy in MPLS or SD-WAN network topologies as it can optimize the media path and can significantly reduce network bandwidth requirements at sites where the Peeredge Orchestrator is deployed.