* defines the format of emergency_location_object field
* set cirpack as default since that was the original format
* add PIDF-LO for implementing TR Notruf
Change-Id: Ifcac50b7147f7233d42e1abea75c6cfc1d59f604
* voip_preferences 'type' can be 2, means' blob'
* voip_preferences data_type enum add: 'blob'
* 4 new tables:
- voip_dom_preferences_blob
- voip_usr_preferences_blob
- voip_contract_preferences_blob
- voip_peer_preferences_blob
(they are innodb page compressed)
* triggers on insert/delete on these tables
cause the 'value' field of the related
voip_usr/dom/contract/peer_preferences table to
be updated with the id of the record, required
for kamailio to find the related blob record without
replicating the blob data
* procedure for adding a new blob entry:
1. insert into voip_usr_preferences with the empty value
2. insert into voip_usr_preferences_blob
3. the voip_usr_preferences value will be automatically updated
with the id of the created blob record
Change-Id: I9330613f50de20bc098a94f3fc28cfd4b3ad3c68
Added new usr_preferences with attribute = "no_404_fallback"
This option will enable/disable the user to disable 404 fallback when the callee UAc
replies with a 404 not found.
Change-Id: I414014e920f8f0fbd690b8b3551b0afbed5c6625
* with MariaDB 10.5 REFERENCES syntax in the CREATE TABLE
column definition now creates automatic foreign keys.
That causes duplicate foreign keys, one manually defined
in the CREATE TABLE/ALTER TABLE statements and one that is
automatically created with _ibfk_<int> suffix. Therefore,
the REFERENCE syntax in the column definition is removed,
as all of those REFERENCEs are covered by the FOREIGN KEY
ones.
Change-Id: I969a8d3d31d680c0e7f15c1cfb31e8c2abe6eb74
* this table is in the provisioning database and is used
to add additional location mappings for terminated calls on a
subscriber instead of the 'location_from_subscriber' preference
* 'location_from_subscriber' preference data is migrated into
the new table
Change-Id: I92726e765c51e87c4d815d01161d8866fe58ef9c
* this new view accumulates possible auth data
containing both subscrber usernames and devices
(aliases with is_devid=1)
* this view is used in subscriber auth and the proxy
code to fetch registered devices not only by
subscriber username but also by the device
Change-Id: Ic4e2596ad461c70acf34cf75a2590640813ec2ca
* Switch all 'redirect_sipwise' and 'profile_sipwise'
to 'redirect_ale' bootstrap method
* Remove them from enum
Change-Id: I394d5926c75a3784cb0fecff983ff3cfd3a889a5
This user/password combination is not used any longer by the monitoring
system and it is a security risk as it is using a hardcoded password
instead of the one from constants.yml.
Change-Id: If00789343e57c5e1e058e431d3dcfc59a6e3fd58
A new 'peer_group_tag' preferences allows to store a string value, which
will be used to narrow peering selection.
The 'caller_pattern' of a peering group has to match this tag to be
considered for outgoing calls.
Change-Id: Ia1ce7a70a3b036f7c37b054c0aeba36fb9b21352
* The 'is_system' column will be used for users
that will have permission to see, create,
edit, delete lawful intercept admins
* Make the default administrator is_system and
revoke its lawful_intercept flag
Change-Id: Ib3349d4e5719f1a16df00647f24ac49174ccc792
this cdr tag will be used to persist the compressed
delta datastructure for contract_balance records.
additional tablespace consumption is minimal: there
will be only one string value (~20chars on average)
required per cdr.
Change-Id: I32557443df2efa7381c85ddfb8c380c8df02df5e
* Store 'email' for administrators to use
for password reset
* Add additional 'can_reset_passsword' column
to indicate wether an admin can request
password reset
Change-Id: If383e1328eb091c68b8419c574dfae307e1b7920
A regression found in mr7.5 forced to apply an up script only
in that specific version (commit 5580ed34).
The commit is to create a dummy up script in order to keep the
ids consistent in all the versions.
Change-Id: I3d16a9edc3791ac030018ba95c4704388b5e4066
* determine the master db node name to use
for ngcp-sync-db master-slave replication restoration
if the CENTRAL_DBHOST is set by default to db01 only.
if the current nodename ends with "a" then db01a is used,
otehrwise db01b is used as the master host. that is
to make sure that during the upgrade the correct "side"
is used to replicate the data from and avoid lossy
statements that break replication.
Change-Id: I1a51bd0d975390d9269ef5208ce8275f9e055a1f