When the Peeredge Switches are SBC is directly connected to a service provider or customer’s MPLS network, we assign each customer a dedicated MPLS Virtual Routing and Forwarding (VRF) instance.
If there is a network-to-network interface (NNI) connection directly into the 46 Labs data centers, then a dedicated VLAN in the Peeredge data center is connected to each customer’s VRF. The 46 Labs data center subnets (hosting Peeredge SwitchesSBCs) are advertised into the customer’s VRF via multi-protocol BGP. The customer’s MPLS VRF must contain the IP routes necessary to reach the SIP Trunking endpoints. If a media flow-around design is used, then the IP routes for all IP endpoints (i.e. Phonesphones) must also be advertised and reachable in the customer’s MPLS VRF. Since each MPLS customer has a dedicated VRF, MPLS networks are typically considered to be secure. As such, use the TCP or UDP protocols to communicate with the Peeredge SwitchesSBC.
If there is no NNI connection directly into the 46 Labs data centers, then the Peeredge Switch SBC can be placed in the Service Provider or Customer network to access the MPLS network.
If there in no NNI connection directly into the 46 Labs data centers, then an additional network topology is required to reach the 46 Labs cloud.
...
Use end-to-end quality of service (QOSQoS) configurations to guarantee high-quality voice calls across the MPLS network.
Support a media flow-around (anchor media disabled) design to optimize the routing of RTP/SRTP media between the customer’s endpoints (i.e. IP Phones) and the Peeredge SwitchesSBC.
Cons
More expensive than most other network topologies.