Network Topology Considerations

The choice of network connectivity to the Peeredge SBC can significantly impact the SIP Trunking design and security options available to you. The Peeredge SBC 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 SBCs.

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

The 46 Labs Public Cloud. The Peeredge SBC is, by design, managed in the cloud. The 46 Labs Public Cloud hosts your dedicated portal to manage the configurations of all your Peeredge SBCs, 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.

The PSTN Provider(s)

The customer(s) Sip Signaling and Media Endpoints.

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