nextcloud / nextcloud/talk-android

Sometimes call seems to start, but doesn't

Open
#4,861 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug feature: call ☎️
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

Steps to reproduce
  1. Start a call in Talk Android
  2. End the call in Talk Android
Expected behaviour

The attempted call should happen and leave a record in the chat.

Actual behaviour

After dropping the attempted call, no trace of it is found in the chat. Basically the attempted call never took place, but the user has the impression that it did.

Device brand and model

Murena Teracube 2e

Android version

12

Nextcloud Talk app version

21.0.0

Nextcloud server version

31.0.2

Talk version

21.0.1

Custom Signaling server configured

Yes (specify version in Additional Information)

Custom TURN server configured

Yes

Custom STUN server configured

Yes

Android logs

No response

Server log

Additional information

It doesn't happen every time I start a call, but it when it does, it does against a Nextcloud and Talk HPB server (Signaling, HPB and TURN) that otherwise works fine. It saw it happening only on 1-to-1 conversations, but mainly because I don't do group calls in that server.

Closing/reopening the app solves the problem.

The problem also used to happen on another device, also with /e/os, and a recent version of Talk Android and server-side components. In that case, I suspected it was somewhat related to multi-account, but in this device, I don't have multiple accounts and never had.

I would be happy to provide logs (Android) but I need guidance to extract them.

Signaling Server version:2.0.2
coTURN version: stock version on Ubuntu 24.04
Janus: 1.3.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the intermittent missing-call-record issue in Talk Android using the reported Android, Talk, signaling, TURN and Janus versions. Collect Android logs as requested in the issue and compare one-to-one calls that leave a chat record with those that do not. Done means the cause is identified and the attempted call reliably leaves the expected trace, with regression coverage if the affected code path is located.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
audio-video-rtc, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.