Install the Nextcloud app
The app is the Nextcloud half of the system: the meeting list, the settings, the chat commands and the files. It does not record anything itself — that is the connector's job, and the two find each other through one key.
Before you start
- Nextcloud 30 or newer, with Talk installed.
- A High Performance Backend for Talk. Not optional: per-speaker audio is what makes a transcript say who spoke, and without an HPB there is no per-speaker audio to take.
- An account on this service — the key comes from there.
- Shell access to run
occ, or an administrator who has it.
1. Install the app
Unpack the release into your Nextcloud apps/ directory and enable it:
tar -xzf voxonta-3.0.0.tar.gz -C /path/to/nextcloud/apps/
sudo -u www-data php occ app:enable voxontaA Meetings entry appears in the top bar. It is empty until the first call is transcribed.
2. Give it a key
In Administration settings → Voxonta, paste the service key from your account. The app checks it immediately and says so if the service does not answer.
The same key goes into the connector in step 3. One key covers both directions: the connector asks the app which calls are live, and the app asks the service what a finished call produced.
3. Connect the capture service
The connector runs outside Nextcloud, on the same machine as your Talk High Performance Backend. It needs three things:
NEXTCLOUD_URL | Where your Nextcloud lives, e.g. https://cloud.example.com |
|---|---|
APP_SERVICE_TOKEN | The same key you pasted in step 2 |
GATEWAY_TOKEN | Your service key, from your account |
Running it yourself is described in a page of its own. If we host the connector for you, this step is already done.
/apps/voxonta/api/v1/service/calls every five seconds; if that
answers 404 or 401, no call is ever seen. This exact mistake cost us a week
of silent blindness, so the connector logs it loudly — check its log first
when nothing is transcribed.
4. Hold a test call
Start a call in any conversation, say a few sentences, and hang up. Within a minute or two you should see the transcript in Meetings. The summary and the analysis arrive later — usually within the hour, sometimes longer for a long meeting.
If nothing appears, in this order:
- The connector's log — does it say Call monitor started, and does it see the call?
- Administration settings → Voxonta — does the service report itself as seen recently?
- Whether anybody actually spoke. A silent call produces an empty transcript, and that is a correct answer rather than a failure.
Chat commands
/no-record | Stop transcribing this call |
|---|---|
/record | Resume |
The commands reach the app through a Talk bot, which has to be enabled in the
conversation — that is the occ talk:bot:setup step, and it is separate
from anyone joining the room. In practice they work in the group and public
conversations where the bot was set up, and not in one-to-one calls, where it
normally is not. Sent up to five minutes before a call, the command prevents
transcription from starting at all.
Where the files land
Transcripts and analyses are written by a service account into its own folders, then shared with the people who were in the call. In a group conversation the app also posts the links into the chat; in a one-to-one it cannot, so the share is the notification.