Nextcloud Talk 24.0.3 issues a warning of a missing feature_changed_users

[kaynemo]

Hi all!
Nextcloud Talk 24.0.3 app issues a yellow warning that a changed_users feature connecting to 2.1.1 signaling server.

2.1.1 signaling server
X-Spreed-Signaling-Features: audio-video-permissions, chat-relay, dialout, federation, hello-v2, incall-all, join-features, mcu, offer-codecs, recipient-call, serverinfo, simulcast, switchto, transient-data, transient-sessiondata, update-sdp, welcome

24.0.3 Talk
sed -n '/getSignalingServerMissingFeatures/,/^\t}/p' apps/spreed.24.0.3.bak/lib/Signaling/Manager.php
$missingFeatures = $this->getSignalingServerMissingFeatures($features);
if (!empty($missingFeatures)) {
return [
'status' => Http::STATUS_OK,
'data' => [
'warning' => 'UPDATE_OPTIONAL',
'features' => $missingFeatures,
'version' => $data['version'],
],
];
}

		/**
		 * Store appconfig for some optional features that require different
		 * behaviour on PHP backend side
		 */
		if (in_array('changed-users', $features, true)) {
			$this->appConfig->setAppValueBool(Manager::HAS_FEATURE_CHANGED_USERS, true);
		}

		return [
			'status' => Http::STATUS_OK,
			'data' => [
				'version' => $data['version'],
			],
		];
	} catch (ConnectException) {
		return [
			'status' => Http::STATUS_INTERNAL_SERVER_ERROR,
			'data' => [
				'error' => 'CAN_NOT_CONNECT',
			],
		];
	} catch (\Exception $e) {
		return [
			'status' => Http::STATUS_INTERNAL_SERVER_ERROR,
			'data' => [
				'error' => (string)$e->getCode(),
			],
		];
	}

}
protected function getSignalingServerMissingFeatures(array $features): array {
	$optionFeatures = [
		'dialout',
		'join-features',
		'chat-relay',
		'changed-users',
	];

	return array_values(array_diff($optionFeatures, $features));
}

Just thought you should know. The missing feature is an "update optional" class, but I am sure a lot of people running a setup similar to mine will freak out.

[Wohlstand]

I built a latest dev version (the top of branch "master"), and the warning is still be. This also happens on my side too!

[ziomimmo77]

I am experiencing the same issue; the warning showed up right after upgrading Talk to version 24.0.3

[Pouriyan]

Hi,
I’m seeing the same warning after upgrading my Nextcloud environment.

Current setup:

• Nextcloud: 34.0.2
• Talk / spreed: 24.0.3
• nextcloud-spreed-signaling: 2.1.1~docker
• Janus: 1.4.1
• NATS: 2.10.27
• Deployment: Docker Compose, dedicated HPB/signaling server

The signaling service itself seems to be working correctly. All HPB-related containers are healthy, and the signaling server is reachable both internally and through the public endpoint.

Health/connectivity checks:

curl -sS https://talk.example.com/api/v1/welcome

returns:

json
{"nextcloud-spreed-signaling":"Welcome","version":"2.1.1~docker"}

The signaling logs also show successful connections to NATS and Janus:

text
Connection established to nats://nats:4222
Connected to Janus WebRTC Server 1.4.1
Using janus MCU
Listening on 0.0.0.0:8080

However, in the Nextcloud Talk administration page I still get this warning:

text
Running version: 2.1.1~docker; Server does not support all features of this Talk version, missing features: changed-users

So from my side, the HPB/signaling stack appears to be operational, but Talk 24.0.3 seems to expect a feature named changed-users that is not advertised/supported by the current 2.1.1~docker signaling release.

Could you please confirm whether support for the changed-users feature is already implemented in the source code but not yet available in the official Docker image, or if it is planned for a future release?

Also, is it safe to keep using 2.1.1~docker with Talk 24.0.3 in production while waiting for the next signaling release, assuming calls and MCU functionality are working normally?

Thank you for your work on this project.

[fancycode]

The message / feature is about an optimization that will be part of the upcoming release of the signaling server (see #1175 for details).
Nextcloud Talk will still work as before with older versions as the Talk app only enables the new functionality after the signaling server has been updated.

Feel free to subscribe to #1175 to get notified when this is merged.

[klimenkotolik]

same here :)

[crocobc]

hi there, Same problem also regards

[philotma]

Hi all, It's still the same for me since few time. I'm waiting about a new version of nextcloud-spreed-signaling to compile or a new version of Talk without this feature. So I have role back of nextcloud 34.0.1 ( before 34.0.2) with Talk 24.0.2.

[fancycode]

As written in #1283 (comment) Talk will work as before without this feature, there is no need to rollback any versions of Talk because of this warning.

Also see nextcloud/spreed#18846