* proper activation of virtual host was only done when "server-started"
event was triggered, so only on start
* ngcp-panel [de]activates the domain via console using hosts:[de]activate()
* hook to "host-[de]activated" to [de]activate the necessary subdomains
Change-Id: I3a94a600ed2b485e069b77ec9310e34a2d5194bf
(cherry picked from commit addb5e5544)
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
* 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
* 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
> mod_c2s: Traceback[c2s]: /usr/lib/prosody/util/sql.lua:189:
> Error executing statement parameters: Data too long for column '_uuid' at row 1
Change-Id: I9e7d6a310ee5e5e8f83cbc97cb2f7ebcf4f534b5
* reduce debug output
* fire_offline_message():
- assert that we have a from nick
- check the original from jid too for is_pushd_blocked()
Change-Id: I0718fe71b9ea06e16de14aeb6017ce3986f16a71
avoid errors like:
> mod_c2s: Traceback[c2s]: /usr/lib/prosody/modules/mod_sipwise_pushd.lua:145:
> attempt to index field '?' (a nil value)
> stack traceback:
> /usr/lib/prosody/modules/mod_sipwise_pushd.lua:145: in function 'get_muc_caller'
Change-Id: Ie32195f49cef6b2145deba6ea78b8b1c43ea7d41
* dataform with domain field, if field value is '*'
result is the list of domains served by the server
Change-Id: I5ea272178a183c633cf38a2f439252d8af168681
- No need to save MUC participants on redis
the message will be processed by sipwise_pushd
module at the server that has the MUC room in memory
- Load sipwise_pushd module at 'conference.' host if
is enabled at the config in order to process
'message/bare' events to catch MUC messages
- fix shard when subscriber offline
Change-Id: I9d56b3867075d496135ff5b530cc6b23aa16b987
Victor Seva
Richard Fuchs
Victor Seva
Andreas Granig