is it possible to make the notification display text preview instead of the generic "New message" popup in lock screen?

Depends, it might be possible once encrypted push is developed. Else you'd send all your messages to Google/Apple.

Depends, it might be possible once encrypted push is developed. Else you'd send all your messages to Google/Apple.

I was assuming the push notification would wake up the phone, at which point siskin could take over and check with the server -- but from this answer I take it siskin isn't actually woken up and it's purely infos from the push server? :/ In that case I agree it's best not to send content, right...

The server should have the info that it's a call and not a text message though?

Push notifications for calls are in SiskinIM only supported if encrypted push notifications are used. In other cases, the XMPP server has no way to inform the push component which forwards notifications to APNS that it actually received a voice call (not a message).

AFAIK, prosody has support for encrypted notification (including those for voice calls), so please verify that you are using a recent version of prosody (with mod_cloud_notify_encrypted enabled - if I correctly remember the name of that module).

AFAIK, prosody has support for encrypted notification (including those for voice calls), so please verify that you are using a recent version of prosody (with mod_cloud_notify_encrypted enabled - if I correctly remember the name of that module).

Thanks! I don't have this module enabled, I'll give it a try and reopen if required.

Hm, bit of a mixed result here: I've updated prosody to the latest 0.11.13 (from 0.11.12) and enabled mod_cloud_notify_encrypted. my bonus I-don't-really-care question thus got fixed: text messages content now displays along with sender name (but not all the time? sometimes we still get the usual New message! popup instead, I can't see a pattern in how to reproduce) ... but calls still show as "New message!", without any hint that it's a call nor ringing.

Anything else to try? For what it's worth here are the modules I have enabled right now:

modules_enabled = {

  "admin_adhoc";

  "announce";
  "blocklist";
  "bookmarks";

  "carbons";
  "cloud_notify";
  "cloud_notify_encrypted";
  "csi";
  "dialback";
  "disco";
  "groups";
  "http_files";


  "mam";
  "motd";
  "pep";
  "ping";
  "private";
  "proxy65";
  "register";
  "roster";
  "saslauth";
  "server_contact_info";
  "smacks";
  "time";
  "tls";
  "uptime";

  "vcard_legacy";
  "version";
  "watchregistrations";

  "welcome";
  "turncredentials";
  "turncredentials";
"external_services";
};

It is possible that "New message!" is displayed for ie. OMEMO encrypted messages or other types of message for which notification is sent but without a body.

As for calls showing as "New message!", I suppose you would need to reach out to Prosody to clarify what is being sent and what is not in their notifications.

Thanks for the reply!

I've added traces to the mod_cloud_notify module to check what prosody was sending -- I didn't realize that "New message!" came from prosody itself, and I've confirmed it indeed does send just that...

In particular, I can see there's an urn:xmpp:jingle-message:0 notification that goes to the notify module but never makes it to the request sent to server... So I'll go get digging on their side first, it looks like siskin does what's it's being asked to do :)

I'm closing this (again) until I've got that bit working and might reopen it if I need further assistance with siskin at this point, you've been of great help!

For follow up if anyone else stumbles upon this thread: I was right on track, and your advice about mod_cloud_notify_encrypted was the most helpful, it does everything required since last year.

The problem was that siskin does not recheck the discovery informations ( https://xeps.tigase.net//docs/push-notifications/encrypt/issue #421-discovering-support ) when reconnecting on server restart, the account had to be disabled/re-enabled on the device. This can be confirmed by checking for encryption settings in the cloud_notify config of the user in prosody's libdir as I was suggested here: https://groups.google.com/g/prosody-users/c/sSPALD-1Q9k

I have another qualm now that missed calls don't leave any log for the user, but I'll open a different issue for that. Thank you both for the help!