Signal-ios: Incoming Voice Calls Never Ring

[PlainSite]

When receiving a voice call, there is no audible indication that a call is coming in, even though iOS Home -> Settings -> Sounds -> Ringer and Alerts volume is not off and overall volume is up. "Notification sounds" in Signal -> Settings -> Notifications are on. There is no ring if Signal is the foreground application, there is no ring if Signal is a background application, and there is no ring if the device is on the lock screen.

This is broader than #1467. Even if Signal is in the foreground and I am looking right at it, when a call comes in, I hear nothing.

Steps to reproduce

• Receive a call on Signal.

Actual result: Nothing you can hear.
Expected result: Audible ringing.

Device info

Device: iPod Touch MKHL2LL/A
iOS version: 10.2
Signal version: 2.6.10

[riyapenn]

Does the phone vibrate?

Temporary work around: Update Signal, then go to Signal > Settings > Privacy > Make sure iOS Call Integration is enabled

Adding user logs:
12:52 PM https://gist.github.com/7744b8fd8927d8b47bc564c81df310a0

10:02 AM https://gist.github.com/2a7a27368acd53684f8d10d666f0ea12

[michaelkirk]

@harcesz - this is for reporting issues with Signal on iOS. Could you see if there are similar issues at https://github.com/WhisperSystems/Signal-Android/issues and post a new one if not?

Please include a debug log after receiving a call with this behavior.

[basnijholt]

I have iOS Call Integration enabled and the latest version of Signal and still have this issue.

No vibration, no notification, and no sound, only a "Missed call" notification. When I unmute I do get the call.

[PlainSite]

Unfortunately this bug has come back in recent versions of Signal. I'm now using 2.11.4 on iOS 10.3.2 (14F89) on the same iPod touch. I will often get a text alert for a Missed Call that happened 10 or more minutes prior, even though the iPod has been on wifi the entire time with volume up (although in some cases the iPod screen is blank or "sleeping" while the call comes in). Nonetheless, previously with CallKit, the iPod would "wake up" and play the ringtone to notify the user that a call was coming in.

Furthermore, when trying to call the caller back, there's often a possibly related or separate problem where the call button in the top right simply does not work. It does not respond to taps, and a call is never placed. The only way around this is to restart Signal.

Upon restarting Signal, there's usually a one to three minute period of waiting while the various message threads (no more than ten, most fairly short) load. First, nothing appears, then phone numbers appear in the table view, and finally those are replaced by people's names. But the app is totally unresponsive while this happens, and it takes a much longer time than it should.

So there you go. Three bugs in one.

[PlainSite]

@riyapenn Also, the iPod touch cannot vibrate. It's not a phone.

[AlfonsoMuskedunder]

This is also an issue on iOS 9 devices.

Yesterday I (on Android) called a friend with such device three times, sitting right next to her. The iPhone never rang; only a notification on the lock screen appeared.

In case it might help, here's her debug log: ~ 21:57 https://gist.github.com/anonymous/50bcdfa217989dc59db1d5c15a9bd49d

(Btw, it took a very long time until the sonar tone changed to the dialing tone. If I hadn't wanted to test the issue, I would've hung up thinking a connection was impossible to establish.)

[PlainSite]

This is again a problem and an incredibly irritating one. Signal can clearly be running in the background, and there's no indication whatsoever that a call is coming in.

[michaelkirk]

Can you provide a debug log the covers the time in question?

Also any details about your network connectivity, e.g. were you in wifi? 3G? LTE?

On Sep 3, 2017, at 14:15, PlainSite [e-mail] wrote:

This is again a problem and an incredibly irritating one. Signal can be running front and center, and there's no indication whatsoever that a call is coming in.

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

[rocknjohn]

I also experience this with consistency on both wifi and LTE as both the caller and receiver. I've tried toggling CallKit off and on with no change.

Caller
iPhone 6
Signal 2.15.3.2
iOS 10.3.3

Receiver
iPhone 6
Signal 2.15.3.2
iOS Unknown, probably 10.3.3

To repro, two users should have a chat thread open as if they were messaging one another, then one person attempts to call the other.
Caller: When calling, the phone will show "Signal connecting..." and that loud, uncomfortable, connecting tone occurs over and over, but never advances to the ring tone as it should. Eventually I give up and end the call.
Receiver: Receiver _has their phone open to the chat thread_ for the person who they are expecting a call from. Phone will never ring and then a "missed call" notification will appear in the thread.

I believe a critical part of this bug is that _Signal is open on the receiver's phone when the incoming call is attempted_ because I am able to call successfully when they do not have the app open.

I can submit a debug log but would prefer it to be fully redacted https://github.com/WhisperSystems/Signal-iOS/issues/2540

[jdrissel]

This is also happening on my Android phones. Both a S7Edge and a Note8 are impacted.

[jdrissel]

I suspect this may be at least partially a server side problem because the same thing happens on Android.

Here are the debug logs, call placed from iphone7 to a note 8. The iPhone got a pastekit error10001 when I tried to get a log. Here is the Android log: https://gist.github.com/c7136cb8d99a20cd7aa3964923a2cc85

Here are the logs for a call from the Note 8 to the iPhone 6. Again the iPhone failed to submit a log.
https://gist.github.com/668577b3e0ff5a0be87c8a9af8b81436

I will cross post to the Android github too....

[PlainSite]

This continues to be a problem with Signal version 2.18.2.1 on iOS 11.1.1. Ringer volume is up. Yet the iPod does not ring, does not display a graphical indication that a call is coming in, and does not tell me with a notification that I have a missed call. I only see in the call history that a call has been missed after the fact.

[reliableboss]

While on signal app call, my incoming voice calls gets rejected. I does not know of the incoming call, there is no ringing or any notification. I only know when after signal call I check the call log, there is rejected call. I am using android phone.

[AlfonsoMuskedunder]

@reliableboss This is the issue tracker for iOS devices. But there are a couple of similar reports in the Android tracker, e.g. https://github.com/WhisperSystems/Signal-Android/issues/6990.

[mikemorris]

I experienced a variation of this issue last night on an iPhone 8 running iOS 11.1.1 - incoming voice calls would only ring while the device was locked. If the device was unlocked (with Signal in foreground or background), I'd only get a missed call notification after the caller hung up, no incoming call notification of any sort appeared while the device was unlocked.

I have iOS Call Integration enabled and Show Caller's Name & Number disabled. Always Relay Calls is disabled. I didn't have debug logs enabled but I could possibly turn them on to attempt to reproduce if that would be helpful.

[michaelkirk]

Can you provide a debug log? (Settings > advanced > debug log)

And ideally have the caller provide one as well?

And what (local) time did each failing call occur so I can trace it down in the logs.

On Dec 6, 2017, at 13:51, Mike Morris [e-mail] wrote:

I experienced a variation of this issue last night on an iPhone 8 running iOS 11.1.1 - incoming voice calls would only ring while the device was locked. If the device was unlocked (with Signal in foreground or background), I'd only get a missed call notification after the caller hung up, no incoming call notification of any sort appeared while the device was unlocked.

I have iOS Call Integration enabled and Show Caller's Name & Number disabled. Always Relay Calls is disabled. I didn't have debug logs enabled but I could possibly turn them on to attempt to reproduce if that would be helpful.

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

[PlainSite]

It's been a year. This is still an incredibly annoying problem.

[hajoucha]

The same here.

[alexanderadam]

Did you check whether you use a VPN or AdBlocker that blocks access to Google servers?

If so, this might related to Signal Android issue 6990.

The other issue was closed because of the closing of user feedback (or called more euphemistically "Spring Cleaning"). However, I want to mention it again:

Signal should ideally show the user(s) that, for some reason, no successful connection could be made. And maybe even give a hint to the user(s) like Some AdBlocker might be the reason. If you use one ensure that you whitelisted $host..

The device that doesn't get the call can obviously see that this is probably a technical issue because it never "rings" but shows the "missed call" notice afterwards.

So it seems to be technically possible.

[niechoda]

Hi guys,
Signal version 2.30.2.16
iPhone X, iOS :12.1

Same situation as described above "Incoming Voice Calls Never Ring", I will get : "Missed Call" notification but no, ring.
I can make outgoing calls / chat without any problems
As amazing software as "Signal" is, this bug makes it unusable on my iPhone.

Any suggestions for debugging / fixing, would be much appreciated .

[michaelkirk-signal]

@niechoda - is the call that you're having trouble connecting with someone who is in your contacts?

Are you the caller or the callee?

Do you, or the person you're calling have "always relay calls" enabled in settings?

[niechoda]

hi @michaelkirk

• person was not in my contacts, and adding it fixed that problem.
• so is it a feature that if number is not in contacts it will not ring ?
• none of the people involved has "Always Relay Calls" enabled

[PlainSite]

Still a problem, and silent calls are almost always for people in the contact list.

[michaelkirk-signal]

A handful of call connectivity issues have been resolved since this was opened.

In particular, the issue that @niechoda was having should now be resolved.

If you have trouble with calling in the future, please file a new issue with up to date details and a fresh debug log.

[jrw]

On my Android, I had to enable Settings -> SMS & MMS -> WiFi Calling compatibility mode in order to get any kind of notification that I was receiving an incoming call.