* provisioning.voip_peer_rules triggers use internally
a join by IP address to insert/update entries in
kamailio.lcr_rule_target. in cases where there are 2 hosts
per peering group with the same IP address, the triggers
fail because they select duplicate peer hosts. to address
that the "lcr_rule_target join" in the relevant triggers
is adjusted to join the hosts tables by gw_name isntead,
since gw_name is guaranteed unique per peer group
(controlled by a unique key)
Change-Id: I36669efc22bb62ad34c57aac4d978435dbb26f0c
(cherry picked from commit b6d98d8464)
* addresses an issue with the foreign key cannot be
recreated as it relies on the lnp_providers table,
affected since MariaDB 10.1.37
Change-Id: I785fcae727e975839c710f327bd10a659384c39c
(cherry picked from commit 2234f05ddf)
* when peer group is changed for a peer rule
it is now correctly reflected in
kamailio.lcr_rule and kamailio.lcr_rule_target
Change-Id: I0a449a224874bd098a3d3c973958f812dbf78530
(cherry picked from commit 676ded265b)
* as the new introduced ngcp.timezone table is not replicated
in my.cnf by default it must be as not_replicated and
only become available when both nodes contain the same
updated my.cnf tempalte and MariaDB is also restarted on
both of them
* fill in ngcp.timezone with a default record
Change-Id: I34c080a6fa62d951fa01218f9049ef3e1d6668f0
(cherry picked from commit 094509c182)
* ngcp.timezone is used in the
v_subscriber_timezone
v_contract_timezone
v_reseller_timezone views as the fallback one
Change-Id: Iaa2d835b4bffddf0f7aeae639f0316756c63f590
(cherry picked from commit 7bf462428e)
(cherry picked from commit 578720e36b)
to definitely have the table in place before
creating the views, even if the table was created by
a replicated .up while not replicating ngcp.* or
ngcp.timezone yet (also added in bakport)
Change-Id: I4071ce82857d5961fd58cc9fb20d19b650c8b64f
* ngcp.timezone is used in the
v_subscriber_timezone
v_contract_timezone
v_reseller_timezone views as the fallback one
Change-Id: I52b7b413c7af3d54577665517197a13ca7a95b7d
(cherry picked from commit 7bf462428e)
* ngcp.timzone table contains the
timezone value from config.yml
general.timezone
Change-Id: Icbf6805bbdd0469aff863e063044994fabf9e00b
(cherry picked from commit 19a8b4dc73)
* this change brings back the accounting.cdr tables
to use composite primary keys, that is compatible with
partitioning
Change-Id: I52dc5e665db1a9b9964b52690a7f0792310e1b1b
(cherry picked from commit 0cb5170683)
* ngcp.tzinfo_version is meant to store
the tzdata package version used in
the 'mysql_tzinfo_to_sql' data synchronisation.
Change-Id: I389ee0d189aff40ab94f55e04025a2e44e7027c8
(cherry picked from commit eb5112d1f4)
* created a stored procedure that moves the firmwwares data
into a new table as chunked blocks, that resolves the
innodb_log_file_size and max_allowe_packet limitations
enabling any size of data
Change-Id: I52ffcc5e0dad4ce35e70cdb13192de1eb54b909c
(cherry picked from commit dacd644cf9)
+ anticipate warnings in .down, if string values
other than "fixed" or "mobile" are present
+ .down scripts now dropped, no rollbacks supported.
Change-Id: I82f4b6d814892586613da3e670e8e50b50ae54b3
(cherry picked from commit 3217af7a52)
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
(cherry picked from commit 33cea1ade1)
* 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