Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Video calls: Conversations doesn't show Monal's video feed #1002

Open
5 tasks done
lissine0 opened this issue Feb 16, 2024 · 10 comments
Open
5 tasks done

[Bug]: Video calls: Conversations doesn't show Monal's video feed #1002

lissine0 opened this issue Feb 16, 2024 · 10 comments

Comments

@lissine0
Copy link
Member

What Monal Release channel are you using?

Alpha

iOS system version

16.7

iOS Monal version

Alpha 8669792 (Feb 15 2024 22:14:54 UTC)

macOS system version

No response

macOS Monal version

No response

Used XMPP server (domain)

Personal

Which XMPP-Server software are you using?

Prosody

XMPP Server Software Version

No response

How many accounts are you using in Monal?

1

What happened?

When doing video calls between Monal and Conversations (no matter who initiates them),
sometimes in Conversations, no video feed is received from my Monal contact.
Tested with Conversations 2.13.1+free

Anything else?

  • The bug happens about 50% of the time.
  • The logs from Monal and from Conversations were not taken at the same time.
  • I sent the logs through email.
  • The issue doesn't exist with Dino. I didn't test with other clients (yet).

FAQ

Considerations for XMPP users

Related Issues

XEP-Check

  • I have checked that at least XEP-198, XEP-0280, XEP-0352, XEP-0357, XEP-0313 and XEP-0163 are activated on my server and shown as 'green' under Settings --> Account--> (i) in advanced settings

Notifications-Menu

  • I have checked that all checkmarks are present under Settings --> Notifications
@lissine0
Copy link
Member Author

Update: this bug also happens with Beagle IM.
So it's more likely the issue is on Monal's side.

@madfoss
Copy link

madfoss commented Feb 19, 2024

This bug also happens between Monal users.

@tmolitor-stud-tu
Copy link
Member

If I check the log on a Monal device only seeing black (e.g. Monal-to-Monal videocall), I get the following logged by webrtc.
The SSRC mentioned is one of the 2 SSRCs the webrtc implementation negotiated as SSRC-group: <ssrc-group><source ssrc='3411384671'/><source ssrc='2730024798'/></ssrc-group>
I don't have any clue why and I don't know how to fix that either :(
Comparing the jingle negotiation with Conversations (which uses webrtc, too) gives no visible difference (both negotiate a SSRC-group containing 2 SSRCs).

(webrtc_video_engine.cc:3182): Creating default receive stream for SSRC=3411384671.
(webrtc_video_engine.cc:2846): AddRecvStream (default stream): {ssrcs:[3411384671];ssrc_groups:;stream_ids:;}
(webrtc_video_engine.cc:2823): Receive stream with SSRC '3411384671' already exists.
(webrtc_video_engine.cc:3185): Could not create default receive stream.
(webrtc_video_engine.cc:3240): No stream found to set base minimum playout delay
(webrtc_video_engine.cc:3003): SetSink: ssrc:3411384671 nullptr
(call.cc:1405): Failed to demux packet 3411384671
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.
(webrtc_video_engine.cc:3152): Another unsignalled ssrc packet arrived shortly after the creation of an unsignalled ssrc stream. Dropping packet.

The last message gets repeated several times, then a whole cycle is starting over again (e.g. the first message cited here).

@jpggithub
Copy link

I have the same bug using Monocles (Android) with a person who use Monal 6.2.0 : can't see his video feed 50% of the time

@sailoona
Copy link

I also tried video call twice, all I get from conversations is a black screen. I gave it up.

@tmolitor-stud-tu
Copy link
Member

tmolitor-stud-tu commented Jun 30, 2024 via email

@jpggithub
Copy link

Approximatively 50% of the time, I can't see the video feed of a person using Monal 6.4.0.
I personally use Monocles (Android).
I switch off the conversation (sometimes 2-3 times) and then I can see the video feed.

@tmolitor-stud-tu
Copy link
Member

@jpggithub Known bug, but no known fix. Try to fix it yourself and create a PR if you want to help :)

@jpggithub
Copy link

Don't misunderstand me, I only found useful to confirm the bug for this version because I see "Improve AV-Call connectivity (allow incoming P2P connections)" in the changelog. So I tested it again, that's all. I have no abilities to fix the bug myself...

@lameventanas
Copy link

I just experienced this bug between Monal and Conversations.
I hope it's fixed soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants