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

Signal silently fails on establishing calls when time is de-synchronised #9633

Closed
4 tasks done
szotsaki opened this issue May 18, 2020 · 5 comments
Closed
4 tasks done
Assignees
Labels

Comments

@szotsaki
Copy link


Bug description

Symptoms are very similar to #7733: caller calls the other party when the time on their phones are some minutes drifted away and callee sees only "You have a missed call" notification in the chat. The caller can continuously observe that Signal tries to connect but it won't succeed in the end.

The issue is the silent failure. A user cannot be expected to figure out that their call failed because of some minute deviance from atomic clock.

Steps to reproduce

  • Have two phones with their clock set some minutes off in both directions.
  • Try to call each other.

Actual result: Signal is just trying to connect but after a minute of trying the other party receives a chat message that they had a missed call.
Expected result: Signal warns the users that establishing this call is not possible because of the drifted time.

Device info

Device independent based on previous comments.

Comments which describe this behaviour:

@gab81
Copy link

gab81 commented Dec 13, 2020

hello, i have the same problem #10281 and our 2 phones that call each other have the very same time setting (although i think using this to make it work is a bit crazy), so that does not work.

@jknockaert
Copy link

Does anyone have an indication as to what the tolerance is for system clock accuracy? Android phones sync to cellular network provided clocks. Perhaps the tolerance limits used in Signal could be increased a bit to account for lazy syncing by android (and by cellular network opps)?

@Xashyar
Copy link

Xashyar commented Feb 19, 2021

Has this issue been solved via c591ec3?

@cody-signal
Copy link
Contributor

Hey Folks, thanks for sticking with us. We recently pushed some fixes and hopeful changes to calling in the latest 5.6 beta.

I'm hopeful it'll fix some issues for some of you but I believe gremlins are still lurking in calling. So, after updating to the beta, if you are still encountering the issues above please provide updated debug logs and anything interesting about your calling situation. Examples of things that are interesting: phone has non-standard hardware (like no camera), using bluetooth, in a region that has internet restrictions, using a VPN, etc.

@stale
Copy link

stale bot commented Jan 26, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Jan 26, 2022
@stale stale bot closed this as completed Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

5 participants