<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
When `auto_bind_ipv6` is enabled on a system without ipv6, kamailio starts, enumerates all interfaces but does not perform no listening at all. In addition, no errors are reported, see below from final part of boot log, no other infos are logged.
While this can be worked around by putting that config value behind a definition and autodetection by an external script, should not it work and just start on ipv4 if ipv6 is not available?
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
Just start Kam as root, with no `listen` directives (to let it listen on all ipv4) and `auto_bind_ipv6` set to 1.
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: lo Fam: 2 Flg: 10049 Adr: 127.0.0.1
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: enp81s0u1u4 Fam: 2 Flg: 11043 Adr: 192.168.1.222
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: wlp0s20f3 Fam: 2 Flg: 11043 Adr: 192.168.1.196
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: br-65b842ff8266 Fam: 2 Flg: 1003 Adr: 192.168.49.1
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: br-kamnet Fam: 2 Flg: 11043 Adr: 172.23.42.1
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: br-f1829eb65bac Fam: 2 Flg: 1003 Adr: 172.18.0.1
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: br-f521fee918b4 Fam: 2 Flg: 1003 Adr: 172.19.0.1
0(1) DEBUG: <core> [core/socket_info.c:1764]: add_interfaces(): If: docker0 Fam: 2 Flg: 1003 Adr: 172.17.0.1
0(1) DEBUG: <core> [core/socket_info.c:1507]: build_iface_list(): received 728 byles
0(1) DEBUG: <core> [core/socket_info.c:1507]: build_iface_list(): received 20 byles
0(1) DEBUG: <core> [core/socket_info.c:1510]: build_iface_list(): done receiving netlink info
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 1 (n: 0)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '127.0.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '127.0.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is lo
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 3 (n: 1)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '192.168.1.222'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '192.168.1.222'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is enp81s0u1u4
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 4 (n: 2)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '192.168.1.196'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '192.168.1.196'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is wlp0s20f3
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 5 (n: 3)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '192.168.49.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '192.168.49.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is br-65b842ff8266
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 6 (n: 4)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '172.23.42.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '172.23.42.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is br-kamnet
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 7 (n: 5)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '172.18.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '172.18.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is br-f1829eb65bac
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 8 (n: 6)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '172.19.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '172.19.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is br-f521fee918b4
0(1) DEBUG: <core> [core/socket_info.c:1542]: build_iface_list(): trying network interface index: 9 (n: 7)
0(1) DEBUG: <core> [core/socket_info.c:1559]: build_iface_list(): iface <IFA_ADDRESS> address is '172.17.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1569]: build_iface_list(): iface <IFA_LOCAL> address is '172.17.0.1'
0(1) DEBUG: <core> [core/socket_info.c:1573]: build_iface_list(): iface name is docker0
0(1) DEBUG: <core> [core/socket_info.c:1507]: build_iface_list(): received 1740 byles
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
head of 5.8 branch as of today
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
ubuntu noble (in a docker container)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4098
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4098(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
I have run in to an issue when sending diameter requests using the ims_diameter_server
module. Shared memory keeps increasing and are not being freed until restart of kamailio.
This leads to all shared memory is being used and no more are able to be allocated.
This only happens when the request is sent synchronously. When sent asynchronously shared
memory is being freed as far as I can see.
Following functions have been used for sending requests.
diameter_request([peer], appid, commandcode, message)
diameter_request_async([peer], appid, commandcode, message)
### Troubleshooting
Sent a bunch of diameter requests and verified that shared memory for the following functions are not freed.
do_receive(600):
AAATranslateMessage(500):
AAACreateAVP(137):
#### Reproduction
It's possible to reproduce by sending sync diameter request and verify shared memory.
Example of diameter request block
```
route[CHECK_LOCATION] {
diameter_request("hss.ims.test.local", "16777217", "306",
"[ " +
"{ \"avpCode\":260, \"vendorId\":0, \"Flags\":64,
\"list\":[ { \"avpCode\":266, \"vendorId\":0,
\"Flags\":64, \"int32\":10415 }, { \"avpCode\":258,
\"vendorId\":0, \"Flags\":64, \"int32\":16777217 } ] },
" +
"{ \"avpCode\":277, \"vendorId\":0, \"Flags\":64,
\"int32\":1 }, " +
"{ \"avpCode\":283, \"vendorId\":0, \"Flags\":64,
\"string\":\"ims.test.local\"}, " +
"{ \"avpCode\":706, \"vendorId\":10415,
\"Flags\":192, \"int32\":0 }, " +
"{ \"avpCode\":700, \"vendorId\":10415,
\"Flags\":192, \"list\": [ { \"avpCode\":601,
\"vendorId\":10415, \"Flags\":192,
\"string\":\"tel:" + $fU + "\" }]}, " +
"{ \"avpCode\":707, \"vendorId\":10415,
\"Flags\":192, \"int32\":0 }, " +
"{ \"avpCode\":703, \"vendorId\":10415,
\"Flags\":192, \"int32\":14 } ]");
xlog("L_INFO", "Sent Diameter request");
}
```
Stats
cdp:replies_received = 343310
shmem:fragments = 142
shmem:free_size = 1221489992
shmem:max_used_size = 948242168
shmem:real_used_size = 925993656
shmem:total_size = 2147483648
shmem:used_size = 558205656
kamcmd mod.stats cdp shm
do_receive(600): 256245808
AAATranslateMessage(500): 64420712
AAACreateAVP(137): 218100320
Total: 538774000
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.7.4 (x86_64/linux) dc393e
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: dc393e
compiled on 13:56:27 Feb 27 2024 with gcc 8.5.0
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
Linux bmatkamas1 4.18.0-553.16.1.el8_10.x86_64 #1 SMP Thu Aug 1 04:16:12 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.10 (Ootpa)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4116
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4116(a)github.com>
voztovoice created an issue (kamailio/kamailio#4160)
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If you submit a feature request (or enhancement) add the description of what you would like to be added.
If there is no content to be filled in a section, the entire section can be removed.
Note that a feature request may be closed automatically after about 2 months
if there is no interest from developers or community users to implement it, being
considered expired. In such case can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the item is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in the proposed feature request.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Expected behavior
#### Actual observed behavior
#### Debugging Data
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a improvement.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4160
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4160(a)github.com>
voztovoice created an issue (kamailio/kamailio#4161)
As Asterisk PBX since version 20.12 supports **SHA-256** for digest authentication, it would be useful to be able to configure the authentication algorithm according to the device with which kamailio communicates.
It could be by indicating the two algorithms at the same time in this parameter:
**modparam("auth", "algorithm", "MD5,SHA-256")**
or have a function that allows activate one or the other depending on the device with which Kamailio communicates.
This because all the softphones I have tested so far do not support SHA-256
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4161
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4161(a)github.com>