* 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
+ events_relations: store associated id's (int):
-subscriber_profile_id
-pilot_subscriber_profile_id
-primary_number_id
-pilot_subscriber_primary_number_id
-subscriber_profile_set_id
-pilot_subscriber_profile_set_id
+ events_tags: store associated strings:
-number cc,ac,sn
-pilot number cc,ac,sn
-subscriber profile name
-pilot susbcriber profile name
-subscriber profile set name
-pilot subscriber profile set name
no alter table required
Change-Id: I74c54c0c3505fc014c640bf3298e81ab97ac0ad8
* on OLD.enabled = 1 AND NEW.enabled = 0
limit delete to only 1 row to cover cases when
there are several identical rules within one group
(e.g. 2+ ALL NULL rules)
Change-Id: Id19ea55f81324e44870b743ecb1d96f593f1436b
* copy all existing data from autoprov_firmwares.data field
into autoprov_firmwares_data
* remove autoprov_firmwares.data field
Change-Id: I7a62208a323e1bc2d35df4db5828518d897855e3
+_not_replicated, as there can be hundred k's
records (remember a new contact is created for every
subscriber). as mediator copies contact gpp columns
into the cdr, "ALTER contacts" will likely block mediator.
Change-Id: I678291936a03963fd56cfbb6e9f1b2e13e2b05a4
-undo lnp unique constraints
-restoring separate number index to accelerate actual numbers view
-retain cascade delete restrict
-15285->15288
-start date index
Change-Id: I6380479da14302abdb7309da4b7ec22cebe568cd
If set and a call is done within a pbx customer, the call is blocked
in blacklist, and is allowed in whitelist.
Change-Id: I3a113a29baa0c1500e23016d05c8225024dcf295
* "partition" is a reserved word in MariaDB and as such
the existing column with name partition is escaped
as `partition`
* MariaDB is more restrictive to column alterations that have
foreign keys in another tables and as such added
constract drop/add wrapped into LOCK TABLES.
LOCK TABLES is essential there as after DROP FOREIGN KEY
up until the CONSTRANT is recreated again there is a chance
to break the consistency with a wrong sql statement executed
when the up script is being applied.
Change-Id: I4b08a1c5b2c5e1632e2683f62251fe3873ebc58e
creating the index takes few 100msec for
a table with 100k rows, so imho no _not_replicated
required.
Change-Id: I63cc65d934955557675d5a33f7ec9c14bfdde565
tables to support a new subscriber preference, which allows to provide
a custom cli when the a-number matches a configured pattern
Change-Id: Ia7688470978aa88634197176139465e6c674a5b8
This allows to reject any VSC coming from the subscriber, disabling
the possibility to provision subscriber features on the system.
Change-Id: I5cceb70875467a8252ce588ddc90d4c2fbd3c8de
* active_watchers.user_agent had no default value
> [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Field 'user_agent' doesn't have a default value (1364)
Change-Id: Ie9e7091dbc6f4122056fddc01f514222f61f948e
+immediate use for netcologne's "calling party category"
+per source/destination
+per customer/reseller/carrier
+TEXT instead of varchar(255)
+upcoming use eg. for location data.
Change-Id: I24abe06310a7f9ba6f0cb3e044db4ebb0b297cf1
+replace old lnp_provider_id index by multi-column unique index
(safe one index)
+not replicated, as lnp_numbers table could get large
Change-Id: I776358e42345f9a58bd3c755f7e40b12c1ac0a25
in the future, we will connect one rtc-session to all related
networks (via rtc-accounts). therefore, there is no need anymore,
to store the network tag here. assign a default, in order to ensure
compatibility with old and new code
Change-Id: I76c69250217e1295f511e74a17ef55504e526b80
Authoritative is rejecting call with 404 if number is not assigned
to local subscriber.
Skip Rewrite is skipping lnp rewrite rules.
Change-Id: I8d7654bbe02db6f2a92f93712e5b34185ede423d
-original ALTER TABLE accounting.cdr is refactored by introducing first set of separate entity-attribute-value tables. hot-fixable, no downtimes.
-further refactored to extract "provider" and "direction" columns elements (n=2) to manage values in data tables in a n-dimensional mannor. it turns out rateomats column model implementation will get complex to support data tables for arbitrary dimensions n.
-updated table names, removed autoinc staring values (ids cannot be distinguished in data tables any more)
-removed IF NOT/EXISTS
-added GRANTs for 'exporter'@'localhost'
MT#17795:
Melita needs the billing profile package id tracked in cdrs. Note that this is the package assigned to the contract at the time rate-o-mat processes the cdr (no history!), which also specifies the interval for creating balance interval records.
*_*_profile_package_id int(11) unsigned
MT#17795:
Link to the balance interval (billing.contract_balances record) for the sake of completeness. It might also be useful for invoice generation (MT#14253).
*_*_contract_balance_id int(11) unsigned
MT#17795:
The balance interval's cash balance values before and after rating the call.
*_*_cash_balance_before decimal(14,6)
*_*_cash_balance_after decimal(14,6)
MT#17795:
The balance interval's free time balance values before and after rating the call.
*_*_free_time_balance_before int(10) unsigned
*_*_free_time_balance_after int(10) unsigned
Change-Id: Ie891fc13a3610f4cdd9a57ccc573cc395c4e3729
* This will be executed in every node in order to
be able to have different versions during the upgrade process
* skip changes to table uacreg, we don't have it
Change-Id: I5b6256f2b2942da5260ef3b32492188a4357e405
- added location_id to kamailio.contract_preferences
- granted select on provisioniong.contract_locations* to kamailio
- updated provisioning.voip_contract_preferences triggers
- added contract_location_pref to voip_preferences
- added contract_location_pref to voip_preferences_enum
- concurrent_max/out/total are marked as contract_location_pref
- emergency_prefix/suffix/cli are marked as contract_location_pref
Change-Id: I057166e69acfb2dd4900233f2e6543e93e2e2d6e
This is used to enable an LNP lookup for calls from peers using
the network-provided calling party number. Useful to write the
source_lnp_prefix for a specific number block into CDRs.
Change-Id: Ie2a60c6c62d06b688b38db45dba5843735c8981c
We need an option to force outbound calls to peer when call comes
from peer in case the called party is not local but has an LNP entry.
Also, we need to store lnp prefixes in CDR.
Change-Id: I61b3886d545b27d46f0affe8457620601b5be61a
Add new caller/callee_lnp columns for rewrite rules.
Update triggers to populate dialplan from rwr.
Populate new caller/callee_lnp columns with rwr seq numbers.
Change-Id: I6c2e6175357c06608fd28e956a9e2892f32502b3
- The LNP provider table needs to have a routing prefix
- The LNP number table needs to have a key on the number col
Change-Id: Ida7741f2806043bf55178fe9402ee4675cc539c4
The problem I am trying to solve was that the trigger MT#10199 that handles enum
preferences inserts default values into prof_preferences table for the enum
preferences with default values and these defaults become real prefs instead of
the values set by user on the domain level, while user can neither see nor
change prof preferences. This affects all subscribers with any subscriber
profile assigned.
So the decision is to have no defaults on the profile level (like we do on the
subscriber level). User can set the preferences explicitly in the profile.
Also we need to show null option "use domain default" on the profile level.
P.S. While at it, I noticed that preference 'ua_header_mode' did not have the
'use domain default' option, so I had to add it before fixing all preferences.
Change-Id: I3037b0da44bf794b11c564d61de940de27de23e2
Andrew Pogrebennyk
Kirill Solomko
Irina Peshinskaya
Rene Krenn
Hans-Peter Herzog
Gerhard Jungwirth
Richard Fuchs
Andreas Granig
Victor Seva
Jozef Kenyeres
Dominik Kukacka