Temporarily Register Devices to a Different Core

There are times when a route to a specific core is resulting in poor call quality or other issues due to an intermediary hop. As a last resort, you can use the this article to temporarily register devices to a different core other than the client's parent core. These steps will not guarantee a resolution of the issue and should only be done after having already performed the troubleshooting steps to eliminate other possible resolutions. As a reminder, these steps are meant to be temporary until resolution is found since pointing devices to a different core can lead to cross core calls.

Requirements

• Access to the Manager Portal

• Evidence of Loss and Latency on the route between the Client's network and the datacenter they are registered to (A traceroute using Ping Plotter)