A client asked recently for a phone book to replace the contacts within FusionPBX with something similar to use. So here it is, our first version.
At the moment it only supports Yealink, we'll be adding more phones as and when we have time. Please report any bugs. Once we have some additional phone support and any bugs ironed out, we will submit it to the project.
To use it, untar the file into your FusionPBX apps folder, this can usually be found at /var/www/fusionpbx/apps.
Once you have done that you will need to go to advanced/upgrade and go through all the options one at a time except update source.
Log out then back in and in the Apps dropdown you should see a new entry phonebook.
There is an import function but this will only work with existing Yealink phonebooks.
I hav added a short video showing how to use it but I expect most will be able to work it out for themselves.
If you are using provisioning, for each phonebook entry you will need to add a pair of variables similar to:
yealink_remote_phonebook_1_name
yealink_remote_phonebook_1_url
yealink_remote_phonebook_2_name
yealink_remote_phonebook_2_url
etc,etc
Because the phonebook will be being deployed over https you will need a real certificate on the server or change the following security setting on the Yealink phones:
Video if you need it:
At the moment it only supports Yealink, we'll be adding more phones as and when we have time. Please report any bugs. Once we have some additional phone support and any bugs ironed out, we will submit it to the project.
To use it, untar the file into your FusionPBX apps folder, this can usually be found at /var/www/fusionpbx/apps.
Once you have done that you will need to go to advanced/upgrade and go through all the options one at a time except update source.
Log out then back in and in the Apps dropdown you should see a new entry phonebook.
There is an import function but this will only work with existing Yealink phonebooks.
I hav added a short video showing how to use it but I expect most will be able to work it out for themselves.
If you are using provisioning, for each phonebook entry you will need to add a pair of variables similar to:
yealink_remote_phonebook_1_name
yealink_remote_phonebook_1_url
yealink_remote_phonebook_2_name
yealink_remote_phonebook_2_url
etc,etc
Because the phonebook will be being deployed over https you will need a real certificate on the server or change the following security setting on the Yealink phones:
Video if you need it: