You create a BYOC Premises Edge group to enable premises-based Edges and phones to communicate on a low latency LAN or WAN and to optimize call routing for outbound calls. 

A new Edge group cannot function until you associate it with one or more Edges. When you add an Edge to an Edge group, the system creates resources that are then shared among all the Edges in the group. The added Edge also gains access to shared trunks

Note: Edges in one Edge group cannot communicate to Edges in another Edge group. For organizations with multiple locations, use site configuration to manage Edges not Edge groups. Only create separate Edge groups if you do not want direct communication between Edges in the separate groups.

Consider the following before you add resources to a BYOC Premises Edge group:

  • Each Edge is associated with a site. A site handles call routing for a specific location, therefore each Edge has a relationship to a specific calling area.
  • Local Site Routing improves call routing by making Edges site aware within an Edge group. Calls will be routed through local (same site) Edges when possible to save bandwidth and reduce latency.
  • Each site in the Edge group requires trunks that work for the site location. An Edge group requires an external SIP trunk to connect to the service provider. A SIP phone trunk or WebRTC phone trunk is required to connect your phones to the Edge group.
  • When you add an Edge to an Edge group, the Edge can share the resources, including trunks, with the other Edges in the Edge group. For example, if an Edge is connected to a long-distance line, the other Edges in the group can use that line when you add the Edge to the Edge group.

Map the site and trunks you need in an Edge group before adding the Edges. After you determine the trunks you need, you add the Edges attached to those trunks to the Edge group.

Edge group setup is detailed in Create a BYOC Premises Edge group with a phone trunk.