[SR-Users] Re: Not responding to OPTIONS if existing tcp connection

[Daniel-Constantin Mierla via sr-users]

Hello,

if there are no errors reported by Kamailio, maybe the outgoing queue
for the socket is full and the kernel discards messages, check with netstat.

Another option could be that the sngrep fails to capture it, maybe the
src/dst ports are random and I do not now what are the rules sngrep use
for catching sip traffic.

Cheers,
Daniel

On 18.07.24 15:02, Jon Bonilla (Manwe) via sr-users wrote:
> Hi all
>
> version 5.7.6 Debian 12
>
> I'm having issues with a kamailio server not sending 200 to some OPTIONS
> requests.
> It does send 200 to some subscribers but not 100% of the time to 100% of subs.
> I have enabled debug=3 in that server and this is what I found:
>
> If the log says that it found existing tcp connection and it's reusing it I
> can't see the 200ok in a sngrep capture. Example:
>
>   [core/receive.c:126]: sip_check_fline(): first line indicates a SIP
>  reply
>
>  [core/tcp_main.c:1722]: _tcpconn_find(): found connection by id: 2
>  
>   [core/tcp_main.c:2614]: tcpconn_send_put(): send from reader (360359
> (18)), reusing fd
>
>   [core/tcp_main.c:2845]: tcpconn_do_send(): sending...
>  
>   [core/tcp_main.c:2881]: tcpconn_do_send(): after real write: c=
>  0x7fb0faa893d8 n=384 fd=14 
>   [core/tcp_main.c:2882]: tcpconn_do_send(): buf=#012SIP/2.0 200
>  Keepalive#015#012Via: SIP/2.0/TCP
>  
> 10.35.190.105:5060;branch=z9hG4bK15ebf764;rport=55894;received=1.1.1.186#015#012From:
>  "Unknown" ;tag=as5311c3a7#015#012To:   1.1.1.138>;tag=054524a74bcccf444a0f08f67c5b7657.d07b5401#015#012Call-ID:
>  15dcd38c46f915576ded132a11d8ff4c@10.35.190.105:5060#015#012CSeq: 102
>  OPTIONS#015#012Server: aaa SBC#015#012Content-Length: 0#015#012#015#012
>
>   [core/receive.c:531]: receive_msg(): request-route executed in: 302 
> usec
>
>
> On the other side, if kamailio doesn't find an existing tcp connection (at
> least nothing in the logs about that) I can see the 200 ok in sngrep. Example:
>
>  [core/receive.c:126]: sip_check_fline(): first line indicates a SIP 
> reply
>
>  [core/receive.c:531]: receive_msg(): request-route executed in: 295 
> usec
>
>
> All subs use tcp. And the kamailio.cfg is very simple regarding OPTIONS:
> Sanity, check maxfwd and sl_send_reply(200). 
>
> Any hints?
>
>
>
> cheers,
>
> Jon
>
>
>
>
> -- 
> PekePBX, the multitenant PBX solution
> https://pekepbx.com
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: SHM Memory leak?

[Daniel-Constantin Mierla via sr-users]

What is the memory manager that you use, is the default one or do you
provide -x cli parameter?

Cheers,
Daniel

On 18.07.24 17:09, Ihor Olkhovskyi wrote:
> Daniel,
>
> thanks, so shm_status is returning A LOT of data, not sure how to
> analyze it, regarding shm_summary, I'm getting the same, so will just
> citate part of my previous message:
>
> corex.shm_summary returns the following:
>
> https://pastebin.com/tFYwygjU
>
> I see a lot of memory allocated to
>
> core/tcp_main.c: tcpconn_new(1201) (around 100 MB count= 1225),
> tls: tls_init.c: ser_malloc(364) (66 MB, count = 69815)
>
> But still kamctl stats shmem showing 2GB of used memory.
>
>
> Le jeu. 18 juil. 2024 à 09:53, Daniel-Constantin Mierla
>  a écrit :
>
> Hello,
>
> set memlog value lower or equal with the one for debug, and memdbg
> to a higher value than debug.
>
> Cheers,
> Daniel
>
> On 12.07.24 21:23, Ihor Olkhovskyi wrote:
>>
>> Daniel,
>>
>> Thanks for an answer,
>>
>> Just a question, what should be options for
>>
>> debug=2
>> log_stderror=no
>>
>> memdbg=5
>> memlog=5
>>
>> mem_join=1
>> mem_safety=1
>>
>> to get the most of
>>
>> kamctl rpc corex.shm_summary ?
>>
>> Cause when I'm setting
>>
>> kamcmd corex.debug 5 
>>
>> I'm getting all of the list of fragments which is really
>> something not easy to read.
>>
>> corex.shm_summary returns the following:
>>
>> https://pastebin.com/tFYwygjU
>>
>> I see a lot of memory allocated to
>>
>> core/tcp_main.c: tcpconn_new(1201) (around 100 MB count= 1225),
>> tls: tls_init.c: ser_malloc(364) (66 MB, count = 69815)
>>
>> But still kamctl stats shmem showing 2GB of used memory.
>>
>> Thanks in advance!
>>
>> Le 10/07/2024 à 14:11, Daniel-Constantin Mierla a écrit :
>>>
>>> Hello,
>>>
>>> first, the value for -M is too high, I cannot easily think of a
>>> case when one needs 1GB of private memory for each kamailio process.
>>>
>>> You can try to run the rpc command shm.stats and look in the
>>> syslog for the report to check if it is different that what you
>>> get with mod.mem_stats.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 10.07.24 11:36, Ihor Olkhovskyi via sr-users wrote:
 Hello!

 I'm trying to get where all the SHM memory gone. For the moment
 I'm using these settings:
 -m 8192 -M 1024
 which means 8G of SHM meory.
 Kamailio parameters are the following

 fork=yes
 children=8
 tcp_children=12
 enable_tls=yes
 enable_sctp=no
 tls_threads_mode=2
 tcp_accept_no_cl=yes
 tcp_max_connections=63536
 tls_max_connections=63536
 tcp_accept_aliases=no
 tcp_async=yes
 tcp_connect_timeout=10
 tcp_conn_wq_max=63536
 tcp_crlf_ping=yes
 tcp_delayed_ack=yes
 tcp_fd_cache=yes
 tcp_keepalive=yes
 tcp_keepcnt=3
 tcp_keepidle=30
 tcp_keepintvl=10
 tcp_linger2=30
 tcp_rd_buf_size=8
 tcp_send_timeout=10
 tcp_wq_blk_size=2100
 tcp_wq_max=10485760
 open_files_limit=63536

 And having ~1000 TLS/WSS clients I'm getting this after 3 days
 of running:
 {
   "jsonrpc":  "2.0",
   "result": [
     "shmem:fragments = 2796",
     "shmem:free_size = 3737947072", (3.7 G)
     "shmem:max_used_size = 4857418512", (4.8 G)
     "shmem:real_used_size = 4851987520",
     "shmem:total_size = 8589934592",
     "shmem:used_size = 4838988096"  (4.8 G)
   ],
   "id": 984479
 }
 Means half of SHM memory is gone

 When running kamcmd mod.stats all shm I'm getting (output
 truncated for the largest values)

 Module: core
 {
   ...
         tcpconn_new(1201): 130669280 (0.13 G)
       ...
         Total: 131657632 (0.13 G)
 }

 Module: sl
 {
  ...
         Total: 7520
 }

 Module: siptrace
 {
  ...
         Total: 13520
 }

 Module: rr
 {
         Total: 0
 }

 Module: dialog
 {
 ...
         Total: 146080
 }

 Module: permissions
 {
 ...
         Total: 62144
 }

 Module: htable
 {
   
         Total: 3359552 (3.3 M)
 }

 Module: rtpengine
 {
  ...
         Total: 31456
 }

 Module: textopsx
 {
         Total: 0
 }

 Module: tsilo
 {
  ...
         Total: 75072
 }

 Module: tm
 {
  
         Total: 

[SR-Users] Re: Possible Kamailio memmory leak - version 5.8.2

[Daniel-Constantin Mierla via sr-users]

Hello,


indeed the previous commit was destroying a single avp, I pushed a new
one to destroy all of them with that name. I am wondering if all avps,
no matter the name should be destroyed.


Anyhow, could you fetch the latest git master version and try your
scenario again?


Cheers,
Daniel


On 16.07.24 16:11, Vanderlei Torres Batistela wrote:
> Hello Daniel,
>
> I tried with git master branch and it works only for a simple
> event-route script where avp(msg) is not modified as below:
>
>
> # event route
> event_route[network:msg] {
>
>     xlog("L_INFO", " Event_Route \n");
>     if (is_incoming()) {
>         xlog("L_INFO", "Received message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>     } else {
>         xlog("L_INFO", "Sending message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>      }
> }
>
>
> Then I tried it using this script as an example to set the message to
> send out:
>
> # event route
> event_route[network:msg] {
>
>     xlog("L_INFO", " Event_Route \n");
>     if (is_incoming()) {
>         xlog("L_INFO", "Received message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>     } else {
>         xlog("L_INFO", "Sending message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("var(x)= $var(x)");
>         $var(x)="a=3gOoBTC" + "\r" + "\n";
>         $avp(msg) = $(avp(msg){s.replace,$var(x),});
>         avp_print();
>      }
> }
>
> Examining the attached log I saw that for each INVITE retransmission
> (handled by another processor-pid) the avp (msg) is not freed and is
> accumulated.
> So I modified the script to delete the avp(msg) before using it and
> that fixed the issue.
>
> 2) Delete avp(msg) before using it
>
> # event route
> event_route[network:msg] {
>
>     xlog("L_INFO", " Event_Route \n");
>     if (is_incoming()) {
>         xlog("L_INFO", "Received message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>     } else {
>         xlog("L_INFO", "Sending message '$mb' \n");
>         $(avp(msg)[*]) = $null;    
> <--
>         $avp(msg) = $mb;
>         xinfo("var(x)= $var(x)");
>         $var(x)="a=3gOoBTC" + "\r" + "\n";
>         $avp(msg) = $(avp(msg){s.replace,$var(x),});
>         avp_print();
>      }
> }
>
>
> This workaround also fixed the issue in the original 5.8.2 version.
>
> Regards,
>
> Vanderlei
>
>
>
>
> 
> *De:* Daniel-Constantin Mierla 
> *Enviado:* quarta-feira, 10 de julho de 2024 07:05
> *Para:* Kamailio (SER) - Users Mailing List 
> *Cc:* Vanderlei Torres Batistela 
> *Assunto:* Re: [SR-Users] Possible Kamailio memmory leak - version 5.8.2
>  
> Hello,
>
> I couldn't spot any error message in the log file that you attached,
> have you taken it when you encountered the problem?
>
> Anyhow, I am not familiar with the implementation of the
> event_route[network:msg], but the shm info indicates the leak to be
> related to avp, so I pushed a patch to destroy the nio_msg_avp avp
> after event route execution. Can you try with git master branch and
> see if works ok?
>
> Cheers,
> Daniel
>
> On 02.07.24 16:24, Vanderlei Torres Batistela via sr-users wrote:
>
> Hello all,
>
> I am using a very simple scritp with corex module enabled .
>  Normal calls works fine, but a scenario where INVITE does not
> receive response and the call is released with SIP 408 (request
> timeout) leads to memmory leak.  I verified it making a lot of 
> calls with this scenario and printing the  shared memory (using
> kamcmd core.shmmem) .  Its ocurred with modparam("corex",
> "nio_intercept", 1).
>  If  I modify to modparam("corex", "nio_intercept", 0) the memmory
> leak does not ocurr anymore.
> The problem also occurs in another scenario where the SIP Cancel
> message is not responded to.
>
> My script has this event route
>  
> # event route
> event_route[network:msg] {
>
>     xlog("L_INFO", "Dentro do Event_Route \n");
>     if (is_incoming()) {
>         xlog("L_INFO", "Received message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>     } else {
>         xlog("L_INFO", "Sending message '$mb' \n");
>          $avp(msg) = $mb;
>     };
> }
>
> Test done wtih 4000 calls:
>
> [root@labcom070 kamailio]# kamctl stats shmem
> {
>   "jsonrpc":  "2.0",
>   "result": [
>     "shmem:fragments = 900",
>     "shmem:free_size = 6180368",
>     "shmem:max_used_size = 66980272",
>     "shmem:real_used_size = 60928496",
>     "shmem:total_size = 67108864",
>     "shmem:used_size = 54884944"
>   ],
>   "id": 393115
> }
>
>
> [root@labcom070 kamailio]# kamcmd mod.stats all shm
> Module: core
> {
>         create_avp(178): 52257504
>  

[SR-Users] Re: SHM Memory leak?

[Daniel-Constantin Mierla via sr-users]

Hello,

set memlog value lower or equal with the one for debug, and memdbg to a
higher value than debug.

Cheers,
Daniel

On 12.07.24 21:23, Ihor Olkhovskyi wrote:
>
> Daniel,
>
> Thanks for an answer,
>
> Just a question, what should be options for
>
> debug=2
> log_stderror=no
>
> memdbg=5
> memlog=5
>
> mem_join=1
> mem_safety=1
>
> to get the most of
>
> kamctl rpc corex.shm_summary ?
>
> Cause when I'm setting
>
> kamcmd corex.debug 5 
>
> I'm getting all of the list of fragments which is really something not
> easy to read.
>
> corex.shm_summary returns the following:
>
> https://pastebin.com/tFYwygjU
>
> I see a lot of memory allocated to
>
> core/tcp_main.c: tcpconn_new(1201) (around 100 MB count= 1225),
> tls: tls_init.c: ser_malloc(364) (66 MB, count = 69815)
>
> But still kamctl stats shmem showing 2GB of used memory.
>
> Thanks in advance!
>
> Le 10/07/2024 à 14:11, Daniel-Constantin Mierla a écrit :
>>
>> Hello,
>>
>> first, the value for -M is too high, I cannot easily think of a case
>> when one needs 1GB of private memory for each kamailio process.
>>
>> You can try to run the rpc command shm.stats and look in the syslog
>> for the report to check if it is different that what you get with
>> mod.mem_stats.
>>
>> Cheers,
>> Daniel
>>
>> On 10.07.24 11:36, Ihor Olkhovskyi via sr-users wrote:
>>> Hello!
>>>
>>> I'm trying to get where all the SHM memory gone. For the moment I'm
>>> using these settings:
>>> -m 8192 -M 1024
>>> which means 8G of SHM meory.
>>> Kamailio parameters are the following
>>>
>>> fork=yes
>>> children=8
>>> tcp_children=12
>>> enable_tls=yes
>>> enable_sctp=no
>>> tls_threads_mode=2
>>> tcp_accept_no_cl=yes
>>> tcp_max_connections=63536
>>> tls_max_connections=63536
>>> tcp_accept_aliases=no
>>> tcp_async=yes
>>> tcp_connect_timeout=10
>>> tcp_conn_wq_max=63536
>>> tcp_crlf_ping=yes
>>> tcp_delayed_ack=yes
>>> tcp_fd_cache=yes
>>> tcp_keepalive=yes
>>> tcp_keepcnt=3
>>> tcp_keepidle=30
>>> tcp_keepintvl=10
>>> tcp_linger2=30
>>> tcp_rd_buf_size=8
>>> tcp_send_timeout=10
>>> tcp_wq_blk_size=2100
>>> tcp_wq_max=10485760
>>> open_files_limit=63536
>>>
>>> And having ~1000 TLS/WSS clients I'm getting this after 3 days of
>>> running:
>>> {
>>>   "jsonrpc":  "2.0",
>>>   "result": [
>>>     "shmem:fragments = 2796",
>>>     "shmem:free_size = 3737947072", (3.7 G)
>>>     "shmem:max_used_size = 4857418512", (4.8 G)
>>>     "shmem:real_used_size = 4851987520",
>>>     "shmem:total_size = 8589934592",
>>>     "shmem:used_size = 4838988096"  (4.8 G)
>>>   ],
>>>   "id": 984479
>>> }
>>> Means half of SHM memory is gone
>>>
>>> When running kamcmd mod.stats all shm I'm getting (output truncated
>>> for the largest values)
>>>
>>> Module: core
>>> {
>>>   ...
>>>         tcpconn_new(1201): 130669280 (0.13 G)
>>>       ...
>>>         Total: 131657632 (0.13 G)
>>> }
>>>
>>> Module: sl
>>> {
>>>  ...
>>>         Total: 7520
>>> }
>>>
>>> Module: siptrace
>>> {
>>>  ...
>>>         Total: 13520
>>> }
>>>
>>> Module: rr
>>> {
>>>         Total: 0
>>> }
>>>
>>> Module: dialog
>>> {
>>> ...
>>>         Total: 146080
>>> }
>>>
>>> Module: permissions
>>> {
>>> ...
>>>         Total: 62144
>>> }
>>>
>>> Module: htable
>>> {
>>>   
>>>         Total: 3359552 (3.3 M)
>>> }
>>>
>>> Module: rtpengine
>>> {
>>>  ...
>>>         Total: 31456
>>> }
>>>
>>> Module: textopsx
>>> {
>>>         Total: 0
>>> }
>>>
>>> Module: tsilo
>>> {
>>>  ...
>>>         Total: 75072
>>> }
>>>
>>> Module: tm
>>> {
>>>  
>>>         Total: 3459504 (3.4 M)
>>> }
>>>
>>> Module: usrloc
>>> {
>>>  
>>>         Total: 1217616
>>> }
>>>
>>> Module: pua_dialoginfo
>>> {
>>>  ...
>>>         Total: 8720
>>> }
>>>
>>> Module: pua
>>> {
>>>  ...
>>>         Total: 150848
>>> }
>>>
>>> Module: pike
>>> {
>>>  ...
>>>         Total: 9504
>>> }
>>>
>>> Module: websocket
>>> {
>>>         wsconn_add(198): 54139856 (54 M)
>>>  ...
>>>         Total: 54148096 (54 M)
>>> }
>>>
>>> Module: debugger
>>> {
>>>  ...
>>>         Total: 21872
>>> }
>>>
>>> Module: tmx
>>> {
>>>         Total: 512
>>> }
>>>
>>> Module: kex
>>> {
>>>        
>>>         Total: 1888
>>> }
>>>
>>> Module: tls
>>> {
>>> ...
>>>         ser_malloc(364): 87246112 (87 M)
>>>  ...
>>>         Total: 87997168 (87 M)
>>> }
>>>
>>> Module: secfilter
>>> {
>>> ...
>>>         Total: 768
>>> }
>>>
>>> Module: exec
>>> {
>>>  ...
>>>         Total: 16
>>> }
>>>
>>> Module: dispatcher
>>> {
>>>  ...
>>>         Total: 2992
>>> }
>>>
>>> Module: cfgutils
>>> {
>>>  ...
>>>         Total: 48
>>> }
>>>
>>> Module: app_python3
>>> {
>>>  ...
>>>         Total: 32
>>> }
>>>
>>> So, I'm guessing, where all the memory gone? Is there any way to get
>>> more detailed info on SHM?
>>>
>>> Kamailio 5.8.2
>>>
>>> -- 
>>> Thanks in advance,
>>> Ihor
>>>
>>> __
>>> Kamailio - Users Mailing List - Non Commercial Discussions
>>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>>> 

[SR-Users] Re: Changing ksr_tcp_accept_iplimit from default 1024

[Daniel-Constantin Mierla via sr-users]

Hello,

see:

  -
https://www.kamailio.org/wikidocs/cookbooks/5.8.x/core/#tcp_accept_iplimit

Cheers,
Daniel

On 16.07.24 16:52, Who AmI via sr-users wrote:
> Hi list,
>
> I hope you are all well?
>
> I am currently loadtesting some services internally and I am getting
> an odd error around TCP connections from the same source IP below:
>
> "/usr/sbin/kamailio[1806789]: CRITICAL:  [core/tcp_main.c:4459]:
> handle_new_connect(): hit the limit of connections per source IP
> (my_ip:39043) - rejecting"
>
> Its from the core the error so I was looking at the cookbooks and
> documentation but cannot get around this specific limit or find a
> configuration to tweak that fixes it.
>
> The limit only affects TCP (will affect TLS as well but I haven't got
> that far) and is 1024 it seems.
>
> Kamailio version is: 5.7.6
> OS: Ubuntu 22.04
>
> Things I have done so far:
> I have set limitNOFILE=65535 in the service file
> Set the tcp/tls_max_connections at 8192 (default is 2048)
> Increase the tcp_rd_buf_size to 16k+
>
>
> The service I am using to loadtest is SIPp with flags "-t tn" for TCP
> multisocket as this service will have much more than 1024 concurrent
> TCP connections to it from a single source IP.
>
> I think I have missed something basic here as the devel and the source
> code references: "ksr_tcp_accept_iplimit" here at line 541:
> https://github.com/kamailio/kamailio/blob/master/src/main.c#L541
>
> I cannot find a way to change this with a configuration line it seems,
> am I being blind or is my only option to build from source and change
> this?
>
> Many Thanks,
>
> John.
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio Developers Meeting, Nov 19-20, 2024, in Dusseldorf

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server project is organizing another meeting of its
developers and community members during November 19-20, 2024 (Tue-Wed),
hosted again by sipgate.de in Dusseldorf, Germany.

The event is intended to facilitate the interaction between Kamailio
developers and contributors in order to offer a convenient environment
for working together on several topics of high interest for the project,
including writing code for Kamailio and its tools, improving
documentation, or discuss about future development.

Everyone from the community is welcome to join, developer or user
interested in helping the project. Please note we have a limited
capacity of seats in the meeting room, the main policy for accepting
participants being first come first server. Also, very important to be
aware that this is not an event to learn how to use Kamailio.

More details about the event, the venue, how to register, are available at:

  * https://www.kamailio.org/w/developers-meeting/

Looking forward to those two intensive hacking Kamailio days in Dusseldorf!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: SHM Memory leak?

[Daniel-Constantin Mierla via sr-users]

Hello,

first, the value for -M is too high, I cannot easily think of a case
when one needs 1GB of private memory for each kamailio process.

You can try to run the rpc command shm.stats and look in the syslog for
the report to check if it is different that what you get with mod.mem_stats.

Cheers,
Daniel

On 10.07.24 11:36, Ihor Olkhovskyi via sr-users wrote:
> Hello!
>
> I'm trying to get where all the SHM memory gone. For the moment I'm
> using these settings:
> -m 8192 -M 1024
> which means 8G of SHM meory.
> Kamailio parameters are the following
>
> fork=yes
> children=8
> tcp_children=12
> enable_tls=yes
> enable_sctp=no
> tls_threads_mode=2
> tcp_accept_no_cl=yes
> tcp_max_connections=63536
> tls_max_connections=63536
> tcp_accept_aliases=no
> tcp_async=yes
> tcp_connect_timeout=10
> tcp_conn_wq_max=63536
> tcp_crlf_ping=yes
> tcp_delayed_ack=yes
> tcp_fd_cache=yes
> tcp_keepalive=yes
> tcp_keepcnt=3
> tcp_keepidle=30
> tcp_keepintvl=10
> tcp_linger2=30
> tcp_rd_buf_size=8
> tcp_send_timeout=10
> tcp_wq_blk_size=2100
> tcp_wq_max=10485760
> open_files_limit=63536
>
> And having ~1000 TLS/WSS clients I'm getting this after 3 days of running:
> {
>   "jsonrpc":  "2.0",
>   "result": [
>     "shmem:fragments = 2796",
>     "shmem:free_size = 3737947072", (3.7 G)
>     "shmem:max_used_size = 4857418512", (4.8 G)
>     "shmem:real_used_size = 4851987520",
>     "shmem:total_size = 8589934592",
>     "shmem:used_size = 4838988096"  (4.8 G)
>   ],
>   "id": 984479
> }
> Means half of SHM memory is gone
>
> When running kamcmd mod.stats all shm I'm getting (output truncated
> for the largest values)
>
> Module: core
> {
>   ...
>         tcpconn_new(1201): 130669280 (0.13 G)
>       ...
>         Total: 131657632 (0.13 G)
> }
>
> Module: sl
> {
>  ...
>         Total: 7520
> }
>
> Module: siptrace
> {
>  ...
>         Total: 13520
> }
>
> Module: rr
> {
>         Total: 0
> }
>
> Module: dialog
> {
> ...
>         Total: 146080
> }
>
> Module: permissions
> {
> ...
>         Total: 62144
> }
>
> Module: htable
> {
>   
>         Total: 3359552 (3.3 M)
> }
>
> Module: rtpengine
> {
>  ...
>         Total: 31456
> }
>
> Module: textopsx
> {
>         Total: 0
> }
>
> Module: tsilo
> {
>  ...
>         Total: 75072
> }
>
> Module: tm
> {
>  
>         Total: 3459504 (3.4 M)
> }
>
> Module: usrloc
> {
>  
>         Total: 1217616
> }
>
> Module: pua_dialoginfo
> {
>  ...
>         Total: 8720
> }
>
> Module: pua
> {
>  ...
>         Total: 150848
> }
>
> Module: pike
> {
>  ...
>         Total: 9504
> }
>
> Module: websocket
> {
>         wsconn_add(198): 54139856 (54 M)
>  ...
>         Total: 54148096 (54 M)
> }
>
> Module: debugger
> {
>  ...
>         Total: 21872
> }
>
> Module: tmx
> {
>         Total: 512
> }
>
> Module: kex
> {
>        
>         Total: 1888
> }
>
> Module: tls
> {
> ...
>         ser_malloc(364): 87246112 (87 M)
>  ...
>         Total: 87997168 (87 M)
> }
>
> Module: secfilter
> {
> ...
>         Total: 768
> }
>
> Module: exec
> {
>  ...
>         Total: 16
> }
>
> Module: dispatcher
> {
>  ...
>         Total: 2992
> }
>
> Module: cfgutils
> {
>  ...
>         Total: 48
> }
>
> Module: app_python3
> {
>  ...
>         Total: 32
> }
>
> So, I'm guessing, where all the memory gone? Is there any way to get
> more detailed info on SHM?
>
> Kamailio 5.8.2
>
> -- 
> Thanks in advance,
> Ihor
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Possible Kamailio memmory leak - version 5.8.2

[Daniel-Constantin Mierla via sr-users]

Hello,

I couldn't spot any error message in the log file that you attached,
have you taken it when you encountered the problem?

Anyhow, I am not familiar with the implementation of the
event_route[network:msg], but the shm info indicates the leak to be
related to avp, so I pushed a patch to destroy the nio_msg_avp avp after
event route execution. Can you try with git master branch and see if
works ok?

Cheers,
Daniel

On 02.07.24 16:24, Vanderlei Torres Batistela via sr-users wrote:
> Hello all,
>
> I am using a very simple scritp with corex module enabled .  Normal
> calls works fine, but a scenario where INVITE does not
> receive response and the call is released with SIP 408 (request
> timeout) leads to memmory leak.  I verified it making a lot of 
> calls with this scenario and printing the  shared memory (using kamcmd
> core.shmmem) .  Its ocurred with modparam("corex", "nio_intercept", 1).
>  If  I modify to modparam("corex", "nio_intercept", 0) the memmory
> leak does not ocurr anymore.
> The problem also occurs in another scenario where the SIP Cancel
> message is not responded to.
>
> My script has this event route
>  
> # event route
> event_route[network:msg] {
>
>     xlog("L_INFO", "Dentro do Event_Route \n");
>     if (is_incoming()) {
>         xlog("L_INFO", "Received message '$mb' \n");
>         $avp(msg) = $mb;
>         xinfo("avp(msg) = $avp(msg)");
>     } else {
>         xlog("L_INFO", "Sending message '$mb' \n");
>          $avp(msg) = $mb;
>     };
> }
>
> Test done wtih 4000 calls:
>
> [root@labcom070 kamailio]# kamctl stats shmem
> {
>   "jsonrpc":  "2.0",
>   "result": [
>     "shmem:fragments = 900",
>     "shmem:free_size = 6180368",
>     "shmem:max_used_size = 66980272",
>     "shmem:real_used_size = 60928496",
>     "shmem:total_size = 67108864",
>     "shmem:used_size = 54884944"
>   ],
>   "id": 393115
> }
>
>
> [root@labcom070 kamailio]# kamcmd mod.stats all shm
> Module: core
> {
>         create_avp(178): 52257504
>         counters_prefork_init(211): 53760
>         cfg_clone_str(132): 112
>         cfg_shmize(221): 832
>         main_loop(1381): 16
>         init_pt(104): 16
>         init_pt(103): 16
>         init_pt(102): 6224
>         cfg_register_ctx(47): 96
>         init_tcp(5197): 8192
>         init_tcp(5191): 32768
>         init_tcp(5182): 16
>         init_tcp(5175): 16
>         init_tcp(5167): 16
>         init_tcp(5161): 16
>         init_tcp(5149): 16
>         init_avps(92): 16
>         init_avps(91): 16
>         init_dst_blocklist(435): 16384
>         init_dst_blocklist(427): 16
>         timer_alloc(494): 96
>         init_dns_cache(368): 16
>         init_dns_cache(359): 16384
>         init_dns_cache(351): 16
>         init_dns_cache(343): 16
>         init_timer(264): 16
>         init_timer(263): 16384
>         init_timer(262): 16
>         init_timer(261): 16
>         init_timer(250): 16
>         init_timer(218): 16
>         init_timer(207): 278544
>         init_timer(206): 16
>         init_timer(194): 16
>         cfg_child_cb_new(832): 64
>         sr_cfg_init(371): 16
>         sr_cfg_init(364): 16
>         sr_cfg_init(356): 16
>         sr_cfg_init(344): 16
>         sr_cfg_init(332): 16
>         ksr_shutdown_phase_init(123): 16
>         rpc_hash_add(118): 16
>         qm_shm_lock_init(1463): 16
>         Total: 52687808
> }
>
>  I attached  my kamailio  script used and a log with one call   using
> the command "kamcmd corex.shm_summary" with modparam("corex",
> "nio_intercept", 1)
> and  modparam("corex", "nio_intercept", 0)
>
> Regards,
>
> Vanderlei
>
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:


-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.6.6 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.6.6 stable release is out.

This is a maintenance release of the latest stable branch, 5.6, that
includes fixes since the release of v5.6.5. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.6.x. Deployments running previous v5.6.x
versions are strongly recommended to be upgraded to v5.6.6.

Note that 5.6 is now the third last stable branch, v5.6.6 being the last
planned released in 5.5.x series. The latest two stable branch are 5.7
and 5.8, with v5.8.2 being released a while ago.


For more details about version 5.6.6 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/07/kamailio-v5-6-6-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.6.6

[Daniel-Constantin Mierla via sr-users]

Hello,

short reminder that today v5.6.6 is going to be release, as usual, any
commits to branch 5.6 have to be announced to sr-dev mailing list and
wait for the ack before pushing to the repo to avoid conflicts with the
release building process. Once the announcement is out, the commits can
go in the branch as usual.

Note that this is going to be the last release in the 5.6.x series,
therefore migration to the series 5.8.x or 5.7.x is advisable.

Cheers,
Daniel

On 27.06.24 10:29, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.6.6 (out of branch 5.6) later
> this week (likely on Wednesday, July 3, 2024). If anyone is aware of
> issues not yet on the bug tracker, report them there asap in order to
> have a better chance to be fixed.
>
> This is going to be the last release out of branch 5.6 to mark the end
> of official/packaging maintenance.
>
> Cheers,
> Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.7.6 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.7.6 stable release is out.

This is a maintenance release of the latest stable branch, 5.7, that
includes fixes since the release of v5.7.5. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.7.x. Deployments running previous v5.7.x
versions are strongly recommended to be upgraded to v5.7.6.

For more details about version 5.7.6 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/07/kamailio-v5-7-6-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Note that 5.7.x is currently the previous stable release series, the
latest is 5.8.x and v5.8.2 was released on June 12, 2024.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.7.6

[Daniel-Constantin Mierla via sr-users]

Hello,

short reminder that today v5.7.6 is going to be release, as usual, any
commits to branch 5.7 have to be announced to sr-dev mailing list and
wait for the ack before pushing to the repo to avoid conflicts with the
release building process. Once the announcement is out, the commits can
go in the branch as usual.

Cheers,
Daniel

On 27.06.24 10:20, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.7.6 (out of branch 5.7) on
> Tuesday, July 2, 2024. If anyone is aware of issues not yet on the bug
> tracker, report them there asap in order to have a better chance to be
> fixed.
>
> Cheers,
> Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: SRV in advertise?

[Daniel-Constantin Mierla via sr-users]

Hello,

indeed, as mentioned, the presence of a port in a SIP address makes it
to skip SRV lookup.

Anyhow, I am jumping in to see what is the Kamailio version used in this
scenario? I don't recall exactly, but a while ago there was a related
commit, at least it looked like when I did some backports today for next
planned release in 5.6.x series.

Cheers,
Daniel

On 01.07.24 19:16, Ben Kaufman via sr-users wrote:
>
> While I don’t know if it will or won’t cause the failure, you
> shouldn’t have a port number in something you’re intending to use as a
> SRV record. 
>
>  
>
> - Kaufman
>
>  
>
>  
>
> *From:*David Villasmil 
> *Sent:* Monday, July 1, 2024 9:19 AM
> *To:* Ben Kaufman 
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] SRV in advertise?
>
>  
>
>
>   
>
> *CAUTION:*This email originated from outside the organization. _Do not
> click links or open attachments_ unless you recognize the sender and
> know the content is safe.
>
>  
>
> Hey all,
>
>  
>
> Joel, it’s failing saying the destination is unresolvable and Ben, I’m
> setting it like
>
>  
>
> Listen=tls:1.2.3.4:5061  advertise
> mydomain.com:5061 
>
>  
>
> My domain.com  srv is like 
>
>  
>
> _sips._tcp.domain.com  resolving to
> sip.domain.com  (among others like udp, etc)
>
>  
>
> I would expect Kamailio to resolve its own srv, or have an option NOT
> to attempt to resolve and just the set host in the record-route, but
> maybe that’s just not how it works. Yes, setting sip.domain.com:5061
>  works but the the record-route would
> have that (sip.domain.com ) exact same host
> and the client might disconnect and reconnect to that dns instead of
> the actual SRV.
>
>
> Regards,
>
>  
>
> David Villasmil
>
> email: david.villasmil.w...@gmail.com
>
>  
>
>  
>
>  
>
> On Mon, 1 Jul 2024 at 15:46, Ben Kaufman  wrote:
>
> Are you using a hostname that should resolve as srv , for example,
> sip.domain.com , or are you using the
> underscore, scheme, underscore transport protocol, hostname type
> like _sip._udp.domain.com ?
>
>  
>
> Regards,
>
> Kaufman
>
>  
>
> *From:*David Villasmil via sr-users 
> *Sent:* Sunday, June 30, 2024 6:02 PM
> *To:* Kamailio (SER) - Users Mailing List
> 
> *Cc:* David Villasmil 
> *Subject:* [SR-Users] SRV in advertise?
>
>  
>
>
>   
>
> *CAUTION:*This email originated from outside the organization. _Do
> not click links or open attachments_ unless you recognize the
> sender and know the content is safe.
>
>  
>
> Hello guys,
>
>  
>
> I'm trying to use an SRV as an advertised address but kamailio
> fails to start. Is this not possible?
>
>  
>
> Thanks,
>
>  
>
> David Villasmil
>
> email: david.villasmil.w...@gmail.com
>
>  
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.6.6

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.6.6 (out of branch 5.6) later
this week (likely on Wednesday, July 3, 2024). If anyone is aware of
issues not yet on the bug tracker, report them there asap in order to
have a better chance to be fixed.

This is going to be the last release out of branch 5.6 to mark the end
of official/packaging maintenance.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.7.6

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.7.6 (out of branch 5.7) on
Tuesday, July 2, 2024. If anyone is aware of issues not yet on the bug
tracker, report them there asap in order to have a better chance to be
fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.8.2 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.8.2 stable release is out.

This is a maintenance release of the latest stable branch, 5.8, that
includes fixes since the release of v5.8.1. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.8.x. Deployments running previous v5.8.x
versions are strongly recommended to be upgraded to v5.8.2.

For more details about version 5.8.2 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/06/kamailio-v5-8-2-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.8.2

[Daniel-Constantin Mierla via sr-users]

Hello,

quick reminder that v5.8.2 is going to be released today, as usual, till
the release announcement is out, any commits to branch 5.8 should be
announced on sr-dev mailing list and wait for ack before pushing it to
the git repo. Once the release is out, commits can go into branch 5.8 as
usual.

Cheers,
Daniel

On 07.06.24 20:07, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.8.2 (out of branch 5.8) on
> Wednesday,
> June 12, 2024. If anyone is aware of issues not yet on the bug tracker,
> report them there asap in order to have a better chance to be fixed.
>
> Cheers,
> Daniel
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: New features in v.5.8

[Daniel-Constantin Mierla via sr-users]

Hello,

On 10.06.24 09:45, Leonid Fainshtein via sr-users wrote:
> Hi,
> In the "Kamailio v5.8.0 Release Notes" I see: "SIP overload control
> support for server (RFC7339)". Where can I find some more details
> about the feature?
first read the RFC to understand what all is about. In Kamailio was
added the ability (or more flexibility) to parse or set the related Via
parameters.
> Also, the similar question about the new "influxdbc" module. What are
> the possible use cases for this module?

If you use influxdb for collecting metrics/statistics as time series.
You should read more about influxdb itself to see if it is useful for
you or not.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.8.2

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.8.2 (out of branch 5.8) on
Wednesday,
June 12, 2024. If anyone is aware of issues not yet on the bug tracker,
report them there asap in order to have a better chance to be fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com


__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: libstirshaken installation issues

[Daniel-Constantin Mierla via sr-users]

Hello,

this looks like related only to the libstirshaken project, nothing to do
with Kamailio module. Apparently is about deprecated functions treated
as errors, but you have to address the issue to the libstirshaken project.

Alternatively, in Kamailio you can use secsipid module, which also
offers STIR/SHAKEN functionality.

Cheers,
Daniel

On 28.05.24 23:20, tfayomi--- via sr-users wrote:
> Hi All,
>
> I am attempting to install the stirshaken module for kamailio and I ran into 
> a couple issues installing the open source c library for libstirshaken. When 
> I use the make command, I'm getting this error:
>
> src/stir_shaken.c: In function 'stir_shaken_is_key_trusted':
> src/stir_shaken.c:726:9: error: 'EVP_PKEY_cmp' is deprecated: Since OpenSSL 
> 3.0 [-Werror=deprecated-declarations]
>   726 | if (!EVP_PKEY_cmp(pkey, candidate_pkey)) {
>   | ^~
> In file included from /usr/include/openssl/x509.h:29,
>  from /usr/include/openssl/ssl.h:31,
>  from /usr/include/libks2/libks/ks_ssl.h:25,
>  from /usr/include/libks2/libks/ks.h:80,
>  from include/stir_shaken.h:15,
>  from src/stir_shaken.c:1:
> /usr/include/openssl/evp.h:1418:5: note: declared here
>  1418 | int EVP_PKEY_cmp(const EVP_PKEY *a, const EVP_PKEY *b);
>   | ^~~~
> At top level:
> cc1: note: unrecognized command-line option 
> '-Wno-gnu-zero-variadic-macro-arguments' may have been intended to silence 
> earlier diagnostics
> cc1: all warnings being treated as errors
> make: *** [Makefile:1337: src/stir_shaken.lo] Error 1
>
> I tried going into the stir_shaken file and changing EVP_PKEY_cmp to 
> EVP_PKEY_eq, but it just brings up more deprecation errors. I also tried 
> rolling back the openssl version on my machine to openssl version 1.1 and 
> changing EVP_PKEY_eq back to EVP_PKEY_cmp, but the same error persists. Is 
> there any way to resolve this error, or is there another library that can be 
> used to get the stirshaken module for kamailio?
>
> Thanks in advance,
> Temi
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: $dlg_var() not implemented in ims_dialog module

[Daniel-Constantin Mierla via sr-users]

Hello,

On 17.05.24 08:39, Valentin Christoph via sr-users wrote:
>
> Dear all,
>
>  
>
> I would probably need to store some dialog scoped information in an
> IMS environment, but the ims_dialog module does not implement the
> $dlg_var() pseudo variable.
>
>  
>
> Do you know other, maybe better, possibilities to store dialog scoped
> information in an IMS (CSCF) environment?
>
I leverage a lot htable, even when dialog is used. The call-id ($ci) is
the same for all messages within the dialog and it can be used as a prefix:

$sht(dlg=>$ci::xyz)

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Kamailio IPSec module

[Daniel-Constantin Mierla via sr-users]

Hello,

On 15.05.24 22:09, H Yavari via sr-users wrote:
> Hi all,
>
> I was reviewing the `ims_ipsec_pcscf` code and noticed that this
> module creates a pool of sockets using different ports
> (ipsec_max_connections). I'm unclear on the necessity of this
> approach. Can't we simply create one server listener and one client
> listener to handle all UE connections? If this is feasible, is there
> still a need to create the pool at startup?
>
> I'm curious if this is due to an architectural limitation or if the
> IPSec module can be modified to replace the current implementation
> with a more efficient one.

technically it is no restriction to have one client socket and one
server socket. I am not much active in the VoLTE or VoNR, although I
played lately with the later, but from some past discussions I
understood that the specs suggest/recommend this approach with a pool of
sockets -- I haven't read the specs to confirm personally if that's the
case.

Anyhow, during the OSMNT'24 and KamailioWorld'24 conferences, I had
discussions with some participants interested in the topic and switching
to (or adding the option of) single client/server socket was considered
to be done in the future.

For now, if you are concerned of using too many resources due to many
children processes, you can use development version (git master branch)
where you have the option to have threads for receiving traffic on UDP
sockets, with a single pool of processes to handle the UDP SIP traffic:

  -
https://www.kamailio.org/wikidocs/cookbooks/devel/core/#udp_receiver_mode

Or, even better, if you can develop the code for having single
client/server socket, just do it and make a PR.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: TLS module crashes with FIPS OpenSSL

[Daniel-Constantin Mierla via sr-users]

The backtrace is from shutdown cleanup as pointed before, so it is not
the one that caused the crash.

To get more than one core file, so it is not going to have core file
overwritten, you have to enable one core file per pid/process (or set
core file name pattern), some hints at:

 - https://www.kamailio.org/wikidocs/tutorials/troubleshooting/coredumpfile/

Searching on the web should reveal other tutorials about it.

Then you should get more than one core file on a crash and you should
grab the backtrace from all of them.

You should also install the debugging symbols for libssl and libcrypto,
there could be useful details shown in the backtraces.

Cheers,
Daniel


On 14.05.24 19:38, Marat Gareev via sr-users wrote:
> Henning,
> I can't find anything else. But I caught one more segfault in the same
> scenario (stopping service)...
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7f3614f3c609 in init_thread_deregister.isra () from 
> /lib64/libcrypto.so.3
> Missing separate debuginfos, use: dnf debuginfo-install 
> kamailio-5.7.5-4817.x86_64
> (gdb) bt
> #0  0x7f3614f3c609 in init_thread_deregister.isra () from 
> /lib64/libcrypto.so.3
> #1  0x7f3614e69daa in ossl_provider_free.part () from 
> /lib64/libcrypto.so.3
> #2  0x7f3614ea81a0 in OPENSSL_sk_pop_free () from /lib64/libcrypto.so.3
> #3  0x7f3614e68878 in prov_conf_ossl_ctx_free () from 
> /lib64/libcrypto.so.3
> #4  0x7f3614e5d405 in CRYPTO_free_ex_data () from /lib64/libcrypto.so.3
> #5  0x7f3614e5d59f in context_deinit.part () from /lib64/libcrypto.so.3
> #6  0x7f3614e600b2 in OPENSSL_cleanup () from /lib64/libcrypto.so.3
> #7  0x7f36151b921e in ?? ()
> #8  0x0001a298 in ?? ()
> #9  0x7f3604cc66c8 in ?? ()
> #10 0x7ffead90c920 in ?? ()
> #11 0x0071e0a0 in futex_release (lock=0x7f3615b7c930 ) at 
> core/mem/../mem/../futexlock.h:134
> #12 0x006e993e in destroy_tls () at core/tls_hooks.c:75
> #13 0x0041f278 in cleanup (show_status=1) at main.c:595
> #14 0x00420af1 in shutdown_children (sig=15, show_status=1) at 
> main.c:722
> #15 0x00421717 in handle_sigs () at main.c:753
> #16 0x00430c88 in main_loop () at main.c:1989
> #17 0x00439d13 in main (argc=14, argv=0x7ffead90d2f8) at main.c:3213
> + unexpected message in log
> INFO kernel: [26983.427997] traps: kamailio[88753] general protection fault 
> ip:7f5a83585609 sp:7ffc9b2b4400 error:0 in 
> libcrypto.so.3.0.7[7f5a8339d000+25c000]
>
> Richard,
> I start service with the following parameters
> /usr/local/sbin/kamailio --atexit=no -m 256 -P
> /var/run/ser/kamailio.pid -u ser -g ser -f
> /usr/local/etc/kamailio/kamailio.cfg -w /usr/local
>
> вт, 14 мая 2024 г. в 18:57, Richard Chan via sr-users
> :
>
> Can you try with
>
> kamailio ... --atexit=no 
>
>
>
> On Tue, 14 May 2024, 13:13 Marat Gareev via sr-users,
>  wrote:
>
> Hello again,
>
> I've updated Kamailio to 5.7.5, set tls_threads_mode=2 and got
> another segfault:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7f26bb352efd in __strlen_avx2 () from /lib64/libc.so.6
> Missing separate debuginfos, use: dnf debuginfo-install 
> kamailio-5.7.5-4817.x86_64
> (gdb) bt
> #0  0x7f26bb352efd in __strlen_avx2 () from /lib64/libc.so.6
> #1  0x7f26bb31a278 in __vfprintf_internal () from /lib64/libc.so.6
> #2  0x7f26bb3dd4ea in __vsyslog_internal () from /lib64/libc.so.6
> #3  0x7f26bb3dd9ca in syslog () from /lib64/libc.so.6
> #4  0x0071e574 in qm_debug_check_frag (qm=0x7f26aa4ee000, 
> f=0x7f26aa638388, file=0x7f26baa5b0b6 "tls: tls_init.c", line=399, 
> efile=0x8abb39 "core/mem/q_malloc.c", eline=526) at core/mem/q_malloc.c:126
> #5  0x007227c3 in qm_free (qmp=0x7f26aa4ee000, 
> p=0x7f26aa6383c0, file=0x7f26baa5b0b6 "tls: tls_init.c", func=0x7f26baa5cdb8 
> "ser_free", line=399, mname=0x7f26baa5b0b2 "tls") at core/mem/q_malloc.c:526
> #6  0x0072d2c9 in qm_shm_free (qmp=0x7f26aa4ee000, 
> p=0x7f26aa6383c0, file=0x7f26baa5b0b6 "tls: tls_init.c", func=0x7f26baa5cdb8 
> "ser_free", line=399, mname=0x7f26baa5b0b2 "tls")
> at core/mem/q_malloc.c:1364
> #7  0x7f26baa12ea9 in ?? ()
> #8  0x7f26aa6383c0 in ?? ()
> #9  0x01b3ba70914b in ?? ()
> #10 0x7f26ba853e4b in ?? () from /lib64/libcrypto.so.3
> #11 0x7f26aa6383c0 in ?? ()
> #12 0x7f26aa6383c0 in ?? ()
> #13 0x7f26ba61cfc5 in conf_modules_finish_int () from 
> /lib64/libcrypto.so.3
> #14 0x7f26ba61d694 in CONF_modules_unload () from 
> /lib64/libcrypto.so.3
> #15 0x7f26ba6c0ff9 in OPENSSL_cleanup () from 
> /lib64/libcrypto.so.3
> #16 0x7f26baa1a21e in ?? ()
> #17 0x0001000623b0 in ?? ()
> #18 0x7f26aa5276c8 in ?? ()
> 

[SR-Users] Re: dynamic selection of authentication algorithm

[Daniel-Constantin Mierla via sr-users]

On 14.05.24 13:01, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> are you still planning to add this patch to the repo?
> Based on non-existing comments, looks like I'm the only one interested.
> So it is not worth to create a PR. 

I actually replied on you initial email at that time, saying that is
interesting to add it. My previous email was a follow up of that email.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: dynamic selection of authentication algorithm

[Daniel-Constantin Mierla via sr-users]

Hello,

are you still planning to add this patch to the repo?

Cheers,
Daniel

On 28.04.24 23:10, Daniel-Constantin Mierla wrote:
> Hello,
>
> it is an acceptable variant, you can go ahead and push the commit and
> docs for the new function.
>
> Later over the time, I might look at adding also a parameter option to
> the existing functions.
>
> Cheers,
> Daniel
>
> On 20.04.24 19:57, Juha Heinanen via sr-users wrote:
>> How about this new function that sets the algorithm?
>>
>> -- Juha
>>
>> iff --git a/src/modules/auth/auth_mod.c b/src/modules/auth/auth_mod.c
>> index 534ad9e20f..4e3a584d22 100644
>> --- a/src/modules/auth/auth_mod.c
>> +++ b/src/modules/auth/auth_mod.c
>> @@ -74,6 +74,10 @@ int w_consume_credentials(struct sip_msg *msg, char *s1, 
>> char *s2);
>>   * Check for credentials with given realm
>>   */
>>  int w_has_credentials(struct sip_msg *msg, char *s1, char *s2);
>> +/*
>> + * Set authentication algorithm
>> + */
>> +int w_auth_algorithm(struct sip_msg *msg, char *alg, char* s2);
>>  
>>  static int pv_proxy_authenticate(
>> struct sip_msg *msg, char *realm, char *passwd, char *flags);
>> @@ -170,6 +174,8 @@ static cmd_export_t cmds[] = {
>> REQUEST_ROUTE},
>> {"pv_auth_check", (cmd_function)w_pv_auth_check, 4, fixup_pv_auth_check,
>> 0, REQUEST_ROUTE},
>> +   {"auth_algorithm", w_auth_algorithm, 1, fixup_spve_null, 0,
>> +   REQUEST_ROUTE},
>> {"bind_auth_s", (cmd_function)bind_auth_s, 0, 0, 0},
>>  
>> {0, 0, 0, 0, 0, 0}
>> @@ -475,6 +481,35 @@ int w_has_credentials(sip_msg_t *msg, char *realm, char 
>> *s2)
>> return -1;
>> }
>> return ki_has_credentials(msg, );
>> +
>> +}
>> +/**
>> + *
>> + */
>> +int w_auth_algorithm(sip_msg_t *msg, char* alg, char* s2)
>> +{
>> +   if (fixup_get_svalue(msg, (gparam_t*)alg, _algorithm) < 0) {
>> +   LM_ERR("failed to get algorithm value\n");
>> +   return -1;
>> +   }
>> +
>> +   if (strcmp(auth_algorithm.s, "MD5") == 0) {
>> +   hash_hex_len = HASHHEXLEN;
>> +   calc_HA1 = calc_HA1_md5;
>> +   calc_response = calc_response_md5;
>> +   }
>> +   else if (strcmp(auth_algorithm.s, "SHA-256") == 0) {
>> +   hash_hex_len = HASHHEXLEN_SHA256;
>> +   calc_HA1 = calc_HA1_sha256;
>> +   calc_response = calc_response_sha256;
>> +   }
>> +   else {
>> +   LM_ERR("Invalid algorithm provided."
>> +   " Possible values are \"\", \"MD5\" or \"SHA-256\"\n");
>> +   return -1;
>> +   }
>> +
>> +   return 1;
>>  }
>>  
>>  #ifdef USE_NC
>> __
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
>> Important: keep the mailing list in the recipients, do not reply only to the 
>> sender!
>> Edit mailing list options or unsubscribe:
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.7.5 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.7.5 stable release is out.

This is a maintenance release of the latest stable branch, 5.7, that
includes fixes since the release of v5.7.4. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.7.x. Deployments running previous v5.7.x
versions are strongly recommended to be upgraded to v5.7.5.

For more details about version 5.7.5 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/05/kamailio-v5-7-5-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Note that 5.7.x is currently the previous stable release series, the
latest is 5.8.x and v5.8.1 was released on April 3, 2024.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.7.5

[Daniel-Constantin Mierla via sr-users]

Hello,

short reminder that today is planned to release v5.7.5. As usual, until
the announcement is out, any commit that should go to branch 5.7 has to
be announced to sr-dev mailing list and wait for ack before pushing to
git repository in order to avoid conflicts with release building process.

Cheers,
Daniel

On 03.05.24 09:28, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.7.5 (out of branch 5.7) on
> Wednesday, May 8, 2024. If anyone is aware of issues not yet on the bug
> tracker, report them there asap in order to have a better chance to be
> fixed.
>
> Cheers,
> Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: sql_query fails from event_route

[Daniel-Constantin Mierla via sr-users]

On 07.05.24 11:15, Juha Heinanen via sr-users wrote:
> Juha Heinanen via sr-users writes:
>
>> I noticed that sql_query does not (anymore)  work when called from
>> event route:
> I created bug issue https://github.com/kamailio/kamailio/issues/3843
> about this to GitHub, since it really looks like a bug, because the same
> code has worked fine in some earlier K release.

I posted on the tracker as well, but for sake of completing the
discussion here for mailing list archive ...

Connection close event is executed from TCP main process, which likely
has no SQL connection open. Till some point in the past, connection
close event was triggered from a few places (from tcp worker processes),
but actually it was not done for all cases when the connections were
closed, some of these events missing (there are situations when only tcp
main process close the connections). Now, I would strongly advise doing
anything time expensive in the TCP main process, it was designed only as
tcp connections manager, so in this case, I would rather delegate the
sql query to an async worker (via async module or via mqueue+rtimer).

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: sql_query fails from event_route

[Daniel-Constantin Mierla via sr-users]

correction, see inline ...

On 07.05.24 12:34, Daniel-Constantin Mierla wrote:
>
>
> On 07.05.24 11:15, Juha Heinanen via sr-users wrote:
>> Juha Heinanen via sr-users writes:
>>
>>> I noticed that sql_query does not (anymore)  work when called from
>>> event route:
>> I created bug issue https://github.com/kamailio/kamailio/issues/3843
>> about this to GitHub, since it really looks like a bug, because the same
>> code has worked fine in some earlier K release.
>
> I posted on the tracker as well, but for sake of completing the
> discussion here for mailing list archive ...
>
> Connection close event is executed from TCP main process, which likely
> has no SQL connection open. Till some point in the past, connection
> close event was triggered from a few places (from tcp worker
> processes), but actually it was not done for all cases when the
> connections were closed, some of these events missing (there are
> situations when only tcp main process close the connections). Now, I
> would strongly advise
>
^^^ advise *against* doing ...


> doing anything time expensive in the TCP main process, it was designed
> only as tcp connections manager, so in this case, I would rather
> delegate the sql query to an async worker (via async module or via
> mqueue+rtimer).
>
> Cheers, Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.7.5

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.7.5 (out of branch 5.7) on
Wednesday, May 8, 2024. If anyone is aware of issues not yet on the bug
tracker, report them there asap in order to have a better chance to be
fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: dynamic selection of authentication algorithm

[Daniel-Constantin Mierla via sr-users]

Hello,

it is an acceptable variant, you can go ahead and push the commit and
docs for the new function.

Later over the time, I might look at adding also a parameter option to
the existing functions.

Cheers,
Daniel

On 20.04.24 19:57, Juha Heinanen via sr-users wrote:
> How about this new function that sets the algorithm?
>
> -- Juha
>
> iff --git a/src/modules/auth/auth_mod.c b/src/modules/auth/auth_mod.c
> index 534ad9e20f..4e3a584d22 100644
> --- a/src/modules/auth/auth_mod.c
> +++ b/src/modules/auth/auth_mod.c
> @@ -74,6 +74,10 @@ int w_consume_credentials(struct sip_msg *msg, char *s1, 
> char *s2);
>   * Check for credentials with given realm
>   */
>  int w_has_credentials(struct sip_msg *msg, char *s1, char *s2);
> +/*
> + * Set authentication algorithm
> + */
> +int w_auth_algorithm(struct sip_msg *msg, char *alg, char* s2);
>  
>  static int pv_proxy_authenticate(
> struct sip_msg *msg, char *realm, char *passwd, char *flags);
> @@ -170,6 +174,8 @@ static cmd_export_t cmds[] = {
> REQUEST_ROUTE},
> {"pv_auth_check", (cmd_function)w_pv_auth_check, 4, fixup_pv_auth_check,
> 0, REQUEST_ROUTE},
> +   {"auth_algorithm", w_auth_algorithm, 1, fixup_spve_null, 0,
> +   REQUEST_ROUTE},
> {"bind_auth_s", (cmd_function)bind_auth_s, 0, 0, 0},
>  
> {0, 0, 0, 0, 0, 0}
> @@ -475,6 +481,35 @@ int w_has_credentials(sip_msg_t *msg, char *realm, char 
> *s2)
> return -1;
> }
> return ki_has_credentials(msg, );
> +
> +}
> +/**
> + *
> + */
> +int w_auth_algorithm(sip_msg_t *msg, char* alg, char* s2)
> +{
> +   if (fixup_get_svalue(msg, (gparam_t*)alg, _algorithm) < 0) {
> +   LM_ERR("failed to get algorithm value\n");
> +   return -1;
> +   }
> +
> +   if (strcmp(auth_algorithm.s, "MD5") == 0) {
> +   hash_hex_len = HASHHEXLEN;
> +   calc_HA1 = calc_HA1_md5;
> +   calc_response = calc_response_md5;
> +   }
> +   else if (strcmp(auth_algorithm.s, "SHA-256") == 0) {
> +   hash_hex_len = HASHHEXLEN_SHA256;
> +   calc_HA1 = calc_HA1_sha256;
> +   calc_response = calc_response_sha256;
> +   }
> +   else {
> +   LM_ERR("Invalid algorithm provided."
> +   " Possible values are \"\", \"MD5\" or \"SHA-256\"\n");
> +   return -1;
> +   }
> +
> +   return 1;
>  }
>  
>  #ifdef USE_NC
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: ERROR: [core/ppcfg.c:275]: pp_ifdef_level_error(): different number of preprocessor directives: 1 more #!if[n]def as #!endif

[Daniel-Constantin Mierla via sr-users]

Hello,

can you add an extra EoL at the end of the file and try again? iirc, at
some point there was an issue counting the #!endif at the end of the
file if it was not followed by a new line. I think that was fixed.

Also, kamailio has a cli parameter to print the config after evaluating
pre-processor directive, you can use it to see if the result is what you
expect to be active in kamailio.cfg

Cheers,
Daniel

On 25.04.24 15:47, Tristan Ferreira via sr-users wrote:
>
> Hi,
>
> I am trying to learn Kamailio to set up a SIP/RTP proxy for WebRTC
> with FreeSWITCH, and I wanted to use this configuration file template
> as a starting point.
> (Source: https://github.com/havfo/WEBRTC-to-SIP)
>
> But i have the error : *ERROR: [core/ppcfg.c:275]:
> pp_ifdef_level_error(): different number of preprocessor directives: 1
> more #!if[n]def as #!endif*
>
> I don't understand because I checked and everything seems okay with
> the if/endif statements to me.
>
> |# grep '#!ifndef' kamailio.cfg | wc -l 2 # grep '#!ifdef'
> kamailio.cfg | wc -l 49 # grep '#!endif' kamailio.cfg | wc -l 51 |
>
> And it's ok for chat gpt too :
>
> |#!ifdef : 49 occurrences #!ifndef : 2 occurrences Total (#!ifdef and
> #!ifndef) : 51 occurrences #!endif : 51 occurrences |
> Is there a problem with the parser or a compatibility problem (i am on 
> *5.6.3*) ?
> |#!KAMAILIO # #!define WITH_MYSQL #!define WITH_AUTH #!define
> WITH_USRLOCDB #!define WITH_TLS #!define WITH_HOMER #!define
> WITH_WEBSOCKETS #!define WITH_ANTIFLOOD #!define WITH_IPV6 ##!define
> WITH_BRIDGE_ON_FAIL #!define WITH_LOCALHOST_WS ##!define
> WITH_LOCALHOST_SIP #!substdef "!MY_SIP_PORT!5060!g" #!substdef
> "!MY_SIPS_PORT!5061!g" #!substdef "!MY_WS_PORT!8080!g" #!substdef
> "!MY_WSS_PORT!4443!g" #!substdef "!MY_IP4_ADDR!X-X!g"
> #!substdef "!IP4_LOCALHOST!127.0.0.1!g" #!substdef
> "!MY_WS4_ADDR!tcp:MY_IP4_ADDR:MY_WS_PORT!g" #!substdef
> "!MY_WSS4_ADDR!tls:MY_IP4_ADDR:MY_WSS_PORT!g" #!substdef
> "!LOCALHOST_WS4_ADDR!tcp:IP4_LOCALHOST:MY_WS_PORT!g" #!substdef
> "!LOCALHOST_WSS4_ADDR!tls:IP4_LOCALHOST:MY_WSS_PORT!g" #!ifdef
> WITH_IPV6 #!substdef "!MY_IP6_ADDR![XX-XX]!g" #!substdef
> "!IP6_LOCALHOST![::1]!g" #!substdef
> "!MY_WS6_ADDR!tcp:MY_IP6_ADDR:MY_WS_PORT!g" #!substdef
> "!MY_WSS6_ADDR!tls:MY_IP6_ADDR:MY_WSS_PORT!g" #!substdef
> "!LOCALHOST_WS6_ADDR!tcp:IP6_LOCALHOST:MY_WS_PORT!g" #!substdef
> "!LOCALHOST_WSS6_ADDR!tls:IP6_LOCALHOST:MY_WSS_PORT!g" #!endif
> #!substdef "!MY_DOMAIN!-!g" # *** Value defines - IDs used
> later in config #!ifdef WITH_MYSQL # - database URL - used to connect
> to database server by modules such # as: auth_db, acc, usrloc, a.s.o.
> #!ifndef DBURL #!define DBURL
> "mysql://kamailio:kamailiorw@localhost/kamailio" #!endif #!endif # -
> flags # FLT_ - per transaction (message) flags # FLB_ - per branch
> flags #!define FLT_NATS 5 #!define FLB_NATB 6 #!define FLB_NATSIPPING
> 7 #!define FLB_RTPWS 8 #!define FLB_IPV6 9 #!define FLB_V4V6 10
> #!define FLB_BRIDGE 11 ### Global Parameters # ### LOG
> Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG
> debug=4 log_stderror=no #!else debug=2 log_stderror=no #!endif
> memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4
> port=MY_SIP_PORT tls_port_no=MY_SIPS_PORT #!ifdef WITH_TLS
> enable_tls=yes #!endif listen=MY_IP4_ADDR #!ifdef WITH_LOCALHOST_SIP
> listen=IP4_LOCALHOST #!endif #!ifdef WITH_IPV6 listen=MY_IP6_ADDR
> #!ifdef WITH_LOCALHOST_SIP listen=IP6_LOCALHOST #!endif #!endif
> #!ifdef WITH_WEBSOCKETS listen=MY_WS4_ADDR #!ifdef WITH_LOCALHOST_WS
> listen=LOCALHOST_WS4_ADDR #!endif #!ifdef WITH_IPV6 listen=MY_WS6_ADDR
> #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WS6_ADDR #!endif #!endif
> #!ifdef WITH_TLS listen=MY_WSS4_ADDR #!ifdef WITH_LOCALHOST_WS
> listen=LOCALHOST_WSS4_ADDR #!endif #!ifdef WITH_IPV6
> listen=MY_WSS6_ADDR #!ifdef WITH_LOCALHOST_WS
> listen=LOCALHOST_WSS6_ADDR #!endif #!endif #!endif #!endif
> use_dns_cache = on # Use KAMAILIO internal DNS cache use_dns_failover
> = on # Depends on KAMAILIO internal DNS cache dns_srv_loadbalancing =
> on # dns_try_naptr = on # dns_retr_time=1 # Time in seconds before
> retrying a DNS request dns_retr_no=3 # Number of DNS retransmissions
> before giving up # Set protocol preference order - ignore target
> priority dns_naptr_ignore_rfc= yes # Ignore target NAPTR priority
> dns_tls_pref=50 # First priority: TLS dns_tcp_pref=30 # Second
> priority: TCP dns_udp_pref=10 # Third priority: UDP
> tcp_connection_lifetime=3604 tcp_accept_no_cl=yes
> tcp_rd_buf_size=16384 # set paths to location of modules (to sources
> or installation folders) #!ifdef WITH_SRCPATH mpath="modules/" #!else
> mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" #!endif #!ifdef
> WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "kex.so"
> loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so"
> loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule
> "maxfwd.so" loadmodule "usrloc.so" loadmodule 

[SR-Users] Maintenance work overnight on kamailio.org server

[Daniel-Constantin Mierla via sr-users]

Hello,

there is some planned work on the data center infrastructure hosting
kamailio.org server that is going to affect briefly the web server (web
site, wiki) and the mailing lists.

The downtime is expected to be 10-15 minutes around 1:00am Western
Europe time (CEST / GMT+2), but if it takes longer or repeats, be
patient for a while.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Updating $fn malforms packet.

[Daniel-Constantin Mierla via sr-users]

Hello,

On 09.04.24 15:37, James Lipski via sr-users wrote:
>
>
> Hello,
>
> I have remote users registering/ routing calls through my server. When
> calls do pass through the server, the server updates the from name, to
> uri and from uri via updating the pseudovariables $fn, $tu, and $fu
> respectively. While this is has been working, I do occasionally see
> calls failing to process as the remote gateway fails the call with a
> "400 Bad From header". Inspecting the A-leg INVITE and the B-leg
> INVITE after updating the pseudovariables, I see the following:
>
> A-leg INVITE:
> INVITE sip:15551112...@example.com SIP/2.0
> Via: SIP/2.0/UDP
> 79..xx.xx.xx:61379;rport;branch=z9hG4bKPj2b8935f4460447538d0176dcfb5c74a1
> Max-Forwards: 70
> From: sip:12223334...@example.com;tag=dff3c585a6154f23898e1121918f1752
> To: sip:15551112...@example.com
> Contact: 
> Call-ID: d793331e066f47bdafc0ad957cb506cc
> CSeq: 30770 INVITE
> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
> NOTIFY, REFER, MESSAGE, OPTIONS
> Supported: replaces, 100rel, timer, norefersub
> Session-Expires: 1800
> Min-SE: 90
> Proxy-Authorization: Digest username="1222333", realm="example.com
> ", nonce="ZhUw02YVL6cdi51KMymTxGpzCZCZhd8G",
> uri="sip:15551112...@example.com ",
> response="3a25b4ea0b1154e31caee1184a92f12b"
> Content-Type: application/sdp
> Content-Length:   627
>
> v=0
> o=- 3921660487 3921660487 IN IP4 79..xx.xx.xx
> s=pjmedia
> b=AS:84
> t=0 0
> a=X-nat:0
> m=audio 4006 RTP/AVP 96 97 98 99 3 0 8 9 120 121 122
> c=IN IP4 79..xx.xx.xx
> b=TIAS:64000
> a=rtcp:4007 IN IP4 79..xx.xx.xx
> a=sendrecv
> a=rtpmap:96 speex/16000
> a=rtpmap:97 speex/8000
> a=rtpmap:98 speex/32000
> a=rtpmap:99 iLBC/8000
> a=fmtp:99 mode=30
> a=rtpmap:3 GSM/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:9 G722/8000
> a=rtpmap:120 telephone-event/16000
> a=fmtp:120 0-16
> a=rtpmap:121 telephone-event/8000
> a=fmtp:121 0-16
> a=rtpmap:122 telephone-event/32000
> a=fmtp:122 0-16
> a=ssrc:63772004 cname:3ff849bd611036a7
>
>
>
> --
> B-leg INVITE:
> INVITE sip:15551112...@togateway.com SIP/2.0
> Record-Route:
> 
> Via: SIP/2.0/UDP
> 10.64.54.207:5060;branch=z9hG4bK919d.5ca83e030c0879093169546cd80591a6.0
> Via: SIP/2.0/UDP
> 79..xx.xx.xx:61379;received=79..xx.xx.xx;rport=61379;branch=z9hG4bKPj2b8935f4460447538d0176dcfb5c74a1
> Max-Forwards: 15
> From: sip:12125557...@example.com"Updated Name"
> ;tag=dff3c585a6154f23898e1121918f1752
> To: sip:15551112...@togateway.com
> Contact: 
> Call-ID: d793331e066f47bdafc0ad957cb506cc
> CSeq: 30770 INVITE
> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
> NOTIFY, REFER, MESSAGE, OPTIONS
> Supported: replaces, 100rel, timer, norefersub
> Session-Expires: 1800
> Min-SE: 90
> Content-Type: application/sdp
> Content-Length:   609
>
> v=0
> o=- 3921660487 3921660487 IN IP4 10.64.54.207
> s=pjmedia
> b=AS:84
> t=0 0
> a=X-nat:0
> m=audio 18400 RTP/AVP 96 97 98 99 3 0 8 9 120 121 122
> c=IN IP4 10.64.54.207
> b=TIAS:64000
> a=ssrc:63772004 cname:3ff849bd611036a7
> a=rtpmap:96 speex/16000
> a=rtpmap:97 speex/8000
> a=rtpmap:98 speex/32000
> a=rtpmap:99 iLBC/8000
> a=fmtp:99 mode=30
> a=rtpmap:3 GSM/8000
> a=rtpmap:0 PCMU/8000
> a=rtpmap:8 PCMA/8000
> a=rtpmap:9 G722/8000
> a=rtpmap:120 telephone-event/16000
> a=fmtp:120 0-16
> a=rtpmap:121 telephone-event/8000
> a=fmtp:121 0-16
> a=rtpmap:122 telephone-event/32000
> a=fmtp:122 0-16
> a=sendrecv
> a=rtcp:18401
>
> Note that I've updated the following on the B-leg:
>
> $fn = "Updated Name" // originally nothing
> $fu = sip:12125557...@example.com // originally
> sip:12223334...@example.com
> $tu = sip:15551112...@togateway.com // originally
> sip:15551112...@example.com
>
>
> While the from uri, and to uri do get updated, the from name is
> injected in the wrong place of the from header. This only seems to
> happen when the A-leg is missing the "<" and ">" characters enclosing
> the from headers.
>
> Should I not be updating the pseudo variables in this manner to update
> the from name, to uri and from uri; is there another way to update
> these attributes of the header without malforming it?

looks like a bug, you can open an issue on the tracker.

On the other hand, updating directly with variables the To/From
attributes is somehow unsafe overall, the option to do it so was made
more for testing or particular use cases. It is recommended to use the
uac module and its functions uac_replace_from()/_to() for this purpose.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the 

[SR-Users] Re: Kamailio Admin Book email

[Daniel-Constantin Mierla via sr-users]

Hello,

as you can see on the page with the form for requesting to purchase the
book, incomplete requests are not making it through:

"The requests with invalid or incomplete values for the required fields
are ignored."

Searching over the discarded requests, the provided address in your
message is incomplete. Those details are required by Eu/German laws for
invoice and income taxes.

Cheers,
Daniel

On 07.04.24 23:15, sadik.oualla.mohamed--- via sr-users wrote:
> Hello,
>
> Last week, I submitted a request on the Asipto website to purchase the 
> Kamailio Admin Book and received an automatic confirmation email. However, I 
> have not received any further instructions on how to complete the purchase. I 
> replied to the automatic email to follow up, but still, there has been no 
> response. I need to get the book as soon as possible.
>
> Please note, I am writing from a different email address than the one I used 
> to make the request on Asipto's site. If there are any issues with their 
> contact email, or if further verification is needed, please let me know how 
> to proceed securely without sharing personal details publicly on this list.
>
> Regards,
> Mohamed.
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.8.1 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.8.1 stable release is out.

This is a maintenance release of the latest stable branch, 5.8, that
includes fixes since the release of v5.8.0. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.8.x. Deployments running previous v5.8.x
versions are strongly recommended to be upgraded to v5.8.1.

For more details about version 5.8.1 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/04/kamailio-v5-8-1-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.8.1

[Daniel-Constantin Mierla via sr-users]

Hello,

short reminder that today is planned to release v5.8.1. As usual, until
the announcement is out, any commit that should go to branch 5.8 has to
be announced to sr-dev mailing list and wait for ack before pushing to
git repository in order to avoid conflicts with release building process.

Cheers,
Daniel

On 26.03.24 12:01, Daniel-Constantin Mierla wrote:
> Hello,
>
> with many countries having public holidays around Catholic Easter, I am
> considering to release Kamailio v5.8.1 (out of branch 5.8) on Wednesday,
> April 3, 2024. If anyone is aware of issues not yet on the bug tracker,
> report them there asap in order to have a better chance to be fixed.
>
> Cheers,
> Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.8.1

[Daniel-Constantin Mierla via sr-users]

Hello,

with many countries having public holidays around Catholic Easter, I am
considering to release Kamailio v5.8.1 (out of branch 5.8) on Wednesday,
April 3, 2024. If anyone is aware of issues not yet on the bug tracker,
report them there asap in order to have a better chance to be fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: RFC5626 Keep-Alive with CRLF

[Daniel-Constantin Mierla via sr-users]

Hello,

there is the core option:

  - https://www.kamailio.org/wikidocs/cookbooks/5.8.x/core/#tcp_crlf_ping

But I guess is the client that sends crlfcrlf and the server sends back
crlf.

Cheers,
Daniel

On 21.03.24 16:26, Ihor Olkhovskyi via sr-users wrote:
> Just to add a bit for an issue:
>
> On a mobile client, Linphone in particular, system may be in state,
> that it "believes", that TCP connection still exists, but on a server
> (Kamailio) side it's already closed by tcp_keepalive_enable() option. 
> As I got, RST is not reaching mobile device (which is ok, I assume, in
> a mobile world).
>
> But device due to "internal believes" sending the packets via already
> dead TCP connection and as a result, on outgoing call I'm getting 408
> - Timeout.
> Linphone developers suggested to use this CRLF method for keepalive,
> so I'm asking after finding traces of this RFC only in outbound module.
>
> P.S.: I know, keepalive on TCP and mobile world is usually a bad idea,
> but maybe it's better in general than SIP OPTIONS ping. From my point
> of view, TCP stack state should be enough already, but reality is reality
>
> Le jeu. 21 mars 2024 à 16:18, Ihor Olkhovskyi
>  a écrit :
>
> Julien,
>
> Yes, I did. It just invokes setsockopt() from system library  -
> https://linux.die.net/man/3/setsockopt
>
> This one is a bit different.
>
> Le jeu. 21 mars 2024 à 14:29, Julien Chavanton
>  a écrit :
>
> Did you look at the tcpops module.
>
> I am sometimes getting confused but I think this is the one
> made by the kernel and it is simply a socket option flag.
>
> On Thu, Mar 21, 2024, 6:14 AM Ihor Olkhovskyi via sr-users
>  wrote:
>
> Hello,
>
> A bit generic question, does Kamailio supports CRLF
> keepalive per
> https://www.rfc-editor.org/rfc/rfc5626#section-4.4.1 ?
> It's more for tracking TCP connection states, as seems
> tcp_keepalive_enable is not super reliable especially in
> mobile networks.
>
> -- 
> Best regards,
> Ihor (Igor)
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to
> sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not
> reply only to the sender!
> Edit mailing list options or unsubscribe:
>
>
>
> -- 
> Best regards,
> Ihor (Igor)
>
>
>
> -- 
> Best regards,
> Ihor (Igor)
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Wrong documentation for module 'Userblacklist'

[Daniel-Constantin Mierla via sr-users]

Hello,

the module userblacklist has been renamed to userblocklist a while ago,
but the html index for modules' documentation was forgotten to be
updated. I just did it.

Look at the documentation for userblocklist module and if something is
not working, report an issue on the tracker.

  - https://www.kamailio.org/docs/modules/stable/modules/userblocklist.html

Cheers,
Daniel

On 20.03.24 11:37, Björn Klasen via sr-users wrote:
> Hi everybody,
>
> I'm a little bit confused about the documentation of the Userblacklist
> module as I think it has to be Userblocklist since version 5.x. Also
> some of the commands and some column names in the database have changed.
> I can remember that the documentation was right at some point, but the
> it has been changed back to Userblacklist. I wonder if nobody noticed
> that because the old commands do not work.
>
> BR, Björn
>
> -- 
> Björn Klasen, Senior Specialist (VoIP)
> TNG Stadtnetz GmbH, TNG-Technik
> Gerhard-Fröhler-Straße 12
> 24106 Kiel・Deutschland
>
> T +49 431 7097-10
> F +49 431 7097-555
> bkla...@tng.de
> https://www.tng.de
>
> Executive board (Geschäftsführer):
> Dr. Sven Willert (CEO/Vorsitz),
> Gunnar Peter, Sven Schade,
> Carsten Tolkmit, Bernd Sontheimer
>
> Amtsgericht Kiel HRB 6002 KI
> USt-ID: DE225201428
> Die Information über die Verarbeitung Ihrer Daten
> gemäß Artikel 12 DSGVO können Sie unter
> https://www.tng.de/datenschutz/ abrufen.
> __
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only
> to the sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Bug in htable in 5.8.0

[Daniel-Constantin Mierla via sr-users]

Hello,

I pushed a commit to ctl module in master branch trying to address this
issue. Can you test and report if works ok now? If yes, then I will
backport.

Cheers,
Daniel

On 16.03.24 12:22, Patrick Karton via sr-users wrote:
> Same bug in 5.7. versions
>
> Le 15 mars 2024 15:08, Brooks Bridges via sr-users
>  a écrit :
>
> Thanks Daniel, I’ll give that a try.
>
>  
>
>  
> Brooks Bridges
> Sr. Developer
>
>   
>
> ​Direct: (888) 444‑
> Office: (561) 453‑4085
> Email: bbrid...@skyetel.com
>   
> 902 Clint Moore Road
> ​Suite 206
> ​Boca Raton, FL 33487
> www.skyetel.com 
>
> *From:* Daniel-Constantin Mierla 
> *Sent:* Thursday, March 14, 2024 23:16
> *To:* Kamailio (SER) - Users Mailing List
> 
> *Cc:* Brooks Bridges 
> *Subject:* Re: [SR-Users] Bug in htable in 5.8.0
>
>  
>
> Hello,
>
> On 15.03.24 00:15, Brooks Bridges via sr-users wrote:
>
> We have some scripts that are setting values in an htable for
> various things, one of which is to disable options replies to
> take a system “out of service”.  We discovered today upon
> deploying 5.8.0 that the “htable.seti” command appears to be
> broken.
>
>  
>
> [root@ip-10-52-42-102 ~]# kamcmd htable.seti system_settings
> option_pings_off 1
>
> error: 500 - Not enough parameters (htable name, key name and
> value)
>
>  
>
> however if we do htable.sets it works fine (although not an
> integer so it’s breaking our shutdown scripts).
>
>  
>
> [root@ip-10-52-42-102 ~]# kamcmd htable.sets system_settings
> option_pings_off 1
>
> Ok. Key set to new value.
>
> [root@ip-10-52-42-102 ~]#
>
>  
>
> I’ve looked through the commit history for htable and haven’t
> found anything that really stands out as a possible issue, so
> can the gurus please take a look?
>
> the problem should be with kamcmd+ctl, not htable, use kamctl (or
> kamcli) instead:
>
> kamctl rpc htable.seti system_settings option_pings_off 1
>
> (kamcli rpc htable.seti system_settings option_pings_off 1)
>
> I will look into kamcmd/ctl, likely is related to conversion of
> values, many fields are now long instead of int and kamcmd is not
> much maintained, it uses a custom (undocumented) binary-rpc
> protocol and none of its original developers is active.
>
> Cheers,
> Daniel
>
> -- 
>
> Daniel-Constantin Mierla (@ asipto.com)
>
> twitter.com/miconda -- linkedin.com/in/miconda
>
> Kamailio Consultancy, Training and Development Services -- asipto.com
>
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
>
> Confidentiality Notice: This e-mail, and any attachment to it,
> contains privileged and confidential information intended only for
> the use of the individual(s) or entity named on the e-mail. If the
> reader of this e-mail is not the intended recipient, or the
> employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that reading this e-mail is
> strictly prohibited. If you have received this e-mail in error,
> please immediately return it to the sender and delete it from your
> system.
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Bug in htable in 5.8.0

[Daniel-Constantin Mierla via sr-users]

Hello,

On 15.03.24 00:15, Brooks Bridges via sr-users wrote:
>
> We have some scripts that are setting values in an htable for various
> things, one of which is to disable options replies to take a system
> “out of service”.  We discovered today upon deploying 5.8.0 that the
> “htable.seti” command appears to be broken.
>
>  
>
> [root@ip-10-52-42-102 ~]# kamcmd htable.seti system_settings
> option_pings_off 1
>
> error: 500 - Not enough parameters (htable name, key name and value)
>
>  
>
> however if we do htable.sets it works fine (although not an integer so
> it’s breaking our shutdown scripts).
>
>  
>
> [root@ip-10-52-42-102 ~]# kamcmd htable.sets system_settings
> option_pings_off 1
>
> Ok. Key set to new value.
>
> [root@ip-10-52-42-102 ~]#
>
>  
>
> I’ve looked through the commit history for htable and haven’t found
> anything that really stands out as a possible issue, so can the gurus
> please take a look?
>
the problem should be with kamcmd+ctl, not htable, use kamctl (or
kamcli) instead:

kamctl rpc htable.seti system_settings option_pings_off 1

(kamcli rpc htable.seti system_settings option_pings_off 1)

I will look into kamcmd/ctl, likely is related to conversion of values,
many fields are now long instead of int and kamcmd is not much
maintained, it uses a custom (undocumented) binary-rpc protocol and none
of its original developers is active.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: append_hf not working

[Daniel-Constantin Mierla via sr-users]

Hello,

append_to_reply() adds the header to the replies generated by Kamailio.
A request that is generated by UA after a 3xx does not have to preserve
any header received in 3xx, it is a completely new request, the previous
one failed. If you handle the 3xx in Kamailio, you can get the headers
of the reply in failure route via T_rpl(...) and add them to the request.

Cheers,
Daniel

On 13.03.24 17:16, Calvin E. via sr-users wrote:
> According to a packet capture, changing append_hf() to
> append_to_reply() affected a 302 message that Kamailio is forwarding
> to sending to itself, but the subsequent INVITE did not keep the
> header. What am I missing?
>
> On Mon, Mar 11, 2024 at 7:28 AM Ben Kaufman via sr-users
>  wrote:
>> There's also the question of when the header was appended as well, right?  
>> Calling append_hf() after creating a transaction will only apply that header 
>> to the current branch, not to subsequent branches.
>>
>>
>> -Original Message-
>> From: James Browne via sr-users 
>> Sent: Monday, March 11, 2024 7:03 AM
>> To: Kamailio (SER) - Users Mailing List 
>> Cc: James Browne 
>> Subject: [SR-Users] Re: append_hf not working
>>
>> CAUTION: This email originated from outside the organization. Do not click 
>> links or open attachments unless you recognize the sender and know the 
>> content is safe.
>>
>>
>> One pitfall would be to think that this function would add this header field 
>> to any reply that kamailio would send. This append_hf() function should add 
>> a header field to a SIP request that it *relays*, but would not add it to a 
>> response that kamailio *generates* (for that, you would use the 
>> append_to_reply() function).
>>
>> James
>>
>> On Mon, 11 Mar 2024 at 11:26, Alex Balashov via sr-users 
>>  wrote:
>>> Indeed, it has become a bit of a cliché that msg_apply_changes() should be 
>>> called after append_hf(), uac_replace_from(), etc.
>>>
>>> This should be dispelled. In the vast majority of use-cases, it is not only 
>>> unnecessary, but highly undesirable.
>>>
>>> -- Alex
>>>
 On 11 Mar 2024, at 06:45, Henning Westerholt via sr-users 
  wrote:

 Hello,
  the usage of msg_apply_changes is not necessary (not even recommended) 
 for append_hf (and other functions) to work. The OP was talking about a 
 packet capture, so I assume that he got the capture after the proxy send 
 out the message.
  Cheers,
  Henning
   -- Henning Westerholt -
 https://sk/
 alatan.de%2Fblog%2F=05%7C02%7Cbkaufman%40bcmone.com%7Cb9eabef23
 1974f061db008dc41c47c6b%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7
 C638457559371077852%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
 IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=IUKBac
 HQspO1gtJ5B3ZULUOt6oAJKaTMBWM6R%2FDiq1Y%3D=0
 Kamailio services - https://gilawa.com/
   From: Unai Rodriguez via sr-users 
 Sent: Montag, 11. März 2024 09:33
 To: Calvin E. via sr-users ; Kamailio
 (SER) - Users Mailing List 
 Cc: Unai Rodriguez 
 Subject: [SR-Users] Re: append_hf not working  Using
 https://kamailio.org/docs/modules/stable/modules/textopsx.html#textopsx.f.msg_apply_changes
  might be relevant in your case...
  With best wishes, Unai Rodriguez
 On 11 Mar 2024 at 09:22 +0100, Benoit Panizzon via sr-users 
 , wrote:

 Hi Calvin


 I'm trying to add something simple like the following:

 append_hf("X-testheader: True\r\n", "From");

 However, I don't see my X-testheader in a packet capture. Are there
 any common pitfalls that would prevent append_hf from working as
 expected?

 Weird, I use this a lot and it always works. But I never attempted
 to specify the header after which it should be appended. Does it
 work if you don't specifiy "From"?

 Mit freundlichen Grüssen

 -Benoît Panizzon-
 --
 I m p r o W a r e A G - Leiter Commerce Kunden
 __

 Zurlindenstrasse 29 Tel +41 61 826 93 00
 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web
 http://www/
 .imp.ch%2F=05%7C02%7Cbkaufman%40bcmone.com%7Cb9eabef231974f061d
 b008dc41c47c6b%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C63845755
 9371097127%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM
 zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=fOFt%2BsXu%2FDg
 3EeKqhoRlybWURiVXfz%2B0Di8aSYFWxvQ%3D=0
 __
 __
 Kamailio - Users Mailing List - Non Commercial Discussions To
 unsubscribe send an email to sr-users-le...@lists.kamailio.org
 Important: keep the mailing list in the recipients, do not reply only to 
 the sender!
 Edit mailing list options or unsubscribe:
 __
 Kamailio - Users Mailing List 

[SR-Users] Re: 5.8 acc module failed_filter error

[Daniel-Constantin Mierla via sr-users]

On 12.03.24 03:13, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> It might be a regression by commit 675f6c02248, can you try with latest
>> master or with the patch of the commit:
>>
>>   -
>> https://github.com/kamailio/kamailio/commit/4dc37aee853bbcf9d7fdb96245b76aaa8dfa2930
> I tried with latest master and it started OK.  Pretty serious stuff.
> Perhaps a new tag 5.8.1 is needed.

It will be a 5.8.1 soon, but we have to wait and see what else it pops
up, usually after a .0 release, a bunch of things need tuning, releasing
after each commit is not feasible. We also have nightly builds for
debian/ubuntu and source installation should use the branch 5.8, not tags.

On the other hand, it might not be as bad as it seems, it is only for
startup and only when the a previous modparam (or some other operation)
frees a chunk that can be reused by next one. Also, it affects only
PARAM_STRING, not PARAM_STR. That's the reason it was not discovered by
testing with the default config file or other configs (at least I run
master in a testing environment with many more modules loaded than
default kamailio.cfg) -- the regression is rather old, from June 2023.
The main docker-based tests were also ok.

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: 5.8 acc module failed_filter error

[Daniel-Constantin Mierla via sr-users]

On 11.03.24 20:45, Juha Heinanen via sr-users wrote:
> Daniel-Constantin Mierla writes:
>
>> what are the operating system and the compiler used?
> Sorry, Debian 12 using gcc version 12.2.0.

It might be a regression by commit 675f6c02248, can you try with latest
master or with the patch of the commit:

  -
https://github.com/kamailio/kamailio/commit/4dc37aee853bbcf9d7fdb96245b76aaa8dfa2930

If it works, then you can go ahead and backport to 5.8 branch.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: 5.8 acc module failed_filter error

[Daniel-Constantin Mierla via sr-users]

Hello,

what are the operating system and the compiler used?

Cheers,
Daniel

On 11.03.24 07:45, Juha Heinanen via sr-users wrote:
> My SIP proxy didn't start with Kamailio 5.8 using the same config that
> starts OK with 5.7.  The error is:
>
> 2024-03-11T06:56:06.457107+02:00 lohi /usr/bin/sip-proxy[2358954]: DEBUG: acc 
> [acc_mod.c:362]: parse_failed_filter(): failed_filter 0 = 407
> 2024-03-11T06:56:06.457265+02:00 lohi /usr/bin/sip-proxy[2358954]: ERROR: acc 
> [acc_mod.c:369]: parse_failed_filter(): response code is not followed by 
> comma or end of string
> 2024-03-11T06:56:06.457436+02:00 lohi /usr/bin/sip-proxy[2358954]: ERROR: acc 
> [acc_mod.c:439]: mod_init(): failed to parse failed_filter param
>
> The relevant params are:
>
> modparam("acc", "failed_transaction_flag", 8)
> modparam("acc", "failed_filter", "407")
>
> I didn't find any difference in acc_mod.c source code between 5.7 and
> 5.8 and parse_failed_filter function looked OK.
>
> Then I added a debug statement in the beginning of parse_failed_filter
> function:
>
>   LM_DBG("parsing failed_filter %s\n", s);
>
> and got to syslog:
>
> cc_mod.c:341]: parse_failed_filter(): parsing failed_filter 
> 407rmissions|pua|rtpengine)$
>
> That explains the parse_failed_filter error, but where does that bogus
> param value come from?
>
> Before acc params I have:
>
> modparam("auth_db|dialplan|domain|htable|lcr|msilo|mtree|permissions|pua|rtpengine",
>  "db_url", "mysql:///sip_proxy")
> modparam("registrar|nathelper", "received_avp", "$avp(received_uri)")
>
> So it from there, but why?  Is there a bug somewhere or is my SIP proxy
> running out of memory or something?  Before the above error messages,
> there are no other error messages.
>
> -- Juha
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: from TCP to UDP and Kamailio doing it wrong

[Daniel-Constantin Mierla via sr-users]

Hello,

check your config if the mtu-related parameters are set:

  - https://www.kamailio.org/wikidocs/cookbooks/5.7.x/core/#udp_mtu

Be sure you grep all the files if the config is split in many.

There is also a function that could result in switching protocols:
 
  -
https://www.kamailio.org/wikidocs/cookbooks/5.7.x/core/#udp_mtu_try_protoproto

Cheers,
Daniel

On 08.03.24 12:01, Alberto Diez via sr-users wrote:
> Hi Henning,
>
> yes as soon as I solve it I will try to give you a config and a sipp
> script that shows you the issue. It seems its in the function 
> build_req_buf_from_sip_req (modules/tm/msg_translator.c)  that if you
> have a flag in the message that says FL_TCP_MTU_FB and your message is
> larger than a given MTU for UDP that you can define in the core config
> it will change you to TCP even if you have used t_relay_to_udp  so I
> am trying to find out why my message has that flag and what's the
> value of that MTU parameter etc.
>
> I just explain it here so that in the future someone else has the
> problem kamilio all of a sudden deciding TCP when it should have been
> UDP, maybe its because of this flag, config parameter and crazy
> behavior (if I would have used t_relay maybe not so crazy but I used
> t_relay_to_udp explicitly... so quite crazy that instead of returning
> an error or something it tries TCP).
>
> Best regards
>
> alberto
>
> El 08/03/2024 a las 11:38, Henning Westerholt escribió:
>> Hello,
>>
>> this sound indeed strange, as this is used from many people without
>> any problems. Its not expected to use C programming to alter the
>> message transport for relaying.
>>
>> If you can reproduce and minimize the problem towards a small test
>> cfg and a test message, it would be great if you could open an issue
>> in our tracker.
>>
>> Cheers,
>>
>> Henning
>>
>>> -Original Message-
>>> From: Alberto Diez via sr-users 
>>> Sent: Freitag, 8. März 2024 10:28
>>> To: sr-users@lists.kamailio.org
>>> Cc: Alberto Diez 
>>> Subject: [SR-Users] Re: from TCP to UDP and Kamailio doing it wrong
>>>
>>> thanks Alex. Sadly in my case the Request-URI does not contain a
>>> transport
>>> parameter.
>>>
>>> So the call to prepare_new_uac() function is deciding based on another
>>> parameter (don't know which, was trying to avoid investigating that
>>> because
>>> the function is a pain and not commented). I think its quite
>>> counter-intuitive,
>>> and for me a bug, that you call t_relay_to_udp and Kamailio tries to
>>> connect
>>> over TCP  Same if its dispatcher module asking to dispatch to
>>> UDP and
>>> t_relay decides TCP (because it calls this same function at the end)
>>> etc.
>>>
>>> By the way I also tried forcing the socket from the config file to
>>> be the UDP
>>> one, and nothing. Prior to calling prepare_new_uac the socket is the
>>> UDP one,
>>> but after calling that function it has changed the socket to a TCP one.
>>>
>>> Would be great if anyone has a hint what could be going on and why
>>> prepare_new_uac changes the socket and based on what param
>>>
>>> Best regards
>>>
>>> alberto
>>>
>>> El 07/03/2024 a las 21:44, Alex Balashov via sr-users escribió:
 If you just strip the incoming ;transport=tcp attribute, I think
 all should be
>>> well when t_relay() consumes the modified RURI.
> On 7 Mar 2024, at 12:48, Alberto Diez via sr-users >> us...@lists.kamailio.org> wrote:
> Hi Sergiu,
> yes I am pretty sure something is going wrong.
> I do have kamailio listening udp sockets and also the dispatcher
> is on UDP
>>> doing SIP OPTIONS over UDP all the time without any problem.
> I have not tried forcing the socket I tried to find out why
> kamailio is trying to
>>> use TCP with the targets even when I use t_relay_to_udp and that's
>>> how I
>>> ended up finding that function which claims not to do something if
>>> next_hop
>>> is 0 but doing it nevertheless (which I guess is something going
>>> wrong in
>>> general in Kamailio not in particular in my setup).
> I will try forcing the socket, but that crazy tm module function
> rewrites the socket was already given as a destination (yes I already
> checked that in the C code before!) Best regards alberto El
> 07/03/2024 a las 17:43, Sergiu Pojoga escribió:
>> You must be doing something essentially wrong if it came down to
>>> checking C functions for something as trivial as transport conversion..
>> Are you sure you have a UDP listening socket?
>> kamcmd corex.list_sockets
>>
>> Result of:
>> kamcmd dispatcher.list
>>
>> Have you tried forcing the send socket?
>> https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#fs_-_f
>> orced_send_socket
>>
>> Cheers
>>
>> On Thu, Mar 7, 2024 at 11:27 AM Alberto Diez via sr-users >> us...@lists.kamailio.org> wrote:
>> Hi kamailio community,
>>
>> I have an issue with a Kamailio 5.7. It's listening both in TCP and
>> UDP.  In my scenario 

[SR-Users] Kamailio v5.8.0 Released - new major version is out

[Daniel-Constantin Mierla via sr-users]

Kamailio v5.8.0 is out – it comes with 4 new modules and a large set of
improvements touching again more than 50 existing modules.

You can read a bit more detailed release notes at:

   * https://www.kamailio.org/w/kamailio-v5-8-0-release-notes/

Many thanks to all developers and community members that made possible
this release.

v5.8.0 brings more flexibility and optimizations across many existing
components and modules, new parameters, functions, variables and
transformations.

Enjoy Kamailio v5.8.0!

Thank you for flying Kamailio!
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

short notification that v5.8.0 is going to be released today, therefore
any commits to branch 5.8 have to be announced to sr-dev and wait for
the ack before pushing to git repository in order to avoid conflicts
with the release building process. Once the announcement is out, commits
can be pushed to branch 5.8 as usual.

Cheers,
Daniel

On 06.03.24 07:56, Daniel-Constantin Mierla wrote:
> Hello,
>
> with still some docs to be updated for v5.8.0, the plan is to get the
> new version out tomorrow, March 7, 2024.
>
> Cheers,
> Daniel
>
> On 27.02.24 16:49, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> I propose to aim to get out 5.8.0 next week on Wednesday or Thursday
>> (March 6 or 7, 2024). I haven't seen much activity around issues in the
>> new features/modules. If time allows to build the pages for what-is-new
>> and how-to-upgrade (which I think it should be rather minimal), then I
>> think it should be no other major task. Overall it will be almost two
>> weeks since the 5.8 branch was created.
>>
>> Cheers,
>> Daniel
>>
>> On 23.02.24 12:11, Daniel-Constantin Mierla wrote:
>>> Hello,
>>>
>>> quick note that later today I will create the branch 5.8, notification
>>> emails will be sent once done.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 16.02.24 08:01, Daniel-Constantin Mierla wrote:
 Hello,

 hopefully the devel version is now more stabilized after the freezing,
 the new components being adjusted enough not to need many more changes.
 Therefore I consider to branch 5.8 out of devel version next week on
 Friday, February 23, 2024, sometime around noon UTC.

 After that the master branch becomes open for new features, and branch
 5.8 has to be hammered further to build the 5.8.x series.

 Cheers,
 Daniel

 On 10.01.24 10:11, Daniel-Constantin Mierla wrote:
> Hello,
>
> discussed a bit during the online Kamailio devel meeting, it is time to
> set the milestones towards the next major Kamailio release series v5.8.x.
>
> If no other suggestions that suit more developers, I would propose to
> freeze by end of this month or early February, then test for about 4
> weeks as usual and release by end of February or during March.
>
> If anyone wants to add new features/modules, they have to be published
> till freezing date, either pushed in the git repository or proposed as
> pull request.
>
> Cheers,
> Daniel
 -- 
 Daniel-Constantin Mierla (@ asipto.com)
 twitter.com/miconda -- linkedin.com/in/miconda
 Kamailio Consultancy, Training and Development Services -- asipto.com
 Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
 Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

>>> -- 
>>> Daniel-Constantin Mierla (@ asipto.com)
>>> twitter.com/miconda -- linkedin.com/in/miconda
>>> Kamailio Consultancy, Training and Development Services -- asipto.com
>>> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
>>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>>>
>> -- 
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda
>> Kamailio Consultancy, Training and Development Services -- asipto.com
>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

with still some docs to be updated for v5.8.0, the plan is to get the
new version out tomorrow, March 7, 2024.

Cheers,
Daniel

On 27.02.24 16:49, Daniel-Constantin Mierla wrote:
> Hello,
>
> I propose to aim to get out 5.8.0 next week on Wednesday or Thursday
> (March 6 or 7, 2024). I haven't seen much activity around issues in the
> new features/modules. If time allows to build the pages for what-is-new
> and how-to-upgrade (which I think it should be rather minimal), then I
> think it should be no other major task. Overall it will be almost two
> weeks since the 5.8 branch was created.
>
> Cheers,
> Daniel
>
> On 23.02.24 12:11, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> quick note that later today I will create the branch 5.8, notification
>> emails will be sent once done.
>>
>> Cheers,
>> Daniel
>>
>> On 16.02.24 08:01, Daniel-Constantin Mierla wrote:
>>> Hello,
>>>
>>> hopefully the devel version is now more stabilized after the freezing,
>>> the new components being adjusted enough not to need many more changes.
>>> Therefore I consider to branch 5.8 out of devel version next week on
>>> Friday, February 23, 2024, sometime around noon UTC.
>>>
>>> After that the master branch becomes open for new features, and branch
>>> 5.8 has to be hammered further to build the 5.8.x series.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 10.01.24 10:11, Daniel-Constantin Mierla wrote:
 Hello,

 discussed a bit during the online Kamailio devel meeting, it is time to
 set the milestones towards the next major Kamailio release series v5.8.x.

 If no other suggestions that suit more developers, I would propose to
 freeze by end of this month or early February, then test for about 4
 weeks as usual and release by end of February or during March.

 If anyone wants to add new features/modules, they have to be published
 till freezing date, either pushed in the git repository or proposed as
 pull request.

 Cheers,
 Daniel
>>> -- 
>>> Daniel-Constantin Mierla (@ asipto.com)
>>> twitter.com/miconda -- linkedin.com/in/miconda
>>> Kamailio Consultancy, Training and Development Services -- asipto.com
>>> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
>>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>>>
>> -- 
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda
>> Kamailio Consultancy, Training and Development Services -- asipto.com
>> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

I propose to aim to get out 5.8.0 next week on Wednesday or Thursday
(March 6 or 7, 2024). I haven't seen much activity around issues in the
new features/modules. If time allows to build the pages for what-is-new
and how-to-upgrade (which I think it should be rather minimal), then I
think it should be no other major task. Overall it will be almost two
weeks since the 5.8 branch was created.

Cheers,
Daniel

On 23.02.24 12:11, Daniel-Constantin Mierla wrote:
> Hello,
>
> quick note that later today I will create the branch 5.8, notification
> emails will be sent once done.
>
> Cheers,
> Daniel
>
> On 16.02.24 08:01, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> hopefully the devel version is now more stabilized after the freezing,
>> the new components being adjusted enough not to need many more changes.
>> Therefore I consider to branch 5.8 out of devel version next week on
>> Friday, February 23, 2024, sometime around noon UTC.
>>
>> After that the master branch becomes open for new features, and branch
>> 5.8 has to be hammered further to build the 5.8.x series.
>>
>> Cheers,
>> Daniel
>>
>> On 10.01.24 10:11, Daniel-Constantin Mierla wrote:
>>> Hello,
>>>
>>> discussed a bit during the online Kamailio devel meeting, it is time to
>>> set the milestones towards the next major Kamailio release series v5.8.x.
>>>
>>> If no other suggestions that suit more developers, I would propose to
>>> freeze by end of this month or early February, then test for about 4
>>> weeks as usual and release by end of February or during March.
>>>
>>> If anyone wants to add new features/modules, they have to be published
>>> till freezing date, either pushed in the git repository or proposed as
>>> pull request.
>>>
>>> Cheers,
>>> Daniel
>> -- 
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda
>> Kamailio Consultancy, Training and Development Services -- asipto.com
>> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
>> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Development is open for future release of v5.9.x series

[Daniel-Constantin Mierla via sr-users]

Hello,

the branch 5.8 was created, therefore the master branch is open for
adding new features, to be part of future release series v5.9.x (or
whatever version is decided for next series).

Any bug fix committed to master that applies to 5.8.x or older stable
branches should be backported as usual with "git cherry-pick -x ..." to
appropriate branches like 5.8 or 5.7.

Expect that v5.8.0 will be released in a few weeks from now.

Based on the workflow used during the past years, the next future
release v5.9.0 should be out after another 8-10 months of development,
plus 1-2 months of testing, so sometime during the last part of 2024 or
the beginning of 2025.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Branch 5.8 has been created

[Daniel-Constantin Mierla via sr-users]

Hello,

the branch 5.8 has been created, to be used for releasing v5.8.x series.

To check out this branch, the following commands can be used:

   git clone https://github.com/kamailio/kamailio kamailio-5.8
   cd kamailio-5.8
   git checkout -b 5.8 origin/5.8

Pushing commits in this branch:

  git push origin 5.8:5.8

Note that 5.8 is an official stable branch, so only bug fixes, missing
kemi exports (discuss on sr-dev if not sure) or improvements to
documentation or helper tools can be pushed to this branch.

As usual, if there is a bug fixed, commit and push first to master
branch and then cherry pick to 5.8 branch:

  git cherry-pick -x COMMITID

In few weeks, the first release from branch 5.8 will be out,
respectively Kamailio v5.8.0.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

quick note that later today I will create the branch 5.8, notification
emails will be sent once done.

Cheers,
Daniel

On 16.02.24 08:01, Daniel-Constantin Mierla wrote:
> Hello,
>
> hopefully the devel version is now more stabilized after the freezing,
> the new components being adjusted enough not to need many more changes.
> Therefore I consider to branch 5.8 out of devel version next week on
> Friday, February 23, 2024, sometime around noon UTC.
>
> After that the master branch becomes open for new features, and branch
> 5.8 has to be hammered further to build the 5.8.x series.
>
> Cheers,
> Daniel
>
> On 10.01.24 10:11, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> discussed a bit during the online Kamailio devel meeting, it is time to
>> set the milestones towards the next major Kamailio release series v5.8.x.
>>
>> If no other suggestions that suit more developers, I would propose to
>> freeze by end of this month or early February, then test for about 4
>> weeks as usual and release by end of February or during March.
>>
>> If anyone wants to add new features/modules, they have to be published
>> till freezing date, either pushed in the git repository or proposed as
>> pull request.
>>
>> Cheers,
>> Daniel
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: htable write access state

[Daniel-Constantin Mierla via sr-users]

Hello,

On 21.02.24 10:30, Patrick Karton via sr-users wrote:
> Hello are htable protected for  multiple write access? 
>
> can i safely update htable from one process and be sure another
> process will access it for write operation ? if yes is the lock on all
> the htable or only on the bucket where the key belongs ? 

yes, read and write are protected by a lock on the bucket where the key
is stored.


Only if you need to do a read, plus some other operations to update the
item and then write back, without letting other process to update the
item meanwhile, you need to do locking using the functions provided by
htable in this scope.


Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

hopefully the devel version is now more stabilized after the freezing,
the new components being adjusted enough not to need many more changes.
Therefore I consider to branch 5.8 out of devel version next week on
Friday, February 23, 2024, sometime around noon UTC.

After that the master branch becomes open for new features, and branch
5.8 has to be hammered further to build the 5.8.x series.

Cheers,
Daniel

On 10.01.24 10:11, Daniel-Constantin Mierla wrote:
> Hello,
>
> discussed a bit during the online Kamailio devel meeting, it is time to
> set the milestones towards the next major Kamailio release series v5.8.x.
>
> If no other suggestions that suit more developers, I would propose to
> freeze by end of this month or early February, then test for about 4
> weeks as usual and release by end of February or during March.
>
> If anyone wants to add new features/modules, they have to be published
> till freezing date, either pushed in the git repository or proposed as
> pull request.
>
> Cheers,
> Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Get the amount of open TCP connection from routing logic

[Daniel-Constantin Mierla via sr-users]

Hello,


there is a statistic value giving the active tcp connections (which
include the tls connections) and then you can get the value via
$stat(...) variable:


  -
https://www.kamailio.org/wikidocs/cookbooks/5.7.x/pseudovariables/#statname-statistics


I don't recall right now if the name of the stat is with its group id or
without, you have to try.


Cheers,
Daniel


On 06.02.24 12:02, Sebastian Damm via sr-users wrote:
> Hello,
>
> My plan is to reject new inbound requests if there is already a
> certain number of open connections on one Kamailio server. I could
> answer with a 503 and directly close the connection forcing the client
> to reconnect and the loadbalancer to send traffic to a different node
> on the next connect. It's just a last-resort measure to prevent
> Kamailio from running into the configured TCP connection limit
> (workarounding a poorly-implemented external load balancer).
>
> Since I didn't find anything in the docs: Is there a pseudovariable
> containing the current number of open tcp/tls connections on this
> Kamailio? I can (and already do) query them via kamcmd or rpc, but can
> I access the variable from inside the routing script as well?
>
> Regards,
> Sebastian
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Development for v5.8.x is frozen

[Daniel-Constantin Mierla via sr-users]

Hello,

the formal notification that the development for the next major version
5.8.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 5.8 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 5.8.

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 5.8.

Once the branch 5.8 is created, new features can be pushed again to
master branch as usual. From that moment, the v5.8.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 5.8 is going to be built at:

  * https://www.kamailio.org/wikidocs/features/new-in-5.8.x/

Upgrade guidelines will be collected at:

  * https://www.kamailio.org/wikidocs/install/upgrade/5.7.x-to-5.8.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.7.x to 5.8.x.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Freezing development for 5.8.x series

[Daniel-Constantin Mierla via sr-users]

Hello,

short reply to refresh on freezing plan and bump the message at the top
for everyone.

Cheers,
Daniel

On 30.01.24 08:16, Daniel-Constantin Mierla wrote:
> Hello,
>
> I propose to aim freezing the development for 5.8.x series at the end of
> the 1st of February 2024 (Thursday).
>
> 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 5.8.0.
> Unfreezing will happen earlier, after the first weeks of testing when
> the 5.8 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
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Freezing development for 5.8.x series

[Daniel-Constantin Mierla via sr-users]

Hello,

I propose to aim freezing the development for 5.8.x series at the end of
the 1st of February 2024 (Thursday).

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 5.8.0.
Unfreezing will happen earlier, after the first weeks of testing when
the 5.8 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
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: How to get media IP

[Daniel-Constantin Mierla via sr-users]

On 24.01.24 10:33, mm e via sr-users wrote:
> When receiving a call I get the following message：
>
> INVITE sip:123456789@192.168.1.118:29363 SIP/2.0
> Via: SIP/2.0/UDP 
> 192.168.1.118:65178;branch=z9hG4bK-d87543-4a4a6b6c49541b2c-1--d87543-;rport
> Max-Forwards: 70
> Contact: 
> To: "123456789"
> From: "96341";tag=af3c7c31
> Call-ID: OTFhN2M2YmRmNmU2N2I1ZmQxNmM4ODg4YzRiZmQyNTc.
> CSeq: 1 INVITE
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, 
> INFO
> Content-Type: application/sdp
> User-Agent: eyeBeam release 1011d stamp 40820
> Content-Length: 339
>
> v=0
> o=- 3 2 IN IP4 192.168.1.118
> s=CounterPath eyeBeam 1.5
> c=IN IP4 192.168.1.118
> t=0 0
> m=audio 32170 RTP/AVP 0 8 18 101
> a=alt:1 1 : +YhwgPgy ayLEx4wo 192.168.1.118 32170
> a=fmtp:18 annexb=no
> a=fmtp:101 0-15
> a=rtpmap:18 G729/8000
> a=rtpmap:101 telephone-event/8000
> a=sendrecv
>
> How to print the media IP in SDP separately in the log? I didn't find the 
> Pseudo-Variables..can you help me

For the records, I have just added $sdp(c:ip) to return media IP.

For current versions, as it was pointed in another response, you have to
leverage functions from sdpops, textops or textopsx and transformations
to extract the corresponding token from the sdp.

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

would it be possible to get the skeleton in the git repo or as PR for
the new module by end of the month? It is still a week and completing
missing parts can be done during the testing phase.

Cheers,
Daniel

On 23.01.24 10:13, Henning Westerholt wrote:
> Hello Daniel,
>
> we are working on a new module right now (related to special logging for high 
> CPS setups), which would be nice to integrate if possible. Its isolated, so 
> would not touch any other module and/or the core. There is also another core 
> refactoring in progress (to replace the atomic operations with the standard 
> Linux kernel support for better support of non-Intel/AMD architectures), but 
> this probably needs to wait to the next release cycle then.
>
> Best regards,
>
> Henning Westerholt
>
> -- 
> Henning Westerholt – https://skalatan.de/blog/
> Kamailio services – https://gilawa.com
>
>> -Original Message-
>> From: Daniel-Constantin Mierla 
>> Sent: Montag, 15. Januar 2024 11:33
>> To: Henning Westerholt ; Kamailio (SER) - Devel Mailing List
>> 
>> Cc: busin...@lists.kamailio.org; Kamailio (SER) - Users Mailing List > us...@lists.kamailio.org>
>> Subject: Re: [Kamailio-Business] Roadmap to next major Kamailio release
>> series v5.8.x
>>
>> Hello,
>>
>> first week of February is a semester school break in many regions, if someone
>> announces that he has ongoing work to a new module/feature, then freezing
>> can be postponed.
>>
>> But if not, I would rather do it earlier than waiting for nothing, because
>> starting later could end up in getting closer the Catholic Easter, which is 
>> earlier
>> this year, by end of March, a week before another holiday starts. Considering
>> the constraints on late March and April, if not out by mid of March or so, 
>> next
>> time frame will be end of April or during May.
>>
>> Cheers,
>> Daniel
>>
>> On 11.01.24 17:12, Henning Westerholt wrote:
>>> Hello,
>>>
>>> early February as a freezing date sounds good to me, just to have one full
>> month after the holiday season/vacation period to allow other people to 
>> finish
>> eventual contributions.
>>> Cheers,
>>>
>>> Henning
>>>
>>> --
>>> Henning Westerholt - https://skalatan.de/blog/ Kamailio services -
>>> https://gilawa.com
>>>
 -Original Message-
 From: Daniel-Constantin Mierla via business
 
 Sent: Mittwoch, 10. Januar 2024 10:11
 To: Kamailio (SER) - Users Mailing List
 ; Kamailio
 (SER) - Devel Mailing List ;
 busin...@lists.kamailio.org
 Subject: [Kamailio-Business] Roadmap to next major Kamailio release
 series v5.8.x

 Hello,

 discussed a bit during the online Kamailio devel meeting, it is time
 to set the milestones towards the next major Kamailio release series 
 v5.8.x.

 If no other suggestions that suit more developers, I would propose to
 freeze by end of this month or early February, then test for about 4
 weeks as usual and release by end of February or during March.

 If anyone wants to add new features/modules, they have to be
 published till freezing date, either pushed in the git repository or 
 proposed
>> as pull request.
 Cheers,
 Daniel

 --
 Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda --
 linkedin.com/in/miconda Kamailio Consultancy, Training and
 Development Services -- asipto.com Kamailio Advanced Training,
 February 20-22, 2024 -- asipto.com Kamailio World Conference, April
 18-19, 2024, Berlin -- kamailioworld.com

 ___
 Kamailio (OpenSER) - business mailing list --
 busin...@lists.kamailio.org To unsubscribe send an email to
 business-le...@lists.kamailio.org
 http://lists.openser-project.org/cgi-
 bin/mailman/listinfo%(cgiext)s/%(_internal_name)s
>> --
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy,
>> Training and Development Services -- asipto.com Kamailio Advanced Training,
>> February 20-22, 2024 -- asipto.com Kamailio World Conference, April 18-19,
>> 2024, Berlin -- kamailioworld.com

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Info: Kamailio World 2024 - Call for presentations

[Daniel-Constantin Mierla via sr-users]

Hi Julien,

yes, the submission was received!

Cheers,
Daniel

On 19.01.24 15:23, Julien Chavanton wrote:
> Hi Daniel, I hope you are well, I miss the community !
>
> I just want to make sure you got my submission, I made it yesterday so
> I am not expecting an answer right away but just in case something
> went wrong ...
>
> Cheers !
>
> On Mon, Jan 8, 2024 at 7:30 AM Daniel-Constantin Mierla via sr-users
>  wrote:
>
> Hello,
>
> a short note to inform that the Call For Presentations is now open for
> Kamailio World 2024. Everyone is welcome to submit proposal for
> presentations to share the knowledge about Kamailio or Real Time
> Communication services, security, high availability, scalability, etc.
>
> Submission form and more details are available at:
>
>   - https://www.kamailioworld.com/k2024/call-for-speakers/
>
> Cheers,
> Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com <http://asipto.com>)
> twitter.com/miconda <http://twitter.com/miconda> --
> linkedin.com/in/miconda <http://linkedin.com/in/miconda>
> Kamailio Consultancy, Training and Development Services --
> asipto.com <http://asipto.com>
> Kamailio World Conference, April 18-19, 2024, Berlin --
> kamailioworld.com <http://kamailioworld.com>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply
> only to the sender!
> Edit mailing list options or unsubscribe:
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: rr, loose_route and corex alias_subdomains

[Daniel-Constantin Mierla via sr-users]

Hello,

the log message in your first email is about not finding the socket. The
record route matches the domain, it is just that the socket to be used
cannot matched by the second Route URI. You can name the sockets and set
them in record-route to handle it.

Cheers
Daniel

On 19.01.24 09:20, Jon Bonilla (Manwe) via sr-users wrote:
> Upgraded to 5.7.4
> Then I added "sindominio.net" example domain to corex aliases
>
> Debug Log:
>
> Jan 19 08:14:32 pekedev33
> kamailio: DEBUG:  [core/modparam.c:135]: set_mod_param_regex(): found
>  in module corex
> [/usr/lib/x86_64-linux-gnu/kamailio/modules/corex.so] 
>
> Jan 19 08:14:32 pekedev33 kamailio: DEBUG: corex [corex_lib.c:117]:
> corex_add_alias_subdomains(): try to add alias: sindominio.net 
>
> Jan 19 08:14:32 pekedev33 kamailio: DEBUG: corex [corex_lib.c:185]:
> corex_add_alias_subdomains(): alias: 0:sindominio.net:0 from value:
> sindominio.net added
>
>
> But from console:
>
> # kamctl rpc corex.list_aliases
> {
>   "jsonrpc":  "2.0",
>   "result": [
> ],
>   "id": 87891
> }
>
>
>
>
>
> -- 
> PekePBX, the multitenant PBX solution
> https://pekepbx.com
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.7.4 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.7.4 stable release is out.

This is a maintenance release of the latest stable branch, 5.7, that
includes fixes since the release of v5.7.3. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.7.x. Deployments running previous v5.7.x
versions are strongly recommended to be upgraded to v5.7.4.

For more details about version 5.7.4 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2024/01/kamailio-v5-7-4-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.7.4

[Daniel-Constantin Mierla via sr-users]

Hello,

here is the usual reminder that v5.7.4 is planned to be released today,
therefore any commit to branch 5.7 has to be announced to sr-dev and
wait for ack to avoid conflicts with the building of the new release.
Once the announcement is out, commits can go in this branch as usual.

Cheers,
Daniel

On 15.01.24 11:40, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.7.4 (out of branch 5.7) on
> Thursday, Jan 18, 2024. If anyone is aware of issues not yet on the bug
> tracker, report them there asap in order to have a better chance to be
> fixed.
>
> Cheers,
> Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.7.4

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.7.4 (out of branch 5.7) on
Thursday, Jan 18, 2024. If anyone is aware of issues not yet on the bug
tracker, report them there asap in order to have a better chance to be
fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: [Kamailio-Business] Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

first week of February is a semester school break in many regions, if
someone announces that he has ongoing work to a new module/feature, then
freezing can be postponed.

But if not, I would rather do it earlier than waiting for nothing,
because starting later could end up in getting closer the Catholic
Easter, which is earlier this year, by end of March, a week before
another holiday starts. Considering the constraints on late March and
April, if not out by mid of March or so, next time frame will be end of
April or during May.

Cheers,
Daniel

On 11.01.24 17:12, Henning Westerholt wrote:
> Hello,
>
> early February as a freezing date sounds good to me, just to have one full 
> month after the holiday season/vacation period to allow other people to 
> finish eventual contributions.
>
> Cheers,
>
> Henning
>
> -- 
> Henning Westerholt - https://skalatan.de/blog/
> Kamailio services - https://gilawa.com
>
>> -Original Message-
>> From: Daniel-Constantin Mierla via business 
>> Sent: Mittwoch, 10. Januar 2024 10:11
>> To: Kamailio (SER) - Users Mailing List ; 
>> Kamailio
>> (SER) - Devel Mailing List ;
>> busin...@lists.kamailio.org
>> Subject: [Kamailio-Business] Roadmap to next major Kamailio release series
>> v5.8.x
>>
>> Hello,
>>
>> discussed a bit during the online Kamailio devel meeting, it is time to set 
>> the
>> milestones towards the next major Kamailio release series v5.8.x.
>>
>> If no other suggestions that suit more developers, I would propose to freeze
>> by end of this month or early February, then test for about 4 weeks as usual
>> and release by end of February or during March.
>>
>> If anyone wants to add new features/modules, they have to be published till
>> freezing date, either pushed in the git repository or proposed as pull 
>> request.
>>
>> Cheers,
>> Daniel
>>
>> --
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy,
>> Training and Development Services -- asipto.com Kamailio Advanced Training,
>> February 20-22, 2024 -- asipto.com Kamailio World Conference, April 18-19,
>> 2024, Berlin -- kamailioworld.com
>>
>> ___
>> Kamailio (OpenSER) - business mailing list -- busin...@lists.kamailio.org To
>> unsubscribe send an email to business-le...@lists.kamailio.org
>> http://lists.openser-project.org/cgi-
>> bin/mailman/listinfo%(cgiext)s/%(_internal_name)s

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: xavp_params_explode broken comma in value?

[Daniel-Constantin Mierla via sr-users]

Hello,

On 12.01.24 11:56, Benoît Panizzon wrote:
> Hi Daniel
>  
>> comma is not allowed in an unquoted value for SIP parameters because
>> it is separator for header bodies that are set on the same header
>> name. Practically the comma is the end of parameters list.
> Thank you for your confirmation I was on the right track.
>
>> It should work with:
>>
>> xavp_params_explode("a=foo;c=\"hello,world\";e=baar", "x");
> Any recipe on how to solve if the value is the 'authentication'
> password taken from the database? As far as I understood the SIP RFC a
> comma is permitted in the SIP password itself, as it is never present
> cleartext in a sip header.
>
> Quick example of what I do when receiving a REGISTER with credentials to pull 
> the password:
>
> $var(query) = "select user,password,language from sometable where auth_user = 
> '" + $var(auth_user) + "' limit 1";
> $var(qresult) = sql_xquery("database", "$var(query)", "userdata");
> xavp_params_implode("userdata","$var(xuserdata)");
>
> $var(xuserdata) is "user=JohnDoe;password=secret,password;language=de_CH"
>
> This is the stored in an $sht to be cached and available for a while and 
> reducde SQL queries.
>
> I guess there is no way to have sql_xquery automatically quote result fields 
> that need quoting.
>
> I could probably do select user,concat('"',password,'"'),language from 
> sometable?
>
> This could also be a potential issue with variable injections via SQL. 
> Immagine some use sets a password ";var=value" this would lead to this var 
> being overwritten I guess.
>
> We are moving towards storing ha1 hashed passwords, so that would solve my 
> issue I guess.

the devel version has a new function to implode with values between quotes:

  -
https://www.kamailio.org/docs/modules/devel/modules/pv.html#pv.f.xavp_params_implode_qval

If you expect any kind of characters, maybe hexa/base32/base64
encoding/decoding is a variant to explore.

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: xavp_params_explode broken comma in value?

[Daniel-Constantin Mierla via sr-users]

Hello,

On 12.01.24 11:01, Benoît Panizzon via sr-users wrote:
> Hey!
>
> I'm hunting down an issue with xavp_params_explode, maybe somebody has
> already come adross it and could confirm it exists and maybe know a
> solution?
>
> xavp_params_explode("a=foo;c=hello,world;e=baar", "x");
>
> $xavp(x=>a) is 'foo'
>
> but x=>c and x=>e are null
>
> Am I right to assume the issue being caused by the comma? Is there a
> way to allow a comma?
comma is not allowed in an unquoted value for SIP parameters because it
is separator for header bodies that are set on the same header name.
Practically the comma is the end of parameters list.

It should work with:

xavp_params_explode("a=foo;c=\"hello,world\";e=baar", "x");

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Internal DNS resolver

[Daniel-Constantin Mierla via sr-users]

Hello,

the core rpc lack proper documentation, not like the case of modules. In
this case, the code should be suggestive of what parameters have to be
provided:

  -
https://github.com/kamailio/kamailio/blob/master/src/core/dns_cache.c#L4744

For each of those values, the corex docs for dns_cache parameter should
give details.

Cheers,
Daniel


On 12.01.24 11:05, Igor Potjevlesch wrote:
>
> Hello Daniel,
>
>  
>
> Thanks! I wll try. I didn't find out how to use dns.add_a. Is someone
> has the exact params lists? Thank you.
>
>  
>
> Regards,
>
>  
>
> Igor.
>
>  
>
> *De :*Daniel-Constantin Mierla 
> *Envoyé :* jeudi 11 janvier 2024 19:36
> *À :* Kamailio (SER) - Users Mailing List 
> *Cc :* Igor Potjevlesch 
> *Objet :* Re: [SR-Users] Internal DNS resolver
>
>  
>
> Hello,
>
>  
>
> On 11.01.24 19:07, Igor Potjevlesch via sr-users wrote:
>
> Hello!
>
>  
>
> I have a quick question about the internal DNS resolver and cache
> embedded in Kamailio.
>
> Is the ability to add an entry with dns.add_a bypass the "real"
> DNS lookup? So, let's say that sip.example.com is publicly resolve
> alternatively with 1.2.3.4 & 5.6.7.8.9, if I do a dns.add_a to add
> my own sip.example.com with, alternatively, 127.0.0.1 and
> 127.0.0.2, will it work?
>
>
>
> yes, it should work, the internal cache is checked first and if entry
> found, then it is used.
>
> You can also add entries in the dns cache at startup via dns_cache
> modparam from corex.
>
> Cheers,
> Daniel
>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy, Training and Development Services -- asipto.com
> Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
> Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
>
> 
>   Sans virus.www.avast.com
> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: registrar questions

[Daniel-Constantin Mierla via sr-users]

On 12.01.24 09:48, mm e via sr-users wrote:
> In addition to the RPC command "kamctl add username password", is there a 
> module with a method to operate the "subscriber" database table?

You can "operate" any sql database table with sqlops module.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Internal DNS resolver

[Daniel-Constantin Mierla via sr-users]

Hello,

On 11.01.24 19:07, Igor Potjevlesch via sr-users wrote:
>
> Hello!
>
>  
>
> I have a quick question about the internal DNS resolver and cache
> embedded in Kamailio.
>
> Is the ability to add an entry with dns.add_a bypass the "real" DNS
> lookup? So, let's say that sip.example.com is publicly resolve
> alternatively with 1.2.3.4 & 5.6.7.8.9, if I do a dns.add_a to add my
> own sip.example.com with, alternatively, 127.0.0.1 and 127.0.0.2, will
> it work?
>
>
yes, it should work, the internal cache is checked first and if entry
found, then it is used.

You can also add entries in the dns cache at startup via dns_cache
modparam from corex.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Roadmap to next major Kamailio release series v5.8.x

[Daniel-Constantin Mierla via sr-users]

Hello,

discussed a bit during the online Kamailio devel meeting, it is time to
set the milestones towards the next major Kamailio release series v5.8.x.

If no other suggestions that suit more developers, I would propose to
freeze by end of this month or early February, then test for about 4
weeks as usual and release by end of February or during March.

If anyone wants to add new features/modules, they have to be published
till freezing date, either pushed in the git repository or proposed as
pull request.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio Advanced Training, February 20-22, 2024 -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Info: Kamailio World 2024 - Call for presentations

[Daniel-Constantin Mierla via sr-users]

Hello,

a short note to inform that the Call For Presentations is now open for
Kamailio World 2024. Everyone is welcome to submit proposal for
presentations to share the knowledge about Kamailio or Real Time
Communication services, security, high availability, scalability, etc.

Submission form and more details are available at:

  - https://www.kamailioworld.com/k2024/call-for-speakers/

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services -- asipto.com
Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: DB invalid connection parameter

[Daniel-Constantin Mierla via sr-users]

Hello,

a bit strange as I haven't seen a similar report and 5.6.x series is out
for quite some time.

It seems to be from the timer routine, what is the db_mode parameter for
usrloc module? Have you set also time_procs param?

Cheers,
Daniel

On 03.01.24 21:28, Sergiu Pojoga via sr-users wrote:
> Hi,
>
> Facing the following error after bumping Kam from 5.3 => 5.4 => 5.5 =>
> 5.6, following instructions on each step about DB structure and module
> changes.
>
> These errors show up since. Any clue what they mean? A couple other
> modules are using the same DB MySQL connector. The data in the DB also
> seems to get updated properly.
>
> Jan 03 15:08:30 sip kamailio[20881]: ERROR:  [db.c:489]:
> db_use_table(): invalid connection parameter
> /Jan 03 15:08:30 sip kamailio[20881]: ERROR: usrloc [ucontact.c:1170]:
> db_update_ucontact_ruid(): sql use_table failed
> Jan 03 15:08:30 sip kamailio[20881]: ERROR: usrloc [urecord.c:438]:
> wb_timer(): updating contact in db failed (aor: u...@domain.com)
> /
>
> version: kamailio 5.6.5 (x86_64/linux) 48d48f
> compiled on 02:32:48 Jan  2 2024 with gcc 4.9.2
>
> DB structure:
>
> location | CREATE TABLE `location` (
>   `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
>   `ruid` varchar(64) NOT NULL DEFAULT '',
>   `username` varchar(64) NOT NULL DEFAULT '',
>   `domain` varchar(64) DEFAULT NULL,
>   `contact` varchar(512) NOT NULL DEFAULT '',
>   `received` varchar(128) DEFAULT NULL,
>   `path` varchar(512) DEFAULT NULL,
>   `expires` datetime NOT NULL DEFAULT '2030-05-28 21:32:15',
>   `q` float(10,2) NOT NULL DEFAULT 1.00,
>   `callid` varchar(255) NOT NULL DEFAULT 'Default-Call-ID',
>   `cseq` int(11) NOT NULL DEFAULT 1,
>   `last_modified` datetime NOT NULL DEFAULT '2000-01-01 00:00:01',
>   `flags` int(11) NOT NULL DEFAULT 0,
>   `cflags` int(11) NOT NULL DEFAULT 0,
>   `user_agent` varchar(255) NOT NULL DEFAULT '',
>   `socket` varchar(64) DEFAULT NULL,
>   `methods` int(11) DEFAULT NULL,
>   `instance` varchar(255) DEFAULT NULL,
>   `reg_id` int(11) NOT NULL DEFAULT 0,
>   `server_id` int(11) NOT NULL DEFAULT 0,
>   `connection_id` int(11) NOT NULL DEFAULT 0,
>   `keepalive` int(11) NOT NULL DEFAULT 0,
>   `partition` int(11) NOT NULL DEFAULT 0,
>   PRIMARY KEY (`id`),
>   UNIQUE KEY `ruid_idx` (`ruid`),
>   KEY `account_contact_idx` (`username`,`domain`,`contact`),
>   KEY `expires_idx` (`expires`),
>   KEY `connection_idx` (`server_id`,`connection_id`),
>   *KEY `tcpcon_idx` (`connection_id`)*
> ) ENGINE=InnoDB AUTO_INCREMENT=287989 DEFAULT CHARSET=latin1
>
> > select * from version where table_name='location';
> table_name: location
> table_version: 9
>
> Thanks.
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Merry Christmas and Happy Holidays 2023-2024!

[Daniel-Constantin Mierla via sr-users]

Kamailio project continued to evolve steadily, a new major release was
out during this year, next one planned in a few months, relying on an
amazing community of developers and users. We hope it kept helping
people and companies world wide to connect with the dear ones and build
a better way of living.

The season holidays are ahead, time to relax, spend time with family and
friends! I take again this chance to express my thanks and greetings to
all the friends, developers, supporting companies and community members
that made 2023 another fantastic year for Kamailio project.

Enjoy the holidays! Merry Christmas!

Daniel

* Santa is flying Kamailio! *

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy, Training and Development Services
Kamailio World Conference - April 18-19, 2024, Berlin

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Info: Next Kamailio World Conference - April 18-19, 2024, Berlin, Germany

[Daniel-Constantin Mierla via sr-users]

Hello,

a short announcement to inform that the dates for next Kamailio World
Conference have been set to April 18-19, 2024, the event to take place
again in Berlin, Germany. It will be a different venue than the past
editions, that one not being available. A pre-conference day is
considered on April 17, 2024, but it is not yet known in what form and
where.

The conference is scheduled a bit earlier than the usual in the year
because Germany hosts the Euro 2024 football championship during
June-July 2024, making May very busy and harder to find adequate
conferencing space in Berlin.

The website and more details will be published soon.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Encoded Call-ID - Topoh module

[Daniel-Constantin Mierla via sr-users]

Hello,


On 14.12.23 00:23, Vanderlei Torres Batistela via sr-users wrote:
> Hello all,
>
> How can I get the encoded Call-Id generated by TOPOH module to store
> in the CDR ?

I don't recall any option offered by topoh itself, maybe you can get
something via event routes executed by sipdump module.


On the other hand, with a bit of C coding, shouldn't be complex to add a
function/variable to topoh for such purpose.


Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: {uri.duri} not working

[Daniel-Constantin Mierla via sr-users]

I pushed a commit to git master and 5.7 branches, can you test and see
if it fixes?


On 12.12.23 13:00, hanxiaofang--- via sr-users wrote:
> `sip:`

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: usrloc ka_mode - Flooding OPTIONS at same time?

[Daniel-Constantin Mierla via sr-users]

Hello,

On 11.12.23 18:56, Benoit Panizzon via sr-users wrote:
> Hi
>
> We have reached 2 registered CPE and start facing issues.
>
> Am I observing correctly that when ka_mode 4 is enabled, OPTIONS are
> send simultaneously to all registered CPE and not spread over the
> interval?
>
> They could be the cause very high pps peaks on network equipment?
>
> If so, is there a way to spread the ka options over time so they don't
> cause such high peaks?
>
> Or even better, is there a way to enable them for only some customers
> via a variable?

there is a modparam ka_mode to tune a bit where to send the keep-alives,
one is done by matching a branch flag used for marking natted devices.
If that is not enough because one wants to differentiate between natted
endpoints and those that have to get keepalove, then, being open source,
one can add support for another ka_mode where a different branch flag
can be used to select what contacts should get keepalive.

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: {uri.duri} not working

[Daniel-Constantin Mierla via sr-users]

Hello,

what is printed by the line:

xinfo("duri = $var(duri)\n");

Cheers,
Daniel

On 12.12.23 08:01, hanxiaofang--- via sr-users wrote:
> Hi Kamailio experts,
>
> OS: Debian11
> Kamailio ver: 5.7.3
>
> {uri.duri} doesn't seem to work
>
> The following script can be reproduced:
>
> ```
> debug=2
> log_stderror=yes
>
> # mpath="/usr/local/lib/kamailio/modules/"
>
> loadmodule "tm.so"
> loadmodule "sl.so"
> loadmodule "pv.so"
> loadmodule "siputils.so"
> loadmodule "xlog.so"
> loadmodule "ctl.so"
> loadmodule "htable.so"
>
> modparam("tm", "failure_reply_mode", 3)
> modparam("tm", "fr_timer", 3)
> modparam("tm", "fr_inv_timer", 12)
>
> request_route {
> xinfo("*** $sel(msg)\n");
>
> sl_send_reply("404", "Not here");
> exit;
> }
>
> event_route[htable:mod-init] {
>   $var(ouri) = "sip:al...@server.com:5060;nat=yes;transport=tcp;line=xyz";
>   $var(duri) = $(var(ouri){uri.duri}); # => 
> "sip:server.com:5060;transport=tcp"
>
>   xinfo("ouri = $var(ouri)\n");
>   xinfo("duri = $var(duri)\n");
>   
>   if ($var(duri) ==  "sip:server.com:5060;transport=tcp" ) {
>   xinfo("uri.duri work well\n");
>   } else {
>   xerr("something is wrong\n");
>   }
> }
> ```
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023

[Daniel-Constantin Mierla via sr-users]

Hello,

last notification: with a little bit of the delay, the meeting just started!

Cheers,
Daniel

On 05.12.23 15:05, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> to sync on time world wide, the meeting should start in about 55
> minutes from now.
>
> Cheers,
> Daniel
>
> On 04.12.23 16:27, Daniel-Constantin Mierla wrote:
>>
>> Hello,
>>
>> sort note to refresh about tomorrow's online devel meeting, more
>> details at:
>>
>>   -
>> https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md
>>
>> Cheers,
>> Daniel
>>
>> On 27.11.23 11:04, Daniel-Constantin Mierla wrote:
>>> Hello,
>>>
>>> we should consider an online devel meeting sometime soon to summarize
>>> what was done at (and still needs to be done after) devel meeting in
>>> Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?
>>>
>>> If considered useful, I propose Dec 5 at 15:00UTC (16:00
>>> Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.
>>>
>>> Topics to be discussed can be added at:
>>>
>>>   -
>>> https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md
>>>
>>> Pull requests can be made by users without git access.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> PS: Previous announcement indicated the start time 14:30 UTC, this
>>> message changes it to 15:00 UTC - 30min later due to a constraint in
>>> availability of one of the Kamailio developers.
>>>
>>> -- 
>>> Daniel-Constantin Mierla -- www.asipto.com
>>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>>>
>> -- 
>> Daniel-Constantin Mierla (@ asipto.com)
>> twitter.com/miconda -- linkedin.com/in/miconda
>> Kamailio Consultancy and Development Services
>> Kamailio Advanced Training -- asipto.com
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy and Development Services
> Kamailio Advanced Training -- asipto.com

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023

[Daniel-Constantin Mierla via sr-users]

Hello,

to sync on time world wide, the meeting should start in about 55 minutes
from now.

Cheers,
Daniel

On 04.12.23 16:27, Daniel-Constantin Mierla wrote:
>
> Hello,
>
> sort note to refresh about tomorrow's online devel meeting, more
> details at:
>
>   -
> https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md
>
> Cheers,
> Daniel
>
> On 27.11.23 11:04, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> we should consider an online devel meeting sometime soon to summarize
>> what was done at (and still needs to be done after) devel meeting in
>> Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?
>>
>> If considered useful, I propose Dec 5 at 15:00UTC (16:00
>> Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.
>>
>> Topics to be discussed can be added at:
>>
>>   -
>> https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md
>>
>> Pull requests can be made by users without git access.
>>
>> Cheers,
>> Daniel
>>
>> PS: Previous announcement indicated the start time 14:30 UTC, this
>> message changes it to 15:00 UTC - 30min later due to a constraint in
>> availability of one of the Kamailio developers.
>>
>> -- 
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>>
> -- 
> Daniel-Constantin Mierla (@ asipto.com)
> twitter.com/miconda -- linkedin.com/in/miconda
> Kamailio Consultancy and Development Services
> Kamailio Advanced Training -- asipto.com

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Kemi questions

[Daniel-Constantin Mierla via sr-users]

Hello,

On 05.12.23 14:50, Stefan-Cristian Mititelu via sr-users wrote:
>
> Hello,
>
> When writing kemi cfg (python in my case), is there any way to get rid
> of standard cfg shared variables and use kemi cfg variables instead?
>
>
> E.g. Instead of $shv(blabla) (in standard config) can I use some
> global python var called 'blabla'? Is it seen and shared by all
> kamailio processes? Or I still need to use
> KSR.pv.get/set("$shv(blabla)") ?
>
the global python native variables are per process, so you can't replace
$shv(...) with them. The python ones are more like $var(...) from kamailio.


However, instead of the generic KSR.pv.get/set(), you can use the
alternative KEMI functions -- see them starting at:


  -
https://www.kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/modules/#ksrpvxshv_get


Cheers,
Daniel


-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023

[Daniel-Constantin Mierla via sr-users]

Hello,

sort note to refresh about tomorrow's online devel meeting, more details at:

  -
https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md

Cheers,
Daniel

On 27.11.23 11:04, Daniel-Constantin Mierla wrote:
> Hello,
>
> we should consider an online devel meeting sometime soon to summarize
> what was done at (and still needs to be done after) devel meeting in
> Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?
>
> If considered useful, I propose Dec 5 at 15:00UTC (16:00
> Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.
>
> Topics to be discussed can be added at:
>
>   -
> https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md
>
> Pull requests can be made by users without git access.
>
> Cheers,
> Daniel
>
> PS: Previous announcement indicated the start time 14:30 UTC, this
> message changes it to 15:00 UTC - 30min later due to a constraint in
> availability of one of the Kamailio developers.
>
> -- 
> Daniel-Constantin Mierla -- www.asipto.com
> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>
-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Info: RTC Devroom at FOSDEM 2024

[Daniel-Constantin Mierla via sr-users]

Hello,

another edition of FOSDEM is approaching and it will include again a
Real Time Communications devroom. If anyone wants to share their
interesting applications or experiences in the field, consider to submit
a presentation proposal. The CfP is available at:

  - https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html

It does not have to be about Kamailio, all RTC topics are welcome, just
think to be something useful for developers, as the event is targeting them.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Evapi Async - suspend transaction for a limited time

[Daniel-Constantin Mierla via sr-users]

Hello,

a suspended transaction is kept silently for the duration of the timeout
(see t_set_fr()), then it fails and jumps to a failure route (if you set
one) -- maybe you can leverage this mechanism somehow.

Cheers,
Daniel

On 29.11.23 12:53, Ilie Soltanici via sr-users wrote:
> Hello,
>
> |I'm trying to use the evapi_async_relay function from the evapi
> module, however,I don't want the transaction to be suspended for more
> than 1 second. For instance, if there's no response from the external
> application within this time frame, I want the script to continue and
> remove that transaction from memory. One potential approach I am
> considering is to add suspended transactions to a hash table with a
> timestamp value. Then, using rtimer module, I could periodically parse
> this table every second and process the results, but I'm not sure how
> efficient is that. Maybe you know other alternative, more efficient
> solutions (from a performance point of view) that could achieve the
> same goal? Any insights or recommendations would be greatly appreciated.|
> |Thank you.|
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Incompatibility of the DMQ htable protocol with older Kamailio versions

[Daniel-Constantin Mierla via sr-users]

Hello,

dmq is designed to work only between kamailio nodes that have the same
major version (e.g., only between kamailio 5.7.x nodes).

That's because even on the network the data may look the same, the
internal structures, types of fields, sizes and meaning of values can be
different. This is similar to how the major storage systems require
nodes in the same replication group.

A note about it is in the docs:
  - https://www.kamailio.org/docs/modules/stable/modules/dmq.html#idm39

To detect different versions in the same cluster, you can eventually
look at the User-Agent header (or Server for replies).

Cheers,
Daniel

On 29.11.23 12:51, Denys Pozniak via sr-users wrote:
> Hello!
>
> I noticed that there are differences in the DMQ htable replication
> protocol for the old version of Kamailio 5.2 and the new 5.7.
> For example, the new version uses action 2 when updating values and
> action 4 to remove.
> The old Kamailio version uses the values 1 and 3 respectively.
>
> Well, as a result, the htable data is not shared between such nodes,
> plus there are errors in the syslog of the old version:
> ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action
>
> It would probably be worth introducing some kind of DMQ htable
> protocol versioning to maintain compatibility?
> And is there any option to make them work together (I wouldn’t really
> want to change the action number in sip/sdp/json on the fly)?
>
> Kamialio 5.2
> {"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
> {"action":3,"htname":"shared","cname":"user","mode":0}
>
> Kamailio 5.7
> {"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1}
> {"action":4,"htname":"shared","cname":"user","mode":0}
> -- 
>
> BR,
> Denys Pozniak
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:


-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: tps_storage_fill_contact(): no r-uri user

[Daniel-Constantin Mierla via sr-users]

I guess you face such case because of the contact mode parameter:

  -
https://www.kamailio.org/docs/modules/stable/modules/topos.html#topos.p.contact_mode

Likely you set that modparam to 1, which needs to take user part from
r-uri and contact. I haven't implemented that functionality, but
apparently is for cases when UAs require user part to match
corresponding user ids.

The default mode is 0, which should not care about lack of user parts in
contact header.

Cheers,
Daniel

On 28.11.23 12:22, Denys Pozniak via sr-users wrote:
> Thanks!
> Yes, I experimented a little with the sipp and determined that the
> topos "requires" a user part of Contact URI.
> If this is so, then it would probably be necessary to indicate this
> somewhere in the module description.
>
> вт, 28 нояб. 2023 г. в 11:42, Yuriy G :
>
> Hi Denis. I think this is topos specific. 
> When topos does topology striping it also affects contact field,
> so it adds some data/id username. So if you wish topos to be
> involved - the same form of the URI should be used. There is also
> API from topos module to handle contact on your own if needed.
>
> On Tue, Nov 28, 2023, 11:25 Denys Pozniak via sr-users
>  wrote:
>
> Hello!
>
> My topology is like this:
> PBX -> Kamailio Topos -> User
>
> When calling the user, PBX does not add the user part in the
> Contact URI, something like:
> Contact: 
>
> When the customer sends a reinvite, the topos turns off for
> this transaction and the sip partially breaks down with error:
>
> topos [tps_storage.c:319]: tps_storage_fill_contact(): no
> r-uri user
> topos [tps_storage.c:615]: tps_storage_record(): failed to store
>
> As far as I understand, the RFC allows the absence of the user
> part in the URI and this occurs quite often.
> I can provide the pcap file and debug log in a private message
> if this helps identify the essence of the problem.
>
> # kamailio -v
> version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty
>
> -- 
>
> BR,
> Denys Pozniak
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not
> reply only to the sender!
> Edit mailing list options or unsubscribe:
>
>
>
> -- 
>
> BR,
> Denys Pozniak
>
>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Info: Issue and PR automatic management

[Daniel-Constantin Mierla via sr-users]

Hello,

during the Kamailio Development Meeting that took place in Dusseldorf
earlier this month, one topic was related to administrative tasks
related to project development and management, how to
simplify/automatize such tasks.

To reduce the work load on volunteering contributors, GitHub Actions
were already used for various tasks related to project development and
management (e.g., automatic builds on commits and pull requests to
detect compile errors or code formatting mistakes).

In Dusseldorf another task was configured to be managed with GitHub
Actions, respectively the check of open issues and pull requests to
evaluate the interest of submitters, developers and community users to
pursue them. If there is no activity on an issue (potential bug or
feature request) or a pull request, after 6 weeks it is marked with the
label `stale`. After two more weeks of no activity, the issue or the
pull request is marked with the label `expired` and closed. Note that
any comment postpones the expire timeline, being considered that there
is interest in pursuing the issue or the pull request.

Requests for features were already treated in this way: if nobody
commits to implement it, it can be closed after one month, but it needed
manual work and many were still kept open. Potential bug reports that
become very old are hard to tackle if the source code changes or new
major releases are out, they might even not be valid anymore.

Anyhow, this automatic operations can be reverted if there is still
interest in pursuing the specific issues or pull requests. A registered
developer can remove labels and reopen a closed issue or pull request.
The non-registered-developer contributors have to make a comment that
includes the token `/notstale` to remove the label `stale` or includes
the token `/notexpired` to reopen a closed item.

This new kind of automatic task management might add a little
inconvenience because one has to restate the interest from time to time
for those items that could not be addressed. However, considering that
Kamailio is an open source collaborative project, in order to be fair
for those that volunteer to spend time and resources for development of
Kamailio, also the users/submitters have to stay engaged, not just
report and forget about.

The process to automatize tasks related to Kamailio development and
administration is work in progress. Everything can be adjusted based on
feedback (e.g., time lines), feel free to suggest improvements or new
solutions to make things easier for everyone within the project ecosystem.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: How to remove record-route and via from a forwarded call?

[Daniel-Constantin Mierla via sr-users]

Hello,

On 27.11.23 14:04, Benoit Panizzon via sr-users wrote:
> Hi List
>
> Two Kamailio Nodes situation.
>
> Node A: Routing Instance.
> Node B: Registrar Instance.
>
> An invite is sent from Node A to B.
>
> Customer registered on B is 'busy' as example.
>
> B initiates Call Forwarding by adding a Diversion Header and sending
> the Invite back to A with a new R-URI towards the CFB destination.
>
> The Invite sent from B to A still has Node B in it's Record-Route. So
> all subsequent SIP messages pass via B, which is not needed and cause
> issue with rtpengine running on B.
>
> I attempted to remove_record_route(); when sending the call back to A,
> but this causes:
>
> parse_headers(): bad header field [;lr;ftag=3910078620-883101371>
>
> It looks like only the beginning of the RR header is removed leaving
> back a competely broken line.
>
> What is the propper was to remove a node from RR and Via routing?

the B should not do record_route() when forwards back INVITE to A.

Via is for routing back replies, if you remove it, node B does
retransmissions because it does not receives any response and will also
send a failure code at some point.

Alternative is to send 302 or something else back to A, which does the
redirect using script operations to fetch the contact address or
uac_redirect module.

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023

[Daniel-Constantin Mierla via sr-users]

Hello,

we should consider an online devel meeting sometime soon to summarize
what was done at (and still needs to be done after) devel meeting in
Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?

If considered useful, I propose Dec 5 at 15:00UTC (16:00
Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.

Topics to be discussed can be added at:

  -
https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md

Pull requests can be made by users without git access.

Cheers,
Daniel

PS: Previous announcement indicated the start time 14:30 UTC, this
message changes it to 15:00 UTC - 30min later due to a constraint in
availability of one of the Kamailio developers.

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Kamailio ver 5.7.3 - source installation warnings

[Daniel-Constantin Mierla via sr-users]

Hello,

what OS and gcc version do you have?

Some old gcc version "mistakenly" reported such warnings:

  - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119

Cheers,
Daniel

On 24.11.23 07:00, Muhammad Danish Moosa via sr-users wrote:
> Hi,
>
> I am planning to upgrade Kamailio to version 5.7.3 to manage some
> memory leaks issues.
>
> I am installing from source and came across these warnings, just
> wanted to be sure if they are safe to be ignored.
>
> cr_func.c: In function ‘set_next_domain_on_rule’:
> cr_func.c:160:2: warning: missing braces around initializer
> [-Wmissing-braces]
>   pv_value_t val = {0};
>   ^
> cr_func.c:160:2: warning: (near initialization for ‘val.rs
> ’) [-Wmissing-braces]
> cr_func.c: In function ‘actually_rewrite’:
> cr_func.c:348:2: warning: missing braces around initializer
> [-Wmissing-braces]
>   pv_value_t val = {0};
>   ^
> cr_func.c:348:2: warning: (near initialization for ‘val.rs
> ’) [-Wmissing-braces]
> cr_func.c: In function ‘ki_cr_load_user_carrier_helper’:
> cr_func.c:782:2: warning: missing braces around initializer
> [-Wmissing-braces]
>   pv_value_t val = {0};
>   ^
> --
>
> LD (gcc) [M p_usrloc.so]                p_usrloc.so
> CC (gcc) [M evrexec.so]         evrexec_mod.o
> evrexec_mod.c:64:1: warning: missing braces around initializer
> [-Wmissing-braces]
>  static evrexec_info_t _evrexec_info = {0};
>  ^
> evrexec_mod.c:64:1: warning: (near initialization for
> ‘_evrexec_info.data’) [-Wmissing-braces]
> LD (gcc) [M evrexec.so]         evrexec.so
> CC (gcc) [M avp.so]             avp.o
> LD (gcc) [M avp.so]             avp.so
> CC (gcc) [M acc_diameter.so]            diam_message.o
> CC (gcc) [M acc_diameter.so]            acc_diameter_mod.o
> CC (gcc) [M acc_diameter.so]            diam_avp.o
> CC (gcc) [M acc_diameter.so]            diam_tcp.o
> LD (gcc) [M acc_diameter.so]            acc_diameter.so
> CC (gcc) [M dmq.so]             bind_dmq.o
> CC (gcc) [M dmq.so]             message.o
> CC (gcc) [M dmq.so]             dmq_funcs.o
> dmq_funcs.c: In function ‘ki_dmq_send_message’:
> dmq_funcs.c:304:3: warning: missing braces around initializer
> [-Wmissing-braces]
>    dmq_peer_t new_peer = {0};
>    ^
> dmq_funcs.c:304:3: warning: (near initialization for
> ‘new_peer.peer_id’) [-Wmissing-braces]
> dmq_funcs.c: In function ‘ki_dmq_bcast_message’:
> dmq_funcs.c:374:3: warning: missing braces around initializer
> [-Wmissing-braces]
>    dmq_peer_t new_peer = {0};
>    ^
> dmq_funcs.c:374:3: warning: (near initialization for
> ‘new_peer.peer_id’) [-Wmissing-braces]
> CC (gcc) [M dmq.so]             notification_peer.o
> CC (gcc) [M dmq.so]             dmq.o
> dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces]
>  sip_uri_t dmq_server_uri = {0};
>  ^
> dmq.c:61:1: warning: (near initialization for ‘dmq_server_uri.user’)
> [-Wmissing-braces]
> dmq.c:67:1: warning: missing braces around initializer [-Wmissing-braces]
>  static sip_uri_t dmq_notification_uri = {0};
>  ^
> dmq.c:67:1: warning: (near initialization for
> ‘dmq_notification_uri.user’) [-Wmissing-braces]
> Muhammad Danish Moosa
>
> " The core of mans' spirit comes from new experiences. "___
> Christopher McCandless
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: RADIUS - Can't use extra attributes

[Daniel-Constantin Mierla via sr-users]

Hello,

On 23.11.23 19:33, Duarte Rocha via sr-users wrote:
> Hello all,
>
> I'm currently implementing a Kamailio with RADIUS. 
>
> I want to send an Access-Request to my RADIUS server and in order to do that 
> i'm using misc_radius module and radius_does_uri_exist() function without any 
> arguments : 
>
> "if (radius_does_uri_exist()) {"
>
> For my module configuration I have the following configurations : 
>
> "modparam("misc_radius", "radius_config", "/etc/radcli/radiusclient.conf")
> modparam("misc_radius", "uri_extra", "Sip-Method=$rm")"
>
> From what i understand, with this config my access-request should contain the 
> default attributes and Sip-Method Attribute but that is not happening. Only 
> defaults attributes are included. 
>
> I've tried to run Kamailio with "-ddd" flag for better debug and i only get 
> this error : "1(176) DEBUG: misc_radius [functions.c:615]: 
> radius_does_uri_user_host_exist(): failure".
>
> Is there any other configuration that i must do?

if you haven't done it, I think you need to exten the radius dictionary
as well. Maybe this (very old) tutorial can help a bit:

- https://www.kamailio.org/docs/kamailio-radius-1.0.x.html

Cheers, Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Online devel meeting on matrix - 14:30 UTC, Dec 5, 2023

[Daniel-Constantin Mierla via sr-users]

Hello,

we should consider an online devel meeting sometime soon to summarize
what was done at (and still needs to be done after) devel meeting in
Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)?

If considered useful, I propose Dec 5 at 14:30UTC (15:30
Berlin/Paris/Madrid/Rome), but we can also look for other dates as well.

Topics to be discussed can be added at:

  -
https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md

Pull requests can be made by users without git access.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Kamailio v5.6.5 Released

[Daniel-Constantin Mierla via sr-users]

Hello,

Kamailio SIP Server v5.6.5 stable release is out.

This is a maintenance release of the latest stable branch, 5.6, that
includes fixes since the release of v5.6.4. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.6.x. Deployments running previous v5.6.x
versions are strongly recommended to be upgraded to v5.6.5.


Note that 5.6 is the second last stable branch, still officially
maintained by Kamailio development team. The latest stable branch is
5.7, with v5.7.3 being release out of it.


For more details about version 5.6.5 (including links and guidelines to
download the tarball or from GIT repository), visit:

  * https://www.kamailio.org/w/2023/11/kamailio-v5-6-5-released/

RPM, Debian/Ubuntu packages will be available soon as well.

Many thanks to all contributing and using Kamailio!

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Releasing v5.6.5

[Daniel-Constantin Mierla via sr-users]

Hello,

short note that the v5.6.5 is going to be prepared soon and released
today, therefore any commits to branch 5.6 must be announced to sr-dev
and wait for ack before pushing to avoid conflicts with release building
process. Once the release announcement is out, commits can go into this
branch as usual.

Cheers,
Daniel

On 21.11.23 11:15, Daniel-Constantin Mierla wrote:
> Hello,
>
> I am considering to release Kamailio v5.6.5 (out of branch 5.6) later
> this week (likely on Thursday or Friday, Nov 23/24, 2023). If anyone is
> aware of
> issues not yet on the bug tracker, report them there asap in order to
> have a better chance to be fixed.
>
> Cheers,
> Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Re: Crash on core/mem/q_malloc.c

[Daniel-Constantin Mierla via sr-users]

Hello,

looks like a buffer overflow by 1 byte. Are you using any custom
module/additional patches, or is it stock kamailio?

Cheers,
Daniel

On 22.11.23 00:46, Igor Potjevlesch via sr-users wrote:
>
> Hello!
>
>  
>
> I'm facing an issue 2/3 times a day with the following errors in the logs:
>
> Nov 22 00:09:02 /usr/local/sbin/kamailio[3720]: CRITICAL: 
> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: prev.
> fragm. tail overwritten(c0c0c000,
> abcdefed)[0x7f9600b754f8:0x7f9600b75530]! Memory allocator was called
> from core: core/re.c:430. Fragment marked by core: db_res.c:139. Exec
> from core/mem/q_malloc.c:391.
>
> Nov 22 00:09:02 /usr/local/sbin/kamailio[3720]: CRITICAL: 
> [core/mem/q_malloc.c:155]: qm_debug_check_frag(): BUG: qm: prev.
> fragm. tail overwritten [0x7f9600b75460:0x7f9600b75498] - fragment
> marked by tm: t_fwd.c:230
>
> Nov 22 00:09:02 abrt-hook-ccpp: Process 3720 (kamailio) of user 0
> killed by SIGABRT - ignoring (repeated crash)
>
>  
>
> Do you have any idea where it could come from? I'm running Kamailio 5.6.4.
>
>  
>
> Regards,
>
>  
>
> Igor.
>
>
> 
>   Sans virus.www.avast.com
> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> __
> Kamailio - Users Mailing List - Non Commercial Discussions
> To unsubscribe send an email to sr-users-le...@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the 
> sender!
> Edit mailing list options or unsubscribe:

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

[SR-Users] Releasing v5.6.5

[Daniel-Constantin Mierla via sr-users]

Hello,

I am considering to release Kamailio v5.6.5 (out of branch 5.6) later
this week (likely on Thursday or Friday, Nov 23/24, 2023). If anyone is
aware of
issues not yet on the bug tracker, report them there asap in order to
have a better chance to be fixed.

Cheers,
Daniel

-- 
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training -- asipto.com

__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe: