You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The authentication for the REST APIs is done with a random key generated during installation and shared.
Enables an SMB share to share audio files.
Work required for implementation on NethServer 8:
NethVoice: implementation of custom module installation
FreePBX Module: No significant modifications required
API: It is no longer possible to directly copy the files into the filesystem, but we can place them in the FreePBX module under the htdocs folder, which will expose them in /freepbx/contatta
The generation of the authentication key and tables, previously done by the installation event, should be moved to the install() of the FreePBX module
Sharing of recordings: A possible solution is to share the recording volume (and possibly the audio files) with sftpgo https://sftpgo.github.io/.
Estimated time:
1 - 8h: I thought of adding a volume from which the modules are taken and copied at the container startup.
2,3,4 - 8h: Possibly less, but some testing will be needed for the installation and update part.
5 - 8h: Using the sftpgo container seems straightforward; my concern is how to expose it, the routes, and what happens during NethVoice updates.
Additionally, some time will be needed for testing and writing an installation procedure.
The text was updated successfully, but these errors were encountered:
The Contatta module consists of three parts:
The authentication for the REST APIs is done with a random key generated during installation and shared.
Enables an SMB share to share audio files.
Work required for implementation on NethServer 8:
Estimated time:
1 - 8h: I thought of adding a volume from which the modules are taken and copied at the container startup.
2,3,4 - 8h: Possibly less, but some testing will be needed for the installation and update part.
5 - 8h: Using the sftpgo container seems straightforward; my concern is how to expose it, the routes, and what happens during NethVoice updates.
Additionally, some time will be needed for testing and writing an installation procedure.
The text was updated successfully, but these errors were encountered: