Hello,
I need to change the self owned FQDN for a PBX. I'm familiar with the process on the PBX side to change the FQDN, however I was hoping for an easier method on the remote phone endpoint side. It would be nice if there was a tool or method, if you have control over both old and new domain DNS, to reprovision remote extensions to update to the new FQDN.
It seems it's close to being possible by what I tested, but maybe more complicated than I understand.
What i did in testing to simulate was set up a cname DNS entry for oldserver.olddomain.com pointing to newserver.newdomain.com. Since I haven't actually changed the FQDN in the PBX, oldserver doesn't exist and newserver is the current PBX. I manually changed the URL's in the phone web interface for the account, STUN server, autoprovision url etc, to simulate being provisioned to oldserver.olddomain.com.
This almost works. The phone does resolve oldserver.olddomain.com to newserver.newdomain.com and registers to newserver.newdomain.com, calls can't be made but what I was hoping was being able to register to the new server then I would be able to then send a reprovision and it would update the phone for the new server urls, reboot and would be done. Alas, reprovision does not work/isn't processed on the phone.
If this was possible, it would certainly be a huge timesaver manually reprovisioning phones on FQDN change, especially large installs.
Thoughts? Ideas? I'm sure there's a background reason why this wouldn't work, probably SSL Certificate issue, but maybe it could be possible?
Thanks.
I need to change the self owned FQDN for a PBX. I'm familiar with the process on the PBX side to change the FQDN, however I was hoping for an easier method on the remote phone endpoint side. It would be nice if there was a tool or method, if you have control over both old and new domain DNS, to reprovision remote extensions to update to the new FQDN.
It seems it's close to being possible by what I tested, but maybe more complicated than I understand.
What i did in testing to simulate was set up a cname DNS entry for oldserver.olddomain.com pointing to newserver.newdomain.com. Since I haven't actually changed the FQDN in the PBX, oldserver doesn't exist and newserver is the current PBX. I manually changed the URL's in the phone web interface for the account, STUN server, autoprovision url etc, to simulate being provisioned to oldserver.olddomain.com.
This almost works. The phone does resolve oldserver.olddomain.com to newserver.newdomain.com and registers to newserver.newdomain.com, calls can't be made but what I was hoping was being able to register to the new server then I would be able to then send a reprovision and it would update the phone for the new server urls, reboot and would be done. Alas, reprovision does not work/isn't processed on the phone.
If this was possible, it would certainly be a huge timesaver manually reprovisioning phones on FQDN change, especially large installs.
Thoughts? Ideas? I'm sure there's a background reason why this wouldn't work, probably SSL Certificate issue, but maybe it could be possible?
Thanks.
