Recently, I updated my FOP2 to the latest version (2.31.36, on August 15, 2023) which brought some new features mainly in the phonebook part.
The module was reformulated, but I noticed that after the update the CID Superfecta module was no longer recognizing the FOP2 contacts (it recognized what was saved in the cache, but not the new contacts).
When checking the error, I realized that it was something related to a variable.
I was curious, I went to check the database to see if there were differences in the visual_phonebook table between the most updated version of FOP2 and the previous version and… yes!
In the previous version, the FOP2 phonebook table was simpler - all the information was on it (name, last name, company, and number)
In this most recent version, the FOP2 Phonebook was divided into 4 - visual phonebook, visual phonebook_phones, visual phonebook_tags and visual phonebook_contacts - these tables are related to each other to feed the structure of the FOP2 phonebook module.
See the before and after structure:
FOP2 Visual Phonebook (before - it is based on this structure that the current CID Superfecta searches)
FOP2 Visual Phonebook - After
FOP2 Visual Phonebook Phones Content
As some clients I serve have already updated FOP2 and use this function, I will try to adapt the FOP2 Source query to search under this new structure - and if it works, I will share the adapted code here.
But it would be cool if this function came natively in FreePBX in future updates of the superfecta module - is there any way to open a ticket for sangoma to analyze the possibility of including this in a future update?