### Description
I'm trying to check if the incoming message is from the dispatcher hosts using
KEMI function ds_is_from_list from a lua script:
```
if KSR.dispatcher.ds_is_from_list("-1", "2") then
KSR.info("Dispatcher List \n");
return "list"
end
```
I'm getting always true if when the sour
### Description
Unable to upgrade Kamailio 5.7 on CentOS7
Error:
```
tls_mod.c: In function ‘fork_child’:
tls_mod.c:348:2: error: ‘for’ loop initial declarations are only allowed in C99
mode
for(int k = 0; k < 16; k++) {
^
tls_mod.c:348:2: note: use option -std=c99 or -std=gnu99 to compile y
Sorry, I haven't had a chance to test with the latest Kamailio version yet. I
just gave up and moved to the evapi module where I can use NATS connection
without any issues.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3253#issuecomment-162706
Hi @henningw ,
Not, I don't see any warnings or errors in the log file.
Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3321#issuecomment-1370928905
You are receiving this because you are subscribed to this thread.
Message ID: ___
### Description
I have the following URI:
```INVITE sip:123456789;phone-context=+1@192.168.1.1;transport=udp;user=phone
SIP/2.0```
I want to remove the phone-context parameter from the URI, so I've tried to use
the function:
```uri_param_rm``` from the siputils package:
```
if (uri_param_rm("
unfortunately that didn't help either, the same error:
```
Nov 28 18:26:35 k1-dev k1-dev[27366]: INFO: nats [nats_mod.c:439]:
nats_init_connection(): adding server [nats://127.0.0.1:4222] [1]
Nov 28 18:26:35 k1-dev k1-dev[27366]: ERROR: nats [nats_mod.c:458]:
nats_init_connection(): could not cr
I installed a nats server on the same box where kamailio is running, and got
the same error:
```
Nov 28 18:02:25 k1-dev k1-dev[25790]: INFO: nats [nats_mod.c:439]:
nats_init_connection(): adding server [nats://127.0.0.1:4222] [1]
Nov 28 18:02:25 k1-dev k1-dev[25790]: ERROR: nats [nats_mod.c:458]
Hi @eschmidbauer ,
Yes, at least using telnet I'm able to connect from Kamailio server.
```
[root@dev src]# telnet 192.168.1.1 4222
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
INFO
{"server_id":"NAK6SMFE53GJYNICKK6QFTXDAIWEL753AC4ZN4CMRFC5XSWXBIA6GUJA","server_name"
Hi @miconda ,
Now it's compiling successfully and kamailio doesn't seem to crash anymore but
it's not starting either.
Those are the errors from the log file:
```
Nov 28 16:20:26 k1-dev k1-dev[24701]: INFO: nats [nats_mod.c:439]:
nats_init_connection(): adding server [nats://192.168.1.1:4222] [
Hi @miconda ,
I can't compile the module anymore, getting the error:
```
make
nats_mod.c: In function ‘nats_cleanup_connection’:
nats_mod.c:540:2: error: ‘for’ loop initial declarations are only allowed in
C99 mode
for(int s = 0; s < NATS_MAX_SERVERS; s++) {
^
nats_mod.c:540:2: note: use opt
Hi @miconda , sorry missed your last comment - I'm going to test it and let you
know the status.
Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3253#issuecomment-1326171094
You are receiving this because you are subscribed to this thread
Below you can find the core dump from the last commit in the master branch:
```
(gdb) bt
#0 0x7f4ac66041cc in uv.io_stop () from /lib64/libuv.so.1
#1 0x7f4ac660a71a in uv.poll_stop.lto_priv () from /lib64/libuv.so.1
#2 0x7f4ac660a763 in uv_poll_stop () from /lib64/libuv.so.1
#3 0x0
Hi @linuxmaniac,
```
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
(gdb) bt
#0 __pthread_kill
Hi @linuxmaniac, @eschmidbauer - unfortunately the patch didn't work either,
kamailio still crashing with the same 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 n
@linuxmaniac, I'm trying to apply the patch you provided but it's not working
for me. Maybe it's for a different branch? I tried with 5.6, master and none of
them worked.
```
patching file src/modules/nats/nats_mod.c
Hunk #1 FAILED at 588.
1 out of 1 hunk FAILED -- saving rejects to file src/mod
Hi @eschmidbauer,
thanks for looking into this, but unfortunately still not working for me, this
is the format I've tried:
```
modparam("nats", "nats_url", "nats://192.168.1.1:4222")
modparam("nats", "subject_queue_group", "sql.test_sub.com:testqueue")
```
--
Reply to this email directly or vi
@eschmidbauer, not sure about that, just tried now to subscribe to a queue and
it's still the same
```
modparam("nats", "subject_queue_group", "test")
```
Log Error:
```
ERROR: nats [nats_mod.c:456]: nats_init_connection(): could not create nats
options [System Error]
ERROR: nats [nats_mod.c:26
There you go:
```
(gdb) f 3
#3 0x7fb35c146d3d in nats_destroy_workers () at nats_mod.c:591
591 uv_poll_stop(&pub_worker->poll);
(gdb) p *pub_worker
$1 = {pid = 0, fd = 0, uvLoop = 0x0, pipe = {data = 0x0, loop = 0x0, type =
UV_UNKNOWN_HANDLE, close_cb = 0x0, handle
Hi @henningw ,
Please find the core dump below:
```
(gdb) bt
#0 0x7fb35c0961cc in uv.io_stop () from /lib64/libuv.so.1
#1 0x7fb35c09c71a in uv.poll_stop.lto_priv () from /lib64/libuv.so.1
#2 0x7fb35c09c763 in uv_poll_stop () from /lib64/libuv.so.1
#3 0x7fb35c146d3d in nats_des
### 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
7fe97b06f1cc sp 7fff72d158f0 error 4 in
libuv.so.1.0.0[7fe97b066000+1f000]
Sep 27 23:08:27 server kernel: Code: 5a 85 ff ff b8 ea
No issues so far, everything works as expected. Thanks, Daniel for looking into
that.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3236#issuecomment-1251023656
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #3236 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3236#event-7413684503
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Develo
### Description
### Troubleshooting
By executing an external script using exec_cmd function I'm getting the
following error:
``failed. exit_status=13, errno=11: Resource temporarily unavailable``
This is happening intermittently, sometimes it's working fine, but sometimes I
see this error in th
Hi Daniel,
Could you please have a look at the following commit:
0bde3ca506467008cf3d8345afa731617b095c8c?
I compiled Kamailio with the latest 5.4 branch
(d43872c11edacf972c2ae72c746517dcf56e2777), excepting this commit - and it
didn't crash for about 5 days already.
--
You are receiving thi
(gdb) frame 0
```
#0 0x7fe8703c342d in update_dialog_vars_dbinfo (cell=0x7fe8765627b8,
var=0x7574617473706973) at dlg_db_handler.c:755
755 SET_STR_VALUE(values+2, var->key);
```
(gdb) p *var
```
Cannot access memory at address 0x7574617473706973
```
(gdb) p full_version
```
$1 =
I have 2 different versions of Kamailio running on 2 different boxes, on one of
them I have version:
```
version: kamailio 5.4.1 (x86_64/linux) a6cb74
```
which works fine, but on another one I have version:
```
version: kamailio 5.4.1 (x86_64/linux) a505f5
```
which is crashing.
Then looks that
Hi,
Unfortunately, this issue is still persisting, Kamailio crashed again twice
with the same symptoms.
/usr/local/sbin/kamailio -V
```
version: kamailio 5.4.1 (x86_64/linux) f57c90
```
(gdb) frame 0
```
#0 0x7fe8703c342d in update_dialog_vars_dbinfo (cell=0x7fe8765627b8,
var=0x757461747370
Reopened #2494.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2494#event-3875739443___
Kamailio (SER) - Development Mailing List
sr-dev
For high intensive servers that might add an overload over the database.
Details here:
https://lists.kamailio.org/pipermail/sr-users/2020-October/110764.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com
Closed #2501.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2501#event-3865414177___
Kamailio (SER) - Development Mailing List
sr-dev@l
Closed #2494.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2494#event-3865397145___
Kamailio (SER) - Development Mailing List
sr-dev@l
Looks that indeed, the commit above was giving that issue, now it seems to be
working better.
Thank you.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2494#issuecomment-706962742
(gdb) frame 0
```
#0 0x7f21b5cdb42d in update_dialog_vars_dbinfo (cell=0x7f21ba5f6348,
var=0x7574617473706973) at dlg_db_handler.c:755
755 SET_STR_VALUE(values+2, var->key);
```
(gdb) set var $it = cell->vars
empty
(gdb) while $it
>p *$it
>set var $it = $it->next
> en
OK, I will recompile it again and will try to test. BTW, the version which is
working ok at the moment with the same configuration and DB - it's this one:
```
version: kamailio 5.4.1 (x86_64/linux) a6cb74
```
--
You are receiving this because you are subscribed to this thread.
Reply to this ema
Not, it's not the same core file as in the first comment, see my comment from
yesterday:
https://github.com/kamailio/kamailio/issues/2494#issuecomment-705498441
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github
Closed #2502.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2502#event-3859818072___
Kamailio (SER) - Development Mailing List
sr-dev@l
Just checked now, works fine with the master branch.
Thank you Daniel.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2502#issuecomment-706140047___
### Description
Monitoring extensions by using KA function from the usrloc module it's not
working for ws contacts
Log Messages
```
Oct 8 16:51:20 devsrv devsrv[31562]: ERROR: usrloc [ul_keepalive.c:277]:
ul_ka_send(): unknown proto [5] for sending keepalive
Oct 8 16:51:50 devsrv devsrv
Sorry, there was a problem with the previous core dump file, it was deleted by
mistake, I just got another one - which I will try to keep for the further
investigations:
See below:
(gdb) frame 0
```
#0 0x7f21b5cdb42d in update_dialog_vars_dbinfo (cell=0x7f21ba5f6348,
var=0x75746174737069
### Description
Would be very handy to have all information from the KA function (KA-Roundtrip
and Last-Keepalive values) in the DB location table as well in two separate
columns.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on Gi
frame 0
> (gdb) frame 0
#0 0x7faef83f542d in update_dialog_vars_dbinfo (cell=0x7faf01fc7418,
var=0x7574617473706973) at dlg_db_handler.c:755
755 SET_STR_VALUE(values+2, var->key);
p *cell
> (gdb) p*cell
$1 = {ref = 2, next = 0x0, prev = 0x0, h_id = 6180, h_entry = 49, state = 5,
Here is the pastebin content of the bt full command:
https://pastebin.com/raw/45jWtRum
(In case that will help)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2494#issuecomment-702
#2057 # Description
After upgrading Kamailio to v5.4 in the last 10 days it crashed twice.
Debugging Data
bt full
> #0 0x7f1d9080142d in update_dialog_vars_dbinfo (cell=0x7f1d96a443c8,
> var=0x36) at dlg_db_handler.c:755
values = {{type = DB1_INT, nul = 0, free = 6450108, val
### Description
Trying to duplicate TLS SIP messages to the remote host directly from Kamailio
by using Siptrace Module. Those are the parameters used by the module:
```
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "force_send_sock", "sip:192.168.1.1:5000")
modparam("siptrace", "trac
Hello,
Kamailio is crashing when I'm trying to set the parameter;
`modparam("tm|usrloc", "xavp_contact", "ulattrs")
`
The crash is happening when I'm register 2 devices with the same extension.
This is the core dump:
Reproduction
Set the following parameter:
`modparam("tm|usrloc", "xavp
### Description
"ds_is_from_list" function from Dispatcher module give false result - when
actually it should be true.
### Troubleshooting
Reproduction
modparam("dispatcher", "db_url",DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "setid_col", "setid")
46 matches
Mail list logo
