signalapp
Phones do NOT ring when have incoming Signal Voice Call
Guidelines
- [x] I have searched searched open and closed issues for duplicates
- [x] I am submitting a bug report for existing functionality that does not work as intended
- [x] This isn't a feature request or a discussion topic
Bug description
I and many of my contacts are all having the same problem. Signal does NOT ring when receiving an incoming Signal Voice Call. When you try to post a help request, you just get back an automated response that indicates that 7.35.0 is not the latest version. But that is the only version you can get from Google Play. I found 7.36.1 on GitHub and installed the APK, but the problem still remains. I do not know if this is an app problem or a server problem. Signal text messenging has been slow for the past few days and even small attachments take forever to upload. My contacts are experiencing the same issue and they are all over the world. All other apps on my phone are working normally including SMS/MMS/RCS and Voice Calls by cellular and WiFi. Please investigate this issue. Thank you.
Screenshots
No response
Device
No response
Android version
No response
Signal version
No response
Link to debug log
No response
The phone-ringing logic has not changed in any recent updates. I am not facing any of the issues you have mentioned. It could be a server-side lag in your region.
Dear Sagar,
Thank you for your reply. I was able after loading the APK for 7.36.1 to raise a ticket with Signal support. I provided them with requested debug info and they are investigating the issue. I will update thread when there is further info.
Thanks.
On Wed, Mar 5, 2025, 10:08 AM Sagar @.***> wrote:
The phone-ringing logic has not changed in any recent updates. I am not facing any of the issues you have mentioned. It could be a server-side lag in your region.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJTW572VKH3RM5MQKE32S4HPLAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRGIYTKNJQGI . You are receiving this because you authored the thread.Message ID: @.***> [image: Sagar0-0]Sagar0-0 left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502
The phone-ringing logic has not changed in any recent updates. I am not facing any of the issues you have mentioned. It could be a server-side lag in your region.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJTW572VKH3RM5MQKE32S4HPLAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRGIYTKNJQGI . You are receiving this because you authored the thread.Message ID: @.***>
This is apparently the WiFi issue that happens to people using Signal for periods of time. It has been reported in the past. If I switch to cellular data the problem stops. All of my friends who are having the same issue are using WiFi. I reported this to Signal Support. I suspect that Signal is using some I/O port that is often blocked by WiFi access points and WiFi router firewalls.
On Wed, Mar 5, 2025, 10:08 AM Sagar @.***> wrote:
The phone-ringing logic has not changed in any recent updates. I am not facing any of the issues you have mentioned. It could be a server-side lag in your region.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJTW572VKH3RM5MQKE32S4HPLAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRGIYTKNJQGI . You are receiving this because you authored the thread.Message ID: @.***> [image: Sagar0-0]Sagar0-0 left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502
The phone-ringing logic has not changed in any recent updates. I am not facing any of the issues you have mentioned. It could be a server-side lag in your region.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2701215502, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJTW572VKH3RM5MQKE32S4HPLAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBRGIYTKNJQGI . You are receiving this because you authored the thread.Message ID: @.***>
A debuglog of a call over wifi issue and then a call over cellular, and then timestamp of both calls, would really help our calling team diagnose any potential issue.
Hi Cody,
I cannot generate a debug log for a WiFi call, because the call never goes through, but I will try to generate a call debug log for a cellular Signal call.
On Mon, Mar 10, 2025, 10:42 AM Cody Henthorne @.***> wrote:
A debuglog of a call over wifi issue and then a call over cellular, and then timestamp of both calls, would really help our calling team diagnose any potential issue.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJWPNHOYCI6T3KEBF4L2TWXHNAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHAZTQMBZGQ . You are receiving this because you authored the thread.Message ID: @.***> [image: cody-signal]cody-signal left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094
A debuglog of a call over wifi issue and then a call over cellular, and then timestamp of both calls, would really help our calling team diagnose any potential issue.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJWPNHOYCI6T3KEBF4L2TWXHNAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHAZTQMBZGQ . You are receiving this because you authored the thread.Message ID: @.***>
Here is the link to my debug log:
https://debuglogs.org/android/7.37.2/308d6b48d4c13deafa603fff551df78076bf1c828386137e5215a72bcb35de8d
I initiated a Wi-Fi call from one of my phones to another phone using signal voice call at 13:00 EDT and let it ring until the call failed. There is no indication on the receiving phone that any call was attempted. I again repeated the same process at 13:04.
At 13:07 I set both phones to use cellular mobile data for signal and everything else and initiated a signal voice call again. The call went through immediately and I answered on the receiving phone after approximately four rings.
In addition please see the two attached png files. When the phones are set to Wi-Fi, signal uses IO Port 2053 k n e t d. When the phones are set to Cellular mobile data the io Port used is 1720 which is h.323/q.931.
I suspect that the io port is blocked by commercial and residential Wi-Fi access points. My wired router does not block these ports I suspect because a voice call from my desktop install of signal goes through without any issue.
For now, I have my phone set to use cellular data only for signal while using Wi-Fi for everything else. That work around seems to be effective.
On Mon, Mar 10, 2025, 10:42 AM Cody Henthorne @.***> wrote:
A debuglog of a call over wifi issue and then a call over cellular, and then timestamp of both calls, would really help our calling team diagnose any potential issue.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJWPNHOYCI6T3KEBF4L2TWXHNAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHAZTQMBZGQ . You are receiving this because you authored the thread.Message ID: @.***> [image: cody-signal]cody-signal left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094
A debuglog of a call over wifi issue and then a call over cellular, and then timestamp of both calls, would really help our calling team diagnose any potential issue.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2710838094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJWPNHOYCI6T3KEBF4L2TWXHNAVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHAZTQMBZGQ . You are receiving this because you authored the thread.Message ID: @.***>
When you are on wifi does anything in the app work, even beyond calling? It seems like your logs have lots of general networking errors across the board like we can't communicate at all with our servers. How are you restricting Signal access to a specific network? Are you blocking anything with a custom firewall or anything like that? Anything else unique about your device networking wise? Are you restricting things like letting the websocket through but not REST calls?
Something just generally seems off and trying to figure out what else could be at play. Thanks.
Dear Cody,
Text messages work but with tremendous delays. Nothing else seems to work in signal when on wi-fi. This is only a recent thing. Prior to this past week or so everything was working. There is a setting in Android that allows you to specify whether an app uses cellular or Wi-Fi or can choose whichever. I have my phone set to prefer cellular right now. When I did these logs I had it set to use either setting. I do not have a custom firewall. I am using a grandstream Wi-Fi access point which is connected to a Verizon FiOS router. My friends who was on the ship in the Caribbean was using the shipboard Wi-Fi which was probably provided by access point. My friend who was down in Georgia in their building was using their public Wi-Fi which is also provided by access point. When I use signal from my desktop PC it goes through the very same Verizon router with no problem. I am not specifically restricting anything. I have noticed threads dating back 2 years in Reddit from people having similar problems. They may never have gotten to open a ticket because of the communication disconnect.
On Tue, Mar 11, 2025, 12:21 PM Cody Henthorne @.***> wrote:
When you are on wifi does anything in the app work, even beyond calling? It seems like your logs have lots of general networking errors across the board like we can't communicate at all with our servers. How are you restricting Signal access to a specific network? Are you blocking anything with a custom firewall or anything like that? Anything else unique about your device networking wise? Are you restricting things like letting the websocket through but not REST calls?
Something just generally seems off and trying to figure out what else could be at play. Thanks.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJV5U4NGNCBANFMYSPL2T4EQ3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE3DCNZQGQ . You are receiving this because you authored the thread.Message ID: @.***> [image: cody-signal]cody-signal left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704
When you are on wifi does anything in the app work, even beyond calling? It seems like your logs have lots of general networking errors across the board like we can't communicate at all with our servers. How are you restricting Signal access to a specific network? Are you blocking anything with a custom firewall or anything like that? Anything else unique about your device networking wise? Are you restricting things like letting the websocket through but not REST calls?
Something just generally seems off and trying to figure out what else could be at play. Thanks.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJV5U4NGNCBANFMYSPL2T4EQ3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE3DCNZQGQ . You are receiving this because you authored the thread.Message ID: @.***>
Dear Cody,
I have an explanation and a work around though it is not a solution.
All of the WiFi access devices in my problem and my friends' problems with accessing Signal are employing Client Isolation mode: Internet. This mode blocks the phone or tablet or computer connected to the WiFi from seeing other devices connected to the WiFi network and only allows your device to see the internet. My access points are set that way to prevent anyone hacking my WiFi from seeing my other computers/phones/tablets/etc. My friend who was on board a ship in the Caribbean was using the ship's WiFi access point set similarly, and my other friend was using their apartment building's free WiFi also set the same way. Something in that mode blocks whatever Signal employs to effect its communication. When I turn off Client Isolation mode Internet, Signal functions normally.
So, the workaround is to either set the device (phone/tablet/computer) to use Cellular Mobile Data for Signal exclusively or when there is a WiFi network available that is not set to Client Isolation mode Internet, use that non-Isolated WiFi network.
Regards.
On Tue, Mar 11, 2025, 12:21 PM Cody Henthorne @.***> wrote:
When you are on wifi does anything in the app work, even beyond calling? It seems like your logs have lots of general networking errors across the board like we can't communicate at all with our servers. How are you restricting Signal access to a specific network? Are you blocking anything with a custom firewall or anything like that? Anything else unique about your device networking wise? Are you restricting things like letting the websocket through but not REST calls?
Something just generally seems off and trying to figure out what else could be at play. Thanks.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJV5U4NGNCBANFMYSPL2T4EQ3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE3DCNZQGQ . You are receiving this because you authored the thread.Message ID: @.***> [image: cody-signal]cody-signal left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704
When you are on wifi does anything in the app work, even beyond calling? It seems like your logs have lots of general networking errors across the board like we can't communicate at all with our servers. How are you restricting Signal access to a specific network? Are you blocking anything with a custom firewall or anything like that? Anything else unique about your device networking wise? Are you restricting things like letting the websocket through but not REST calls?
Something just generally seems off and trying to figure out what else could be at play. Thanks.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2714961704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJV5U4NGNCBANFMYSPL2T4EQ3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE3DCNZQGQ . You are receiving this because you authored the thread.Message ID: @.***>
Having the same issue.
-most recent update from playstore (android) -calling from WiFi to a phone on cellular and vice versa -I'm on GrapheneOS but I'll usually be calling people on Samsung (the most recent fold I think) and this issue seems to also happen sometimes when others are trying to call me.
Calls will sometimes just not ring the others phone, sometimes I'll call three or four times on signal and so I'll call with phone app and it immediately goes though and they'll just get a missed call notification in signal.
FireEyeEian,
For me, the issue was that all of the people including myself were on Wi-Fi systems that were using client isolation mode. That is a mode of Wi-Fi where one Wi-Fi user cannot see another Wi-Fi user on the same access point. In communication with the company that made my Wi-Fi access point, they advised me that client isolation mode internet blocks broadcast and broadcast is a protocol used by signal and numerous other apps. When I switched to client isolation mode radio, the problem went away. Also if I switched to cellular data, the problem went away. So I would suggest if you can control the Wi-Fi access point or router see if it is in client isolation mode internet and if so switch to client isolation mode radio. If you are not able to control the mode of your Wi-Fi then you and the other people you wish to communicate with need to use cellular data.
On Wed, Jun 4, 2025, 11:05 AM FireEyeEian @.***> wrote:
Fireeyeeian left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2940393173
Having the same issue.
-most recent update from playstore (android) -calling from WiFi to a phone on cellular and vice versa -I'm on GrapheneOS but I'll usually be calling people on Samsung (the most recent fold I think) and this issue seems to also happen sometimes when others are trying to call me.
Calls will sometimes just not ring the others phone, sometimes I'll call three or four times on signal and so I'll call with phone app and it immediately goes though and they'll just get a missed call notification in signal.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-2940393173, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJTLA3UODPTXFPMDELT3B4DL5AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNBQGM4TGMJXGM . You are receiving this because you authored the thread.Message ID: @.***>
Also experiencing a similar issue. Both outbound and inbound calls from/to me initiated from MacOS and android to another friend on android and IOS (ipad) would not go through. Both of us just are receiving notifications of missed calls. Once we flipped to mobile, we could each receive and make the calls successfully.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
I encountered this issue too last time I tried (like a month ago), so this isn't stale.
Just had the issue happen on my end this time. I was on my phone doing stuff then it starts vibrating and the answer/decline notification pops up and before I can react to it it goes away and says missed call. I immediately call back but with SMS and get through right away. Apparently they sat through multiple rings on signal trying to call me.
I was on mobile network and I believe they were on their trucks wifi.
Please provide updated debuglogs and rough timestamps of when you believe the call came and didn't ring so we can investigate.
Please provide updated debuglogs and rough timestamps of when you believe the call came and didn't ring so we can investigate.
https://debuglogs.org/android/7.50.1/c5ca5993865bd2713a2f4fc4304911e5ea77625b8aee1a0d227b494fb4a2b059
I believe the call was at Sunday (8/3) at around 6:20pm
Next time it happens I'll get a debuglog on both devices immediately if possible.
I looked at your logs and see a missed call handled around 6:19pm. It looks like we learned about the call and got to the ringing state (vibrate only due to phone setting), and then got a remote hangup 3 seconds later. I see message delivery latency at around 3-4 seconds which isn't bad. From your device's point of view the start of the call and end of the call would've been only 6-7 seconds.
Logs from the other device would be helpful for the next time so thank you in advance for trying. In this case it feels like it was some sort of hold up/delay on the caller side and not your side.
I looked at your logs and see a missed call handled around 6:19pm. It looks like we learned about the call and got to the ringing state (vibrate only due to phone setting), and then got a remote hangup 3 seconds later. I see message delivery latency at around 3-4 seconds which isn't bad. From your device's point of view the start of the call and end of the call would've been only 6-7 seconds.
Logs from the other device would be helpful for the next time so thank you in advance for trying. In this case it feels like it was some sort of hold up/delay on the caller side and not your side.
https://debuglogs.org/android/7.50.1/b2467c67a56f755b8daaf53bb3a6978b6f796b22c0ee0b936d85cdff02e77396
That's the other devices log. Just pulled it so hopefully the time is there still. But just got a plan to record the logs when this happens.
Thanks! I see the call from the caller side only lasted about 10 seconds from start to hangup, which lines up with your logs view pretty closely. I think everything more or less worked as expected. A call was started and 10 seconds later, hung up.
I see a few other calls between the two logs, two successful ones lasting a minute or two each. And a forth failed call that you made right after the troublesome missed call. The other device's log reports multiple network loss events during that time and was not receiving messages of any kind. Once network returned (about ~3m later), the call data was received but was stale/hung up by then.
Unfortunately, I don't see anything wrong per se in how the calls went down based on the logs. Not discounting what you and your call partner experienced, just based on the logs things seemed to have gone as one would expect.
Based upon my own experiences, I suggest that both you and the other party switch your phones to mobile data only and try a series of calls at different times of day and different days of week and see if the problem goes away. The reason that I suggest this is because I was having a problem due to the isolation nature of both my access point and the access point of the people I was in communication with. I changed the isolation mode on my access point and many of my problems went away. I still notice that if I initiate or receive a call through signal using Wi-Fi the call sometimes breaks up or is echoey. So give mobile data a try and please report back so that we can all benefit from your experiences.
On Wed, Aug 6, 2025, 3:43 PM Cody Henthorne @.***> wrote:
cody-signal left a comment (signalapp/Signal-Android#14036) https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-3161373576
Thanks! I see the call from the caller side only lasted about 10 seconds from start to hangup, which lines up with your logs view pretty closely. I think everything more or less worked as expected. A call was started and 10 seconds later, hung up.
I see a few other calls between the two logs, two successful ones lasting a minute or two each. And a forth failed call that you made right after the troublesome missed call. The other device's log reports multiple network loss events during that time and was not receiving messages of any kind. Once network returned (about ~3m later), the call data was received but was stale/hung up by then.
Unfortunately, I don't see anything wrong per se in how the calls went down based on the logs. Not discounting what you and your call partner experienced, just based on the logs things seemed to have gone as one would expect.
— Reply to this email directly, view it on GitHub https://github.com/signalapp/Signal-Android/issues/14036#issuecomment-3161373576, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH2LJRPUGD42NE4LFW4SX33MJLH3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNRRGM3TGNJXGY . You are receiving this because you authored the thread.Message ID: @.***>
I am also having this problem. For me it is related to the screen state. Signal rings just fine if the screen is on. There is no ring or other notification if the screen is off when an incoming call is received (except for "Missed video call" in the chat when I next open the app). Use is on wifi. Phone is a Samsung, battery optimization is off however, while I am pretty sure I had excluded Signal from Samsung's lists of apps that could be put to sleep, now that I look again to check, I see that Signal does not appear in the Samsung list of apps to exclude from sleeping. So is Samsung putting this app to sleep when the screen is off? Why does the app not appear in the list of apps to exclude while all my other apps do? (Settings >> Battery and device care >> Battery >> Background usage limits >> (Never auto-sleeping or Sleeping or Deep sleeping).
Edit 1: It seems that Samsung has an "Unrestricted" app mode which causes apps to not appear in the battery optimization lists. However, despite the "Unrestricted" name, it appears such apps do not have no restrictions! Going to Settings >> Apps >> Special Access >> Optimize battery usage and enabling the selector next to Signal allows the app to be shown in the battery optimization lists. Then going to Settings >> Battery and device care >> Battery >> Background usage limits >> Never auto-sleeping and adding Signal to that list is apparently what prevents it from sleeping.
Edit 2: That doesn't fix it either. Still no ring / no notification for incoming video call when the screen is off. Just the "Missed video call" message in the chat when I next open the app.
Same problem here, it happens on multiple phones, both Android and Iphone, all possible optimizations disabled(background allowed) and still have issues. It randomly works..sometime it does..sometime does not..I did not figured it out a pattern yet. Last period of time become unreliable, either is a signal app bug, either big guys does not like this app.
