no call notification when using own ntfy server #8761
Comments
warioishere
added
the
T-Defect
|
Additional info. I've been talking to ntfy devs and we checked the server deployment of mine, they say my server setup is correct. They said I should reach out to the devs of element on android. Also, it doesnt work with the public ntfy.sh server. Greetings |
|
It may be related to this: https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#ip_range_whitelist |
thanks, just tried this. Added my own push server to the whitelisted IP adresses. Still not luck. Element on Desktop Linux works, it rings. Phone doesnt want to ring when using own push server. Sad no one of the devs answers me on this. |
|
#7069 (comment) follow those steps |
|
Again, I am not having problems receiving notifications at all. Messages notifications do arrive. Also the Push Test on element is sucessful. They only thing i missed was the IP whitelisting, but still, the notifications worked because of some firewall settings I have. The only thing that doesnt work, are call notifications. I dont get notification if someone calls me. Nothing happens, only if I open the app, the call rings. If the app is closed. No ringing, allthough Element passes the Push test, and message notifications do arrive. I checked those steps you linked to me, but no sucess. |
|
|
|
what do you mean by channel notifications? All notifications on Android settings notification wise are allowed for the app. Also i get loud notfication on messages. I will check battery optimiztions on element later. Just curious why I should disable it as it didnt read anything about disabling bat optimizations when own push servers are used. Using googles push services makes the phone ring. Also on battery optimization activated on element. Ill check the logs on element later or tomorrow with my gf thanks in advance :) |
|
I confirm I have the same issue as @warioishere I have to verify but it looks as if other users on my Synapse server wich are using Android with google notification also gets messages notifications but not call notification |
|
I can just tell that the matrix server can reach the ntfy server and everytime I get a message server, I get this on my matrix logs: when someone calls me, there is no log like this. I didnt check the element logs yet, sorry |
|
Here is what I tried : in element by default in the general notification settings, "messages sent by robots" is disable. I enabled it, I will see if this resolve the problem |
That's interesting, can you try your exact same setup with an account on matrix.org ? There might be something with synapse then |
yes, I'll try later. I can imagine that its actually a synapse problem, because it doesnt work n schildichat too, although its a fork I guess and it could have a similar issue. Will let you know |
sorry for this late answer. Tested on matrix.org with my own ntfy server. It works instantly. Getting Call notification. |
|
Additional Info: we are using our own coturn server. Are there things or additional configs needed to be done there? |
|
Additional Info, we are using a Letsencrypt Certificate from letsencrypt for the coturn server, there was once a coturn tester for matrix instances, but I cant find it anymore. It said that time ago that the setup was functional. Now i read this again: Could be the issue? |
|
I changed to ZeroSSL Certificates, now Element Crashes after Calling the phone with my own matrix-synapse instance: |
I am having the exact same problem. With background synchronization as the notification method, it works great (although not always instantly), but at least call notifications work sometimes. However, if I use ntfy, it crashes when an incoming call is received, throwing the exact same error as @warioishere described. I think this might be related to the fact that Element is trying to do something with foreground services, but it isn't allowed (since it is not using that method). I can help with debugging this if you think my theory might be correct. |
sorry to answer so late, but why does it work with googles fcm without a problem, I talked to the devs of ntfy and they say, as far as the logs say, they cant do anything, the push server delivers the message to matrix-synapse properly, and also to the client instantly whenever a message is sent: |
|
If you have an exception FCM don't have that issue because they use an option reserved for system applications ( The good news is there is a way to do the same thing without this privilege. And it will be implemented in the next version of unifiedpush |
Why does it work on matrix.org server then with my ntfy server and the same element version? |
|
This is what this particular exception means. |
I still dont understand why it works on matrix.org Servers and not on my homeserver. What are people doing wrong, as I am not the only one with this kind of problems. I don't need to set element for unlimited background to work with calling notifications with own ntfy server and an account on matrix.org |
|
That's probably how you test it. You have 2 solutions: disable battery optimizations for element (which won't increase your battery consumption), or wait for the new version to be published and adopted by element. |
I dont want to question anything what you say, still I dont unterstand why i dont need to disable bat optimization for element when I use an matrix.org account. I want to understand the matter, not just do some things which I don't understand. |
|
And I just checked. Bat optimization was already deactivated for element |
|
That's interesting. Can you double check you have "allow background usage" and "unrestricted" ? (The new android UI for that is terrible...) There may be another issue behind the scene then |
I double checked:
Element is also not in the Battery Manager in restricted apps |
|
You also have to click on the label "allow background usage" to check if it is optimized |
okay, didnt know that, indeed terribly hidden... It was on optimized, something changed: Now I get a notification for a call, but just a notfication, also now when the phone is screen off, but yea it doesnt ring. But with the matrix.org account on my other phone, with battery optimizations, I the phone rings normally when receiving a call. Both phones have same OS and same element version using the same ntfy server (my own) |
|
Additional info: still this huge delay of message notifications, up to 30min until a newly received messages is shown. |
|
More Info: searched through the issues and found this guys which also had problems: I installed element 1.5.28 and guess what? The phone is ringing also with my matrix server and my own ntfy server. Pls pls pls fix this no calling notfications I would be so happy. We dont want to use googles push or downgrade to such an old version |
|
more information: element 1.5.28 can be in battery optimized mode, it still works. Doesnt need to be in unrestricted mode. |
|
@p1gp1g I am waiting for what you have to say to that older element versions do still work, I see that you are also one of the contributors to element-android. I really would love to know your opinion But hey, my guess is, because I opened another issue where I gathered infos about that little research, and again, no one replies, that its actually not wanted that element works with self hostet push instances? I mean man, that this topic is permantly ignored by whole element-hq just lets me think that, and nothing else, no other reason for that. It used to work, it could be changed back to when it worked, but its not done. |
|
@p1gp1g I know you are propably busy, but can you share your opinion on that? I am running and hosting a whole matrix ecosystem with seperate coturn server since over two years now, and trying to push matrix in switzerland hard, but what everyone hates is, that calling notification do not work, which makes people like not really happy with matrix, and then they switch back to their usual behavior using whatsapp/telegram and co, thats what we want to prevent. |
|
sorry but did you read my messages? I did that, and all I get on normal element is a message notification (for a call), and not a ringing notification. I just get a messages notfication only once and then nothing anymore when someone is calling. I was asking your friendlly, why this element version from the past, as I stated here: makes element/the phone ring when somebody calls. I dont need to even give unrestricted network permissions on that old version. It rings as it should. Even in optimized mode.
|
|
@p1gp1g just another testing, I upgrade on my testing phone from element 1.5.28, to 1.5.30 and thats the version where issues started to arrise: calling notifications stops working. I can make you a video if you dont believe. Version 1.5.28 works with ringing notification even in optimized battery mode. You know, everything I wanna do is just help, and this calling issue is a really issue, I am not dreaming, everyone here that uses ntfy and our server with coturn has the same issue. I am not making this up, if its working on 1.5.28 just completly normaly, why not reverting back to that state in the topic of how notification works? I am not a coder, just a systemadmin. Again, I dont want to bother, but its essential that we have a working calling notification. And thats just not the case. I spend another hour now on testing and giving you information, i dont know how much time I already spend on finding out whats the problem, we even reinstalled our infrastructed, reinstalled coturn, our own ntfy server because people told me I propably have setup problems, but I dont. ntfy server is whitelisted on the homeserver.yml. the Firewalls are not the problem, neither certificates or wrong settings on the coturn server. |
Steps to reproduce
Hello,
I am encountering an issue with call notifications not working when using a custom ntfy server. When selecting Google Push for notifications, both call notifications and the ringtone work as expected. However, switching to a custom ntfy server, the call notifications fail to come through, although message notifications continue to work without issue.
This problem persists across the following setup:
Additionally, if relevant, a custom coturn server has been set up for handling phone and video calls.
Same problem on different phone. Had a p7 Pro with calyx + micro-G before, now having a P8Pro with GrapheneOS, same Problem again.
Could there be a compatibility issue with the custom ntfy server, or is there a specific configuration I might be missing to enable call notifications through it? Any guidance or suggestions on troubleshooting this issue would be greatly appreciated.
Thank you for your assistance.
Outcome
What did you expect?
Calling notification works on external ntfy server
What happened instead?
No ringing at all
Your phone model
Pixel 8 Pro
Operating system version
Android 14 GrapheneOS latest
Application version and app store
No response
Homeserver
f-Droid 1.6.10
Will you send logs?
Yes
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: