From jehanzaib.kiani at gmail.com  Mon Aug  2 00:53:17 2021
From: jehanzaib.kiani at gmail.com (Jehanzaib Younis)
Date: Mon, 2 Aug 2021 12:53:17 +1200
Subject: [OpenSIPS-Users] Search and Replace SIP header name
Message-ID: <CAKrJzCzCuY-RLJRr_h7mruTWTF4oV_ypFNDUZuV9_uQhjd11Wg@mail.gmail.com>

Hi experts,

I am running opensips 2.4.x  just checkin if there is a way to replace the
SIP header name?
I can see the remove_hf in the sipmsgops module but can't find a way to
replace the sip header name.
For example i have a header
H-ABC: <sip:test at 123.com>
i want to replace H-ABC to H-NEWABC


Regards,
Jehanzaib
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210802/9434dff4/attachment.html>

From social at bohboh.info  Mon Aug  2 01:30:35 2021
From: social at bohboh.info (Social Boh)
Date: Sun, 1 Aug 2021 20:30:35 -0500
Subject: [OpenSIPS-Users] Search and Replace SIP header name
In-Reply-To: <CAKrJzCzCuY-RLJRr_h7mruTWTF4oV_ypFNDUZuV9_uQhjd11Wg@mail.gmail.com>
Message-ID: <4df087bf-51b0-4e0c-8a9c-a388c610055f@iPhone-Andrea>

     
 

 you can first remove and then add
 
 
 
   
 

 
 
>  
> On Aug 1, 2021 at 19:56,  <Jehanzaib Younis (mailto:jehanzaib.kiani at gmail.com)>  wrote:
>  
>  
>  
> Hi experts, 
>
>  
> I am running opensips 2.4.x    just checkin if there is a way to replace the SIP header name?  
>  
> I can see the remove_hf in the sipmsgops module but can't find a way to replace the sip header name.  
>  
> For example i have a header  
>  
> H-ABC:  <sip:test at 123.com (mailto:sip%3Atest at 123.com)>
>  
> i want to replace H-ABC to H-NEWABC  
>  
>
>  
>
>  
>  
>  
> Regards,
>  
> Jehanzaib
>  
>  
>  
>  
>  
>  
 
 
     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210801/b0e81ebf/attachment.html>

From kurgan-rus at inbox.ru  Wed Aug  4 12:36:16 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Wed, 04 Aug 2021 15:36:16 +0300
Subject: [OpenSIPS-Users]
 =?utf-8?q?/usr/sbin/opensips=5B7617=5D=3A_ERROR?=
 =?utf-8?q?=3Aauth=5Fdb=3Aget=5Fha1=3A_failed_to_query_database_-_Errors?=
In-Reply-To: <SI2PR06MB4345C7DC54649A8B56638020CFE99@SI2PR06MB4345.apcprd06.prod.outlook.com>
References: <SI2PR06MB4345C7DC54649A8B56638020CFE99@SI2PR06MB4345.apcprd06.prod.outlook.com>
Message-ID: <1628080576.526072825@f711.i.mail.ru>


Hi Shah Hussain,
maybe this will be useful to you:
 
https://www.opensips.org/Documentation/TipsFAQ#toc2
http://controlpanel.opensips.org/htmldoc_8_X_X/user_management.html  — ‘Password mode’ section.
 
-----------------------------------------------
BR, Alexey
https://alexeyka.zantsev.com/

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210804/b962870c/attachment.html>

From farmorg at gmail.com  Thu Aug  5 12:54:51 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 5 Aug 2021 13:54:51 +0100
Subject: [OpenSIPS-Users] Feature Request - drouting
Message-ID: <CAOvQDeud6HFNc5bv-Om=ftuxhEbg-JyjjEH0H144-2J_HnWN5A@mail.gmail.com>

Hi everyone

I am using drouting() which is working well but I am finding the prefix
matching a little limited. It would be really useful to be able to match
mid-range prefixes. For example, in Asterisk you can do do things like:

_+44123456789[2,3]
Which only matches prefixes ending 2 or 3.

Or:
_+44123456789[2-5]
Which matches prefixes ending 2,3,4 or 5

Would it be feasible to add this ability to drouting()?

Thanks and regards
Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210805/98612b52/attachment.html>

From bullehs at gmail.com  Thu Aug  5 18:14:48 2021
From: bullehs at gmail.com (HS)
Date: Thu, 5 Aug 2021 23:14:48 +0500
Subject: [OpenSIPS-Users] Script variable for dbaliases
Message-ID: <CA+PgBoaD1yrrJVJoQZB0TJo7qyPb0kknPd4CBbFqmr6fpfzFsA@mail.gmail.com>

Gents.

My setup works on dbaliases as well as usernames. I understand that the
variable for usernames is du and/or ru. Is there something comparable for
dbaliases. I looked here and couldn't find anything:
https://www.opensips.org/Documentation/Script-CoreVar-3-0

Any suggestions please?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210805/17edc450/attachment.html>

From cc3283 at att.com  Fri Aug  6 12:14:15 2021
From: cc3283 at att.com (CARTWRIGHT, CORY C)
Date: Fri, 6 Aug 2021 12:14:15 +0000
Subject: [OpenSIPS-Users] Possible bug: CRITICAL:core:internal_fork:
 #012>>> no free process slot found while trying to fork again#012
In-Reply-To: <CH2PR02MB65970421BA3FCD423F3FAEBBDEE89@CH2PR02MB6597.namprd02.prod.outlook.com>
References: <CH2PR02MB6597A8E155949E1E6EB7C1C5DE119@CH2PR02MB6597.namprd02.prod.outlook.com>
 <ca2f0c11-c3ca-ce0b-e71e-2f83cfe33f08@opensips.org>
 <CH2PR02MB65970421BA3FCD423F3FAEBBDEE89@CH2PR02MB6597.namprd02.prod.outlook.com>
Message-ID: <CH2PR02MB65975F480578AE5157B6B8FFDEF39@CH2PR02MB6597.namprd02.prod.outlook.com>

Hi Bogdan-Andrei,

Any more thoughts on this?

Thanks,
Cory

From: Users <users-bounces at lists.opensips.org> On Behalf Of CARTWRIGHT, CORY C
Sent: Monday, July 26, 2021 08:09
To: Bogdan-Andrei Iancu <bogdan at opensips.org>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Possible bug: CRITICAL:core:internal_fork: #012>>> no free process slot found while trying to fork again#012

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hello Bogdan,

Sorry for the delayed response, I was on vacation last week.  I am unable to duplicate this in the lab, so I'm leaning towards the option to not crash when the error occurs.  I will also respond on github.

Thank you,
Cory

From: Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>>
Sent: Thursday, July 22, 2021 02:58
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>; CARTWRIGHT, CORY C <cc3283 at att.com<mailto:cc3283 at att.com>>
Subject: Re: [OpenSIPS-Users] Possible bug: CRITICAL:core:internal_fork: #012>>> no free process slot found while trying to fork again#012

Hi Cory,

let's continue the discussion here https://github.com/OpenSIPS/opensips/issues/2575<https://urldefense.com/v3/__https:/github.com/OpenSIPS/opensips/issues/2575__;!!BhdT!1CH_bzlGcb2p7KktCV7QO5xOi9E8aVo3vCB_1_sUne-zcldW5zHjxh88Q2rKMQ$>

Regards,

Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com<https://urldefense.com/v3/__https:/www.opensips-solutions.com__;!!BhdT!1CH_bzlGcb2p7KktCV7QO5xOi9E8aVo3vCB_1_sUne-zcldW5zHjxh_oQJwD_Q$>

OpenSIPS Bootcamp 2021 online

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/<https://urldefense.com/v3/__https:/opensips.org/training/OpenSIPS_eBootcamp_2021/__;!!BhdT!1CH_bzlGcb2p7KktCV7QO5xOi9E8aVo3vCB_1_sUne-zcldW5zHjxh_RMIHMRA$>
On 7/16/21 4:13 PM, CARTWRIGHT, CORY C wrote:
Hello,

Ran across this in my syslogs, so far I have not been able to determine if it's actually affecting calls as our service is not based on live calls.  Here is the full message:




Jul 16 08:25:49  opensips[553787]: CRITICAL:core:fork_dynamic_udp_process: cannot fork UDP process
Jul 16 08:25:49 opensips[553787]: ERROR:core:do_workers_auto_scaling: failed to fork new process for group 1 (current 5 procs)
Jul 16 08:37:26 opensips[553787]: CRITICAL:core:internal_fork: #012>>> no free process slot found while trying to fork again#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues#012<https://urldefense.com/v3/__https:/github.com/OpenSIPS/opensips/issues*012__;Iw!!BhdT!1CH_bzlGcb2p7KktCV7QO5xOi9E8aVo3vCB_1_sUne-zcldW5zHjxh8uD-UF2A$>

My profiling config:

auto_scaling_profile = PROFILE_A
     scale up to 30 on 30% for 4 cycles within 5
     scale down to 5 on 18% for 10 cycles



version: opensips 3.1.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: 229ec0793
main.c compiled on 19:29:24 Jan  8 2021 with gcc 9,



Thanks,
Cory



_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users<https://urldefense.com/v3/__http:/lists.opensips.org/cgi-bin/mailman/listinfo/users__;!!BhdT!1CH_bzlGcb2p7KktCV7QO5xOi9E8aVo3vCB_1_sUne-zcldW5zHjxh_IKvP86A$>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210806/16e0f188/attachment-0001.html>

From miha at softnet.si  Mon Aug  9 06:19:40 2021
From: miha at softnet.si (Miha)
Date: Mon, 9 Aug 2021 08:19:40 +0200
Subject: [OpenSIPS-Users] MOH / rtpengine
Message-ID: <4f5f16ff-ebbe-9243-047e-f3e48c98dcd9@softnet.si>

Hi

when call is being trasfered to another number MS Teams sends new Invite 
with SDP as 'a=inactive'. How can I put ringback ton as MOH for this 
sitation?

I tried with:

if(is_audio_on_hold()) {
                  xlog("L_INFO", "onHOLD");
                                     rtpengine_play_media("file=/home/ringback.wav");
                   }

 From logs i can see that due to a=inactive rtpengine will not play 
media. I tried also to replace inactive with sendonly with function 
body_replace before I call rtpengine_play_media but it does not help.


thank you
miha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210809/f999906c/attachment.html>

From volga629 at networklab.ca  Mon Aug  9 12:13:38 2021
From: volga629 at networklab.ca (volga629 at networklab.ca)
Date: Mon, 9 Aug 2021 09:13:38 -0300
Subject: [OpenSIPS-Users] MOH / rtpengine
In-Reply-To: <4f5f16ff-ebbe-9243-047e-f3e48c98dcd9@softnet.si>
References: <4f5f16ff-ebbe-9243-047e-f3e48c98dcd9@softnet.si>
Message-ID: <ceacad91-46de-529a-0930-bc01fdc7fc17@skillsearch.ca>

An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210809/0139ff3a/attachment.html>

From farmorg at gmail.com  Wed Aug 11 10:35:12 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Wed, 11 Aug 2021 11:35:12 +0100
Subject: [OpenSIPS-Users] Push SDP into Request
Message-ID: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>

Hi everyone

I am using rtpengine_offer() and storing the SDP in a variable which I then
modify using the reg_exp transformation to delete a line.

rtpengine_offer($var(PSTN_TPTY),,$var(SDPbody));
$var(SDPbody) = $(var(SDPbody){re.subst,/a=silenceSupp:off\ -\ -\ -\
-\r\n//g});

How do I then push the resulting variable into the body of the INVITE?

Many thanks
Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210811/e132bc80/attachment.html>

From Johan at democon.be  Wed Aug 11 12:04:28 2021
From: Johan at democon.be (Johan De Clercq)
Date: Wed, 11 Aug 2021 14:04:28 +0200
Subject: [OpenSIPS-Users] Push SDP into Request
In-Reply-To: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>
References: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>
Message-ID: <CAEVWGm-PjYryM8DYrSNQZkNOE2N1xo3skNdykdW3-mOmdZ1eAw@mail.gmail.com>

wouldn't it be better to do first your manip and then pass it to rtpengine
?

Op wo 11 aug. 2021 om 12:39 schreef Mark Farmer <farmorg at gmail.com>:

> Hi everyone
>
> I am using rtpengine_offer() and storing the SDP in a variable which I
> then modify using the reg_exp transformation to delete a line.
>
> rtpengine_offer($var(PSTN_TPTY),,$var(SDPbody));
> $var(SDPbody) = $(var(SDPbody){re.subst,/a=silenceSupp:off\ -\ -\ -\
> -\r\n//g});
>
> How do I then push the resulting variable into the body of the INVITE?
>
> Many thanks
> Mark.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210811/dc5d1a1b/attachment.html>

From kaduww at gmail.com  Wed Aug 11 12:44:48 2021
From: kaduww at gmail.com (Carlos Eduardo)
Date: Wed, 11 Aug 2021 09:44:48 -0300
Subject: [OpenSIPS-Users] Push SDP into Request
In-Reply-To: <CAEVWGm-PjYryM8DYrSNQZkNOE2N1xo3skNdykdW3-mOmdZ1eAw@mail.gmail.com>
References: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>
 <CAEVWGm-PjYryM8DYrSNQZkNOE2N1xo3skNdykdW3-mOmdZ1eAw@mail.gmail.com>
Message-ID: <CAB=EcebqgQU9C6SG2NSZ52QQyrS-DccWfmdQj-SkGfJ_-mSGZQ@mail.gmail.com>

I noticed that when you manipulate before passing to rtpengine, the module
sends the "old" sdp to rtpengine. Does it make sense?

Em qua., 11 de ago. de 2021 às 09:07, Johan De Clercq <Johan at democon.be>
escreveu:

> wouldn't it be better to do first your manip and then pass it to rtpengine
> ?
>
> Op wo 11 aug. 2021 om 12:39 schreef Mark Farmer <farmorg at gmail.com>:
>
>> Hi everyone
>>
>> I am using rtpengine_offer() and storing the SDP in a variable which I
>> then modify using the reg_exp transformation to delete a line.
>>
>> rtpengine_offer($var(PSTN_TPTY),,$var(SDPbody));
>> $var(SDPbody) = $(var(SDPbody){re.subst,/a=silenceSupp:off\ -\ -\ -\
>> -\r\n//g});
>>
>> How do I then push the resulting variable into the body of the INVITE?
>>
>> Many thanks
>> Mark.
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
*Carlos E. Wagner*
*Tecnólogo em Telecomunicações, Opensips Certified Professional*

*Fone: +55 48 99981-0894*
*E-mail:* kaduww at gmail.com
*LinkedIn:* https://www.linkedin.com/in/carlos-eduardo-wagner-96bbb433/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210811/07089219/attachment.html>

From farmorg at gmail.com  Wed Aug 11 13:24:29 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Wed, 11 Aug 2021 14:24:29 +0100
Subject: [OpenSIPS-Users] Push SDP into Request
In-Reply-To: <CAB=EcebqgQU9C6SG2NSZ52QQyrS-DccWfmdQj-SkGfJ_-mSGZQ@mail.gmail.com>
References: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>
 <CAEVWGm-PjYryM8DYrSNQZkNOE2N1xo3skNdykdW3-mOmdZ1eAw@mail.gmail.com>
 <CAB=EcebqgQU9C6SG2NSZ52QQyrS-DccWfmdQj-SkGfJ_-mSGZQ@mail.gmail.com>
Message-ID: <CAOvQDev_anqto8ouBHRfXXTtOrE6LT-Zy-VTrvbRqg2P0Hvmxg@mail.gmail.com>

Thanks for the replies :)

I am not sure I really understand them, however I have solved the problem
like this:

rtpengine_offer($var(PSTN_TPTY),,$var(SDPbody));
$var(reg) = "/a=silenceSupp.*\n//ig";
$var(SDPbody) = $(var(SDPbody){re.subst,$var(reg)});
remove_body_part();
add_body_part("$var(SDPbody)", "application/sdp")

Perhaps there is a better way but this seems to work for now :)



On Wed, 11 Aug 2021 at 13:47, Carlos Eduardo <kaduww at gmail.com> wrote:

> I noticed that when you manipulate before passing to rtpengine, the module
> sends the "old" sdp to rtpengine. Does it make sense?
>
> Em qua., 11 de ago. de 2021 às 09:07, Johan De Clercq <Johan at democon.be>
> escreveu:
>
>> wouldn't it be better to do first your manip and then pass it to
>> rtpengine ?
>>
>> Op wo 11 aug. 2021 om 12:39 schreef Mark Farmer <farmorg at gmail.com>:
>>
>>> Hi everyone
>>>
>>> I am using rtpengine_offer() and storing the SDP in a variable which I
>>> then modify using the reg_exp transformation to delete a line.
>>>
>>> rtpengine_offer($var(PSTN_TPTY),,$var(SDPbody));
>>> $var(SDPbody) = $(var(SDPbody){re.subst,/a=silenceSupp:off\ -\ -\ -\
>>> -\r\n//g});
>>>
>>> How do I then push the resulting variable into the body of the INVITE?
>>>
>>> Many thanks
>>> Mark.
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> *Carlos E. Wagner*
> *Tecnólogo em Telecomunicações, Opensips Certified Professional*
>
> *Fone: +55 48 99981-0894*
> *E-mail:* kaduww at gmail.com
> *LinkedIn:* https://www.linkedin.com/in/carlos-eduardo-wagner-96bbb433/
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Mark Farmer
farmorg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210811/986bf367/attachment-0001.html>

From liviu at opensips.org  Wed Aug 11 14:04:58 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 11 Aug 2021 17:04:58 +0300
Subject: [OpenSIPS-Users] Push SDP into Request
In-Reply-To: <CAOvQDev_anqto8ouBHRfXXTtOrE6LT-Zy-VTrvbRqg2P0Hvmxg@mail.gmail.com>
References: <CAOvQDevzf+5FmtNBOFM6p4-QBJKezU9qu4BZmY3Xxeb1Y8x94w@mail.gmail.com>
 <CAEVWGm-PjYryM8DYrSNQZkNOE2N1xo3skNdykdW3-mOmdZ1eAw@mail.gmail.com>
 <CAB=EcebqgQU9C6SG2NSZ52QQyrS-DccWfmdQj-SkGfJ_-mSGZQ@mail.gmail.com>
 <CAOvQDev_anqto8ouBHRfXXTtOrE6LT-Zy-VTrvbRqg2P0Hvmxg@mail.gmail.com>
Message-ID: <86844998-3f32-c5a3-3998-6a47fcfe08cb@opensips.org>

On 11.08.2021 16:24, Mark Farmer wrote:
>
> Perhaps there is a better way but this seems to work for now :)
>
Hey Mark,

LGTM!  I can't think of a better way of doing either of the SDP editing 
or replacing logic from the OpenSIPS config file.

Cheers,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From jeff at ugnd.org  Wed Aug 11 19:01:05 2021
From: jeff at ugnd.org (Jeff Pyle)
Date: Wed, 11 Aug 2021 15:01:05 -0400
Subject: [OpenSIPS-Users] strange behavior with TCP reply port
Message-ID: <CAPhW+0KO7sv6U92h5WXM8XRZqSnbE_pKrqUuBoVHct3WbnWiKg@mail.gmail.com>

Hello,

This is on the 3.1.3~20210731~b333a222f-1 from the Debian 3.1-nightly repo.

Typically I run with

  modparam("tm", "auto_100trying", 0)

so I can manually send a 100 with

  sl_send_reply(100, "Trying");

earlier in the script, before blocking processes like DB lookups and such.
No problem...until today.  On a TCP (TLS) connection, the sl_send_reply()
function opens a new TCP socket to the UAC on the IP:port listed in the
original message's Contact, rather than sending the 100 on the existing
socket (using the ephemeral port) the UAC used for its TCP socket to us.
Future downstream replies are relayed back upstream to the ephemeral port.
In other words, only the 100 Trying message from sl_send_reply() is opening
a new socket back upstream.

The auto_100trying option from tm, however, sends its 100 messages to the
ephemeral port of the UAC.

How can I get the sl_send_reply() function to reply on the existing TCP
socket?


Regards,
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210811/d1dbff00/attachment.html>

From ag at ag-projects.com  Thu Aug 12 15:36:31 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 12:36:31 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
Message-ID: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>

The auth_db module has some dramatic changes which are either undocumented or not backwards compatible and is unclear how to handle this.

https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2 <https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2>

Aug 12 17:34:10 [3179] CRITICAL:core:yyerror: parse error in /etc/opensips/opensips.cfg.tmp:1170:20-21: Parameter <password_column_2> not found in module <auth_db> - can't set
Aug 12 17:34:10 [3179] modparam("auth_db", "calculate_ha1",     0)
Aug 12 17:34:10 [3179] modparam("auth_db", "password_column",   "ha1")
Aug 12 17:34:10 [3179] modparam("auth_db", "password_column_2", "ha1b")
Aug 12 17:34:10 [3179] ^~
Aug 12 17:34:10 [3179] modparam("auth_db", "user_column",       "username")
Aug 12 17:34:10 [3179] modparam("auth_db", "domain_column",     "domain")
Aug 12 17:34:10 [3179] ERROR:core:parse_opensips_cfg: bad config file (1 errors)

password_column_2 parameter has vanished in 3.2.2 and we relied heavily on its presence as it contained a recalculate hash including the domain name.

How should we deal with this?

Regards,
Adrian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210812/e873be93/attachment.html>

From liviu at opensips.org  Thu Aug 12 16:04:42 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 12 Aug 2021 19:04:42 +0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
Message-ID: <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>

On 12.08.2021 18:36, Adrian Georgescu wrote:
> The auth_db module has some dramatic changes which are either 
> undocumented or not backwards compatible and is unclear how to handle 
> this.
>
> https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2 
> <https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2>

Hi Adrian,

Indeed, with the addition of RFC 8760 support (support for SHA-256 and 
SHA-512-256 auth algorithms), me and Maksym Sobolyev decided to try and 
remove the "ha1b" feature, originally designed to accommodate some 
broken SIP UAs who cannot follow the basic SIP authentication spec.  The 
feature had been in there since the very beginnings, and we were not 
sure if anyone is really benefiting from it anymore nowadays.

A strong reason for removing "ha1b" was the sheer number of hashes to be 
stored per subscriber.  Since we now have 3 algorithms (MD5, SHA-256, 
SHA-512-256), there are 3 hash-columns to store.  With the "ha1b" 
feature, there would be 2 x 3 = 6 hashes in total to store, per user.  
So you can see where this is going: /"Can we get away with dropping ha1b 
and storing half the data per user?"/ ... was the big question.

Still, we agreed that if there is still enough traction for the "ha1b" 
feature from the community, we can easily re-add the ha1b logic and 3 
more columns to the table and backport everything to 3.2.  It's a 
trivial task, frankly.

The big question is: on your platform(s), can you control the software 
in all SIP UAs that incorrectly include "realm" information in the 
"username" field (which should really be just the *user**'s **name*!) 
and fix the problem on the phone side?

PS: I noticed the 3.2 migration page is missing any info on ha1b.  Will 
get it fixed soon, depending on the outcome of the discussion.

Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210812/9a6bf6b8/attachment.html>

From ag at ag-projects.com  Thu Aug 12 17:12:31 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 14:12:31 -0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0 domain
	configuration
Message-ID: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>

Hi,

I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.

But while the config check passed, the server does not start with the old configuration:

loadmodule “tls_mgm.so"
loadmodule “tls_wolfssl.so"
modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
modparam("tls_mgm", "tls_library", "auto”)

modparam("tls_mgm", "server_domain",    "ag-projects-server")
modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")

modparam("tls_mgm", "client_domain",    "ag-projects-client")
modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)


Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm

Any ideas what am I doing wrong?

Adrian




From ag at ag-projects.com  Thu Aug 12 18:59:01 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 15:59:01 -0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
	domain configuration
In-Reply-To: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
Message-ID: <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>

After more digging I discovered that this behaviour does not happen when loading tls_openssl module. 

tls_openssl loads fine this configuration but tls_wolfssl does not.

> On 12 Aug 2021, at 14:12, Adrian Georgescu <ag at ag-projects.com> wrote:
> 
> Hi,
> 
> I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
> 
> But while the config check passed, the server does not start with the old configuration:
> 
> loadmodule “tls_mgm.so"
> loadmodule “tls_wolfssl.so"
> modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
> modparam("tls_mgm", "tls_library", "auto”)
> 
> modparam("tls_mgm", "server_domain",    "ag-projects-server")
> modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
> modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
> modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
> modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
> modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
> modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
> modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
> modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
> modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
> 
> modparam("tls_mgm", "client_domain",    "ag-projects-client")
> modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
> modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
> modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
> modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
> modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
> modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
> modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
> modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
> modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
> 
> 
> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
> 
> Any ideas what am I doing wrong?
> 
> Adrian
> 
> 



From ag at ag-projects.com  Thu Aug 12 19:01:01 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 16:01:01 -0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
	domain configuration
In-Reply-To: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
Message-ID: <DA6249DB-FDE9-40B9-BAA3-ABE9C5448D15@ag-projects.com>

This line looks suspicious as I have not loaded or specified anywhere tls_openssl.

Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded — continuing

Adrian


> On 12 Aug 2021, at 14:12, Adrian Georgescu <ag at ag-projects.com> wrote:
> 
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210812/93f3323c/attachment.html>

From osas at voipembedded.com  Thu Aug 12 19:03:35 2021
From: osas at voipembedded.com (Ovidiu Sas)
Date: Thu, 12 Aug 2021 15:03:35 -0400
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
	domain configuration
In-Reply-To: <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
 <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>
Message-ID: <CAND0LkuM8ViU7ZEg3g85wLQNJNXUKd+t0zsFcBVydJLoaReeJA@mail.gmail.com>

Hello Adrian,

I managed to use wolfssl by forcing it:
  modparam("tls_mgm", "tls_library", "wolfssl")

I haven't tested the auto mode ...

-ovidiu

On Thu, Aug 12, 2021 at 2:59 PM Adrian Georgescu <ag at ag-projects.com> wrote:
>
> After more digging I discovered that this behaviour does not happen when loading tls_openssl module.
>
> tls_openssl loads fine this configuration but tls_wolfssl does not.
>
> > On 12 Aug 2021, at 14:12, Adrian Georgescu <ag at ag-projects.com> wrote:
> >
> > Hi,
> >
> > I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
> >
> > But while the config check passed, the server does not start with the old configuration:
> >
> > loadmodule “tls_mgm.so"
> > loadmodule “tls_wolfssl.so"
> > modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
> > modparam("tls_mgm", "tls_library", "auto”)
> >
> > modparam("tls_mgm", "server_domain",    "ag-projects-server")
> > modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
> > modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
> > modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
> > modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
> > modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
> > modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
> > modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
> > modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
> > modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
> >
> > modparam("tls_mgm", "client_domain",    "ag-projects-client")
> > modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
> > modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
> > modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
> > modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
> > modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
> > modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
> > modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
> > modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
> > modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
> >
> >
> > Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
> > Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
> > Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
> >
> > Any ideas what am I doing wrong?
> >
> > Adrian
> >
> >
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com


From ag at ag-projects.com  Thu Aug 12 19:04:42 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 16:04:42 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
Message-ID: <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>

After removing the ha1b column, I am now getting the following errors and authentication does not work:

Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of sync; you can't run this command now
Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: ERROR:auth_db:get_ha1: failed to query database
Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of sync; you can't run this command now
Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: ERROR:auth_db:get_ha1: failed to query database

auth_db module configuration:

modparam("auth_db", "calculate_ha1",     0)
modparam("auth_db", "password_column",   "ha1")
modparam("auth_db", "user_column",       "username")
modparam("auth_db", "domain_column",     "domain”)

What can be the reason for this?

Regards,
Adrian



> On 12 Aug 2021, at 13:04, Liviu Chircu <liviu at opensips.org> wrote:
> 
> On 12.08.2021 18:36, Adrian Georgescu wrote:
>> The auth_db module has some dramatic changes which are either undocumented or not backwards compatible and is unclear how to handle this.
>> 
>> https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2 <https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2>Hi Adrian,
> 
> Indeed, with the addition of RFC 8760 support (support for SHA-256 and SHA-512-256 auth algorithms), me and Maksym Sobolyev decided to try and remove the "ha1b" feature, originally designed to accommodate some broken SIP UAs who cannot follow the basic SIP authentication spec.  The feature had been in there since the very beginnings, and we were not sure if anyone is really benefiting from it anymore nowadays.
> 
> A strong reason for removing "ha1b" was the sheer number of hashes to be stored per subscriber.  Since we now have 3 algorithms (MD5, SHA-256, SHA-512-256), there are 3 hash-columns to store.  With the "ha1b" feature, there would be 2 x 3 = 6 hashes in total to store, per user.  So you can see where this is going: "Can we get away with dropping ha1b and storing half the data per user?" ... was the big question.
> 
> Still, we agreed that if there is still enough traction for the "ha1b" feature from the community, we can easily re-add the ha1b logic and 3 more columns to the table and backport everything to 3.2.  It's a trivial task, frankly.
> 
> The big question is: on your platform(s), can you control the software in all SIP UAs that incorrectly include "realm" information in the "username" field (which should really be just the user's name!) and fix the problem on the phone side?
> 
> PS: I noticed the 3.2 migration page is missing any info on ha1b.  Will get it fixed soon, depending on the outcome of the discussion.
> 
> Best Regards,
> 
> -- 
> Liviu Chircu
> www.twitter.com/liviuchircu <http://www.twitter.com/liviuchircu> | www.opensips-solutions.com <http://www.opensips-solutions.com/>
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events <http://www.opensips.org/events>_______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210812/e567bbc3/attachment.html>

From liviu at opensips.org  Thu Aug 12 19:11:47 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 12 Aug 2021 22:11:47 +0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>
Message-ID: <67f14ecd-1cf7-059e-fdea-c226ab847aa9@opensips.org>

On 12.08.2021 22:04, Adrian Georgescu wrote:
>
> What can be the reason for this?
>
This exact issue seems to be the object of two identical GitHub issues: 
[1], [2].  Will take a look at this tomorrow and see if I can reproduce.

[1]: https://github.com/OpenSIPS/opensips/issues/2586
[2]: https://github.com/OpenSIPS/opensips/issues/2593

Cheers,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From ag at ag-projects.com  Thu Aug 12 19:17:01 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 12 Aug 2021 16:17:01 -0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
 domain configuration
In-Reply-To: <CAND0LkuM8ViU7ZEg3g85wLQNJNXUKd+t0zsFcBVydJLoaReeJA@mail.gmail.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
 <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>
 <CAND0LkuM8ViU7ZEg3g85wLQNJNXUKd+t0zsFcBVydJLoaReeJA@mail.gmail.com>
Message-ID: <0EC7D365-D976-47FF-B5F1-278B9EB55F2F@ag-projects.com>

H Ovidiu,

I set it up explicitly now but I get the same result, I tried different domains or combination but any definition fails to load.

Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'msteams-server'
Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:core:init_mod: failed to initialize module tls_mgm
Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:core:main: error while initializing modules

loadmodule "tls_mgm.so"
modparam("tls_mgm", "tls_library", "wolfssl")

Regards,
Adrian

> On 12 Aug 2021, at 16:03, Ovidiu Sas <osas at voipembedded.com> wrote:
> 
> Hello Adrian,
> 
> I managed to use wolfssl by forcing it:
>  modparam("tls_mgm", "tls_library", "wolfssl")
> 
> I haven't tested the auto mode ...
> 
> -ovidiu
> 
> On Thu, Aug 12, 2021 at 2:59 PM Adrian Georgescu <ag at ag-projects.com> wrote:
>> 
>> After more digging I discovered that this behaviour does not happen when loading tls_openssl module.
>> 
>> tls_openssl loads fine this configuration but tls_wolfssl does not.
>> 
>>> On 12 Aug 2021, at 14:12, Adrian Georgescu <ag at ag-projects.com> wrote:
>>> 
>>> Hi,
>>> 
>>> I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
>>> 
>>> But while the config check passed, the server does not start with the old configuration:
>>> 
>>> loadmodule “tls_mgm.so"
>>> loadmodule “tls_wolfssl.so"
>>> modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
>>> modparam("tls_mgm", "tls_library", "auto”)
>>> 
>>> modparam("tls_mgm", "server_domain",    "ag-projects-server")
>>> modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
>>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
>>> modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
>>> modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
>>> modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
>>> modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
>>> modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
>>> modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
>>> modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
>>> 
>>> modparam("tls_mgm", "client_domain",    "ag-projects-client")
>>> modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
>>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
>>> modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
>>> modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
>>> modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
>>> modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
>>> modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
>>> modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
>>> modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
>>> 
>>> 
>>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
>>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
>>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
>>> 
>>> Any ideas what am I doing wrong?
>>> 
>>> Adrian
>>> 
>>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 
> 
> -- 
> VoIP Embedded, Inc.
> http://www.voipembedded.com
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From liviu at opensips.org  Thu Aug 12 19:47:21 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 12 Aug 2021 22:47:21 +0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
 domain configuration
In-Reply-To: <0EC7D365-D976-47FF-B5F1-278B9EB55F2F@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
 <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>
 <CAND0LkuM8ViU7ZEg3g85wLQNJNXUKd+t0zsFcBVydJLoaReeJA@mail.gmail.com>
 <0EC7D365-D976-47FF-B5F1-278B9EB55F2F@ag-projects.com>
Message-ID: <c1ee8a53-1678-4e2f-6c76-3ec415e835d2@opensips.org>

On 12.08.2021 22:17, Adrian Georgescu wrote:
> I set it up explicitly now but I get the same result, I tried different domains or combination but any definition fails to load.

Hi gents,

IIRC (Vlad: please correct me if I'm wrong), this initial version of the 
tls_wolfssl module does not have full feature parity with tls_openssl, 
as it is currently only equipped to provide TLS communication for 
modules such as proto_tls and proto_wss.

So when it comes to configuring domains via tls_mgm on top of 
tls_wolfssl, the module MAY lack the required API function 
implementations, hence the errors you are getting.

PS: there seem to be some hints about the above in the module docs [1] 
as well.

[1]: https://opensips.org/docs/modules/3.2.x/tls_wolfssl.html#overview

Cheers,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From osas at voipembedded.com  Thu Aug 12 20:09:07 2021
From: osas at voipembedded.com (Ovidiu Sas)
Date: Thu, 12 Aug 2021 16:09:07 -0400
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
	domain configuration
In-Reply-To: <0EC7D365-D976-47FF-B5F1-278B9EB55F2F@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
 <1F6EE5B6-D78E-475C-986C-2F507C879FC1@ag-projects.com>
 <CAND0LkuM8ViU7ZEg3g85wLQNJNXUKd+t0zsFcBVydJLoaReeJA@mail.gmail.com>
 <0EC7D365-D976-47FF-B5F1-278B9EB55F2F@ag-projects.com>
Message-ID: <CAND0LksLf79pNed9fm9ReWj=cbHzWaOb6gP7wJpttA0uYLHrPA@mail.gmail.com>

I loaded both modules and I just switch between them via the
tls_library parameter and it loads ok:
loadmodule "tls_openssl.so"
loadmodule "tls_wolfssl.so"
loadmodule "tls_mgm.so"
  modparam("tls_mgm", "tls_library", "openssl")
# modparam("tls_mgm", "tls_library", "wolfssl")

I did not test with the latest opensips version ...
I also had some issues with the wolfssl library: is_peer_verified()
doesn't seem to work properly. Because of that I'm still using the
openssl library.

-ovidiu

On Thu, Aug 12, 2021 at 3:17 PM Adrian Georgescu <ag at ag-projects.com> wrote:
>
> H Ovidiu,
>
> I set it up explicitly now but I get the same result, I tried different domains or combination but any definition fails to load.
>
> Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'msteams-server'
> Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:core:init_mod: failed to initialize module tls_mgm
> Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]: ERROR:core:main: error while initializing modules
>
> loadmodule "tls_mgm.so"
> modparam("tls_mgm", "tls_library", "wolfssl")
>
> Regards,
> Adrian
>
> > On 12 Aug 2021, at 16:03, Ovidiu Sas <osas at voipembedded.com> wrote:
> >
> > Hello Adrian,
> >
> > I managed to use wolfssl by forcing it:
> >  modparam("tls_mgm", "tls_library", "wolfssl")
> >
> > I haven't tested the auto mode ...
> >
> > -ovidiu
> >
> > On Thu, Aug 12, 2021 at 2:59 PM Adrian Georgescu <ag at ag-projects.com> wrote:
> >>
> >> After more digging I discovered that this behaviour does not happen when loading tls_openssl module.
> >>
> >> tls_openssl loads fine this configuration but tls_wolfssl does not.
> >>
> >>> On 12 Aug 2021, at 14:12, Adrian Georgescu <ag at ag-projects.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
> >>>
> >>> But while the config check passed, the server does not start with the old configuration:
> >>>
> >>> loadmodule “tls_mgm.so"
> >>> loadmodule “tls_wolfssl.so"
> >>> modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
> >>> modparam("tls_mgm", "tls_library", "auto”)
> >>>
> >>> modparam("tls_mgm", "server_domain",    "ag-projects-server")
> >>> modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
> >>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
> >>> modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
> >>> modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
> >>> modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
> >>> modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
> >>> modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
> >>> modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
> >>> modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
> >>>
> >>> modparam("tls_mgm", "client_domain",    "ag-projects-client")
> >>> modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
> >>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
> >>> modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
> >>> modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
> >>> modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
> >>> modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
> >>> modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
> >>> modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
> >>> modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
> >>>
> >>>
> >>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
> >>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
> >>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
> >>>
> >>> Any ideas what am I doing wrong?
> >>>
> >>> Adrian
> >>>
> >>>
> >>
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> > --
> > VoIP Embedded, Inc.
> > http://www.voipembedded.com
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com


From vladp at opensips.org  Thu Aug 12 21:12:58 2021
From: vladp at opensips.org (Vlad Patrascu)
Date: Fri, 13 Aug 2021 00:12:58 +0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
 domain configuration
In-Reply-To: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
Message-ID: <e51931cf-f0e3-93bb-6d1e-9af9ef18e28a@opensips.org>

Hi Adrian,

The wolfSSL implementation does not support a TLS method range, such as 
"TLSv1-", so that could be one of the causes. What seems strange is that 
there is no warning message: "WARNING:tls_wolfssl:tls_get_method: 
wolfSSL does not support method range specification" which should be 
thrown in such cases.

Regards,

-- 
Vlad Patrascu
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 12.08.2021 20:12, Adrian Georgescu wrote:
> Hi,
>
> I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
>
> But while the config check passed, the server does not start with the old configuration:
>
> loadmodule “tls_mgm.so"
> loadmodule “tls_wolfssl.so"
> modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
> modparam("tls_mgm", "tls_library", "auto”)
>
> modparam("tls_mgm", "server_domain",    "ag-projects-server")
> modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
> modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
> modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
> modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
> modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
> modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
> modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
> modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
> modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
>
> modparam("tls_mgm", "client_domain",    "ag-projects-client")
> modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
> modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
> modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
> modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
> modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
> modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
> modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
> modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
> modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
>
>
> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
>
> Any ideas what am I doing wrong?
>
> Adrian
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From ag at ag-projects.com  Fri Aug 13 11:11:23 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Fri, 13 Aug 2021 08:11:23 -0300
Subject: [OpenSIPS-Users] 3.2.0 TLS MGM module does not load 3.1.0
 domain configuration
In-Reply-To: <e51931cf-f0e3-93bb-6d1e-9af9ef18e28a@opensips.org>
References: <7B6B1633-8B96-4112-AE97-A062A72DDA1B@ag-projects.com>
 <e51931cf-f0e3-93bb-6d1e-9af9ef18e28a@opensips.org>
Message-ID: <18782C62-D28D-4965-9A8E-A72B0492EE33@ag-projects.com>

Thank you Vlad,

I confirm that I was able to load the certificate using wolfssl by setting the protocol version to TLSv1. 

Regards,
Adrian


> On 12 Aug 2021, at 18:12, Vlad Patrascu <vladp at opensips.org> wrote:
> 
> Hi Adrian,
> 
> The wolfSSL implementation does not support a TLS method range, such as "TLSv1-", so that could be one of the causes. What seems strange is that there is no warning message: "WARNING:tls_wolfssl:tls_get_method: wolfSSL does not support method range specification" which should be thrown in such cases.
> 
> Regards,
> 
> -- 
> Vlad Patrascu
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
> 
> On 12.08.2021 20:12, Adrian Georgescu wrote:
>> Hi,
>> 
>> I am using the latest 3.2.0 build with the old TLS configuration, with the aim to try out Wolf SSL stack.
>> 
>> But while the config check passed, the server does not start with the old configuration:
>> 
>> loadmodule “tls_mgm.so"
>> loadmodule “tls_wolfssl.so"
>> modparam("tls_mgm", "client_tls_domain_avp", "tls_client_domain")
>> modparam("tls_mgm", "tls_library", "auto”)
>> 
>> modparam("tls_mgm", "server_domain",    "ag-projects-server")
>> modparam("tls_mgm", "match_ip_address", "[ag-projects-server]*")
>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-server]ag-projects.com")
>> modparam("tls_mgm", "tls_method",       "[ag-projects-server]TLSv1-")
>> modparam("tls_mgm", "certificate",      "[ag-projects-server]/etc/opensips/tls/ag-projects.crt")
>> modparam("tls_mgm", "private_key",      "[ag-projects-server]/etc/opensips/tls/ag-projects.key")
>> modparam("tls_mgm", "ca_list",          "[ag-projects-server]/etc/opensips/tls/ca-list.pem")
>> modparam("tls_mgm", "ca_dir",           "[ag-projects-server]/etc/ssl/certs")
>> modparam("tls_mgm", "verify_cert",      "[ag-projects-server]1")
>> modparam("tls_mgm", "require_cert",     "[ag-projects-server]0")
>> 
>> modparam("tls_mgm", "client_domain",    "ag-projects-client")
>> modparam("tls_mgm", "match_ip_address", "[ag-projects-client]*")
>> modparam("tls_mgm", "match_sip_domain", "[ag-projects-client]ag-projects.com")
>> modparam("tls_mgm", "tls_method",       "[ag-projects-client]TLSv1-")
>> modparam("tls_mgm", "certificate",      "[ag-projects-client]/etc/opensips/tls/ag-projects.crt")
>> modparam("tls_mgm", "private_key",      "[ag-projects-client]/etc/opensips/tls/ag-projects.key")
>> modparam("tls_mgm", "ca_list",          "[ag-projects-client]/etc/opensips/tls/ca-list.pem")
>> modparam("tls_mgm", "ca_dir",           "[ag-projects-client]/etc/ssl/certs")
>> modparam("tls_mgm", "verify_cert",      "[ag-projects-client]1")
>> modparam("tls_mgm", "require_cert",     "[ag-projects-client]0”)
>> 
>> 
>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: tls_mgm matches module tls_mgm
>> Aug 12 18:51:14 live01 opensips[6455]: Aug 12 18:51:14 [6455] DBG:core:set_mod_param_regex: found <require_cert> in module tls_mgm [/usr/lib/x86_64-linux-gnu/opensips/modules/]
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_wolfssl
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency tls_mgm -> module tls_openssl
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module tls_openssl, and it was not loaded -- continuing
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:solve_module_dependencies: solving dependency proto_tls -> module tls_mgm
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:core:init_mod: initializing module tls_mgm
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:mod_init: initializing TLS management
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 rows found in tls_mgm
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:load_info: 0 records found in tls_mgm
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] INFO:tls_mgm:init_tls_dom: Processing TLS domain 'ag-projects-server'
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'ag-projects-server' defined, using default '(null)'
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] DBG:tls_mgm:init_tls_dom: cipher list null ... setting default
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'ag-projects-server'
>> Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455] ERROR:core:init_mod: failed to initialize module tls_mgm
>> 
>> Any ideas what am I doing wrong?
>> 
>> Adrian
>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From ag at ag-projects.com  Fri Aug 13 11:12:47 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Fri, 13 Aug 2021 08:12:47 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
Message-ID: <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>

On 12 Aug 2021, at 13:04, Liviu Chircu <liviu at opensips.org> wrote:
> 
> On 12.08.2021 18:36, Adrian Georgescu wrote:
>> The auth_db module has some dramatic changes which are either undocumented or not backwards compatible and is unclear how to handle this.
>> 
>> https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2 <https://opensips.org/docs/modules/3.1.x/auth_db.html#param_password_column_2>Hi Adrian,
> 
> Indeed, with the addition of RFC 8760 support (support for SHA-256 and SHA-512-256 auth algorithms), me and Maksym Sobolyev decided to try and remove the "ha1b" feature, originally designed to accommodate some broken SIP UAs who cannot follow the basic SIP authentication spec.  The feature had been in there since the very beginnings, and we were not sure if anyone is really benefiting from it anymore nowadays.
> 
> A strong reason for removing "ha1b" was the sheer number of hashes to be stored per subscriber.  Since we now have 3 algorithms (MD5, SHA-256, SHA-512-256), there are 3 hash-columns to store.  With the "ha1b" feature, there would be 2 x 3 = 6 hashes in total to store, per user.  So you can see where this is going: "Can we get away with dropping ha1b and storing half the data per user?" ... was the big question.
> 
> Still, we agreed that if there is still enough traction for the "ha1b" feature from the community, we can easily re-add the ha1b logic and 3 more columns to the table and backport everything to 3.2.  It's a trivial task, frankly.
> 
Hi Liviu,

I would very much like to see this feature ported back to 3.2 please!

Regards,
Adrian
 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210813/859499d0/attachment.html>

From bullehs at gmail.com  Fri Aug 13 15:27:12 2021
From: bullehs at gmail.com (HS)
Date: Fri, 13 Aug 2021 20:27:12 +0500
Subject: [OpenSIPS-Users] SQL Query Variables
Message-ID: <CA+PgBoZ=Qc7-7+T=Q0yHyR=eu5K9HZpAPcgP1y2p9oPGSgds_w@mail.gmail.com>

Hi all.

In my quest to make the push server work on my Opensips 3.0 installation. I
have figured out that the following query isn't working correctly:

$avp(query) = "SELECT token, app, platform, sip_instance from push_tokens
WHERE username='" + $(var(user){s.escape.common}) + "' AND domain='" +
$(var(domain){s.escape.common}) + "'";

When I replace $(var(user...)/$var(domain...) with $(tU..) and $(td..), the
query seems to work. I have tried multiple combinations, but the
original query isn't working.

What do I need to change to make the original query work? I did find
details of what tU is, but nothing about var(user).

Thanks for the help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210813/e3f33dbf/attachment-0001.html>

From kingsley at dns99.co.uk  Sat Aug 14 23:48:23 2021
From: kingsley at dns99.co.uk (Kingsley Tart)
Date: Sun, 15 Aug 2021 00:48:23 +0100
Subject: [OpenSIPS-Users] SQL Query Variables
In-Reply-To: <CA+PgBoZ=Qc7-7+T=Q0yHyR=eu5K9HZpAPcgP1y2p9oPGSgds_w@mail.gmail.com>
References: <CA+PgBoZ=Qc7-7+T=Q0yHyR=eu5K9HZpAPcgP1y2p9oPGSgds_w@mail.gmail.com>
Message-ID: <4317d5d3378f67593eab41d075c95e529ef994b7.camel@dns99.co.uk>

On Fri, 2021-08-13 at 20:27 +0500, HS wrote:
> Hi all.
> 
> In my quest to make the push server work on my Opensips 3.0
> installation. I have figured out that the following query isn't
> working correctly:
> 
> $avp(query) = "SELECT token, app, platform, sip_instance from
> push_tokens WHERE username='" + $(var(user){s.escape.common}) + "'
> AND domain='" + $(var(domain){s.escape.common}) + "'";
> 
> When I replace $(var(user...)/$var(domain...) with $(tU..) and
> $(td..), the query seems to work. I have tried multiple combinations,
> but the original query isn't working.
> 
> What do I need to change to make the original query work? I did find
> details of what tU is, but nothing about var(user).

Does your query contain what you think it does? Do you see what you
expect if you do

xlog("Query=$avp(query)\n");

?

-- 
Cheers,
Kingsley.



From bullehs at gmail.com  Sun Aug 15 11:28:45 2021
From: bullehs at gmail.com (HS)
Date: Sun, 15 Aug 2021 16:28:45 +0500
Subject: [OpenSIPS-Users] SQL Query Variables
In-Reply-To: <CA+PgBoZ=Qc7-7+T=Q0yHyR=eu5K9HZpAPcgP1y2p9oPGSgds_w@mail.gmail.com>
References: <CA+PgBoZ=Qc7-7+T=Q0yHyR=eu5K9HZpAPcgP1y2p9oPGSgds_w@mail.gmail.com>
Message-ID: <CA+PgBoZfEkp4_tCwooA+8jX7itdVhSkhhBxCUHrq6NQYfZ+3YA@mail.gmail.com>

Hi Kingsley.

Thanks a lot for your comment. I realised that the following was missing
before the query:

$var(user) = $rU;
$var(domain) = $rd;

It seems to be working for usernames now. Probably been the toughest bit of
self-learning. Next step, need to figure out how to make this work for
aliases.

Thanks again.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210815/ad84b50e/attachment.html>

From liviu at opensips.org  Mon Aug 16 15:43:25 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 16 Aug 2021 18:43:25 +0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>
Message-ID: <38376add-bda2-59b4-a292-24c966925f84@opensips.org>

On 12.08.2021 22:04, Adrian Georgescu wrote:
> Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: 
> ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of 
> sync; you can't run this command now
> Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: 
> ERROR:auth_db:get_ha1: failed to query database
> Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: 
> ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of 
> sync; you can't run this command now
> Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: 
> ERROR:auth_db:get_ha1: failed to query database

Hi Adrian,

This issue should now be fixed on latest 3.2, per [1].

[1]: https://github.com/OpenSIPS/opensips/commit/c871d9edfce

Best,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From liviu at opensips.org  Mon Aug 16 15:55:31 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 16 Aug 2021 18:55:31 +0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>
Message-ID: <eb86e2e5-3523-bce5-29f4-0eebe1eafbba@opensips.org>

On 13.08.2021 14:12, Adrian Georgescu wrote:
>
> I would very much like to see this feature ported back to 3.2 please!

Hi,

Could you offer a bit more info on why you would want it?  Like what 
kind of SIP phones are still out there that cannot handle the SIP auth 
specs in 2021?  If you think about it, they won't work with other SIP 
servers: no commercial SIP server and no Asterisk, FS, PJSIP, SIP.js, 
drachtio, reSIPprocate, etc.:  Not a single one of these implement this 
crazy "ha1b" feature, and none of them give a single damn if the phone 
is poorly implemented and appends the "@realm" part in the username 
component: they will happily reply with 401 Unauthorized until the 
implementor fixes the phone.

So why should OpenSIPS have this feature? Also, I suggest you open a 
GitHub feature request [1] as well on this topic -- maybe we get more 
opinions from there as well.

[1]: https://github.com/OpenSIPS/opensips/issues

Best,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From ag at ag-projects.com  Mon Aug 16 17:33:28 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Mon, 16 Aug 2021 14:33:28 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <eb86e2e5-3523-bce5-29f4-0eebe1eafbba@opensips.org>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>
 <eb86e2e5-3523-bce5-29f4-0eebe1eafbba@opensips.org>
Message-ID: <748F289F-12D7-4EFC-80CA-BE096B8213BD@ag-projects.com>

Hi Liviu,

I understand now better the purpose of that field and is indeed not needed anymore!

Regards,
Adrian

> On 16 Aug 2021, at 12:55, Liviu Chircu <liviu at opensips.org> wrote:
> 
> On 13.08.2021 14:12, Adrian Georgescu wrote:
>> 
>> I would very much like to see this feature ported back to 3.2 please!
> 
> Hi,
> 
> Could you offer a bit more info on why you would want it?  Like what kind of SIP phones are still out there that cannot handle the SIP auth specs in 2021?  If you think about it, they won't work with other SIP servers: no commercial SIP server and no Asterisk, FS, PJSIP, SIP.js, drachtio, reSIPprocate, etc.:  Not a single one of these implement this crazy "ha1b" feature, and none of them give a single damn if the phone is poorly implemented and appends the "@realm" part in the username component: they will happily reply with 401 Unauthorized until the implementor fixes the phone.
> 
> So why should OpenSIPS have this feature? Also, I suggest you open a GitHub feature request [1] as well on this topic -- maybe we get more opinions from there as well.
> 
> [1]: https://github.com/OpenSIPS/opensips/issues
> 
> Best,
> 
> -- 
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
> 



From ag at ag-projects.com  Mon Aug 16 17:44:11 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Mon, 16 Aug 2021 14:44:11 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <748F289F-12D7-4EFC-80CA-BE096B8213BD@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>
 <eb86e2e5-3523-bce5-29f4-0eebe1eafbba@opensips.org>
 <748F289F-12D7-4EFC-80CA-BE096B8213BD@ag-projects.com>
Message-ID: <669446E6-21D0-4DDC-A32C-639DC8784BC2@ag-projects.com>

There are some leftovers in the module documentation related to password_column_2:

https://opensips.org/html/docs/modules/3.2.x/auth_db.html#param_calculate_ha1 <https://opensips.org/html/docs/modules/3.2.x/auth_db.html#param_calculate_ha1>


The “password_column_2” column contains also HA1 strings but they should be calculated including the domain in the username parameter (as opposed to password_column which (when containing HA1 strings) should always contain HA1 strings calculated without domain in username.


> On 16 Aug 2021, at 14:33, Adrian Georgescu <ag at ag-projects.com> wrote:
> 
> Hi Liviu,
> 
> I understand now better the purpose of that field and is indeed not needed anymore!
> 
> Regards,
> Adrian
> 
>> On 16 Aug 2021, at 12:55, Liviu Chircu <liviu at opensips.org> wrote:
>> 
>> On 13.08.2021 14:12, Adrian Georgescu wrote:
>>> 
>>> I would very much like to see this feature ported back to 3.2 please!
>> 
>> Hi,
>> 
>> Could you offer a bit more info on why you would want it?  Like what kind of SIP phones are still out there that cannot handle the SIP auth specs in 2021?  If you think about it, they won't work with other SIP servers: no commercial SIP server and no Asterisk, FS, PJSIP, SIP.js, drachtio, reSIPprocate, etc.:  Not a single one of these implement this crazy "ha1b" feature, and none of them give a single damn if the phone is poorly implemented and appends the "@realm" part in the username component: they will happily reply with 401 Unauthorized until the implementor fixes the phone.
>> 
>> So why should OpenSIPS have this feature? Also, I suggest you open a GitHub feature request [1] as well on this topic -- maybe we get more opinions from there as well.
>> 
>> [1]: https://github.com/OpenSIPS/opensips/issues
>> 
>> Best,
>> 
>> -- 
>> Liviu Chircu
>> www.twitter.com/liviuchircu | www.opensips-solutions.com
>> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210816/ea429b52/attachment.html>

From ag at ag-projects.com  Mon Aug 16 18:48:07 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Mon, 16 Aug 2021 15:48:07 -0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <38376add-bda2-59b4-a292-24c966925f84@opensips.org>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <7702150B-CEEA-48FD-AEF2-D3347F402F48@ag-projects.com>
 <38376add-bda2-59b4-a292-24c966925f84@opensips.org>
Message-ID: <09C61E98-9621-4AAE-954C-976CA3A3EBD2@ag-projects.com>

I confirm this patch fixed the issue. Thank you Liviu!

Regards,
Adrian


> On 16 Aug 2021, at 12:43, Liviu Chircu <liviu at opensips.org> wrote:
> 
> On 12.08.2021 22:04, Adrian Georgescu wrote:
>> Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of sync; you can't run this command now
>> Aug 12 20:51:59 live01 /usr/sbin/opensips[10064]: ERROR:auth_db:get_ha1: failed to query database
>> Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of sync; you can't run this command now
>> Aug 12 20:52:00 live01 /usr/sbin/opensips[10057]: ERROR:auth_db:get_ha1: failed to query database
> 
> Hi Adrian,
> 
> This issue should now be fixed on latest 3.2, per [1].
> 
> [1]: https://github.com/OpenSIPS/opensips/commit/c871d9edfce
> 
> Best,
> 
> -- 
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From liviu at opensips.org  Mon Aug 16 19:07:39 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 16 Aug 2021 22:07:39 +0300
Subject: [OpenSIPS-Users] auth_db module in 3.2.2
In-Reply-To: <669446E6-21D0-4DDC-A32C-639DC8784BC2@ag-projects.com>
References: <2728B611-4B69-46F1-A116-734421E29E4B@ag-projects.com>
 <75e8458a-996c-a263-1ae0-ace70ebfc960@opensips.org>
 <15B119EC-108B-4ED9-A8ED-E524D559CD03@ag-projects.com>
 <eb86e2e5-3523-bce5-29f4-0eebe1eafbba@opensips.org>
 <748F289F-12D7-4EFC-80CA-BE096B8213BD@ag-projects.com>
 <669446E6-21D0-4DDC-A32C-639DC8784BC2@ag-projects.com>
Message-ID: <dc01939c-ccc5-c879-85fa-9a0bc2238f2d@opensips.org>

On 16.08.2021 20:44, Adrian Georgescu wrote:
> There are some leftovers in the module documentation related to 
> password_column_2:
>
> https://opensips.org/html/docs/modules/3.2.x/auth_db.html#param_calculate_ha1 
> <https://opensips.org/html/docs/modules/3.2.x/auth_db.html#param_calculate_ha1>

Thank you!  Fixed!

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210816/2ee37709/attachment.html>

From liviu at opensips.org  Mon Aug 16 19:59:54 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 16 Aug 2021 22:59:54 +0300
Subject: [OpenSIPS-Users] /usr/sbin/opensips[7617]:
 ERROR:auth_db:get_ha1: failed to query database - Errors
In-Reply-To: <SI2PR06MB4345C7DC54649A8B56638020CFE99@SI2PR06MB4345.apcprd06.prod.outlook.com>
References: <SI2PR06MB4345C7DC54649A8B56638020CFE99@SI2PR06MB4345.apcprd06.prod.outlook.com>
Message-ID: <f470eb4d-bdd6-9cbc-559b-b1a5e8dd6a04@opensips.org>

Hi Shah,

On 27.07.2021 10:01, Shah Hussain Khattak wrote:
>
> 1 - When I try to configure the users via the OpenSIPs control panel, 
> I get following error when I click on Register:
>
> *Inserting user record into DB failed: Array ( [0] => 42S22 [1] => 
> 1054 [2] => Unknown column 'ha1b' in 'field list' )*
OpenSIPS CP should have support for 3.2, including the "ha1b" column 
changes.  Make sure you download/install the 8.3.2 version of the 
Control Panel and try again -- let me know if you still have issues here.
>
> but when alice is trying to register, I am seeing the following errors 
> in the syslog file:
>
> Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> INFO:db_mysql:switch_state_to_disconnected: disconnect event for 
> 0x7f51bb655e10
> Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> INFO:db_mysql:reset_all_statements: resetting all statements on 
> connection: (0x7f51bb6566b0) 0x7f51bb655e10
> Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> INFO:db_mysql:connect_with_retry: re-connected successful for 
> 0x7f51bb655e10
> Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> INFO:db_mysql:db_mysql_do_prepared_query: reconnected to mysql server 
> -> re-init the statement
> *Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of 
> sync; you can't run this command now*
> *Jul 27 05:35:17 ip-172-31-46-21 /usr/sbin/opensips[7618]: 
> ERROR:auth_db:get_ha1: failed to query database*
> *Jul 27 05:35:18 ip-172-31-46-21 /usr/sbin/opensips[7615]: 
> ERROR:db_mysql:db_mysql_store_result: driver error: Commands out of 
> sync; you can't run this command now*
> *Jul 27 05:35:18 ip-172-31-46-21 /usr/sbin/opensips[7615]: 
> ERROR:auth_db:get_ha1: failed to query database*

Indeed!  You have run into an OpenSIPS 3.2 bug, which is now fixed.  The 
3.2.1 release will be pushed tomorrow, so if you are using packages, I 
recommend you wait for it to become available.  If you're using git, 
just pull, rebuild and the bug should be gone!

Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210816/40f70383/attachment-0001.html>

From liviu at opensips.org  Mon Aug 16 20:06:15 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 16 Aug 2021 23:06:15 +0300
Subject: [OpenSIPS-Users] strange behavior with TCP reply port
In-Reply-To: <CAPhW+0KO7sv6U92h5WXM8XRZqSnbE_pKrqUuBoVHct3WbnWiKg@mail.gmail.com>
References: <CAPhW+0KO7sv6U92h5WXM8XRZqSnbE_pKrqUuBoVHct3WbnWiKg@mail.gmail.com>
Message-ID: <a779d09d-d4a9-6a31-7585-5a1c41817025@opensips.org>

On 11.08.2021 22:01, Jeff Pyle wrote:
> the sl_send_reply() function opens a new TCP socket to the UAC on the 
> IP:port listed in the original message's Contact, rather than sending 
> the 100 on the existing socket (using the ephemeral port)

Hi, Jeff!

Just to frame the problem better: are you sure the reply's target 
IP:port is equal to the request's Contact header and not the topmost Via 
header?  Maybe a /force_rport()/ before calling /sl_send_reply()/ is 
everything that's needed here.  *fingers crossed*

Best,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210816/57aeaec8/attachment.html>

From ag at ag-projects.com  Mon Aug 16 20:11:11 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Mon, 16 Aug 2021 17:11:11 -0300
Subject: [OpenSIPS-Users] TLS 3.2.0 experience
In-Reply-To: <C6E35A73-557C-42ED-885E-7EC1F968A8EC@ag-projects.com>
References: <3E3622D1-C75B-47AB-8132-4209CA318055@ag-projects.com>
 <C6E35A73-557C-42ED-885E-7EC1F968A8EC@ag-projects.com>
Message-ID: <FEC10527-A061-41FD-B162-F49A6D291E89@ag-projects.com>

Using wolfssl I experience the same behaviour:

57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)
Aug 16 20:29:57 live01 /usr/sbin/opensips[6932]: CRITICAL:core:io_watch_del: [TCP_main] invalid fd -841671744, not in [0, 53)


> On 16 Aug 2021, at 15:25, Adrian Georgescu <ag at ag-projects.com> wrote:
> 
> Also the server is using 100% CPU.
> 



From spanda at 3clogic.com  Tue Aug 17 10:40:12 2021
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 17 Aug 2021 16:10:12 +0530
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
Message-ID: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>

Hi All ,

I was trying to build opensips-3.2 from git . I am blocked in the
tls_wolfssl module . I don't need this
module . Is there any way to exclude this module?

If this is by default included the do let me know how to solve the error
below .






*make[1]: Entering directory
`/opt/opensips-3.2/modules/tls_wolfssl'configure: error: cannot find
install-sh, install.sh, or shtool in build-aux "."/build-auxmake[1]: ***
[lib/lib/libwolfssl.a] Error 1make[1]: Leaving directory
`/opt/opensips-3.2/modules/tls_wolfssl'make: *** [modules] Error 2*

*What should I do for this ? shtool is already installed . *

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210817/bc00eebc/attachment.html>

From liviu at opensips.org  Tue Aug 17 10:44:37 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Tue, 17 Aug 2021 13:44:37 +0300
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
In-Reply-To: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
References: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
Message-ID: <5e046676-adcc-346d-7bdc-0a0a16bcec87@opensips.org>

On 17.08.2021 13:40, Sasmita Panda wrote:
> I was trying to build opensips-3.2 from git . I am blocked in the 
> tls_wolfssl module . I don't need this
> module . Is there any way to exclude this module?

Hi Sasmita,

This module is already excluded by default.  Make sure to grab the new 
"exclude_modules=" settings from Makefile.conf.template, and not just 
copy-paste your previous Makefile.conf file before building the 3.2 tree.

Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From razvan at opensips.org  Tue Aug 17 11:54:31 2021
From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=)
Date: Tue, 17 Aug 2021 14:54:31 +0300
Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.4 and 3.2.1 minor releases
Message-ID: <c0e08283-d5bf-99a8-d897-c2603154b3e9@opensips.org>

Hi, All!

I am happy to announce you that two new minor releases are out: OpenSIPS 
3.1.4 and 3.2.1.
Both releases are part of our OpenSIPS LTS versions and contain only bug 
fixes, without any syntax changes, so there is no migration needed to 
use them. Therefore we strongly advise you to upgrade your setup to the 
latest available release.

Happy hacking!
-- 
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com


From spanda at 3clogic.com  Thu Aug 19 06:06:19 2021
From: spanda at 3clogic.com (Sasmita Panda)
Date: Thu, 19 Aug 2021 11:36:19 +0530
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
In-Reply-To: <CALf-Q45FYk1Odd-Xa9K2qZO1MSb7C+hojxAs-0u4-XEwp7hiBQ@mail.gmail.com>
References: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
 <b30db6aa-25a8-891c-4389-a1439a1d6b4b@teconisy.com>
 <CALf-Q45FYk1Odd-Xa9K2qZO1MSb7C+hojxAs-0u4-XEwp7hiBQ@mail.gmail.com>
Message-ID: <CALf-Q47tcqA_CU5bwH6xH7KxaEQsjLz-H+5MaR5dFAVoiz-pig@mail.gmail.com>

Opensips-3.2 is crashing when I am starting the process  . Please do help .

Attached the logs in through the pastbean . Please have a look and suggest
how to fix this ..

https://pastebin.com/rkrq6L9w

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*


On Wed, Aug 18, 2021 at 10:12 AM Sasmita Panda <spanda at 3clogic.com> wrote:

> Hi ,
>
> You mean to say the proto_wss module is dependent on the tls_wolfssl
> module . I need proto_wss . proto_tls and tls_mgm .
>
> I had compiled and installed opensips-3.2 . tls_mgm module is dependent on
> tls_openssl or tls_wolfssl . I got this from opensips  documentation  . So
> I compiled with tls_openssl successfully'
>
> Please correct me If I did something wrong .
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Tue, Aug 17, 2021 at 8:00 PM Eugen Prieb <eugen at teconisy.com> wrote:
>
>> Hello,
>>
>> this module is excluded by default...
>>
>> make menuconfig --> Configure Compiling Option --> Configure Exluded
>> Modules ... and deselect "WSS Module"...
>> Save all changes and compile...
>> Am 17.08.2021 um 12:40 schrieb Sasmita Panda:
>>
>> Hi All ,
>>
>> I was trying to build opensips-3.2 from git . I am blocked in the
>> tls_wolfssl module . I don't need this
>> module . Is there any way to exclude this module?
>>
>> If this is by default included the do let me know how to solve the error
>> below .
>>
>>
>>
>>
>>
>>
>> *make[1]: Entering directory `/opt/opensips-3.2/modules/tls_wolfssl'
>> configure: error: cannot find install-sh, install.sh, or shtool in
>> build-aux "."/build-aux make[1]: *** [lib/lib/libwolfssl.a] Error 1
>> make[1]: Leaving directory `/opt/opensips-3.2/modules/tls_wolfssl' make:
>> *** [modules] Error 2 *
>>
>> *What should I do for this ? shtool is already installed . *
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210819/a0776df0/attachment.html>

From liviu at opensips.org  Thu Aug 19 06:37:10 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 19 Aug 2021 09:37:10 +0300
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
In-Reply-To: <CALf-Q47tcqA_CU5bwH6xH7KxaEQsjLz-H+5MaR5dFAVoiz-pig@mail.gmail.com>
References: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
 <b30db6aa-25a8-891c-4389-a1439a1d6b4b@teconisy.com>
 <CALf-Q45FYk1Odd-Xa9K2qZO1MSb7C+hojxAs-0u4-XEwp7hiBQ@mail.gmail.com>
 <CALf-Q47tcqA_CU5bwH6xH7KxaEQsjLz-H+5MaR5dFAVoiz-pig@mail.gmail.com>
Message-ID: <2155de78-789d-6220-27f9-2612df16facc@opensips.org>

On 19.08.2021 09:06, Sasmita Panda wrote:
> Opensips-3.2 is crashing when I am starting the process  . Please do 
> help .
>
> Attached the logs in through the pastbean . Please have a look and 
> suggest how to fix this ..
>
Hi, Sasmita!

Thank you for the nice logs, this bug is now fixed!  So you either have 
to wait until tomorrow's new package builds or you can grab the fix 
immediately if you are using git.

Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From spanda at 3clogic.com  Thu Aug 19 07:23:58 2021
From: spanda at 3clogic.com (Sasmita Panda)
Date: Thu, 19 Aug 2021 12:53:58 +0530
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
In-Reply-To: <2155de78-789d-6220-27f9-2612df16facc@opensips.org>
References: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
 <b30db6aa-25a8-891c-4389-a1439a1d6b4b@teconisy.com>
 <CALf-Q45FYk1Odd-Xa9K2qZO1MSb7C+hojxAs-0u4-XEwp7hiBQ@mail.gmail.com>
 <CALf-Q47tcqA_CU5bwH6xH7KxaEQsjLz-H+5MaR5dFAVoiz-pig@mail.gmail.com>
 <2155de78-789d-6220-27f9-2612df16facc@opensips.org>
Message-ID: <CALf-Q46N2o_GNYh3_Tke=abQUyOSx-JWksXFRTzPxVj_xz22YQ@mail.gmail.com>

git clone https://github.com/OpenSIPS/opensips.git -b 3.2 opensips-3.2

This will give me the latest git branch with fix ? or I need to do
something else ?

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*


On Thu, Aug 19, 2021 at 12:07 PM Liviu Chircu <liviu at opensips.org> wrote:

> On 19.08.2021 09:06, Sasmita Panda wrote:
> > Opensips-3.2 is crashing when I am starting the process  . Please do
> > help .
> >
> > Attached the logs in through the pastbean . Please have a look and
> > suggest how to fix this ..
> >
> Hi, Sasmita!
>
> Thank you for the nice logs, this bug is now fixed!  So you either have
> to wait until tomorrow's new package builds or you can grab the fix
> immediately if you are using git.
>
> Best Regards,
>
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210819/5a00eb08/attachment.html>

From liviu at opensips.org  Thu Aug 19 07:25:23 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 19 Aug 2021 10:25:23 +0300
Subject: [OpenSIPS-Users] Need help installing opensips-3.2 in centos 7 .
In-Reply-To: <CALf-Q46N2o_GNYh3_Tke=abQUyOSx-JWksXFRTzPxVj_xz22YQ@mail.gmail.com>
References: <CALf-Q46PSzURSDOU9_qBwCijUvWKBX3eRU3ewZwetcVKebjs_Q@mail.gmail.com>
 <b30db6aa-25a8-891c-4389-a1439a1d6b4b@teconisy.com>
 <CALf-Q45FYk1Odd-Xa9K2qZO1MSb7C+hojxAs-0u4-XEwp7hiBQ@mail.gmail.com>
 <CALf-Q47tcqA_CU5bwH6xH7KxaEQsjLz-H+5MaR5dFAVoiz-pig@mail.gmail.com>
 <2155de78-789d-6220-27f9-2612df16facc@opensips.org>
 <CALf-Q46N2o_GNYh3_Tke=abQUyOSx-JWksXFRTzPxVj_xz22YQ@mail.gmail.com>
Message-ID: <887b8966-cabe-13e2-33c8-850355edf186@opensips.org>

On 19.08.2021 10:23, Sasmita Panda wrote:
> This will give me the latest git branch with fix ?

Correct!

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From razvan at opensips.org  Thu Aug 19 14:44:51 2021
From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=)
Date: Thu, 19 Aug 2021 17:44:51 +0300
Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.5 and 3.2.2 minor releases
In-Reply-To: <c0e08283-d5bf-99a8-d897-c2603154b3e9@opensips.org>
References: <c0e08283-d5bf-99a8-d897-c2603154b3e9@opensips.org>
Message-ID: <f401622a-ce9e-832c-009f-59704c93a04c@opensips.org>

Hi, All!

Due to some unexpected regressions in the previous release, we've 
decided to make two new releases (just a few days apart): I'm talking 
about OpenSIPS 3.1.4 and 3.2.2.
This new release contains just a few crash fixes (in Dynamic Routing 
startup and in the binary replication protocol), as well as some 
cosmetic changes. There's no migration needed, so we strongly suggest 
you to upgrade to the latest release.

Happy hacking!

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 8/17/21 2:54 PM, Răzvan Crainea wrote:
> Hi, All!
> 
> I am happy to announce you that two new minor releases are out: OpenSIPS 
> 3.1.4 and 3.2.1.
> Both releases are part of our OpenSIPS LTS versions and contain only bug 
> fixes, without any syntax changes, so there is no migration needed to 
> use them. Therefore we strongly advise you to upgrade your setup to the 
> latest available release.
> 
> Happy hacking!


From jeff at ugnd.org  Thu Aug 19 19:10:35 2021
From: jeff at ugnd.org (Jeff Pyle)
Date: Thu, 19 Aug 2021 15:10:35 -0400
Subject: [OpenSIPS-Users] strange behavior with TCP reply port
In-Reply-To: <a779d09d-d4a9-6a31-7585-5a1c41817025@opensips.org>
References: <CAPhW+0KO7sv6U92h5WXM8XRZqSnbE_pKrqUuBoVHct3WbnWiKg@mail.gmail.com>
 <a779d09d-d4a9-6a31-7585-5a1c41817025@opensips.org>
Message-ID: <CAPhW+0KPbDMT2FHZ=NeozWeDR8V4b6f87XHa18c+0oNGmVA7Dw@mail.gmail.com>

Hi Liviu,

You're probably right.  And, force_rport() appears to solve the problem.
I'm calling it first thing in the script so all the replies go to the right
place.  Basic testing seems okay, even on UDP connections into proxy where
everything is 5060.

Do you have any thoughts what this might break?


- Jeff


On Mon, Aug 16, 2021 at 4:06 PM Liviu Chircu <liviu at opensips.org> wrote:

> On 11.08.2021 22:01, Jeff Pyle wrote:
>
> the sl_send_reply() function opens a new TCP socket to the UAC on the
> IP:port listed in the original message's Contact, rather than sending the
> 100 on the existing socket (using the ephemeral port)
>
> Hi, Jeff!
>
> Just to frame the problem better: are you sure the reply's target IP:port
> is equal to the request's Contact header and not the topmost Via header?
> Maybe a *force_rport()* before calling *sl_send_reply()* is everything
> that's needed here.  *fingers crossed*
>
> Best,
>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210819/72e08467/attachment.html>

From liviu at opensips.org  Thu Aug 19 19:57:13 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 19 Aug 2021 22:57:13 +0300
Subject: [OpenSIPS-Users] strange behavior with TCP reply port
In-Reply-To: <CAPhW+0KPbDMT2FHZ=NeozWeDR8V4b6f87XHa18c+0oNGmVA7Dw@mail.gmail.com>
References: <CAPhW+0KO7sv6U92h5WXM8XRZqSnbE_pKrqUuBoVHct3WbnWiKg@mail.gmail.com>
 <a779d09d-d4a9-6a31-7585-5a1c41817025@opensips.org>
 <CAPhW+0KPbDMT2FHZ=NeozWeDR8V4b6f87XHa18c+0oNGmVA7Dw@mail.gmail.com>
Message-ID: <1b12e06f-e994-4bb0-7e56-c147a3298dd0@opensips.org>

On 19.08.2021 22:10, Jeff Pyle wrote:
>
> Do you have any thoughts what this might break?

I wouldn't worry about it, as I've never seen a client complain that 
OpenSIPS included "received=xxx;rport=xxx" in the reply's Via header, so 
it can properly route the reply to its source port.  And even if some of 
these UACs do not support those RFC 3261 parameters, they will outright 
ignore them and process the reply normally.

Best,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From solarmon at one-n.co.uk  Fri Aug 20 09:15:01 2021
From: solarmon at one-n.co.uk (solarmon)
Date: Fri, 20 Aug 2021 10:15:01 +0100
Subject: [OpenSIPS-Users] Dispatcher and rtpproxy group IDs shown in dialog
	info?
Message-ID: <CAOXfywN6BD6x0K2dTUmGe9a2cHoD4W8NQkvCosMTjORVxCv_0g@mail.gmail.com>

Hi,

I'm using "opensipsctl fifo dlg_list_ctx" to get information on what active
dialogs there are.

I am also looking for information about what dispatcher and rtpproxy group
the call dialog is using. Is it possible to get this information for the
call dialog, or inject that information into the call dialog?

Or is that not the right place to get such information?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/45f50360/attachment.html>

From mark at allenclan.co.uk  Fri Aug 20 10:00:37 2021
From: mark at allenclan.co.uk (Mark Allen)
Date: Fri, 20 Aug 2021 11:00:37 +0100
Subject: [OpenSIPS-Users] rtpengine sets - load balancing proxy weighting
In-Reply-To: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
References: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
Message-ID: <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>

I've not been able to find the answer to this. Can anyone help?

On Thu, 22 Jul 2021 at 11:02, Mark Allen <mark at allenclan.co.uk> wrote:

> In the rtpengine documentation [1] in the section "1.2 - Multiple RTP
> proxy usage" it says...
>
>     "The balancing inside a set is done automatically by the module based
> on the weight of each RTP proxy from the set."
>
>
> ...how is the weighting determined? Is there a parameter to allocate a
> weighting value, is weighting allocated by the software dynamically (and if
> so, based on what criteria?), or are all proxies weighted the same?
>
>
>
> [1] https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/26193715/attachment.html>

From mark at allenclan.co.uk  Fri Aug 20 10:31:22 2021
From: mark at allenclan.co.uk (Mark Allen)
Date: Fri, 20 Aug 2021 11:31:22 +0100
Subject: [OpenSIPS-Users] Errors migrating mysql db from OpenSIPS 3.1 to 3.2
Message-ID: <CADaqb1uZ0NQxWV6Ng8Eyj8Pw4b9HiVaP+MrkNWNRiFh_3-POAA@mail.gmail.com>

I've followed the instructions at:
https://www.opensips.org/Documentation/Migration-3-1-0-to-3-2-0 but
OpenSIPS is now erroring because of DB problems. I see errors along the
lines of:

    ERROR:core:db_check_table_version: invalid version 0 for table xcap
found, expected 4

If I go into the database and manually add the version information for each
entry that triggers the error (xcap, presentity, active_watchers, watchers)
using command like...

    INSERT INTO version (table_name, table_version) VALUE ('xcap', 4);

...as per https://github.com/OpenSIPS/opensips-cli/issues/54 - it gets me
past theses tests but unsurprisingly then errors with:

    CRITICAL:db_mysql:wrapper_single_mysql_real_query: driver error (1146):
Table 'opensips_32.active_watchers' doesn't exist

On OpenSIPS 3.1 DB was loading/working without problem.

I have tried reinstalling opensips-cli using instructions at
https://github.com/OpenSIPS/opensips-cli/blob/master/docs/INSTALLATION.md
(using Debian package as this system runs Debian 10 (Buster) but I still
get the same problem.

Any ideas????
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/0adb7fc4/attachment-0001.html>

From john at voxtelesys.com  Fri Aug 20 13:38:06 2021
From: john at voxtelesys.com (John Burke)
Date: Fri, 20 Aug 2021 08:38:06 -0500
Subject: [OpenSIPS-Users] rtpengine sets - load balancing proxy weighting
In-Reply-To: <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
References: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
 <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
Message-ID: <75479ba7-0371-60d9-e052-b08c9ffafd05@voxtelesys.com>

Hey Mark,

The load balancing weights are set on a per node basis via their socket 
URL. If no weight is explicitly set, then the default is 1.

schema:
<proto>:<ip>:<port>(=<weight>)

ex:
udp:192.168.1.200:22222=25

There currently is no way to dynamically change the weight of a node, 
although there's an open PR [1] which would allow for weights to be 
changed via the "rtpengine_enable" MI command.

[1] https://github.com/OpenSIPS/opensips/pull/2600

Thanks,
John Burke


On 8/20/21 5:00 AM, Mark Allen wrote:
> I've not been able to find the answer to this. Can anyone help?
>
> On Thu, 22 Jul 2021 at 11:02, Mark Allen <mark at allenclan.co.uk 
> <mailto:mark at allenclan.co.uk>> wrote:
>
>     In the rtpengine documentation [1] in the section "1.2 - Multiple
>     RTP proxy usage" it says...
>
>       "The balancing inside a set is done automatically by the module
>     based on the weight of each RTP proxy from the set."
>
>
>     ...how is the weighting determined? Is there a parameter to
>     allocate a weighting value, is weighting allocated by the software
>     dynamically (and if so, based on what criteria?), or are all
>     proxies weighted the same?
>
>
>
>     [1]
>     https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616
>     <https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/7c54f67d/attachment.html>

From jeff at ugnd.org  Fri Aug 20 17:13:43 2021
From: jeff at ugnd.org (Jeff Pyle)
Date: Fri, 20 Aug 2021 13:13:43 -0400
Subject: [OpenSIPS-Users] rtpengine sets - load balancing proxy weighting
In-Reply-To: <75479ba7-0371-60d9-e052-b08c9ffafd05@voxtelesys.com>
References: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
 <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
 <75479ba7-0371-60d9-e052-b08c9ffafd05@voxtelesys.com>
Message-ID: <CAPhW+0Ls-Dj=AVNCJ+HFOmdyanCUn0RqZBNhW1+1EVUf5fVjJg@mail.gmail.com>

This may be a good place to ask this, or perhaps not.

Is it possible to define the DB rows in such a way that causes a
priority-based behavior?  Prefer this one, move to the next if the first
isn't available, etc.  As I think through it, it may be possible to do that
manually in the script by calling different groups, but it would be more
convenient if it just worked as a function of the schema.

For example, the way one defines gateways for use in the dr_carriers table
as part of the drouting module.  Something like that if that makes sense.


Regards,
Jeff


On Fri, Aug 20, 2021 at 9:38 AM John Burke via Users <
users at lists.opensips.org> wrote:

> Hey Mark,
>
> The load balancing weights are set on a per node basis via their socket
> URL. If no weight is explicitly set, then the default is 1.
>
> schema:
> <proto>:<ip>:<port>(=<weight>)
>
> ex:
> udp:192.168.1.200:22222=25
>
> There currently is no way to dynamically change the weight of a node,
> although there's an open PR [1] which would allow for weights to be changed
> via the "rtpengine_enable" MI command.
>
> [1] https://github.com/OpenSIPS/opensips/pull/2600
>
> Thanks,
> John Burke
>
>
> On 8/20/21 5:00 AM, Mark Allen wrote:
>
> I've not been able to find the answer to this. Can anyone help?
>
> On Thu, 22 Jul 2021 at 11:02, Mark Allen <mark at allenclan.co.uk> wrote:
>
>> In the rtpengine documentation [1] in the section "1.2 - Multiple RTP
>> proxy usage" it says...
>>
>>     "The balancing inside a set is done automatically by the module based
>> on the weight of each RTP proxy from the set."
>>
>>
>> ...how is the weighting determined? Is there a parameter to allocate a
>> weighting value, is weighting allocated by the software dynamically (and if
>> so, based on what criteria?), or are all proxies weighted the same?
>>
>>
>>
>> [1]
>> https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616
>>
>>
>>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/b1454ec7/attachment.html>

From mark at allenclan.co.uk  Fri Aug 20 17:56:42 2021
From: mark at allenclan.co.uk (Mark Allen)
Date: Fri, 20 Aug 2021 18:56:42 +0100
Subject: [OpenSIPS-Users] rtpengine sets - load balancing proxy weighting
In-Reply-To: <75479ba7-0371-60d9-e052-b08c9ffafd05@voxtelesys.com>
References: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
 <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
 <75479ba7-0371-60d9-e052-b08c9ffafd05@voxtelesys.com>
Message-ID: <CADaqb1t0rozhVY-w4HcX-fvuF054pvhU21JD8k8rWMhnrsUsdg@mail.gmail.com>

Thanks John. That's really helpful

On Fri, 20 Aug 2021, 14:40 John Burke via Users, <users at lists.opensips.org>
wrote:

> Hey Mark,
>
> The load balancing weights are set on a per node basis via their socket
> URL. If no weight is explicitly set, then the default is 1.
>
> schema:
> <proto>:<ip>:<port>(=<weight>)
>
> ex:
> udp:192.168.1.200:22222=25
>
> There currently is no way to dynamically change the weight of a node,
> although there's an open PR [1] which would allow for weights to be changed
> via the "rtpengine_enable" MI command.
>
> [1] https://github.com/OpenSIPS/opensips/pull/2600
>
> Thanks,
> John Burke
>
>
> On 8/20/21 5:00 AM, Mark Allen wrote:
>
> I've not been able to find the answer to this. Can anyone help?
>
> On Thu, 22 Jul 2021 at 11:02, Mark Allen <mark at allenclan.co.uk> wrote:
>
>> In the rtpengine documentation [1] in the section "1.2 - Multiple RTP
>> proxy usage" it says...
>>
>>     "The balancing inside a set is done automatically by the module based
>> on the weight of each RTP proxy from the set."
>>
>>
>> ...how is the weighting determined? Is there a parameter to allocate a
>> weighting value, is weighting allocated by the software dynamically (and if
>> so, based on what criteria?), or are all proxies weighted the same?
>>
>>
>>
>> [1]
>> https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616
>>
>>
>>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/e8989d56/attachment.html>

From kurgan-rus at inbox.ru  Mon Aug 23 11:02:43 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Mon, 23 Aug 2021 14:02:43 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?dialog-dlg-repl_-_not_synced?=
Message-ID: <1629716563.302878903@f737.i.mail.ru>


Hi list,
 
can not find the reason why MI ‘clusterer_list_cap’ command
shows that the dialog replication is not active.
 
It’s necessary to mention that profiles synced successfully,
when I configured it with the ‘profile_replication_cluster’ parameter (later I
removed this due to documentation [1] advice that it’s not necessary if dialog
replication is configured).
 
[1] https://opensips.org/docs/modules/3.1.x/dialog.html#dialog-clustering
 
 
Both instances use 3.1.5 version.
 
######## active node ########
...
modparam("clusterer", "db_mode", 0)
modparam("clusterer", "seed_fallback_interval", 10) # Only relevant for seed node
modparam("clusterer", "my_node_info",        "cluster_id=1,node_id=1,url=bin:10.10.10.11:5555,seed")
modparam("clusterer", "neighbor_node_info",    "cluster_id=1,node_id=2,url=bin:10.10.10.10:5555")
modparam("clusterer", "sharing_tag", "node1/1=active")
...
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "db_mode", 0)
modparam("dialog", "profiles_no_value", "inbound/s; outbound/s;")
modparam("dialog", "dialog_replication_cluster", 1)
…
...
    if (is_method("INVITE")) {
        create_dialog("B");
        set_dlg_sharing_tag("node1");
 
 
 
######## backup node ########
…
modparam("clusterer", "db_mode", 0)
modparam("clusterer", "seed_fallback_interval", 10) # Only relevant for seed node
modparam("clusterer", "my_node_info",        "cluster_id=1,node_id=2,url=bin:10.10.10.10:5555")
modparam("clusterer", "neighbor_node_info",    "cluster_id=1,node_id=1,url=bin:10.10.10.11:5555")
modparam("clusterer", "sharing_tag", "node2/1=backup")
...
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "db_mode", 0)
modparam("dialog", "profiles_no_value", "inbound/s; outbound/s;")
modparam("dialog", "dialog_replication_cluster", 1)
…
…
    if (is_method("INVITE")) {
        create_dialog("B");
        set_dlg_sharing_tag("node2");
 
 
 
 
With such configurations, both instances show ‘not synced’:
 
voip ~ # opensips-cli -x mi clusterer_list_cap
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Capabilities": [
                {
                    "name": "dialog-dlg-repl",
                    "state": "not synced"
                }
            ]
        }
    ]
}
 
 
Have I missed something in the configuration?
-----------------------------------------------
BR, Alexey
http://alexeyka.zantsev.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210823/692fea9c/attachment.html>

From kurgan-rus at inbox.ru  Mon Aug 23 13:01:02 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Mon, 23 Aug 2021 16:01:02 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?dialog-dlg-repl_-_not_synced?=
In-Reply-To: <1629716563.302878903@f737.i.mail.ru>
References: <1629716563.302878903@f737.i.mail.ru>
Message-ID: <1629723662.519611453@f706.i.mail.ru>


I changed a bit according to ‘active-backup’ scheme, but still the same.
 
### active node
modparam("clusterer", "sharing_tag", "vip/1=active")
 
 
### backup node
modparam("clusterer", "sharing_tag", "vip/1=backup")
 
And this for both nodes:

    if (is_method("INVITE")) {
        create_dialog("B");
        set_dlg_sharing_tag("vip");
 
 
-----------------------------------------------
BR, Alexey
http://alexeyka.zantsev.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210823/2a89dd44/attachment.html>

From tgrande at aligera.com.br  Mon Aug 23 20:59:27 2021
From: tgrande at aligera.com.br (Thomas Grande)
Date: Mon, 23 Aug 2021 17:59:27 -0300
Subject: [OpenSIPS-Users] Create REGISTER request from scratch
Message-ID: <CANMy1O2v3fipirseJn34JtF7be3D-9ABivnsTGpYLZrFkniz_A@mail.gmail.com>

Greetings,

I'm considering migrating from Kamailio to OpenSIPS due to some modules
that are missing on Kamailio, however I'm struggling to see a correspondent
to the Kamailio's uac_req_send() function, that basically allows me to send
any SIP request that I may need.

I checked B2BUA functionality, but for what I understood it only works for
INVITE dialogs.

Could you enlighten me on this one?

Best regards,

-- 
*Thomás Alimena Del Grande*
Engenharia - Aligera
Tel. 51 3500-0121
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210823/297ae452/attachment.html>

From alexei.vasilyev at gmail.com  Tue Aug 24 04:48:32 2021
From: alexei.vasilyev at gmail.com (Alexey Vasilyev)
Date: Tue, 24 Aug 2021 06:48:32 +0200
Subject: [OpenSIPS-Users] Create REGISTER request from scratch
In-Reply-To: <CANMy1O2v3fipirseJn34JtF7be3D-9ABivnsTGpYLZrFkniz_A@mail.gmail.com>
References: <CANMy1O2v3fipirseJn34JtF7be3D-9ABivnsTGpYLZrFkniz_A@mail.gmail.com>
Message-ID: <495D4E00-F25A-4D41-96B1-E1A9873E1F34@gmail.com>

Hi Thomas,

Please look at t_new_request:  https://opensips.org/docs/modules/3.2.x/tm.html#func_t_new_request

> 23 авг. 2021 г., в 22:59, Thomas Grande via Users <users at lists.opensips.org> написал(а):
> 
> Greetings,
> 
> I'm considering migrating from Kamailio to OpenSIPS due to some modules that are missing on Kamailio, however I'm struggling to see a correspondent to the Kamailio's uac_req_send() function, that basically allows me to send any SIP request that I may need.
> 
> I checked B2BUA functionality, but for what I understood it only works for INVITE dialogs.
> 
> Could you enlighten me on this one?
> 
> Best regards,
> 
> -- 
> Thomás Alimena Del Grande
> Engenharia - Aligera
> Tel. 51 3500-0121
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/a7309002/attachment.html>

From mark at allenclan.co.uk  Tue Aug 24 07:03:52 2021
From: mark at allenclan.co.uk (Mark Allen)
Date: Tue, 24 Aug 2021 08:03:52 +0100
Subject: [OpenSIPS-Users] OpenSIPS 3.1 Debian Buster package
Message-ID: <CADaqb1tF-hkyM5+nEma7=2JXmi5Ch4Mp5Jo-mSd2nwp6kOLeAQ@mail.gmail.com>

Hi all,

We're using a Debian Buster system. I've tried installing 3.2 but hit
problems with the database migration. I've tried to revert to 3.1 but can't
seem to access that versions package - 3.2 is the only one I can see.

As per https://apt.opensips.org/packages.php?v=3.1 I've entered...

    apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 049AD65B
    echo "deb https://apt.opensips.org buster 3.1-releases"
>/etc/apt/sources.list.d/opensips.list
    echo "deb https://apt.opensips.org buster cli-nightly"
>/etc/apt/sources.list.d/opensips-cli.list

...but the only version I can see with 'apt search opensips' is 3.2

If I try...

    apt install opensips=3.1

...or...

    apt install opensips=3.1.5

...nothing is found. How do I access the 3.1 package?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/ad293e54/attachment.html>

From mark at allenclan.co.uk  Tue Aug 24 07:24:01 2021
From: mark at allenclan.co.uk (Mark Allen)
Date: Tue, 24 Aug 2021 08:24:01 +0100
Subject: [OpenSIPS-Users] OpenSIPS 3.1 Debian Buster package
In-Reply-To: <CADaqb1tF-hkyM5+nEma7=2JXmi5Ch4Mp5Jo-mSd2nwp6kOLeAQ@mail.gmail.com>
References: <CADaqb1tF-hkyM5+nEma7=2JXmi5Ch4Mp5Jo-mSd2nwp6kOLeAQ@mail.gmail.com>
Message-ID: <CADaqb1spzuDeihbmbcFD4VVXJ5vPQWke+0NWsRGGSOOiRm=q3g@mail.gmail.com>

Ah! Scratch that. I've got it working now. What I was missing was that the
version for apt was 3.1.5-1, so...

    apt install opensips=3.1.5-1

...worked for me

On Tue, 24 Aug 2021 at 08:03, Mark Allen <mark at allenclan.co.uk> wrote:

> Hi all,
>
> We're using a Debian Buster system. I've tried installing 3.2 but hit
> problems with the database migration. I've tried to revert to 3.1 but can't
> seem to access that versions package - 3.2 is the only one I can see.
>
> As per https://apt.opensips.org/packages.php?v=3.1 I've entered...
>
>     apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 049AD65B
>     echo "deb https://apt.opensips.org buster 3.1-releases"
> >/etc/apt/sources.list.d/opensips.list
>     echo "deb https://apt.opensips.org buster cli-nightly"
> >/etc/apt/sources.list.d/opensips-cli.list
>
> ...but the only version I can see with 'apt search opensips' is 3.2
>
> If I try...
>
>     apt install opensips=3.1
>
> ...or...
>
>     apt install opensips=3.1.5
>
> ...nothing is found. How do I access the 3.1 package?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/cdb4964b/attachment.html>

From farmorg at gmail.com  Tue Aug 24 15:18:05 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Tue, 24 Aug 2021 16:18:05 +0100
Subject: [OpenSIPS-Users] OpenSIPs 3.2 wolfssl module compilation error
In-Reply-To: <e7c0919b-244c-4b8a-8674-ba5240dea79c@democon.be>
References: <2f2bda26-96a0-abce-172b-4bc0e0356595@bohboh.info>
 <c3d356c1-f912-7f1b-255b-bf07bfcb5056@opensips.org>
 <37a6581e-208a-76b2-b8de-742913a2ad6c@democon.be>
 <0b15afea-9f05-817e-9c6b-20fbd28c84d5@opensips.org>
 <e7c0919b-244c-4b8a-8674-ba5240dea79c@democon.be>
Message-ID: <CAOvQDesAwCR4wY7V1HW1SXOCFonRO0n9392KJ9j9xi7GK1WB=Q@mail.gmail.com>

Hi everyone

I am using the 3.2.2 tarball rather than cloning the Git repo and make
menuconfig to compile/install on Ubuntu 20.04.3.
I am getting the same error:

make[2]: Entering directory
'/usr/local/src/opensips/opensips-3.2.2/modules/tls_wolfssl'
/bin/sh: 3: ./autogen.sh: not found
env: ‘./configure’: No such file or directory
make[2]: *** [Makefile:15: lib/lib/libwolfssl.a] Error 127
make[2]: Leaving directory
'/usr/local/src/opensips/opensips-3.2.2/modules/tls_wolfssl'
make[1]: *** [Makefile:197: modules] Error 2
make[1]: Leaving directory '/usr/local/src/opensips/opensips-3.2.2'


Press any key to return to menuconfig

Has anyone else had the same problem?

Regards
Mark.


On Fri, 4 Jun 2021 at 09:01, johan <johan at democon.be> wrote:

> Apparently I missed that post.
>
> @Ovidiu Sas : well done, works like a charm.
>
>
> wkr,
>
> On 4/06/2021 09:21, Răzvan Crainea wrote:
> > Hi, Johan!
> >
> > My fix was related to the tar balls - for git cloning, please see
> > Ovidiu's reply [1].
> >
> > [1] http://lists.opensips.org/pipermail/devel/2021-June/028929.html
> >
> > Best regards,
> >
> > Răzvan Crainea
> > OpenSIPS Core Developer
> > http://www.opensips-solutions.com
> >
> > On 6/4/21 10:03 AM, johan wrote:
> >> good morning Razvan
> >>
> >>
> >> using : sudo git clone https://github.com/OpenSIPS/opensips.git -b 3.2
> >> opensips_3_2
> >>
> >>
> >>
> >> I still have below error
> >>
> >>
> >> make[2]: Entering directory '/usr/src/opensips_3_2/modules/tls_wolfssl'
> >> /bin/sh: 3: ./autogen.sh: not found
> >> env: ‘./configure’: No such file or directory
> >> make[2]: *** [Makefile:15: lib/lib/libwolfssl.a] Error 127
> >> make[2]: Leaving directory '/usr/src/opensips_3_2/modules/tls_wolfssl'
> >> make[1]: *** [Makefile:197: modules] Error 2
> >> make[1]: Leaving directory '/usr/src/opensips_3_2'
> >>
> >> On 3/06/2021 12:07, Răzvan Crainea wrote:
> >>> Hello!
> >>>
> >>> It looks like there was a problem building the tarball for the
> >>> 3.2-beta[1] and the wolfssl directory was not properly packed.
> >>> I've just fixed this, can you please pull the sources again?
> >>>
> >>> [1] https://opensips.org/pub/opensips/3.2.0/
> >>>
> >>> Best regards,
> >>>
> >>> Răzvan Crainea
> >>> OpenSIPS Core Developer
> >>> http://www.opensips-solutions.com
> >>>
> >>> On 5/25/21 2:38 AM, Social Boh wrote:
> >>>> Hello,
> >>>>
> >>>> I'm trying to install OpenSIPs 3.2 on Almalinux 8 (CentOS 8) and I
> >>>> can't compile this module:
> >>>>
> >>>> make[2]: se entra en el directorio
> >>>> '/usr/src/opensips_3_2/modules/wolfssl'
> >>>> /bin/sh: linea 2: ./autogen.sh: No such file or directory
> >>>>
> >>>> Any hint?
> >>>>
> >>>> Regards
> >>>>
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at lists.opensips.org
> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at lists.opensips.org
> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Mark Farmer
farmorg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/54fdf0df/attachment-0001.html>

From farmorg at gmail.com  Tue Aug 24 16:21:34 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Tue, 24 Aug 2021 17:21:34 +0100
Subject: [OpenSIPS-Users] OpenSIPs 3.2 wolfssl module compilation error
In-Reply-To: <CAOvQDesAwCR4wY7V1HW1SXOCFonRO0n9392KJ9j9xi7GK1WB=Q@mail.gmail.com>
References: <2f2bda26-96a0-abce-172b-4bc0e0356595@bohboh.info>
 <c3d356c1-f912-7f1b-255b-bf07bfcb5056@opensips.org>
 <37a6581e-208a-76b2-b8de-742913a2ad6c@democon.be>
 <0b15afea-9f05-817e-9c6b-20fbd28c84d5@opensips.org>
 <e7c0919b-244c-4b8a-8674-ba5240dea79c@democon.be>
 <CAOvQDesAwCR4wY7V1HW1SXOCFonRO0n9392KJ9j9xi7GK1WB=Q@mail.gmail.com>
Message-ID: <CAOvQDetxtZ92WDXYB_yW+E95Kp14wexyAv2Phshjjw2pVzZpkA@mail.gmail.com>

Looks like the same issue exists in the tarball.
The  directory modules/tls_wolfssl/lib/wolfssl/ is empty.

HTH
Mark.


On Tue, 24 Aug 2021 at 16:18, Mark Farmer <farmorg at gmail.com> wrote:

> Hi everyone
>
> I am using the 3.2.2 tarball rather than cloning the Git repo and make
> menuconfig to compile/install on Ubuntu 20.04.3.
> I am getting the same error:
>
> make[2]: Entering directory
> '/usr/local/src/opensips/opensips-3.2.2/modules/tls_wolfssl'
> /bin/sh: 3: ./autogen.sh: not found
> env: ‘./configure’: No such file or directory
> make[2]: *** [Makefile:15: lib/lib/libwolfssl.a] Error 127
> make[2]: Leaving directory
> '/usr/local/src/opensips/opensips-3.2.2/modules/tls_wolfssl'
> make[1]: *** [Makefile:197: modules] Error 2
> make[1]: Leaving directory '/usr/local/src/opensips/opensips-3.2.2'
>
>
> Press any key to return to menuconfig
>
> Has anyone else had the same problem?
>
> Regards
> Mark.
>
>
> On Fri, 4 Jun 2021 at 09:01, johan <johan at democon.be> wrote:
>
>> Apparently I missed that post.
>>
>> @Ovidiu Sas : well done, works like a charm.
>>
>>
>> wkr,
>>
>> On 4/06/2021 09:21, Răzvan Crainea wrote:
>> > Hi, Johan!
>> >
>> > My fix was related to the tar balls - for git cloning, please see
>> > Ovidiu's reply [1].
>> >
>> > [1] http://lists.opensips.org/pipermail/devel/2021-June/028929.html
>> >
>> > Best regards,
>> >
>> > Răzvan Crainea
>> > OpenSIPS Core Developer
>> > http://www.opensips-solutions.com
>> >
>> > On 6/4/21 10:03 AM, johan wrote:
>> >> good morning Razvan
>> >>
>> >>
>> >> using : sudo git clone https://github.com/OpenSIPS/opensips.git -b 3.2
>> >> opensips_3_2
>> >>
>> >>
>> >>
>> >> I still have below error
>> >>
>> >>
>> >> make[2]: Entering directory '/usr/src/opensips_3_2/modules/tls_wolfssl'
>> >> /bin/sh: 3: ./autogen.sh: not found
>> >> env: ‘./configure’: No such file or directory
>> >> make[2]: *** [Makefile:15: lib/lib/libwolfssl.a] Error 127
>> >> make[2]: Leaving directory '/usr/src/opensips_3_2/modules/tls_wolfssl'
>> >> make[1]: *** [Makefile:197: modules] Error 2
>> >> make[1]: Leaving directory '/usr/src/opensips_3_2'
>> >>
>> >> On 3/06/2021 12:07, Răzvan Crainea wrote:
>> >>> Hello!
>> >>>
>> >>> It looks like there was a problem building the tarball for the
>> >>> 3.2-beta[1] and the wolfssl directory was not properly packed.
>> >>> I've just fixed this, can you please pull the sources again?
>> >>>
>> >>> [1] https://opensips.org/pub/opensips/3.2.0/
>> >>>
>> >>> Best regards,
>> >>>
>> >>> Răzvan Crainea
>> >>> OpenSIPS Core Developer
>> >>> http://www.opensips-solutions.com
>> >>>
>> >>> On 5/25/21 2:38 AM, Social Boh wrote:
>> >>>> Hello,
>> >>>>
>> >>>> I'm trying to install OpenSIPs 3.2 on Almalinux 8 (CentOS 8) and I
>> >>>> can't compile this module:
>> >>>>
>> >>>> make[2]: se entra en el directorio
>> >>>> '/usr/src/opensips_3_2/modules/wolfssl'
>> >>>> /bin/sh: linea 2: ./autogen.sh: No such file or directory
>> >>>>
>> >>>> Any hint?
>> >>>>
>> >>>> Regards
>> >>>>
>> >>>
>> >>> _______________________________________________
>> >>> Users mailing list
>> >>> Users at lists.opensips.org
>> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> >>>
>> >>> _______________________________________________
>> >>> Users mailing list
>> >>> Users at lists.opensips.org
>> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users at lists.opensips.org
>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
> --
> Mark Farmer
> farmorg at gmail.com
>


-- 
Mark Farmer
farmorg at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/04ed5158/attachment.html>

From Louis.Rochon at comtechtel.com  Tue Aug 24 19:34:04 2021
From: Louis.Rochon at comtechtel.com (Louis Rochon)
Date: Tue, 24 Aug 2021 19:34:04 +0000
Subject: [OpenSIPS-Users] Route Header removal
Message-ID: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>

We are trying to remove the Route header from an incoming Invite.

Even with remove_hf, Opensips still routes towards the content of the Route header.

Opensips.cfg:
------------------
route {

if ( is_method("INVITE") ) {
.
.
.
xlog("removing Route Header: $(hdr(Route)[0])\n");
remove_hf("Route");
xlog( "Route Header still present?: $(hdr(Route)[0])\n");
};
.
.
.
And then we send the call to a b2b_init_request line.

Both xlogs show the route header still there. And indeed, the opensips attempts to route according to the contents of the route header.

Suggestions?


Louis
NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210824/290ee715/attachment.html>

From liviu at opensips.org  Wed Aug 25 06:20:39 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 25 Aug 2021 09:20:39 +0300
Subject: [OpenSIPS-Users] OpenSIPs 3.2 wolfssl module compilation error
In-Reply-To: <CAOvQDetxtZ92WDXYB_yW+E95Kp14wexyAv2Phshjjw2pVzZpkA@mail.gmail.com>
References: <2f2bda26-96a0-abce-172b-4bc0e0356595@bohboh.info>
 <c3d356c1-f912-7f1b-255b-bf07bfcb5056@opensips.org>
 <37a6581e-208a-76b2-b8de-742913a2ad6c@democon.be>
 <0b15afea-9f05-817e-9c6b-20fbd28c84d5@opensips.org>
 <e7c0919b-244c-4b8a-8674-ba5240dea79c@democon.be>
 <CAOvQDesAwCR4wY7V1HW1SXOCFonRO0n9392KJ9j9xi7GK1WB=Q@mail.gmail.com>
 <CAOvQDetxtZ92WDXYB_yW+E95Kp14wexyAv2Phshjjw2pVzZpkA@mail.gmail.com>
Message-ID: <45306e58-a203-4ed9-0d61-18070a7ab183@opensips.org>

On 24.08.2021 19:21, Mark Farmer wrote:
> Looks like the same issue exists in the tarball.
> The  directory modules/tls_wolfssl/lib/wolfssl/ is empty.
>
Hi, Mark!

Thank you for the report!  I've now fixed the tarball generation 
procedure, so this problem will no longer re-occur.

The issue was a missing "--recursive" option to the "git clone" command, 
so the WolfSSL sources were not getting pulled.  So this should solve 
your git-based approach as well.  An updated tarball is available on the 
Downloads.

Cheers,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2021 Distributed | www.opensips.org/events



From razvan at opensips.org  Wed Aug 25 10:03:49 2021
From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=)
Date: Wed, 25 Aug 2021 13:03:49 +0300
Subject: [OpenSIPS-Users] Route Header removal
In-Reply-To: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>
References: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>
Message-ID: <29bb50ac-fd9a-1579-b891-de73f4094998@opensips.org>

Hi, Louis!

Almost all changes (perhaps the only exception is the R-URI and parts of 
the Contact header) performed on the SIP message will only be visible in 
the outgoing message, but *NOT* reflected in the script. This means that 
whatever change you perform to the message will not be visible by the 
functions used - this is the intended behavior.
If you don't want to route according the the Record-Route algorithm, 
you'll have to catch the request in the local_route and force sending it 
to whatever other destination you want.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 8/24/21 10:34 PM, Louis Rochon wrote:
> We are trying to remove the Route header from an incoming Invite.
> 
> Even with remove_hf, Opensips still routes towards the content of the 
> Route header.
> 
> Opensips.cfg:
> 
> ------------------
> 
> route {
> 
> if ( is_method("INVITE") ) {
> 
> .
> 
> .
> 
> .
> 
> xlog("removing Route Header: $(hdr(Route)[0])\n");
> 
> remove_hf("Route");
> 
> xlog( "Route Header still present?: $(hdr(Route)[0])\n");
> 
> };
> 
> .
> 
> .
> 
> .
> 
> And then we send the call to a b2b_init_request line.
> 
> Both xlogs show the route header still there. And indeed, the opensips 
> attempts to route according to the contents of the route header.
> 
> Suggestions?
> 
> **
> 
> **
> 
> *Louis*
> 
> NOTICE TO RECIPIENT: This email, including attachments, may contain 
> information which is confidential, proprietary, attorney-client 
> privileged and / or controlled under U.S. export laws and regulations 
> and may be restricted from disclosure by applicable State and Federal 
> law. Nothing in this email shall create any legal binding agreement 
> between the parties unless expressly stated herein and provided by an 
> authorized representative of Comtech Telecommunications Corp. or its 
> subsidiaries. If you are not the intended recipient of this message, be 
> advised that any dissemination, distribution, or use of the contents of 
> this message is strictly prohibited. If you received this message in 
> error, please notify us immediately by return email and permanently 
> delete all copies of the original email and any attached documentation 
> from any computer or other media.
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 


From kurgan-rus at inbox.ru  Wed Aug 25 10:30:41 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Wed, 25 Aug 2021 13:30:41 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?dialog-dlg-repl_-_not_synced?=
In-Reply-To: <1629723662.519611453@f706.i.mail.ru>
References: <1629716563.302878903@f737.i.mail.ru>
 <1629723662.519611453@f706.i.mail.ru>
Message-ID: <1629887441.44935732@f703.i.mail.ru>


If I also enable profile replication, MI command shows that it’s synced successfully,
with the same settings as for other types of replication.
 
But the dialogs and dr_gateways status is not synced, according to MI output,
and I can not understand what’s wrong with the configuration.
Why something is synced and other is not.
 
 
modparam("clusterer", "my_node_info",             "cluster_id=1,node_id=1,url=bin:10.10.10.11:5555,seed")
modparam("clusterer", "neighbor_node_info",    "cluster_id=1,node_id=2,url=bin:10.10.10.10:5555")
modparam("clusterer", "sharing_tag", "vip/1=active")
 
modparam("dialog", "profiles_no_value", "inbound/b; outbound/b;")
modparam("dialog", "dialog_replication_cluster", 1)
modparam("dialog", "profile_replication_cluster", 1)
 
modparam("drouting", "cluster_id", 1)
modparam("drouting", "cluster_sharing_tag", "vip")
 
 
voip ~ # opensips-cli -x mi clusterer_list_cap
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Capabilities": [
                {
                    "name": "drouting-status-repl",
                    "state": "not synced"
                },
                {
                    "name": "dialog-dlg-repl",
                    "state": "not synced"
                },
                {
                    "name": "dialog-prof-repl",
                    "state": "Ok"
                }

 
 
 
-----------------------------------------------
BR, Alexey
http://alexeyka.zantsev.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210825/cef472da/attachment-0001.html>

From rob.dyck at telus.net  Wed Aug 25 16:56:01 2021
From: rob.dyck at telus.net (Rob Dyck)
Date: Wed, 25 Aug 2021 09:56:01 -0700
Subject: [OpenSIPS-Users] OpenSIPs 3.2 wolfssl module compilation error
In-Reply-To: <45306e58-a203-4ed9-0d61-18070a7ab183@opensips.org>
References: <2f2bda26-96a0-abce-172b-4bc0e0356595@bohboh.info>
 <CAOvQDetxtZ92WDXYB_yW+E95Kp14wexyAv2Phshjjw2pVzZpkA@mail.gmail.com>
 <45306e58-a203-4ed9-0d61-18070a7ab183@opensips.org>
Message-ID: <4792299.0VBMTVartN@blacky.mylan>

There still seems to be a problem and it exists for the tarball and git ( with workaround 
for autogen.sh ).

./configure: line 5272: syntax error near unexpected token `2.4.2' 
./configure: line 5272: `LT_PREREQ(2.4.2)' 
make[1]: *** [Makefile:15: lib/lib/libwolfssl.a] Error 2


On Tuesday, August 24, 2021 11:20:39 P.M. PDT Liviu Chircu wrote:
> On 24.08.2021 19:21, Mark Farmer wrote:
> > Looks like the same issue exists in the tarball.
> > The  directory modules/tls_wolfssl/lib/wolfssl/ is empty.
> 
> Hi, Mark!
> 
> Thank you for the report!  I've now fixed the tarball generation
> procedure, so this problem will no longer re-occur.
> 
> The issue was a missing "--recursive" option to the "git clone" command,
> so the WolfSSL sources were not getting pulled.  So this should solve
> your git-based approach as well.  An updated tarball is available on the
> Downloads.
> 
> Cheers,
> 
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2021 Distributed | www.opensips.org/events
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210825/5dc27c6b/attachment.html>

From tgrande at aligera.com.br  Wed Aug 25 20:58:05 2021
From: tgrande at aligera.com.br (Thomas Grande)
Date: Wed, 25 Aug 2021 17:58:05 -0300
Subject: [OpenSIPS-Users] Create REGISTER request from scratch
In-Reply-To: <495D4E00-F25A-4D41-96B1-E1A9873E1F34@gmail.com>
References: <CANMy1O2v3fipirseJn34JtF7be3D-9ABivnsTGpYLZrFkniz_A@mail.gmail.com>
 <495D4E00-F25A-4D41-96B1-E1A9873E1F34@gmail.com>
Message-ID: <CANMy1O0q9o+hPC-5b2_W3oW-NnE2MV+NeKmbzozUfT4A3Z45rQ@mail.gmail.com>

Hi Alexey,

I got it to send a REGISTER message, but without a contact header. Can it
be done with t_new_request?

Best regards,

Em ter., 24 de ago. de 2021 às 01:48, Alexey Vasilyev <
alexei.vasilyev at gmail.com> escreveu:

> Hi Thomas,
>
> Please look at t_new_request:
> https://opensips.org/docs/modules/3.2.x/tm.html#func_t_new_request
>
> 23 авг. 2021 г., в 22:59, Thomas Grande via Users <
> users at lists.opensips.org> написал(а):
>
> Greetings,
>
> I'm considering migrating from Kamailio to OpenSIPS due to some modules
> that are missing on Kamailio, however I'm struggling to see a correspondent
> to the Kamailio's uac_req_send() function, that basically allows me to send
> any SIP request that I may need.
>
> I checked B2BUA functionality, but for what I understood it only works for
> INVITE dialogs.
>
> Could you enlighten me on this one?
>
> Best regards,
>
> --
> *Thomás Alimena Del Grande*
> Engenharia - Aligera
> Tel. 51 3500-0121
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

-- 
*Thomás Alimena Del Grande*
Engenharia - Aligera
Tel. 51 3500-0121
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210825/98b72fb9/attachment.html>

From osas at voipembedded.com  Wed Aug 25 21:26:56 2021
From: osas at voipembedded.com (Ovidiu Sas)
Date: Wed, 25 Aug 2021 17:26:56 -0400
Subject: [OpenSIPS-Users] Create REGISTER request from scratch
In-Reply-To: <CANMy1O0q9o+hPC-5b2_W3oW-NnE2MV+NeKmbzozUfT4A3Z45rQ@mail.gmail.com>
References: <CANMy1O2v3fipirseJn34JtF7be3D-9ABivnsTGpYLZrFkniz_A@mail.gmail.com>
 <495D4E00-F25A-4D41-96B1-E1A9873E1F34@gmail.com>
 <CANMy1O0q9o+hPC-5b2_W3oW-NnE2MV+NeKmbzozUfT4A3Z45rQ@mail.gmail.com>
Message-ID: <CAND0LkuC2_jP3iLdZZHFpq0_06XTu46F8_xuXTry0pcLEv53+w@mail.gmail.com>

Use the registrant module and remove the contact header in the outgoing
route.

-ovidiu

On Wed, Aug 25, 2021 at 16:59 Thomas Grande via Users <
users at lists.opensips.org> wrote:

> Hi Alexey,
>
> I got it to send a REGISTER message, but without a contact header. Can it
> be done with t_new_request?
>
> Best regards,
>
> Em ter., 24 de ago. de 2021 às 01:48, Alexey Vasilyev <
> alexei.vasilyev at gmail.com> escreveu:
>
>> Hi Thomas,
>>
>> Please look at t_new_request:
>> https://opensips.org/docs/modules/3.2.x/tm.html#func_t_new_request
>>
>> 23 авг. 2021 г., в 22:59, Thomas Grande via Users <
>> users at lists.opensips.org> написал(а):
>>
>> Greetings,
>>
>> I'm considering migrating from Kamailio to OpenSIPS due to some modules
>> that are missing on Kamailio, however I'm struggling to see a correspondent
>> to the Kamailio's uac_req_send() function, that basically allows me to send
>> any SIP request that I may need.
>>
>> I checked B2BUA functionality, but for what I understood it only works
>> for INVITE dialogs.
>>
>> Could you enlighten me on this one?
>>
>> Best regards,
>>
>> --
>> *Thomás Alimena Del Grande*
>> Engenharia - Aligera
>> Tel. 51 3500-0121
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
> --
> *Thomás Alimena Del Grande*
> Engenharia - Aligera
> Tel. 51 3500-0121
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
VoIP Embedded, Inc.
http://www.voipembedded.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210825/57dfacc1/attachment.html>

From Louis.Rochon at comtechtel.com  Fri Aug 27 14:01:32 2021
From: Louis.Rochon at comtechtel.com (Louis Rochon)
Date: Fri, 27 Aug 2021 14:01:32 +0000
Subject: [OpenSIPS-Users] Route Header removal
In-Reply-To: <29bb50ac-fd9a-1579-b891-de73f4094998@opensips.org>
References: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>
 <29bb50ac-fd9a-1579-b891-de73f4094998@opensips.org>
Message-ID: <BLAPR09MB63401E25E245B245D65DBE5DE6C89@BLAPR09MB6340.namprd09.prod.outlook.com>

Răzvan,

Thank you for the quick response. 2 Notes:

1. I saw another post about the visibility of header changes post manipulation. I now understand the subtleties of that mechanism. Thanks!

2. I am trying to remove the "Route" header, and not the "Record-Route" header. From my understanding, the Route header as the ability or override the R-URI. OpenSIPS does exactly that (as per spec.), which is why I want to remove it.

However, even " remove_hf("Route");" OpenSIPS still attempts to route based on the contents of the "Route" header.

Louis

-----Original Message-----
From: Users <users-bounces at lists.opensips.org> On Behalf Of Razvan Crainea
Sent: August 25, 2021 6:04 AM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] Route Header removal


WARNING: External Email: Exercise Caution

Hi, Louis!

Almost all changes (perhaps the only exception is the R-URI and parts of the Contact header) performed on the SIP message will only be visible in the outgoing message, but *NOT* reflected in the script. This means that whatever change you perform to the message will not be visible by the functions used - this is the intended behavior.
If you don't want to route according the the Record-Route algorithm, you'll have to catch the request in the local_route and force sending it to whatever other destination you want.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=9Fz%2FcUnMykh6fP8LgaDgVSF%2FKEbdKIaXA%2FEkACXvTKQ%3D&amp;reserved=0

On 8/24/21 10:34 PM, Louis Rochon wrote:
> We are trying to remove the Route header from an incoming Invite.
>
> Even with remove_hf, Opensips still routes towards the content of the
> Route header.
>
> Opensips.cfg:
>
> ------------------
>
> route {
>
> if ( is_method("INVITE") ) {
>
> .
>
> .
>
> .
>
> xlog("removing Route Header: $(hdr(Route)[0])\n");
>
> remove_hf("Route");
>
> xlog( "Route Header still present?: $(hdr(Route)[0])\n");
>
> };
>
> .
>
> .
>
> .
>
> And then we send the call to a b2b_init_request line.
>
> Both xlogs show the route header still there. And indeed, the opensips
> attempts to route according to the contents of the route header.
>
> Suggestions?
>
> **
>
> **
>
> *Louis*
>
> NOTICE TO RECIPIENT: This email, including attachments, may contain
> information which is confidential, proprietary, attorney-client
> privileged and / or controlled under U.S. export laws and regulations
> and may be restricted from disclosure by applicable State and Federal
> law. Nothing in this email shall create any legal binding agreement
> between the parties unless expressly stated herein and provided by an
> authorized representative of Comtech Telecommunications Corp. or its
> subsidiaries. If you are not the intended recipient of this message,
> be advised that any dissemination, distribution, or use of the
> contents of this message is strictly prohibited. If you received this
> message in error, please notify us immediately by return email and
> permanently delete all copies of the original email and any attached
> documentation from any computer or other media.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists
> .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%
> 7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca
> 9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown
> %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
> XVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXI
> yc%3D&amp;reserved=0
>

_______________________________________________
Users mailing list
Users at lists.opensips.org
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXIyc%3D&amp;reserved=0
NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.


From john at voxtelesys.com  Fri Aug 27 19:45:05 2021
From: john at voxtelesys.com (John Burke)
Date: Fri, 27 Aug 2021 14:45:05 -0500
Subject: [OpenSIPS-Users] Route Header removal
In-Reply-To: <BLAPR09MB63401E25E245B245D65DBE5DE6C89@BLAPR09MB6340.namprd09.prod.outlook.com>
References: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>
 <29bb50ac-fd9a-1579-b891-de73f4094998@opensips.org>
 <BLAPR09MB63401E25E245B245D65DBE5DE6C89@BLAPR09MB6340.namprd09.prod.outlook.com>
Message-ID: <06da4575-0aec-1847-5111-051f7c231292@voxtelesys.com>

Hey Louis,

I thought I might jump in here about your point (2).  If you are 
referring to preloaded Route header(s) in the initial request, then you 
just need to take care when calling the loose_route [1] method. If you 
don't trust, or want to disregard, any preloaded Routes then don't call 
loose_route and remove the header via remove_hf to prevent downstream 
proxies from potentially mis-routing the request.  There are cases when 
you may want to allow loose routing of preloaded sets, such as in the 
case of a mid-registrar with Path support [2].

[1] https://opensips.org/html/docs/modules/devel/rr.html#func_loose_route
[2] https://opensips.org/html/docs/modules/devel/path.html

_Example:_
route {
     ...
     #sequential routing
     ...
     #process preloaded routes
     if (is_present_hf("Route")) {
             if (...) { # honor routes
                     loose_route();
                     t_relay();
                     exit;
             } else {   # don't process and strip routes
                     remove_hf("Route");
             }
     }
     ...
}


Thanks,
John Burke
**
*
*
On 8/27/21 9:01 AM, Louis Rochon wrote:
> Răzvan,
>
> Thank you for the quick response. 2 Notes:
>
> 1. I saw another post about the visibility of header changes post manipulation. I now understand the subtleties of that mechanism. Thanks!
>
> 2. I am trying to remove the "Route" header, and not the "Record-Route" header. From my understanding, the Route header as the ability or override the R-URI. OpenSIPS does exactly that (as per spec.), which is why I want to remove it.
>
> However, even " remove_hf("Route");" OpenSIPS still attempts to route based on the contents of the "Route" header.
>
> Louis
>
> -----Original Message-----
> From: Users <users-bounces at lists.opensips.org> On Behalf Of Razvan Crainea
> Sent: August 25, 2021 6:04 AM
> To: users at lists.opensips.org
> Subject: Re: [OpenSIPS-Users] Route Header removal
>
>
> WARNING: External Email: Exercise Caution
>
> Hi, Louis!
>
> Almost all changes (perhaps the only exception is the R-URI and parts of the Contact header) performed on the SIP message will only be visible in the outgoing message, but *NOT* reflected in the script. This means that whatever change you perform to the message will not be visible by the functions used - this is the intended behavior.
> If you don't want to route according the the Record-Route algorithm, you'll have to catch the request in the local_route and force sending it to whatever other destination you want.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=9Fz%2FcUnMykh6fP8LgaDgVSF%2FKEbdKIaXA%2FEkACXvTKQ%3D&amp;reserved=0
>
> On 8/24/21 10:34 PM, Louis Rochon wrote:
>> We are trying to remove the Route header from an incoming Invite.
>>
>> Even with remove_hf, Opensips still routes towards the content of the
>> Route header.
>>
>> Opensips.cfg:
>>
>> ------------------
>>
>> route {
>>
>> if ( is_method("INVITE") ) {
>>
>> .
>>
>> .
>>
>> .
>>
>> xlog("removing Route Header: $(hdr(Route)[0])\n");
>>
>> remove_hf("Route");
>>
>> xlog( "Route Header still present?: $(hdr(Route)[0])\n");
>>
>> };
>>
>> .
>>
>> .
>>
>> .
>>
>> And then we send the call to a b2b_init_request line.
>>
>> Both xlogs show the route header still there. And indeed, the opensips
>> attempts to route according to the contents of the route header.
>>
>> Suggestions?
>>
>> **
>>
>> **
>>
>> *Louis*
>>
>> NOTICE TO RECIPIENT: This email, including attachments, may contain
>> information which is confidential, proprietary, attorney-client
>> privileged and / or controlled under U.S. export laws and regulations
>> and may be restricted from disclosure by applicable State and Federal
>> law. Nothing in this email shall create any legal binding agreement
>> between the parties unless expressly stated herein and provided by an
>> authorized representative of Comtech Telecommunications Corp. or its
>> subsidiaries. If you are not the intended recipient of this message,
>> be advised that any dissemination, distribution, or use of the
>> contents of this message is strictly prohibited. If you received this
>> message in error, please notify us immediately by return email and
>> permanently delete all copies of the original email and any attached
>> documentation from any computer or other media.
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists
>> .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%
>> 7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca
>> 9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown
>> %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
>> XVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXI
>> yc%3D&amp;reserved=0
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXIyc%3D&amp;reserved=0
> NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210827/bc534827/attachment.html>

From file2122 at gmail.com  Mon Aug 30 07:22:17 2021
From: file2122 at gmail.com (Fulo Lin)
Date: Mon, 30 Aug 2021 15:22:17 +0800
Subject: [OpenSIPS-Users] How to handle concurrent answering calls?
Message-ID: <CAMADgHpTeFdTA40JqbN3cfRxTj8dhX5v6FuGcc-Y7DvBtiVMRA@mail.gmail.com>

When the user has two devices answering the phone at the same time, I
expect the first device to answer the call and the second device to be
cancelled.

The current opensips will indeed cancel the second call, but the first call
will have no sound, and the call will be disconnected after a few seconds.

I found that opensips sends all 200 Ok (SDP) to the caller, and I expect
that the second 200 Ok (SDP) should not be sent to the caller.

I try to block the second 200 Ok(SDP) in onreply_route, like this.

onreply_route[handle_nat] {
         if (t_check_status("200")) {
                 # t_cancel_branch(); No effect
                 # drop(); No effect
                 #exit;
         }
}

But this seems to have no effect.

Is there a way to block the second 200 Ok (SDP) in onreply_route?

Or is there any other way to handle concurrent answering calls?

I use opensips 3.1.5 and rtpproxy 2.2.0.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210830/d82923fb/attachment.html>

From volga629 at networklab.ca  Mon Aug 30 12:34:59 2021
From: volga629 at networklab.ca (volga629)
Date: Mon, 30 Aug 2021 09:34:59 -0300
Subject: [OpenSIPS-Users] How to handle concurrent answering calls?
In-Reply-To: <CAMADgHpTeFdTA40JqbN3cfRxTj8dhX5v6FuGcc-Y7DvBtiVMRA@mail.gmail.com>
References: <CAMADgHpTeFdTA40JqbN3cfRxTj8dhX5v6FuGcc-Y7DvBtiVMRA@mail.gmail.com>
Message-ID: <ac32802c-895c-20c6-3657-f21f81c121f1@skillsearch.ca>

An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210830/b1920014/attachment.html>

From rembgrets at gmail.com  Tue Aug 31 10:33:11 2021
From: rembgrets at gmail.com (ryan embgrets)
Date: Tue, 31 Aug 2021 15:33:11 +0500
Subject: [OpenSIPS-Users] Opensips taking a lot of private memoy with
	drouting/mongodb
Message-ID: <CAJ_X8k7GG9nRM34tNgqvfhERctR89+pQO3e65H48w8ZAgNrh5A@mail.gmail.com>

Greetings,

I am using opensips version: opensips 3.1.3 (x86_64/linux) with drouting
module on the top of mongodb.

I see my opensips dr_reload getting failed with below error.

Aug 31 10:20:57 opensips /usr/sbin/opensips[32163]: WARNING:core:fm_malloc:
not enough continuous free pkg memory (20047472 bytes left, need 22020096),
attempting defragmentation... please increase the "-M" command line
parameter!
Aug 31 10:20:57 opensips /usr/sbin/opensips[32163]: ERROR:core:fm_malloc:
not enough free pkg memory (20047472 bytes left, need 22020096), please
increase the "-M" command line parameter!
Aug 31 10:20:57 opensips /usr/sbin/opensips[32163]:
ERROR:core:db_realloc_rows: no memory left
Aug 31 10:20:57 opensips /usr/sbin/opensips[32163]:
ERROR:cachedb_mongodb:mongo_db_query_trans: failed to realloc rows
Aug 31 10:20:57 opensips /usr/sbin/opensips[32163]:
ERROR:drouting:dr_load_routing_info: DB query failed

There are just 50k Recods inside the drouting table and i have specified -M
50MB for the opensips with 8 children.

Why opensips is complaining about private memory? should not be the
drouting records into shared memory ?

I have another setup on mysql where i have more than 0.5M records and
opensips runs fine with 16MB private memory.

Any pointer what might be causing this is appreciated.

Ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210831/bdac4a81/attachment.html>

From Louis.Rochon at comtechtel.com  Tue Aug 31 20:43:36 2021
From: Louis.Rochon at comtechtel.com (Louis Rochon)
Date: Tue, 31 Aug 2021 20:43:36 +0000
Subject: [OpenSIPS-Users] Route Header removal
In-Reply-To: <06da4575-0aec-1847-5111-051f7c231292@voxtelesys.com>
References: <BLAPR09MB634040EA80E0952FBAA43D47E6C59@BLAPR09MB6340.namprd09.prod.outlook.com>
 <29bb50ac-fd9a-1579-b891-de73f4094998@opensips.org>
 <BLAPR09MB63401E25E245B245D65DBE5DE6C89@BLAPR09MB6340.namprd09.prod.outlook.com>
 <06da4575-0aec-1847-5111-051f7c231292@voxtelesys.com>
Message-ID: <BLAPR09MB6340A60D07800FCAECE2B903E6CC9@BLAPR09MB6340.namprd09.prod.outlook.com>

Mr. Burke,

Yes indeed, I looked into how I was using loose_route and that was the problem!

Thanks for the great find!

regards,

Louis Rochon
________________________________
From: Users <users-bounces at lists.opensips.org> on behalf of John Burke via Users <users at lists.opensips.org>
Sent: August 27, 2021 3:45 PM
To: users at lists.opensips.org <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Route Header removal




WARNING: External Email: Exercise Caution

Hey Louis,

I thought I might jump in here about your point (2).  If you are referring to preloaded Route header(s) in the initial request, then you just need to take care when calling the loose_route [1] method.  If you don't trust, or want to disregard, any preloaded Routes then don't call loose_route and remove the header via remove_hf to prevent downstream proxies from potentially mis-routing the request.  There are cases when you may want to allow loose routing of preloaded sets, such as in the case of a mid-registrar with Path support [2].

[1] https://opensips.org/html/docs/modules/devel/rr.html#func_loose_route<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Fhtml%2Fdocs%2Fmodules%2Fdevel%2Frr.html%23func_loose_route&data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cfa785681107c4848338c08d969934aa7%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637656903637083313%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6VQl33o3LiPX%2Bf%2Buzk1Vh9JYTiLgnJfUHcVuUcnt1%2Bo%3D&reserved=0>
[2] https://opensips.org/html/docs/modules/devel/path.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Fhtml%2Fdocs%2Fmodules%2Fdevel%2Fpath.html&data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cfa785681107c4848338c08d969934aa7%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637656903637093269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qvZvtxuyAjEYdQhdvEFLj8zReoo3wHEpnC1%2BAfi6sK4%3D&reserved=0>

Example:
route {
    ...
    #sequential routing
    ...
    #process preloaded routes
    if (is_present_hf("Route")) {
            if (...) { # honor routes
                    loose_route();
                    t_relay();
                    exit;
            } else {   # don't process and strip routes
                    remove_hf("Route");
            }
    }
    ...
}


Thanks,
John Burke

On 8/27/21 9:01 AM, Louis Rochon wrote:

Răzvan,

Thank you for the quick response. 2 Notes:

1. I saw another post about the visibility of header changes post manipulation. I now understand the subtleties of that mechanism. Thanks!

2. I am trying to remove the "Route" header, and not the "Record-Route" header. From my understanding, the Route header as the ability or override the R-URI. OpenSIPS does exactly that (as per spec.), which is why I want to remove it.

However, even " remove_hf("Route");" OpenSIPS still attempts to route based on the contents of the "Route" header.

Louis

-----Original Message-----
From: Users <users-bounces at lists.opensips.org><mailto:users-bounces at lists.opensips.org> On Behalf Of Razvan Crainea
Sent: August 25, 2021 6:04 AM
To: users at lists.opensips.org<mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Route Header removal


WARNING: External Email: Exercise Caution

Hi, Louis!

Almost all changes (perhaps the only exception is the R-URI and parts of the Contact header) performed on the SIP message will only be visible in the outgoing message, but *NOT* reflected in the script. This means that whatever change you perform to the message will not be visible by the functions used - this is the intended behavior.
If you don't want to route according the the Record-Route algorithm, you'll have to catch the request in the local_route and force sending it to whatever other destination you want.

Best regards,

Răzvan Crainea
OpenSIPS Core Developer
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=9Fz%2FcUnMykh6fP8LgaDgVSF%2FKEbdKIaXA%2FEkACXvTKQ%3D&amp;reserved=0<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cfa785681107c4848338c08d969934aa7%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637656903637093269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2F1leryLAZUa5VH97%2BoHFQFhYfp%2B6dsQ%2F1hxsLT8FMSU%3D&reserved=0>

On 8/24/21 10:34 PM, Louis Rochon wrote:


We are trying to remove the Route header from an incoming Invite.

Even with remove_hf, Opensips still routes towards the content of the
Route header.

Opensips.cfg:

------------------

route {

if ( is_method("INVITE") ) {

.

.

.

xlog("removing Route Header: $(hdr(Route)[0])\n");

remove_hf("Route");

xlog( "Route Header still present?: $(hdr(Route)[0])\n");

};

.

.

.

And then we send the call to a b2b_init_request line.

Both xlogs show the route header still there. And indeed, the opensips
attempts to route according to the contents of the route header.

Suggestions?

**

**

*Louis*

NOTICE TO RECIPIENT: This email, including attachments, may contain
information which is confidential, proprietary, attorney-client
privileged and / or controlled under U.S. export laws and regulations
and may be restricted from disclosure by applicable State and Federal
law. Nothing in this email shall create any legal binding agreement
between the parties unless expressly stated herein and provided by an
authorized representative of Comtech Telecommunications Corp. or its
subsidiaries. If you are not the intended recipient of this message,
be advised that any dissemination, distribution, or use of the
contents of this message is strictly prohibited. If you received this
message in error, please notify us immediately by return email and
permanently delete all copies of the original email and any attached
documentation from any computer or other media.

_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists
.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%
7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca
9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown
%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJ
XVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXI
yc%3D&amp;reserved=0




_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&amp;data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cac163de2930d4203b8b508d967afbbdb%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637654826786421255%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=SQ6Z9NSskYelktXtqBTHCBy73ryDA0FdRdSdhmJXIyc%3D&amp;reserved=0<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cfa785681107c4848338c08d969934aa7%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637656903637093269%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6fhr7Rovr7dKqRmXWuziuMlsvIvdoi5Dt%2F8JylZGJXk%3D&reserved=0>
NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media.

_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=04%7C01%7CLouis.Rochon%40comtechtel.com%7Cfa785681107c4848338c08d969934aa7%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637656903637103219%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NCOpfsMk%2BPKlnkiPHEuAd5FgcPqiusPQstBUcmWsaAc%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210831/e42b0677/attachment-0001.html>

From john at voxtelesys.com  Fri Aug 20 13:21:13 2021
From: john at voxtelesys.com (John Burke)
Date: Fri, 20 Aug 2021 13:21:13 -0000
Subject: [OpenSIPS-Users] rtpengine sets - load balancing proxy weighting
In-Reply-To: <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
References: <CADaqb1vYO-O9qOon_jygh313x7pc5Vjd1wncanw0DYK0C9Ff0g@mail.gmail.com>
 <CADaqb1vyn8prbP9xej314dtH=6Kq-r3J1ZX0-uCFu3u2XNeDdA@mail.gmail.com>
Message-ID: <77d38a0e-705e-d1c8-2532-7bcaeb2e669d@voxtelesys.com>

Hey Mark,

The load balancing weights are set on a per node basis via their socket 
URL. If no weight is explicitly set, then the default is 1.

schema:
<proto>:<ip>:<port>(=<weight>)

ex:
udp:192.168.1.200:22222=25

There currently is no way to dynamically change the weight of a node, 
although there's an open PR [1] which would allow for weights to be 
changed via the "rtpengine_enable" MI command.

[1] https://github.com/OpenSIPS/opensips/pull/2600

Thanks,
John



On 8/20/21 5:00 AM, Mark Allen wrote:
> I've not been able to find the answer to this. Can anyone help?
>
> On Thu, 22 Jul 2021 at 11:02, Mark Allen <mark at allenclan.co.uk 
> <mailto:mark at allenclan.co.uk>> wrote:
>
>     In the rtpengine documentation [1] in the section "1.2 - Multiple
>     RTP proxy usage" it says...
>
>       "The balancing inside a set is done automatically by the module
>     based on the weight of each RTP proxy from the set."
>
>
>     ...how is the weighting determined? Is there a parameter to
>     allocate a weighting value, is weighting allocated by the software
>     dynamically (and if so, based on what criteria?), or are all
>     proxies weighted the same?
>
>
>
>     [1]
>     https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616
>     <https://opensips.org/html/docs/modules/3.1.x/rtpengine.html#idp4123616>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210820/8ebb25f7/attachment-0001.html>

From volga629 at skillsearch.ca  Mon Aug 30 12:25:49 2021
From: volga629 at skillsearch.ca (volga629)
Date: Mon, 30 Aug 2021 12:25:49 -0000
Subject: [OpenSIPS-Users] How to handle concurrent answering calls?
In-Reply-To: <CAMADgHpTeFdTA40JqbN3cfRxTj8dhX5v6FuGcc-Y7DvBtiVMRA@mail.gmail.com>
References: <CAMADgHpTeFdTA40JqbN3cfRxTj8dhX5v6FuGcc-Y7DvBtiVMRA@mail.gmail.com>
Message-ID: <28f9f432-bd6d-aa58-d603-3f4d11313b4d@skillsearch.ca>

An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20210830/629b8dc0/attachment-0001.html>