Your message dated Wed, 24 Jan 2024 09:35:09 +0000
with message-id <[email protected]>
and subject line Bug#1060286: fixed in nextcloud-spreed-signaling 1.2.2-3
has caused the Debian Bug report #1060286,
regarding nextcloud-spreed-signaling: Not able to connect to MCU (payload does
not contain a valid sdp)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1060286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060286
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: nextcloud-spreed-signaling
Source-Version: 1.2.2-3
Done: Mike Gabriel <[email protected]>
We believe that the bug you reported is fixed in the latest version of
nextcloud-spreed-signaling, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel <[email protected]> (supplier of updated
nextcloud-spreed-signaling package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 24 Jan 2024 10:12:19 +0100
Source: nextcloud-spreed-signaling
Architecture: source
Version: 1.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Mike Gabriel <[email protected]>
Closes: 1060286
Changes:
nextcloud-spreed-signaling (1.2.2-3) unstable; urgency=medium
.
[ Mike Gabriel ]
* debian/patches:
+ Drop build-with-sdp-3.4.patch. Resolved upstream (and wrong approach).
See: https://github.com/strukturag/nextcloud-spreed-signaling/pull/301
and https://github.com/strukturag/nextcloud-spreed-signaling/issues/
279#issuecomment-1196857450. (Closes: #1060286).
* debian/changelog:
+ Adjust @fancycode's real name in previous upload stanza.
.
[ Joachim Bauch ]
* debian/control:
+ Adjust dependencies under Suggests: fields.
Checksums-Sha1:
0bdc2d23e4f971eba34f11d3b7c7d42d98a0f478 3140
nextcloud-spreed-signaling_1.2.2-3.dsc
9cfe7c2721b37ee31fa48887eade7e5ac2b19e63 17652
nextcloud-spreed-signaling_1.2.2-3.debian.tar.xz
76fc2e03f670faff4566b080aa95336a81a10048 7061
nextcloud-spreed-signaling_1.2.2-3_source.buildinfo
Checksums-Sha256:
f4a94e0f29fcfae5a2e98deba367aaf8a7f0903443047bed887463b3d592955f 3140
nextcloud-spreed-signaling_1.2.2-3.dsc
e678701a4057598f206c47597cbd24f999ae23caac88800321ba857a911a15f9 17652
nextcloud-spreed-signaling_1.2.2-3.debian.tar.xz
8100421483162dee6b07c6139b51ffc932eb17e3fe8a8a5371b10231060da49c 7061
nextcloud-spreed-signaling_1.2.2-3_source.buildinfo
Files:
935bc71cf1d9c97734d19d89b477742b 3140 golang optional
nextcloud-spreed-signaling_1.2.2-3.dsc
48029a0a0ed5dd7d298579b9d5f8341a 17652 golang optional
nextcloud-spreed-signaling_1.2.2-3.debian.tar.xz
9b3506d8a084922cf70a84bf6f17b26a 7061 golang optional
nextcloud-spreed-signaling_1.2.2-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmWw1hEVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxBWAP/judeVGKjpzxVxKz4oiGQ8Zcp3em
WbwndydUEjG2TMuDXyhOhovc4PzyJNj/i0wFi+yX0E2lm8lDTBolQSFZcAcB/3X9
FQZdppsUyY9/BvpC7Nwnl4bWNCwKsBUg2scYlX9tGnejMZ97Izh1vdJBxwaPz2B2
2qrfuw+XBXL4gR/v6cXnce1/PnXNnKLJzRfB7eTYgvsuFxvTd017noxd0OJNpr0c
wJOjyL+2gFoNu4MWysnUCXn1ScwM/WMqrSM2O2buAq3G2d7rSGi56AQTueIL88ax
Woop8QhO0i+3f5O9Iaav8sm9eE58L6YEiuGZatltHbVXM43PAWvmzZURKHEs5N5v
bj7Dm8f83merBZ5ovQ6eAp9hT4X5a3xinV0cuKdQgXTl5YnOE7ls45HsVzC3JjZD
i1PPZ3IqI5CQmbSlTJpAj304Hi5Yv/SK5bzo3XTQpzg1sB6kl/ngVZJn5B+Aw49y
5cQZU/BsHLW4BbTexOjxQrJYAJKFw8HllEeF+N9J6cj9r6jhkgypK98mxGe62wh6
oxtDsrM7T553V5dXkvUWYmgJcgx/kox5dj7dmX9Y7ToaxWs+h4WPITH/xn4MlWj+
zy3GHhGbXNVYe+eaEd8IqDpLpOHeoGxu55B1EjPZmyL22XZX9Dki8bMoW4mhOXFq
51ePg7Cc40UuXvh7
=Tw8L
-----END PGP SIGNATURE-----
--- End Message ---
