The problem of the shop has been solved and it is possible to purchase licenses for supervisors and queues. However, I repeat, that it does not seem to me the correct way to carry out the project, for every small change there is an infinite number of elements to consider. Let’s start in order
The system went into block because more than one user was associated with more than 2 queues, so until the removal of this configuration it was not possible to apply any changes and this after the update of the various modules for a license change. Maybe you should have warned before (but even today when you update a module you no longer know anything about what has been updated and/or modified, unlike before, when it was enough to click in the module history to understand if a possible update was destructive for the customer, I had already spoken about it and asked Support, but there is no solution since the links to issues.freepbx.org/ now generically point to github)
The block was bypassed only with a direct query in the asterisk mysql database to trace which users had these configurations, an undocumented fact.
If the software is still in demo until January 31st why insert these limitations without warning customers? and also find yourself with open cases in support?
This beta liicense is still valid until 31 January 2025. Also, if the beta licence is still present on the PBX (before 31 Jan), the PBX will NOT use the purchased licence.
Therefore, you will need to delete the beta licence files manually, if you want to use your purchased licence.
Please delete the following files from your PBX:
/var/spool/asterisk/tmp/scd_queue_enable_call_control
/var/spool/asterisk/tmp/scd_enable_call_view_monitor_permission
/var/spool/asterisk/tmp/scd_queue_enable_vis_perms
Then restart the PBX. Run the following command on the PBX console:
fwconsole restart
Even by purchasing the licenses things don’t work. First the system detects that there is still a beta license and therefore you have to manually provide this series of activities (where is the documentation ???) further complicating things
Once this is done, if you try to buy the licenses in the store you have a further error… “You hace to renew thi item before adding new ones” what does it mean? Another case open to Support
Now I understand the beauty of an open system, in continuous development and so on, but the question is WHY do you have to complicate the life of customers who regularly pay for commercial modules?