I am trying to figure out how to provision my Yealink phones on my Raspi, which does not support EndPoint Manager. I have read https://wiki.asterisk.org/wiki/display/AST/Phone+Provisioning%2C+Putting+it+all+together.
However, when I type
http show status
The result is that the http command is not found. Any ideas?
Enable the http mini server in Advanced Settings.
You could just get the template, put the settings in, name it MAC.cfg (MAC being the actual MAC no :'s) and put it in /tftpboot
What is the miniserver and is it documented anywhere?
I was able to solve the problem by entering the Asterisk CLI, where http is a command. You can enter the Asterisk CLI by typing
asterisk -r
at a command prompt. Anyway, enabling the miniserver did not make http a valid shell command.
@BlazeStudios Where do you get the template? How do you get the phone to communicate with the FreePBX server to get the config file? Do you use a STUN server like googleâs, or an SBC?
Yealink should have them on their site somewhere. As for the rest, since youâre on a RasPi you would have to install a TFTP service and setup /tftpboot as the default directory.
Also, if youâre just provisioning a phone and not using anything special (macroâs etc) on the Yealink, just log into the Yealinkâs GUI and program it.
Uh, Iâll have to read up on how to do that thing with TFTP. Do you have a pointer to that? The Asterisk manual doesnât mention TFTP. It says
With the above examples, the phones would be pointed to:
http://192.168.1.1:8080/asterisk/phoneprov
for pulling config files.
Any idea how to point the phone to a particular IP address?
And what do you mean by âJust log into the Yealink GUI and program it.â
You need to get the Yealink Admin/User manuals and read them. Now you are asking about Yealink phone stuff that is not a FreePBX issue. Once you do that youâll realize how easy these phones are to program and if you only have 1 or a handful it will be better than using that old Asterisk method that no one uses anymore because it sucked.
Part of the problem with all this is, you donât know what the phones are capable of or where things are in the phone itself. So you need to learn the phone first then worry about making a provisioning server for it.
Are you saying that you can provision phones without creating templates in Asterisk?
Yes, twice now. Please go read the Yealink manuals.
OK. Most of our users just use their mobile phones. Only a couple of us have Yealink phones. What about iPhones? Is there a softphone for those? How do you provision those?
Again, you would have to find a softphone youâd want to use. Something like Bria and then just like I said with the Yealinks, you need to read the Admin/User manuals. All of this is in those manuals, thatâs why they have them. You need to do some research and figure out what the best options for you are going to be.
I found the Yealink manual. It is 556 pages. Should keep me busy this winter trying to provision my phones! Thanks.
If you dont want to read manuals or watch youtube videos, hire Sangoma support.
Thatâs a rather absurd suggestion consider the hourly cost of Sangoma support and the fact this is a Yealink thing not a Sangoma thing. Sangoma support is not there to provision your third party vendor phones.
This isnât that hard. Get IP of phone, go to http://ipofphone and enter default admin user/pass. Configure phone. Not only is this covered in the User/Admin manuals but the Quick Start Guide that is available and generally comes in the box with the phone.
This is like 30 minutes of work for everything.
I donât think provisioning the phone is in the Quick Start Guide. But it is in the Admin Guide (pp 61-69) as you suggested. There are some chapters on where to put the rom file and some other files. Then, I will have to do the same thing for the iPhone app (Bria), and figure out how to tell remote users how to provision their phones. Maybe 30 minutes of work for some, but not meâŚ
STOP. You have not listened to a thing I have said. You can LOG INTO THE PHONES GUI AND SETUP THE PHONE THAT WAY.
Stop with this damn provisioning server thing. I have kept saying that if you have a small amount of phones and arenât doing anything advanced on it (and it doesnât sound like it) then you can just use their GUI to setup the accounts. This is like 5 minutes of work PER PHONE.
Again, why donât you figure out how these phone actually work and what they can do before you start worrying about setting a provisioning server for them and what it should be doing.
Sorry. When I say provision, I mean connect the phone to the PBX. Apparently, that means that you have to put a boot file, config file, and resource file up on the PBX, and then point the phone at the PBX as described in pp 61-69 of the Admin manual. Unless I have misunderstood your suggestion.
I do not see how that could possibly be five minutes of work to read those pages, create the files, and carry out the procedure, which is apparently very error prone.
A provisioning server would be necessary for remote users. I would also have to figure out how to tell them how to do it.
No it does not. It means you do what I have been saying this entire time. Log into the phones GUI and SET UP THE ACCOUNT. The Admin guide would have things like âHow to Connect to Phone GUIâ and âHere are the default ADMIN username and passwords.â and âHereâs how to change the default admin passwordââŚ
Did you notice that many of those pages have screenshots of the phone GUIâs interface with instructions on not only how to program the features via the GUI but the corresponding config file settings?
Ah, page 73:
Phone User Interface
Phone user interface makes configurations available to users and administrators; but the Advanced/Advanced Settings
option is only available to administrators and requires an administrator password (default: admin).
You can configure IP phones via Phone user interface on a per-phone basis.
That must be what you mean. Although it still seems you have to load a bunch of files onto the PBX first. That chapter pp 73-91 discusses provisioning servers, and four different methods of getting the files onto the phone.
Here is the manual:
Stop.
Take a breath.
Take another breath.
Now forget the word âprovisioningâ, erase it from your vocabulary. You want to configure a phone to REGISTER to a SIP server. Once the extension has been created on the PBX, you will login to the PHONE GUI and configure it to register to the PBX. If this takes longer than 10 minutes you are doing it wrong. If you create a single text file you are doing it wrong. If you touch anything other than the phone you are doing it wrong.