The previous fix was backported to mr4.5 and mr3.8 LTS while mr5.[0-3] was untouched.
It resulted to the fact that systems upgraded via release where grants.yml has user 'export'
will have it restored. Also we need to care about Carrier's 3308 here so we have to use _not_replicated.
The current fix will be included into mr5.5.1+ only,
so it is safe to use "IF EXISTS" as in upgrade
mr4.5->mr5.5 it will be executed in new MariaDB 10.1
Change-Id: I5f1612393aea2676f96d6824a9ab641d29bb8407
+ anticipate warnings in .down, if string values
other than "fixed" or "mobile" are present
+ .down scripts now dropped, no rollbacks supported.
Change-Id: I82f4b6d814892586613da3e670e8e50b50ae54b3
* kamailio.acc_backup and kamailio.acc_trash are not replicated
and therefore, changes to those tables must be done separately
for sp1 and sp2
Change-Id: I633838d2bbf6f346de0a9e97dcfd9234060e334e
* remove primary key and create (id,start_time) index
for the following accounting tables:
- cdr
- cdr_cash_balance_data
- cdr_time_balance_data
- cdr_relation_data
- cdr_tag_data
Change-Id: I399e9504496bdfd4600466d8fb67abccb3a0c40f
* backward compatibility to support existing 0 values
of the 'lock' preference in voip_usr_preferences
Change-Id: I7c497e14695891d3b7a4ee018cf5429f79a0a485
- required to support acc-cleanup's "backup" and "archive"
modes. for "cleanup" mode, they are not needed considering
the original plan with cdr delete triggers.
- delete triggers for accounting.cdr slow down the cleanup,
so we take them out. separate cleanup jobs should be registered.
this way, the performance of 3.x cleanup must be axactly restored.
- same for events; also there was no index for the
events.timestamp column yet
Change-Id: Ia117e237533814b5175eb2b1fab8fdc153878f83
* add t38 preference to enable/disable t38 support per subscriber
* add ecm preference to enable/disable ecm support per subscriber
Change-Id: I3ae69fa49c952732c012c5fd385104e5ebdc92fa
* Add probe column to provisioning.voip_peer_hosts
* Add trigger to populate kamailio.dispatcher on active probing
* Fix kamailio.version table to version 4 of dispatcher table to
use the attrs column.
* Write peerid (used for routing) and also peername and peergid
(used for monitoring) into dispatcher attrs
* Only enable probing if peer is enabled
Change-Id: I29bc23ec27bf59672656fc972171a518aecce133
by adding the subscriber_id. This is still fine, to reference them
uniquely per subscriber but allows e.g. for the same name in different
subscriber like the automatically created sets like "quickset_cfu".
Change-Id: If72354639f501e8925680a664ef61951940b8ece
Storing salt and bcrypt hash per admin in this column.
Also clear existing ssl certs for security reasons. If someone
lost his key, it needs to be deleted and re-generated.
Change-Id: I0db91865f1ee248037bb0eaa31a97937c71d0ad6
since it can be written using a separate db connection,
pointing to a database that is not fully replicated,
foreign keys will cause failing inserts, updates etc.
Change-Id: I65108abdce1f5ad86b982adaf4d0d762fd0a634d
Rene Krenn
Alexander Lutay
Andreas Granig
Andrew Pogrebennyk
Jozef Kenyeres
Kirill Solomko
Irina Peshinskaya
Hans-Peter Herzog
Gerhard Jungwirth
Richard Fuchs