Temporarily Register Devices to a Different Core

Updated at April 22nd, 2024

+ More

Table of Contents

Proxy SRV DNS Records Devices Overrides Yealink Grandstream SNOM Polycom Apply Override

Scope

Intended Audience: White Label Partners

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)

Proxy SRV DNS Records

DNS SRV Records has been moved to it's own document and can be found here

Devices Overrides

Yealink

account.1.outbound_host="<Proxy SRV DNS Record>"
SkipOutboundProxy="1"

Grandstream

P48="<Proxy SRV DNS Record>"

SNOM

Tested on Snom D series

user_outbound1="<Proxy SRV DNS Record>:0"

Polycom

voIpProt.SIP.outboundProxy.address="<Proxy SRV DNS Record>"

Apply Override

Apply custom overrides
If this is WLP, send them the required overrides and the following doc

https://voipdocs.io/en/articles/234-add-custom-overrides

If this is Direct/CP, apply the overrides for the affected devices or domains defaults.
1. Ensure the affected device(s) register to the core you selected

alternate core temporary registration