date:20191127

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

So what I can tell you is libmysqlclient-dev was upgraded to
5.7.28-0ubuntu0.16.04.2 from 5.7.26. We were experiencing kamailio memory
footprint increasing with load. Aside from the stacktraces posted above
there was this in the logs
 [core/mem/q_malloc.c:290]: qm_find_free():
qm_find_free(0x7fc19180f000, 5720); Free fragment not found!

On Wed, Nov 27, 2019 at 3:59 PM Henning Westerholt  wrote:

> Thanks for the notice, good that it was sorted out. Could you add the
> crashing mysql package version here, just to compare in the future if new
> reports show up..
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* Daniel Greenwald 
> *Sent:* Wednesday, November 27, 2019 9:42 PM
> *To:* Henning Westerholt 
> *Cc:* Kamailio (SER) - Users Mailing List ;
> mico...@gmail.com
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> Thanks we ended up downgrading the mysql packages to 5.7.11-0ubuntu6 and
> seems to have resolved the issue.Seems the latest package caused craziness.
> Warning to others..
>
>
>
> On Wed, Nov 27, 2019 at 2:07 PM Henning Westerholt  wrote:
>
> Hello,
>
>
>
> This one package should contain all (packaged) debug info.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
> Kamailio Merchandising – https://skalatan.de/merchandising
>
>
>
> *From:* Daniel Greenwald 
> *Sent:* Wednesday, November 27, 2019 7:55 PM
> *To:* Henning Westerholt 
> *Cc:* Kamailio (SER) - Users Mailing List ;
> mico...@gmail.com
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> Yeah Yeah but what about the modules? Are there dbg packages for those, I
> don't see them?
>
>
>
> On Wed, Nov 27, 2019 at 1:27 PM Henning Westerholt  wrote:
>
> With google?  The package is called kamailio-dbg
>
>
>
>
> https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages
>
>
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
> Kamailio Merchandising – https://skalatan.de/merchandising
>
>
>
> *From:* sr-users  *On Behalf Of *Daniel
> Greenwald
> *Sent:* Wednesday, November 27, 2019 6:36 PM
> *To:* Daniel-Constantin Mierla 
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> How do I install the symbol packages?
>
>
>
> On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
> wrote:
>
> We noticed mysql did an upgrade to 5.7
>
>
>
> On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>
>
> On 27.11.19 18:15, Daniel Greenwald wrote:
>
> yes tls is loaded before db_mysql, is that bad?
>
> Not, tls before any other modules potentially using libssl is the right
> order.
>
>
>
> Yes apt updates were run so could have been updates to anything. OS
> version is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last
> run a couple of weeks ago.
>
>
>
> Upon further digging I think the tls change was released a couple weeks
> ago so yes probably unrelated.
>
>
>
> Install the packages with debug symbols for kamailio, libmysqlclient and
> libssl/libcrypto, then grab again the "bt full", it should show more
> details in the backtrace that may help to identify the issue.
>
> Cheers,
> Daniel
>
>
>
>
>
>
>
>
>
> On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
> The issue seems to come from libmysqlclient library, not to kamailio
> handling sip traffic over tls.
>
> Is tls module loaded before the db_mysql module?
>
> Have you made other updates to the operating system? Or only the change
> you mentioned about server requiring and verifying certificates?
>
> What version of ubuntu do you run?
>
> I see that it uses libssl 1.0, so it is no relation with the change in
> libssl 1.1 internal api.
>
> Cheers,
> Daniel
>
> On 27.11.19 17:38, Daniel Greenwald wrote:
>
> Core was generated by `/usr/sbin/kamailio -P
> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> 681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
> directory.
> (gdb) bt
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> #1  0x7fc864920b79 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #2  0x7fc86492117a in lh_retrieve () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #3  0x7fc864923651 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #4  0x7fc8649240de in ERR_get_state () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #5  0x7fc864924326 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #6  0x7fc864c8a8e0 in SSL_get_error () from
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> #7

Re: [SR-Users] Possible conflict between t_newtran and setflag for ACC

2019-11-27 Thread Patrick Wakano

Thanks for your reply Henning!

I also removed it from my script.
The only thing is that when using it there is this nasty side effect, so I
think if the function is meaningless it can be removed.
I will create a ticket for it, so it can be evaluated what is the best
approach.

Thank you,
Kind regards,
Patrick Wakano


On Thu, 28 Nov 2019 at 06:12, Henning Westerholt  wrote:

> Hello,
>
>
>
> usually it is not needed anymore to do this t_newtran early in the cfg.
> Check this discussion from 2015 out:
>
>
>
>
> http://sip-router.1086192.n5.nabble.com/Transaction-good-practices-with-t-relay-t-newtran-and-t-release-td137433.html
>
>
>
> There is also another function in tmx, t_precheck_trans which can be used
> to detect re-transmissions without actually creating a new one.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
>
>
> *From:* sr-users  *On Behalf Of *Patrick
> Wakano
> *Sent:* Wednesday, November 27, 2019 3:26 AM
> *To:* Kamailio (SER) - Users Mailing List 
> *Subject:* [SR-Users] Possible conflict between t_newtran and setflag for
> ACC
>
>
>
> Hello list,
>
> Hope you all doing well!
>
>
>
> I am using the ACC module and using the setflag() function as done in
> several examples. It works fine. However, I've added the t_newtran()
> function almost in the begging of the INVITE handler to help the
> retransmission detection and after that I noticed the ACC was not saving
> anything in DB.
>
> So after debugging I discovered that if I call the t_newtran() before
> setting the ACC flags, the module will not save the calls in DB, but if I
> call it after setting the ACC flags, it works
>
> So my question is, is this a bug or it is a expected side effect so when
> one is using t_newtran you must be careful and set all your transaction
> flags before? (ACC are the only transaction flags I am using so can't tell
> if other modules have the same problem)
>
> This is happening in Kamailio 5.2.2.
>
>
>
> Thank you!
>
> Kind regards,
>
> Patrick Wakano
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Henning Westerholt

Thanks for the notice, good that it was sorted out. Could you add the crashing 
mysql package version here, just to compare in the future if new reports show 
up..

Cheers,

Henning

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

From: Daniel Greenwald 
Sent: Wednesday, November 27, 2019 9:42 PM
To: Henning Westerholt 
Cc: Kamailio (SER) - Users Mailing List ; 
mico...@gmail.com
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

Thanks we ended up downgrading the mysql packages to 5.7.11-0ubuntu6 and seems 
to have resolved the issue.Seems the latest package caused craziness. Warning 
to others..

On Wed, Nov 27, 2019 at 2:07 PM Henning Westerholt 
mailto:h...@skalatan.de>> wrote:
Hello,

This one package should contain all (packaged) debug info.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising

From: Daniel Greenwald mailto:dgreenw...@gmail.com>>
Sent: Wednesday, November 27, 2019 7:55 PM
To: Henning Westerholt mailto:h...@skalatan.de>>
Cc: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>; 
mico...@gmail.com
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

Yeah Yeah but what about the modules? Are there dbg packages for those, I don't 
see them?

On Wed, Nov 27, 2019 at 1:27 PM Henning Westerholt 
mailto:h...@skalatan.de>> wrote:
With google?  The package is called kamailio-dbg

https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages


--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising

From: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 On Behalf Of Daniel Greenwald
Sent: Wednesday, November 27, 2019 6:36 PM
To: Daniel-Constantin Mierla mailto:mico...@gmail.com>>
Cc: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

How do I install the symbol packages?

On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
mailto:dgreenw...@gmail.com>> wrote:
We noticed mysql did an upgrade to 5.7

On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:


On 27.11.19 18:15, Daniel Greenwald wrote:
yes tls is loaded before db_mysql, is that bad?
Not, tls before any other modules potentially using libssl is the right order.

Yes apt updates were run so could have been updates to anything. OS version is 
16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last run a couple of 
weeks ago.

Upon further digging I think the tls change was released a couple weeks ago so 
yes probably unrelated.



Install the packages with debug symbols for kamailio, libmysqlclient and 
libssl/libcrypto, then grab again the "bt full", it should show more details in 
the backtrace that may help to identify the issue.

Cheers,
Daniel





On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:

The issue seems to come from libmysqlclient library, not to kamailio handling 
sip traffic over tls.

Is tls module loaded before the db_mysql module?

Have you made other updates to the operating system? Or only the change you 
mentioned about server requiring and verifying certificates?

What version of ubuntu do you run?

I see that it uses libssl 1.0, so it is no relation with the change in libssl 
1.1 internal api.

Cheers,
Daniel
On 27.11.19 17:38, Daniel Greenwald wrote:
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f 
/etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or directory.
(gdb) bt
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
#1  0x7fc864920b79 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x7fc86492117a in lh_retrieve () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#3  0x7fc864923651 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#4  0x7fc8649240de in ERR_get_state () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#5  0x7fc864924326 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#6  0x7fc864c8a8e0 in SSL_get_error () from 
/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x7fc843831cbc in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#8  0x7fc84380d078 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#9  0x7fc84380d317 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#10 0x7fc84380e09c in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#11 0x7fc843801fe7 in ?? () from

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

Thanks we ended up downgrading the mysql packages to 5.7.11-0ubuntu6 and
seems to have resolved the issue.Seems the latest package caused craziness.
Warning to others..

On Wed, Nov 27, 2019 at 2:07 PM Henning Westerholt  wrote:

> Hello,
>
>
>
> This one package should contain all (packaged) debug info.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
> Kamailio Merchandising – https://skalatan.de/merchandising
>
>
>
> *From:* Daniel Greenwald 
> *Sent:* Wednesday, November 27, 2019 7:55 PM
> *To:* Henning Westerholt 
> *Cc:* Kamailio (SER) - Users Mailing List ;
> mico...@gmail.com
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> Yeah Yeah but what about the modules? Are there dbg packages for those, I
> don't see them?
>
>
>
> On Wed, Nov 27, 2019 at 1:27 PM Henning Westerholt  wrote:
>
> With google?  The package is called kamailio-dbg
>
>
>
>
> https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages
>
>
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
> Kamailio Merchandising – https://skalatan.de/merchandising
>
>
>
> *From:* sr-users  *On Behalf Of *Daniel
> Greenwald
> *Sent:* Wednesday, November 27, 2019 6:36 PM
> *To:* Daniel-Constantin Mierla 
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> How do I install the symbol packages?
>
>
>
> On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
> wrote:
>
> We noticed mysql did an upgrade to 5.7
>
>
>
> On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>
>
> On 27.11.19 18:15, Daniel Greenwald wrote:
>
> yes tls is loaded before db_mysql, is that bad?
>
> Not, tls before any other modules potentially using libssl is the right
> order.
>
>
>
> Yes apt updates were run so could have been updates to anything. OS
> version is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last
> run a couple of weeks ago.
>
>
>
> Upon further digging I think the tls change was released a couple weeks
> ago so yes probably unrelated.
>
>
>
> Install the packages with debug symbols for kamailio, libmysqlclient and
> libssl/libcrypto, then grab again the "bt full", it should show more
> details in the backtrace that may help to identify the issue.
>
> Cheers,
> Daniel
>
>
>
>
>
>
>
>
>
> On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
> The issue seems to come from libmysqlclient library, not to kamailio
> handling sip traffic over tls.
>
> Is tls module loaded before the db_mysql module?
>
> Have you made other updates to the operating system? Or only the change
> you mentioned about server requiring and verifying certificates?
>
> What version of ubuntu do you run?
>
> I see that it uses libssl 1.0, so it is no relation with the change in
> libssl 1.1 internal api.
>
> Cheers,
> Daniel
>
> On 27.11.19 17:38, Daniel Greenwald wrote:
>
> Core was generated by `/usr/sbin/kamailio -P
> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> 681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
> directory.
> (gdb) bt
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> #1  0x7fc864920b79 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #2  0x7fc86492117a in lh_retrieve () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #3  0x7fc864923651 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #4  0x7fc8649240de in ERR_get_state () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #5  0x7fc864924326 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #6  0x7fc864c8a8e0 in SSL_get_error () from
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> #7  0x7fc843831cbc in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #8  0x7fc84380d078 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #9  0x7fc84380d317 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #10 0x7fc84380e09c in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #11 0x7fc843801fe7 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #12 0x7fc8438030d8 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #13 0x7fc843804e36 in mysql_real_query () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #14 0x7fc843db0f76 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #15 0x7fc8433bbb79 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #16 0x7fc8433bf95b in db_do_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #17 0x7fc843db5a86 in db_mysql_update () from
>

Re: [SR-Users] Kamailio developers meeting - follow up remarks

2019-11-27 Thread Henning Westerholt

Hello,

Great summary, thanks Daniel and Giacomo. If people are interested about seeing 
some pictures from the two days and the evening event - I've added some to my 
blog (with some delay due to traveling): 
https://skalatan.de/en/blog/kamailio-hackathon-2019 

Cheers,

Henning

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

-Original Message-
From: sr-users  On Behalf Of 
Daniel-Constantin Mierla
Sent: Friday, November 22, 2019 9:59 AM
To: Kamailio (SER) - Devel Mailing List ; Kamailio 
(SER) - Users Mailing List 
Subject: [SR-Users] Kamailio developers meeting - follow up remarks

Hello,

last week we had the 2nd annual Kamailio Developers Meeting hosted by Sipgate 
in Dusseldorf, Germany:

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

16 people were at the event in various roles.

Giacomo Vacca published on his blog a good summary of what happened there:

  *
https://www.giacomovacca.com/2019/11/my-notes-on-kamailio-developer-meeting.html

This year we had a lot of discussions, as well as work done on multiple planes, 
not only Kamailio code. So I am trying to list here some of the conclusions for 
future development, the technical aspects of the meeting, so everyone is aware 
and can provide feedback.

1) Effective work was done on:

  * kamailio code
  * kamailio rpm packaging
  * kamailio tools (kamctl)
  * kamailio release process
  * kamailio project keys (to be used to sign the packages)

2) Documentation

2.a) Wiki

  * it was somehow a rough consensus to move the wiki content to github, along 
with changing the format from dokuwiki markdown to the standard/github 
markdown. This should enable people to make pull requests so developers or 
community members can review and aprove new content. It also makes it easier to 
contribute using existing github account, now the kamailio.org/wiki is 
requiring to make a dedicated account, which many prefer not to do it.

  * the presentation can be done either by using mkdocs to generate html files 
hosted on kamailio.org or using the github provided wiki portal.

 2.b) Docs for variables and transformations

  * there was a proposal to move them in the documentation the modules that 
export them, there are pros and cons, needs more discussions. Now they are in 
the wiki, so this probably has to resume after deciding on 2.a).

3) Kamailio Modules

3.a) replication (dmq) - several participants discussed about negotiations 
between nodes to take active role on some cases (e.g., active dialogs)

3.b) api integration - quite some interest in JSON-based API routing, 
concluding in extending rtjson to cover more use cases

3.c) security - have options to restrict the use of TLS1.3 or newer

4) Kamailio Releases

  * v5.3.2 was released during the event, allowing to document the process
  * work to automatize the process is planned, then eventually assing teams for 
takeing cares of releases from specific branches

5) Kamailio Testing

  * existing docker-based testing framework should be extended and integrated 
in CD/CI pipeline

6) Kamailio packages

6.a) rpms

  * rpm.kamailio.org has been prepared and is expected to take over the 
opensuse build service for building rpms and hosting them. Expected to provide 
support for hosting many kamailio versions in the same release series so one 
can do downgrade to older releases. Also, there is work in progress to provide 
nightly builds.

6.b) debs

  * work is planned to offer many kamailio versions in the same release series

7) Kamailio tools

  * kamctl/kamdbctl should be obsoleted in favor of kamcli, which offers a 
better framework for input validation and output formatting, as well as better 
portability, no longer depending on shell interpreter

8) Various discussions

  * kemi exports from C point of view and how to combine the documentation for 
modules and their kemi exports
  * how to make kamaiio friendlier in virtualized environments (ended up in the 
need of making the use of advertised address a bit more dynamic)
  * project organizatoric topics - to be approached separately
  * next events - Fosdem - someone should submit a proposal to present about 
Kamailio

9) Long term goals

We speak here more or less about Kamailio 6.0 ...

  * change the behaviour of the native config interpreter to be consistent with 
the other programming languages in terms of handling the response code (change 
what is now: the evaluation of negative value to false and positive value to 
true and the hidden return 0 to exit)

  * make the pool of processes more generic, so they can handle traffic from 
more sockets (being sip traffic or something else) -- this should make better 
use of resources, as some sockets might be less busy that others

I hope I covered the important topics, if I remember something else, I will 
reply on this thread. Or maybe other participants can contribute missing topics.

Should anyone have comments or suggestions on the above topics,

Re: [SR-Users] Possible conflict between t_newtran and setflag for ACC

2019-11-27 Thread Henning Westerholt

Hello,

usually it is not needed anymore to do this t_newtran early in the cfg. Check 
this discussion from 2015 out:

http://sip-router.1086192.n5.nabble.com/Transaction-good-practices-with-t-relay-t-newtran-and-t-release-td137433.html

There is also another function in tmx, t_precheck_trans which can be used to 
detect re-transmissions without actually creating a new one.

Cheers,

Henning

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

From: sr-users  On Behalf Of Patrick Wakano
Sent: Wednesday, November 27, 2019 3:26 AM
To: Kamailio (SER) - Users Mailing List 
Subject: [SR-Users] Possible conflict between t_newtran and setflag for ACC

Hello list,
Hope you all doing well!

I am using the ACC module and using the setflag() function as done in several 
examples. It works fine. However, I've added the t_newtran() function almost in 
the begging of the INVITE handler to help the retransmission detection and 
after that I noticed the ACC was not saving anything in DB.
So after debugging I discovered that if I call the t_newtran() before setting 
the ACC flags, the module will not save the calls in DB, but if I call it after 
setting the ACC flags, it works
So my question is, is this a bug or it is a expected side effect so when one is 
using t_newtran you must be careful and set all your transaction flags before? 
(ACC are the only transaction flags I am using so can't tell if other modules 
have the same problem)
This is happening in Kamailio 5.2.2.

Thank you!
Kind regards,
Patrick Wakano
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio xavp_contact - Segmentation Fault

2019-11-27 Thread Henning Westerholt

Hello,

Thank you - please open a bug report on our tracker about this problem with the 
info you provided in the e-mail.

Cheers,

Henning

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


From: sr-users  On Behalf Of Ilie Soltanici
Sent: Wednesday, November 27, 2019 8:00 PM
To: Kamailio (SER) - Users Mailing List 
Subject: [SR-Users] Kamailio xavp_contact - Segmentation Fault

Hello,

Kamailio is crashing when i'm trying to set the parameter;

modparam("tm|usrloc", "xavp_contact", "ulattrs")
That's happening with Kamailio 5.3.1 and 5.2.5 too.

Crash is happening when Im register 2 devices with the same extension.

This is the core dump:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/kamailio -P 
/var/run/kamailio/kamailio.pid -f /usr/local/etc/ka'.
Program terminated with signal 11, Segmentation fault.
#0  0x0057cca2 in xavp_get_internal (name=0x8, list=0x0, idx=0, 
prv=0x0) at core/xavp.c:288
288 core/xavp.c: No such file or directory.

(gdb) bt
#0  0x0057cca2 in xavp_get_internal (name=0x8, list=0x0, idx=0, 
prv=0x0) at core/xavp.c:288
#1  0x00581869 in xavp_insert (xavp=0x0, idx=0, list=0x0) at 
core/xavp.c:752
#2  0x7f05be0ee3a1 in ki_t_next_contacts (msg=0x7f05cb76c218) at 
t_serial.c:552
#3  0x7f05be0f09e8 in t_next_contacts (msg=0x7f05cb76c218, key=0x0, 
value=0x0) at t_serial.c:756
#4  0x00434d41 in do_action (h=0x7ffe93c9cad0, a=0x7f05cb642250, 
msg=0x7f05cb76c218) at core/action.c:1067
#5  0x004418e8 in run_actions (h=0x7ffe93c9cad0, a=0x7f05cb642250, 
msg=0x7f05cb76c218) at core/action.c:1572
#6  0x00441fa9 in run_actions_safe (h=0x7ffe93c9de90, a=0x7f05cb642250, 
msg=0x7f05cb76c218) at core/action.c:1636
#7  0x0065734e in rval_get_int (h=0x7ffe93c9de90, msg=0x7f05cb76c218, 
i=0x7ffe93c9cf78, rv=0x7f05cb642570, cache=0x0) at core/rvalue.c:912
#8  0x0065b8fe in rval_expr_eval_int (h=0x7ffe93c9de90, 
msg=0x7f05cb76c218, res=0x7ffe93c9cf78, rve=0x7f05cb642568) at 
core/rvalue.c:1910
#9  0x0065bd51 in rval_expr_eval_int (h=0x7ffe93c9de90, 
msg=0x7f05cb76c218, res=0x7ffe93c9d42c, rve=0x7f05cb642c98) at 
core/rvalue.c:1918
#10 0x00434807 in do_action (h=0x7ffe93c9de90, a=0x7f05cb645028, 
msg=0x7f05cb76c218) at core/action.c:1043
#11 0x004418e8 in run_actions (h=0x7ffe93c9de90, a=0x7f05cb637e48, 
msg=0x7f05cb76c218) at core/action.c:1572
#12 0x00431767 in do_action (h=0x7ffe93c9de90, a=0x7f05cb583858, 
msg=0x7f05cb76c218) at core/action.c:691
#13 0x004418e8 in run_actions (h=0x7ffe93c9de90, a=0x7f05cb574750, 
msg=0x7f05cb76c218) at core/action.c:1572
#14 0x00442071 in run_top_route (a=0x7f05cb574750, msg=0x7f05cb76c218, 
c=0x0) at core/action.c:1657
#15 0x005874a9 in receive_msg (buf=0xa6ec00  "OPTIONS 
sip:10@192.168.0.231:5060 SIP/2.0\r\nVia: 
SIP/2.0/UDP 
192.168.0.231;branch=z9hG4bKd8a9.1b3abe656532065414a2f35a8916008d.1\r\nVia: 
SIP/2.0/UDP 192.168.0.131:5060;received=192.168.0.131;branch=z9hG"...,
len=694, rcv_info=0x7ffe93c9e4d0) at core/receive.c:341
#16 0x0047bf81 in udp_rcv_loop () at core/udp_server.c:541
#17 0x00424f9d in main_loop () at main.c:1669
#18 0x0042c688 in main (argc=13, argv=0x7ffe93c9ea18) at main.c:2710

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

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Henning Westerholt

Hello,

This one package should contain all (packaged) debug info.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising

From: Daniel Greenwald 
Sent: Wednesday, November 27, 2019 7:55 PM
To: Henning Westerholt 
Cc: Kamailio (SER) - Users Mailing List ; 
mico...@gmail.com
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

Yeah Yeah but what about the modules? Are there dbg packages for those, I don't 
see them?

On Wed, Nov 27, 2019 at 1:27 PM Henning Westerholt 
mailto:h...@skalatan.de>> wrote:
With google?  The package is called kamailio-dbg

https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages


--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising

From: sr-users 
mailto:sr-users-boun...@lists.kamailio.org>>
 On Behalf Of Daniel Greenwald
Sent: Wednesday, November 27, 2019 6:36 PM
To: Daniel-Constantin Mierla mailto:mico...@gmail.com>>
Cc: Kamailio (SER) - Users Mailing List 
mailto:sr-users@lists.kamailio.org>>
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

How do I install the symbol packages?

On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
mailto:dgreenw...@gmail.com>> wrote:
We noticed mysql did an upgrade to 5.7

On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:


On 27.11.19 18:15, Daniel Greenwald wrote:
yes tls is loaded before db_mysql, is that bad?
Not, tls before any other modules potentially using libssl is the right order.

Yes apt updates were run so could have been updates to anything. OS version is 
16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last run a couple of 
weeks ago.

Upon further digging I think the tls change was released a couple weeks ago so 
yes probably unrelated.



Install the packages with debug symbols for kamailio, libmysqlclient and 
libssl/libcrypto, then grab again the "bt full", it should show more details in 
the backtrace that may help to identify the issue.

Cheers,
Daniel





On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:

The issue seems to come from libmysqlclient library, not to kamailio handling 
sip traffic over tls.

Is tls module loaded before the db_mysql module?

Have you made other updates to the operating system? Or only the change you 
mentioned about server requiring and verifying certificates?

What version of ubuntu do you run?

I see that it uses libssl 1.0, so it is no relation with the change in libssl 
1.1 internal api.

Cheers,
Daniel
On 27.11.19 17:38, Daniel Greenwald wrote:
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f 
/etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or directory.
(gdb) bt
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
#1  0x7fc864920b79 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x7fc86492117a in lh_retrieve () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#3  0x7fc864923651 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#4  0x7fc8649240de in ERR_get_state () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#5  0x7fc864924326 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#6  0x7fc864c8a8e0 in SSL_get_error () from 
/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x7fc843831cbc in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#8  0x7fc84380d078 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#9  0x7fc84380d317 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#10 0x7fc84380e09c in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#11 0x7fc843801fe7 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#12 0x7fc8438030d8 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#13 0x7fc843804e36 in mysql_real_query () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#14 0x7fc843db0f76 in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#15 0x7fc8433bbb79 in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#16 0x7fc8433bf95b in db_do_update () from 
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#17 0x7fc843db5a86 in db_mysql_update () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#19 0x7fc83f22aad3 in update_dialog_dbinfo () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#20 0x7fc83f21a065 in dlg_onroute () from

[SR-Users] Kamailio xavp_contact - Segmentation Fault

2019-11-27 Thread Ilie Soltanici

Hello,

Kamailio is crashing when i'm trying to set the parameter;

modparam("tm|usrloc", "xavp_contact", "ulattrs")

That's happening with Kamailio 5.3.1 and 5.2.5 too.

Crash is happening when Im register 2 devices with the same extension.

This is the core dump:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/sbin/kamailio -P
/var/run/kamailio/kamailio.pid -f /usr/local/etc/ka'.
Program terminated with signal 11, Segmentation fault.
#0  0x0057cca2 in xavp_get_internal (name=0x8, list=0x0, idx=0,
prv=0x0) at core/xavp.c:288
288 core/xavp.c: No such file or directory.

(gdb) bt
#0  0x0057cca2 in xavp_get_internal (name=0x8, list=0x0, idx=0,
prv=0x0) at core/xavp.c:288
#1  0x00581869 in xavp_insert (xavp=0x0, idx=0, list=0x0) at
core/xavp.c:752
#2  0x7f05be0ee3a1 in ki_t_next_contacts (msg=0x7f05cb76c218) at
t_serial.c:552
#3  0x7f05be0f09e8 in t_next_contacts (msg=0x7f05cb76c218, key=0x0,
value=0x0) at t_serial.c:756
#4  0x00434d41 in do_action (h=0x7ffe93c9cad0, a=0x7f05cb642250,
msg=0x7f05cb76c218) at core/action.c:1067
#5  0x004418e8 in run_actions (h=0x7ffe93c9cad0, a=0x7f05cb642250,
msg=0x7f05cb76c218) at core/action.c:1572
#6  0x00441fa9 in run_actions_safe (h=0x7ffe93c9de90,
a=0x7f05cb642250, msg=0x7f05cb76c218) at core/action.c:1636
#7  0x0065734e in rval_get_int (h=0x7ffe93c9de90,
msg=0x7f05cb76c218, i=0x7ffe93c9cf78, rv=0x7f05cb642570, cache=0x0) at
core/rvalue.c:912
#8  0x0065b8fe in rval_expr_eval_int (h=0x7ffe93c9de90,
msg=0x7f05cb76c218, res=0x7ffe93c9cf78, rve=0x7f05cb642568) at
core/rvalue.c:1910
#9  0x0065bd51 in rval_expr_eval_int (h=0x7ffe93c9de90,
msg=0x7f05cb76c218, res=0x7ffe93c9d42c, rve=0x7f05cb642c98) at
core/rvalue.c:1918
#10 0x00434807 in do_action (h=0x7ffe93c9de90, a=0x7f05cb645028,
msg=0x7f05cb76c218) at core/action.c:1043
#11 0x004418e8 in run_actions (h=0x7ffe93c9de90, a=0x7f05cb637e48,
msg=0x7f05cb76c218) at core/action.c:1572
#12 0x00431767 in do_action (h=0x7ffe93c9de90, a=0x7f05cb583858,
msg=0x7f05cb76c218) at core/action.c:691
#13 0x004418e8 in run_actions (h=0x7ffe93c9de90, a=0x7f05cb574750,
msg=0x7f05cb76c218) at core/action.c:1572
#14 0x00442071 in run_top_route (a=0x7f05cb574750,
msg=0x7f05cb76c218, c=0x0) at core/action.c:1657
#15 0x005874a9 in receive_msg (buf=0xa6ec00  "OPTIONS
sip:10@192.168.0.231:5060 SIP/2.0\r\nVia: SIP/2.0/UDP
192.168.0.231;branch=z9hG4bKd8a9.1b3abe656532065414a2f35a8916008d.1\r\nVia:
SIP/2.0/UDP 192.168.0.131:5060;received=192.168.0.131;branch=z9hG"...,
len=694, rcv_info=0x7ffe93c9e4d0) at core/receive.c:341
#16 0x0047bf81 in udp_rcv_loop () at core/udp_server.c:541
#17 0x00424f9d in main_loop () at main.c:1669
#18 0x0042c688 in main (argc=13, argv=0x7ffe93c9ea18) at main.c:2710

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

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

Yeah Yeah but what about the modules? Are there dbg packages for those, I
don't see them?

On Wed, Nov 27, 2019 at 1:27 PM Henning Westerholt  wrote:

> With google?  The package is called kamailio-dbg
>
>
>
>
> https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages
>
>
>
>
>
> --
>
> Henning Westerholt – https://skalatan.de/blog/
>
> Kamailio services – https://gilawa.com
>
> Kamailio Merchandising – https://skalatan.de/merchandising
>
>
>
> *From:* sr-users  *On Behalf Of *Daniel
> Greenwald
> *Sent:* Wednesday, November 27, 2019 6:36 PM
> *To:* Daniel-Constantin Mierla 
> *Cc:* Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] Kamailio 5.2.3 segfaulting
>
>
>
> How do I install the symbol packages?
>
>
>
> On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
> wrote:
>
> We noticed mysql did an upgrade to 5.7
>
>
>
> On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>
>
> On 27.11.19 18:15, Daniel Greenwald wrote:
>
> yes tls is loaded before db_mysql, is that bad?
>
> Not, tls before any other modules potentially using libssl is the right
> order.
>
>
>
> Yes apt updates were run so could have been updates to anything. OS
> version is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last
> run a couple of weeks ago.
>
>
>
> Upon further digging I think the tls change was released a couple weeks
> ago so yes probably unrelated.
>
>
>
> Install the packages with debug symbols for kamailio, libmysqlclient and
> libssl/libcrypto, then grab again the "bt full", it should show more
> details in the backtrace that may help to identify the issue.
>
> Cheers,
> Daniel
>
>
>
>
>
>
>
>
>
> On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
> The issue seems to come from libmysqlclient library, not to kamailio
> handling sip traffic over tls.
>
> Is tls module loaded before the db_mysql module?
>
> Have you made other updates to the operating system? Or only the change
> you mentioned about server requiring and verifying certificates?
>
> What version of ubuntu do you run?
>
> I see that it uses libssl 1.0, so it is no relation with the change in
> libssl 1.1 internal api.
>
> Cheers,
> Daniel
>
> On 27.11.19 17:38, Daniel Greenwald wrote:
>
> Core was generated by `/usr/sbin/kamailio -P
> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> 681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
> directory.
> (gdb) bt
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> #1  0x7fc864920b79 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #2  0x7fc86492117a in lh_retrieve () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #3  0x7fc864923651 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #4  0x7fc8649240de in ERR_get_state () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #5  0x7fc864924326 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #6  0x7fc864c8a8e0 in SSL_get_error () from
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> #7  0x7fc843831cbc in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #8  0x7fc84380d078 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #9  0x7fc84380d317 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #10 0x7fc84380e09c in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #11 0x7fc843801fe7 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #12 0x7fc8438030d8 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #13 0x7fc843804e36 in mysql_real_query () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #14 0x7fc843db0f76 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #15 0x7fc8433bbb79 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #16 0x7fc8433bf95b in db_do_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #17 0x7fc843db5a86 in db_mysql_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #19 0x7fc83f22aad3 in update_dialog_dbinfo () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #20 0x7fc83f21a065 in dlg_onroute () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #21 0x7fc841017917 in run_rr_callbacks () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #22 0x7fc84100c0dd in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #23 0x7fc84100c7aa in loose_route () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #24 0x7fc84100ffb5 in ?? () from
>

[SR-Users] Kamailio Parrallel Forking

2019-11-27 Thread Ilie Soltanici

Hello,

I'm trying to use parallel forking if one extension is registered from
multiple devices. (using WebSockets)

This is the related code from kamailio.cfg:


if (!t_load_contacts()) {
  xlogl("L_WARN", "Error loading contacts for $rU\n");
  sl_send_reply("500", "Server Internal Error (Code:$cfg(line))");
  exit;
  } else {
  xlogl("L_INFO", "Contacts loaded for $rU\n");
  }

  if (!t_next_contacts()) {
  xlogl("L_INFO", "t_next_contacts - Only one contact found for $rU,
calling\n");
  } else {
  xlogl("L_INFO", "t_next_contacts - Multiple contacts found, parallel
forking\n");
  }

  route(RELAY);



I noticed that on Kamailio 5.2.5 - this code is working fine, and Kamailio
is sending an INVITE to both Devices.But, on Kamailio 5.3.1 - that's not
working anymore. For some reason, kamailio is sending just one INVITE to
one device with wrong URI. The URI is set to the second device instead of
the correct one.

Was something changed in the t_next_contacts function related to this?
Thank you
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Henning Westerholt

With google?  The package is called kamailio-dbg

https://www.google.com/search?source=hp=rL3eXfK2Gqj3qwHg6rGACw=kamailio+debian+debug+packages=kamailio+debian+debug+packages


--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising

From: sr-users  On Behalf Of Daniel 
Greenwald
Sent: Wednesday, November 27, 2019 6:36 PM
To: Daniel-Constantin Mierla 
Cc: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Kamailio 5.2.3 segfaulting

How do I install the symbol packages?

On Wed, Nov 27, 2019 at 12:23 PM Daniel Greenwald 
mailto:dgreenw...@gmail.com>> wrote:
We noticed mysql did an upgrade to 5.7

On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:


On 27.11.19 18:15, Daniel Greenwald wrote:
yes tls is loaded before db_mysql, is that bad?
Not, tls before any other modules potentially using libssl is the right order.


Yes apt updates were run so could have been updates to anything. OS version is 
16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last run a couple of 
weeks ago.

Upon further digging I think the tls change was released a couple weeks ago so 
yes probably unrelated.



Install the packages with debug symbols for kamailio, libmysqlclient and 
libssl/libcrypto, then grab again the "bt full", it should show more details in 
the backtrace that may help to identify the issue.

Cheers,
Daniel





On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla 
mailto:mico...@gmail.com>> wrote:

The issue seems to come from libmysqlclient library, not to kamailio handling 
sip traffic over tls.

Is tls module loaded before the db_mysql module?

Have you made other updates to the operating system? Or only the change you 
mentioned about server requiring and verifying certificates?

What version of ubuntu do you run?

I see that it uses libssl 1.0, so it is no relation with the change in libssl 
1.1 internal api.

Cheers,
Daniel
On 27.11.19 17:38, Daniel Greenwald wrote:
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f 
/etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or directory.
(gdb) bt
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
#1  0x7fc864920b79 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x7fc86492117a in lh_retrieve () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#3  0x7fc864923651 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#4  0x7fc8649240de in ERR_get_state () from 
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#5  0x7fc864924326 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#6  0x7fc864c8a8e0 in SSL_get_error () from 
/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x7fc843831cbc in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#8  0x7fc84380d078 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#9  0x7fc84380d317 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#10 0x7fc84380e09c in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#11 0x7fc843801fe7 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#12 0x7fc8438030d8 in ?? () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#13 0x7fc843804e36 in mysql_real_query () from 
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#14 0x7fc843db0f76 in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#15 0x7fc8433bbb79 in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#16 0x7fc8433bf95b in db_do_update () from 
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#17 0x7fc843db5a86 in db_mysql_update () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#19 0x7fc83f22aad3 in update_dialog_dbinfo () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#20 0x7fc83f21a065 in dlg_onroute () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#21 0x7fc841017917 in run_rr_callbacks () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#22 0x7fc84100c0dd in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#23 0x7fc84100c7aa in loose_route () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#24 0x7fc84100ffb5 in ?? () from 
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#25 0x00480a22 in do_action ()
#26 0x0048db3f in run_actions ()
#27 0x0048e1fa in run_actions_safe ()
#28 0x00450aed in rval_get_int ()
#29 0x004551ed in rval_expr_eval_int ()
#30 0x004804d0 in do_action ()
#31 0x0048db3f in run_actions ()
#32 0x0047d2a3 in do_action ()

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

We noticed mysql did an upgrade to 5.7

On Wed, Nov 27, 2019 at 12:19 PM Daniel-Constantin Mierla 
wrote:

>
> On 27.11.19 18:15, Daniel Greenwald wrote:
>
> yes tls is loaded before db_mysql, is that bad?
>
> Not, tls before any other modules potentially using libssl is the right
> order.
>
>
> Yes apt updates were run so could have been updates to anything. OS
> version is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last
> run a couple of weeks ago.
>
> Upon further digging I think the tls change was released a couple weeks
> ago so yes probably unrelated.
>
>
> Install the packages with debug symbols for kamailio, libmysqlclient and
> libssl/libcrypto, then grab again the "bt full", it should show more
> details in the backtrace that may help to identify the issue.
>
> Cheers,
> Daniel
>
>
>
>
>
> On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> The issue seems to come from libmysqlclient library, not to kamailio
>> handling sip traffic over tls.
>>
>> Is tls module loaded before the db_mysql module?
>>
>> Have you made other updates to the operating system? Or only the change
>> you mentioned about server requiring and verifying certificates?
>>
>> What version of ubuntu do you run?
>>
>> I see that it uses libssl 1.0, so it is no relation with the change in
>> libssl 1.1 internal api.
>>
>> Cheers,
>> Daniel
>> On 27.11.19 17:38, Daniel Greenwald wrote:
>>
>> Core was generated by `/usr/sbin/kamailio -P
>> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
>> 681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
>> directory.
>> (gdb) bt
>> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
>> #1  0x7fc864920b79 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #2  0x7fc86492117a in lh_retrieve () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #3  0x7fc864923651 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #4  0x7fc8649240de in ERR_get_state () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #5  0x7fc864924326 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #6  0x7fc864c8a8e0 in SSL_get_error () from
>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>> #7  0x7fc843831cbc in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #8  0x7fc84380d078 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #9  0x7fc84380d317 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #10 0x7fc84380e09c in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #11 0x7fc843801fe7 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #12 0x7fc8438030d8 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #13 0x7fc843804e36 in mysql_real_query () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #14 0x7fc843db0f76 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
>> #15 0x7fc8433bbb79 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
>> #16 0x7fc8433bf95b in db_do_update () from
>> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
>> #17 0x7fc843db5a86 in db_mysql_update () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
>> #18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #19 0x7fc83f22aad3 in update_dialog_dbinfo () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #20 0x7fc83f21a065 in dlg_onroute () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #21 0x7fc841017917 in run_rr_callbacks () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #22 0x7fc84100c0dd in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #23 0x7fc84100c7aa in loose_route () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #24 0x7fc84100ffb5 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #25 0x00480a22 in do_action ()
>> #26 0x0048db3f in run_actions ()
>> #27 0x0048e1fa in run_actions_safe ()
>> #28 0x00450aed in rval_get_int ()
>> #29 0x004551ed in rval_expr_eval_int ()
>> #30 0x004804d0 in do_action ()
>> #31 0x0048db3f in run_actions ()
>> #32 0x0047d2a3 in do_action ()
>> #33 0x0048db3f in run_actions ()
>> #34 0x0048e306 in run_top_route ()
>> #35 0x005b815c in receive_msg ()
>> #36 0x004ab07f in udp_rcv_loop ()
>> #37 0x0042533c in main_loop ()
>> ---Type  to continue, or q  to quit---
>> #38 0x0042cb3a in main ()
>>
>>
>> On Wed, Nov 27, 2019 at 11:10 AM Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>> You got a core file, logs show that:
>>>
>>>

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel-Constantin Mierla


On 27.11.19 18:15, Daniel Greenwald wrote:
> yes tls is loaded before db_mysql, is that bad?
Not, tls before any other modules potentially using libssl is the right
order.
>
> Yes apt updates were run so could have been updates to anything. OS
> version is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we
> last run a couple of weeks ago.
>
> Upon further digging I think the tls change was released a couple
> weeks ago so yes probably unrelated.


Install the packages with debug symbols for kamailio, libmysqlclient and
libssl/libcrypto, then grab again the "bt full", it should show more
details in the backtrace that may help to identify the issue.

Cheers,
Daniel


>
>
>
> On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> The issue seems to come from libmysqlclient library, not to
> kamailio handling sip traffic over tls.
>
> Is tls module loaded before the db_mysql module?
>
> Have you made other updates to the operating system? Or only the
> change you mentioned about server requiring and verifying
> certificates?
>
> What version of ubuntu do you run?
>
> I see that it uses libssl 1.0, so it is no relation with the
> change in libssl 1.1 internal api.
>
> Cheers,
> Daniel
>
> On 27.11.19 17:38, Daniel Greenwald wrote:
>> Core was generated by `/usr/sbin/kamailio -P
>> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  __memcmp_sse4_1 () at
>> ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
>> 681     ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file
>> or directory.
>> (gdb) bt
>> #0  __memcmp_sse4_1 () at
>> ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
>> #1  0x7fc864920b79 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #2  0x7fc86492117a in lh_retrieve () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #3  0x7fc864923651 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #4  0x7fc8649240de in ERR_get_state () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #5  0x7fc864924326 in ?? () from
>> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
>> #6  0x7fc864c8a8e0 in SSL_get_error () from
>> /lib/x86_64-linux-gnu/libssl.so.1.0.0
>> #7  0x7fc843831cbc in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #8  0x7fc84380d078 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #9  0x7fc84380d317 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #10 0x7fc84380e09c in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #11 0x7fc843801fe7 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #12 0x7fc8438030d8 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #13 0x7fc843804e36 in mysql_real_query () from
>> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
>> #14 0x7fc843db0f76 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
>> #15 0x7fc8433bbb79 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
>> #16 0x7fc8433bf95b in db_do_update () from
>> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
>> #17 0x7fc843db5a86 in db_mysql_update () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
>> #18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #19 0x7fc83f22aad3 in update_dialog_dbinfo () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #20 0x7fc83f21a065 in dlg_onroute () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
>> #21 0x7fc841017917 in run_rr_callbacks () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #22 0x7fc84100c0dd in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #23 0x7fc84100c7aa in loose_route () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #24 0x7fc84100ffb5 in ?? () from
>> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
>> #25 0x00480a22 in do_action ()
>> #26 0x0048db3f in run_actions ()
>> #27 0x0048e1fa in run_actions_safe ()
>> #28 0x00450aed in rval_get_int ()
>> #29 0x004551ed in rval_expr_eval_int ()
>> #30 0x004804d0 in do_action ()
>> #31 0x0048db3f in run_actions ()
>> #32 0x0047d2a3 in do_action ()
>> #33 0x0048db3f in run_actions ()
>> #34 0x0048e306 in run_top_route ()
>> #35 0x005b815c in receive_msg ()
>> #36 0x004ab07f in udp_rcv_loop ()
>> #37 0x0042533c in main_loop ()
>> ---Type  to continue, or q  to quit---
>>

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

yes tls is loaded before db_mysql, is that bad?

Yes apt updates were run so could have been updates to anything. OS version
is 16.04.6 LTS (GNU/Linux 4.4.0-1098-aws x86_64) Updates we last run a
couple of weeks ago.

Upon further digging I think the tls change was released a couple weeks ago
so yes probably unrelated.



On Wed, Nov 27, 2019 at 12:03 PM Daniel-Constantin Mierla 
wrote:

> The issue seems to come from libmysqlclient library, not to kamailio
> handling sip traffic over tls.
>
> Is tls module loaded before the db_mysql module?
>
> Have you made other updates to the operating system? Or only the change
> you mentioned about server requiring and verifying certificates?
>
> What version of ubuntu do you run?
>
> I see that it uses libssl 1.0, so it is no relation with the change in
> libssl 1.1 internal api.
>
> Cheers,
> Daniel
> On 27.11.19 17:38, Daniel Greenwald wrote:
>
> Core was generated by `/usr/sbin/kamailio -P
> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> 681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
> directory.
> (gdb) bt
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> #1  0x7fc864920b79 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #2  0x7fc86492117a in lh_retrieve () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #3  0x7fc864923651 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #4  0x7fc8649240de in ERR_get_state () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #5  0x7fc864924326 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #6  0x7fc864c8a8e0 in SSL_get_error () from
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> #7  0x7fc843831cbc in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #8  0x7fc84380d078 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #9  0x7fc84380d317 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #10 0x7fc84380e09c in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #11 0x7fc843801fe7 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #12 0x7fc8438030d8 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #13 0x7fc843804e36 in mysql_real_query () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #14 0x7fc843db0f76 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #15 0x7fc8433bbb79 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #16 0x7fc8433bf95b in db_do_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #17 0x7fc843db5a86 in db_mysql_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #19 0x7fc83f22aad3 in update_dialog_dbinfo () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #20 0x7fc83f21a065 in dlg_onroute () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #21 0x7fc841017917 in run_rr_callbacks () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #22 0x7fc84100c0dd in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #23 0x7fc84100c7aa in loose_route () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #24 0x7fc84100ffb5 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #25 0x00480a22 in do_action ()
> #26 0x0048db3f in run_actions ()
> #27 0x0048e1fa in run_actions_safe ()
> #28 0x00450aed in rval_get_int ()
> #29 0x004551ed in rval_expr_eval_int ()
> #30 0x004804d0 in do_action ()
> #31 0x0048db3f in run_actions ()
> #32 0x0047d2a3 in do_action ()
> #33 0x0048db3f in run_actions ()
> #34 0x0048e306 in run_top_route ()
> #35 0x005b815c in receive_msg ()
> #36 0x004ab07f in udp_rcv_loop ()
> #37 0x0042533c in main_loop ()
> ---Type  to continue, or q  to quit---
> #38 0x0042cb3a in main ()
>
>
> On Wed, Nov 27, 2019 at 11:10 AM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> You got a core file, logs show that:
>>
>> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
>> [main.c:764]: handle_sigs(): core was generated
>>
>> Locate it and send the full backtrace with gdb from it.
>>
>> Cheers,
>> Daniel
>> On 27.11.19 16:03, Daniel Greenwald wrote:
>>
>> I'm sorry you are correct, the version we are running is 5.2.5. I've just
>> run ulimit -c unlimited to hopefully get a core dump next time since I
>> don't see one in /var/lib/systemd/coredump/. Not sure if there is anything
>> I need to do to get a coredump.
>> The log just shows:
>>
>> 2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: 
>> [core/pass_fd.c:277]: receive_fd(): EOF

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel-Constantin Mierla

The issue seems to come from libmysqlclient library, not to kamailio
handling sip traffic over tls.

Is tls module loaded before the db_mysql module?

Have you made other updates to the operating system? Or only the change
you mentioned about server requiring and verifying certificates?

What version of ubuntu do you run?

I see that it uses libssl 1.0, so it is no relation with the change in
libssl 1.1 internal api.

Cheers,
Daniel

On 27.11.19 17:38, Daniel Greenwald wrote:
> Core was generated by `/usr/sbin/kamailio -P
> /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> 681     ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
> directory.
> (gdb) bt
> #0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
> #1  0x7fc864920b79 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #2  0x7fc86492117a in lh_retrieve () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #3  0x7fc864923651 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #4  0x7fc8649240de in ERR_get_state () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #5  0x7fc864924326 in ?? () from
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> #6  0x7fc864c8a8e0 in SSL_get_error () from
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> #7  0x7fc843831cbc in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #8  0x7fc84380d078 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #9  0x7fc84380d317 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #10 0x7fc84380e09c in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #11 0x7fc843801fe7 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #12 0x7fc8438030d8 in ?? () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #13 0x7fc843804e36 in mysql_real_query () from
> /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
> #14 0x7fc843db0f76 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #15 0x7fc8433bbb79 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #16 0x7fc8433bf95b in db_do_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
> #17 0x7fc843db5a86 in db_mysql_update () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
> #18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #19 0x7fc83f22aad3 in update_dialog_dbinfo () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #20 0x7fc83f21a065 in dlg_onroute () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
> #21 0x7fc841017917 in run_rr_callbacks () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #22 0x7fc84100c0dd in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #23 0x7fc84100c7aa in loose_route () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #24 0x7fc84100ffb5 in ?? () from
> /usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
> #25 0x00480a22 in do_action ()
> #26 0x0048db3f in run_actions ()
> #27 0x0048e1fa in run_actions_safe ()
> #28 0x00450aed in rval_get_int ()
> #29 0x004551ed in rval_expr_eval_int ()
> #30 0x004804d0 in do_action ()
> #31 0x0048db3f in run_actions ()
> #32 0x0047d2a3 in do_action ()
> #33 0x0048db3f in run_actions ()
> #34 0x0048e306 in run_top_route ()
> #35 0x005b815c in receive_msg ()
> #36 0x004ab07f in udp_rcv_loop ()
> #37 0x0042533c in main_loop ()
> ---Type  to continue, or q  to quit---
> #38 0x0042cb3a in main ()
>
>
> On Wed, Nov 27, 2019 at 11:10 AM Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> You got a core file, logs show that:
>
> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
> [main.c:764]: handle_sigs(): core was generated
>
> Locate it and send the full backtrace with gdb from it.
>
> Cheers,
> Daniel
>
> On 27.11.19 16:03, Daniel Greenwald wrote:
>> I'm sorry you are correct, the version we are running is 5.2.5.
>> I've just run ulimit -c unlimited to hopefully get a core dump
>> next time since I don't see one in /var/lib/systemd/coredump/.
>> Not sure if there is anything I need to do to get a coredump.
>> The log just shows:
>>
>> 2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: 
>> [core/pass_fd.c:277]: receive_fd(): EOF on 33
>> 2019-11-27T14:04:22.299092+00:00,ip-10-0-33-149: ALERT: 
>> [main.c:761]: handle_sigs(): child process 12674 exited by a
>> signal 11
>> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
>> [main.c:764]: handle_sigs(): core was generated
>> 2019-11-27T14:04:22.299564+00:00,ip-10-0-33-149: INFO: 
>> [main.c:787]:

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid
-f /etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
681 ../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or
directory.
(gdb) bt
#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:681
#1  0x7fc864920b79 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#2  0x7fc86492117a in lh_retrieve () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#3  0x7fc864923651 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#4  0x7fc8649240de in ERR_get_state () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#5  0x7fc864924326 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
#6  0x7fc864c8a8e0 in SSL_get_error () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0
#7  0x7fc843831cbc in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#8  0x7fc84380d078 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#9  0x7fc84380d317 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#10 0x7fc84380e09c in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#11 0x7fc843801fe7 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#12 0x7fc8438030d8 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#13 0x7fc843804e36 in mysql_real_query () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#14 0x7fc843db0f76 in ?? () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#15 0x7fc8433bbb79 in ?? () from
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#16 0x7fc8433bf95b in db_do_update () from
/usr/lib/x86_64-linux-gnu/kamailio/libsrdb1.so.1
#17 0x7fc843db5a86 in db_mysql_update () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/db_mysql.so
#18 0x7fc83f22a61b in update_dialog_dbinfo_unsafe () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#19 0x7fc83f22aad3 in update_dialog_dbinfo () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#20 0x7fc83f21a065 in dlg_onroute () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/dialog.so
#21 0x7fc841017917 in run_rr_callbacks () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#22 0x7fc84100c0dd in ?? () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#23 0x7fc84100c7aa in loose_route () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#24 0x7fc84100ffb5 in ?? () from
/usr/lib/x86_64-linux-gnu/kamailio/modules/rr.so
#25 0x00480a22 in do_action ()
#26 0x0048db3f in run_actions ()
#27 0x0048e1fa in run_actions_safe ()
#28 0x00450aed in rval_get_int ()
#29 0x004551ed in rval_expr_eval_int ()
#30 0x004804d0 in do_action ()
#31 0x0048db3f in run_actions ()
#32 0x0047d2a3 in do_action ()
#33 0x0048db3f in run_actions ()
#34 0x0048e306 in run_top_route ()
#35 0x005b815c in receive_msg ()
#36 0x004ab07f in udp_rcv_loop ()
#37 0x0042533c in main_loop ()
---Type  to continue, or q  to quit---
#38 0x0042cb3a in main ()


On Wed, Nov 27, 2019 at 11:10 AM Daniel-Constantin Mierla 
wrote:

> You got a core file, logs show that:
>
> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
> [main.c:764]: handle_sigs(): core was generated
>
> Locate it and send the full backtrace with gdb from it.
>
> Cheers,
> Daniel
> On 27.11.19 16:03, Daniel Greenwald wrote:
>
> I'm sorry you are correct, the version we are running is 5.2.5. I've just
> run ulimit -c unlimited to hopefully get a core dump next time since I
> don't see one in /var/lib/systemd/coredump/. Not sure if there is anything
> I need to do to get a coredump.
> The log just shows:
>
> 2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: 
> [core/pass_fd.c:277]: receive_fd(): EOF on 33
> 2019-11-27T14:04:22.299092+00:00,ip-10-0-33-149: ALERT: 
> [main.c:761]: handle_sigs(): child process 12674 exited by a signal 11
> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
> [main.c:764]: handle_sigs(): core was generated
> 2019-11-27T14:04:22.299564+00:00,ip-10-0-33-149: INFO: 
> [main.c:787]: handle_sigs(): terminating due to SIGCHLD
> 2019-11-27T14:04:22.299892+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300298+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300569+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300820+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301070+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301315+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301564+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel-Constantin Mierla

You got a core file, logs show that:

2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
[main.c:764]: handle_sigs(): core was generated

Locate it and send the full backtrace with gdb from it.

Cheers,
Daniel

On 27.11.19 16:03, Daniel Greenwald wrote:
> I'm sorry you are correct, the version we are running is 5.2.5. I've
> just run ulimit -c unlimited to hopefully get a core dump next time
> since I don't see one in /var/lib/systemd/coredump/. Not sure if there
> is anything I need to do to get a coredump.
> The log just shows:
>
> 2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: 
> [core/pass_fd.c:277]: receive_fd(): EOF on 33
> 2019-11-27T14:04:22.299092+00:00,ip-10-0-33-149: ALERT: 
> [main.c:761]: handle_sigs(): child process 12674 exited by a signal 11
> 2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
> [main.c:764]: handle_sigs(): core was generated
> 2019-11-27T14:04:22.299564+00:00,ip-10-0-33-149: INFO: 
> [main.c:787]: handle_sigs(): terminating due to SIGCHLD
> 2019-11-27T14:04:22.299892+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300298+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300569+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.300820+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301070+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301315+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301564+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.301823+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.302056+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.302277+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.302525+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.302773+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
> 2019-11-27T14:04:22.303020+00:00,ip-10-0-33-149: INFO: 
> [main.c:842]: sig_usr(): signal 15 received
>
> On Wed, Nov 27, 2019 at 9:49 AM Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> If you use the repo listed at http://deb.kamailio.org/ , then it
> should be 5.2.5, and there is also option to install 5.2 branch
> debs built nightly.
>
> Cheers,
> Daniel
>
> On 27.11.19 15:37, Daniel Greenwald wrote:
>> I'm using ubuntu packages, I believe 5.2.3 is latest?
>>
>> On Wed, Nov 27, 2019 at 9:34 AM Daniel-Constantin Mierla
>> mailto:mico...@gmail.com>> wrote:
>>
>> Hello,
>>
>> that log message is irrelevant for actual crash. Did you get
>> core files? Or other log messages before the one you pasted?
>>
>> You should upgrade first to latest 5.2.x, either 5.2.5 or
>> latest branch 5.2.
>>
>> Cheers,
>> Daniel
>>
>> On 27.11.19 15:22, Daniel Greenwald wrote:
>>> I'm seeing this in the log and kamailio is crashing every
>>> hour or so:
>>> CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
>>> 33/var/log/kamailio/kamailio.log
>>>
>>> Any ideas? Should I emergency upgrade to 5.3.1?
>>>
>>> ___
>>> 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 World Conference - April 27-29, 2020, in Berlin -- 
>> www.kamailioworld.com 
>>
> -- 
> Daniel-Constantin Mierla -- www.asipto.com 
> www.twitter.com/miconda  -- 
> www.linkedin.com/in/miconda 
> Kamailio World Conference - April 27-29, 2020, in Berlin -- 
> www.kamailioworld.com 
>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- 
www.kamailioworld.com

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

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

I'm sorry you are correct, the version we are running is 5.2.5. I've just
run ulimit -c unlimited to hopefully get a core dump next time since I
don't see one in /var/lib/systemd/coredump/. Not sure if there is anything
I need to do to get a coredump.
The log just shows:

2019-11-27T14:04:22.298010+00:00,ip-10-0-33-149: CRITICAL: 
[core/pass_fd.c:277]: receive_fd(): EOF on 33
2019-11-27T14:04:22.299092+00:00,ip-10-0-33-149: ALERT: 
[main.c:761]: handle_sigs(): child process 12674 exited by a signal 11
2019-11-27T14:04:22.299316+00:00,ip-10-0-33-149: ALERT: 
[main.c:764]: handle_sigs(): core was generated
2019-11-27T14:04:22.299564+00:00,ip-10-0-33-149: INFO:  [main.c:787]:
handle_sigs(): terminating due to SIGCHLD
2019-11-27T14:04:22.299892+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.300298+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.300569+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.300820+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.301070+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.301315+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.301564+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.301823+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.302056+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.302277+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.302525+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.302773+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received
2019-11-27T14:04:22.303020+00:00,ip-10-0-33-149: INFO:  [main.c:842]:
sig_usr(): signal 15 received

On Wed, Nov 27, 2019 at 9:49 AM Daniel-Constantin Mierla 
wrote:

> If you use the repo listed at http://deb.kamailio.org/ , then it should
> be 5.2.5, and there is also option to install 5.2 branch debs built nightly.
>
> Cheers,
> Daniel
> On 27.11.19 15:37, Daniel Greenwald wrote:
>
> I'm using ubuntu packages, I believe 5.2.3 is latest?
>
> On Wed, Nov 27, 2019 at 9:34 AM Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> that log message is irrelevant for actual crash. Did you get core files?
>> Or other log messages before the one you pasted?
>>
>> You should upgrade first to latest 5.2.x, either 5.2.5 or latest branch
>> 5.2.
>>
>> Cheers,
>> Daniel
>> On 27.11.19 15:22, Daniel Greenwald wrote:
>>
>> I'm seeing this in the log and kamailio is crashing every hour or so:
>> CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
>> 33/var/log/kamailio/kamailio.log
>>
>> Any ideas? Should I emergency upgrade to 5.3.1?
>>
>> ___
>> Kamailio (SER) - Users Mailing 
>> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
>> www.linkedin.com/in/miconda
>> Kamailio World Conference - April 27-29, 2020, in Berlin -- 
>> www.kamailioworld.com
>>
>> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
> Kamailio World Conference - April 27-29, 2020, in Berlin -- 
> www.kamailioworld.com
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel-Constantin Mierla

If you use the repo listed at http://deb.kamailio.org/ , then it should
be 5.2.5, and there is also option to install 5.2 branch debs built nightly.

Cheers,
Daniel

On 27.11.19 15:37, Daniel Greenwald wrote:
> I'm using ubuntu packages, I believe 5.2.3 is latest?
>
> On Wed, Nov 27, 2019 at 9:34 AM Daniel-Constantin Mierla
> mailto:mico...@gmail.com>> wrote:
>
> Hello,
>
> that log message is irrelevant for actual crash. Did you get core
> files? Or other log messages before the one you pasted?
>
> You should upgrade first to latest 5.2.x, either 5.2.5 or latest
> branch 5.2.
>
> Cheers,
> Daniel
>
> On 27.11.19 15:22, Daniel Greenwald wrote:
>> I'm seeing this in the log and kamailio is crashing every hour or so:
>> CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
>> 33/var/log/kamailio/kamailio.log
>>
>> Any ideas? Should I emergency upgrade to 5.3.1?
>>
>> ___
>> 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 World Conference - April 27-29, 2020, in Berlin -- 
> www.kamailioworld.com 
>
-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- 
www.kamailioworld.com

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

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

I'm using ubuntu packages, I believe 5.2.3 is latest?

On Wed, Nov 27, 2019 at 9:34 AM Daniel-Constantin Mierla 
wrote:

> Hello,
>
> that log message is irrelevant for actual crash. Did you get core files?
> Or other log messages before the one you pasted?
>
> You should upgrade first to latest 5.2.x, either 5.2.5 or latest branch
> 5.2.
>
> Cheers,
> Daniel
> On 27.11.19 15:22, Daniel Greenwald wrote:
>
> I'm seeing this in the log and kamailio is crashing every hour or so:
> CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
> 33/var/log/kamailio/kamailio.log
>
> Any ideas? Should I emergency upgrade to 5.3.1?
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
> Kamailio World Conference - April 27-29, 2020, in Berlin -- 
> www.kamailioworld.com
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel-Constantin Mierla

Hello,

that log message is irrelevant for actual crash. Did you get core files?
Or other log messages before the one you pasted?

You should upgrade first to latest 5.2.x, either 5.2.5 or latest branch 5.2.

Cheers,
Daniel

On 27.11.19 15:22, Daniel Greenwald wrote:
> I'm seeing this in the log and kamailio is crashing every hour or so:
> CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
> 33/var/log/kamailio/kamailio.log
>
> Any ideas? Should I emergency upgrade to 5.3.1?
>
> ___
> 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 World Conference - April 27-29, 2020, in Berlin -- 
www.kamailioworld.com

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

[SR-Users] Kamailio 5.2.3 segfaulting

2019-11-27 Thread Daniel Greenwald

I'm seeing this in the log and kamailio is crashing every hour or so:
CRITICAL:  [core/pass_fd.c:277]: receive_fd(): EOF on
33/var/log/kamailio/kamailio.log

Any ideas? Should I emergency upgrade to 5.3.1?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] How to enforce REGISTER with AKAv1 (IMS)

2019-11-27 Thread Moshe A

Hello,

How can we enforce REGISTER with AKAv1?

Here our setup

1. kamailio version 4.3.4 for IMS
2. Boghe IMS client v1.0.58.550
3. scscf.cfg is configure with:
#!define REG_AUTH_DEFAULT_ALG "AKAv1-MD5"
4. Set Authentication Schemes in Private User Identity - IMPI for user bob
to:
Digest-AKAv1 (3GPP)

results:
First REGISTER fails with 401 Unauthorized
Second REGISTER 200 OK, but the REGISTER is MD5 and not AKAv1


Attached is tcpdump.

By the way: in which DB should we find Authentication Schemes? can't find
it in hss_db, kamailio and not in scscf.

Thank you,
Moshe.


register-bob-4.pcap
Description: Binary data
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] No Audio using RTP Proxy

2019-11-27 Thread Karsten Horsmann

Hi Sujit,


you can use sngrep to inspect the sdp coming from the upstream sip gateways
and the answer that Kamailio creates.

This helps you to understand and debug.

Cheers
Karsten Horsmann

Sujit Roy  schrieb am Mi., 27. Nov. 2019, 07:13:

> Hello
>
> I am facing a problem as below. Please suggest for the work around.
>
> My call flow is like this.
>
> SIP Gateway-1 (IP x.179) -> SIP Gateway-2 ( IP x.177) -> Kamalio+RTPProxy
>
> So when the call arrives at Kamalio+RTPProxy, i m getting below in log.
>
> Nov 26 23:25:31 rtpproxy[18508]: INFO:GLOBAL:rtpp_command_ul_handle: new
> IPv4/IPv4 session 1b7c870763616c6c15fff410@ 192.168.100.177, tag
> 1aa18fc201a68168;1 requested, type strong
> Nov 26 23:25:31 rtpproxy[18508]: INFO:1b7c870763616c6c15fff410@
> 192.168.100.177:rtpp_command_ul_handle: new session on IPv4 port 15920
> created, tag 1aa18fc201a68168;1
> Nov 26 23:25:31 rtpproxy[18508]:
> INFO:1b7c870763616c6c15fff410@192.168.100.177:rtpp_stream_prefill_addr:
> pre-filling caller's RTP address with 192.168.100.177:27360
> Nov 26 23:25:31 rtpproxy[18508]: INFO:1b7c870763616c6c15fff410@
> 192.168.100.177:rtpp_stream_prefill_addr: pre-filling caller's RTCP
> address with 192.168.100.177:27361
>
> But x.177 is working on signalling mode only ( Not routing Media ) . As a
> result, i m not getting any voice from IP x.179
>
> What can be done to change the caller's RTP address to x.179 in RTPProxy ?
>
> Thanks
>
> --
> Regards
> ===
> Sujit Roy
>
> ___
> 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

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Possible conflict between t_newtran and setflag for ACC

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio developers meeting - follow up remarks

Re: [SR-Users] Possible conflict between t_newtran and setflag for ACC

Re: [SR-Users] Kamailio xavp_contact - Segmentation Fault

Re: [SR-Users] Kamailio 5.2.3 segfaulting

[SR-Users] Kamailio xavp_contact - Segmentation Fault

Re: [SR-Users] Kamailio 5.2.3 segfaulting

[SR-Users] Kamailio Parrallel Forking

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

Re: [SR-Users] Kamailio 5.2.3 segfaulting

[SR-Users] Kamailio 5.2.3 segfaulting

[SR-Users] How to enforce REGISTER with AKAv1 (IMS)

Re: [SR-Users] No Audio using RTP Proxy

25 matches

Site Navigation

Mail list logo

Footer information