[10:41:20]
<lautre> Nextcloud-signaling server should be somewhere, isn't it?
[10:41:21]
<ljf> lautre i am not sure that having nextcloud-signaling in the same network than your local network is a good idea if you want to call from your local network
[10:44:42]
<lautre> In the interface, it's say that coturn working (may be stun too).
[10:44:52]
<ljf> (maybe if signaling is in the local network and stun outside it's ok)
[10:44:52]
<ljf> in the tuto: it uses coturn as stun, but stun can't be in the local network, cause if you try to contact it from the local network it returns a local ip and not the public IP (+ port)...
[10:44:52]
<ljf> Don't remember exactly, i made the nextcloud-signaling package 1 or 2 years ago...
[10:45:06]
<lautre> To ma, was for users (like other users than my local networks)
[10:45:39]
<lautre> In fact, I have the server, in an office. And, all users are outside
[10:45:44]
<lautre> There is NAT for IPv4
[10:46:05]
<lautre> I will think about what you wrote...
[11:29:42]
<lautre> I think, I misspeled something. I can't make the Nextcloud-Signaling working. It's always say "The connexion to the websocket failed".
It's not depending to the users.
But, may be it's because the Nextcloud and the Signaling are on the same VM Yunohost?
[11:29:52]
<ljf> if all users are outside, it could work
[11:31:17]
<lautre> I will try to finish to install Nextcloud-Signaling on other VM (same lan), may be...
[Will need time, for opening ports...]