Update the log_debug preference from boolean version to enum with
three log levels : NOTICE, INFO and DEBUG.
Update the attribute name to call_log_level.
Change-Id: Iab2edbaec82702d74859a687cb814f5c71c68d3f
By default, Prosody automatically handles table management.
As a result, executing the down script will fail because the index
has already been created by Prosody.
Adding IF NOT EXISTS prevents errors when the index already exists.
Change-Id: Ie9289ec5381fd1082047e5c9a762e7a31cf1c55c
In some cases, the prosody.prosody table contains duplicated entries.
This causes the 15841.up migration script to fail when creating the
new index.
To prevent this, add a step before dropping/creating the index to
remove all duplicate rows from the table.
Change-Id: I912dd8484231689d5b1f3dc5087bb69a96c496eb
Added a downscript for 15418/15780 upscript so in the case a downgrade
is executed, it will bring the schema back to pre-trixie situation.
Change-Id: Ib7aff58fe101318a80628a065a983d66546390b3
Move the 'log_debug' preference in the 'Internals' group.
Hide the 'log_debug' preference on domain and profile level,
Withdraw the usage of this preference on subscriber and customer level.
Change-Id: Id62962aa9b69d330ecaf43f78292e4934f4d6e1f
Add new 'log_debug' preference in voip_preferences for Cloud PBX,
allowing scoped SIP debug logging to be enabled at subscriber,
domain or peer level. Preference is exposed to subscribers,
default is disabled.
Change-Id: Ic55bdc937a9804fe266cb2072b786429af2a1828
The upscript 15418.up was created in 2018 and recently it was adapted
for debian/trixie. In turn, this will cause warnings in ngcp-status as
ngcp-mysql-compare-dbs script shows inconsistencies between the json
file and the db itself.
Original change:
719fd2750b
Adaptations:
57b924cce039e6d65add374f456ffb
To fix these inconsistencies, add a new upscript with the exact same
details as in 15418.up including the latest adaptations and a 'DROP
PROCEDURE IF EXISTS.
Change-Id: I9a3d2373954326b2f6786dc8c5c27fc58cb73c44
The new column store a value 0 or 1 to define wether the
ncos is applied when the time_set matches or not.
Change-Id: I65a8085afc61f0607fc90521015a4ceef11adc7b
The new column allows to store the label to show on the
deskphone's displays for the line types 'speeddial', 'forward' and
'transfer'.
Change-Id: I1323a4ac941b9ed15aa0bbd4ed59f387b8349b12
* add column ngcp.db_schema.site_id that is for multi site environments
and defaults to 1.
* the column is relied upon by ngcp-update-db-schema, mainly
to apply not_replicated scripts on sites with the different
site_id but same node name.
* site_id is only inserted for db nodes and otherwise left as NULL
* site_id=NULL means that the revisions are also meant for for both
sites (for ngcp-upgrade scenarios)
* ngcp-update-db-schema improvements:
- add site_id support
- config.node_roles key is now stored as-is and values
are converted as following:
* "yes"/"no" -> boolean True/False
* true/false -> boolean True/False
* else -> string
- check_release_column_exists() is reworked to
check_column_exists(column_name: str)
- fix except cause in main() to return error with the
stack trace as RuntimeError, instead of Exception
(as the latter returned only the error value).
Change-Id: I7c92b37db6562fa39f90a748fc567b100a8d9334
COLR = 'Connected line identification restriction'.
If set to true, the CLI is not displayed to the repmote
party on incoming calls.
Change-Id: I6e41534d8bc5d222f1d19dff1b809869ee9d951d
Add "ON UPDATE CASCADE ON DELETE CASCADE" to the ALTER statement
to fix issue with other down scripts failing to delete the
corresponding voip_preferences_enum entries due to this missing
parameter in 15787.down script.
Change-Id: I6bb91e9c0ea5f03c774ff826e8a29c0f5635eaaf
The new handle contains the announcement that will be played
to the calleer when the callee has the preference 'dnd' activated.
Change-Id: Id3201e9d2ae6ecb56fd858558d0a20d790306033
The down script tries removing some triggers from the wrong database,
add "USE provisioning" to fix it.
Change-Id: I407fde403aa5ee0a87282db0cf53d57d11155422
* shared entries now correctly mutually exclude entries with the same
numbers that are defined by subscribers (goes by precedence).
* add own field to contract and subscriber phonebook views to
identify if the entry was created by the subscriber/contract_id
or inherited.
Change-Id: I5494974b3c16026bb718f9a499e4b25e6b56e4ad
2-Factor-Authentication (2FA) for subscribers based on
voip_preferences only, to support lazy OTP secret initialisation
by application logic.
Change-Id: I265fe1c6e5b75d96aa77b6169ac7508bbf65fbb3
- use coalesce(unix_timestamp(if(x)),if(x)) rather than
coalesce(unix_timestamp(if(x)),0)
- fix from_unixtime(0) also in transform_billing_mappings()
in 15418.up
Change-Id: I55a54deb9e6e3412650e56cefed87a6637a2c0d1
* _effective_start date is now correctly becomes 0 if undefined
to address the general from_unixtime() change in MariaDB 11.5
that requires a value.
* the fix is taken from:
e935ac42 2025-04-29 MT#62676 fixes for mariadb 10.8/debian trixie [Rene Krenn]
Change-Id: I01cf96af3095fbf6e3cb9def9ddeb6c1f1883929
base/8629.up introduced voip_preferences_enum with auto
named foreign key as
"FOREIGN KEY (preference_id) REFERENCES voip_preferences (id)"
which auto created a missing index as
`preference_id` (`preference_id`).
diff/15787.up re-created the foreign key as named
"ADD CONSTRAINT `pref_id_fk` FOREIGN KEY (`preference_id`) ... "
which normally should cause the auto created `preference_id` key
to be renamed to `pref_id_fk`.
but customers who had their database re-synced, had that index
turned from "auto created" to "permanent" and therefore, causing
diff/15787.up to keep the original index name as `preference_id`.
that in turn, caused ngcp-mysql-compare-dbs to report db inconsistencies
as the default schema/.sql files are built with `pref_id_fk`.
the current fix addresses the index issue by dropping it as either
`preference_id` or `pref_id_fk` and creating it as a named index
`pref_id_idx`, so that it wont be affected by the issue anymore.
Change-Id: I4c777902251f915a1b07e92744d78e81087d607c
* fix peering hosts weight update to be correctly performed
only for the same peering host (was for the whole peering group).
Change-Id: Iaca327b1d49f2e50f9aa258e72392ffafe271fd3
* recreate provisioning.voip_phost_*_trig triggers with the same
content to fix a possible discrepancy caused by
15783_not_replicated.up
Change-Id: Id184e50c94ba9f92eb4ba6d243457e0343353704
* triggers are removed from the not replicated script because
they create an issue if this script is applied on the other
node after 15791.up and 15797.up and revert the triggrs to
inintended state.
Change-Id: Iac830c24d0d51d693e6dbe76cea3766feebf7dd8
Added 2 new prefereences inside group "Cloud PBX"
to let the admin to control how many times the AA welcome message
must be played before overflowing in case of timeout or wrong key selection.
Change-Id: I19debd3dc06cd9234355a67ffdc8b5c9db42f61f
* make 15798 as "not_replicated" otherwise the "freeswitch"
database creation is not replicated to the other nodes during
upgrade because there are no my.cnf yet with
"replicate-wild-do-table=freeswitch.%"
* all CREATE statements in the .up script adjusted to be as
CREATE ... IF NOT EXISTS, as the not_replicated script will
be executed once more on the existing deployments.
Change-Id: Idf6c9e8a304639ecabab0a442273cba4b306a6e1
The newly implemented manual ban release needs extra fields to
return for the client.
* Add `last_banned_at` timestamp for admins and subscribers
* Add `last_banned_ip` varchar(45) for admins and subscribers
Change-Id: I691bf2f5c62180d6fb010c3e844a79384f81b3d3
* v_contract_phonebook - returns shared+contract+reseller phonebook
entries, where same numbers are merged into contract > shared > reseller
entries
* v_contract_shared_phonebook - returns shared+contract phonebook
entries, where same numbers are merged into contract > shared entries
* v_contract_reseller_phonebook - returns contract+reseller phonebook
entries, where same numbers are merged into contract > reseller entries
* v_subscriber_phonebook - returns subscriber+contract+reseller phonebook
entries, where same numbers are merged into
subscriber > contract > reselelr entries
* v_subscriber_contract_phonebook - returns subscriber+contract phonebook
entries, where same numbers are merged into
subscriber > contract entries
* v_subscriber_reseller_phonebook - returns subscriber+reseller phonebook
entries, where same numbers are merged into
subscriber > reseller entries
* shared entries of subscribers within the same customer are considered
"customer" entries and shown in v_subscriber_phonebook or
v_subscriber_contract_phonebook
Change-Id: Id66502fadea93be05e3dab7f386e92068fcde21d
This commit adds a list of tables:
- `limit_data`
- `db_data`
- `group_data`
required by the mod_db of freeswitch, which
from now on is in use.
Add them, because we are of the full table
schemas control, not the freeswitch service.
Change-Id: I59b6161a393ca6816cfaba527cf339add55224f5
* Fixes bug reported by frontend team where in case a billing.voucher is updated the
`valid_until` field automaticly updates to the current_timestamp.
Change-Id: Ie4bcd9ebf0eeda066768781c89d892180cfb3c57
* reason for this change is because the related
changes in the kamailio table get replicated to the
active node during the upgrade and that breaks outbound peer
provisioning / selection by running kamailio there
Change-Id: I69416b5737cf05695cbfd1c2e4544faa8b1a2ab2
* reason for this change is because the related
changes in the kamailio table get replicated to the
active node during the upgrade and that breaks outbound peer
provisioning / selection by running kamailio there
Change-Id: I69416b5737cf05695cbfd1c2e4544faa8b1a2ab0
Prefs codecs_id_filter and codecs_id_list are no more selectable.
Records inside kamailio.user_preferences will be automatically deleted by triggers.
Change-Id: I6224a8cae8df7e6f159142a8ee09a0ab9b26b1be
Add a preference, which introduces a mixed mode of handling AA
choices and extensions dialing via AA menu.
Can be enabled or disabled (default).
If enabled then instant extensions dialing mode is used,
otherwise the usual one (which requires dialing through
the *asterisk sign).
Can be applied at the following levels:
- domain (has always default value 'disabled')
- profile (inherits from domain if doesn't have own value)
- subscriber (inherits from domain if doesn't have own value)
Change-Id: Ibf1d08268a9b72d2524881951700776fdc9ec215
voicebox_unavailable sound handle is notsupported since mr5.3
and it is even mentioned as not supported in the handbook.
It is time to removed it completely from the system.
Change-Id: I9bd0122fc192d5d5906494b5051e471556f8778a
The change of the ENUM 'direction' column removing old values
and adding the new ones, creates problems to existing HM
records.
The records with direction 'inbound' or 'outbound' loose
their direction right after the ENUM is updated.
To fix the issue we have before to add the new values,
then migrate the enties, and finally remove all the values
not needed.
Change-Id: Ib350b6aaada2cdabccb01947f131d3389e1a5110
Commit 5f0bfdae7c wrongly disabled
preference ignore_cf_when_hunting at domain level.
Actually in template there is a reference to this parameter at domain level
(it was missed on first analysis) and for this reason
the corresponding flag in provisioning.voip_preferences must be set to 1.
Change-Id: I89b9597e8bc46a8ccf3e07edcb13199a831aef68
* this column is added to billing.admins and
provisoning.voip_subscribers to control the amount
of consequent bans for progressive ban increase.
Change-Id: I09c5205294b11aec16f0c6a7a3b9257ff5b90e01
kthiry
Jose Su
Marco Capetta
Kirill Solomko
Fabricio Santolin da Silva
Rene Krenn
Richard Fuchs
Victor Seva
Alessio Garzi
Bertold Vincze
Donat Zenichev