Phonebook for VoIP phones
Make your Odoo contacts available from VoIP phones
This module is used as XML user directory service for different VoIP phones.
Supported IP phones:
- Digium A & D Series
- Odoo 9, 10, 11 and 12 support.
- IP based ACL to restrict access to phonebook only from LAN.
- Support for your phone model can be added on your request...
If your installation is a single db (using db_filter) you have to do nothing.
If you have many databases then add phonebook to your server_wide_modules setting, e.g.:
; for Odoo 9 and 10 server_wide_modules=web,web_kanban,phonebook ; For Odoo 11 and 12 server_wide_modules=web,phonebook
Activate Developer mode and go to Settings -> Technical -> Parameters -> Phonebook.
Adjust settings for your environment.
Open your phone settings and set XML phonebook URL. URL is made of your Odoo server address, db name and phone model.
Let demonstrate it with the following example.
- Odoo server address: http://my.odoo.com:8069
- Database name: demo
- Phone model: Grandstream
For single Odoo db installation (db_filter is used) the following URL is constructed:
For multi database Odoo environments database should be injected in the path:
- http://my.odoo.com:8069/phonebook/demo/gs/phonebook.xml (note demo in the path)
Aastra phones download CSV file with contacts via TFTP. So with Aastra phones you should setup a cron script to periodically update file with contacts. Example:
curl -o phonebook.csv http://my.odoo.com:8069/phonebook/demo/aastra/phonebook.csv
Atcom phones support HTTP phonebook feature. Example URL: http://my.odoo.com:8069/phonebook/demo/atcom/phonebook.xml
The Configuration file can include a link to a user-defined Corporate Directory file, using the 'provisioning/corporate_directory_uri' parameter.
For example: provisioning/corporate_directory_uri=phonebook.csv
You need to create a cron script to periodically reload the phonebook from Odoo and put it into provisioning folder.
curl -o phonebook.csv http://my.odoo.com:8069/phonebook/demo/audiocodes/phonebook.csv
Remote retrieval, as a part of the phone's configuration file, is controlled with the AUTOUPDATE CONFIG MODULE configuration section with the Auto Pbook Url configuration parameter, e.g.:
<<VOIP CONFIG FILE>>Version:2.0000000000 <AUTOUPDATE CONFIG MODULE> Auto Pbook Url :http://my.odoo.com:8069/phonebook/demo/digium_a/phonebook.xml <<END OF FILE>>
Contacts files that the phone should load are separate files, defined by DPMA or configured in the phone's main configuration XML file. For DPMA, Contacts files are specified for a phone configuration using the phone configuration parameter: contact as noted above.
Multiple "contact" lines may be used for each phone configuration.
For XML configuration, Contacts files are specified using the <contacts> element.
Go to PHONE -> REMOTE CONTACT -> Remote Phonebook Settings.
Add phonebook URL in the Server URL field. Example URL: http://my.odoo.com:8069/phonebook/demo/fanvil/phonebook.xml
Grandseam phones add phonebook.xml to server URL. So You should specify only the part of URL. Example: http://my.odoo.com:8069/phonebook/demo/gs/.
Set Network -> Application Settings -> Enable Application [YES].
Set Telephone -> Application Settings -> Network Phonebook URL to http://my.odoo.com:8069/phonebook/demo/panasonic/contacts.xml.
As Polycom phones cannot get contact book from HTTP you need to create cron script that will periodically download contacts from Odoo and put it in your TFTP server root where your phones are provisoned.
curl -o 000000000000-directory.xml http://my.odoo.com:8069/phonebook/demo/polycom/phonebook.xml
Refer to Polycom provision documentation for details or contact for support.
Add phonebook URL to <setting-files> tag. Example URL: http://my.odoo.com:8069/phonebook/demo/snom/phonebook.xml
According to documentation SNOM phones can store 100-250 directory entries. If you require some way to filter contacts that go to SNOM phones contact me for a discussion.
You can easily customize phone templates.
Go to Settings -> Technical -> User Interface - Views.
Type phonebook in the search fields and press enter. You will see all templates of this module.
Find one that is required and customize it.
I have collected some links for your convinience. Please let me know if some links get broken.
- Response header fix (returns text/xml instead of text/html).
- Settings page and HTTP auth option for phones models supporting this option.
- Aastra phones support added.
- Yealink phones support added.
- Atcom phones support added.
- Panasonic phones support added.
- Digium phones support added.
- Audiocodes phones support added.
- SNOM phones support added.
- Fanvil phones support added.
- Odoo version 10.0 module release.
- Polycom phones support added.
- Initial release with Grandstream support.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.