Are you using jitsi-meet and jicofo? Do you have e2eping enabled in config.js?
We would need more context to debug, but here’s what the message means: Endpoint A sent a targeted message to endpoint 8dd0d16d. Endpoint A’s bridge forwarded it to another bridge via octo, and the second bridge did not know about endpoint 8dd0d16d, so the message was dropped.
There are a few possible explanations:
- If there are 3 or more bridges in the conference, some of them will print this message. This is a bug I just noticed, and it’s completly harmless. The message would be logged periodically.
- There might be a race condition between an endpoint joining the MUC (so other endpoints know about it and start sending messages to it), and all bridges in the conference being updated with the info for the new endpoint. The message would be logged once.
- Something else that I can’t think of.
I am pretty sure that the only case where we use targeted messages is with e2eping, which means they are harmless. In fact, we recommend disabling e2eping in config.js because it’s onlly used to display an “end-to-end RTT” in the interface and requires a lot of messages especially for large conferences.