Please correct me if I’m wrong but:
- Yealink phones, like most other sip devices, load their config via tftp
- one would have to both start the tftp service as well as open the firewall for that
On a pbx exposed to the internet, I don’t like to do that very much. Is there a way to auto-provision via the commercial EPM and https?
EPM exposes whatever protocols you have configured for provisioning in System Admin, including https. I don’t have tftp or ftp enabled on this system for provisioning, so this is what the Yealink template looks like:
System Admin pro allows you to protect your http(s) provisioning services with credentials, otherwise you want to ensure you’re not exposing it to untrusted source IPs.
fwconsole firewall trust [phone ip]
should do that. Excellent!
set up the template exactly like that (PhoneApps to https though). How do you then provision a phone?
I would think: Trust phone’s ip and set the url of the server in Advanced/Auto Provision/URL.
Only that does not seem to do the trick. I see some traffic reach the server but no config is pulled it seems. Am I missing something?
Provisioning URLs take the form:
where the domain is whatever IP/fqdn is needed for the phone to reach the server, and the port is whatever is defined for http(s) provisioning.
makes a lot of sense! Now I wonder what user and pass might be for provisioning. Not the extension’s I would guess?
User and password are as defined in Syadmin Pro → Provisioning protocols. If you don’t have sysadmin pro or if they are disabled, then you omit them:
And it feels like smoking crack
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.