The quick answer to your question is, no. When it comes to inbound calls, the Edge does not have a built in load balancing scheme to distribute calls among other Edges.

While our redundancy scheme will help spread the calls among the Edges, it is primarily designed for handling maintenance and fault situations where one of your Edges becomes unavailable - it's not really a load balancing scheme.

When it comes to load balancing inbound calls among the Edges, you will want to configure your SBC to distribute (maybe a round robin) all the inbound calls among the three Edges in order to fully leverage the capacity of all three of the Edges.

If you only configure your SBC to route calls to a single Edge, once that Edge reaches its call capacity limit, it won't be able to handle any more inbound calls even though you have two more Edges with available capacity.

For example, if the SBC is only routing calls to Edge A, then Edge A will receive and direct the call to the appropriate station. If that station's primary is Edge B, then Edge B will handle the call. However, since the call path originated with Edge A, that means that Edge A will be a part of the call path for the duration of the call. So even though the station handling the call is on Edge B, Edge A is still tied up with the call.

So, to load balance incoming calls, your SBC needs to distribute inbound calls among the three Edges.

The quick answer to your question is, no. When it comes to inbound calls, the Edge does not have a built in load balancing scheme to distribute calls among other Edges.

While our redundancy scheme will help spread the calls among the Edges, it is primarily designed for handling maintenance and fault situations where one of your Edges becomes unavailable - it's not really a load balancing scheme.

When it comes to load balancing inbound calls among the Edges, you will want to configure your SBC to distribute (maybe a round robin) all the inbound calls among the three Edges in order to fully leverage the capacity of all three of the Edges.

If you only configure your SBC to route calls to a single Edge, once that Edge reaches its call capacity limit, it won't be able to handle any more inbound calls even though you have two more Edges with available capacity.

For example, if the SBC is only routing calls to Edge A, then Edge A will receive and direct the call to the appropriate station. If that station's primary is Edge B, then Edge B will handle the call. However, since the call path originated with Edge A, that means that Edge A will be a part of the call path for the duration of the call. So even though the station handling the call is on Edge B, Edge A is still tied up with the call.

So, to load balance incoming calls, your SBC needs to distribute inbound calls among the three Edges.

The quick answer to your question is, no. When it comes to inbound calls, the Edge does not have a built in load balancing scheme to distribute calls among other Edges.

While our redundancy scheme will help spread the calls among the Edges, it is primarily designed for handling maintenance and fault situations where one of your Edges becomes unavailable - it's not really a load balancing scheme.

When it comes to load balancing inbound calls among the Edges, you will want to configure your SBC to distribute (maybe a round robin) all the inbound calls among the three Edges in order to fully leverage the capacity of all three of the Edges.

If you only configure your SBC to route calls to a single Edge, once that Edge reaches its call capacity limit, it won't be able to handle any more inbound calls even though you have two more Edges with available capacity.

For example, if the SBC is only routing calls to Edge A, then Edge A will receive and direct the call to the appropriate station. If that station's primary is Edge B, then Edge B will handle the call. However, since the call path originated with Edge A, that means that Edge A will be a part of the call path for the duration of the call. So even though the station handling the call is on Edge B, Edge A is still tied up with the call.

So, to load balance incoming calls, your SBC needs to distribute inbound calls among the three Edges.

Please be informed that this specific bug related to the old faulty kernel version is already being worked on by our internal Dev teams. Likewise, please be aware that as of May 16, development testing of the automated fix for the kernel panic has been completed. Several controlled implementation with product support have also been completed where the kernel update was done over the air (automated) with manual kernel update as fallback. Please be assured that the kernel image has been thoroughly tested and previous issues seen during manual update has been addressed.<o:p></o:p>

 <o:p></o:p>

On June 17 after 5 PM GMT, we will be enabling the feature toggle that will make the automated kernel image available to your org. This means that on the next maintenance schedule after the said date, the kernel image of your edges will be updated together with the usual updates of edge version. We ask that you please call our support line immediately should you encounter any unexpected behaviors that may point to an issue with the edges after the update.


<o:p></o:p>best regards