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

[szotsaki]

• [X] I have searched open and closed issues for duplicates
• [X] I am submitting a bug report for existing functionality that does not work as intended
• [X] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
• [X] 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 there the user there is an error happening during the call and the call has never been initiated.

References: #7603

[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.

[erik55]

It seems to work now in both directions both with WiFi and mobile network. Messages also are sent and received immediately.

S5 Mini log

S7 log still not possible, it always crashes. That seems to be the solution: If the logging on the S7 crashes, then connection is working.

I will now restart the S7 phone to make it work again (the logging).

S7 log right after restarting

[erik55]

Still seems to work in both directions after restart of S7. The connectivity seems to be somehow established.

[mpiffault]

Same problem here :

• No VPN on both phones
• France (I don't think it can be blocked for the moment)
• GSM for both phones
• Moto G on Android 5.1 for both devices

Sometime call pass, sometime not.
I'll come back with logs later.

[mirasPL]

I cant call to my contacts all the time conecting but my contact can call me not every time but they can. Text is ok. Android 8.1.0 One plus one Ireland

[szotsaki]

@mirasPL Please, attach logs right after the failed call attempt described in the comment above. Do you have VPN enabled?

[mirasPL]

https://debuglogs.org/6926f8a7ed3e901e2aef5f86aed86317ba7040827fe1944eb06b8d8c6f08fe3b
This is my logs after failed call no VPN

[szotsaki]

Now I could reproduce the issue. The following logs are from the receiver side.

• With VPN (DNS66 ad-filter) turned on LTE-LTE didn't work. Log: https://debuglogs.org/6c5af80a13d7ddf016349d6bbecb9ed8a0af4d2cd89aeb7aaa3624835b33936d
• Without VPN (put to the exception list) WiFi (receiver side), LTE didn't work. Log: https://debuglogs.org/0745f9ed9d3e217c57e5301b0df6ac15001a6ce912692af023c17d3baf522a15

"Didn't work" means that only the notification arrived that I have a missed call. You can compare the two logs and possibly find out whether VPN has any importance regarding this issue.

Countries: don't block apps and sites.

Android: latest 8.0
Signal: latest version.

Do you need any other information we can provide to you?

[Frejr]

I have this problem too. Almost. I can make and receive calls, when I'm connected to WiFi . My phone operator seems to give me only IPv6 address (IPv4 available over tunnel), so maybe somewhere here's the problem (or Android version).

Testing:
Two phones with the same mobile operator (no VPN connections).

• my: WiFi, second: LTE (calls possible)
• my: LTE, second: LTE (calls imposiible)
• switching between cell-network and WiFi on the second phone not done yet, but I asked someone else for this and still problem only when my phone isn't WiFi connected.

Others unintentional "tests" shows, that problems appears only when I'm not WiFi connected. All other function works fine (messages, pictures and attachments) and are not network type dependent.

Apps on both ends were killed and started again - I found it helped to someone. No positive results.

Here's first log (my phone):
https://debuglogs.org/764d4007a185cdc40ad90f8afcc356091abcb5e861e2c4a76bf8be0eab54589d

And the second after reboot (without connect to WiFi on start - also my device):
https://debuglogs.org/b588786285c1e2031d3e7bd1f6e91722bb2dc966181d216bf33669b9274ce578

Please let me know if I could give any more data, because problem is little bit annoying.

[kuala-lumpur1]

I can confirm the problem. I have the same problem and tried on both Android and IOS and Signal is not blocked on my country and i don't use VPN or Tor on both devices.

For me to solve this issue, I just switch between the Wifi and Mobile network and trying to call about 3 to 4 times until the call established successfully.

Sometimes it works when both phones are connecting to Wifi .. and sometimes it works when one device is on WiFi and the other one is on Mobile network.

[ghost]

This issue seemed to resolve itself for me when I stopped using a DNS changer. I was using the application DNSChanger and with it enabled calls did not work on neither LTE or WiFi. I suppose this may be he same issue as it working with VPNs. This shouldn't be the case though. My Wi-Fi network uses a local DNS and it seems to work fine, but when I try to change the DNS on the device specifically (Android phone), Signal calls fail.

[mattimac]

@kuala-lumpur1 @Frejr @szotsaki
Hey guys, i believe i observed similar problem and it seemts to be ipv6 related.
The issue described above is visible on my Orange LTE in Poland . By default the APN is "internetipv6" which provides the phone IPv6 address ONLY to the phone.
You can change the apn to "internet" and get an IPv4 address (private one).

In both scenarios text messaging works fine, the issue is with the calls.

On ipv6 only APN on android :

• when i call somebody i can see "dialing" forever, signal is not ringing on the other side
• when sb calls me i cannot see his call

On ipv4 only APN on andoid:

• usually when i call somebody i can see "dialing" then "connecting" (and stuck here). on the other side user is able to accept the call but he does not hear or see me (call seems established).
• when sb is calling me when i am on ipv4 APN i am able to receive call without issues, audio and camera image on both sides are fine.

Can someone look into this? Seems like the ipv6 only connection seem to make a difference. The carrier (Orange Poland) claims they do not shape traffic in any way that can cause Signal or any other app to malfunction. Please note that Orange has a long story of routing all traffic outside it's network from Poland through Germany (Frankfurt) and to the other ISPs from there.

Device: Samsung Galaxy S7 SM-G930F
OS: Oreo 8.0 (XEO unbranded official rom for Poland)

[Frejr]

@mattimac: Yes! YES! YEEEEEEESSSS! It is! This helped! Tank you! I din't know, that I can change it!

So… We have one thing what causes problems. ONLY IPv6 protocol.

[kuala-lumpur1]

@mattimac
Can you explain how to change the apn to "internet" and get an IPv4 address (private one) ?

I'm having this issue with both Wifi and Mobile Network !

@moxie0
Is there any update regarding this issue ? maybe the reply of @mattimac can help ?!

[vipulparashar]

Go to seetings - click on 'more' -
Click on 'Mobile Networks' -
Click on 'Access Point Names' -
Click on your 'APN' -
Click on 'APN PROTOCOL', Update it to 'ipv4'

This is valid for mobile networks only.

[mattimac]

Anything more we can do to draw devs attention to it?

[kuala-lumpur1]

I just checked my mobile and actually it's By Default set to IPv4.

Still hope to find solution for this problem

[cegg1]

@moxie0 I can confirm that setting the mobile access point to IPv4-only has fixed Signal calls for me.
Thanks @mattimac for finally figuring it out!

Signal 4.24.7, Pixel 2 stock 8.1 Oreo, on the EE UK network

[szotsaki]

A gentle ping.

In my language of Google Play all Signal comments are about of this bug (of course without explicitly mentioning it). They cannot initiate a call, only missed call sign is reported etc.

I would like to ask if you have any ETA for fixing this issue.

The application is, otherwise, great but this makes using it a bit erratic. Thank you!

[erik55]

For me the problem is fixed, I don’t know what happened, but it’s not reproducible anymore. But a problem I still have is: Sometimes when I make a call, it echoes for ever. But when I send a message and then start calling, it works almost immediately. Somewhat of a workaround.

[mattimac]

For me problem still exists and chaning APN IP mode to IPv4 seems to be quite reliable workaround.

[ghost]

Mine is already on IPv4 and even with wifi it fails too

[omd10]

I can confirm this. IPv4 may be workaround for some, but it is not a real fix. I even doubt that it is related to this issue, mine was always on IPv4. The application receives the push but has issues with power management and/or notifications. Logs provided in #8302.

[dorakas]

This issue started on my phone after they changed something in the signal notification system

[rabsonic]

will test today IPv4 settings, but there is another thing
After maby last app update. Signal refuses other calls (gsm normal calls) without any notification.
Example: I'm talking with person A on Signal while person B is calling me via phone app, after two normal signals person B get bussy tone, moreover I did not get any information about that somebody is calling me.
In previus Signal version I could provide even 3way communication, when I was talking with sbd on signal, other people could call me and I could answaer or not the call.

[1301051906]

Can anyone just tell me how can I do to make the voice call? Yesterday I used an iPhone 6 IOS 11 adding a new friend on signal for the first time and then I made the call successfully. However today I can't. Why? NO VPN, version 2.30.2.16, SAME WIFI, TWO PHONES ON MY HANDS

[erik55]

A workaround that I use is:

• Start a call, then write a message. Then switch back to the call (works on Android).
• Or write a message shortly before calling, like “will call now”.

[ozgurakyazi]

A workaround that I use is:

* Start a call, then write a message. Then switch back to the call (works on Android).

* Or write a message shortly before calling, like “will call now”.

I tried these workarounds before for many times but it did not work for me. But this one, constantly works and makes me able to talk via Signal.
Here it is:

• Send a message like "Call me"
• Go back to main screen of Signal(all conversations listed) and wait there until call comes.

If I wait in that person's conversation, I mostly see Missed Call as a new message in the feed.

[dorakas]

The most akward part is that sometimes calls work perfectly and sometimes under the same conditions don't work at all

[mattimac]

@dorakas @ozgurakyazi @rabsonic can you check if you whitelist signal in power optimization - set to "do not optimize" if receiving the calls is more reliable?

[dorakas]

It seems that this problem resolved for me. The bad thing is nothing changed. There was no update for pixel 3 and no relevant commit in signal

[five-c-d]

these appear to be exceptional cases we're looking at that seem to arise from specific device configurations. I have 10 Android devices on my desk right now, and sadly I'm unable to reproduce... --https://github.com/signalapp/Signal-Android/issues/8302#issuecomment-437759492

@greyson-signal , suggest trying the following, since in my experience there is a latency-related aspect. (Meaning, worse latency worsens the problem i.e. makes it somewhat more reproducible when it is known to sometimes happen with a given device-pair... but there is no guarantee that call-setup will fail, nor a guarantee that call-setup will work either... unfortunately I cannot pinpoint a truly reproducible set of steps, even on a device which 'often' experiences the trouble I go for weeks at a time with no issues, then have a rash of no-ring-just-see-missed-call type of problems... but usually just with one or two other persons, both devices typically cryptocall fine 99.3% of the time with 99.8% of contacts).

• android#A1: configure as wifi-hotspot#H1, and connect A1 to the internet via dataplan (only), using VPN#V1 software that allows you to pick a country-node of your choice
• android#B2: configure as wifi-hotspot#H2, and connect B2 to the internet via dataplan (only), using VPN#V2 software that allows you to pick a country-node of your choice
  
  
• android#C3: configure with dataplan turned off, and connect to the internet (only) via hotspot#H1 up above
• android#D4: configure with dataplan turned off, and connect to the internet (only) via hotspot#H2 up above

This setup should allow you to place a cryptocall from android#C3 to android#D4 which has a lot of latency, and will exercise the regional STUN/TURN servers of your choice (recommend you try western EU per the four androids below), and make the selection of ICE candidate(s) take a significant amount of handshaking.

If you STILL cannot get call-setup-failure, try broadband noise: insert microwave oven #M5 physically in between android#C3 and the 'ISP' thereof android#A1, and cook some ramen whilst attempting cryptocalls (you can also use a large electric motor such as a washing machine... or aluminum foil as DIY reflectors... if you dislike ramen). You can also run CPU-intensive or RAM-intensive apps on your two hotspot-providing-devices, to further exacerbate things.

It may help if android#C3 is a newer flagship samsung, s8 / s9 and friends with at least android v8+ running, whereas android#D4 is a cheap older smartphone running an older version of android v4/v5/v6/v7 ...that might be circumstantial though, i.e. not be essential

p.s. Some additional debuglogs captured 2019-01-22 on four androids that saw problems in various crypto-call attempts, are discussed here == https://community.signalusers.org/t/calls-take-a-long-time-to-connect/4954/8 In particular, shellSignal in one of their cryptocall attempts has a suspiciously-close-to-exactly-60-seconds pause happening "just" after handleCallOfferMessage and "just" before WebRtcCallService: onStartCommand on the recipient-device. Which suggests a timeout, though no exception was thrown.

I don't think these are config-specific device-specific bugs

Another thread, which is more general and has no debuglogs but does have some mention of the removal of sonar-ping MP3 recently, is here == https://community.signalusers.org/t/why-do-signal-calls-take-much-longer-than-wa-calls-before-ringing/5871 I realize that OWS is hampered in the ability to see call-setup-troubles across the userbase of signalapp, because you do NOT spy on endusers :-) Thank you for that, greatly.

But I strongly suspect, having run into the never-rings-just-throws-missed-call problem on multiple devices with multiple contacts at various times during the past six months, that the trouble is not device-specific config-specific. All my contacts are using stock ROMs, almost none of them enable any non-default settings (within signalapp nor within the underlying OS of the smartphone), and so on. There is some kind of root cause here, in the webRTC layer or the wrapper around it -- since invariably, in my anecdotal experience at least, the "missed call" textual-message sent via signal-protocol arrives without ANY trouble -- regardless of whether there are 'network errors' according to the logfile that seemed to be the 'proximate cause' of the webrtc failure.

Like dorakas, my cryptocalling woes periodically resolve themselves despite no relevant client-side commits... and I can reliably make calls for days or even weeks, even to contacts that used to be problematic... but later the problems always crop back up again. So the problem is either server-side (and if so almost certain TURN/STUN/ICE/similar stuff and not signal-server proper), or a subtle timing-related condition client-side, maybe?

[mattimac]

Hey guys, it seems that we did not clearly isolated the issue and ensured this is actually one issue.
This is extremely frustrating, devs keep on adding new features while we still do not have reliability regarding one of the most basic features - calls. They have exceptional quality once established but i still observe this issues with no ringing on the other side.

This is extremely frustrating as I spend days trying to track down the cause but with no luck. Any ideas what approach can bring us more progress on this?

@dorakas @ozgurakyazi @rabsonic @erik55 @szotsaki @vipulparashar @kuala-lumpur1
do you still experience this issue? any workarounds seem solid for any of you?

Please note that android firmware updates seem to clear APN settings for me, i can see i had again ipv6 by default! Please recheck this one and test if switching to ipv4 fixes this until the next firmware update!

[ozgurakyazi]

Hey,
I am still using the workaround I mentioned before. I am having the other side call me, instead of me calling them. Before they call me, I go to the main(home) screen of Signal, to my limited experience, if I wait in the conversation screen of the caller, call does not arrive to me(again, this is just limited experience).

Another point I would like to add is, I am having this issue only with 1 specific smartphone model(Samsung Galaxy Trend S7560, 2 different phones same problem. I can provide with logs, if needed, in 2 weeks).

Sorry to inform that, I did not check power optimization in those phones. Will do it and write down the result.

About ipv6 configuration, I dont have currently access to both phones, so I cant really change anything. But they are able to call my phone, does ipv6 configuration somehow blocks the connection just one way? Also, they are always connected to wifi(wifi only), ipv6 is only for mobile networks, isn't it? In any case, I will try this.

Is there any other simple tests you would like me to do?

Best,

[szotsaki]

This bug is still present on the latest version of Signal (4.33.5).

@greyson-signal @moxie-signal : Do you need any specific information from us in order to make Signal calls working?

[basketas]

So a year old bug I am also witnessing can't be pinpointed and fixed :/ I really hated to have to switch to other apps, because this bug is more than CRITICAL...

[five-c-d]

@basketas , there seem to be at least four different manifestations... the symptom is the same, "missed call", but the gory details, as revealed in the debuglogs, are very different. Can you please upload some debuglog-pairs, one from the caller and one from the callee, where you experience the problem? And ideally, some debuglogs from successful calls, for comparison, from those two devices.

does ipv6 configuration somehow blocks the connection just one way?

@ozgurakyazi -- Yes, this seems to be the case, at least with some configurations. One person that was receiving no calls on dataplan, but got them to work on wifi or by using the VPN with their dataplan (which typically ADDS latency and HURTS cryptocalling but in this situation helped), traced the difficulty to enabling a non-default DNS-lookup service. https://community.signalusers.org/t/calls-not-connecting-possible-issue-with-dns-over-tls-and-or-ipv6/6286/31 This was different from the usual 7733 type of bug, but methinks related to some flavours thereof. The workaround was to return to using the normal DNS-lookup service of the carrier... does anybody who is experience 7733 buggy behavior, have cloudflare or dns.google 1.1.1.1 or 8.8.4.4 or 8.8.8.8 enabled, perhaps?

@ozgurakyazi -- And if you have those debuglogs you spoke of, which were to become available after a couple weeks... well, it has been a couple of weeks. You can post them here if you prefer, or for easier discussion, start a new thread at https://community.signalUsers.org -- you can login with your github credentials, or signup with another email if you prefer

@szotsaki -- my understanding is that the troubleshooting is hard, because is Greyson is unable to reproduce the problem on any of his dozen test-devices. Most of the people who experience the problem intermittently (including myself), find it to be very hard to pin down, i.e. it cannot be reproduced on demand, even with their own devices. Sometimes my one contact that has trouble cryptocalling me, gets through right away, other times it takes two tries, and SOMETIMES it takes five tries... but quite often it picks up in under five seconds total, which is just peachy. We cannot determine what the difference is, on the peachy-superb call-setup incidents, versus the sour-note-takes-thirty-seconds incidents. Networks the same, devices the same, often the same day, no obvious changes to signalapp nor to the handsets/OSes. It is a critical bug though, for most people that are impacted by it.

[erik55]

Just wanted to tell, that the bug disappeared on my phones. I am using several phones, and all the calls in either direction work now: Samsung S5 mini, Samsung S7, Samsung S9, iPhone SE.

Unfortunately I don’t know, when the bug disappeared.

[pietervw]

We are still experiencing this bug most of the time.

Here are the logs off our 2 phones:
https://debuglogs.org/1803944df359aeee66995314c94b117e076e81a95cb41f8046fec6ce287b5e74

https://debuglogs.org/daeffb3b881de0d753dee94975b57d1f4faa8d9ae9dc3bf261d0d8642c4f72d1

Any assistance would be appreciated

[ozgurakyazi]

@mattimac @five-c-d I could not login to the
https://community.signalUsers.org with my github credentials but I created the new topic.

Here it goes: https://community.signalusers.org/t/issue-7733-call-always-miss-new-debug-logs/6493

[five-c-d]

@pietervw , almost certainly you are onto something, though it might not solve all the problems (ozgurakyazi is experiencing failures on wifi-to-wifi calls ... as is the case in my intermittent MissedCall situation).

But at least in one situation, cryptocalls worked fine on wifi, worked fine on wifiWithVpn, worked fined on dataplanWithVpn, and mysteriously failed with dataplanSansVpn. The problem was that one of the devices was an S9 with android v9, and the enduser had enabled 1.1.1.1 as their DNS-provider. We suspect (but do not know for sure) that there was IPv6-related something something going on under the hood, which using the VPN-on-dataplan masked successfully. https://community.signalusers.org/t/calls-not-connecting-possible-issue-with-dns-over-tls-and-or-ipv6/6286/31 Can you see what your DNS-lookup settings are like, in your android network-settings? Do you have an app installed which allows you to perform ping&traceroute type of tests from your android, such as Termux perhaps?

[ozgurakyazi]

Hello All,
With the helps of @five-c-d , the problem is resolved (at least for 4 different phones I have access to) now. :+1: :clap: :smile:
The source was the time. All 4 phones were seemingly in the same time(was varying at most 1 minutes.). But when I check the time configurations, 3 of them were in the different(wrong) time zones. I changed all time zones to the correct ones and enabled automatic time. Now all the calls work for all directions :fireworks:

I hope this is the problem for all and the issue is fixed.

Thank you all :)

[five-c-d]

@pietervw , please see https://community.signalusers.org/t/spurious-missed-call-on-dataplan-android-7733/6504 ... it looks like you are having some process-problems (both people dialing each other simultaneously -- which is understandable since this is a frustrating bug). See the comment about 'Receiver not registered' which is possibly related to #8402 on the +xxx79 enduser's handset.

But even when you are not having mid-air-collisions happen, there are a lot of strange exceptions in your debuglogs you posted == https://github.com/signalapp/Signal-Android/issues/7733#issuecomment-468351112 In particular, this cannot be correct:

• 2019-02-28 17:36:05.398 SAST W SignalServiceMessageSender: java.io.IOException: No connection!

The same exact device just received a bunch of packets over the same exact dataplan-connection. There are a lot of TimeoutException and a lot of DuplicateMessageException errors (especially on the one 'successful' call-attempt at 17:44 excerpted here). There are some recent hits in github for DupeMsgE, but they might not be directly related. Why is signal4android under the impression that it has "No connection" when clearly it has one?

[davidar]

Whitelisting Signal in the power optimisation settings seems to have resolved this for me.

[DemiMarie]

I can think of two problems:

1. Does Signal use the proper Android VOIP APIs?
2. Does Signal use real-time FCM notifications?

[yaomtc]

While I've also experienced missed Signal calls (I have it set to vibrate but I haven't felt it), I feel that this Gadgetbridge bug report is relevant:

https://github.com/Freeyourgadget/Gadgetbridge/issues/786

I use Gadgetbridge to get most of my notifications, but Gadgetbridge ignores "ongoing" notifications, which Signal uses for calls. Maybe it would help if there were an option to send one regular notification when the call is coming in, and then start the "ongoing" notification while the call is going, if necessary.

[kravietz]

I have identified one more thing that is causing this symptom: Signal seems to rely on Google Play Services and I couldn't get Signal calls to work on a custom ROM (LineageOS) with the services app replaced by MicroG for privacy. The emulation of Google Services in MicroG was however disabled and apparently Signal wasn't getting some kind of notification - when I re-enabled them, it all started to work.

[mattimac]

does ipv6 configuration somehow blocks the connection just one way?

@ozgurakyazi -- Yes, this seems to be the case, at least with some configurations. One person that was receiving _no_ calls on dataplan, but got them to work on wifi or by using the VPN with their dataplan (which typically ADDS latency and HURTS cryptocalling but in this situation helped), traced the difficulty to enabling a non-default DNS-lookup service. https://community.signalusers.org/t/calls-not-connecting-possible-issue-with-dns-over-tls-and-or-ipv6/6286/31 This was different from the usual 7733 type of bug, but methinks related to some flavours thereof. The workaround was to return to using the normal DNS-lookup service of the carrier... does anybody who is experience 7733 buggy behavior, have cloudflare or dns.google 1.1.1.1 or 8.8.4.4 or 8.8.8.8 enabled, perhaps?

I use DNS over https (avaiilable natively on samsung S9 android 9) please remember to test with and without it this may be important factor.

[harmonicus]

Hey there, hew guy here,
missed call problem,

i have both phones on desk, they have automatic (same) timezones, ipv4, wifi connection
Android 8.0 and Android 5.1

I found out that Orbot blocks calling/recieving - TOR + VPN (both in Orbot)
Orbot version 16.0.5-RC-2-tor-0.3.4.9

1. when both phones have Orbot disabled -
   all ok; all works

2. Android 8.0 is calling, Android 5.1 receiving
   A. Android 8.0 TOR off, VPN off; Android 5.1 Orbot on, VPN on
   all ok; calling works, sound works
   B. Android 8.0 TOR on, VPN on; Android 5.1 Orbot on, VPN on
   missed call problem,
   C. Android 8.0 TOR on, VPN off; Android 5.1 Orbot on, VPN on
   all ok; calling works, sound works

3. Android 5.1 is calling, Android 8.0 receiving
   A. Android 5.1 TOR off, VPN off; Android 8.0 Orbot on, VPN on
   reciever do not hear ringing sound, on main screen there are no changes, but you can see icon of calling one the top line. Anyways when the call is answered there is no connection established
   B. Android 5.1 TOR on, VPN on; Android 8.0 Orbot on, VPN on
   missed call problem,
   C. Android 5.1 TOR on, VPN off; Android 8.0 Orbot on, VPN on
   same as in 3.A.
   D. Android 5.1 TOR off, VPN off; Android 8.0 Orbot on, VPN off
   i can see on main screen incoming call and answer it and establish connection, BUT i can not hear the calling sound (vibrations are there). When connection is established, i hear no voice on the other side (bad)
   E. Android 5.1 TOR off, VPN off; Android 8.0 Orbot off, VPN off
   same as 3.D. - no calling sound, no hearing sound

Android 8.0
https://debuglogs.org/b3363c1eaedd655ade75de1edb683356de0fb759021b0042e0e249edc16a14d6
Android 5.1
https://debuglogs.org/c86aa192c1b5c8c169e5594da181375ae1d38a3c0abe01fe3cc85330935c92a3

Time stamps
2A, 1219
2B 1220
2C 1221
3A 1221
3B 1223
3C 1223
3D 1225
3E 1226

Ok, so that my piece of the cake

EDIT:
small changes, on android 8.0 sometimes there is a calling voice (sometimes not), and after connection is properly established sometimes there is voice on the other side (sometimes not), sometimes just one microphone works, sometimes non - and that on both devices with Orbot completly off

And yes VoiceNotes works perfect

[mattimac]

@harmonicus please save as much debug log assigned to each of the cases i bet that will be helpful for the devs to look into it.
Here is short manual if needed https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports

[five-c-d]

i would have to make the whole process again

No, the debuglogs are not erased ... just capture the debuglog on your android 8.x device, now, then submit it, longpress to copy the URL#1.

Then do the same on your android 5.x device, submit and copy URL#2.

Paste both URLs here, and give us some idea of what timestamp is associated with each test#1 / 2A / 2B / 2C / 3A / 3B / 3C / 3D.

I can say though that because of the high jitter&latency, cryptocalling through Orbot is pretty much guaranteed to be awful (possibly even non-functional). You can usually make voiceNotes work, which is like a kinda-sorta semi-realtime conversation... to a moonbase.

[harmonicus]

moonbase :)

I've edited main post above - logs, time stamps, small edit

[Ben-Russell]

https://debuglogs.org/b6218683e2430f809079a9d12d62a4f87d26cf5e49ff55478e52c15903f99f02

Of the last 4 phone calls, 3 went directly to missed and the last one is the only one that actually rang my phone. How can I stop this from happening?

[Ben-Russell]

I have no vpn or anything similar installed on my phone.

[ozgurakyazi]

Without checking the debug log, can you check the time settings of all the phones?

It would be easier to have them automatically set with correct timezones. Let us know what happens after putting them all auto.
Best Regards,

Özgür Akyazı

---- On Tue, 02 Jul 2019 03:14:18 +0200 [email protected] wrote ----

https://debuglogs.org/b6218683e2430f809079a9d12d62a4f87d26cf5e49ff55478e52c15903f99f02

Of the last 4 phone calls, 3 went directly to missed and the last one is the only one that actually rang my phone. How can I stop this from happening?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Sensor66]

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6.

Whitelisting of power optimization does not help.

Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

[mattimac]

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6.

Whitelisting of power optimization does not help.

Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

Is that ipv6 only wifi? If not are you able to use ipv4 only and narrow down the issue to ipv6 networking?

[JoshGrahamMoore]

Is there a thread for iOS too? Both me and my partner can't call each other, same issue. Rings and rings but nothing, then the second you hang up you get the missed call notification.

[mattimac]

Is there a thread for iOS too? Both me and my partner can't call each other, same issue. Rings and rings but nothing, then the second you hang up you get the missed call notification.

can you attach debug logs from both sides?
can you test more on LTE/cellular data and wifi? can you tell in any of those cases: wifi/cellular data if you get ipv4 or ipv6 address to test if ipv4 or ipv6 makes any difference?

[Sensor66]

@ mattimac

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6.
Whitelisting of power optimization does not help.
Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

Is that ipv6 only wifi? If not are you able to use ipv4 only and narrow down the issue to ipv6 networking?

I have a TP-Link Access Point TL-WA801ND, and I think that is IPV4 only, but I am not sure and could not find it.

[mattimac]

@greyson-signal @moxie-signal
OK guys i believe i was able to isolate the problem and it seems in that scenario chaning the APN from ipv6/dual stack to ipv4 fixes the issue. Here are debug logs. Please note Orange claims they do not shape the traffic in any way.

Phone A (dials the call) - Samung galaxy A70 SM-a705FN PPR1.180610.011.A705FNXXU3ASG6
SIM: Poland Operator: Play
Phone B (wait for the call) Samsung galaxy S9+ SM-G965F PPR1.180610.011.G965FXXS6CSH5
SIM: Poland Operator: Orange
Phone B configured APN profiles:

1. "Orange INTERNET" (default)
   Name: Orange INTERNET
   APN: internetipv6
   Proxy: not set
   Port: not set
   Username: internet
   Password: internet
   Server: not set
   MMSC: not set
   Proxy MMS: not set
   MCC 260
   MNC 3
   Authentication type: no auth
   APN tyoe: default,supl
   APN protocol: ipv6
   APN roaming protocol: ipv4
   Connection: undefined
   Virtual cellular network operator type: SPN
   Virtual cellular network operator value: Orange

On this profile phone gets two IP addresses:
2a:00:f41:1870:xxxx:xxxx:xxxx:xxxx:xxxx ipv6 address
192.0.0.4 ipv4 address

1. "ipv4" (custom)
   Name: ipv4
   APN: internet
   Proxy: not set
   Port: not set
   Username: internet
   Password: internet
   Server: not set
   MMSC: not set
   Proxy MMS: not set
   MCC 260
   MNC 3
   Authentication type: no auth
   APN tyoe: default,supl
   APN protocol: ipv4
   APN roaming protocol: ipv4
   Connection: undefined
   Virtual cellular network operator type: SPN
   Virtual cellular network operator value: Orange

On this profile phone gets 10.71.xxx.xx IP address only

Phone A set up on test wifi network 192.168.7.0/24 vlan, dont worry bout connection quality - dediacted cable connection from UPC 600/60 for those tests

In scenario where both phone A and B are on wifi everything works great.

In scenario where phone A is on wifi and phone B is on LTE (customized APN with ipv4) phone B does receive the call properly
phone A call log
https://debuglogs.org/25ab0b41bb878995228f0c9e0a7b6519aaa20cb51adbf6197a58c66d91c3d3e4
phone B call log
https://debuglogs.org/dbe73db4ae7fec032d79ed49a7b8f429bd204731c12ae50c931a90cca94e2494

In scenario where phone A is on wifi and phone B is on LTE (default APN with ipv6) phone B does NOT receive the call properly
around 23:00
phone A call log
https://debuglogs.org/4c3a676bd862504d840e9193d42107924e830711f3caeac668bf6b537fbf343b
phone B call log (what is interesting there is incoming call icon on notification bar at the toip and in notification drawer there is constantly "connecting"
https://debuglogs.org/650e826933b3624faeeb66be37b872972021cf44be8e163422f5cb37b2b60356

Interesting part, notification with no vibration and sound? this what we see on notification bar (screenshot below)

2019-09-18 23:02:16.373 CEST I MessageNotifier: Posted notification. Notification(channel=messages_1 pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x1 color=0xff2090ea category=msg actions=2 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0)
2019-09-18 23:02:16.380 CEST D LockManager: Entered Lock State: PARTIAL
2019-09-18 23:02:16.381 CEST D AccelerometerListener: enable(false)
2019-09-18 23:02:16.397 CEST I IncomingRinger: Cancelling vibrator

Phone B screenshot while phone A tries to ring phone B and on phone B side no ringing but "connecting" (only the icon on notification bar and notification with "connecting" information")

Logs sent just after each scenario

[MrWolf-to]

Hi, I had the same issue with my Samsung Galaxy S7 edge with Oreo. If I tried to call from another phone of mine, calling would't work and I received the message of missed call.
Oddly enough, viceversa worked, so I thought it was a phone problem.

Searching for this problem on Google, I found a solution on Reddit that seems to work, at least for me: just set "Date and time" on automatic.

[mattimac]

@greyson-signal is there anything we can do as we already have test report, debug logs and some proofs that may be connected to ipv6 only? Can i do anything on my setup to provide more useful information?

[szazer]

I have the same problem on four smartphones, operator Orange Poland (2xAndroid 8, 1xAndroid 7.1.1, and one of them is 9.0 Pie). I announced that is not problem of GSM operator (APN). That's no matter LTE or HSPA or GSM technology. The big problem is Google DNS. I installed Cloudfare 1.1.1.1 aplication from Google Play, turned on this app, DNS was switched to 1.1.1.1 and Signal began work PERFECTLY. And there is one problem: when DNS are changed to 1.1.1.1 Google Play shop doesn't work at all, many Google service doesn't work too... Generally i have deleted Signal from my smartphones because this issue is not accepted for me, there is not professional application for home / bussines using. Bye Bye funny Signal. I use Wire today, its work perfectly ! :-) Full encrypt and works on WIFI, LTE, HSPA, GSM and any ADSL or VDSL broadband connections. See you on Wire :)

[szotsaki]

Just to have all the information in one place:

_Originally posted by @usergoodvery in https://github.com/signalapp/Signal-Android/issues/8302#issuecomment-509656511_

Signal folks this issue and #7733 are most likely related to some logical bug in how you set IceTransportsType.RELAY for PeerConnection configuration as in https://github.com/signalapp/Signal-Android/blob/e603162ee767d56fa16f56701cd29010f22ed22d/src/org/thoughtcrime/securesms/webrtc/PeerConnectionWrapper.java#L72

Since you are automatically forcing non system contacts on the TURN path as per https://github.com/signalapp/Signal-Android/blob/84fd1a9140e15a3f02bec6a2803d26223acc44a3/src/org/thoughtcrime/securesms/service/WebRtcCallService.java#L389 (suspect very few users turn this option on by default) your TURN servers are probably overloaded and users are getting random success rate with their webrtc connections, because system-contact vs non-system-contact is random and highly localised to each user.

The remote peer won't be trickling ICE candidates back, and onIceConnectionChange won't evolve out of the CHECKING state forcing a timeout and users seeing missed call note.

@alan-signal, @greyson-signal, @moxie-signal: does it give the necessary input for you to start investigating this issue further?

[DemiMarie]

Also, some users are behind nasty NATs that force them to the TURN path.

[mattimac]

Can someone with more in-depth knowledge about ipv6 analyze this? I found description of how Orange introduced Ipv6 to its network. I remind that there are issues with calls on IPv6 only, on IPv4 LTE on Orange the problem does not exist.
http://www.data.proidea.org.pl/plnog/12edycja/day2/track4/01_ipv6_implementation.pdf

[lcortier]

I have that bug with only one person, which is very annoying because it's my significant other :(
We both are using the same mobile data provider.
No VPN on either phone. I'm the only contact she has with Signal.
We verified each other's signal contact last time we were physically together.
No change.
Up to a few weeks ago, she could not call me but I could.
Now it's not working in both directions.
Back to WhatsApp for the moment :(

[mattimac]

@lcortier Check APNs on both phones and let us know if they are ipv6 or ipv4 or dual.
If dual or ipv6 change to ipv4 and let us know if that fixes the issue.
provide debug logs if not.

[lcortier]

APN on my phone (OnePlus 6T) is ipv4, on my partner's phone (Samsung Galaxy S7), it's all greyed out. I tried to explain how to set a new APN for her but it didn't work...
Will try again tomorrow.
Thanks for the quick answer !

[mattimac]

APN on my phone (OnePlus 6T) is ipv4, on my partner's phone (Samsung Galaxy S7), it's all greyed out. I tried to explain how to set a new APN for her but it didn't work...
Will try again tomorrow.
Thanks for the quick answer !

its grayed out because you cant edit this one but that is still applied let me know what info is there. you can create new one with setting the same or similar.

[lcortier]

its grayed out because you cant edit this one but that is still applied let me know what info is there. you can create new one with setting the same or similar.

Ok, the greyed out and the new one we created are both in IPv4.

[attila-lendvai]

i have experienced this with one contact (Samsung phone with standard OS). my calls immediately went to missed call on her side, on my side it was "dialing". she could call me for a while.

then it stopped working both ways.

then it started to work again for both directions.

we didn't deliberately change anything in our environment, at most Signal app updates.

here are two logs that may help:

https://debuglogs.org/df39172a406a0797c8500a73e77b6de710b309f9605567870939689807d7099e

https://debuglogs.org/8d479835a25e70f185aa63c471322e114be06c2e94fad0ce17654b11f11a9152

[lcortier]

Yessss ! Issue solved.
Her clock was set to manual and was 10 minutes late.
I just set it to automatic and everything started to work immediately in both directions now.
Wouhouuu, after 4 months of research and getting mad about "such a stupid bug", I understand how it was just a "feature". :)
Why her clock was set to manual, I'll never know (it's a second hand phone, so she didn't do it) and even why Google allows phones to be set in manual (at least for the general public) when many apps may start to bug if not synchronized is beyond me.

[erik55]

Just wanted to comment, that I have the same issues. And the non automatic time (manual time) and time shift seems to be the problem. (Here on Canary Islands I have to set it on manual, as otherwise the timezone changes several times a day, as we have providers that send the mainland Spain time zone, others the Canary Islands time zone.)

Conclusion: Is there a possibility for Signal to circumvent this non-working phone calls? At least show a hint: _Maybe your or your callees time isn’t set correct or differ?_

[mattimac]

Just wanted to comment, that I have the same issues. And the non automatic time (manual time) and time shift seems to be the problem. (Here on Canary Islands I have to set it on manual, as otherwise the timezone changes several times a day, as we have providers that send the mainland Spain time zone, others the Canary Islands time zone.)

Conclusion: Is there a possibility for Signal to circumvent this non-working phone calls? At least show a hint: _Maybe your or your callees time isn’t set correct or differ?_

Please look for this issue and then if not already reported start separate one including debug logs and all data required. This is not in scope of issue #7733 i believe as issue seems to be at least ipv6 related (at the same time on both ends same time and timezone).

[strugee]

@lcortier it's not a feature and it is, in fact, a bug, because there is no such thing as time.

[szakib]

I have seen this issue on two (receiving) phones now, a CAT S41 and a Sony Xperia Z2. Source does not seem to matter. Please solve this. I convinced my family a year ago to switch to Signal, but if calls don't work reliably, I cannot keep the non-technical members on this platform.

[erik55]

@lcortier it's not a feature and it is, in fact, a bug, because there is no such thing as time.

Haka, very funny. Point 6 says “Protocol ideas that require synchronized clocks are doomed to failure.”

Well, we are all doomed, as the developers don't stick to their own rules.

I have reproduced it just now. If my time is set wrong only 3 or 4 minutes I can't call my daughter (Samsung S7), neither can she call me.

Surprisingly I can call my wife (also Samsung S7).

Maybe that is the only bug for all users? Workaround: synchronize your clocks! Tsss.

[strugee]

@erik55 you're missing my point, I think. I'm not disputing that it can be reproduced! I was addressing the comment that said "I didn't realize this was a feature and not a bug" because that implies that it doesn't need to be fixed, when really it does.

[lcortier]

What I mean is, as an ex-developper, I perfectly understand why time synchronisation is needed for a communication application.
My issue being solved just by synchronizing time, I tip my hat to you guys. Good luck :)

[kirkawolff]

A fix should be simpler than synchronizing clocks. It seems to me the problem is the ring-timeout is comparing the local clock with the sender's initiation time stamp. This should be easily resolved by starting a ring timeout upon receipt of the request in the receiver's end rather than depending on both end's clocks to be synchronized. The alternative is to use a separate clock in the app that's synchronized with a server so both phones can be working from the same reference. Asking users to turn on clock synchronization on their phone isn't reasonable for several reasons such as the fact that cell towers are often the source of time in this case and they often are way off. Also, cell phones are some of the worst devices at keeping time without synchronization, they commonly drift 30 minutes per year.

[ioogithub]

I have this issue as well. I have two contacts that I used to communicate with during signal.

I am using LineageOS version 17 on a Motorola G7
Contact 1 was using an iPhone 7 but has upgraded to iPhone 11
Contact 2 is using a Samsung A8

None of us can use signal. The calls go right to missed call on all of our phones. I just tested for 30 minutes with both contacts, having them call me and me calling them. Not a single call actually worked, it just goes to Missed call immediately.

We all had to abandoned Signal because of this issue, it just doesn't work an any platform on any phone. There is no way to contact each other.

I have been trying to get family members to use Signal but we are back to regular cell service. What is going on with Signal that it is so broken?

Edit: None of our clocks are set to manual time and none of us are using a VPN or private DNS.

[quantizzed]

Same with me. I tried to move my family to using Signal, but failed due to the problems with missed calls (and messages, too, by the way, as described in issues #8604 and #9533 ).

[ioogithub]

It is very frustrating. I can't recommend anyone using Signal at this time, too many problems, it is obviously not ready for prime time.

It is a struggle trying to get users onto the platform. The answer I get is "why can't you use Facebook messenger like everyone else"

What am I supposed to say when Signal doesn't even work, here try this platform that is more secure but is unreliable and don't actually work?

Signal seems like more of a proof of concept.

[donfn]

@ioogithub E x a c t l y. I've brought ~10 people on signal and they are slowly drifting away to facebook again, because signal simply does not work.

[kravietz]

@ioogithub @donfn You could try https://matrix.org/ as it offers comparable levels of security and privacy while being fully open-source and federated.

[szakib]

Dear Signal developers,

Maybe it would be time to fix this fundamental bug reported two years ago, before all your users leave.

@ioogithub @donfn You could try https://matrix.org/ as it offers comparable levels of security and privacy while being fully open-source and federated.

[jknockaert]

This is a pretty persistant issue. Have been trying a little bit everything (like disabling battery optimization for Signal), but I couldn't make incoming calls working reliably. Am running Signal on a Motorola with fully updated Android One, so on that side it's as stock as it gets.

[DemiMarie]

@moxie0 I strongly suspect the problem is with Signal’s TURN servers. Can you confirm?

Signal needs to ensure that its TURN servers can handle the load even if every call uses them.

[donfn]

@ioogithub @DemiMarie @szakib @quantizzed I checked the issue mentioned above and setting my phone's time to "Automatic" solved the issue for good!
The problem for me was indeed very stupid, though I think signal should independently keep its own time to avoid such sync issues (especially if incoming calls depend on it!) ...
I don't know though if this is practically feasible or at all possible.

At least, please make the app check on start-up whether the device's time has a high margin of error when compared to a NTP server and warn users to check their time settings.

Thanks.

[quantizzed]

@donfn

I checked the issue mentioned above and setting my phone's time to "Automatic" solved the issue for good!

I'm not sure the issue is caused exclusively by
time synchronization problem. My phone's clock is set to synchronize with network time by default, yet the problem persists.

But even if it is a time synchronization problem, how am I supposed to control other peoples' phones? And why are other messaging platforms not affected?

[iexos]

But even if it is a time synchronization problem, how am I supposed to control other peoples' phones?

You can select a message, and see the details with (i). Then compare their sent timestamp to your received timestamp. This is how I found about a 3 min difference, because they didn't synchronize their time. Explain the problem, and that they have to synchronize their time. Make sure the their messages are sent from the device you are trying to call with, and not from another linked device.

That said, of course it should not happen like this, its far from the "easy" usability Signal is trying to achieve.

[mfn]

That fixed it for me too. Had a friends phone who complained about this, all incoming calls (voice, video) immediately appeared as "you missed a call" or so.

Turns out his time was not synced and off by 2 minutes in the future. Went to settings, synced time, issue fixed.

Of course no one knows why this wasn't enabled 😄

[szotsaki]

Since this bug report is specifically about the _non_ time-sync issue, I have created a new 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 https://github.com/signalapp/Signal-Android/issues/9633. Thank you.

[Gorkde]

We had the same problem.
Reason was the person on the receiving end had set the time on her Phone 5 minutes before the actual time.

[codethief]

@Gorkde: As @szotsaki mentioned right in the comment above yours, the present bug is not about the time synchronization issue. For that one please refer to #9633.

[mattimac]

@greyson-signal @alan-signal @moxie-signal can devs have a look at possible cause pointed here? https://github.com/signalapp/Signal-Android/issues/7733#issuecomment-574279071

[joe564338]

I have this same issue. Times between me and the other person are synchronized. I don't know how to fix here is debug log: https://debuglogs.org/7f169d0b20d25ab9e1b58482cf950f7a25deafb8685bc8a1d518e70f3a2406b8
The issue only started happening last weekend on June 6th. I have no idea what changed to cause this.

[joe564338]

Here's my contact's debug log
https://debuglogs.org/4d45f370921f9a354f4adf79591b003a820a61589fad82993657895f98cc7137.zip

[morphine00]

Possibly related (Android), I had a missed Signal call from some half an hour ago, but just got a new notification about that very same call, and when I tapped the contact in the app, it showed _two_ missed calls, marked as "now."

[loxK]

Same issue. It happens randomly, when both phones are connected on a fast network, with sound enabled, do not disturb disabled. I double check with the Troubleshooting page

When calling the client should have two different ringing feedback in the earpiece: one when trying to make the other phone ring, one when the other phone actually rings.

[secbug]

Having this issue with my bosses phone and mine right now. Can communicate to literally anyone else on the app, and same with him to others, but calls seem to be entirely missed. Like today, I received no notification and there was no call missed receipt left but yet my boss says it couldn't get through.

[trochdewei]

I faced similar problem. Signal calls almost unusable. I granted app all permissions, check everything - no luck. No one can call me. On my phone i have crDroid 6.9 firmware based on Android 10

[capitolfrills]

@greyson-signal I am still experiencing this issue that I reported awhile ago (#10058) and also here. This has been going on for at least half a year. Incoming Signal calls used to work fine for me, but now when I am receiving incoming calls, I can hear the call ringing, but no notification box and the phone screen does not change to enable me to answer the call. If I open Signal, open a message and select the call icon only then does the incoming call screen appear and allow me to answer the call. This issue is reproduceable for me and happens with every incoming call, whether on wifi or network.

Device info

Device: OnePlus 7
OS: Oxygen OS 10.3.4.GM21AA
Signal version: 4.75.4

Closed related ticket #10058
Related to #8302

[gab81]

hello, i have the same problem https://github.com/signalapp/Signal-Android/issues/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.

[cawauk]

Same problem here, experiencing for the last few months. Huawei Mate 20 pro. Latest version of signal (today's), Android 10.1

For some reason it always happens at night when my partner calls between 9pm and midnight, at which point my DND switches on. I don't think AI is that advanced (yet) to not ring my phone...

However, this issue never happens during the day (that I can remember) and as I tend to use my phone less often in the evenings, wondering if signal is having trouble waking my phone from deep sleep (even though all options are on in Android for signal to run in the background)?

[gab81]

Same problem here, experiencing for the last few months. Huawei Mate 20 pro. Latest version of signal (today's), Android 10.1

For some reason it always happens at night when my partner calls between 9pm and midnight, at which point my DND switches on. I don't think AI is that advanced (yet) to not ring my phone...

However, this issue never happens during the day (that I can remember) and as I tend to use my phone less often in the evenings, wondering if signal is having trouble waking my phone from deep sleep (even though all options are on in Android for signal to run in the background)?

interesting, yeah it's something happening across the board.... i also noticed that Signal doesn't send the edge light notifications (those lights on the edges of Samsungs) when the phone screen is off for messages only.... so with messages he cannot wake up the phone from deep sleep. i used a 3rd party app and works now. Strangely enough with phone calls, he wakes up the phone and shows the fancy lights....

So i think they need to up some permissions. Similar to what you experienced that if the phone is in deep sleep probably in the evenings, you don't get the calls. I tested with yesterday's update to 5.xxx and so far didn't lose any calls but didn't call much 👍

[haffenloher]

@cawauk

For some reason it always happens at night when my partner calls between 9pm and midnight, at which point my DND switches on. [...] However, this issue never happens during the day

Sorry if I'm being dumb, but does this mean that for you, Signal calls ring when DND is off and they don't ring when DND is on? That sounds like the expected behavior. Unless your partner is a starred contact for whom DND should be ignored, but that would be a separate issue.

[cawauk]

@cawauk

For some reason it always happens at night when my partner calls between 9pm and midnight, at which point my DND switches on. [...] However, this issue never happens during the day

Sorry if I'm being dumb, but does this mean that for you, Signal calls ring when DND is off and they don't ring when DND is on? That sounds like the expected behavior. Unless your partner is a starred contact for whom DND should be ignored, but that would be a separate issue.

Sorry, didn't explain that well. DND starts at midnight, partner calls before midnight. Usually 11pm. Never rings. But when she calls at 9am, it always always rings.

[jknockaert]

Signal calls ring when DND is off and they don't ring when DND is on? That sounds like the expected behavior. Unless your partner is a starred contact for whom DND should be ignored, but that would be a separate issue.

I'm not sure this is to be expected behaviour. With DND on you can tweak android settings such that regular phone calls still ring (regardless of a contact being starred or not). But Signal wouldn't respect these settings. Incoming Signal calls seem to follow the settings for notifications rather than phonecalls. So if DND mutes notifications incoming Signal calls don't ring.