* 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
(cherry picked from commit 1cfafba736)
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
(cherry picked from commit 8dab7cc0e4)
The preference allows to enable the conversion of SIP INFO messages
containing application/dtmf-relay or application/dtmf payloads to
RFC DTMF events.
Added note that the feature is restricted to internal generated
INFO messages and it will not detect and convert exetrnal generated
INFO messages.
Change-Id: I02b5a72f3f5c1c5dfc1e5ed8a8746013ef9a1901
In particular add the following preferences:
* concurrent_max_in
* concurrent_max_in_per_account
* concurrent_max_in_total
Change-Id: I02bf2bc567acf52c832a2808b319b89c3d73fff4
* tables for intermediate cdrs are created as copies
from existing cdr tables
* the tables have similar names and prefixed with int_
* partitioning is removed in those tables
* int_cdr has a new column acc_ref that contains a reference
to the related acc 'INVITE' record,
and also used as a unique index
Change-Id: Ib9951d9d4618c4cfbb0991da3e8c803a7ccb61dd
* is_ccare flags a user as customer care one
and is used in ngcp-panel to restrict the role
only to Customer/Subsceriber related scopes
Change-Id: I72ff7d2d3ba6e56306e1a326f26475cee28e8100
* allowed_ips_header preference provides with a SIP
header name to take the IP address from for
"allowed_clis" ipauth check
Change-Id: I23790881c35534a82993e9afd645a754fb5723c0
* 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
* this table is supposed to group cdrs
by a common identifier. for now it is call_id
it does not contain a dictionary like other
cdr_* relation tables because the field must be
of the similar type as well as to make it possible
to have multi field groups in the future.
Change-Id: Ie304c00bb5f061c80402de7a1072c206b11619ab
Must be 0 for string-key/string-val instead of 1 for
string-key/int-val, otherwise kamailio complains about
invalid int parameter in lua script.
Change-Id: I3421f3706efab9703fb046e0c6981785bb4bc696
We're querying for the alias during registration phase to check if the
dev-id passed by the device is a native alias or a devid alias.
Change-Id: I183cde2690e50bf233f388d79783ce1e5e868aa9
Sipwise Jenkins Builder
Kirill Solomko
Marco Capetta
Andreas Granig
Rene Krenn
Flaviu Mates
Guillem Jover
Irina Peshinskaya
Richard Fuchs
Alexander Lutay