Calls always income as missed ones without ringing and Signal doesn't report the call failed

[szotsaki]

Please, report issues only from version 5.6 upwards!

General complaints forum and user help-out on this issue: https://community.signalusers.org/t/make-signal-calls-reliably-ring-on-the-receiver-side/18510

• I have searched open and closed issues for duplicates
• I am submitting a bug report for existing functionality that does not work as intended
• I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• This isn't a feature request or a discussion topic

---

Bug description

Users are welcome to re-submit bug reports

When Signal is opened in front of me on my phone and via Hangouts PC I hear the other party while his Signal is actually ringing me. My Signal shows no sign that I'm being called. At the end of ringing, when the network automatically disconnects, I immediately receive a "You have a missed call" notification in the chat.

Reproduced on three different WiFi networks with the same person.

The time difference between the two phones is approximately 5 seconds. Both phones are set to synch to carrier time.

Steps to reproduce

• Make phone A call phone B in Signal
• Observe that phone B gets no notification about the incoming call just the missed one.

Actual result: Call arrives as missed one.
Expected result: Phone B rings.

Screenshots

Device info

Device: Sony F5121
Android version: 7.1.1
Signal version: 4.14.10

Link to debug log

Callee debug log: https://gist.github.com/anonymous/9984ab543d85a181b06b02954564c060
Caller debug log: https://gist.github.com/anonymous/5eae662fee114e5e07a72dbd02c0e92d

Original report: #7314

@moxie0:

According to the logs in the issue, the devices are not able to find a valid ICE candidate.

Please, unambiguously tell the user there is an error happening during the call and the call has never been initiated.

References: #7603

Since this bug report is specifically about the non time-sync issue, there's another one for the time-sync problem. Please, don't clog this report with NTP-timing issues anymore but you're more than welcome to add your comments in and subscribe to #9633. Thank you.

[moxie0]

Do either of you have a VPN enabled?

[cegg1]

In my case I don't have a VPN or Tor enabled on any of the phones and neither do my contacts.

[szotsaki]

In my case I have DNS66 enabled (which is an "in-phone" VPN for ad-blocking) but several times applications circumvent it. My contact doesn't have a VPN.

[moxie0]

@szotsaki Can you try disabling and retest?

[alandom]

i have the exact same issue with my signal. please let me know if you solve the issue.

[erik55]

I have the same issue. Sometimes calls work, sometimes I only get a missed call message (Samsung S7 phone and Samsung S5 mini on the other side).

Another thing: When we are calling each other at the same time, no connection is achived/no call is coming in, neither is there a callee busy sign/tone.

How could I help improve this?

[hbasold]

I can confirm that the same happens also for calls between a Fairphone 1 (Android 4.2.2) and an iPhone in both directions. Please let me know if you need anything.

[szotsaki]

If you want this fixed sooner, please provide:

• whether you use any kind of VPN on your phone;
• whether you live in a country in which Signal can be blocked;
• networks of both phones (WiFi, GSM etc.);
• logs from "Settings > Advanced" right after the unsuccessful calls from both phones.

I myself can retest the VPN-less solution a bit later.

[erik55]

When I experienced this, both phones were connected via WiFi, no VPN. At the moment I can’t reproduce this. (maybe one of the WiFis was bad, slow?).

But still: When we are calling each other at the same time, no connection is achived/no call is coming in, neither is there a callee busy sign/tone. It just submarine echoes for ever. Separate bug?

[haffenloher]

@erik55

When we are calling each other at the same time, no connection is achived/no call is coming in, neither is there a callee busy sign/tone. It just submarine echoes for ever. Separate bug?

Yep. You could open a new report for that if you like.

[erik55]

The last thing, I mean when we are calling each other at the same time, seems to work now: I hear that the busy sign/tone.

And now I can always call, but the other person can't call me anymore (I only get messages: Missed call). When I read that I can at least call back.

[szotsaki]

@erik55: could you please answer the comment above you to make it easier to fix this bug?

[erik55]

OK, both phones are now in the same WiFi. The Samsung S7 has always the Signal beta version, the Samsung S5 Mini the regular version.

Problem: S7 can call S5 Mini, but S5 Mini can't call S7.

Successful call from S7 to S5 Mini

• S7 log

• S5 Mini log

Now try to call from S5 Mini to S7

I hear submarine echo on the S5 Mini, and immediately get a message of a missed call on the S7, while the S5 Mini continues to submarine echo.

• S7 log

• S5 Mini log

[erik55]

This is all so buggy!!!

I tried the same with the mobile network, WiFi deactivated. No connection at all. And messages from S7 to S5 Mini arrive quite fast, but messages from S5 Mini to S7 take 5 or 10 minutes (some only arrived after putting the S5 Mini in the WiFi again). But the mobile network on the S5 Mini seems bad, because it changes from H+ to 3G every few seconds.

I put both phones in the WiFi again, send some messages in both directions and was then able to establish a call from S5 Mini to S7!!

• S5 Mini log

• S7 log not possible, because every time I click on Advanced, Submit diagnose log I see for a few seconds Loading logs… and then Signal stopped, restart Signal app. Annoying.