Phones do NOT ring when have incoming Signal Voice Call #14036
Comments
|
The phone-ringing logic has not changed in any recent updates. |
|
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
<#14036 (comment)>,
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)
<#14036 (comment)>
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
<#14036 (comment)>,
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
<#14036 (comment)>,
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)
<#14036 (comment)>
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
<#14036 (comment)>,
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
<#14036 (comment)>,
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)
<#14036 (comment)>
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
<#14036 (comment)>,
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
<#14036 (comment)>,
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)
<#14036 (comment)>
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
<#14036 (comment)>,
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
<#14036 (comment)>,
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)
<#14036 (comment)>
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
<#14036 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOH2LJV5U4NGNCBANFMYSPL2T4EQ3AVCNFSM6AAAAABYKPEXSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE3DCNZQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Guidelines
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 text was updated successfully, but these errors were encountered: