Re: [SR-Users] Hello Group - I have a "challenge"

[Henning Westerholt]

Hello Kevin,

not having looked into your cfg, can you check this two things:

- the format of your "log_prefix" parameter, for reference compare to 
e.g. this one "log_prefix="{$mt $hdr(CSeq) $ci} "
- do you have a a request_route configured?

Cheers,

Henning


Am 04.09.19 um 02:49 schrieb Kevin Greene:
> I recently did the upgrade from v4.4 to 5.2 (via Yum).
>
> When starting Kamailio, I get these three errors. Not sure if they are 
> related or not but I do not think so.
>
> Have spent a lot of time searching on Google for the answer and have 
> not found the solution.
>
> [root@ids kamailio]# kamctl restart
>
> INFO: Stopping Kamailio :
> INFO: stopped
>
> INFO: Starting Kamailio :
> INFO: started (pid: 44608)
>
> [root@ids kamailio]# tail -f /var/log/sipserver.log
>
> Sep  4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR:  
> [core/pvapi.c:1119]: pv_parse_spec2(): wrong char [t/116] in [$mt] at 
> [2 (0)]
>
> Sep  4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR:  
> [core/dprint.c:451]: log_prefix_init(): wrong format[{$mt $hdr(CSeq) 
> $ci} ]
>
> Sep  4 00:39:06 ids /usr/sbin/kamailio[44626]: ERROR:  
> [core/receive.c:319]: receive_msg(): no request_route {...} and no 
> other config routing engine registered
>
> The last error is repeated many times (each time a remote user tries 
> to connect I think).
>
> I can send any additional files if needed.
>
> Thanks. I am burning out on this upgrade.
>
> Kevin
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] [sr-dev] Planning the next major release - v5.3.0

[Daniel-Constantin Mierla]

Hello,

quick reminder that at the end of today the master branch will be frozen
to prepare the release of the next major version 5.3.0 -- no new
features to be pushed for a few weeks, the focus will be on testing.

Cheers,
Daniel

On 30.08.19 16:58, Daniel-Constantin Mierla wrote:
> Hello,
>
> if no other comments, the plan is to freeze on the 4th of September.
>
> Cheers,
> Daniel
>
> On 22.08.19 21:57, Henning Westerholt wrote:
>> Hello Daniel,
>>
>> sounds good. I know from private discussions about one more module that 
>> might be needed to be integrated. I will ask for an update there. From 
>> my side there is one medium sized core cleanup missing, but September 
>> 4th should be fine for me.
>>
>> Cheers,
>>
>> Henning
>>
>> Am 20.08.19 um 09:56 schrieb Daniel-Constantin Mierla:
>>> Hello,
>>>
>>> it's about the time to set the milestones to the next major release -
>>> v5.3.0. There are 6 new modules and many other enhancements to existing
>>> components in git master branch, also during the last irc devel meeting
>>> it was proposed to freeze after summer holidays.
>>>
>>> At this moment I would propose Wednesday, September 4, 2019 to freeze
>>> the development. Then the release should be about one month later, after
>>> testing interval.
>>>
>>> In case there are people willing a bit more time for development, we can
>>> freeze one week later, September 11, or another date  -- your
>>> suggestions here.
>>>
>>> Cheers,
>>> Daniel
>>>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Hello Group - I have a "challenge"

[Kevin Greene]

I recently did the upgrade from v4.4 to 5.2 (via Yum).

When starting Kamailio, I get these three errors. Not sure if they are 
related or not but I do not think so.


Have spent a lot of time searching on Google for the answer and have not 
found the solution.


[root@ids kamailio]# kamctl restart

INFO: Stopping Kamailio :
INFO: stopped

INFO: Starting Kamailio :
INFO: started (pid: 44608)

[root@ids kamailio]# tail -f /var/log/sipserver.log

Sep  4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR:  
[core/pvapi.c:1119]: pv_parse_spec2(): wrong char [t/116] in [$mt] at [2 
(0)]


Sep  4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR:  
[core/dprint.c:451]: log_prefix_init(): wrong format[{$mt $hdr(CSeq) $ci} ]


Sep  4 00:39:06 ids /usr/sbin/kamailio[44626]: ERROR:  
[core/receive.c:319]: receive_msg(): no request_route {...} and no other 
config routing engine registered


The last error is repeated many times (each time a remote user tries to 
connect I think).


I can send any additional files if needed.

Thanks. I am burning out on this upgrade.

Kevin

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio stops processing requests over UDP

[Daniel-Constantin Mierla]

On 03.09.19 10:53, Daniel-Constantin Mierla wrote:
> On 03.09.19 09:54, Juha Heinanen wrote:
>> Juha Heinanen writes:
>>
>>> Here is two traps taken about 8 minutes apart during the same freeze:
>>>
>>> https://box.tutpro.com/tmp/gdb_kamailio_20190902_120249
>>> https://box.tutpro.com/tmp/gdb_kamailio_20190902_121032
>>>
>>> During the freeze, it was possible to make MySQL queries to accounting
>>> table using mysql cli command.
>> Looks like 8 UDP receivers are waiting for futexlock and 8 are in
>> udp_rcv_loop.  Those that are waiting for the lock are processing the
>> same reply.  Same in both traps.
>>
>> There is also mysql ping going on by timer process.

The mysql client library is stuck, waiting for a poll event to happen.
It is the insert done for accounting on SIP response.

It is hard to say what is the reason, maybe you can install the debug
symbols for lib mysql client library and the the backtrace shows details
of what happens inside the library. The mysql modules was not
significantly touched for a long time, so might be something specific
for lib mysql (mariadb) client.

Cheers,
Daniel

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


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Unexpected BYEs from dialog module

[Henning Westerholt]

Hi Alex,

answer inline below

Am 02.09.19 um 10:04 schrieb Alex Balashov:
>> just looked briefly into the code. There is only one place in the
>> dialog module that ends a dialog with "dlg_bye_all" - and this happens
>> in the dlg_ontimeout routine, if there is the proper flag set for the
>> particular dialog.
>>
>> Do you have the send_bye parameter set to 1 or use the
>> $dlg_ctx(timeout_bye) PV? Is there any configured timeout that relates
>> to the ~150s that you see in the module? It is always ~150s or does it
>> change from call to call?

So you've set dhe dlg_bye_all parameter. Could you try to deactivate it 
just for a brief time and see if the problem does occur as well? Then we 
know at for sure that it is related to this functionality.

>> No, mysteriously there is not.
>>
>> While the value of the timeout_avp can vary from call to call, in the
>> case of these particular calls--and indeed, 95%+ of calls--it is set to
>> 7200 sec. The default_timeout modparam is set to 28800 sec (8 hours).
>>
>> The timeout period always seems to be 150-160 sec, but as you note, the
>> arithmetical relationship between this period and any formally declared
>> timeouts is a mystery.

Another idea , there is the dlg_clean_timer which is 90s. But this is 
still a bit off to your observed time period.

Maybe an additional timer is  running before.

>> About the other topic - the matching mode: if there is an existing,
>> but broken RR DID parameter, the code will stop processing and not try
>> again the other match mode.
>>
>> This is correct according the docs "1 - DID_FALLBACK - the match is
>> first tried based on DID and if not present, it will fall back to SIP
>> matching;", but could be changed to be more resilient, I agree.
> Ah, I see. Well, "if not present" is a bit ambiguous from a layperson's
> perspective; in my case the cookie is present but incorrect and so does
> not match a known dialog, so I didn't know offhand if the code treat the
> parameter as though it were altogether absent, or whether it would treat
> it as present but wrong and abort processing as you suggest. :-)

Yes, this could be improved, I agree.

Cheers,

Henning


-- 
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] crash/mem leaks on low memory

[Daniel-Constantin Mierla]

Hello,

you were looking at the wrong log message, that warning is not the
reason of kamailio not running, just saying that libssl is known to have
some issue when low shared memory is available, but starting and
operating is fine till that moment.

The real problem is pointed by:

Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: 
[core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on
172.31.35.49:5091  : Address already in use

There is another application listening on the same ip:port. Maybe
kamailio is already running?

Cheers,
Daniel

On 03.09.19 15:28, Gaurav Bmotra wrote:
> hi Vlad
> thanks you for reply 
>  kamailio shared memory is already 512 (kamailio -m 512)
> but still same error getting  in logs 
>
> On Tue, Sep 3, 2019 at 6:44 PM Vlad Toma  > wrote:
>
> Hello,
> You should try to increase the ram memory for kamailio when you
> start it ( kamailio -m 256) . I think your problem is similar to
> this one https://github.com/kamailio/kamailio/issues/1635 
>
> Regards,
> Vlad
>
>
> On Tue, Sep 3, 2019 at 3:46 PM Gaurav Bmotra
> mailto:saigauravmehr...@gmail.com>>
> wrote:
>
> hi 
> i m using kamailio 5.1 on Ubuntu 18.04
> i m geting this error in logs and it stop registration form
> soft-phone
> plz help me 
>
> 
> 
> WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491
> (crash/mem leaks on low memory) workaround enabled (on low
> memory tls operations will fail preemptively) with free memory th
> 
> 
> kamailio.service - LSB: Start the Kamailio SIP proxy server
>    Loaded: loaded (/etc/init.d/kamailio; generated)
>    Active: active (exited) since Tue 2019-09-03 12:09:19 UTC;
> 26min ago
>      Docs: man:systemd-sysv-generator(8)
>   Process: 27237 ExecStart=/etc/init.d/kamailio start
> (code=exited, status=0/SUCCESS)
>
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO:
>  [core/cfg/cfg_ctx.c:595]: cfg_set_now():
> tls.low_mem_threshold2 has been changed to 7077888
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO:
>  [main.c:2636]: main(): processes (at least): 27 - shm
> size: 536870912 - pkg size: 8388608
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR:
> dispatcher [dispatcher.c:813]: ds_warn_fixup(): failover
> functions used, but required AVP parameters are NULL --
> feature disabled
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO:
>  [core/udp_server.c:153]: probe_max_receive_buffer():
> SO_RCVBUF is initially 212992
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO:
>  [core/udp_server.c:205]: probe_max_receive_buffer():
> SO_RCVBUF is finally 425984
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR:
>  [core/tcp_main.c:2850]: tcp_init(): bind(c,
> 0x7f0b41b001f4, 16) on 172.31.35.49:5091
>  : Address already in use
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO:
>  [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API
> not initialized 
>
> -- 
> thank you 
>
>
>
>
>
>
>
> *Regards:*
> Gaurav Kumar
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> -- 
>
>
>
>
>
>
>
>
> *Regards:*
> Gaurav Kumar
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

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

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] crash/mem leaks on low memory

[Gaurav Bmotra]

hi Vlad
thanks you for reply
 kamailio shared memory is already 512 (kamailio -m 512)
but still same error getting  in logs

On Tue, Sep 3, 2019 at 6:44 PM Vlad Toma  wrote:

> Hello,
> You should try to increase the ram memory for kamailio when you start it
> ( kamailio -m 256) . I think your problem is similar to this one
> https://github.com/kamailio/kamailio/issues/1635
>
> Regards,
> Vlad
>
>
> On Tue, Sep 3, 2019 at 3:46 PM Gaurav Bmotra 
> wrote:
>
>> hi
>> i m using kamailio 5.1 on Ubuntu 18.04
>> i m geting this error in logs and it stop registration form soft-phone
>> plz help me
>>
>>
>> 
>> WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem
>> leaks on low memory) workaround enabled (on low memory tls operations will
>> fail preemptively) with free memory th
>>
>> 
>> kamailio.service - LSB: Start the Kamailio SIP proxy server
>>Loaded: loaded (/etc/init.d/kamailio; generated)
>>Active: active (exited) since Tue 2019-09-03 12:09:19 UTC; 26min ago
>>  Docs: man:systemd-sysv-generator(8)
>>   Process: 27237 ExecStart=/etc/init.d/kamailio start (code=exited,
>> status=0/SUCCESS)
>>
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
>> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been
>> changed to 7077888
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
>> [main.c:2636]: main(): processes (at least): 27 - shm size: 536870912 - pkg
>> size: 8388608
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: dispatcher
>> [dispatcher.c:813]: ds_warn_fixup(): failover functions used, but required
>> AVP parameters are NULL -- feature disabled
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
>> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially
>> 212992
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
>> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally
>> 425984
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: 
>> [core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on
>> 172.31.35.49:5091 : Address already in use
>> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
>> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
>>
>> --
>> thank you
>>
>>
>>
>>
>>
>>
>>
>> *Regards:*
>> Gaurav Kumar
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>


-- 








*Regards:*
Gaurav Kumar
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] crash/mem leaks on low memory

[Vlad Toma]

Hello,
You should try to increase the ram memory for kamailio when you start it
( kamailio -m 256) . I think your problem is similar to this one
https://github.com/kamailio/kamailio/issues/1635

Regards,
Vlad


On Tue, Sep 3, 2019 at 3:46 PM Gaurav Bmotra 
wrote:

> hi
> i m using kamailio 5.1 on Ubuntu 18.04
> i m geting this error in logs and it stop registration form soft-phone
> plz help me
>
>
> 
> WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem
> leaks on low memory) workaround enabled (on low memory tls operations will
> fail preemptively) with free memory th
>
> 
> kamailio.service - LSB: Start the Kamailio SIP proxy server
>Loaded: loaded (/etc/init.d/kamailio; generated)
>Active: active (exited) since Tue 2019-09-03 12:09:19 UTC; 26min ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 27237 ExecStart=/etc/init.d/kamailio start (code=exited,
> status=0/SUCCESS)
>
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been
> changed to 7077888
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
> [main.c:2636]: main(): processes (at least): 27 - shm size: 536870912 - pkg
> size: 8388608
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: dispatcher
> [dispatcher.c:813]: ds_warn_fixup(): failover functions used, but required
> AVP parameters are NULL -- feature disabled
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially
> 212992
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally
> 425984
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: 
> [core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on
> 172.31.35.49:5091 : Address already in use
> Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
>
> --
> thank you
>
>
>
>
>
>
>
> *Regards:*
> Gaurav Kumar
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] crash/mem leaks on low memory

[Gaurav Bmotra]

hi
i m using kamailio 5.1 on Ubuntu 18.04
i m geting this error in logs and it stop registration form soft-phone
plz help me


WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem
leaks on low memory) workaround enabled (on low memory tls operations will
fail preemptively) with free memory th

kamailio.service - LSB: Start the Kamailio SIP proxy server
   Loaded: loaded (/etc/init.d/kamailio; generated)
   Active: active (exited) since Tue 2019-09-03 12:09:19 UTC; 26min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 27237 ExecStart=/etc/init.d/kamailio start (code=exited,
status=0/SUCCESS)

Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
[core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been
changed to 7077888
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
[main.c:2636]: main(): processes (at least): 27 - shm size: 536870912 - pkg
size: 8388608
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: dispatcher
[dispatcher.c:813]: ds_warn_fixup(): failover functions used, but required
AVP parameters are NULL -- feature disabled
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
[core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially
212992
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
[core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally
425984
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: 
[core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on
172.31.35.49:5091 : Address already in use
Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: 
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized

-- 
thank you







*Regards:*
Gaurav Kumar
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio stops processing requests over UDP

[Daniel-Constantin Mierla]

On 03.09.19 09:54, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> Here is two traps taken about 8 minutes apart during the same freeze:
>>
>> https://box.tutpro.com/tmp/gdb_kamailio_20190902_120249
>> https://box.tutpro.com/tmp/gdb_kamailio_20190902_121032
>>
>> During the freeze, it was possible to make MySQL queries to accounting
>> table using mysql cli command.
> Looks like 8 UDP receivers are waiting for futexlock and 8 are in
> udp_rcv_loop.  Those that are waiting for the lock are processing the
> same reply.  Same in both traps.
>
> There is also mysql ping going on by timer process.

Yesterday I started a trip and didn't get the time to look over the last
two traces, I should be able to do it later today.

In the first trace, the ping-pong looked like internally in the
libmysqlclient library before doing the acc insert, probably to wake
up/be sure connection is alive, and that seemed to be stuck.

Cheers,
Daniel

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


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio stops processing requests over UDP

[Juha Heinanen]

Juha Heinanen writes:

> Here is two traps taken about 8 minutes apart during the same freeze:
> 
> https://box.tutpro.com/tmp/gdb_kamailio_20190902_120249
> https://box.tutpro.com/tmp/gdb_kamailio_20190902_121032
> 
> During the freeze, it was possible to make MySQL queries to accounting
> table using mysql cli command.

Looks like 8 UDP receivers are waiting for futexlock and 8 are in
udp_rcv_loop.  Those that are waiting for the lock are processing the
same reply.  Same in both traps.

There is also mysql ping going on by timer process.

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] How to detect miss call and accomplished call

[Henning Westerholt]

Hello Anuran,

you are probably want to look into the "acc" accounting module. The default cfg 
already has some code for this. It can account e.g. succesful and failed calls.

Cheers,

Henning

Am 03.09.19 um 06:36 schrieb Anuran Barman:
Hi,
I want to show call logs in my SIP app. How can I do this with Kamailio? I want 
to do it from the kamailio.cfg file. Is it possible to do it from where? I 
guess Dialog module should be used for this, but can not figure out how to do 
it. I want minimalist feature like who call whom with timestamp, thats all. How 
can I do this?



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] evapi mismatch version

[Bill Neely]

Built from yum with 5.2 repo, Not sure where the evapi module lives.

Bill


On 9/2/19 10:30 AM, Juha Heinanen wrote:

b...@novatrope.us writes:


Installed Kam 5.2.4, but now getting version mismatch on evapi.

ERROR:  [core/sr_module.c:348]: version_control(): module version
mismatch for /usr/lib64/kamailio/modules/evapi.so; core: kamailio 5.2.4
(x86_64/linux); module: kamailio 5.1.6 (x86_64/linux)

Anybody know how to get the correct evapi version. I am running centos
7

Make sure that when you built Kamailio 5.2, also evapi module got built.
Now your evapi module is from Kamailio 5.1.

-- Juha

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users