Yealink provisioning not working

[has...@gmail.com]

I cant get Yealink provisioning to work properly.  Testing with a T42G on 18.12 release.  Logs show phone pulls y000000000028.cfg through tftp.  However the contents of that file in the tftproot directory seem to want the phone to pull the MAC specific file from "custom_mac_cfg.url = http://<sipdomain.tld>:8185/$MAC.cfg".  I am not sure why sipXcom configures phone to pull the MAC specific <MAC address of phone>.cfg file over tftp but http should work. However the phone fails to configure.  When I try to browse to http://<sipdomain.tld>:8185/<MAC address of phone>.cfg or just http://<sipdomain.tld>:8185/ for that matter, I seem to get redirected to http://<sipdomain.tld>:12001/sipxconfig and the page load times out.  All ports are open on the firewall for testing.

[Benedikt Machens]

Am Dienstag, 12. Februar 2019 15:29:40 UTC+1 schrieb has...@gmail.com:

I cant get Yealink provisioning to work properly.  Testing with a T42G on 18.12 release.  Logs show phone pulls y000000000028.cfg through tftp.  However the contents of that file in the tftproot directory seem to want the phone to pull the MAC specific file from "custom_mac_cfg.url = http://<sipdomain.tld>:8185/$MAC.cfg".  I am not sure why sipXcom configures phone to pull the MAC specific <MAC address of phone>.cfg file over tftp but http should work. However the phone fails to configure.  When I try to browse to http://<sipdomain.tld>:8185/<MAC address of phone>.cfg or just http://<sipdomain.tld>:8185/ for that matter, I seem to get redirected to http://<sipdomain.tld>:12001/sipxconfig and the page load times out.  All ports are open on the firewall for testing.

Hi,

the y000000000028.cfg is a redirect file to tell your T42G to get it's config from the auto provisioning plugin (web request). If you try to access this plugin via a web browser you don't get any content, because your browser user agent is not "Yealink T...."

Do you have all plugins activated? sipXyealink, sipXprovisioning ? You can also take a look at /var/log/sipxpbx/sipxprovision.log to see whats going wrong in the provsioning process

Regards

Benedikt

 

[has...@gmail.com]

Thanks for this.  The logs were helpful in troubleshooting and it ended up being a DNS issue.  I have another concern about best practices to provision phones over the internet but I will create a new thread.

[Michael Picher]

It's never DNS...

--------------------------------------------------------

Michael W. Picher

Thunder Hill Properties, LLC

639 Cross Hill Rd, Vassalboro, ME 04989

207-458-1892

mpi...@gmail.com

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/abc50f46-10f3-4e88-a5e3-b6abc313c448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.