Package: nextcloud-spreed-signaling
Version: 1.2.2-1~bpo12+1
Severity: normal
Dear Maintainer,
The backports version of nextcloud-spreed-signaling seems not to be able
to connect to janus-gateway, while the self-built signaling server from
the same version (1.2.2) works fine.
* What exactly did you do (or not do) that was effective (or ineffective)?
Installation of package (bookworm-backports) and testing the signaling
server with janus and nats-server, configured as described in the readme.
* What was the outcome of this action?
The nextcloud-spreed-signaling server as packed in the Debian package
cannot establish connection to MCU.
* What outcome did you expect instead?
Signaling server connecting to janus as MCU.
I tried to set up nextcloud-spreed-signaling server in conjunction with
janus (1.1.2-1) and nats-server (2.9.10-1).
The configs are as follows:
/etc/janus/janus.transport.websockets.jcfg contains:
general: {
json = "indented"
ws = true
ws_port = 8188
ws_interface = "lo"
wss = false
}
and the signaling configuration in
/etc/nextcloud-spreed-signaling/server.conf
[mcu]
type = janus
url = ws://127.0.0.1:8188
(Same with localhost:8188 as ws url) Janus seems to work as intended. I
have build nextcloud-spreed-signaling from source of the latest release
(1.2.2) which is the same version as the packed version. When running
the self-built signaling server with the same config files the signaling
server works fine.
When using the signaling server from the Debian (bookworm-backports)
package and attempting to connect, janus seems to work, reading from the
logs (when debug logging is turned on):
mcu_janus.go:292: Connected to Janus WebRTC Server 1.1.2 by Meetecho s.r.l.
mcu_janus.go:298: Found JANUS VideoRoom plugin 0.0.9 by Meetecho s.r.l.
mcu_janus.go:303: Data channels are supported mcu_janus.go:307:
Full-Trickle is enabled
mcu_janus.go:309: Maximum bandwidth 1048576 bits/sec per publishing stream
mcu_janus.go:310: Maximum bandwidth 2097152 bits/sec per screensharing
stream
mcu_janus.go:316: Created Janus session 6409739776862493
mcu_janus.go:323: Created Janus handle 2619322330759171
main.go:263: Using janus MCU
hub.go:387: Using a timeout of 10s for MCU requests
backend_server.go:98: Using configured TURN API key
backend_server.go:99: Using configured shared TURN secret
...
However, the nextcloud-spreed-signaling server shows not to be able to
connect:
clientsession.go:281: Permissions of session XY changed: [publish-audio
publish-video publish-screen control]
hub.go:2161: Session XY sent unsupported offer video, ignoring (payload
does not contain a valid sdp)
room.go:665: Session joined call XXXXXX
hub.go:2193: No MCU publisher found for session XY to send ...
As the self-built signaling server from the same version works fine, I
suspect there might be an error in the Debian package of the
nextcloud-spreed-signaling.
Best regards,
Gerald
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-17-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nextcloud-spreed-signaling depends on:
ii adduser 3.134
ii libc6 2.36-9+deb12u3
Versions of packages nextcloud-spreed-signaling recommends:
ii janus 1.1.2-1
ii nats-server 2.9.10-1+b3
nextcloud-spreed-signaling suggests no packages.
-- Configuration Files:
/etc/nextcloud-spreed-signaling/server.conf changed [not included]
-- no debconf information
