### Description
Ping @xkaraman
cmake error on installation; it seems to be looking for various xxxxx.txt files
```
cmake --install .
-- Install configuration: "Debug"
-- Installing: /home/centos/src/CHROOT/usr/local/kamailio/sbin/kamailio
-- kamailio.cfg already exists in /home/centos/src/CHROOT/usr/local/kamailio/etc/kamailio/kamailio.cfg Installing as kamailio.sample
-- Up-to-date: /home/centos/src/CHROOT/usr/local/kamailio/etc/kamailio/kamailio.cfg.sample
-- Installing: /home/centos/src/CHROOT/usr/local/kamailio/lib64/kamailio/modules/async.so
-- Set runtime path of "/home/centos/src/CHROOT/usr/local/kamailio/lib64/kamailio/modules/async.so" to "/usr/local/kamailio/lib64/kamailio"
-- Installing: /home/centos/src/CHROOT/usr/local/kamailio/share/doc/kamailio/modules/README.async
-- Installing: /home/centos/src/CHROOT/usr/local/kamailio/lib64/kamailio/modules/auth.so
-- Set runtime path of "/home/centos/src/CHROOT/usr/local/kamailio/lib64/kamailio/modules/auth.so" to "/usr/local/kamailio/lib64/kamailio"
CMake Error at src/modules/cmake_install.cmake:96 (file):
file INSTALL cannot find
"/home/centos/src/kamailio-5.8/src/modules/auth/auth.txt": No such file or
directory.
Call Stack (most recent call first):
src/cmake_install.cmake:85 (include)
cmake_install.cmake:47 (include)
```
### Troubleshooting
#### Reproduction
```
cmake -DCMAKE_INSTALL_PREFIX=/usr/local/kamailio .
cmake --build .
DESTDIR=~/temp/INSTALLROOT cmake --install .
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4076
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4076(a)github.com>
Module: kamailio
Branch: master
Commit: 763d3622fdb2cdd7916963b6d3f4d532525a5fcc
URL: https://github.com/kamailio/kamailio/commit/763d3622fdb2cdd7916963b6d3f4d53…
Author: Xenofon Karamanos <xk(a)gilawa.com>
Committer: Xenofon Karamanos <xk(a)gilawa.com>
Date: 2024-12-17T13:31:59Z
cmake: Make docs install optional
---
Modified: cmake/modules-docs.cmake
---
Diff: https://github.com/kamailio/kamailio/commit/763d3622fdb2cdd7916963b6d3f4d53…
Patch: https://github.com/kamailio/kamailio/commit/763d3622fdb2cdd7916963b6d3f4d53…
---
diff --git a/cmake/modules-docs.cmake b/cmake/modules-docs.cmake
index f4ac35d3ba6..53beeae6fb9 100644
--- a/cmake/modules-docs.cmake
+++ b/cmake/modules-docs.cmake
@@ -140,6 +140,9 @@ else()
RENAME README.${MODULE_NAME}
DESTINATION ${CMAKE_INSTALL_DOCDIR}/modules
COMPONENT kamailio_docs
+ # Since the depepndencies might not have been build as they are not in the default target
+ # and required to build explicitly using `make kamailio_docs`, allow them to be optional.
+ OPTIONAL
)
endif()
Hello,
the formal notification that the development for the next major version
6.0.0 is now frozen. The focus has to be on testing the master branch.
Also, the master branch should not get commits with new features till
the branch 6.0 is created, expected to happen in 2-4 weeks, a matter of
how testing goes on. Meanwhile, the commits with new features in the C
code can be pushed to personal branches, new pull requests can still be
done, but they will be merged after branching 6.0.
Can still be done commits with documentation improvements, enhancements
to related tools (e.g., kamctl, kamcmd), merging exiting pull requests
at this moment, exporting missing KEMI functions and completing the
functionality of the new modules added for 6.0.
Once the branch 6.0 is created, new features can be pushed again to
master branch as usual. From that moment, the v6.0.0 should be out very
soon, time used for further testing but also preparing the release of
packages.
If someone is not sure if a commit brings a new feature, just make a
pull request and it can be discussed there on github portal or via
sr-dev mailing list.
A summary of what is new in upcoming 6.0 is going to be built at:
* https://www.kamailio.org/wikidocs/features/new-in-6.0.x/
Upgrade guidelines will be collected at:
* https://www.kamailio.org/wikidocs/install/upgrade/5.8.x-to-6.0.0/
Everyone is more than welcome to contribute to the above wiki pages,
especially to the upgrade guidelines, to help everyone else during the
migration process from v5.8.x to 6.0.x.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
### Description
I don't know if this is a bug, or if I missing some config requirements. I mentioned the issue on the sr-user but did not get any comment.
In case serial (or combined serial/parallel) branching is wished, the q value from the registered contact is considered to define the order in which a call is serial branched.
If a CPE registers without q value, the value can be defined by:
modparam("registrar", "default_q", 500)
If a CPE registers with a q value, the client provided value is not being overridden by the default_q setting.
In order to force the order there is a need to override the q value provided by a CPE.
According to the Manual this is possible:
modparam("registrar", "xavp_cfg", "reg")
https://www.kamailio.org/docs/modules/devel/modules/registrar.html#registra…
q - q value of contact (integer 0-1000). It overrides q value given in contact header and default_q parameter. Used in save().
#### Reproduction
Actual config:
```
modparam("registrar", "method_filtering", 1)
modparam("registrar", "max_contacts", 10)
modparam("registrar", "max_expires", 3600)
modparam("registrar", "gruu_enabled", 0)
modparam("registrar", "retry_after", 30)
modparam("registrar", "xavp_cfg", "reg")
modparam("registrar", "default_q", 600)
modparam("registrar", "use_path", 1)
modparam("registrar", "path_mode", 1)
modparam("registrar", "path_check_local", 0)
```
```
route[REGISTRAR] {
# Create an AOR based on the auth_username for the location service.
$var(saveuri) = "sip:" + $aU + "@" + $rd;
$xavp(reg=>q) = 450;
$var(result) = save("location","0x00","$var(saveuri)");
if ($var(result) == -2) {
xlog("L_ERR", "$cfg(route): Too many contacts for $var(saveuri)\n");
sl_reply_error();
}
if ($var(result) == -1) {
xlog("L_ERR", "$cfg(route): Error saving location $var(saveuri)\n");
sl_reply_error();
}
if ($var(result) == 1) {
xlog("L_INFO", "$cfg(route): Contact $var(saveuri) inserted\n");
}
if ($var(result) == 2) {
if ($avp(debug) > 0) {
xlog("L_INFO", "$cfg(route): Contact $var(saveuri) updated\n");
}
}
if ($var(result) == 3) {
xlog("L_INFO", "$cfg(route): Contact $var(saveuri) deleted\n");
}
if ($var(result) == 4) {
xlog("L_INFO", "$cfg(route): Contact $var(saveuri) returned\n");
}
}
```
#### Debugging Data
```
# kamctl ul show | json_pp | grep "Q"
"Q" : 0.6,
"Q" : 0.6,
"Q" : 0.6,
"Q" : 0.5,
"Q" : 0.6,
"Q" : 0.6,
"Q" : 0.6,
```
CPE providing a q value (0.5 in this case for CPE 4) are not overriden.
CPE providing no q value are inserted with default_q value.
Expectation: $xavp(reg=>q) = 450 should cause all CPE to register with Q: 0.45
#### Log Messages
No errors logged while saving contact.
#### SIP Traffic
I could show the Register messages of CPE with q= attribute and without, but I don't think this contributes to solving the issue.
### Possible Solutions
I attempted some other notations like:
$xavp(reg>q)
or
$xavp(reg[0]=>q)
none worked.
I also noted some time ago that setting: $xavp(reg=>max_contacts) also does not work
### Additional Information
```
# kamailio -v
version: kamailio 5.7.6 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 11.4.0
```
```
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
```
Any help / hints appreciated!
-Benoît-
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4068
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4068(a)github.com>
Hello,
I propose to aim freezing the development for 6.0.x series at the end of
the 16th of December 2024 (Monday).
New features that one wants to get in this release series have to be
pushed to git repository or pull requests made for them. Afterwards
usually follows a 4-6 weeks of testing till the first release 6.0.0.
Unfreezing will happen earlier, after the first weeks of testing when
the 6.0 branch will be created.
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com