Yealink provisioning to new host

[telforce]

Next week i'm going to migrate a 3CX in the cloud system to another host. This instance has about 10 extensions which are provisioned through the 3CX manager interface using the direct Stun remote method. Ik now this uses the Yealink RPS system to provision a phone.

From experience i know that if you try to provision a Yealink phone which was already provisioned before you can't do that because in the Yealink RPS system the MAC is tied to the old host machine.

Question1: What is the right way to do this? If i delete the provisioning profile under the extension will this also remove the MAC from the Yealink RPS platform or do i have to make a ticket with Yealink about this?

Question2: When i make a backup of the 3CX config and import that to the new host is it possible to re-provision the Yealink phones from that new host through the 3CX admin interface or do i have to manually reset every phone to factory settings?

 

[AWS2P]

Question1: What is the right way to do this? If i delete the provisioning profile under the extension will this also remove the MAC from the Yealink RPS platform or do i have to make a ticket with Yealink about this?

No , it won't produce that, you need to remove Mac adress from RPS server, factory reset phones to be sure no previous setting stay in for future use on another configuration

If i can advise you to use an SBC instead of Stun for your new cloud install or do you have VPN link ?

 

[telforce]

ok thanks so i will have to contact Yealink to remove the MAC addresses.

I have never worked with SBC. Why do you recommend it?

The disadvantages i see:

-This is a remote client. I have to install a piece of hardware which will be a single point of failure
-Because this is remote it would require remote SSH access to the box which will be a pain to get taken care of by their network department

 

[AWS2P]

SBC avoid lot of pain for port management for each phone you use .
SBC give phone same as local lan visibility and for provisioning it's working like a charm
SBC need only 5090 port to work with pbx
No more RPS problem as you are know obliged to face with just to remove config.

yes SBC run a piece of hardware, but a single PI 3B+ can handle up to 30 phones, so if you have 10 you are comfortable.
Pi is very low price, if you don't trust, you can have one spare part.

I use several Pi as SBC and they are working h24/7/365 and never had to do something on .

SBC is on windows version too, so access can be easily done with any remote access software like Any desk, teamviewer.....

other interest of windows SBC is once remote connected you have easy access to phones GUI as you are local same LAN so you can do phone management easy

 

[YiannisH_3CX]

You are moving the PBX to another host, but are you changing the FQDN? If not then after you move the server wait for the DNS to point to the new public IP. Once that is done restart the Yealink phones and they should contact the PBX at the new IP address. If that does not work then the router of the remote site might need a restart to get the new IP address.
If your FQDN will remain the same and you restore your backup the provisioning link will not change.