Hi,
is it possible to create a conversation with a user-defined, custom token?
Like custom-name in
https://mynextcloud.example/call/custom-name
Alternatively, is there a way to re-create a conversation with token custom-name instead of a random name?
I am using a Nextcloud Talk conversation to receive administration messages of network clients, as replacement of a local Postfix email server.
In case of accidental deletion of this conversation: Can I re-create it with same name instead of adjusting all clients to use a new conversation id?
Thanks for any hints, cheers.
Nextcloud version: 30.0.6
Talk Server version: 20.1.4
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no
Operating system: Debian
Browser name and version: Firefox ESR 128
Hm, no answer yet?
Some more details:
Clients currently can send Nextcloud Talk messages as guests like this (room should allow guests):
conversation_id="abcdef12"
# initiate guest session via cookies + optional room pw, then ...
curl \
"https://mynextcloud.example/ocs/v2.php/apps/spreed/api/v1/chat/${conversation_id}"\
-H "OCS-APIRequest: true"\
--data-raw "{\"message\":\"${message}\", \"actorDisplayName\": \"${actor}\"}"
This works well. But note that script is tied to a randomly generated room session "abcdef12".
If room accidentally gets deleted or is not available anymore for other reasons, I cannot re-create this conversation token and would need to adjust all 20 clients.
So my question would be: Is a stable token id possible (or token re-creation as workaround)?
After more investigation: Stable conversation token isn’t supported afaik.
You can enable Apache mods proxy and proxy_http as workaround, forwarding requests from a stable URL like https://mynextcloud.example/ocs/v2.php/apps/spreed/api/v1/chat/${stable_token} to URL of conversation token randomly created by Nextcloud Talk.
Note, Redirect cannot be used, as Nextcloud Talk API needs POST.