### Description
Trying to get NATS module working but Kamailio is refusing to start.
```
Sep 27 23:08:27 server kernel: kamailio[338880]: segfault at 70 ip 00007fe97b06f1cc sp 00007fff72d158f0 error 4 in libuv.so.1.0.0[7fe97b066000+1f000]
Sep 27 23:08:27 server kernel: Code: 5a 85 ff ff b8 ea ff ff ff c3 0f 1f 40 00 f3 0f 1e fa 8b 4e 30 83 f9 ff 0f 84 80 00 00 00 48 83 ec 08 85 c9 0f 88 90 00 00 00 <3b> 4f 70 73 45 f7 d2 21 56 28 48 8d 4e 18 48 89 f0 48 8b 76 18 75
Sep 27 23:08:27 …
[View More]server systemd[1]: Started Process Core Dump (PID 338886/UID 0).
```
#### Log Messages
In the log message I'm getting the following error:
```
INFO: nats [nats_mod.c:437]: nats_init_connection(): adding server [nats://192.168.1.1:4222] [1]
ERROR: nats [nats_mod.c:456]: nats_init_connection(): could not create nats options [System Error]
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(version: kamailio 5.6.1 (x86_64/linux) 34e6dd)
```
NATS Server version:
```
nats-server: v2.9.0
```
libnats version:
```
libnats.so.3.4.0
```
* **Operating System**:
```
CentOS Stream 9
5.14.0-163.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 8 13:52:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```
* **Module Configuration**:
```
loadmodule "nats.so"
modparam("nats", "nats_url", "nats://192.168.1.1:4222")
```
There is no issue at the network/firewall level as by using telnet I'm able to connect to the NATS server successfully.
What is weird is that with tcpdump I can't see even attempts to connect to the NATS server.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3253
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3253(a)github.com>
[View Less]
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3508
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3508(a)github.com>
Hi team,
I was tested with Volte by using kamailio sip server . I want to know its supporting VoNR for 5G voice call .
For my understanding
VoNR requires kamailio IMS to use SBI interface, it's not implemented in kamailio IMS.
Please correct me if I am wrong ?
If not implemented means , any pipeline in feature.
Regards,
Sivaneshkumar K
Mobiveil INC., CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may …
[View More]contain proprietary confidential or privileged information or otherwise be protected by law. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender and destroy all copies and the original message.
[View Less]
Module: kamailio
Branch: master
Commit: 7ca151a0479e4971980f4bbbc10cbd8f7deea1b6
URL: https://github.com/kamailio/kamailio/commit/7ca151a0479e4971980f4bbbc10cbd8…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-07-10T11:01:31+02:00
modules: readme files regenerated - msilo ... [skip ci]
---
Modified: src/modules/msilo/README
---
Diff: https://github.com/kamailio/kamailio/commit/7ca151a0479e4971980f4bbbc10cbd8……
[View More]
Patch: https://github.com/kamailio/kamailio/commit/7ca151a0479e4971980f4bbbc10cbd8…
---
diff --git a/src/modules/msilo/README b/src/modules/msilo/README
index 987c9504ebd..046a57ca068 100644
--- a/src/modules/msilo/README
+++ b/src/modules/msilo/README
@@ -70,7 +70,8 @@ Juha Heinanen
4. Functions
4.1. m_store([owner])
- 4.2. m_dump([owner])
+ 4.2. m_store_addrs(owner, srcaddr, dstaddr)
+ 4.3. m_dump([owner])
5. Statistics
@@ -118,8 +119,9 @@ Juha Heinanen
1.30. Set the ���extra_hdrs_avp��� parameter
1.31. Set the ���skip_notification_flag��� parameter
1.32. m_store usage
- 1.33. m_dump usage
- 1.34. Kamailio config script - sample msilo usage
+ 1.33. m_store_addrs usage
+ 1.34. m_dump usage
+ 1.35. Kamailio config script - sample msilo usage
Chapter 1. Admin Guide
@@ -168,7 +170,8 @@ Chapter 1. Admin Guide
4. Functions
4.1. m_store([owner])
- 4.2. m_dump([owner])
+ 4.2. m_store_addrs(owner, srcaddr, dstaddr)
+ 4.3. m_dump([owner])
5. Statistics
@@ -655,7 +658,8 @@ m_store(...);
4. Functions
4.1. m_store([owner])
- 4.2. m_dump([owner])
+ 4.2. m_store_addrs(owner, srcaddr, dstaddr)
+ 4.3. m_dump([owner])
4.1. m_store([owner])
@@ -679,7 +683,28 @@ m_store();
m_store("$tu");
...
-4.2. m_dump([owner])
+4.2. m_store_addrs(owner, srcaddr, dstaddr)
+
+ Similar to m_store(), but instead of getting source user address from
+ From-URI and destination user address from To_URI, this function allows
+ to give them via parameters.
+
+ Meaning of the parameters is as follows:
+ * owner - is a string that must contain a SIP URI in whose inbox the
+ message will be stored. It can have any pseudo variable.
+ * srcaddr - is a string that must contain a SIP URI corresponding to
+ From user. It can have any pseudo variable.
+ * dstaddr - is a string that must contain a SIP URI correspinding to
+ To user. It can have any pseudo variable.
+
+ This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+
+ Example 1.33. m_store_addrs usage
+...
+m_store_addrs("sip:$rU@a.com", "sip:$fU@a.com", "sip:$tU@a.com");
+...
+
+4.3. m_dump([owner])
The method sends stored messages for the SIP user that has registered
to the contact address in the registration. The method should be called
@@ -693,7 +718,7 @@ m_store("$tu");
This function can be used from REQUEST_ROUTE.
- Example 1.33. m_dump usage
+ Example 1.34. m_dump usage
...
m_dump();
m_dump("$fu");
@@ -735,7 +760,7 @@ m_dump("$fu");
Next picture displays a sample usage of msilo.
- Example 1.34. Kamailio config script - sample msilo usage
+ Example 1.35. Kamailio config script - sample msilo usage
...
#
# MSILO usage example
[View Less]
Module: kamailio
Branch: master
Commit: 8da60f5a0a55fa2d5bb084b8215b96ec4c032161
URL: https://github.com/kamailio/kamailio/commit/8da60f5a0a55fa2d5bb084b8215b96e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-07-10T10:48:46+02:00
msilo: docs for m_store_addrs()
---
Modified: src/modules/msilo/doc/msilo_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/8da60f5a0a55fa2d5bb084b8215b96e……
[View More]Patch: https://github.com/kamailio/kamailio/commit/8da60f5a0a55fa2d5bb084b8215b96e…
---
diff --git a/src/modules/msilo/doc/msilo_admin.xml b/src/modules/msilo/doc/msilo_admin.xml
index abd3e45bbff..189ee5ee9e6 100644
--- a/src/modules/msilo/doc/msilo_admin.xml
+++ b/src/modules/msilo/doc/msilo_admin.xml
@@ -731,6 +731,49 @@ m_store(...);
m_store();
m_store("$tu");
...
+</programlisting>
+ </example>
+ </section>
+ <section id="msilo.f.m_store_addrs">
+ <title><function moreinfo="none">m_store_addrs(owner, srcaddr, dstaddr)</function></title>
+ <para>
+ Similar to m_store(), but instead of getting source user address from
+ From-URI and destination user address from To_URI, this function allows
+ to give them via parameters.
+ </para>
+ <para>Meaning of the parameters is as follows:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>owner</emphasis> - is a string that must contain
+ a SIP URI in whose inbox the message will be stored. It can have
+ any pseudo variable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>srcaddr</emphasis> - is a string that must contain
+ a SIP URI corresponding to From user. It can have
+ any pseudo variable.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>dstaddr</emphasis> - is a string that must contain
+ a SIP URI correspinding to To user. It can have
+ any pseudo variable.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ </para>
+ <example>
+ <title><function>m_store_addrs</function> usage</title>
+ <programlisting format="linespecific">
+...
+m_store_addrs("sip:$rU@a.com", "sip:$fU@a.com", "sip:$tU@a.com");
+...
</programlisting>
</example>
</section>
[View Less]
When used different application servers like:
1) kamailio;
2) freeswitch;
3) crm
Required correlate logs and events between all daemons.
For such purposes can be used tracing (OpenTelementry, Zipkin).
An example for Envoy tracking can look like
POST /api/v2/spans HTTP/1.1
host: zipkin
content-type: application/json
x-envoy-internal: true
x-forwarded-for: 217.12.247.98
x-envoy-expected-rq-timeout-ms: 5000
transfer-encoding: chunked
2ad
[{"tags":{"upstream_cluster":"…
[View More]dynamic_forward_proxy_cluster","component":"proxy","response_flags":"DC","peer.address":"127.0.0.1","http.method":"CONNECT","http.protocol":"HTTP/1.1","downstream_cluster":"-","user_agent":"curl/7.85.0","request_size":"842","guid:x-request-id":"0456e862-4cf7-9ee2-b280-e6f59965a70d","
upstream_cluster.name
":"dynamic_forward_proxy_cluster","http.status_code":"200","response_size":"3750"},"name":"
ifconfig.net:443
","annotations":[{"timestamp":1688924085239932,"value":"ss"}],"kind":"SERVER","localEndpoint":{"port":0,"ipv4":"217.12.247.98"},"timestamp":1688924084352715,"shared":true,"traceId":"67480febdcdd48dc","duration":886997,"id":"67480febdcdd48dc"}]
0
HTTP/1.1 202 Accepted
content-length: 0
server: Armeria/1.17.2
date: Sun, 9 Jul 2023 17:34:47 GMT
where json body looks like
[
{
"tags": {
"upstream_cluster": "dynamic_forward_proxy_cluster",
"component": "proxy",
"response_flags": "DC",
"peer.address": "127.0.0.1",
"http.method": "CONNECT",
"http.protocol": "HTTP/1.1",
"downstream_cluster": "-",
"user_agent": "curl/7.85.0",
"request_size": "842",
"guid:x-request-id": "0456e862-4cf7-9ee2-b280-e6f59965a70d",
"upstream_cluster.name": "dynamic_forward_proxy_cluster",
"http.status_code": "200",
"response_size": "3750"
},
"name": "ifconfig.net:443",
"annotations": [
{
"timestamp": 1688924085239932,
"value": "ss"
}
],
"kind": "SERVER",
"localEndpoint": {
"port": 0,
"ipv4": "217.12.247.98"
},
"timestamp": 1688924084352715,
"shared": true,
"traceId": "67480febdcdd48dc",
"duration": 886997,
"id": "67480febdcdd48dc"
}
]
I looking to create a task for the team developer to develop a module like
"tracing_zipkin". This module should allow trace transactions and dialogs
1. request and response timing;
2. dialog start-stop events;
3. business logic like call hold/unhold, media added//removed (video,
text, message, audio), request multipart content raw or filtered.
I will appreciate it if you share your thoughts about how JSON POST should
look.
Sergey Safarov
[View Less]
### Description
* kamailio 5.6.1 on AlmaLinux 9 and OpenSSL 3.0.5
* Used tlsa to separate the OS version of OpenSSL (which is 3.0.1). The same issue happens
with the OS version of OpenSSL
* Generating TLS client traffic
* The issue will occur at about 25 conn/sec
* Multiple unpredicatable types of shm corruption
### Troubleshooting
* No issue with tlsa + OpenSSL 1.1.1q; the module can sustain 50 conn/sec up to 500 persistent connections.
#### Reproduction
1. Used kamailio configuration from …
[View More]the outbound module documentation; i.e., configure kamailio as a TLS edge proxy.
To isolate the registrar is another kamailio system
1. Use a SIP load tester to generate REGISTER traffic(Expires: 600) ; at the end of the REGISTER, keep the connection alive and reREGISTER at 300 secs.
1. Generate traffic at > 25 conn/sec (with < 25 conn/sec the test usually succeeds)
#### Debugging Data
BT in comments below
#### Log Messages
#### SIP Traffic
### Possible Solutions
### Additional Information
5.6.1
* **Operating System**:
AlmaLinux 9, with (OS) OpenSSL 3.0.1. I used tlsa + OpenSSL 3.0.5
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3222
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3222(a)github.com>
[View Less]
### Description
--
Hello Team,
We are using Kamailio 5.4.7 and we found there is a random crash. We have observed the core logs and we noticed it is due to some of the RPC events. We have noticed it has been crashed from the "ctl handler" process.
--
#### Debugging Data
--
Core dump files are attached.
[core-7519.txt](https://github.com/kamailio/kamailio/files/9099633/core-7519…
[core-17582.txt](https://github.com/kamailio/kamailio/files/9099634/core-175…
[core-7519.txt](https://github.…
[View More]com/kamailio/kamailio/files/9099638/core-7519…
[core-17582.txt](https://github.com/kamailio/kamailio/files/9099639/core-175…
--
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.4.7 (x86_64/linux) a19fe1
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, 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_BLACKLIST, 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: a19fe1
compiled on 02:56:57 Feb 16 2022 with gcc 8.3.0
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3186
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3186(a)github.com>
[View Less]
Module: kamailio
Branch: 5.7
Commit: 44130062640ccbbc7e796cc748d432fe3382c328
URL: https://github.com/kamailio/kamailio/commit/44130062640ccbbc7e796cc748d432f…
Author: Stefan Mititelu <stefan-cristian.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan-cristian.mititelu(a)1and1.ro>
Date: 2023-07-05T13:56:26+03:00
ims_qos: check and log for NULL sessionId
(cherry picked from commit 1b291315b43da1148cee5f3821ddbe49b0c86b7f)
---
Modified: src/modules/ims_qos/rx_aar.c
---
…
[View More]Diff: https://github.com/kamailio/kamailio/commit/44130062640ccbbc7e796cc748d432f…
Patch: https://github.com/kamailio/kamailio/commit/44130062640ccbbc7e796cc748d432f…
---
diff --git a/src/modules/ims_qos/rx_aar.c b/src/modules/ims_qos/rx_aar.c
index 1c376c98008..0f7373915a1 100644
--- a/src/modules/ims_qos/rx_aar.c
+++ b/src/modules/ims_qos/rx_aar.c
@@ -149,6 +149,11 @@ void async_aar_callback(int is_timeout, void *param, AAAMessage *aaa, long elaps
LM_DBG("Success, received code: [%i] from PCRF for AAR request\n", cdp_result);
counter_inc(ims_qos_cnts_h.successful_media_aars);
+ if(!aaa->sessionId) {
+ LM_ERR("NULL AAA sessionId from PCRF!\n");
+ goto error;
+ }
+
LM_DBG("Auth session ID [%.*s]", aaa->sessionId->data.len, aaa->sessionId->data.s);
if(!data->aar_update) {
@@ -286,6 +291,12 @@ void async_aar_reg_callback(int is_timeout, void *param, AAAMessage *aaa, long e
create_return_code(result);
goto done;
}
+
+ if(!aaa->sessionId) {
+ LM_ERR("NULL AAA sessionId from PCRF!\n");
+ goto error;
+ }
+
//need to set Rx auth data to say this session has been successfully opened
//This is used elsewhere to prevent acting on termination events when the session has not been opened
//getting auth session
[View Less]
Module: kamailio
Branch: 5.6
Commit: 5154f20964e08d2853bbf96afdeecceac8fe7650
URL: https://github.com/kamailio/kamailio/commit/5154f20964e08d2853bbf96afdeecce…
Author: Stefan Mititelu <stefan-cristian.mititelu(a)1and1.ro>
Committer: Stefan Mititelu <stefan-cristian.mititelu(a)1and1.ro>
Date: 2023-07-05T13:54:29+03:00
ims_qos: check and log for NULL sessionId
(cherry picked from commit 1b291315b43da1148cee5f3821ddbe49b0c86b7f)
---
Modified: src/modules/ims_qos/rx_aar.c
---
…
[View More]Diff: https://github.com/kamailio/kamailio/commit/5154f20964e08d2853bbf96afdeecce…
Patch: https://github.com/kamailio/kamailio/commit/5154f20964e08d2853bbf96afdeecce…
---
diff --git a/src/modules/ims_qos/rx_aar.c b/src/modules/ims_qos/rx_aar.c
index dbc2aebaeb6..287df6d9894 100644
--- a/src/modules/ims_qos/rx_aar.c
+++ b/src/modules/ims_qos/rx_aar.c
@@ -149,6 +149,11 @@ void async_aar_callback(int is_timeout, void *param, AAAMessage *aaa, long elaps
LM_DBG("Success, received code: [%i] from PCRF for AAR request\n", cdp_result);
counter_inc(ims_qos_cnts_h.successful_media_aars);
+ if(!aaa->sessionId) {
+ LM_ERR("NULL AAA sessionId from PCRF!\n");
+ goto error;
+ }
+
LM_DBG("Auth session ID [%.*s]", aaa->sessionId->data.len, aaa->sessionId->data.s);
if(!data->aar_update) {
@@ -286,6 +291,12 @@ void async_aar_reg_callback(int is_timeout, void *param, AAAMessage *aaa, long e
create_return_code(result);
goto done;
}
+
+ if(!aaa->sessionId) {
+ LM_ERR("NULL AAA sessionId from PCRF!\n");
+ goto error;
+ }
+
//need to set Rx auth data to say this session has been successfully opened
//This is used elsewhere to prevent acting on termination events when the session has not been opened
//getting auth session
[View Less]
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, …
[View More]tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils, ...)
- [X] Each component has a single commit (if not, squash them into one commit)
- [X] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [X] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Check for NULL sessionId from PCRF, which can lead to kamailio crash.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3503
-- Commit Summary --
* ims_qos: check and log for NULL sessionId
-- File Changes --
M src/modules/ims_qos/rx_aar.c (11)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3503.patchhttps://github.com/kamailio/kamailio/pull/3503.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3503
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3503(a)github.com>
[View Less]
Module: kamailio
Branch: master
Commit: 2dbaa727a38e29da0f887fa5d0d8d20392839f9b
URL: https://github.com/kamailio/kamailio/commit/2dbaa727a38e29da0f887fa5d0d8d20…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2023-07-05T07:04:46Z
tm: remove obselete comment, add clarification for reply_wait mode 2
---
Modified: src/modules/tm/rpc_uac.c
---
Diff: https://github.com/kamailio/kamailio/commit/2dbaa727a38e29da0f887fa5d0d8d20……
[View More]Patch: https://github.com/kamailio/kamailio/commit/2dbaa727a38e29da0f887fa5d0d8d20…
---
diff --git a/src/modules/tm/rpc_uac.c b/src/modules/tm/rpc_uac.c
index ce22b6121c1..d461d123a13 100644
--- a/src/modules/tm/rpc_uac.c
+++ b/src/modules/tm/rpc_uac.c
@@ -626,12 +626,12 @@ static void rpc_uac_block_callback(
* only if reply_wait is set to 1. Otherwise the rpc reply will be sent
* immediately and it will be success if the parameters were ok and t_uac did
* not report any error.
- * Note: reply waiting (reply_wait==1) is not yet supported.
* @param rpc - rpc handle
* @param c - rpc current context
* @param reply_wait - if 1 do not generate a rpc reply until final response
* for the transaction arrives, if 0 immediately send
- * an rpc reply (see above).
+ * an rpc reply (see above). If 2 blocking wait until
+ * final response for the transaction arrives.
*/
static void rpc_t_uac(rpc_t *rpc, void *c, int reply_wait)
{
[View Less]
### Description
The dbmode behavior was modified (see the commit reference bellow) and does not clearly align with the documentation anymore, I still need the feature when we can persist htable records that were inserted at runtime.
In fact I do not understand that value of writing back only records that where loaded from the DB, this seems equivalent to dbmode 0 (if the db is not altered) ?
Maybe you can help me understand why we the change is needed @miconda ?
```
dbmode - if set to 1, …
[View More]the content of hash table is written to database table when the SIP server is stopped (i.e., ensure persistency over restarts). Default value is 0 (no write back to db table).
```
```
commit b1fa63b1547fc5af6cc1e97db42ea76db1bf927b
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Wed Apr 13 13:11:30 2022 +0200
htable: track when records were successfully loaded from database
- write back only in such case
diff --git a/src/modules/htable/ht_api.c b/src/modules/htable/ht_api.c
index 00023e7153..f212600e21 100644
--- a/src/modules/htable/ht_api.c
+++ b/src/modules/htable/ht_api.c
@@ -1099,7 +1099,7 @@ int ht_db_sync_tables(void)
ht = _ht_root;
while(ht)
{
- if(ht->dbtable.len>0 && ht->dbmode!=0 && ht->ncols==0)
+ if(ht->dbtable.len>0 && ht->dbmode!=0 && ht->dbload!=0 && ht->ncols==0)
{
LM_DBG("sync db table [%.*s] from ht [%.*s]\n",
ht->dbtable.len, ht->dbtable.s,
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3422
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3422(a)github.com>
[View Less]