Re: [OpenSIPS-Users] opensips udp workers lock up with sched_yield

2020-03-10 Thread Bogdan-Andrei Iancu
Hi William, I suspect you may hit some deadlock (most like a wild guess, as there is not much data to check). And the only advice I can give you is to upgrade to 2.4 (simple one) or 3.0 (a bit more complex). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-

Re: [OpenSIPS-Users] Presence 404 Not Here

2020-03-10 Thread Bogdan-Andrei Iancu
Hi, As the 404 Not Here is generated from script, I guess you have a scripting issue when comes to handling sequential requests, mainly sequential SUBSCRIBE requests without loose_route(). On the failing branch of the loose_route() test you should have test of SUBSCRIBE and trigger the presen

Re: [OpenSIPS-Users] Presence 404 Not Here

2020-03-10 Thread Social Boh
Thank you. Solved changing catchs SUBSCRIBE on if (has_totag()) { route. Regards --- I'm SoCIaL, MayBe El 10/03/2020 a las 03:55, Bogdan-Andrei Iancu escribió: Hi, As the 404 Not Here is generated from script, I guess you have a scripting issue when comes to handling sequential requests, m

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Liviu Chircu
On 10.03.2020 00:25, Calvin Ellison wrote: I also noticed DB_DOUBLE is missing from /avpops/avpops_db.c but I don't know C well enough to do the needful. Do you know what should be done to make it a string? Here's my updated /db_mysql/res.c. I did as you suggested and moved MYSQL_TYPE_NEWDECI

Re: [OpenSIPS-Users] SEG violation in 3.0.2

2020-03-10 Thread Liviu Chircu
On 07.03.2020 00:26, Robert Dyck wrote: The following configuration snippet worked for me in 2.4 but causes a coredump in 3.0.1 and 3.0.2. Hey, Robert! Sadly, I think this bug is caused by some debug printing log which is accessing invalid memory.  Can you try to up your "log_level" [1] to 3 a

Re: [OpenSIPS-Users] SEG violation in 3.0.2

2020-03-10 Thread Liviu Chircu
On 10.03.2020 18:09, Liviu Chircu wrote: Meanwhile, I'll get the bug fixed. Fixed on 2.4+. -- Liviu Chircu www.twitter.com/liviuchircu | www.opensips-solutions.com OpenSIPS Summit, Amsterdam, May 2020 www.opensips.org/events ___ Users mailing li

Re: [OpenSIPS-Users] Second Contact when sending 302 Redirect using async avp_db_query

2020-03-10 Thread Liviu Chircu
On 09.03.2020 18:37, Calvin Ellison wrote: After a moment of contemplation, I realized it makes sense that a 3xx response Contact would be based on the request URI In my case, it took almost 8 years of contemplation to realize this.  Looking at the "R-URI -> Contact for 3XX" code, it seems i

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Brett Nemeroff
Liviu, Thanks for the quick fix! I can’t believe this hasn’t been more of an issue. But then again, it may be a weird thing to want a double in the script context since you can’t or at least shouldn’t be doing a lot of high level stuff there. Calvin / Liviu, I haven’t tested this fix yet, but I re

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Liviu Chircu
On 10.03.2020 18:39, Brett Nemeroff wrote: This isn’t really a problem unless you are going to math it or push it into something else without casting it. I agree, but at script level, there is no support for manipulating "long" integers, let along "double" precision integers.  So casting the "

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Brett Nemeroff
Totally agree that this is the right thing to do. I just wanted the list to know it’s a STRING. I don’t think it’s obvious. Thanks again!! On Tue, Mar 10, 2020 at 11:45 AM Liviu Chircu wrote: > On 10.03.2020 18:39, Brett Nemeroff wrote: > > This isn’t really a problem unless you are going to m

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Calvin Ellison
The patch appears to be working as intended with regards to storing and later using the decimal value as a string: Mar 10 09:50:15 localhost /usr/sbin/opensips[27541]: DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x7f8ecd2b5d68)[14]=[delay] Mar 10 09:50:15 localhost /usr/sbin/opensips[27541]: DBG:

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Liviu Chircu
On 10.03.2020 19:07, Calvin Ellison wrote: However, when printed it appears as "0.001900". If that his how thing string would be passed to mathops, etc., it would cause problems for anyone interested in significant digits. Indeed, the "%lf" format specified in C truncates double numbers down t

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Brett Nemeroff
Liviu, My preference would be to default to 8, but make it defined in the header file for those who want to recompile it. 6 is ok, it’s usually the minimum precision that is acceptable. Thanks!! On Tue, Mar 10, 2020 at 12:19 PM Liviu Chircu wrote: > On 10.03.2020 19:07, Calvin Ellison wrote: >

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Calvin Ellison
On Tue, Mar 10, 2020 at 10:31 AM Brett Nemeroff wrote: > Liviu, > My preference would be to default to 8, but make it defined in the header > file for those who want to recompile it. 6 is ok, it’s usually the minimum > precision that is acceptable. > My comment about significant digits was with

Re: [OpenSIPS-Users] MySQL Type: FIELD_TYPE_NEWDECIMAL (246) uses DB_INT result type but should use float

2020-03-10 Thread Brett Nemeroff
Actually, I think that may be a good idea Liviu, Can you inspect the DB type to derive a precision for the STRING format? Then maybe default to 8 if you can't derive it? I think that gives us the best of everything. But it does require a column datatype inspection. What do you think? -Brett On Tue

Re: [OpenSIPS-Users] Public IP in REGISTER

2020-03-10 Thread Liviu Chircu
On 09.03.2020 02:24, Jehanzaib Younis wrote:               if (is_method("REGISTER")) {                         fix_nated_register();                         nat_keepalive(); Hi, Jehanzaib! Bingo!  This is the cause of your strange double-pinging. You are using two NAT pinging modules at the

Re: [OpenSIPS-Users] Opensips installation on Ubuntu 18.04

2020-03-10 Thread Liviu Chircu
On 23.02.2020 04:09, Anderson Catão wrote: Linking opensips main.o: In function `pthread_mutex_init': /usr/local/src/opensips-2.4.7/ssl_tweaks.h:32: undefined reference to `pthread_mutexattr_setpshared' Hey Anderson, Did you solve your problem?  Those symbols are typically provided by the "l