Tigase XMPP Server comes with support for XEP-0357: Push Notifications allowing user to receive notifications for messages received while his XMPP client is not connected enabled by default.
You can disable this feature with following settings:
'sess-man' { 'urn:xmpp:push:0' (active: false) {} }
If you wish Tigase XMPP Server not to forward body of the message or sender details in the push notification you can disable that with following settings:
'sess-man' { 'urn:xmpp:push:0' () { 'with-body' = false 'with-sender' = false } }
Push notifications may also be sent by Tigase XMPP Server when new message is received and all resources of recipient are
in AWAY/XA/DND state.
To enable this type of notifications you need to enable additional push delivery extension named away
in default push processor:
'sess-man' () { 'urn:xmpp:push:0' () { 'away' () {} } }
As this behaviour may not be expected by users and users need a compatible XMPP client to properly handle this notifications
(XMPP client needs to retrieve message history from server to get actual message), in addition to enabling this plugin on
the server, XMPP clients need to explicitly activate this feature. They can do that by including away
attribute with value of true
in push enable
element send to the server, as in following example:
Enabling Push notifications for away/xa/dnd account.
<iq type='set' id='x43'> <enable xmlns='urn:xmpp:push:0' away='true' jid='push-5.client.example' node='yxs32uqsflafdk3iuqo'> <x xmlns='jabber:x:data' type='submit'> .... </x> </enable> </iq>
If later on, user decides to disable notification for account in away/xa/dnd state, it may disable push notifications or once
again send stanza to enable push notification but without away
attribute being set:
<iq type='set' id='x43'> <enable xmlns='urn:xmpp:push:0' away='true' jid='push-5.client.example' node='yxs32uqsflafdk3iuqo'> <x xmlns='jabber:x:data' type='submit'> .... </x> </enable> </iq>