We are in the process of removing the obsolete init scripts, so trying
to use them directly will make these operations not work at all.
In addition these actions are always denied on NGCP via our permanent
policy-rc.d, so there is no point in even trying.
Change-Id: I0ef824b419f8e48c06c240889626fb3fea43d61e
squashed commit of
commit 4a38d9ad2b (HEAD -> master)
Author: Victor Seva <linuxmaniac@torreviejawireless.org>
Date: Mon Mar 26 14:15:41 2018 +0200
[sipwise_redis_sessions] clean previous local sessions on start
commit a514e6b60d
Author: Victor Seva <linuxmaniac@torreviejawireless.org>
Date: Mon Mar 26 14:08:31 2018 +0200
[mod_shard] clean redis info on shard/send error
if We can't connect to a shard node, clean that info from
redis depending on the stanza
MUC, persistent rooms are always defined in muc module on start, so don't
check for them locally, set as local in redis if no other node has it
closes#3
Change-Id: I33b32dacb6aa4010d520c1d04ef81736d6555370
commit d207cf102b
Author: Victor Seva <linuxmaniac@torreviejawireless.org>
Date: Wed Feb 21 21:23:58 2018 +0100
[mod_shard_client] detect loop on shard messages
Add 'via' attribute to shard stanza in order to detect loops
closes#2
Change-Id: I1e5f947a7b6fdcbd0e0d773b790929dc0681fbcd
This is more like a hack working around the unknown root cause of
why the storage driver is returning trailing garbage for some of
the entries of the key column.
It doesn't happen on the mysql client, so maybe lua related?
Change-Id: I4a5d0b27f0c6dbf9d220e86f1ab6d9e929ad2d89
- Bump Standards-Version to 3.9.8.
- Bump debhelper compatibility version 10.
- Switch from Priority extra to optional.
- Canonicalize Homepage URL.
- Add a debian/.gitignore file.
Change-Id: I0df02c5252fc686c7c40808aa0dcb69636a8af86
* sipwise app logic needs the presence of the nick attribute
always to map jid and nick on MUC room
* FTR, nick is at presence from attribute
Change-Id: I710e98f1a4c5b3ea524d980dea99e3bd70deb072
* sipwise app needs 'urn:xmpp:mam:1' at disco result
* upstream did implement supporting urn:xmpp_mam:[0-2] slightly different
looking through the code y noticed that if the disco has no 'to' it shows
the versions of mam supported
<!-- Out Fri 07 Apr 2017 10:53:38 AM CEST -->
<iq type='get'
id='info1'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
<!-- In Fri 07 Apr 2017 10:53:38 AM CEST -->
<iq id='info1' type='result' to='vseva@sipwise.com/Gajim' from='vseva@sipwise.com'>
<query xmlns='http://jabber.org/protocol/disco#info';>
<feature var='urn:xmpp:mam:0'/>
<feature var='urn:xmpp:mam:1'/>
<feature var='urn:xmpp:mam:2'/>
<feature var='urn:xmpp:sid:0'/>
<identity type='pep' category='pubsub'/>
<feature var='http://jabber.org/protocol/pubsub#publish'/>
</query>
</iq>
That is not what the XEP 0313 says:
<quote>
7. Determining support
If a server or other entity hosts archives and supports MAM queries, it MUST
advertise the 'urn:xmpp:mam:2' feature in response to Service Discovery
(XEP-0030) [15] requests made to archiving JIDs
(i.e. JIDs hosting an archive, such as users' bare JIDs):
</quote>
Change-Id: I1e69f4ce0270b79d3940c8806d4b30ae55aadd98
* If a muc room has no description set, send its room name
instead of "prosody chatroom" to provide proper context
in push messages.
Change-Id: Id8259d69a3ebefa63da97ae0c71e39df0d558a08
* migrate from files to dirs as upstream
* refresh debian/control list of modules
* refresh mod_auth_sql.patch
* update_plugins.sh for automate the process
* keep the list of prosody modules at
prosody-modules.list file
* keep the upstream mercurial revision at
prosody-modules.revision file
Change-Id: Id4a0a2c4e88dae64641270ee79c6ee206f5bb695
Sipwise Jenkins Builder
Andreas Granig
Guillem Jover
Richard Fuchs
Victor Seva
Sergii Kipot
Victor Seva