- Joined
- Dec 17, 2015
- Messages
- 36
- Reaction score
- 7
We are deploying a number of phone systems this week, and we've run into an autoprovision problem with T48G and T46G (It maybe more than that, but that's all we use for phones).
The problem appears in if the Yealink phone's provisioning URL is set to a DNS name, autoprovision never happens. I am a professional as far as networks are concerned and am intimately familiar with DNS. I have checked our resolution, forward/reverse and internal DNS servers, everything resolves properly and has the appropriate records.
If I change the provisioning URL from http://3cxserver:5000/provisioning/reallylongstring to http://192.168.1.1:5000/provisioning/reallylongstring and hit autoprovison on the phone, it works perfectly, but the URL reverts back to http://3cxserver:5000/provisioning/reallylongstring and if I want to reprovision I have to do that dance again.
Has anyone else experienced this issue?
The problem appears in if the Yealink phone's provisioning URL is set to a DNS name, autoprovision never happens. I am a professional as far as networks are concerned and am intimately familiar with DNS. I have checked our resolution, forward/reverse and internal DNS servers, everything resolves properly and has the appropriate records.
If I change the provisioning URL from http://3cxserver:5000/provisioning/reallylongstring to http://192.168.1.1:5000/provisioning/reallylongstring and hit autoprovison on the phone, it works perfectly, but the URL reverts back to http://3cxserver:5000/provisioning/reallylongstring and if I want to reprovision I have to do that dance again.
Has anyone else experienced this issue?