Module: kamailio
Branch: master
Commit: 9c4e3fc30c63095a71e42bb480fcf26699ee8ecc
URL: https://github.com/kamailio/kamailio/commit/9c4e3fc30c63095a71e42bb480fcf26…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-26T13:39:16+01:00
db_berkeley: km_doc - updated project name
---
Modified: src/modules/db_berkeley/km_doc/db_berkeley_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/9c4e3fc30c63095a71e42bb480fcf26…
Patch: https://github.com/kamailio/kamailio/commit/9c4e3fc30c63095a71e42bb480fcf26…
---
diff --git a/src/modules/db_berkeley/km_doc/db_berkeley_admin.xml b/src/modules/db_berkeley/km_doc/db_berkeley_admin.xml
index 7d7a9bad4e..bd74a1eee2 100644
--- a/src/modules/db_berkeley/km_doc/db_berkeley_admin.xml
+++ b/src/modules/db_berkeley/km_doc/db_berkeley_admin.xml
@@ -9,9 +9,9 @@
]>
<chapter>
-
+
<title>&adminguide;</title>
-
+
<section>
<title>Overview</title>
<para>
@@ -35,7 +35,7 @@
</itemizedlist>
</para>
</section>
-
+
<section>
<title>External Libraries or Applications</title>
<para>
@@ -199,7 +199,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)
Installation of Kamailio is performed by simply running make install
as root user of the main directory. This will install the binaries
in /usr/local/sbin/.
- If this was successful, openser control engine files should now
+ If this was successful, kamailio control engine files should now
be installed as /usr/local/sbin/kamdbctl.
</para>
@@ -212,7 +212,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)
<para>
Edit &ctltool;rc - There are two parameters in this file that should be
- configured before openserctrdb script can work properly: DBENGINE and DB_PATH.
+ configured before kamdbctl script can work properly: DBENGINE and DB_PATH.
Edit file: '/usr/local/etc/kamailio/&ctltool;rc'
</para>
<programlisting format="linespecific">
@@ -228,7 +228,7 @@ modparam("db_berkeley", "journal_roll_interval", 3600)
The DB files are initially seeded with necessary meta-data.
This is a good time to review the meta-data section details,
before making modifications to your tables dbschema.
- By default, the files are installed in '/usr/local/share/kamailio/db_berkeley/openser'
+ By default, the files are installed in '/usr/local/share/kamailio/db_berkeley/kamailio'
By default these tables are created Read/Write and without any journalling as
shown. These settings can be modified on a per table basis.
Note: If you plan to use kambdb_recover, you must change the LOGFLAGS.
Module: kamailio
Branch: master
Commit: b0c51f5768afe7869d7aadfc05bee40863975b43
URL: https://github.com/kamailio/kamailio/commit/b0c51f5768afe7869d7aadfc05bee40…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-26T13:36:36+01:00
permissions: updated project anem in same register deny file
---
Modified: src/modules/permissions/config/register.deny
---
Diff: https://github.com/kamailio/kamailio/commit/b0c51f5768afe7869d7aadfc05bee40…
Patch: https://github.com/kamailio/kamailio/commit/b0c51f5768afe7869d7aadfc05bee40…
---
diff --git a/src/modules/permissions/config/register.deny b/src/modules/permissions/config/register.deny
index 920ea482f6..be20d1563e 100644
--- a/src/modules/permissions/config/register.deny
+++ b/src/modules/permissions/config/register.deny
@@ -1,6 +1,4 @@
#
-# $Id$
-#
# Suppose that we have a PSTN gateway with IP address 1.2.3.4
# We should prevent REGISTER messages that contain that IP
# address in Contact header field because that can cause serious
@@ -22,5 +20,5 @@ ALL : "^sip:.*1\.2\.3\.4$"
# domains that point to any IP. To prevent this the usage of hostnames
# and domains in the Contact header field should be avoided.
# A better solution to this problem is the usage of the dst_blocklist
-# feature in the openser core. All "critical" IPs should be added to
+# feature in the kamailio core. All "critical" IPs should be added to
# this list.
Module: kamailio
Branch: master
Commit: d2a1df24b8042de7802bbf466441cda95b7e64f2
URL: https://github.com/kamailio/kamailio/commit/d2a1df24b8042de7802bbf466441cda…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-03-26T13:25:15+01:00
db_oracle: docs - tool name is kamailio_orasel
---
Modified: src/modules/db_oracle/doc/db_oracle_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/d2a1df24b8042de7802bbf466441cda…
Patch: https://github.com/kamailio/kamailio/commit/d2a1df24b8042de7802bbf466441cda…
---
diff --git a/src/modules/db_oracle/doc/db_oracle_admin.xml b/src/modules/db_oracle/doc/db_oracle_admin.xml
index e5e9842fa1..05e6aaccf2 100644
--- a/src/modules/db_oracle/doc/db_oracle_admin.xml
+++ b/src/modules/db_oracle/doc/db_oracle_admin.xml
@@ -143,16 +143,16 @@ modparam("db_oracle", "reconnect", 0.5)
</itemizedlist>
</section>
<section>
- <title>Utility openser_orasel</title>
+ <title>Utility kamailio_orasel</title>
<para>
- For working with &ctltool; script, should be able to print the 'query'
- results to the terminal in a user-readable form. The standard command-line
- Oracle client (sqlplus) is not quite suitable for this, as it cannot align
- row width to real (received) data's (it always prints a cell width as
- described in the db scheme). This problem has been solved by inclusion the
- utility openser_oracle, which formats printing approximately in the same
- way as the 'mysql' client utility. In addition, this utility known about
- the "agreements and types" in DB that are used in &kamailio; for the work
+ For working with &ctltool; script, should be able to print the 'query'
+ results to the terminal in a user-readable form. The standard command-line
+ Oracle client (sqlplus) is not quite suitable for this, as it cannot align
+ row width to real (received) data's (it always prints a cell width as
+ described in the db scheme). This problem has been solved by inclusion the
+ utility kamailio_oracle, which formats printing approximately in the same
+ way as the 'mysql' client utility. In addition, this utility known about
+ the "agreements and types" in DB that are used in &kamailio; for the work
with Oracle and formats printing taking these into account.
</para>
</section>
Hello!
In many cases, I missed the ability to set attributes to a dispatcher group. Right now I’m in need to disable/enable ping checks per group. We could also use that to have alphanumeric aliases so I could use
ds_select_dst(”STUPIDPBXS”, ”6”)
If anyone else has looked into this we can join forces, otherwise I’ll make a proposal and some code for it. If there are objections from a beauty, syntax, architecture or just alignment of the stars reason - any reason that is - please let me hear it now before I start running against a wall just to find out it’s not doable or simply the wrong thing to do :-)
Cheers,
/O