nextcloud-spreed-signaling icon indicating copy to clipboard operation
nextcloud-spreed-signaling copied to clipboard

Published 20 hours ago • verified publisher icon strukturag

Connection Problem with Signaling server

Open markkhanippbx opened this issue 2 years ago • 3 comments

Hi I'm using Nextcloud 23. After updating I installed a fresh signaling server using following steps.

https://morph027.gitlab.io/blog/nextcloud-spreed-signaling/

Now all is fine on server end it is connecting with NC23 with url and key. But when joining the call error comes on both ends saying connection problem.

image

Janus server is updated and running.

markkhanippbx avatar Aug 12 '22 22:08 markkhanippbx

I have the same issue. I had also posted here but didn't get solution. please someone advise here.

zohaib09 avatar Aug 13 '22 16:08 zohaib09

Did you tried with different browsers?

muchachagrande avatar Aug 26 '22 16:08 muchachagrande

Please check chrome://webrtc-internals for problems. Are your users behind a firewall / proxy / NAT and did you configure a STUN and TURN server? Most likely this is related to the clients not being able to connect to the Janus WebRTC gateway.

fancycode avatar Aug 30 '22 08:08 fancycode

Hi *, multiply users have the same problem with the current version, nothing on user side has changed. I think we had good results with the version with the hash: ddb7ece62244131b2eec3a91c8d4df074665d2b0

The issues started after upgrade to v1.0.0 Tag.

In the new version some persons do not hear or see some other persons. Multiply retries will fix this randomly. It seems that persons with slow internet have more issues than persons with fast internet. So maybe the issue could be a timeout setting or reconnect count or something similar.

I have to downgrade as the new version can not be used any longer. If the issue remains after the downgrade I will leave another message here.

Of course, it is still possible or perhaps even likely, that the issue is related to janus or coturn, but it is really hard to discover these details as user. If the issue comes with the dependencies it could be nice if at least the docker-compose version would link valid versions.

I'm using a valid certificate and the ports for coturn are not blocked from ISP or locally. The problem remains. Additionally, the issues seems to be browser independent. Possibly some browsers have slightly better results, but it is hard to measure.

Thanks for reading and best regards!

masterxq avatar Nov 11 '22 02:11 masterxq

The signaling server does not transmit audio/video, so I doubt that the problem is related to the signaling server. Most likely there is a problem with the Janus / STUN / TURN setup where as a result some clients can't connect to the Janus gateway.

Debugging such connectivity issues is out of scope for the signaling server, please open a issue at the Nextcloud community support for Talk at https://help.nextcloud.com/c/support/talk/52.

fancycode avatar Jan 17 '23 12:01 fancycode