From johan at democon.be  Fri Dec  1 15:16:36 2023
From: johan at democon.be (johan)
Date: Fri, 1 Dec 2023 16:16:36 +0100
Subject: [OpenSIPS-Users] on SIP number presentation.
Message-ID: <b402c235-c35c-4556-b2ec-5329f89186c2@democon.be>

All,

the opinions are divided on this at 2 very big customers.

with number presentation allowed, what is displayed to the B user if the 
following 3 headers have different numbers in the invite.

- pai

- ppi

- from.


to me, the answer is that from takes precedence.


what is the list's opinion.



From Ben.Newlin at genesys.com  Fri Dec  1 16:08:30 2023
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Fri, 1 Dec 2023 16:08:30 +0000
Subject: [OpenSIPS-Users] on SIP number presentation.
In-Reply-To: <b402c235-c35c-4556-b2ec-5329f89186c2@democon.be>
References: <b402c235-c35c-4556-b2ec-5329f89186c2@democon.be>
Message-ID: <BN0PR10MB52085A6FA452C9C3FB3AA3279581A@BN0PR10MB5208.namprd10.prod.outlook.com>

I agree with you. The From number should always be what is displayed to the called party.

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of johan <johan at democon.be>
Date: Friday, December 1, 2023 at 10:20 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: [OpenSIPS-Users] on SIP number presentation.
 EXTERNAL EMAIL - Please use caution with links and attachments

All,

the opinions are divided on this at 2 very big customers.

with number presentation allowed, what is displayed to the B user if the
following 3 headers have different numbers in the invite.

- pai

- ppi

- from.


to me, the answer is that from takes precedence.


what is the list's opinion.


_______________________________________________
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/20231201/2cf3e827/attachment.html>

From prathibhab.tvm at gmail.com  Mon Dec  4 12:27:05 2023
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Mon, 4 Dec 2023 17:57:05 +0530
Subject: [OpenSIPS-Users] Dialplan
Message-ID: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>

How to write dialplan to route the calls coming to 112, to one of the free
call takers?

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231204/c0a3bb35/attachment.html>

From prathibhab.tvm at gmail.com  Mon Dec  4 12:30:58 2023
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Mon, 4 Dec 2023 18:00:58 +0530
Subject: [OpenSIPS-Users] Dialplan
In-Reply-To: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
References: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
Message-ID: <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>

How to identify a free call taker in the group?

On Mon, 4 Dec 2023 at 17:57, Prathibha B <prathibhab.tvm at gmail.com> wrote:

> How to write dialplan to route the calls coming to 112, to one of the free
> call takers?
>
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231204/a8d6b3c8/attachment.html>

From bogdan at opensips.org  Tue Dec  5 09:33:24 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 11:33:24 +0200
Subject: [OpenSIPS-Users] Help dropping SQL injection attacks
In-Reply-To: <d762af95-cf4a-4015-9a9c-1ce42d2cd0dc@switchtel.co.za>
References: <d762af95-cf4a-4015-9a9c-1ce42d2cd0dc@switchtel.co.za>
Message-ID: <7721d776-dcf5-4271-ae48-ef565b4e5569@opensips.org>

Hi Gregory,

As it is said, there is no single way to skin the cat :). Your approach 
is a valid one, by using the escaping transformation. Maybe you should 
check the s.escape.user [1].

Such checks make sense when using avp_db_query(), so raw queries. The 
internal queries (like auth, etc) are done via prepared statements, so 
safe to injections.

[1] https://www.opensips.org/Documentation/Script-Tran-3-2#s.escape.user

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 30.11.2023 02:34, Gregory Massel via Users wrote:
>
> Hi all
>
> I'm wondering what the best practice is in terms of detection and 
> dropping attempted SQL injection attacks?
>
> Is something like the following adequate or can this be enhanced:
>
> if ( $fU != $(fU{s.escape.common}) || $tU != $(tU{s.escape.common}) ) {
> 	drop();
> }
>
> Obviously this does not remove the need to escape anything passed to 
> avp_db_query(), however, what I want to do is identify these sorts of 
> attacks at the top of the script and avoid processing.
>
> To date all the attacks I've seen focus on the contact and from user, 
> e.g.:
> INVITEsip:00111390237920793 at x.x.x.x:5060;transport=UDP  SIP/2.0
> Contact:<sip:a'or'3=3-- at x.x.x.x:5060;transport=UDP>
> To:<sip:00111390237920793 at x.x.x.x;transport=UDP>
> From:<sip:a'or'3=3-- at x.x.x.x;transport=UDP>;tag=v2pjtxqb
> I'm not quite sure how to match the Contact user. Would the following 
> work?
> if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) {
> 	drop();
> }
> -- 
> Regards
> *Gregory Massel*
>
> _______________________________________________
> 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/20231205/3b9f3100/attachment.html>

From bogdan at opensips.org  Tue Dec  5 09:34:40 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 11:34:40 +0200
Subject: [OpenSIPS-Users] Dialplan
In-Reply-To: <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>
References: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
 <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>
Message-ID: <f517938d-03de-4ca0-91ae-cd5626a6a63c@opensips.org>

What do you mean by "free call taker in the group" ? something like in 
call centers?

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 04.12.2023 14:30, Prathibha B wrote:
> How to identify a free call taker in the group?
>
> On Mon, 4 Dec 2023 at 17:57, Prathibha B <prathibhab.tvm at gmail.com> wrote:
>
>     How to write dialplan to route the calls coming to 112, to one of
>     the free call takers?
>
>     -- 
>     Regards,
>     B.Prathibha
>
>
>
> -- 
> Regards,
> B.Prathibha
>
> _______________________________________________
> 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/20231205/24e0b316/attachment.html>

From jehanzaib.kiani at gmail.com  Tue Dec  5 09:40:34 2023
From: jehanzaib.kiani at gmail.com (Jehanzaib Younis)
Date: Tue, 5 Dec 2023 22:40:34 +1300
Subject: [OpenSIPS-Users] CANCEL handling issue
In-Reply-To: <CAKrJzCz+mD2Of3yAZFRdUyhojveCjir-guDet0VQ4vSgrJAysg@mail.gmail.com>
References: <CALOQYisnNcQ-wOfrdSpb9dN8VG5zdF5=Y1=0K7N6JG2yJ=oy2A@mail.gmail.com>
 <a01547c4-c302-5bf0-6ee4-5267cab24a56@opensips.org>
 <CALOQYitt5UgVUJ0Xt_1iAMLZVODmkre5PbdN4B8XiaFjqDah2g@mail.gmail.com>
 <c32c37dc-fa6d-97a8-829b-962940ee5449@opensips.org>
 <CALOQYisHrUxNw4ArN0myGpZ28jLhqSiP3BMJgY5nH1ak4krmow@mail.gmail.com>
 <6a74b7b1-b9eb-12ac-b7c4-bf2a77f62ceb@opensips.org>
 <CALOQYisscw0DJJU22t1FO+pgbV7edyqQb+qeq2tDKZ=FwUG_xg@mail.gmail.com>
 <f65c57aa-5487-4c0e-b38d-769384197f20@opensips.org>
 <CAKrJzCysnx0LmZRLSphH5imQwUzSAoYDiPZtPTmrNx3Vtwvakg@mail.gmail.com>
 <CAKrJzCz+mD2Of3yAZFRdUyhojveCjir-guDet0VQ4vSgrJAysg@mail.gmail.com>
Message-ID: <CAKrJzCyUcCYiC2HzNs3FfitiQt+2NVBnU_Re_7Jn2imBzTHNRA@mail.gmail.com>

Hi Bogdan,

I have the same issue, i have just upgraded the opensips to 3.4.2 version.
It did not fix the issue but the other issue iam getting is t_relay is not
accepting any parameter.
The documentation is not clearly saying how to put *no-auto-477* - (old
*0x02* flag). in my old 3.3.2 version i used to t_relay(2) but it is not
working in the 3.4.2 version anymore. i tried all the options but none of
them is working.


Regards,
Jehanzaib


On Tue, Nov 28, 2023 at 10:54 PM Jehanzaib Younis <jehanzaib.kiani at gmail.com>
wrote:

> I have the exact same issue. I am also not able to change the Via header.
>
> Regards,
> Jehanzaib
>
>
> On Tue, Nov 28, 2023 at 10:48 PM Jehanzaib Younis <
> jehanzaib.kiani at gmail.com> wrote:
>
>> Hi Bogdan,
>>
>> The only difference is, I am receiving traffic on UDP and sending on TCP
>> socket.
>> sorry i forgot to mention before the advertised_address is
>> globally defined (public ip)
>>
>>
>> Regards,
>> Jehanzaib
>>
>>
>> On Tue, Nov 28, 2023 at 10:26 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi,
>>>
>>> I just made a simple test using only `advertised_address` and calling
>>> from A to B and cancelling from A. The CANCEL from OpenSIPS to B obeys the
>>> advertising. I used the latest 3.3 :
>>>     version: opensips 3.3.8 (x86_64/linux)
>>>
>>> Tested with both UDP and TCP, worked in both cases.
>>>
>>> SO, try also the latest 3.3, to see if it works for you too. If not, try
>>> to put together a minimal cfg to support user registration + calls between
>>> users, cfg to show the problem.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>>   https://www.siphub.com
>>>
>>> On 27.11.2023 13:44, nz deals wrote:
>>>
>>> Hi Bogdan,
>>> No other advertisement via socket definition or any script function.
>>>
>>> Thank you
>>>
>>> On Fri, 24 Nov 2023 at 05:47, Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> wrote:
>>>
>>>> Just checking, only the `advertised_address` global param [1], no other
>>>> kind of advertising (via socket definition or script function) ?
>>>>
>>>> [1]
>>>> https://www.opensips.org/Documentation/Script-CoreParameters-3-3#advertised_address
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>   https://www.opensips-solutions.com
>>>>   https://www.siphub.com
>>>>
>>>> On 11/22/23 10:47 PM, nz deals wrote:
>>>>
>>>> Hi Bogdan,
>>>> My opensips version is opensips 3.3.5 (x86_64/linux)
>>>>
>>>> Regards,
>>>> Jason
>>>>
>>>> On Thu, 23 Nov 2023 at 01:49, Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>> wrote:
>>>>
>>>>> What is your exact opensips version ( `opensips -V` ) ?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>>
>>>>> OpenSIPS Founder and Developer
>>>>>   https://www.opensips-solutions.com
>>>>>   https://www.siphub.com
>>>>>
>>>>> On 11/22/23 12:24 PM, nz deals wrote:
>>>>>
>>>>> Thanks Bogdan,
>>>>>
>>>>> It is due to receiving CANCEL from the caller. Yes using an
>>>>> advertised_address globally. One of our public addresses.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Wed, 22 Nov 2023 at 23:08, Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Jason,
>>>>>>
>>>>>> The CANCEL generated by OpenSIPS, is it due to a received CANCEL or
>>>>>> due to an internal timeout / forking? ALso do you use any advertising in
>>>>>> your setup? if yes, is it per socket, global or ?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bogdan-Andrei Iancu
>>>>>>
>>>>>> OpenSIPS Founder and Developer
>>>>>>   https://www.opensips-solutions.com
>>>>>>   https://www.siphub.com
>>>>>>
>>>>>> On 11/22/23 7:04 AM, nz deals wrote:
>>>>>>
>>>>>> Hi folks,
>>>>>>
>>>>>> Is there any bug in the CANCEL handling in the version 3.3.x?
>>>>>> I have a weird issue,
>>>>>> The INVITE have a VIA header as my private ip
>>>>>> Via: SIP/2.0/TCP 192.XX.XX.XX:5060;branch=XXXXXXX
>>>>>>
>>>>>> But when i CANCEL the call, the CANCEL have my public ip in the VIA
>>>>>> header.
>>>>>> Via: SIP/2.0/TCP 104.xx.xx.xx:5060;branch=xxxxxxx
>>>>>>
>>>>>> Anyway can I change the via in the cancel?
>>>>>>
>>>>>> Regards,
>>>>>> Jason
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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/20231205/278dfc9b/attachment-0001.html>

From andrew.colin at ipcortex.co.uk  Tue Dec  5 10:36:32 2023
From: andrew.colin at ipcortex.co.uk (Andrew Colin)
Date: Tue, 5 Dec 2023 10:36:32 +0000
Subject: [OpenSIPS-Users] Strange Nat issue
In-Reply-To: <c93dd9a7-ee46-444e-9543-18ea990eda0c@opensips.org>
References: <AM0PR07MB5249E18B61E4732DA083D63EA483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <2d3c557f-6b8b-4b2c-a955-4a711812fdd7@opensips.org>
 <AM0PR07MB52492F7FFD2E02075800B710A483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <aa476431-082a-4170-a2cc-274b6a2d94b1@opensips.org>
 <AM0PR07MB5249958E03F906A0C86217A1A483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <c93dd9a7-ee46-444e-9543-18ea990eda0c@opensips.org>
Message-ID: <AM0PR07MB52490A9BE464AB67AC2C45B3A485A@AM0PR07MB5249.eurprd07.prod.outlook.com>

Hi Razvan

The error I see is

No ack received for an extended period of time

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

From prathibhab.tvm at gmail.com  Tue Dec  5 10:49:53 2023
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Tue, 5 Dec 2023 16:19:53 +0530
Subject: [OpenSIPS-Users] Dialplan
In-Reply-To: <f517938d-03de-4ca0-91ae-cd5626a6a63c@opensips.org>
References: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
 <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>
 <f517938d-03de-4ca0-91ae-cd5626a6a63c@opensips.org>
Message-ID: <CAJh_-cC3MeSj05Ow4GagEdqr4S417=k+gxnkd4=7ZVb_1FjR7Q@mail.gmail.com>

Yes, you are right.

On Tue, 5 Dec 2023 at 15:04, Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> What do you mean by "free call taker in the group" ? something like in
> call centers?
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 04.12.2023 14:30, Prathibha B wrote:
>
> How to identify a free call taker in the group?
>
> On Mon, 4 Dec 2023 at 17:57, Prathibha B <prathibhab.tvm at gmail.com> wrote:
>
>> How to write dialplan to route the calls coming to 112, to one of the
>> free call takers?
>>
>> --
>> Regards,
>> B.Prathibha
>>
>
>
> --
> Regards,
> B.Prathibha
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231205/bf69d480/attachment.html>

From bogdan at opensips.org  Tue Dec  5 10:57:37 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 12:57:37 +0200
Subject: [OpenSIPS-Users] CANCEL handling issue
In-Reply-To: <CAKrJzCyUcCYiC2HzNs3FfitiQt+2NVBnU_Re_7Jn2imBzTHNRA@mail.gmail.com>
References: <CALOQYisnNcQ-wOfrdSpb9dN8VG5zdF5=Y1=0K7N6JG2yJ=oy2A@mail.gmail.com>
 <a01547c4-c302-5bf0-6ee4-5267cab24a56@opensips.org>
 <CALOQYitt5UgVUJ0Xt_1iAMLZVODmkre5PbdN4B8XiaFjqDah2g@mail.gmail.com>
 <c32c37dc-fa6d-97a8-829b-962940ee5449@opensips.org>
 <CALOQYisHrUxNw4ArN0myGpZ28jLhqSiP3BMJgY5nH1ak4krmow@mail.gmail.com>
 <6a74b7b1-b9eb-12ac-b7c4-bf2a77f62ceb@opensips.org>
 <CALOQYisscw0DJJU22t1FO+pgbV7edyqQb+qeq2tDKZ=FwUG_xg@mail.gmail.com>
 <f65c57aa-5487-4c0e-b38d-769384197f20@opensips.org>
 <CAKrJzCysnx0LmZRLSphH5imQwUzSAoYDiPZtPTmrNx3Vtwvakg@mail.gmail.com>
 <CAKrJzCz+mD2Of3yAZFRdUyhojveCjir-guDet0VQ4vSgrJAysg@mail.gmail.com>
 <CAKrJzCyUcCYiC2HzNs3FfitiQt+2NVBnU_Re_7Jn2imBzTHNRA@mail.gmail.com>
Message-ID: <a1cd41da-37e7-4840-8bbf-c3c3d86728f4@opensips.org>

Hi,

Could you please detail a bit your case? what kind of advertising are 
you using? per socket, global? ALso, an off-list pcap (covering both in 
and out traffic for opensips) will help.

In regards the t_relay, as per docs, just do t_relay("no-auto-477")

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 11:40, Jehanzaib Younis wrote:
> Hi Bogdan,
>
> I have the same issue, i have just upgraded the opensips to 3.4.2 
> version.  It did not fix the issue but the other issue iam getting is 
> t_relay is not accepting any parameter.
> The documentation is not clearly saying how to put /no-auto-477/ - 
> (old /0x02/ flag). in my old 3.3.2 version i used to t_relay(2) but it 
> is not working in the 3.4.2 version anymore. i tried all the options 
> but none of them is working.
>
>
> Regards,
> Jehanzaib
>
>
> On Tue, Nov 28, 2023 at 10:54 PM Jehanzaib Younis 
> <jehanzaib.kiani at gmail.com> wrote:
>
>     I have the exact same issue. I am also not able to change the Via
>     header.
>
>     Regards,
>     Jehanzaib
>
>
>     On Tue, Nov 28, 2023 at 10:48 PM Jehanzaib Younis
>     <jehanzaib.kiani at gmail.com> wrote:
>
>         Hi Bogdan,
>
>         The only difference is, I am receiving traffic on UDP and
>         sending on TCP socket.
>         sorry i forgot to mention before the advertised_address is
>         globally defined (public ip)
>
>
>         Regards,
>         Jehanzaib
>
>
>         On Tue, Nov 28, 2023 at 10:26 PM Bogdan-Andrei Iancu
>         <bogdan at opensips.org> wrote:
>
>             Hi,
>
>             I just made a simple test using only `advertised_address`
>             and calling from A to B and cancelling from A. The CANCEL
>             from OpenSIPS to B obeys the advertising. I used the
>             latest 3.3 :
>                 version: opensips 3.3.8 (x86_64/linux)
>
>             Tested with both UDP and TCP, worked in both cases.
>
>             SO, try also the latest 3.3, to see if it works for you
>             too. If not, try to put together a minimal cfg to support
>             user registration + calls between users, cfg to show the
>             problem.
>
>             Regards,
>
>             Bogdan-Andrei Iancu
>
>             OpenSIPS Founder and Developer
>                https://www.opensips-solutions.com
>                https://www.siphub.com
>
>             On 27.11.2023 13:44, nz deals wrote:
>>             Hi Bogdan,
>>             No other advertisement via socket definition or any
>>             script function.
>>
>>             Thank you
>>
>>             On Fri, 24 Nov 2023 at 05:47, Bogdan-Andrei Iancu
>>             <bogdan at opensips.org> wrote:
>>
>>                 Just checking, only the `advertised_address` global
>>                 param [1], no other kind of advertising (via socket
>>                 definition or script function) ?
>>
>>                 [1]
>>                 https://www.opensips.org/Documentation/Script-CoreParameters-3-3#advertised_address
>>
>>                 Regards,
>>
>>                 Bogdan-Andrei Iancu
>>
>>                 OpenSIPS Founder and Developer
>>                    https://www.opensips-solutions.com
>>                    https://www.siphub.com
>>
>>                 On 11/22/23 10:47 PM, nz deals wrote:
>>>                 Hi Bogdan,
>>>                 My opensips version is opensips 3.3.5 (x86_64/linux)
>>>
>>>                 Regards,
>>>                 Jason
>>>
>>>                 On Thu, 23 Nov 2023 at 01:49, Bogdan-Andrei Iancu
>>>                 <bogdan at opensips.org> wrote:
>>>
>>>                     What is your exact opensips version ( `opensips
>>>                     -V` ) ?
>>>
>>>                     Regards,
>>>
>>>                     Bogdan-Andrei Iancu
>>>
>>>                     OpenSIPS Founder and Developer
>>>                        https://www.opensips-solutions.com
>>>                        https://www.siphub.com
>>>
>>>                     On 11/22/23 12:24 PM, nz deals wrote:
>>>>                     Thanks Bogdan,
>>>>
>>>>                     It is due to receiving CANCEL from the caller.
>>>>                     Yes using an advertised_address globally. One
>>>>                     of our public addresses.
>>>>
>>>>                     Thanks
>>>>
>>>>                     On Wed, 22 Nov 2023 at 23:08, Bogdan-Andrei
>>>>                     Iancu <bogdan at opensips.org> wrote:
>>>>
>>>>                         Hi Jason,
>>>>
>>>>                         The CANCEL generated by OpenSIPS, is it due
>>>>                         to a received CANCEL or due to an internal
>>>>                         timeout / forking? ALso do you use any
>>>>                         advertising in your setup? if yes, is it
>>>>                         per socket, global or ?
>>>>
>>>>                         Regards,
>>>>
>>>>                         Bogdan-Andrei Iancu
>>>>
>>>>                         OpenSIPS Founder and Developer
>>>>                            https://www.opensips-solutions.com
>>>>                            https://www.siphub.com
>>>>
>>>>                         On 11/22/23 7:04 AM, nz deals wrote:
>>>>>                         Hi folks,
>>>>>
>>>>>                         Is there any bug in the CANCEL handling in
>>>>>                         the version 3.3.x?
>>>>>                         I have a weird issue,
>>>>>                         The INVITE have a VIA header as my private ip
>>>>>                         Via: SIP/2.0/TCP
>>>>>                         192.XX.XX.XX:5060;branch=XXXXXXX
>>>>>
>>>>>                         But when i CANCEL the call, the CANCEL
>>>>>                         have my public ip in the VIA header.
>>>>>                         Via: SIP/2.0/TCP
>>>>>                         104.xx.xx.xx:5060;branch=xxxxxxx
>>>>>
>>>>>                         Anyway can I change the via in the cancel?
>>>>>
>>>>>                         Regards,
>>>>>                         Jason
>>>>>
>>>>>                         _______________________________________________
>>>>>                         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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231205/900b9c8d/attachment-0001.html>

From bogdan at opensips.org  Tue Dec  5 10:58:57 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 12:58:57 +0200
Subject: [OpenSIPS-Users] Dialplan
In-Reply-To: <CAJh_-cC3MeSj05Ow4GagEdqr4S417=k+gxnkd4=7ZVb_1FjR7Q@mail.gmail.com>
References: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
 <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>
 <f517938d-03de-4ca0-91ae-cd5626a6a63c@opensips.org>
 <CAJh_-cC3MeSj05Ow4GagEdqr4S417=k+gxnkd4=7ZVb_1FjR7Q@mail.gmail.com>
Message-ID: <b5c6cfe9-929d-401a-97ce-dfe00d89123c@opensips.org>

Then take a look at the call_center module:
https://opensips.org/html/docs/modules/3.4.x/call_center.html

Regards

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 12:49, Prathibha B wrote:
> Yes, you are right.
>
> On Tue, 5 Dec 2023 at 15:04, Bogdan-Andrei Iancu <bogdan at opensips.org> 
> wrote:
>
>     What do you mean by "free call taker in the group" ? something
>     like in call centers?
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 04.12.2023 14:30, Prathibha B wrote:
>>     How to identify a free call taker in the group?
>>
>>     On Mon, 4 Dec 2023 at 17:57, Prathibha B
>>     <prathibhab.tvm at gmail.com> wrote:
>>
>>         How to write dialplan to route the calls coming to 112, to
>>         one of the free call takers?
>>
>>         -- 
>>         Regards,
>>         B.Prathibha
>>
>>
>>
>>     -- 
>>     Regards,
>>     B.Prathibha
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Regards,
> B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231205/049b0c7e/attachment.html>

From amel.guesmi at sofrecom.com  Tue Dec  5 11:01:43 2023
From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com)
Date: Tue, 5 Dec 2023 11:01:43 +0000
Subject: [OpenSIPS-Users] Staless mode in opensips
Message-ID: <89e2c7a66d51430c892754b558265caa@sofrecom.com>

Hi opensips experts,

We have always worked Opensips in a statefull mode and the first words in the routing module description are "OpenSIPS is basically only a transaction statefull proxy".

I've also seen that there was a stateless module "The SL module allows OpenSIPS to act as a stateless UA server and generate replies to SIP requests without keeping state" but is it possible to use functionality of Opensips like dialplan and dispatcher without keeping state of the dialog ?

Thanks for your help

On belhalf of my colleague Guillaume

BR, Amel

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

From Johan at democon.be  Tue Dec  5 11:08:34 2023
From: Johan at democon.be (Johan De Clercq)
Date: Tue, 5 Dec 2023 12:08:34 +0100
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
Message-ID: <CAEVWGm8Y4nLFx4RA-FSWvWTUx60BF=8LeEcTaR4Jr9RDKpG1yA@mail.gmail.com>

I usually make a mix f.e. on OPTIONS, subscribe, notify I send 200 OK with
sl_send_reply.
INVITE handling I always do stateful.
Normally, the dependencies of a module are described in the module
documentation.
I hope this helps.

BR, Johan.

Op di 5 dec 2023 om 12:04 schreef <amel.guesmi at sofrecom.com>:

> Hi opensips experts,
>
> We have always worked Opensips in a statefull mode and the first words in
> the routing module description are “OpenSIPS is basically *only* a
> transaction statefull proxy”.
>
> I’ve also seen that there was a stateless module “The SL module allows
> OpenSIPS to act as a stateless UA server and generate replies to SIP
> requests without keeping state” but is it possible to use functionality of
> Opensips like dialplan and dispatcher without keeping state of the dialog ?
>
> Thanks for your help
>
> On belhalf of my colleague Guillaume
>
> BR, Amel
>
>
> _______________________________________________
> 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/20231205/3d7f6ba2/attachment.html>

From bogdan at opensips.org  Tue Dec  5 11:14:36 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 13:14:36 +0200
Subject: [OpenSIPS-Users] Strange Nat issue
In-Reply-To: <AM0PR07MB52490A9BE464AB67AC2C45B3A485A@AM0PR07MB5249.eurprd07.prod.outlook.com>
References: <AM0PR07MB5249E18B61E4732DA083D63EA483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <2d3c557f-6b8b-4b2c-a955-4a711812fdd7@opensips.org>
 <AM0PR07MB52492F7FFD2E02075800B710A483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <aa476431-082a-4170-a2cc-274b6a2d94b1@opensips.org>
 <AM0PR07MB5249958E03F906A0C86217A1A483A@AM0PR07MB5249.eurprd07.prod.outlook.com>
 <c93dd9a7-ee46-444e-9543-18ea990eda0c@opensips.org>
 <AM0PR07MB52490A9BE464AB67AC2C45B3A485A@AM0PR07MB5249.eurprd07.prod.outlook.com>
Message-ID: <bfee83df-8f43-4ede-b4ac-b4f215fda97c@opensips.org>

Andrew,

Please capture (or xlog the Contact hdr) the 200 OK reply you receive 
from the callee. Most probably there is something weird with it, making 
the ACK to be badly routed.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 12:36, Andrew Colin via Users wrote:
>
> Hi Razvan
>
> The error I see is
>
> No ack received for an extended period of time
>
>
> _______________________________________________
> 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/20231205/d605747b/attachment-0001.html>

From bogdan at opensips.org  Tue Dec  5 11:16:36 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 5 Dec 2023 13:16:36 +0200
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
Message-ID: <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>

Hi,

Your post is a bit confusing when comes to state (and statefull) - are 
you talking about transaction statefull or dialog statefull ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 13:01, amel.guesmi at sofrecom.com wrote:
>
> Hi opensips experts,
>
> We have always worked Opensips in a statefull mode and the first words 
> in the routing module description are “OpenSIPS is basically /only/ a 
> transaction statefull proxy”.
>
> I’ve also seen that there was a stateless module “The SL module allows 
> OpenSIPS to act as a stateless UA server and generate replies to SIP 
> requests without keeping state” but is it possible to use 
> functionality of Opensips like dialplan and dispatcher without keeping 
> state of the dialog ?
>
> Thanks for your help
>
> On belhalf of my colleague Guillaume
>
> BR, Amel
>
>
> _______________________________________________
> 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/20231205/ce72cb48/attachment.html>

From prathibhab.tvm at gmail.com  Tue Dec  5 11:21:45 2023
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Tue, 5 Dec 2023 16:51:45 +0530
Subject: [OpenSIPS-Users] Dialplan
In-Reply-To: <b5c6cfe9-929d-401a-97ce-dfe00d89123c@opensips.org>
References: <CAJh_-cB4LQ6ekk1prYnk=dGFvKaC+inOXjZ7p=i3Mr4uFzNEeg@mail.gmail.com>
 <CAJh_-cB=bTb+y=0q9f1cSins6bp7O=Rz2GO+ADcCnefeAKg8kQ@mail.gmail.com>
 <f517938d-03de-4ca0-91ae-cd5626a6a63c@opensips.org>
 <CAJh_-cC3MeSj05Ow4GagEdqr4S417=k+gxnkd4=7ZVb_1FjR7Q@mail.gmail.com>
 <b5c6cfe9-929d-401a-97ce-dfe00d89123c@opensips.org>
Message-ID: <CAJh_-cB=46nPqyc69xqdct9FM5UfgweiggnA_RO6BGA9a8zcyg@mail.gmail.com>

Thanks, I'll check it out.

On Tue, 5 Dec 2023 at 16:29, Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Then take a look at the call_center module:
>     https://opensips.org/html/docs/modules/3.4.x/call_center.html
>
> Regards
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 05.12.2023 12:49, Prathibha B wrote:
>
> Yes, you are right.
>
> On Tue, 5 Dec 2023 at 15:04, Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> What do you mean by "free call taker in the group" ? something like in
>> call centers?
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 04.12.2023 14:30, Prathibha B wrote:
>>
>> How to identify a free call taker in the group?
>>
>> On Mon, 4 Dec 2023 at 17:57, Prathibha B <prathibhab.tvm at gmail.com>
>> wrote:
>>
>>> How to write dialplan to route the calls coming to 112, to one of the
>>> free call takers?
>>>
>>> --
>>> Regards,
>>> B.Prathibha
>>>
>>
>>
>> --
>> Regards,
>> B.Prathibha
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
> --
> Regards,
> B.Prathibha
>
>
>

-- 
Regards,
B.Prathibha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231205/7a20078b/attachment.html>

From greg at switchtel.co.za  Tue Dec  5 12:45:15 2023
From: greg at switchtel.co.za (Gregory Massel)
Date: Tue, 5 Dec 2023 14:45:15 +0200
Subject: [OpenSIPS-Users] Help dropping SQL injection attacks
In-Reply-To: <7721d776-dcf5-4271-ae48-ef565b4e5569@opensips.org>
References: <d762af95-cf4a-4015-9a9c-1ce42d2cd0dc@switchtel.co.za>
 <7721d776-dcf5-4271-ae48-ef565b4e5569@opensips.org>
Message-ID: <792aa98d-9e35-478a-b63e-50bc1d1a55d4@switchtel.co.za>

Thank you Bogdan!

It's worth noting that, if using {s.escape.user}, it won't detect a SQL 
injection, however, it may detect other potentially problematic 
characters, so one then has to apply both checks individually, e.g.

if ( $fU != $(fU{s.escape.common}) || $tU != $(tU{s.escape.common}) ) {
	xlog ("Rejecting SQL injection attempt received from $socket_in(proto):$si:$sp (Method: $rm; From: $fu; To: $tu; Contact: $ct).");
	send_reply (403,"Forbidden");
	exit;
}
if ( $fU != $(fU{s.escape.user}) || $tU != $(tU{s.escape.user}) ) {
	xlog ("Rejecting request with unusual characters received from $socket_in(proto):$si:$sp (Method: $rm; From: $fu; To: $tu; Contact: $ct).");
	send_reply (403,"Forbidden");
	exit;
}

So above doesn't block UTF-8; it just enforces that it must be received 
from the client in fully escaped form.

I'm gathering that UTF-8 is actually acceptable for the user part (and 
most other parts) of the URI, provided that it's encoded with '%'? I 
work with purely ASCII user parts however, out of interest, was 
wondering if it is allowable and/or commonplace to use Unicode extended 
character sets for any portions of the URI in parts of the world where 
other character sets are more frequently used? From what I could find, 
it seems that UTF16 is not allowed in the User Part and that the domain 
would be internationalised using Punycode, so the full URI should always 
be encoded in ASCII but with UTF-8 (but not UTF-16) permitted in 
%-encoded form for the user part?

With respect to the Contact header, I'm struggling a bit. Is the syntax 
below correct?

if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) {
	send_reply (403,"Forbidden");
	exit;
}

-- 
Thanks
*Gregory Massel*

On 2023-12-05 11:33, Bogdan-Andrei Iancu wrote:
> Hi Gregory,
>
> As it is said, there is no single way to skin the cat :). Your 
> approach is a valid one, by using the escaping transformation. Maybe 
> you should check the s.escape.user [1].
>
> Such checks make sense when using avp_db_query(), so raw queries. The 
> internal queries (like auth, etc) are done via prepared statements, so 
> safe to injections.
>
> [1] https://www.opensips.org/Documentation/Script-Tran-3-2#s.escape.user
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 30.11.2023 02:34, Gregory Massel via Users wrote:
>>
>> Hi all
>>
>> I'm wondering what the best practice is in terms of detection and 
>> dropping attempted SQL injection attacks?
>>
>> Is something like the following adequate or can this be enhanced:
>>
>> if ( $fU != $(fU{s.escape.common}) || $tU != $(tU{s.escape.common}) ) {
>> 	drop();
>> }
>>
>> Obviously this does not remove the need to escape anything passed to 
>> avp_db_query(), however, what I want to do is identify these sorts of 
>> attacks at the top of the script and avoid processing.
>>
>> To date all the attacks I've seen focus on the contact and from user, 
>> e.g.:
>> INVITEsip:00111390237920793 at x.x.x.x:5060;transport=UDP  SIP/2.0
>> Contact:<sip:a'or'3=3-- at x.x.x.x:5060;transport=UDP>
>> To:<sip:00111390237920793 at x.x.x.x;transport=UDP>
>> From:<sip:a'or'3=3-- at x.x.x.x;transport=UDP>;tag=v2pjtxqb
>> I'm not quite sure how to match the Contact user. Would the following 
>> work?
>> if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) {
>> 	drop();
>> }
>> -- 
>> Regards
>> *Gregory Massel*
>>
>> _______________________________________________
>> 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/20231205/95a89aed/attachment.html>

From amel.guesmi at sofrecom.com  Tue Dec  5 15:20:40 2023
From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com)
Date: Tue, 5 Dec 2023 15:20:40 +0000
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
 <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>
Message-ID: <82a9d9383dae484c916a069949974eae@sofrecom.com>

Hello
Sorry if I wasn’t clear.
We would like to implement a dialog stateless SIP proxy. Once the correct SIP routing is found, we would like to allow the SIP-based elements to perform midcall signaling directly with one another.
Best regards,


De : Users <users-bounces at lists.opensips.org> De la part de Bogdan-Andrei Iancu
Envoyé : mardi 5 décembre 2023 12:17
À : OpenSIPS users mailling list <users at lists.opensips.org>; GUESMI Amel SOFRECOM <amel.guesmi at sofrecom.com>
Cc : BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com>; DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
Objet : Re: [OpenSIPS-Users] Staless mode in opensips

Hi,

Your post is a bit confusing when comes to state (and statefull) - are you talking about transaction statefull or dialog statefull ?

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com
On 05.12.2023 13:01, amel.guesmi at sofrecom.com<mailto:amel.guesmi at sofrecom.com> wrote:

Hi opensips experts,

We have always worked Opensips in a statefull mode and the first words in the routing module description are “OpenSIPS is basically only a transaction statefull proxy”.

I’ve also seen that there was a stateless module “The SL module allows OpenSIPS to act as a stateless UA server and generate replies to SIP requests without keeping state” but is it possible to use functionality of Opensips like dialplan and dispatcher without keeping state of the dialog ?

Thanks for your help

On belhalf of my colleague Guillaume

BR, Amel




_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto: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/20231205/1e404410/attachment-0001.html>

From bogdan at opensips.org  Wed Dec  6 14:19:32 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 6 Dec 2023 16:19:32 +0200
Subject: [OpenSIPS-Users] Help dropping SQL injection attacks
In-Reply-To: <792aa98d-9e35-478a-b63e-50bc1d1a55d4@switchtel.co.za>
References: <d762af95-cf4a-4015-9a9c-1ce42d2cd0dc@switchtel.co.za>
 <7721d776-dcf5-4271-ae48-ef565b4e5569@opensips.org>
 <792aa98d-9e35-478a-b63e-50bc1d1a55d4@switchtel.co.za>
Message-ID: <eebd3c16-fcb1-4c01-9944-12dc463130b0@opensips.org>

Hi Gregory,

For the grammar of the SIP username, see the 
https://www.ietf.org/rfc/rfc3261.html, page 221 - you have all the 
details there.

For the contact test, yes, it should be correct.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 14:45, Gregory Massel wrote:
>
> Thank you Bogdan!
>
> It's worth noting that, if using {s.escape.user}, it won't detect a 
> SQL injection, however, it may detect other potentially problematic 
> characters, so one then has to apply both checks individually, e.g.
>
> if ( $fU != $(fU{s.escape.common}) || $tU != $(tU{s.escape.common}) ) {
> 	xlog ("Rejecting SQL injection attempt received from $socket_in(proto):$si:$sp (Method: $rm; From: $fu; To: $tu; Contact: $ct).");
> 	send_reply (403,"Forbidden");
> 	exit;
> }
> if ( $fU != $(fU{s.escape.user}) || $tU != $(tU{s.escape.user}) ) {
> 	xlog ("Rejecting request with unusual characters received from $socket_in(proto):$si:$sp (Method: $rm; From: $fu; To: $tu; Contact: $ct).");
> 	send_reply (403,"Forbidden");
> 	exit;
> }
>
> So above doesn't block UTF-8; it just enforces that it must be 
> received from the client in fully escaped form.
>
> I'm gathering that UTF-8 is actually acceptable for the user part (and 
> most other parts) of the URI, provided that it's encoded with '%'? I 
> work with purely ASCII user parts however, out of interest, was 
> wondering if it is allowable and/or commonplace to use Unicode 
> extended character sets for any portions of the URI in parts of the 
> world where other character sets are more frequently used? From what I 
> could find, it seems that UTF16 is not allowed in the User Part and 
> that the domain would be internationalised using Punycode, so the full 
> URI should always be encoded in ASCII but with UTF-8 (but not UTF-16) 
> permitted in %-encoded form for the user part?
>
> With respect to the Contact header, I'm struggling a bit. Is the 
> syntax below correct?
>
> if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) {
> 	send_reply (403,"Forbidden");
> 	exit;
> }
> -- 
> Thanks
> *Gregory Massel*
>
> On 2023-12-05 11:33, Bogdan-Andrei Iancu wrote:
>> Hi Gregory,
>>
>> As it is said, there is no single way to skin the cat :). Your 
>> approach is a valid one, by using the escaping transformation. Maybe 
>> you should check the s.escape.user [1].
>>
>> Such checks make sense when using avp_db_query(), so raw queries. The 
>> internal queries (like auth, etc) are done via prepared statements, 
>> so safe to injections.
>>
>> [1] https://www.opensips.org/Documentation/Script-Tran-3-2#s.escape.user
>>
>> Regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>> On 30.11.2023 02:34, Gregory Massel via Users wrote:
>>>
>>> Hi all
>>>
>>> I'm wondering what the best practice is in terms of detection and 
>>> dropping attempted SQL injection attacks?
>>>
>>> Is something like the following adequate or can this be enhanced:
>>>
>>> if ( $fU != $(fU{s.escape.common}) || $tU != $(tU{s.escape.common}) ) {
>>> 	drop();
>>> }
>>>
>>> Obviously this does not remove the need to escape anything passed to 
>>> avp_db_query(), however, what I want to do is identify these sorts 
>>> of attacks at the top of the script and avoid processing.
>>>
>>> To date all the attacks I've seen focus on the contact and from 
>>> user, e.g.:
>>> INVITEsip:00111390237920793 at x.x.x.x:5060;transport=UDP  SIP/2.0
>>> Contact:<sip:a'or'3=3-- at x.x.x.x:5060;transport=UDP>
>>> To:<sip:00111390237920793 at x.x.x.x;transport=UDP>
>>> From:<sip:a'or'3=3-- at x.x.x.x;transport=UDP>;tag=v2pjtxqb
>>> I'm not quite sure how to match the Contact user. Would the 
>>> following work?
>>> if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) {
>>> 	drop();
>>> }
>>> -- 
>>> Regards
>>> *Gregory Massel*
>>>
>>> _______________________________________________
>>> 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/20231206/b6df45c0/attachment.html>

From bogdan at opensips.org  Wed Dec  6 14:21:20 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 6 Dec 2023 16:21:20 +0200
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <82a9d9383dae484c916a069949974eae@sofrecom.com>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
 <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>
 <82a9d9383dae484c916a069949974eae@sofrecom.com>
Message-ID: <e387e7f3-cebe-437c-a2d1-03acdd4f3917@opensips.org>

Hi,

If you want your OpenSIPS not to stay in the middle of the dialog (after 
the initial request) you should not do any record_route() and you should 
not use the dialog module at all.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 05.12.2023 17:20, amel.guesmi at sofrecom.com wrote:
>
> Hello
>
> Sorry if I wasn’t clear.
>
> We would like to implement a dialog stateless SIP proxy. Once the 
> correct SIP routing is found, we would like to allow the SIP-based 
> elements to perform midcall signaling directly with one another.
>
> Best regards,
>
> *De :*Users <users-bounces at lists.opensips.org> *De la part de* 
> Bogdan-Andrei Iancu
> *Envoyé :* mardi 5 décembre 2023 12:17
> *À :* OpenSIPS users mailling list <users at lists.opensips.org>; GUESMI 
> Amel SOFRECOM <amel.guesmi at sofrecom.com>
> *Cc :* BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com>; 
> DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
> *Objet :* Re: [OpenSIPS-Users] Staless mode in opensips
>
> Hi,
>
> Your post is a bit confusing when comes to state (and statefull) - are 
> you talking about transaction statefull or dialog statefull ?
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 05.12.2023 13:01, amel.guesmi at sofrecom.com wrote:
>
>     Hi opensips experts,
>
>     We have always worked Opensips in a statefull mode and the first
>     words in the routing module description are “OpenSIPS is basically
>     /only/ a transaction statefull proxy”.
>
>     I’ve also seen that there was a stateless module “The SL module
>     allows OpenSIPS to act as a stateless UA server and generate
>     replies to SIP requests without keeping state” but is it possible
>     to use functionality of Opensips like dialplan and dispatcher
>     without keeping state of the dialog ?
>
>     Thanks for your help
>
>     On belhalf of my colleague Guillaume
>
>     BR, Amel
>
>
>
>     _______________________________________________
>
>     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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231206/ab05e90e/attachment.html>

From rvg at rvgeerligs.nl  Wed Dec  6 18:58:07 2023
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Wed, 06 Dec 2023 18:58:07 +0000
Subject: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS
 version question
In-Reply-To: <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
References: <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
 <CAOPUfWXK24wv-XmRT-yWUucb0yH6qtqMnwTwJEHXJsozXoW0rA@mail.gmail.com>
Message-ID: <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>

Hi all,

I do not know where to post this, but maybe it is all right.

I use:
Opensips 3.4 compiled on Oracle VM ARM Ubuntu 22.04.2 LTS - php 7.4 with OCP 9.3.3. Everything works!
Installed OCP 9.3.4 and many menues on the left side have no reaction:
CallCenter
keepalived
TLS management !
UAC registrant
SMPP Gateway
TCP Management

Regards,

Ronald Geerligs




October 2, 2023 at 8:49 AM, "Răzvan Crainea" <razvan at opensips.org> wrote:


> 
> Hi, Nineto!
> 
> Although it was not already released, OpenSIPS master branch should be 
> compatible with OpenSIPS 3.4. The compatibility process is not yet 
> complete, therefore a full release (9.3.4) is not available yet for 
> OpenSIPS 3.4.
> 
> Best regards,
> 
> Răzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com/ / https://www.siphub.com/
> 
> On 9/29/23 19:15, Nine to one wrote:
> 
> > 
> > Hello OpenSIPS Control Panel developers,
> >  
> >  From website OCP only mentioned support up to OpenSIPS 3.3, I am using 
> >  3.4, so want to know if current OCP already support OpenSIPS 3.4 or not.
> >  
> >  Thanks,
> >  Nineto
> >  
> >  _______________________________________________
> >  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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231206/dc96333a/attachment-0001.html>

From bogdan at opensips.org  Thu Dec  7 08:08:50 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 7 Dec 2023 10:08:50 +0200
Subject: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS
 version question
In-Reply-To: <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>
References: <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
 <CAOPUfWXK24wv-XmRT-yWUucb0yH6qtqMnwTwJEHXJsozXoW0rA@mail.gmail.com>
 <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>
Message-ID: <f4f77f31-1922-4a67-854e-0954e66051ff@opensips.org>

Hi Ronald,

So same server with an OpenSIPS 3.4 works with OCP 9.3.3, but not with 
OCP 9.3.4 - the only difference between the 2 tests is the version of 
OCP, still exactly the same env is used, right ? Any setting in the 
modules.inc.php ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 06.12.2023 20:58, rvg at rvgeerligs.nl wrote:
> Hi all,
>
> I do not know where to post this, but maybe it is all right.
>
> I use:
> Opensips 3.4 compiled on Oracle VM ARM Ubuntu 22.04.2 LTS - php 7.4 
> with OCP 9.3.3. Everything works!
> Installed OCP 9.3.4 and many menues on the left side have no reaction:
> CallCenter
> keepalived
> TLS management !
> UAC registrant
> SMPP Gateway
> TCP Management
>
> Regards,
>
> Ronald Geerligs
>
>
> October 2, 2023 at 8:49 AM, "Răzvan Crainea" <razvan at opensips.org 
> <mailto:razvan at opensips.org?to=%22R%C4%83zvan%20Crainea%22%20%3Crazvan%40opensips.org%3E>> 
> wrote:
>
>     Hi, Nineto!
>
>     Although it was not already released, OpenSIPS master branch
>     should be
>     compatible with OpenSIPS 3.4. The compatibility process is not yet
>     complete, therefore a full release (9.3.4) is not available yet for
>     OpenSIPS 3.4.
>
>     Best regards,
>
>     Răzvan Crainea
>     OpenSIPS Core Developer / SIPhub CTO
>     http://www.opensips-solutions.com/ / https://www.siphub.com/
>
>     On 9/29/23 19:15, Nine to one wrote:
>
>         Hello OpenSIPS Control Panel developers,
>         From website OCP only mentioned support up to OpenSIPS 3.3, I
>         am using
>         3.4, so want to know if current OCP already support OpenSIPS
>         3.4 or not.
>         Thanks,
>         Nineto
>         _______________________________________________
>         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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231207/1ff9a994/attachment.html>

From amel.guesmi at sofrecom.com  Thu Dec  7 13:58:35 2023
From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com)
Date: Thu, 7 Dec 2023 13:58:35 +0000
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <e387e7f3-cebe-437c-a2d1-03acdd4f3917@opensips.org>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
 <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>
 <82a9d9383dae484c916a069949974eae@sofrecom.com>
 <e387e7f3-cebe-437c-a2d1-03acdd4f3917@opensips.org>
Message-ID: <b42bcf89e33c40f394a9d6ccd35b8081@sofrecom.com>

Hello Bogdan,

Thank you for confirming the feasability.
Do you think that if we use opensips in stateless mode, this could impact the performance or way that it behaves ?
If you have an answer i twill be great intil we tests and see.
Thank you

BR, Amel

De : Bogdan-Andrei Iancu <bogdan at opensips.org>
Envoyé : mercredi 6 décembre 2023 15:21
À : OpenSIPS users mailling list <users at lists.opensips.org>; GUESMI Amel SOFRECOM <amel.guesmi at sofrecom.com>
Cc : BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com>; DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
Objet : Re: [OpenSIPS-Users] Staless mode in opensips

Hi,

If you want your OpenSIPS not to stay in the middle of the dialog (after the initial request) you should not do any record_route() and you should not use the dialog module at all.

Best regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com
On 05.12.2023 17:20, amel.guesmi at sofrecom.com<mailto:amel.guesmi at sofrecom.com> wrote:
Hello
Sorry if I wasn’t clear.
We would like to implement a dialog stateless SIP proxy. Once the correct SIP routing is found, we would like to allow the SIP-based elements to perform midcall signaling directly with one another.
Best regards,


De : Users <users-bounces at lists.opensips.org><mailto:users-bounces at lists.opensips.org> De la part de Bogdan-Andrei Iancu
Envoyé : mardi 5 décembre 2023 12:17
À : OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>; GUESMI Amel SOFRECOM <amel.guesmi at sofrecom.com><mailto:amel.guesmi at sofrecom.com>
Cc : BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com><mailto:chaker.barkaoui at sofrecom.com>; DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com><mailto:guillaume.desgeorge at orange.com>
Objet : Re: [OpenSIPS-Users] Staless mode in opensips

Hi,

Your post is a bit confusing when comes to state (and statefull) - are you talking about transaction statefull or dialog statefull ?

Regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com
On 05.12.2023 13:01, amel.guesmi at sofrecom.com<mailto:amel.guesmi at sofrecom.com> wrote:

Hi opensips experts,

We have always worked Opensips in a statefull mode and the first words in the routing module description are “OpenSIPS is basically only a transaction statefull proxy”.

I’ve also seen that there was a stateless module “The SL module allows OpenSIPS to act as a stateless UA server and generate replies to SIP requests without keeping state” but is it possible to use functionality of Opensips like dialplan and dispatcher without keeping state of the dialog ?

Thanks for your help

On belhalf of my colleague Guillaume

BR, Amel





_______________________________________________

Users mailing list

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

http://lists.opensips.org/cgi-bin/mailman/listinfo/users




_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto: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/20231207/4d7b22c1/attachment.html>

From simon at softnet.si  Thu Dec  7 15:17:57 2023
From: simon at softnet.si (Simon Gajski)
Date: Thu, 7 Dec 2023 16:17:57 +0100
Subject: [OpenSIPS-Users] opensips is restarting after call is finished
Message-ID: <5396b869-04a9-47dc-a000-63a949c12a57@softnet.si>

Hi

we are running opensips 3.4.2
on Ubuntu 22.04.3 LTS
and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 git-master-74075f63

Opensips acts as SBC with RTP engine enabled.

Calls are working fine, however after each call is finished, bellow 
action happens.

We had same problem with opensips 3.2 and Ubuntu 20. So we did upgrade 
to latest stable release, and it is the same.

Is this opensips script configuration issue or a bug? And how could I 
fix it?

Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
child process 28495 exited by a signal 11
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
core was generated
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
terminating due to SIGCHLD
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28491]: INFO:core:sig_usr: 
signal 15 received
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28492]: INFO:core:sig_usr: 
signal 15 received
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 4(28492) [timer] terminated, still 
waiting for 16 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 18(28508) [TCP main] terminated, 
still waiting for 15 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 3(28491) [time_keeper] terminated, 
still waiting for 14 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 16(28504) [TCP receiver] 
terminated, still waiting for 13 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 2(28490) [MI FIFO] terminated, 
still waiting for 12 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 15(28503) [TCP receiver] 
terminated, still waiting for 11 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 14(28502) [TCP receiver] 
terminated, still waiting for 10 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 12(28500) [TCP receiver] 
terminated, still waiting for 9 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 1(28489) [HTTPD 127.0.0.1:8888] 
terminated, still waiting for 8 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 8(28496) [SIP receiver 
udp:213.253.120.65:5060] terminated, still waiting for 7 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 10(28498) [TCP receiver] 
terminated, still waiting for 6 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 13(28501) [TCP receiver] 
terminated, still waiting for 5 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 9(28497) [TCP receiver] terminated, 
still waiting for 4 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 11(28499) [TCP receiver] 
terminated, still waiting for 3 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 6(28494) [SIP receiver 
udp:213.253.120.65:5060] terminated, still waiting for 2 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 17(28507) [Timer handler] 
terminated, still waiting for 1 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
INFO:core:shutdown_opensips: process 5(28493) [SIP receiver 
udp:213.253.120.65:5060] terminated, still waiting for 0 more
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:cleanup: cleanup
Dec  7 15:59:47 sbc2 opensips: INFO:core:fix_poll_method: using epoll as 
the IO watch method (auto detected)
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: 
version: opensips 3.4.2 (x86_64/linux)
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: using 
64 MB of shared memory, allocator: F_MALLOC
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: using 
4 MB of private process memory, allocator: F_MALLOC
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
WARNING:core:init_reactor_size: shrinking reactor size from 262144 
(autodetected via rlimit) to 10485 (limited by memory of 10% from 4Mb)
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
WARNING:core:init_reactor_size: use 'open_files_limit' to enforce other 
limit or increase pkg memory
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:init_reactor_size: reactor size 10485 (using up to 0.40Mb of 
memory per process)
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_THRESHOLD(1)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_SHM_THRESHOLD(2)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_PKG_THRESHOLD(3)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_PROC_AUTO_SCALE(4)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_TCP_DISCONNECT(5)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:tm:mod_init: TM - 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:sl:mod_init: 
Initializing StateLess engine
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
NOTICE:signaling:mod_init: initializing module ...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_MYSQL_CONNECTION(6)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:dialog:mod_init: 
Dialog module - initializing
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_DLG_STATE_CHANGED(7)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:rr:mod_init: rr - 
initializing
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:uac:mod_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:acc:mod_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_ACC_EVENT(8)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_ACC_CDR(9)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_ACC_MISSED_EVENT(10)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:textops:mod_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:maxfwd:mod_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:sipmsgops:mod_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:avpops:avpops_init: 
initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:drouting:dr_init: 
dynamic routing - initializing
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:drouting:init_prefix_tree: counted 10 possible chars under a node
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_DROUTING_STATUS(11)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:permissions:mod_init: default allow file 
(/etc/opensips/permissions.allow) not found => empty rule set
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:permissions:mod_init: default deny file 
(/etc/opensips/permissions.deny) not found => empty rule set
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:regex:mod_init: 
initializing module...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:regex:mod_init: 
'file' parameter is not set, group matching disabled
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:topology_hiding:mod_init: initializing...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_RTPENGINE_STATUS(12)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:userblacklist:mod_init: initializing ...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:userblacklist:mod_init: finished initializing
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:dialplan:mod_init: 
initializing module...
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: 
initializing UDP-plain protocol
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: 
initializing TCP-plain protocol
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
INFO:core:evi_publish_event: Registered event <E_CORE_LOG(13)>
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31290]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31291]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: 
INFO:drouting:dr_reload_data_head: loading drouting data!
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31295]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31296]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31297]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31298]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31299]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31300]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31301]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31302]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31303]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31304]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31305]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31306]: 
INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support 
for it enabled
Dec  7 15:59:48 sbc2 opensips: INFO:core:daemonize: pre-daemon process 
exiting with 0

Thanks for all tips.

BR
Simon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231207/cf031e8b/attachment-0001.html>

From bogdan at opensips.org  Thu Dec  7 15:43:11 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 7 Dec 2023 17:43:11 +0200
Subject: [OpenSIPS-Users] Staless mode in opensips
In-Reply-To: <b42bcf89e33c40f394a9d6ccd35b8081@sofrecom.com>
References: <89e2c7a66d51430c892754b558265caa@sofrecom.com>
 <1bde6871-36eb-4fac-ab9b-78e7e030d425@opensips.org>
 <82a9d9383dae484c916a069949974eae@sofrecom.com>
 <e387e7f3-cebe-437c-a2d1-03acdd4f3917@opensips.org>
 <b42bcf89e33c40f394a9d6ccd35b8081@sofrecom.com>
Message-ID: <76b89bad-3bee-4e3d-b7e7-142c625da88f@opensips.org>

Hi,

Check this:
https://www.opensips.org/About/PerformanceTests-3-4#toc6

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 07.12.2023 15:58, amel.guesmi at sofrecom.com wrote:
>
> Hello Bogdan,
>
> Thank you for confirming the feasability.
>
> Do you think that if we use opensips in stateless mode, this could 
> impact the performance or way that it behaves ?
>
> If you have an answer i twill be great intil we tests and see.
>
> Thank you
>
> BR, Amel
>
> *De :*Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Envoyé :* mercredi 6 décembre 2023 15:21
> *À :* OpenSIPS users mailling list <users at lists.opensips.org>; GUESMI 
> Amel SOFRECOM <amel.guesmi at sofrecom.com>
> *Cc :* BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com>; 
> DESGEORGE Guillaume INNOV/IT-S <guillaume.desgeorge at orange.com>
> *Objet :* Re: [OpenSIPS-Users] Staless mode in opensips
>
> Hi,
>
> If you want your OpenSIPS not to stay in the middle of the dialog 
> (after the initial request) you should not do any record_route() and 
> you should not use the dialog module at all.
>
> Best regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 05.12.2023 17:20, amel.guesmi at sofrecom.com wrote:
>
>     Hello
>
>     Sorry if I wasn’t clear.
>
>     We would like to implement a dialog stateless SIP proxy. Once the
>     correct SIP routing is found, we would like to allow the SIP-based
>     elements to perform midcall signaling directly with one another.
>
>     Best regards,
>
>     *De :*Users <users-bounces at lists.opensips.org>
>     <mailto:users-bounces at lists.opensips.org>*De la part de*
>     Bogdan-Andrei Iancu
>     *Envoyé :* mardi 5 décembre 2023 12:17
>     *À :* OpenSIPS users mailling list <users at lists.opensips.org>
>     <mailto:users at lists.opensips.org>; GUESMI Amel SOFRECOM
>     <amel.guesmi at sofrecom.com> <mailto:amel.guesmi at sofrecom.com>
>     *Cc :* BARKAOUI Chaker SOFRECOM <chaker.barkaoui at sofrecom.com>
>     <mailto:chaker.barkaoui at sofrecom.com>; DESGEORGE Guillaume
>     INNOV/IT-S <guillaume.desgeorge at orange.com>
>     <mailto:guillaume.desgeorge at orange.com>
>     *Objet :* Re: [OpenSIPS-Users] Staless mode in opensips
>
>     Hi,
>
>     Your post is a bit confusing when comes to state (and statefull) -
>     are you talking about transaction statefull or dialog statefull ?
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>       
>
>     OpenSIPS Founder and Developer
>
>        https://www.opensips-solutions.com
>
>        https://www.siphub.com
>
>     On 05.12.2023 13:01, amel.guesmi at sofrecom.com wrote:
>
>         Hi opensips experts,
>
>         We have always worked Opensips in a statefull mode and the
>         first words in the routing module description are “OpenSIPS is
>         basically /only/ a transaction statefull proxy”.
>
>         I’ve also seen that there was a stateless module “The SL
>         module allows OpenSIPS to act as a stateless UA server and
>         generate replies to SIP requests without keeping state” but is
>         it possible to use functionality of Opensips like dialplan and
>         dispatcher without keeping state of the dialog ?
>
>         Thanks for your help
>
>         On belhalf of my colleague Guillaume
>
>         BR, Amel
>
>
>
>
>         _______________________________________________
>
>         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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231207/f8737ebd/attachment.html>

From bogdan at opensips.org  Thu Dec  7 15:52:37 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 7 Dec 2023 17:52:37 +0200
Subject: [OpenSIPS-Users] opensips is restarting after call is finished
In-Reply-To: <5396b869-04a9-47dc-a000-63a949c12a57@softnet.si>
References: <5396b869-04a9-47dc-a000-63a949c12a57@softnet.si>
Message-ID: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>

Hi Simon,

Well, the log is very self explanatory:
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
child process 28495 exited by a signal 11
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
core was generated
Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
terminating due to SIGCHLD

Or shortly, you opensips just crashed :). So see 
https://opensips.org/Documentation/TroubleShooting-Crash for how to 
report further.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 07.12.2023 17:17, Simon Gajski via Users wrote:
>
> Hi
>
> we are running opensips 3.4.2
> on Ubuntu 22.04.3 LTS
> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 git-master-74075f63
>
> Opensips acts as SBC with RTP engine enabled.
>
> Calls are working fine, however after each call is finished, bellow 
> action happens.
>
> We had same problem with opensips 3.2 and Ubuntu 20. So we did upgrade 
> to latest stable release, and it is the same.
>
> Is this opensips script configuration issue or a bug? And how could I 
> fix it?
>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
> child process 28495 exited by a signal 11
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
> core was generated
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
> terminating due to SIGCHLD
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28491]: INFO:core:sig_usr: 
> signal 15 received
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28492]: INFO:core:sig_usr: 
> signal 15 received
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 4(28492) [timer] terminated, 
> still waiting for 16 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 18(28508) [TCP main] terminated, 
> still waiting for 15 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 3(28491) [time_keeper] 
> terminated, still waiting for 14 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 16(28504) [TCP receiver] 
> terminated, still waiting for 13 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 2(28490) [MI FIFO] terminated, 
> still waiting for 12 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 15(28503) [TCP receiver] 
> terminated, still waiting for 11 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 14(28502) [TCP receiver] 
> terminated, still waiting for 10 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 12(28500) [TCP receiver] 
> terminated, still waiting for 9 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 1(28489) [HTTPD 127.0.0.1:8888] 
> terminated, still waiting for 8 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 8(28496) [SIP receiver 
> udp:213.253.120.65:5060] terminated, still waiting for 7 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 10(28498) [TCP receiver] 
> terminated, still waiting for 6 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 13(28501) [TCP receiver] 
> terminated, still waiting for 5 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 9(28497) [TCP receiver] 
> terminated, still waiting for 4 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 11(28499) [TCP receiver] 
> terminated, still waiting for 3 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 6(28494) [SIP receiver 
> udp:213.253.120.65:5060] terminated, still waiting for 2 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 17(28507) [Timer handler] 
> terminated, still waiting for 1 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
> INFO:core:shutdown_opensips: process 5(28493) [SIP receiver 
> udp:213.253.120.65:5060] terminated, still waiting for 0 more
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:cleanup: cleanup
> Dec  7 15:59:47 sbc2 opensips: INFO:core:fix_poll_method: using epoll 
> as the IO watch method (auto detected)
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: 
> version: opensips 3.4.2 (x86_64/linux)
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: 
> using 64 MB of shared memory, allocator: F_MALLOC
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: 
> using 4 MB of private process memory, allocator: F_MALLOC
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> WARNING:core:init_reactor_size: shrinking reactor size from 262144 
> (autodetected via rlimit) to 10485 (limited by memory of 10% from 4Mb)
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> WARNING:core:init_reactor_size: use 'open_files_limit' to enforce 
> other limit or increase pkg memory
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:init_reactor_size: reactor size 10485 (using up to 0.40Mb of 
> memory per process)
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_THRESHOLD(1)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_SHM_THRESHOLD(2)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_PKG_THRESHOLD(3)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_PROC_AUTO_SCALE(4)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_TCP_DISCONNECT(5)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:tm:mod_init: TM - 
> initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:sl:mod_init: 
> Initializing StateLess engine
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> NOTICE:signaling:mod_init: initializing module ...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_MYSQL_CONNECTION(6)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:dialog:mod_init: 
> Dialog module - initializing
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_DLG_STATE_CHANGED(7)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:rr:mod_init: rr - 
> initializing
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:uac:mod_init: 
> initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:acc:mod_init: 
> initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_ACC_EVENT(8)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_ACC_CDR(9)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_ACC_MISSED_EVENT(10)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:textops:mod_init: 
> initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:maxfwd:mod_init: 
> initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:sipmsgops:mod_init: initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:avpops:avpops_init: initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:drouting:dr_init: 
> dynamic routing - initializing
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:drouting:init_prefix_tree: counted 10 possible chars under a node
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_DROUTING_STATUS(11)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:permissions:mod_init: default allow file 
> (/etc/opensips/permissions.allow) not found => empty rule set
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:permissions:mod_init: default deny file 
> (/etc/opensips/permissions.deny) not found => empty rule set
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:regex:mod_init: 
> initializing module...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:regex:mod_init: 
> 'file' parameter is not set, group matching disabled
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:topology_hiding:mod_init: initializing...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_RTPENGINE_STATUS(12)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:userblacklist:mod_init: initializing ...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:userblacklist:mod_init: finished initializing
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:dialplan:mod_init: initializing module...
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: 
> initializing UDP-plain protocol
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: 
> initializing TCP-plain protocol
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: 
> INFO:core:evi_publish_event: Registered event <E_CORE_LOG(13)>
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31290]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31291]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: 
> INFO:drouting:dr_reload_data_head: loading drouting data!
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31295]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31296]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31297]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31298]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31299]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31300]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31301]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31302]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31303]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31304]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31305]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31306]: 
> INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, 
> support for it enabled
> Dec  7 15:59:48 sbc2 opensips: INFO:core:daemonize: pre-daemon process 
> exiting with 0
>
> Thanks for all tips.
>
> BR
> Simon
>
>
> _______________________________________________
> 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/20231207/1277ab49/attachment-0001.html>

From bogdan at opensips.org  Thu Dec  7 17:18:32 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 7 Dec 2023 19:18:32 +0200
Subject: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS
 version question
In-Reply-To: <3399a87ce490752dbcd1d34fb2741a6287c0c176@rvgeerligs.nl>
References: <f4f77f31-1922-4a67-854e-0954e66051ff@opensips.org>
 <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
 <CAOPUfWXK24wv-XmRT-yWUucb0yH6qtqMnwTwJEHXJsozXoW0rA@mail.gmail.com>
 <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>
 <3399a87ce490752dbcd1d34fb2741a6287c0c176@rvgeerligs.nl>
Message-ID: <6699ab05-9c42-4d5d-9f9f-c415b812cc8e@opensips.org>

Hi Ronald,

Tool as Addresses or Diaplan are still working in 9.3.4 ? and just to 
clarify, what exactly means "no reaction"? when you click on the "Call 
Center" tool, you still have the old tool in the main right window? or 
is it turning blank ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 07.12.2023 15:44, rvg at rvgeerligs.nl wrote:
> Hi Bogdan,
>
> Short answer: yes.
> Did not change anything in modules.inc.php.
>
> I have 2 directories opensips-cp and opensipscp, containing 9.3.3 and 
> 9.3.4 respectively. also configured in apache2.
> Copied the db.inc.php from the 9.3.3 to the 9.3.4 directory.
>
> Regards,
>
> Ronald Geerligs
>
> December 7, 2023 at 9:08 AM, "Bogdan-Andrei Iancu" 
> <bogdan at opensips.org 
> <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>> 
> wrote:
>
>     Hi Ronald,
>
>     So same server with an OpenSIPS 3.4 works with OCP 9.3.3, but not
>     with OCP 9.3.4 - the only difference between the 2 tests is the
>     version of OCP, still exactly the same env is used, right ? Any
>     setting in the modules.inc.php ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 06.12.2023 20:58, rvg at rvgeerligs.nl wrote:
>
>         Hi all,
>         I do not know where to post this, but maybe it is all right.
>         I use:
>         Opensips 3.4 compiled on Oracle VM ARM Ubuntu 22.04.2 LTS -
>         php 7.4 with OCP 9.3.3. Everything works!
>         Installed OCP 9.3.4 and many menues on the left side have no
>         reaction:
>         CallCenter
>         keepalived
>         TLS management !
>         UAC registrant
>         SMPP Gateway
>         TCP Management
>         Regards,
>         Ronald Geerligs
>
>         October 2, 2023 at 8:49 AM, "Răzvan Crainea"
>         <razvan at opensips.org
>         <mailto:razvan at opensips.org?to=%22R%C4%83zvan%20Crainea%22%20%3Crazvan%40opensips.org%3E>>
>         wrote:
>
>             Hi, Nineto!
>             Although it was not already released, OpenSIPS master
>             branch should be
>             compatible with OpenSIPS 3.4. The compatibility process is
>             not yet
>             complete, therefore a full release (9.3.4) is not
>             available yet for
>             OpenSIPS 3.4.
>             Best regards,
>             Răzvan Crainea
>             OpenSIPS Core Developer / SIPhub CTO
>             http://www.opensips-solutions.com/ / https://www.siphub.com/
>             On 9/29/23 19:15, Nine to one wrote:
>
>                 Hello OpenSIPS Control Panel developers,
>                 From website OCP only mentioned support up to OpenSIPS
>                 3.3, I am using
>                 3.4, so want to know if current OCP already support
>                 OpenSIPS 3.4 or not.
>                 Thanks,
>                 Nineto
>                 _______________________________________________
>                 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231207/2dd714f8/attachment.html>

From bogdan at opensips.org  Fri Dec  8 07:39:03 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 8 Dec 2023 09:39:03 +0200
Subject: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS
 version question
In-Reply-To: <7c3c6b1e0591853f5d73591f7be6eda86fc704ea@rvgeerligs.nl>
References: <6699ab05-9c42-4d5d-9f9f-c415b812cc8e@opensips.org>
 <f4f77f31-1922-4a67-854e-0954e66051ff@opensips.org>
 <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
 <CAOPUfWXK24wv-XmRT-yWUucb0yH6qtqMnwTwJEHXJsozXoW0rA@mail.gmail.com>
 <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>
 <3399a87ce490752dbcd1d34fb2741a6287c0c176@rvgeerligs.nl>
 <7c3c6b1e0591853f5d73591f7be6eda86fc704ea@rvgeerligs.nl>
Message-ID: <5d70d638-f0dd-418d-8150-5464cdd235aa@opensips.org>

Hi Ronald,

yes, please check for ERR or WARN in php.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 07.12.2023 22:26, rvg at rvgeerligs.nl wrote:
> Hi Bogdan-Andrei,
>
> The others like adresses and dialplan or dynamic routing (very 
> important one) work and the dialogues give the right answers.
> No reaction means blank page.
>
> Want me to enable PHP error messages?
>
> Regards,
>
> Ronald
>
> December 7, 2023 at 6:18 PM, "Bogdan-Andrei Iancu" 
> <bogdan at opensips.org 
> <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>> 
> wrote:
>
>     Hi Ronald,
>
>     Tool as Addresses or Diaplan are still working in 9.3.4 ? and just
>     to clarify, what exactly means "no reaction"? when you click on
>     the "Call Center" tool, you still have the old tool in the main
>     right window? or is it turning blank ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 07.12.2023 15:44, rvg at rvgeerligs.nl wrote:
>
>         Hi Bogdan,
>         Short answer: yes.
>         Did not change anything in modules.inc.php.
>         I have 2 directories opensips-cp and opensipscp, containing
>         9.3.3 and 9.3.4 respectively. also configured in apache2.
>         Copied the db.inc.php from the 9.3.3 to the 9.3.4 directory.
>         Regards,
>         Ronald Geerligs
>
>         December 7, 2023 at 9:08 AM, "Bogdan-Andrei Iancu"
>         <bogdan at opensips.org
>         <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>>
>         wrote:
>
>             Hi Ronald,
>
>             So same server with an OpenSIPS 3.4 works with OCP 9.3.3,
>             but not with OCP 9.3.4 - the only difference between the 2
>             tests is the version of OCP, still exactly the same env is
>             used, right ? Any setting in the modules.inc.php ?
>
>             Regards,
>
>             Bogdan-Andrei Iancu
>
>             OpenSIPS Founder and Developer
>                https://www.opensips-solutions.com
>                https://www.siphub.com
>
>             On 06.12.2023 20:58, rvg at rvgeerligs.nl wrote:
>
>                 Hi all,
>                 I do not know where to post this, but maybe it is all
>                 right.
>                 I use:
>                 Opensips 3.4 compiled on Oracle VM ARM Ubuntu 22.04.2
>                 LTS - php 7.4 with OCP 9.3.3. Everything works!
>                 Installed OCP 9.3.4 and many menues on the left side
>                 have no reaction:
>                 CallCenter
>                 keepalived
>                 TLS management !
>                 UAC registrant
>                 SMPP Gateway
>                 TCP Management
>                 Regards,
>                 Ronald Geerligs
>
>                 October 2, 2023 at 8:49 AM, "Răzvan Crainea"
>                 <razvan at opensips.org
>                 <mailto:razvan at opensips.org?to=%22R%C4%83zvan%20Crainea%22%20%3Crazvan%40opensips.org%3E>>
>                 wrote:
>
>                     Hi, Nineto!
>                     Although it was not already released, OpenSIPS
>                     master branch should be
>                     compatible with OpenSIPS 3.4. The compatibility
>                     process is not yet
>                     complete, therefore a full release (9.3.4) is not
>                     available yet for
>                     OpenSIPS 3.4.
>                     Best regards,
>                     Răzvan Crainea
>                     OpenSIPS Core Developer / SIPhub CTO
>                     http://www.opensips-solutions.com/ /
>                     https://www.siphub.com/
>                     On 9/29/23 19:15, Nine to one wrote:
>
>                         Hello OpenSIPS Control Panel developers,
>                         From website OCP only mentioned support up to
>                         OpenSIPS 3.3, I am using
>                         3.4, so want to know if current OCP already
>                         support OpenSIPS 3.4 or not.
>                         Thanks,
>                         Nineto
>                         _______________________________________________
>                         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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231208/d0f28d09/attachment-0001.html>

From neven at softnet.si  Fri Dec  8 11:35:02 2023
From: neven at softnet.si (Neven Grzancic)
Date: Fri, 8 Dec 2023 12:35:02 +0100
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
Message-ID: <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>

Dear Bogdan,

we tried following https://opensips.org/Documentation/TroubleShooting-Crash and trying different things, and even though the syslog shows that the core file was dumped:

Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in opensips[55816fbd0000+1f000]
Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 [Warning] Aborted connection 400 to db: 'opensips' user: 'opensips' host: 'localhost' (Got an error reading communication packets)
Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: child process 4363 exited by a signal 11
Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: core was generated
Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: terminating due to SIGCHLD
Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: signal 15 received
Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: signal 15 received

the core does not get generated, or at least not in the directory provided via options at runtime (-w /tmp). The issue is always repeatable (the daemon crashes after every finished call), if there are more active calls at the moment of the crash, whose calls remain active and proceed normally until termination (which again causes a crash). We also tried enabling debug mode, but in that case the process does not start successfully and runs into a timeout. In any case, any additional help or suggestion on how to successfully generate the core dump would be much appreciated, as we seem to have ran into a wall here...

On 08.12.23 12:26, Simon Gajski wrote:
> 
> 
> 
> -------- Posredovano sporočilo --------
> Zadeva: 	Re: [OpenSIPS-Users] opensips is restarting after call is finished
> Datum: 	Thu, 7 Dec 2023 17:52:37 +0200
> Od: 	Bogdan-Andrei Iancu <bogdan at opensips.org>
> Za: 	Simon Gajski <simon at softnet.si>, OpenSIPS users mailling list <users at lists.opensips.org>
> 
> 
> 
> Hi Simon,
> 
> Well, the log is very self explanatory:
> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: child process 28495 exited by a signal 11
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: core was generated
> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: terminating due to SIGCHLD
> 
> Or shortly, you opensips just crashed :). So see https://opensips.org/Documentation/TroubleShooting-Crash for how to report further.
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> 
> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>
>> Hi
>>
>> we are running opensips 3.4.2
>> on Ubuntu 22.04.3 LTS
>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 git-master-74075f63
>>
>> Opensips acts as SBC with RTP engine enabled.
>>
>> Calls are working fine, however after each call is finished, bellow action happens.
>>
>> We had same problem with opensips 3.2 and Ubuntu 20. So we did upgrade to latest stable release, and it is the same.
>>
>> Is this opensips script configuration issue or a bug? And how could I fix it?
>>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: child process 28495 exited by a signal 11
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: core was generated
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: terminating due to SIGCHLD
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28491]: INFO:core:sig_usr: signal 15 received
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28492]: INFO:core:sig_usr: signal 15 received
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 4(28492) [timer] terminated, still waiting for 16 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 18(28508) [TCP main] terminated, still waiting for 15 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 3(28491) [time_keeper] terminated, still waiting for 14 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 16(28504) [TCP receiver] terminated, still waiting for 13 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 2(28490) [MI FIFO] terminated, still waiting for 12 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 15(28503) [TCP receiver] terminated, still waiting for 11 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 14(28502) [TCP receiver] terminated, still waiting for 10 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 12(28500) [TCP receiver] terminated, still waiting for 9 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 1(28489) [HTTPD 127.0.0.1:8888] terminated, still waiting for 8 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 8(28496) [SIP receiver udp:213.253.120.65:5060] terminated, still waiting for 7 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 10(28498) [TCP receiver] terminated, still waiting for 6 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 13(28501) [TCP receiver] terminated, still waiting for 5 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 9(28497) [TCP receiver] terminated, still waiting for 4 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 11(28499) [TCP receiver] terminated, still waiting for 3 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 6(28494) [SIP receiver udp:213.253.120.65:5060] terminated, still waiting for 2 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 17(28507) [Timer handler] terminated, still waiting for 1 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:shutdown_opensips: process 5(28493) [SIP receiver udp:213.253.120.65:5060] terminated, still waiting for 0 more
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:cleanup: cleanup
>> Dec  7 15:59:47 sbc2 opensips: INFO:core:fix_poll_method: using epoll as the IO watch method (auto detected)
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: version: opensips 3.4.2 (x86_64/linux)
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: using 64 MB of shared memory, allocator: F_MALLOC
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:core:main: using 4 MB of private process memory, allocator: F_MALLOC
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: WARNING:core:init_reactor_size: shrinking reactor size from 262144 (autodetected via rlimit) to 10485 (limited by memory of 10% from 4Mb)
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: WARNING:core:init_reactor_size: use 'open_files_limit' to enforce other limit or increase pkg memory
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:init_reactor_size: reactor size 10485 (using up to 0.40Mb of memory per process)
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_THRESHOLD(1)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_SHM_THRESHOLD(2)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_PKG_THRESHOLD(3)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_PROC_AUTO_SCALE(4)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_TCP_DISCONNECT(5)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:tm:mod_init: TM - initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:sl:mod_init: Initializing StateLess engine
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:signaling:mod_init: initializing module ...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_MYSQL_CONNECTION(6)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:dialog:mod_init: Dialog module - initializing
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_DLG_STATE_CHANGED(7)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:rr:mod_init: rr - initializing
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:uac:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:acc:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_ACC_EVENT(8)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_ACC_CDR(9)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_ACC_MISSED_EVENT(10)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:textops:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:maxfwd:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:sipmsgops:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:avpops:avpops_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:drouting:dr_init: dynamic routing - initializing
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:drouting:init_prefix_tree: counted 10 possible chars under a node
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_DROUTING_STATUS(11)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:permissions:mod_init: default allow file (/etc/opensips/permissions.allow) not found => empty rule set
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:permissions:mod_init: default deny file (/etc/opensips/permissions.deny) not found => empty rule set
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:regex:mod_init: initializing module...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: NOTICE:regex:mod_init: 'file' parameter is not set, group matching disabled
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:topology_hiding:mod_init: initializing...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_RTPENGINE_STATUS(12)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:userblacklist:mod_init: initializing ...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:userblacklist:mod_init: finished initializing
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:dialplan:mod_init: initializing module...
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: initializing UDP-plain protocol
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:mod_init: initializing TCP-plain protocol
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31289]: INFO:core:evi_publish_event: Registered event <E_CORE_LOG(13)>
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31290]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[31291]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31294]: INFO:drouting:dr_reload_data_head: loading drouting data!
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31295]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31296]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31297]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31298]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31299]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31300]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31301]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31302]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31303]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31304]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31305]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 /usr/sbin/opensips[31306]: INFO:rtpengine:rtpe_test: rtp proxy <udp:127.0.0.1:2223> found, support for it enabled
>> Dec  7 15:59:48 sbc2 opensips: INFO:core:daemonize: pre-daemon process exiting with 0
>>
>> Thanks for all tips.
>>
>> BR
>> Simon
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 

-- 
Best regards / Lep pozdrav
Neven Grzancic, dipl.inž.el.(UN)
techsupport - systems administration & networking
-----------------------------------------------------------------------
Softnet d.o.o.       tel:  +386 1 8100 100  |   the quieter you
Borovec 2         direct:  +386 1 8100 107  | become, the more you
1236 Trzin           fax:  +386 1 8100 101  |   are able to hear
-----------------------------------------------------------------------


From bogdan at opensips.org  Fri Dec  8 13:17:14 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 8 Dec 2023 15:17:14 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
Message-ID: <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>

Hi Simon,

Maybe you have some apport service running on the machine, moving the 
core file.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 08.12.2023 13:35, Neven Grzancic wrote:
> Dear Bogdan,
>
> we tried following 
> https://opensips.org/Documentation/TroubleShooting-Crash and trying 
> different things, and even though the syslog shows that the core file 
> was dumped:
>
> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: CRITICAL:core:sig_usr: 
> segfault in process pid: 4363, id: 7
> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault 
> at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in 
> opensips[55816fbd0000+1f000]
> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 [Warning] 
> Aborted connection 400 to db: 'opensips' user: 'opensips' host: 
> 'localhost' (Got an error reading communication packets)
> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
> child process 4363 exited by a signal 11
> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
> core was generated
> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
> terminating due to SIGCHLD
> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: 
> signal 15 received
> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: 
> signal 15 received
>
> the core does not get generated, or at least not in the directory 
> provided via options at runtime (-w /tmp). The issue is always 
> repeatable (the daemon crashes after every finished call), if there 
> are more active calls at the moment of the crash, whose calls remain 
> active and proceed normally until termination (which again causes a 
> crash). We also tried enabling debug mode, but in that case the 
> process does not start successfully and runs into a timeout. In any 
> case, any additional help or suggestion on how to successfully 
> generate the core dump would be much appreciated, as we seem to have 
> ran into a wall here...
>
> On 08.12.23 12:26, Simon Gajski wrote:
>>
>>
>>
>> -------- Posredovano sporočilo --------
>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call is 
>> finished
>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling list 
>> <users at lists.opensips.org>
>>
>>
>>
>> Hi Simon,
>>
>> Well, the log is very self explanatory:
>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: 
>> child process 28495 exited by a signal 11
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>> INFO:core:handle_sigs: core was generated
>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>
>> Or shortly, you opensips just crashed :). So see 
>> https://opensips.org/Documentation/TroubleShooting-Crash for how to 
>> report further.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>
>>> Hi
>>>
>>> we are running opensips 3.4.2
>>> on Ubuntu 22.04.3 LTS
>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>> git-master-74075f63
>>>
>>> Opensips acts as SBC with RTP engine enabled.
>>>
>>> Calls are working fine, however after each call is finished, bellow 
>>> action happens.
>>>
>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>> upgrade to latest stable release, and it is the same.
>>>
>>> Is this opensips script configuration issue or a bug? And how could 
>>> I fix it?
>>>
>>> [....]
>>>
>>> Thanks for all tips.
>>>
>>> BR
>>> Simon
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>



From simon at softnet.si  Fri Dec  8 14:13:22 2023
From: simon at softnet.si (Simon Gajski)
Date: Fri, 8 Dec 2023 15:13:22 +0100
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
Message-ID: <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>

Hi Bogdan

you were right
we have the core file now

Please let me know where to send it (gzipped is approx 2MB)


BR
Simon

Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
> Hi Simon,
>
> Maybe you have some apport service running on the machine, moving the 
> core file.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 08.12.2023 13:35, Neven Grzancic wrote:
>> Dear Bogdan,
>>
>> we tried following 
>> https://opensips.org/Documentation/TroubleShooting-Crash and trying 
>> different things, and even though the syslog shows that the core file 
>> was dumped:
>>
>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: CRITICAL:core:sig_usr: 
>> segfault in process pid: 4363, id: 7
>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault 
>> at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in 
>> opensips[55816fbd0000+1f000]
>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 [Warning] 
>> Aborted connection 400 to db: 'opensips' user: 'opensips' host: 
>> 'localhost' (Got an error reading communication packets)
>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
>> child process 4363 exited by a signal 11
>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
>> core was generated
>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: 
>> terminating due to SIGCHLD
>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: 
>> signal 15 received
>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: 
>> signal 15 received
>>
>> the core does not get generated, or at least not in the directory 
>> provided via options at runtime (-w /tmp). The issue is always 
>> repeatable (the daemon crashes after every finished call), if there 
>> are more active calls at the moment of the crash, whose calls remain 
>> active and proceed normally until termination (which again causes a 
>> crash). We also tried enabling debug mode, but in that case the 
>> process does not start successfully and runs into a timeout. In any 
>> case, any additional help or suggestion on how to successfully 
>> generate the core dump would be much appreciated, as we seem to have 
>> ran into a wall here...
>>
>> On 08.12.23 12:26, Simon Gajski wrote:
>>>
>>>
>>>
>>> -------- Posredovano sporočilo --------
>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call 
>>> is finished
>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling 
>>> list <users at lists.opensips.org>
>>>
>>>
>>>
>>> Hi Simon,
>>>
>>> Well, the log is very self explanatory:
>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>> INFO:core:handle_sigs: core was generated
>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>
>>> Or shortly, you opensips just crashed :). So see 
>>> https://opensips.org/Documentation/TroubleShooting-Crash for how to 
>>> report further.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>>    https://www.siphub.com
>>>
>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>
>>>> Hi
>>>>
>>>> we are running opensips 3.4.2
>>>> on Ubuntu 22.04.3 LTS
>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>> git-master-74075f63
>>>>
>>>> Opensips acts as SBC with RTP engine enabled.
>>>>
>>>> Calls are working fine, however after each call is finished, bellow 
>>>> action happens.
>>>>
>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>>> upgrade to latest stable release, and it is the same.
>>>>
>>>> Is this opensips script configuration issue or a bug? And how could 
>>>> I fix it?
>>>>
>>>> [....]
>>>>
>>>> Thanks for all tips.
>>>>
>>>> BR
>>>> Simon
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>


From bogdan at opensips.org  Fri Dec  8 14:16:42 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 8 Dec 2023 16:16:42 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
Message-ID: <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>

Simon, I do not need the corefile, usually it is huge - as per web 
instructions (see the prev link), extract the backtrace (using gdb) and 
share it with me.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 08.12.2023 16:13, Simon Gajski wrote:
> Hi Bogdan
>
> you were right
> we have the core file now
>
> Please let me know where to send it (gzipped is approx 2MB)
>
>
> BR
> Simon
>
> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>> Hi Simon,
>>
>> Maybe you have some apport service running on the machine, moving the 
>> core file.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>> Dear Bogdan,
>>>
>>> we tried following 
>>> https://opensips.org/Documentation/TroubleShooting-Crash and trying 
>>> different things, and even though the syslog shows that the core 
>>> file was dumped:
>>>
>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault 
>>> at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in 
>>> opensips[55816fbd0000+1f000]
>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>> [Warning] Aborted connection 400 to db: 'opensips' user: 'opensips' 
>>> host: 'localhost' (Got an error reading communication packets)
>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>> INFO:core:handle_sigs: core was generated
>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: 
>>> signal 15 received
>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: 
>>> signal 15 received
>>>
>>> the core does not get generated, or at least not in the directory 
>>> provided via options at runtime (-w /tmp). The issue is always 
>>> repeatable (the daemon crashes after every finished call), if there 
>>> are more active calls at the moment of the crash, whose calls remain 
>>> active and proceed normally until termination (which again causes a 
>>> crash). We also tried enabling debug mode, but in that case the 
>>> process does not start successfully and runs into a timeout. In any 
>>> case, any additional help or suggestion on how to successfully 
>>> generate the core dump would be much appreciated, as we seem to have 
>>> ran into a wall here...
>>>
>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>
>>>>
>>>>
>>>> -------- Posredovano sporočilo --------
>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call 
>>>> is finished
>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling 
>>>> list <users at lists.opensips.org>
>>>>
>>>>
>>>>
>>>> Hi Simon,
>>>>
>>>> Well, the log is very self explanatory:
>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>> INFO:core:handle_sigs: core was generated
>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>
>>>> Or shortly, you opensips just crashed :). So see 
>>>> https://opensips.org/Documentation/TroubleShooting-Crash for how to 
>>>> report further.
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>    https://www.opensips-solutions.com
>>>>    https://www.siphub.com
>>>>
>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> we are running opensips 3.4.2
>>>>> on Ubuntu 22.04.3 LTS
>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>> git-master-74075f63
>>>>>
>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>
>>>>> Calls are working fine, however after each call is finished, 
>>>>> bellow action happens.
>>>>>
>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>>>> upgrade to latest stable release, and it is the same.
>>>>>
>>>>> Is this opensips script configuration issue or a bug? And how 
>>>>> could I fix it?
>>>>>
>>>>> [....]
>>>>>
>>>>> Thanks for all tips.
>>>>>
>>>>> BR
>>>>> Simon
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>>
>>



From venefax at gmail.com  Fri Dec  8 14:25:57 2023
From: venefax at gmail.com (Saint Michael)
Date: Fri, 8 Dec 2023 09:25:57 -0500
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
	finished
In-Reply-To: <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
Message-ID: <CAC9cSOAegxWJ0xwMtdvppO7YZd8k0TK=JT6167Pbvzdq0UttNg@mail.gmail.com>

I am.very interested in this case.


On Fri, Dec 8, 2023, 9:20 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Simon, I do not need the corefile, usually it is huge - as per web
> instructions (see the prev link), extract the backtrace (using gdb) and
> share it with me.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> On 08.12.2023 16:13, Simon Gajski wrote:
> > Hi Bogdan
> >
> > you were right
> > we have the core file now
> >
> > Please let me know where to send it (gzipped is approx 2MB)
> >
> >
> > BR
> > Simon
> >
> > Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
> >> Hi Simon,
> >>
> >> Maybe you have some apport service running on the machine, moving the
> >> core file.
> >>
> >> Regards,
> >>
> >> Bogdan-Andrei Iancu
> >>
> >> OpenSIPS Founder and Developer
> >>   https://www.opensips-solutions.com
> >>   https://www.siphub.com
> >>
> >> On 08.12.2023 13:35, Neven Grzancic wrote:
> >>> Dear Bogdan,
> >>>
> >>> we tried following
> >>> https://opensips.org/Documentation/TroubleShooting-Crash and trying
> >>> different things, and even though the syslog shows that the core
> >>> file was dumped:
> >>>
> >>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]:
> >>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
> >>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault
> >>> at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in
> >>> opensips[55816fbd0000+1f000]
> >>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400
> >>> [Warning] Aborted connection 400 to db: 'opensips' user: 'opensips'
> >>> host: 'localhost' (Got an error reading communication packets)
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: core was generated
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]:
> >>> INFO:core:handle_sigs: terminating due to SIGCHLD
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr:
> >>> signal 15 received
> >>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr:
> >>> signal 15 received
> >>>
> >>> the core does not get generated, or at least not in the directory
> >>> provided via options at runtime (-w /tmp). The issue is always
> >>> repeatable (the daemon crashes after every finished call), if there
> >>> are more active calls at the moment of the crash, whose calls remain
> >>> active and proceed normally until termination (which again causes a
> >>> crash). We also tried enabling debug mode, but in that case the
> >>> process does not start successfully and runs into a timeout. In any
> >>> case, any additional help or suggestion on how to successfully
> >>> generate the core dump would be much appreciated, as we seem to have
> >>> ran into a wall here...
> >>>
> >>> On 08.12.23 12:26, Simon Gajski wrote:
> >>>>
> >>>>
> >>>>
> >>>> -------- Posredovano sporočilo --------
> >>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call
> >>>> is finished
> >>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
> >>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
> >>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling
> >>>> list <users at lists.opensips.org>
> >>>>
> >>>>
> >>>>
> >>>> Hi Simon,
> >>>>
> >>>> Well, the log is very self explanatory:
> >>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
> >>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: core was generated
> >>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]:
> >>>> INFO:core:handle_sigs: terminating due to SIGCHLD
> >>>>
> >>>> Or shortly, you opensips just crashed :). So see
> >>>> https://opensips.org/Documentation/TroubleShooting-Crash for how to
> >>>> report further.
> >>>>
> >>>> Regards,
> >>>>
> >>>> Bogdan-Andrei Iancu
> >>>>
> >>>> OpenSIPS Founder and Developer
> >>>>    https://www.opensips-solutions.com
> >>>>    https://www.siphub.com
> >>>>
> >>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
> >>>>>
> >>>>> Hi
> >>>>>
> >>>>> we are running opensips 3.4.2
> >>>>> on Ubuntu 22.04.3 LTS
> >>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0
> >>>>> git-master-74075f63
> >>>>>
> >>>>> Opensips acts as SBC with RTP engine enabled.
> >>>>>
> >>>>> Calls are working fine, however after each call is finished,
> >>>>> bellow action happens.
> >>>>>
> >>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did
> >>>>> upgrade to latest stable release, and it is the same.
> >>>>>
> >>>>> Is this opensips script configuration issue or a bug? And how
> >>>>> could I fix it?
> >>>>>
> >>>>> [....]
> >>>>>
> >>>>> Thanks for all tips.
> >>>>>
> >>>>> BR
> >>>>> Simon
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231208/119f07e4/attachment-0001.html>

From neven at softnet.si  Fri Dec  8 14:30:39 2023
From: neven at softnet.si (Neven Grzancic)
Date: Fri, 8 Dec 2023 15:30:39 +0100
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
Message-ID: <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>

Hi Bogdan,

good hit on the apport service - thanks!

here's the trace we get from one such crash:

[New LWP 1130]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb) bt full
#0  0x0000000000000000 in ?? ()
No symbol table info available.
#1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, msg=<optimized out>, ctx=0x7f334fcc52c8)
     at /build/opensips-3.4.2/modules/acc/acc.c:965
         i = <optimized out>
         j = <optimized out>
         ret = 6
         res = -1
         nr_leg_vals = <optimized out>
         start_time = {tv_sec = 1702044564, tv_usec = 417047}
         core_s = {s = 0x7f33705e9878 "\006", len = 101}
         leg_s = {s = 0x0, len = <optimized out>}
         extra_s = {s = 0x0, len = <optimized out>}
         send = 0x0
         offset = <optimized out>
         av_type = 32563
         r_stat = <optimized out>
         locked = 0
         duration = 1338791072
         ms_duration = 0
         extra = <optimized out>
         error = <optimized out>
         __FUNCTION__ = "acc_aaa_cdrs"
#2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, ps=0x7ffdb12e09e0)
     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
         ctx = 0x7f334fcc52c8
         dlg = 0x7f334fcc54e0
         __FUNCTION__ = "acc_cdr_cb"
#3  0x00007f334f8142a0 in run_any_trans_callbacks (list=list at entry=0x7f334fcc6d58, type=type at entry=128,
     trans=trans at entry=0x7f334fcc6ce8, req=0x7f334fcc8770, rpl=rpl at entry=0x7f33705e7498, code=code at entry=200)
     at /build/opensips-3.4.2/modules/tm/t_hooks.c:214
         params = {req = 0x7f334fcc8770, rpl = 0x7f33705e7498, code = 200, param = 0x7f334fcc5270,
           extra1 = 0x7ffdb12e0b40, extra2 = 0x7f334fcc6e00}
         cbp = 0x7f334fcc5260
         backup = 0x55c8f7a02b00 <global_avps.lto_priv>
         trans_backup = 0x7f334fcc6ce8
         __FUNCTION__ = "run_any_trans_callbacks"
#4  0x00007f334f818443 in run_trans_callbacks (type=type at entry=128, trans=trans at entry=0x7f334fcc6ce8, req=<optimized out>, rpl=rpl at entry=0x7f33705e7498, code=code at entry=200) at /build/opensips-3.4.2/modules/tm/t_hooks.c:233
No locals.
#5  0x00007f334f818581 in run_trans_callbacks_locked (code=200, rpl=0x7f33705e7498, req=<optimized out>, trans=0x7f334fcc6ce8, type=128) at /build/opensips-3.4.2/modules/tm/t_hooks.c:255
No locals.
#6  run_trans_callbacks_locked (type=128, trans=0x7f334fcc6ce8, req=<optimized out>, rpl=0x7f33705e7498, code=200) at /build/opensips-3.4.2/modules/tm/t_hooks.c:246
No locals.
#7  0x00007f334f82ef22 in relay_reply (t=0x7f334fcc6ce8, p_msg=<optimized out>, branch=<optimized out>, msg_status=<optimized out>, cancel_bitmap=<optimized out>) at /build/opensips-3.4.2/modules/tm/t_reply.c:1408
         relay = 0
         save_clone = 0
         buf = 0x7f33705e9620 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 212.13.249.92:5060;branch=z9hG4bK4e83.fd8885b6.0\r\nVia: SIP/2.0/UDP 212.13.249.94;received=212.13.249.94;rport=5060;branch=z9hG4bKUtNtK5Nj897rr\r\nFrom: <sip:386980731395"...
         res_len = 536
         relayed_code = 200
         relayed_msg = 0x7f33705e7498
         bm = {to_tag_val = {s = 0x7f336f891af8 "\240\350\240\367\310U", len = 0}}
         totag_retr = 0
         reply_status = RPS_COMPLETED
         uas_rb = 0x7f334fcc6de8
         cb_s = {s = 0x7f33705e9620 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 212.13.249.92:5060;branch=z9hG4bK4e83.fd8885b6.0\r\nVia: SIP/2.0/UDP 212.13.249.94;received=212.13.249.94;rport=5060;branch=z9hG4bKUtNtK5Nj897rr\r\nFrom: <sip:386980731395"..., len = 536}
         text = {s = 0x0, len = -140509096}
         __FUNCTION__ = "relay_reply"
#8  0x00007f334f830835 in reply_received (p_msg=0x7f33705e7498) at /build/opensips-3.4.2/modules/tm/t_reply.c:1681
         msg_status = <optimized out>
         last_uac_status = 0
         branch = 0
         reply_status = <optimized out>
         timer = 0
         cancel_bitmap = 0
         uac = 0x7f334fcc6ec0
         t = 0x7f334fcc6ce8
         backup_list = <optimized out>
         has_reply_route = <optimized out>
         old_route_type = <optimized out>
         __FUNCTION__ = "reply_received"
#9  0x000055c8f770e0e5 in forward_reply (msg=0x7f33705e7498) at /build/opensips-3.4.2/forward.c:499
         new_buf = <optimized out>
         to = <optimized out>
         new_len = 1
         mod = 0x7f336f891af8
         proto = <optimized out>
         id = <optimized out>
         send_sock = <optimized out>
         s = <optimized out>
         len = <optimized out>
         error = <optimized out>
         skip = <optimized out>
         error0 = <optimized out>
         __FUNCTION__ = "forward_reply"
#10 0x000055c8f775542d in receive_msg (buf=<optimized out>, len=<optimized out>, rcv_info=<optimized out>, existing_context=0x0, msg_flags=<optimized out>) at /build/opensips-3.4.2/receive.c:278
         msg = 0x7f33705e7498
         start = {tv_sec = 139858358410128, tv_usec = 139859026441837}
         rc = 3
         old_route_type = <optimized out>
         tmp = <optimized out>
         in_buff = {s = 0x55c8f7b24320 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 213.253.120.65:5060;branch=z9hG4bK4e83.b2fe4a51.0\r\nVia: SIP/2.0/UDP 212.13.249.92:5060;branch=z9hG4bK4e83.fd8885b6.0\r\nVia: SIP/2.0/UDP 212.13.249.94;received=212.13.24"..., len = 612}
         ctx = 0x7f33705e8bc8
         __FUNCTION__ = "receive_msg"
#11 0x000055c8f78addd7 in udp_read_req (si=<optimized out>, bytes_read=<optimized out>) at net/proto_udp/proto_udp.c:186
         ri = {src_ip = {af = 2, len = 4, u = {addrl = {94317692413908, 94321635752912}, addr32 = {210593748, 21960, 4153932752, 21960}, addr16 = {26580, 3213, 21960, 0, 64464, 63383, 21960, 0}, addr = "\324g\215\f\310U\000\000\320\373\227\367\310U\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {1098448341, 0}, addr32 = {1098448341, 0, 0, 0}, addr16 = {64981, 16760, 0, 0, 0, 0, 0, 0}, addr = "\325\375xA", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto = 1, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304\324g\215\f\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 210593748}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 210593748, sin6_addr = {__in6_u = {__u6_addr8 = "\000\000\000\000\000\000\000\000 +\240\367\310U\000", __u6_addr16 = {0, 0, 0, 0, 11040, 63392, 21960, 0}, __u6_addr32 = {0, 0, 4154469152, 21960}}}, sin6_scope_id = 2973633109}}, bind_address = 0x7f336f8b52d8}
         len = <optimized out>
         tmp = <optimized out>
         fromlen = 16
         p = <optimized out>
         msg = {s = 0x55c8f7b24320 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 213.253.120.65:5060;branch=z9hG4bK4e83.b2fe4a51.0\r\nVia: SIP/2.0/UDP 212.13.249.92:5060;branch=z9hG4bK4e83.fd8885b6.0\r\nVia: SIP/2.0/UDP 212.13.249.94;received=212.13.24"..., len = 612}
         buf = "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 213.253.120.65:5060;branch=z9hG4bK4e83.b2fe4a51.0\r\nVia: SIP/2.0/UDP 212.13.249.92:5060;branch=z9hG4bK4e83.fd8885b6.0\r\nVia: SIP/2.0/UDP 212.13.249.94;received=212.13.24"...
         __FUNCTION__ = "udp_read_req"
#12 0x000055c8f78c75da in handle_io.constprop.1 (fm=0x7f336f8e7788, event_type=event_type at entry=1, idx=<optimized out>) at net/net_udp.c:295
         n = 0
         read = 0
         __FUNCTION__ = <optimized out>
#13 0x000055c8f78d4c40 in io_wait_loop_epoll.constprop.1.isra.0 (repeat=<optimized out>, t=<optimized out>, h=<optimized out>) at net/../io_wait_loop.h:305
         ret = <optimized out>
         n = <optimized out>
         r = 0
         i = <optimized out>
         e = <optimized out>
         ep_event = {events = 2, data = {ptr = 0xf7a0320000000000, fd = 0, u32 = 0, u64 = 17843316699223293952}}
         fd = <optimized out>
         curr_time = 78
         error = <optimized out>
         __FUNCTION__ = <optimized out>
#14 0x000055c8f78a42b5 in udp_start_processes (chd_rank=<optimized out>, startup_done=<optimized out>) at net/net_udp.c:528
         si = <optimized out>
         p_id = <optimized out>
         i = <optimized out>
         p = <optimized out>
         ifp_udp_rcv = {proc_desc = 0x55c8f796c046 "UDP receiver", flags = 4, type = TYPE_UDP}
         error = <optimized out>
         __FUNCTION__ = "udp_start_processes"
#15 0x000055c8f76d575d in main_loop () at /build/opensips-3.4.2/main.c:239
         startup_done = 0x0
         last_check = 0
         rc = <optimized out>
         chd_rank = <optimized out>
         startup_done = <optimized out>
         last_check = <optimized out>
         rc = <optimized out>
         profiling_handler = <optimized out>
         __FUNCTION__ = <optimized out>
         error = <optimized out>
#16 main (argc=<optimized out>, argv=<optimized out>) at /build/opensips-3.4.2/main.c:968
         c = <optimized out>
         r = <optimized out>
         tmp = 0x7ffdb12e2e53 ""
         tmp_len = <optimized out>
         port = <optimized out>
         proto = 0
         protos_no = <optimized out>
         options = 0x55c8f78ea290 "f:cCm:M:b:l:n:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:"
         ret = <optimized out>
         seed = 3254223836
         rfd = <optimized out>
         procs_no = <optimized out>
         __FUNCTION__ = "main"


On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
> Simon, I do not need the corefile, usually it is huge - as per web instructions (see the prev link), extract the backtrace (using gdb) and share it with me.
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> 
> On 08.12.2023 16:13, Simon Gajski wrote:
>> Hi Bogdan
>>
>> you were right
>> we have the core file now
>>
>> Please let me know where to send it (gzipped is approx 2MB)
>>
>>
>> BR
>> Simon
>>
>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>> Hi Simon,
>>>
>>> Maybe you have some apport service running on the machine, moving the core file.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>>   https://www.siphub.com
>>>
>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>> Dear Bogdan,
>>>>
>>>> we tried following https://opensips.org/Documentation/TroubleShooting-Crash and trying different things, and even though the syslog shows that the core file was dumped:
>>>>
>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in opensips[55816fbd0000+1f000]
>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 [Warning] Aborted connection 400 to db: 'opensips' user: 'opensips' host: 'localhost' (Got an error reading communication packets)
>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: core was generated
>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: INFO:core:handle_sigs: terminating due to SIGCHLD
>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: signal 15 received
>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: signal 15 received
>>>>
>>>> the core does not get generated, or at least not in the directory provided via options at runtime (-w /tmp). The issue is always repeatable (the daemon crashes after every finished call), if there are more active calls at the moment of the crash, whose calls remain active and proceed normally until termination (which again causes a crash). We also tried enabling debug mode, but in that case the process does not start successfully and runs into a timeout. In any case, any additional help or suggestion on how to successfully generate the core dump would be much appreciated, as we seem to have ran into a wall here...
>>>>
>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>
>>>>>
>>>>>
>>>>> -------- Posredovano sporočilo --------
>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after call is finished
>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling list <users at lists.opensips.org>
>>>>>
>>>>>
>>>>>
>>>>> Hi Simon,
>>>>>
>>>>> Well, the log is very self explanatory:
>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: core was generated
>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>
>>>>> Or shortly, you opensips just crashed :). So see https://opensips.org/Documentation/TroubleShooting-Crash for how to report further.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>>
>>>>> OpenSIPS Founder and Developer
>>>>>    https://www.opensips-solutions.com
>>>>>    https://www.siphub.com
>>>>>
>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> we are running opensips 3.4.2
>>>>>> on Ubuntu 22.04.3 LTS
>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 git-master-74075f63
>>>>>>
>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>
>>>>>> Calls are working fine, however after each call is finished, bellow action happens.
>>>>>>
>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did upgrade to latest stable release, and it is the same.
>>>>>>
>>>>>> Is this opensips script configuration issue or a bug? And how could I fix it?
>>>>>>
>>>>>> [....]
>>>>>>
>>>>>> Thanks for all tips.
>>>>>>
>>>>>> BR
>>>>>> Simon
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>
>>>
> 

-- 
Best regards / Lep pozdrav
Neven Grzancic, dipl.inž.el.(UN)
techsupport - systems administration & networking
-----------------------------------------------------------------------
Softnet d.o.o.       tel:  +386 1 8100 100  |   the quieter you
Borovec 2         direct:  +386 1 8100 107  | become, the more you
1236 Trzin           fax:  +386 1 8100 101  |   are able to hear
-----------------------------------------------------------------------

From liviu at opensips.org  Fri Dec  8 14:56:18 2023
From: liviu at opensips.org (Liviu Chircu)
Date: Fri, 8 Dec 2023 16:56:18 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
Message-ID: <65874f59-4adf-4245-ba57-c33e45946eb0@opensips.org>

On 08.12.2023 15:17, Bogdan-Andrei Iancu wrote:
> Maybe you have some apport service running on the machine, moving the 
> core file. 

Hello,

I second this too, as it's the 90% main cause for corefiles not 
generating on my environment.  To confirm, just do:

$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E

... if the output includes "apport", it means the "apport" suite is 
handling all corefile writing, which can be good or bad, depending on 
your settings.

Still, to avoid all of this and simply have the OS write any corefile 
into the dying process's working directory, just run the following under 
"root" user:

$ echo "core.%p" > /proc/sys/kernel/core_pattern

Best regards,

-- 
Liviu Chircu



From thesipguy at gmail.com  Wed Dec  6 14:18:03 2023
From: thesipguy at gmail.com (S.Rosenberg)
Date: Wed, 6 Dec 2023 09:18:03 -0500
Subject: [OpenSIPS-Users] uac_auth DB support
Message-ID: <CAMtj7Ro2uxqebdNL=QDDp8JwLkOEkS2vPbcvqz8UwWGPQSA-dg@mail.gmail.com>

Hi, I'm using the uac_auth to send calls to carriers that require
username/password credentials, until now I only had a handful of carriers
that don't support IP authentication so I hard coded the credentials, I was
thinking of pulling it from the  registrant table as most of the time I
would want to register to them anyway.

I would like to know if OpenSIPS has a way to pull the registrant info via
code without manually doing a DB query?

S. Rosenberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231206/86ff088a/attachment-0001.html>

From bogdan at opensips.org  Fri Dec  8 15:31:32 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 8 Dec 2023 17:31:32 +0200
Subject: [OpenSIPS-Users] OpenSIPS Control Panel supported OpenSIPS
 version question
In-Reply-To: <1d14c97ce8bf0ef8e8d2c10ce10d3fc8ab3ac705@rvgeerligs.nl>
References: <5d70d638-f0dd-418d-8150-5464cdd235aa@opensips.org>
 <6699ab05-9c42-4d5d-9f9f-c415b812cc8e@opensips.org>
 <f4f77f31-1922-4a67-854e-0954e66051ff@opensips.org>
 <a1a67cb4-32bf-4a01-8c0d-1683dbf7dab6@opensips.org>
 <CAOPUfWXK24wv-XmRT-yWUucb0yH6qtqMnwTwJEHXJsozXoW0rA@mail.gmail.com>
 <43df60a3af29ce6d47a7c3d844b4f93ab8892076@rvgeerligs.nl>
 <3399a87ce490752dbcd1d34fb2741a6287c0c176@rvgeerligs.nl>
 <7c3c6b1e0591853f5d73591f7be6eda86fc704ea@rvgeerligs.nl>
 <1d14c97ce8bf0ef8e8d2c10ce10d3fc8ab3ac705@rvgeerligs.nl>
Message-ID: <d316306c-2568-43f5-9e0c-75a1bf0cd114@opensips.org>

Hi Ronald,

Thanks for troubleshooting and fixing this. I pushed the fix on git !
https://github.com/OpenSIPS/opensips-cp/commit/492a0eb46dedc1f09297ed331013254cdd5bf1a8

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 08.12.2023 16:57, rvg at rvgeerligs.nl wrote:
> Hi Bogan-Andrei,
>
> Show errors was not an otion: I get error after log in. Instead I did 
> the following:
>
> using tail -f on apache error log file
>
>
> calling call center on the left menu and result is blank page
>
> [..]
>
>
> calling TLS management on the left panel and result is blank page
>
> [..]
>
>
> Calling UAC Registrant on the left menu and result is blank page
>
> [..]
>
>
> --
>
> diff /var/www/html/opensipscp/web/common/tools/tviewer/tviewer.php 
> /var/www/html/opensips-cp/web/common/tools/tviewer/tviewer.php
>
>
> 68,72c68,70
> < if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns']) 
> {
> < for ($i=0; $i
> < if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']) 
> && 
> $custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']!="" 
> && 
> file_exists($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']))
> < 
> require($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']);
> < }
> ---
> > for ($i=0; 
> $i<count($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns']); 
> $i++) {
> > if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']) 
> && 
> $custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']!="" 
> && 
> file_exists($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']))
> > 
> require($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_columns'][$i]['action_script']);
> 85,89c83,85
> < if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'])) 
> {
> < for ($i=0; $i
> < if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']) 
> && 
> $custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']!="" 
> && 
> file_exists($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']))
> < 
> require($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']);
> < }
> ---
> > for ($i=0; 
> $i<count($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons']); 
> $i++) {
> > if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']) 
> && 
> $custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']!="" 
> && 
> file_exists($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']))
> > 
> require($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_action_buttons'][$i]['action_script']);
> 98,99c94
> < if 
> (isset($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_search']['enabled']) 
> &&
> < 
> $custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_search']['enabled'])
> ---
> > if 
> ($custom_config[$module_id][$_SESSION[$module_id]['submenu_item_id']]['custom_search']['enabled'])
>
>
> I hope this is enough?
>
> Regards,
>
> Ronald
>
> December 8, 2023 at 8:39 AM, "Bogdan-Andrei Iancu" 
> <bogdan at opensips.org 
> <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>> 
> wrote:
>
>     Hi Ronald,
>
>     yes, please check for ERR or WARN in php.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 07.12.2023 22:26, rvg at rvgeerligs.nl wrote:
>
>         Hi Bogdan-Andrei,
>         The others like adresses and dialplan or dynamic routing (very
>         important one) work and the dialogues give the right answers.
>         No reaction means blank page.
>         Want me to enable PHP error messages?
>         Regards,
>         Ronald
>
>         December 7, 2023 at 6:18 PM, "Bogdan-Andrei Iancu"
>         <bogdan at opensips.org
>         <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>>
>         wrote:
>
>             Hi Ronald,
>
>             Tool as Addresses or Diaplan are still working in 9.3.4 ?
>             and just to clarify, what exactly means "no reaction"?
>             when you click on the "Call Center" tool, you still have
>             the old tool in the main right window? or is it turning
>             blank ?
>
>             Regards,
>
>             Bogdan-Andrei Iancu
>
>             OpenSIPS Founder and Developer
>                https://www.opensips-solutions.com
>                https://www.siphub.com
>
>             On 07.12.2023 15:44, rvg at rvgeerligs.nl wrote:
>
>                 Hi Bogdan,
>                 Short answer: yes.
>                 Did not change anything in modules.inc.php.
>                 I have 2 directories opensips-cp and opensipscp,
>                 containing 9.3.3 and 9.3.4 respectively. also
>                 configured in apache2.
>                 Copied the db.inc.php from the 9.3.3 to the 9.3.4
>                 directory.
>                 Regards,
>                 Ronald Geerligs
>
>                 December 7, 2023 at 9:08 AM, "Bogdan-Andrei Iancu"
>                 <bogdan at opensips.org
>                 <mailto:bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>>
>                 wrote:
>
>                     Hi Ronald,
>
>                     So same server with an OpenSIPS 3.4 works with OCP
>                     9.3.3, but not with OCP 9.3.4 - the only
>                     difference between the 2 tests is the version of
>                     OCP, still exactly the same env is used, right ?
>                     Any setting in the modules.inc.php ?
>
>                     Regards,
>
>                     Bogdan-Andrei Iancu
>
>                     OpenSIPS Founder and Developer
>                        https://www.opensips-solutions.com
>                        https://www.siphub.com
>
>                     On 06.12.2023 20:58, rvg at rvgeerligs.nl wrote:
>
>                         Hi all,
>                         I do not know where to post this, but maybe it
>                         is all right.
>                         I use:
>                         Opensips 3.4 compiled on Oracle VM ARM Ubuntu
>                         22.04.2 LTS - php 7.4 with OCP 9.3.3.
>                         Everything works!
>                         Installed OCP 9.3.4 and many menues on the
>                         left side have no reaction:
>                         CallCenter
>                         keepalived
>                         TLS management !
>                         UAC registrant
>                         SMPP Gateway
>                         TCP Management
>                         Regards,
>                         Ronald Geerligs
>
>                         October 2, 2023 at 8:49 AM, "Răzvan Crainea"
>                         <razvan at opensips.org
>                         <mailto:razvan at opensips.org?to=%22R%C4%83zvan%20Crainea%22%20%3Crazvan%40opensips.org%3E>>
>                         wrote:
>
>                             Hi, Nineto!
>                             Although it was not already released,
>                             OpenSIPS master branch should be
>                             compatible with OpenSIPS 3.4. The
>                             compatibility process is not yet
>                             complete, therefore a full release (9.3.4)
>                             is not available yet for
>                             OpenSIPS 3.4.
>                             Best regards,
>                             Răzvan Crainea
>                             OpenSIPS Core Developer / SIPhub CTO
>                             http://www.opensips-solutions.com/ /
>                             https://www.siphub.com/
>                             On 9/29/23 19:15, Nine to one wrote:
>
>                                 Hello OpenSIPS Control Panel developers,
>                                 From website OCP only mentioned
>                                 support up to OpenSIPS 3.3, I am using
>                                 3.4, so want to know if current OCP
>                                 already support OpenSIPS 3.4 or not.
>                                 Thanks,
>                                 Nineto
>                                 _______________________________________________
>                                 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231208/7b4a96ef/attachment-0001.html>

From bogdan at opensips.org  Fri Dec  8 15:38:54 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 8 Dec 2023 17:38:54 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
Message-ID: <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>

It looks you are using (or trying to) the CDR support via AAA.

Could you share the full modparam's for the acc module and the 
radius/diameter support?

Also, in using GDB, just do:
   f 1
   p proto

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 08.12.2023 16:30, Neven Grzancic wrote:
> Hi Bogdan,
>
> good hit on the apport service - thanks!
>
> here's the trace we get from one such crash:
>
> [New LWP 1130]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
> "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/sbin/opensips -P 
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x0000000000000000 in ?? ()
> (gdb) bt full
> #0  0x0000000000000000 in ?? ()
> No symbol table info available.
> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
> msg=<optimized out>, ctx=0x7f334fcc52c8)
>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>         i = <optimized out>
>         j = <optimized out>
>         ret = 6
>         res = -1
>         nr_leg_vals = <optimized out>
>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>         leg_s = {s = 0x0, len = <optimized out>}
>         extra_s = {s = 0x0, len = <optimized out>}
>         send = 0x0
>         offset = <optimized out>
>         av_type = 32563
>         r_stat = <optimized out>
>         locked = 0
>         duration = 1338791072
>         ms_duration = 0
>         extra = <optimized out>
>         error = <optimized out>
>         __FUNCTION__ = "acc_aaa_cdrs"
> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, ps=0x7ffdb12e09e0)
>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>         ctx = 0x7f334fcc52c8
>         dlg = 0x7f334fcc54e0
>         __FUNCTION__ = "acc_cdr_cb"
> [...]
>
>
> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>> Simon, I do not need the corefile, usually it is huge - as per web 
>> instructions (see the prev link), extract the backtrace (using gdb) 
>> and share it with me.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> On 08.12.2023 16:13, Simon Gajski wrote:
>>> Hi Bogdan
>>>
>>> you were right
>>> we have the core file now
>>>
>>> Please let me know where to send it (gzipped is approx 2MB)
>>>
>>>
>>> BR
>>> Simon
>>>
>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>> Hi Simon,
>>>>
>>>> Maybe you have some apport service running on the machine, moving 
>>>> the core file.
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>   https://www.opensips-solutions.com
>>>>   https://www.siphub.com
>>>>
>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>> Dear Bogdan,
>>>>>
>>>>> we tried following 
>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>> trying different things, and even though the syslog shows that the 
>>>>> core file was dumped:
>>>>>
>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in 
>>>>> opensips[55816fbd0000+1f000]
>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>> 'opensips' host: 'localhost' (Got an error reading communication 
>>>>> packets)
>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>> INFO:core:handle_sigs: core was generated
>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: 
>>>>> signal 15 received
>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: 
>>>>> signal 15 received
>>>>>
>>>>> the core does not get generated, or at least not in the directory 
>>>>> provided via options at runtime (-w /tmp). The issue is always 
>>>>> repeatable (the daemon crashes after every finished call), if 
>>>>> there are more active calls at the moment of the crash, whose 
>>>>> calls remain active and proceed normally until termination (which 
>>>>> again causes a crash). We also tried enabling debug mode, but in 
>>>>> that case the process does not start successfully and runs into a 
>>>>> timeout. In any case, any additional help or suggestion on how to 
>>>>> successfully generate the core dump would be much appreciated, as 
>>>>> we seem to have ran into a wall here...
>>>>>
>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> -------- Posredovano sporočilo --------
>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after 
>>>>>> call is finished
>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling 
>>>>>> list <users at lists.opensips.org>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Simon,
>>>>>>
>>>>>> Well, the log is very self explanatory:
>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>> INFO:core:handle_sigs: core was generated
>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>
>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for how 
>>>>>> to report further.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bogdan-Andrei Iancu
>>>>>>
>>>>>> OpenSIPS Founder and Developer
>>>>>>    https://www.opensips-solutions.com
>>>>>>    https://www.siphub.com
>>>>>>
>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> we are running opensips 3.4.2
>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>> git-master-74075f63
>>>>>>>
>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>
>>>>>>> Calls are working fine, however after each call is finished, 
>>>>>>> bellow action happens.
>>>>>>>
>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>>>>>> upgrade to latest stable release, and it is the same.
>>>>>>>
>>>>>>> Is this opensips script configuration issue or a bug? And how 
>>>>>>> could I fix it?
>>>>>>>
>>>>>>> [....]
>>>>>>>
>>>>>>> Thanks for all tips.
>>>>>>>
>>>>>>> BR
>>>>>>> Simon
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opensips.org
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>>
>>>>
>>
>



From simon at softnet.si  Mon Dec 11 08:00:35 2023
From: simon at softnet.si (Simon Gajski)
Date: Mon, 11 Dec 2023 09:00:35 +0100
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
 <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
Message-ID: <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>

Dear Bogdan,

yes, we do use CDR via AAA.
Here are used modparams:

#### ACCounting module
loadmodule "acc.so"
modparam("acc", "early_media", 0)
modparam("acc", "report_cancels", 0)
modparam("acc", "detect_direction", 1)
modparam("acc", "db_url", "mysql://opensips:opensipsrw at localhost/opensips")
#modparam("acc", "db_table_missed_calls", "acc")
modparam("acc", "service_type", 15)
modparam("acc", "leg_fields", "db: 
CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")

and we do  receive CDR in mysql acc table

gdb returns
Core was generated by `/usr/sbin/opensips -P /run/opensips/opensips.pid 
-f /etc/opensips/opensips.cfg'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000000 in ?? ()
(gdb) f 1
#1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
msg=<optimized out>, ctx=0x7f334fcc52c8) at 
/build/opensips-3.4.2/modules/acc/acc.c:965
965     /build/opensips-3.4.2/modules/acc/acc.c: No such file or directory.
(gdb) p proto
$1 = {init_prot = 0x0, create_aaa_message = 0x0, destroy_aaa_message = 
0x0, send_aaa_request = 0x0, dictionary_find = 0x0, avp_add = 0x0, 
avp_get = 0x0}


BR
Simon

Bogdan-Andrei Iancu je 08.12.2023 ob 16:38 napisal:
> It looks you are using (or trying to) the CDR support via AAA.
>
> Could you share the full modparam's for the acc module and the 
> radius/diameter support?
>
> Also, in using GDB, just do:
>   f 1
>   p proto
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
> https://www.opensips-solutions.com
> https://www.siphub.com
>
> On 08.12.2023 16:30, Neven Grzancic wrote:
>> Hi Bogdan,
>>
>> good hit on the apport service - thanks!
>>
>> here's the trace we get from one such crash:
>>
>> [New LWP 1130]
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library 
>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>> Core was generated by `/usr/sbin/opensips -P 
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0x0000000000000000 in ?? ()
>> (gdb) bt full
>> #0  0x0000000000000000 in ?? ()
>> No symbol table info available.
>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>> msg=<optimized out>, ctx=0x7f334fcc52c8)
>>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>>         i = <optimized out>
>>         j = <optimized out>
>>         ret = 6
>>         res = -1
>>         nr_leg_vals = <optimized out>
>>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>>         leg_s = {s = 0x0, len = <optimized out>}
>>         extra_s = {s = 0x0, len = <optimized out>}
>>         send = 0x0
>>         offset = <optimized out>
>>         av_type = 32563
>>         r_stat = <optimized out>
>>         locked = 0
>>         duration = 1338791072
>>         ms_duration = 0
>>         extra = <optimized out>
>>         error = <optimized out>
>>         __FUNCTION__ = "acc_aaa_cdrs"
>> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, ps=0x7ffdb12e09e0)
>>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>>         ctx = 0x7f334fcc52c8
>>         dlg = 0x7f334fcc54e0
>>         __FUNCTION__ = "acc_cdr_cb"
>> [...]
>>
>>
>> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>>> Simon, I do not need the corefile, usually it is huge - as per web 
>>> instructions (see the prev link), extract the backtrace (using gdb) 
>>> and share it with me.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>> https://www.opensips-solutions.com
>>> https://www.siphub.com
>>>
>>> On 08.12.2023 16:13, Simon Gajski wrote:
>>>> Hi Bogdan
>>>>
>>>> you were right
>>>> we have the core file now
>>>>
>>>> Please let me know where to send it (gzipped is approx 2MB)
>>>>
>>>>
>>>> BR
>>>> Simon
>>>>
>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>>> Hi Simon,
>>>>>
>>>>> Maybe you have some apport service running on the machine, moving 
>>>>> the core file.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>>
>>>>> OpenSIPS Founder and Developer
>>>>> https://www.opensips-solutions.com
>>>>> https://www.siphub.com
>>>>>
>>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>>> Dear Bogdan,
>>>>>>
>>>>>> we tried following 
>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>>> trying different things, and even though the syslog shows that 
>>>>>> the core file was dumped:
>>>>>>
>>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 in 
>>>>>> opensips[55816fbd0000+1f000]
>>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>>> 'opensips' host: 'localhost' (Got an error reading communication 
>>>>>> packets)
>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>> INFO:core:handle_sigs: core was generated
>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: INFO:core:sig_usr: 
>>>>>> signal 15 received
>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: INFO:core:sig_usr: 
>>>>>> signal 15 received
>>>>>>
>>>>>> the core does not get generated, or at least not in the directory 
>>>>>> provided via options at runtime (-w /tmp). The issue is always 
>>>>>> repeatable (the daemon crashes after every finished call), if 
>>>>>> there are more active calls at the moment of the crash, whose 
>>>>>> calls remain active and proceed normally until termination (which 
>>>>>> again causes a crash). We also tried enabling debug mode, but in 
>>>>>> that case the process does not start successfully and runs into a 
>>>>>> timeout. In any case, any additional help or suggestion on how to 
>>>>>> successfully generate the core dump would be much appreciated, as 
>>>>>> we seem to have ran into a wall here...
>>>>>>
>>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -------- Posredovano sporočilo --------
>>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after 
>>>>>>> call is finished
>>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users mailling 
>>>>>>> list <users at lists.opensips.org>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Simon,
>>>>>>>
>>>>>>> Well, the log is very self explanatory:
>>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>
>>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for how 
>>>>>>> to report further.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Bogdan-Andrei Iancu
>>>>>>>
>>>>>>> OpenSIPS Founder and Developer
>>>>>>> https://www.opensips-solutions.com
>>>>>>> https://www.siphub.com
>>>>>>>
>>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> we are running opensips 3.4.2
>>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>>> git-master-74075f63
>>>>>>>>
>>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>>
>>>>>>>> Calls are working fine, however after each call is finished, 
>>>>>>>> bellow action happens.
>>>>>>>>
>>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>>>>>>> upgrade to latest stable release, and it is the same.
>>>>>>>>
>>>>>>>> Is this opensips script configuration issue or a bug? And how 
>>>>>>>> could I fix it?
>>>>>>>>
>>>>>>>> [....]
>>>>>>>>
>>>>>>>> Thanks for all tips.
>>>>>>>>
>>>>>>>> BR
>>>>>>>> Simon
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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/20231211/7f9eb425/attachment.html>

From bogdan at opensips.org  Mon Dec 11 09:49:45 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 11 Dec 2023 11:49:45 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
 <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
 <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>
Message-ID: <2b35862e-9486-4a17-8b3b-61753c55cf55@opensips.org>

Hi Simon,

As per the trace posted by Neven, the crash is related to the AAA 
support (for ACC), not the DB one. So, are you using RADIUS or DIAMETER 
for the CDRs?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 11.12.2023 10:00, Simon Gajski wrote:
>
> Dear Bogdan,
>
> yes, we do use CDR via AAA.
> Here are used modparams:
>
> #### ACCounting module
> loadmodule "acc.so"
> modparam("acc", "early_media", 0)
> modparam("acc", "report_cancels", 0)
> modparam("acc", "detect_direction", 1)
> modparam("acc", "db_url", 
> "mysql://opensips:opensipsrw at localhost/opensips")
> #modparam("acc", "db_table_missed_calls", "acc")
> modparam("acc", "service_type", 15)
> modparam("acc", "leg_fields", "db: 
> CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")
>
> and we do  receive CDR in mysql acc table
>
> gdb returns
> Core was generated by `/usr/sbin/opensips -P 
> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x0000000000000000 in ?? ()
> (gdb) f 1
> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
> msg=<optimized out>, ctx=0x7f334fcc52c8) at 
> /build/opensips-3.4.2/modules/acc/acc.c:965
> 965     /build/opensips-3.4.2/modules/acc/acc.c: No such file or 
> directory.
> (gdb) p proto
> $1 = {init_prot = 0x0, create_aaa_message = 0x0, destroy_aaa_message = 
> 0x0, send_aaa_request = 0x0, dictionary_find = 0x0, avp_add = 0x0, 
> avp_get = 0x0}
>
>
> BR
> Simon
>
> Bogdan-Andrei Iancu je 08.12.2023 ob 16:38 napisal:
>> It looks you are using (or trying to) the CDR support via AAA.
>>
>> Could you share the full modparam's for the acc module and the 
>> radius/diameter support?
>>
>> Also, in using GDB, just do:
>>   f 1
>>   p proto
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>> https://www.opensips-solutions.com
>> https://www.siphub.com
>>
>> On 08.12.2023 16:30, Neven Grzancic wrote:
>>> Hi Bogdan,
>>>
>>> good hit on the apport service - thanks!
>>>
>>> here's the trace we get from one such crash:
>>>
>>> [New LWP 1130]
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library 
>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>> Core was generated by `/usr/sbin/opensips -P 
>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  0x0000000000000000 in ?? ()
>>> (gdb) bt full
>>> #0  0x0000000000000000 in ?? ()
>>> No symbol table info available.
>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>> msg=<optimized out>, ctx=0x7f334fcc52c8)
>>>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>>>         i = <optimized out>
>>>         j = <optimized out>
>>>         ret = 6
>>>         res = -1
>>>         nr_leg_vals = <optimized out>
>>>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>>>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>>>         leg_s = {s = 0x0, len = <optimized out>}
>>>         extra_s = {s = 0x0, len = <optimized out>}
>>>         send = 0x0
>>>         offset = <optimized out>
>>>         av_type = 32563
>>>         r_stat = <optimized out>
>>>         locked = 0
>>>         duration = 1338791072
>>>         ms_duration = 0
>>>         extra = <optimized out>
>>>         error = <optimized out>
>>>         __FUNCTION__ = "acc_aaa_cdrs"
>>> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, ps=0x7ffdb12e09e0)
>>>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>>>         ctx = 0x7f334fcc52c8
>>>         dlg = 0x7f334fcc54e0
>>>         __FUNCTION__ = "acc_cdr_cb"
>>> [...]
>>>
>>>
>>> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>>>> Simon, I do not need the corefile, usually it is huge - as per web 
>>>> instructions (see the prev link), extract the backtrace (using gdb) 
>>>> and share it with me.
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>> https://www.opensips-solutions.com
>>>> https://www.siphub.com
>>>>
>>>> On 08.12.2023 16:13, Simon Gajski wrote:
>>>>> Hi Bogdan
>>>>>
>>>>> you were right
>>>>> we have the core file now
>>>>>
>>>>> Please let me know where to send it (gzipped is approx 2MB)
>>>>>
>>>>>
>>>>> BR
>>>>> Simon
>>>>>
>>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>>>> Hi Simon,
>>>>>>
>>>>>> Maybe you have some apport service running on the machine, moving 
>>>>>> the core file.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bogdan-Andrei Iancu
>>>>>>
>>>>>> OpenSIPS Founder and Developer
>>>>>> https://www.opensips-solutions.com
>>>>>> https://www.siphub.com
>>>>>>
>>>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>>>> Dear Bogdan,
>>>>>>>
>>>>>>> we tried following 
>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>>>> trying different things, and even though the syslog shows that 
>>>>>>> the core file was dumped:
>>>>>>>
>>>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 
>>>>>>> in opensips[55816fbd0000+1f000]
>>>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>>>> 'opensips' host: 'localhost' (Got an error reading communication 
>>>>>>> packets)
>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: 
>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: 
>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>
>>>>>>> the core does not get generated, or at least not in the 
>>>>>>> directory provided via options at runtime (-w /tmp). The issue 
>>>>>>> is always repeatable (the daemon crashes after every finished 
>>>>>>> call), if there are more active calls at the moment of the 
>>>>>>> crash, whose calls remain active and proceed normally until 
>>>>>>> termination (which again causes a crash). We also tried enabling 
>>>>>>> debug mode, but in that case the process does not start 
>>>>>>> successfully and runs into a timeout. In any case, any 
>>>>>>> additional help or suggestion on how to successfully generate 
>>>>>>> the core dump would be much appreciated, as we seem to have ran 
>>>>>>> into a wall here...
>>>>>>>
>>>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -------- Posredovano sporočilo --------
>>>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after 
>>>>>>>> call is finished
>>>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users 
>>>>>>>> mailling list <users at lists.opensips.org>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Simon,
>>>>>>>>
>>>>>>>> Well, the log is very self explanatory:
>>>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>
>>>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for 
>>>>>>>> how to report further.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>
>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>> https://www.opensips-solutions.com
>>>>>>>> https://www.siphub.com
>>>>>>>>
>>>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> we are running opensips 3.4.2
>>>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>>>> git-master-74075f63
>>>>>>>>>
>>>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>>>
>>>>>>>>> Calls are working fine, however after each call is finished, 
>>>>>>>>> bellow action happens.
>>>>>>>>>
>>>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we did 
>>>>>>>>> upgrade to latest stable release, and it is the same.
>>>>>>>>>
>>>>>>>>> Is this opensips script configuration issue or a bug? And how 
>>>>>>>>> could I fix it?
>>>>>>>>>
>>>>>>>>> [....]
>>>>>>>>>
>>>>>>>>> Thanks for all tips.
>>>>>>>>>
>>>>>>>>> BR
>>>>>>>>> Simon
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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/20231211/e3c5bdbd/attachment-0001.html>

From simon at softnet.si  Mon Dec 11 10:53:10 2023
From: simon at softnet.si (Simon Gajski)
Date: Mon, 11 Dec 2023 11:53:10 +0100
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <2b35862e-9486-4a17-8b3b-61753c55cf55@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
 <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
 <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>
 <2b35862e-9486-4a17-8b3b-61753c55cf55@opensips.org>
Message-ID: <53fe14b2-30e3-4947-ae28-3f56ac2c93db@softnet.si>

Dear Bogdan

We use only accounting.
But there was left a line do_accounting("aaa"); in cfg script that I 
somehow  missed.

After removal, it works as expected.

Thank you for all help and my apologies not for detecting this earlier.

BR
Simon

Bogdan-Andrei Iancu je 11.12.2023 ob 10:49 napisal:
> Hi Simon,
>
> As per the trace posted by Neven, the crash is related to the AAA 
> support (for ACC), not the DB one. So, are you using RADIUS or 
> DIAMETER for the CDRs?
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 11.12.2023 10:00, Simon Gajski wrote:
>>
>> Dear Bogdan,
>>
>> yes, we do use CDR via AAA.
>> Here are used modparams:
>>
>> #### ACCounting module
>> loadmodule "acc.so"
>> modparam("acc", "early_media", 0)
>> modparam("acc", "report_cancels", 0)
>> modparam("acc", "detect_direction", 1)
>> modparam("acc", "db_url", 
>> "mysql://opensips:opensipsrw at localhost/opensips")
>> #modparam("acc", "db_table_missed_calls", "acc")
>> modparam("acc", "service_type", 15)
>> modparam("acc", "leg_fields", "db: 
>> CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")
>>
>> and we do  receive CDR in mysql acc table
>>
>> gdb returns
>> Core was generated by `/usr/sbin/opensips -P 
>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>> Program terminated with signal SIGSEGV, Segmentation fault.
>> #0  0x0000000000000000 in ?? ()
>> (gdb) f 1
>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>> msg=<optimized out>, ctx=0x7f334fcc52c8) at 
>> /build/opensips-3.4.2/modules/acc/acc.c:965
>> 965     /build/opensips-3.4.2/modules/acc/acc.c: No such file or 
>> directory.
>> (gdb) p proto
>> $1 = {init_prot = 0x0, create_aaa_message = 0x0, destroy_aaa_message 
>> = 0x0, send_aaa_request = 0x0, dictionary_find = 0x0, avp_add = 0x0, 
>> avp_get = 0x0}
>>
>>
>> BR
>> Simon
>>
>> Bogdan-Andrei Iancu je 08.12.2023 ob 16:38 napisal:
>>> It looks you are using (or trying to) the CDR support via AAA.
>>>
>>> Could you share the full modparam's for the acc module and the 
>>> radius/diameter support?
>>>
>>> Also, in using GDB, just do:
>>>   f 1
>>>   p proto
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>> https://www.opensips-solutions.com
>>> https://www.siphub.com
>>>
>>> On 08.12.2023 16:30, Neven Grzancic wrote:
>>>> Hi Bogdan,
>>>>
>>>> good hit on the apport service - thanks!
>>>>
>>>> here's the trace we get from one such crash:
>>>>
>>>> [New LWP 1130]
>>>> [Thread debugging using libthread_db enabled]
>>>> Using host libthread_db library 
>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>> Core was generated by `/usr/sbin/opensips -P 
>>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>> #0  0x0000000000000000 in ?? ()
>>>> (gdb) bt full
>>>> #0  0x0000000000000000 in ?? ()
>>>> No symbol table info available.
>>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>>> msg=<optimized out>, ctx=0x7f334fcc52c8)
>>>>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>>>>         i = <optimized out>
>>>>         j = <optimized out>
>>>>         ret = 6
>>>>         res = -1
>>>>         nr_leg_vals = <optimized out>
>>>>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>>>>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>>>>         leg_s = {s = 0x0, len = <optimized out>}
>>>>         extra_s = {s = 0x0, len = <optimized out>}
>>>>         send = 0x0
>>>>         offset = <optimized out>
>>>>         av_type = 32563
>>>>         r_stat = <optimized out>
>>>>         locked = 0
>>>>         duration = 1338791072
>>>>         ms_duration = 0
>>>>         extra = <optimized out>
>>>>         error = <optimized out>
>>>>         __FUNCTION__ = "acc_aaa_cdrs"
>>>> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, 
>>>> ps=0x7ffdb12e09e0)
>>>>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>>>>         ctx = 0x7f334fcc52c8
>>>>         dlg = 0x7f334fcc54e0
>>>>         __FUNCTION__ = "acc_cdr_cb"
>>>> [...]
>>>>
>>>>
>>>> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>>>>> Simon, I do not need the corefile, usually it is huge - as per web 
>>>>> instructions (see the prev link), extract the backtrace (using 
>>>>> gdb) and share it with me.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>>
>>>>> OpenSIPS Founder and Developer
>>>>> https://www.opensips-solutions.com
>>>>> https://www.siphub.com
>>>>>
>>>>> On 08.12.2023 16:13, Simon Gajski wrote:
>>>>>> Hi Bogdan
>>>>>>
>>>>>> you were right
>>>>>> we have the core file now
>>>>>>
>>>>>> Please let me know where to send it (gzipped is approx 2MB)
>>>>>>
>>>>>>
>>>>>> BR
>>>>>> Simon
>>>>>>
>>>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>>>>> Hi Simon,
>>>>>>>
>>>>>>> Maybe you have some apport service running on the machine, 
>>>>>>> moving the core file.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Bogdan-Andrei Iancu
>>>>>>>
>>>>>>> OpenSIPS Founder and Developer
>>>>>>> https://www.opensips-solutions.com
>>>>>>> https://www.siphub.com
>>>>>>>
>>>>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>>>>> Dear Bogdan,
>>>>>>>>
>>>>>>>> we tried following 
>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>>>>> trying different things, and even though the syslog shows that 
>>>>>>>> the core file was dumped:
>>>>>>>>
>>>>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 
>>>>>>>> in opensips[55816fbd0000+1f000]
>>>>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>>>>> 'opensips' host: 'localhost' (Got an error reading 
>>>>>>>> communication packets)
>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: 
>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: 
>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>>
>>>>>>>> the core does not get generated, or at least not in the 
>>>>>>>> directory provided via options at runtime (-w /tmp). The issue 
>>>>>>>> is always repeatable (the daemon crashes after every finished 
>>>>>>>> call), if there are more active calls at the moment of the 
>>>>>>>> crash, whose calls remain active and proceed normally until 
>>>>>>>> termination (which again causes a crash). We also tried 
>>>>>>>> enabling debug mode, but in that case the process does not 
>>>>>>>> start successfully and runs into a timeout. In any case, any 
>>>>>>>> additional help or suggestion on how to successfully generate 
>>>>>>>> the core dump would be much appreciated, as we seem to have ran 
>>>>>>>> into a wall here...
>>>>>>>>
>>>>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -------- Posredovano sporočilo --------
>>>>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after 
>>>>>>>>> call is finished
>>>>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users 
>>>>>>>>> mailling list <users at lists.opensips.org>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Simon,
>>>>>>>>>
>>>>>>>>> Well, the log is very self explanatory:
>>>>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>>
>>>>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for 
>>>>>>>>> how to report further.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>>
>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>> https://www.opensips-solutions.com
>>>>>>>>> https://www.siphub.com
>>>>>>>>>
>>>>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> we are running opensips 3.4.2
>>>>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>>>>> git-master-74075f63
>>>>>>>>>>
>>>>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>>>>
>>>>>>>>>> Calls are working fine, however after each call is finished, 
>>>>>>>>>> bellow action happens.
>>>>>>>>>>
>>>>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we 
>>>>>>>>>> did upgrade to latest stable release, and it is the same.
>>>>>>>>>>
>>>>>>>>>> Is this opensips script configuration issue or a bug? And how 
>>>>>>>>>> could I fix it?
>>>>>>>>>>
>>>>>>>>>> [....]
>>>>>>>>>>
>>>>>>>>>> Thanks for all tips.
>>>>>>>>>>
>>>>>>>>>> BR
>>>>>>>>>> Simon
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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/20231211/59d33861/attachment-0001.html>

From bogdan at opensips.org  Mon Dec 11 14:46:06 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 11 Dec 2023 16:46:06 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <53fe14b2-30e3-4947-ae28-3f56ac2c93db@softnet.si>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
 <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
 <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>
 <2b35862e-9486-4a17-8b3b-61753c55cf55@opensips.org>
 <53fe14b2-30e3-4947-ae28-3f56ac2c93db@softnet.si>
Message-ID: <19b713a2-9a73-42e5-87c4-65fe18a00e2e@opensips.org>

Hi Simon,

Right, this explains it. Still, we need to do a fix here, to prevent 
such cases, where a backend is required for CDRs, but not configured.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 11.12.2023 12:53, Simon Gajski wrote:
>
> Dear Bogdan
>
> We use only accounting.
> But there was left a line do_accounting("aaa"); in cfg script that I 
> somehow  missed.
>
> After removal, it works as expected.
>
> Thank you for all help and my apologies not for detecting this earlier.
>
> BR
> Simon
>
> Bogdan-Andrei Iancu je 11.12.2023 ob 10:49 napisal:
>> Hi Simon,
>>
>> As per the trace posted by Neven, the crash is related to the AAA 
>> support (for ACC), not the DB one. So, are you using RADIUS or 
>> DIAMETER for the CDRs?
>>
>> Regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>> On 11.12.2023 10:00, Simon Gajski wrote:
>>>
>>> Dear Bogdan,
>>>
>>> yes, we do use CDR via AAA.
>>> Here are used modparams:
>>>
>>> #### ACCounting module
>>> loadmodule "acc.so"
>>> modparam("acc", "early_media", 0)
>>> modparam("acc", "report_cancels", 0)
>>> modparam("acc", "detect_direction", 1)
>>> modparam("acc", "db_url", 
>>> "mysql://opensips:opensipsrw at localhost/opensips")
>>> #modparam("acc", "db_table_missed_calls", "acc")
>>> modparam("acc", "service_type", 15)
>>> modparam("acc", "leg_fields", "db: 
>>> CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")
>>>
>>> and we do  receive CDR in mysql acc table
>>>
>>> gdb returns
>>> Core was generated by `/usr/sbin/opensips -P 
>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  0x0000000000000000 in ?? ()
>>> (gdb) f 1
>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>> msg=<optimized out>, ctx=0x7f334fcc52c8) at 
>>> /build/opensips-3.4.2/modules/acc/acc.c:965
>>> 965     /build/opensips-3.4.2/modules/acc/acc.c: No such file or 
>>> directory.
>>> (gdb) p proto
>>> $1 = {init_prot = 0x0, create_aaa_message = 0x0, destroy_aaa_message 
>>> = 0x0, send_aaa_request = 0x0, dictionary_find = 0x0, avp_add = 0x0, 
>>> avp_get = 0x0}
>>>
>>>
>>> BR
>>> Simon
>>>
>>> Bogdan-Andrei Iancu je 08.12.2023 ob 16:38 napisal:
>>>> It looks you are using (or trying to) the CDR support via AAA.
>>>>
>>>> Could you share the full modparam's for the acc module and the 
>>>> radius/diameter support?
>>>>
>>>> Also, in using GDB, just do:
>>>>   f 1
>>>>   p proto
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>> https://www.opensips-solutions.com
>>>> https://www.siphub.com
>>>>
>>>> On 08.12.2023 16:30, Neven Grzancic wrote:
>>>>> Hi Bogdan,
>>>>>
>>>>> good hit on the apport service - thanks!
>>>>>
>>>>> here's the trace we get from one such crash:
>>>>>
>>>>> [New LWP 1130]
>>>>> [Thread debugging using libthread_db enabled]
>>>>> Using host libthread_db library 
>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>> Core was generated by `/usr/sbin/opensips -P 
>>>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>>> #0  0x0000000000000000 in ?? ()
>>>>> (gdb) bt full
>>>>> #0  0x0000000000000000 in ?? ()
>>>>> No symbol table info available.
>>>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>>>> msg=<optimized out>, ctx=0x7f334fcc52c8)
>>>>>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>>>>>         i = <optimized out>
>>>>>         j = <optimized out>
>>>>>         ret = 6
>>>>>         res = -1
>>>>>         nr_leg_vals = <optimized out>
>>>>>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>>>>>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>>>>>         leg_s = {s = 0x0, len = <optimized out>}
>>>>>         extra_s = {s = 0x0, len = <optimized out>}
>>>>>         send = 0x0
>>>>>         offset = <optimized out>
>>>>>         av_type = 32563
>>>>>         r_stat = <optimized out>
>>>>>         locked = 0
>>>>>         duration = 1338791072
>>>>>         ms_duration = 0
>>>>>         extra = <optimized out>
>>>>>         error = <optimized out>
>>>>>         __FUNCTION__ = "acc_aaa_cdrs"
>>>>> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, 
>>>>> ps=0x7ffdb12e09e0)
>>>>>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>>>>>         ctx = 0x7f334fcc52c8
>>>>>         dlg = 0x7f334fcc54e0
>>>>>         __FUNCTION__ = "acc_cdr_cb"
>>>>> [...]
>>>>>
>>>>>
>>>>> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>>>>>> Simon, I do not need the corefile, usually it is huge - as per 
>>>>>> web instructions (see the prev link), extract the backtrace 
>>>>>> (using gdb) and share it with me.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Bogdan-Andrei Iancu
>>>>>>
>>>>>> OpenSIPS Founder and Developer
>>>>>> https://www.opensips-solutions.com
>>>>>> https://www.siphub.com
>>>>>>
>>>>>> On 08.12.2023 16:13, Simon Gajski wrote:
>>>>>>> Hi Bogdan
>>>>>>>
>>>>>>> you were right
>>>>>>> we have the core file now
>>>>>>>
>>>>>>> Please let me know where to send it (gzipped is approx 2MB)
>>>>>>>
>>>>>>>
>>>>>>> BR
>>>>>>> Simon
>>>>>>>
>>>>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>>>>>> Hi Simon,
>>>>>>>>
>>>>>>>> Maybe you have some apport service running on the machine, 
>>>>>>>> moving the core file.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>
>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>> https://www.opensips-solutions.com
>>>>>>>> https://www.siphub.com
>>>>>>>>
>>>>>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>>>>>> Dear Bogdan,
>>>>>>>>>
>>>>>>>>> we tried following 
>>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>>>>>> trying different things, and even though the syslog shows that 
>>>>>>>>> the core file was dumped:
>>>>>>>>>
>>>>>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 14 
>>>>>>>>> in opensips[55816fbd0000+1f000]
>>>>>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>>>>>> 'opensips' host: 'localhost' (Got an error reading 
>>>>>>>>> communication packets)
>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: 
>>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: 
>>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>>>
>>>>>>>>> the core does not get generated, or at least not in the 
>>>>>>>>> directory provided via options at runtime (-w /tmp). The issue 
>>>>>>>>> is always repeatable (the daemon crashes after every finished 
>>>>>>>>> call), if there are more active calls at the moment of the 
>>>>>>>>> crash, whose calls remain active and proceed normally until 
>>>>>>>>> termination (which again causes a crash). We also tried 
>>>>>>>>> enabling debug mode, but in that case the process does not 
>>>>>>>>> start successfully and runs into a timeout. In any case, any 
>>>>>>>>> additional help or suggestion on how to successfully generate 
>>>>>>>>> the core dump would be much appreciated, as we seem to have 
>>>>>>>>> ran into a wall here...
>>>>>>>>>
>>>>>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------- Posredovano sporočilo --------
>>>>>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting after 
>>>>>>>>>> call is finished
>>>>>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users 
>>>>>>>>>> mailling list <users at lists.opensips.org>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Simon,
>>>>>>>>>>
>>>>>>>>>> Well, the log is very self explanatory:
>>>>>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>> INFO:core:handle_sigs: child process 28495 exited by a signal 11
>>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>>>
>>>>>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for 
>>>>>>>>>> how to report further.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>>>
>>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>>> https://www.opensips-solutions.com
>>>>>>>>>> https://www.siphub.com
>>>>>>>>>>
>>>>>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi
>>>>>>>>>>>
>>>>>>>>>>> we are running opensips 3.4.2
>>>>>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>>>>>> git-master-74075f63
>>>>>>>>>>>
>>>>>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>>>>>
>>>>>>>>>>> Calls are working fine, however after each call is finished, 
>>>>>>>>>>> bellow action happens.
>>>>>>>>>>>
>>>>>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we 
>>>>>>>>>>> did upgrade to latest stable release, and it is the same.
>>>>>>>>>>>
>>>>>>>>>>> Is this opensips script configuration issue or a bug? And 
>>>>>>>>>>> how could I fix it?
>>>>>>>>>>>
>>>>>>>>>>> [....]
>>>>>>>>>>>
>>>>>>>>>>> Thanks for all tips.
>>>>>>>>>>>
>>>>>>>>>>> BR
>>>>>>>>>>> Simon
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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/20231211/affd38ba/attachment-0001.html>

From bogdan at opensips.org  Mon Dec 11 16:30:09 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 11 Dec 2023 18:30:09 +0200
Subject: [OpenSIPS-Users] Fwd: opensips is restarting after call is
 finished
In-Reply-To: <19b713a2-9a73-42e5-87c4-65fe18a00e2e@opensips.org>
References: <b723bfe6-2971-4219-8a8d-c0b71048a9ee@opensips.org>
 <be700f7a-75ef-42fa-adda-ff0902c36c81@softnet.si>
 <bf1a221b-b028-4211-8692-62508c17df0c@softnet.si>
 <dc4cf074-62dc-4837-a333-74feede32a34@opensips.org>
 <0e424bc1-5cd6-4809-843a-14dd8a02a1cb@softnet.si>
 <616044eb-6593-4d1e-9277-988e53802ff8@opensips.org>
 <3ef633cf-223e-49e8-ae6d-a33e6e255947@softnet.si>
 <4fd3bcf4-a3b4-4cf3-8664-eb002090c486@opensips.org>
 <4072c796-692d-4f70-bc1e-1f45d44e4535@softnet.si>
 <2b35862e-9486-4a17-8b3b-61753c55cf55@opensips.org>
 <53fe14b2-30e3-4947-ae28-3f56ac2c93db@softnet.si>
 <19b713a2-9a73-42e5-87c4-65fe18a00e2e@opensips.org>
Message-ID: <5010490d-15b3-48f4-9a42-743bffced64d@opensips.org>

Thanks to Liviu, we now have a fix for this :
https://github.com/OpenSIPS/opensips/commit/42f1eb7ae7dfa702602ca8aa232e9b9016b2d146

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 11.12.2023 16:46, Bogdan-Andrei Iancu wrote:
> Hi Simon,
>
> Right, this explains it. Still, we need to do a fix here, to prevent 
> such cases, where a backend is required for CDRs, but not configured.
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 11.12.2023 12:53, Simon Gajski wrote:
>>
>> Dear Bogdan
>>
>> We use only accounting.
>> But there was left a line do_accounting("aaa"); in cfg script that I 
>> somehow  missed.
>>
>> After removal, it works as expected.
>>
>> Thank you for all help and my apologies not for detecting this earlier.
>>
>> BR
>> Simon
>>
>> Bogdan-Andrei Iancu je 11.12.2023 ob 10:49 napisal:
>>> Hi Simon,
>>>
>>> As per the trace posted by Neven, the crash is related to the AAA 
>>> support (for ACC), not the DB one. So, are you using RADIUS or 
>>> DIAMETER for the CDRs?
>>>
>>> Regards,
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>>    https://www.siphub.com
>>> On 11.12.2023 10:00, Simon Gajski wrote:
>>>>
>>>> Dear Bogdan,
>>>>
>>>> yes, we do use CDR via AAA.
>>>> Here are used modparams:
>>>>
>>>> #### ACCounting module
>>>> loadmodule "acc.so"
>>>> modparam("acc", "early_media", 0)
>>>> modparam("acc", "report_cancels", 0)
>>>> modparam("acc", "detect_direction", 1)
>>>> modparam("acc", "db_url", 
>>>> "mysql://opensips:opensipsrw at localhost/opensips")
>>>> #modparam("acc", "db_table_missed_calls", "acc")
>>>> modparam("acc", "service_type", 15)
>>>> modparam("acc", "leg_fields", "db: 
>>>> CALLER->Anum;CALLEE->Bnum;TYPE->leg_type;SRCIP->srcIP;DESTIP->destIP;DIRECTION->direction")
>>>>
>>>> and we do  receive CDR in mysql acc table
>>>>
>>>> gdb returns
>>>> Core was generated by `/usr/sbin/opensips -P 
>>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>> #0  0x0000000000000000 in ?? ()
>>>> (gdb) f 1
>>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>>> msg=<optimized out>, ctx=0x7f334fcc52c8) at 
>>>> /build/opensips-3.4.2/modules/acc/acc.c:965
>>>> 965     /build/opensips-3.4.2/modules/acc/acc.c: No such file or 
>>>> directory.
>>>> (gdb) p proto
>>>> $1 = {init_prot = 0x0, create_aaa_message = 0x0, 
>>>> destroy_aaa_message = 0x0, send_aaa_request = 0x0, dictionary_find 
>>>> = 0x0, avp_add = 0x0, avp_get = 0x0}
>>>>
>>>>
>>>> BR
>>>> Simon
>>>>
>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 16:38 napisal:
>>>>> It looks you are using (or trying to) the CDR support via AAA.
>>>>>
>>>>> Could you share the full modparam's for the acc module and the 
>>>>> radius/diameter support?
>>>>>
>>>>> Also, in using GDB, just do:
>>>>>   f 1
>>>>>   p proto
>>>>>
>>>>> Regards,
>>>>>
>>>>> Bogdan-Andrei Iancu
>>>>>
>>>>> OpenSIPS Founder and Developer
>>>>> https://www.opensips-solutions.com
>>>>> https://www.siphub.com
>>>>>
>>>>> On 08.12.2023 16:30, Neven Grzancic wrote:
>>>>>> Hi Bogdan,
>>>>>>
>>>>>> good hit on the apport service - thanks!
>>>>>>
>>>>>> here's the trace we get from one such crash:
>>>>>>
>>>>>> [New LWP 1130]
>>>>>> [Thread debugging using libthread_db enabled]
>>>>>> Using host libthread_db library 
>>>>>> "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>>>>> Core was generated by `/usr/sbin/opensips -P 
>>>>>> /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg'.
>>>>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>>>>> #0  0x0000000000000000 in ?? ()
>>>>>> (gdb) bt full
>>>>>> #0  0x0000000000000000 in ?? ()
>>>>>> No symbol table info available.
>>>>>> #1  0x00007f334e06aad5 in acc_aaa_cdrs (dlg=<optimized out>, 
>>>>>> msg=<optimized out>, ctx=0x7f334fcc52c8)
>>>>>>     at /build/opensips-3.4.2/modules/acc/acc.c:965
>>>>>>         i = <optimized out>
>>>>>>         j = <optimized out>
>>>>>>         ret = 6
>>>>>>         res = -1
>>>>>>         nr_leg_vals = <optimized out>
>>>>>>         start_time = {tv_sec = 1702044564, tv_usec = 417047}
>>>>>>         core_s = {s = 0x7f33705e9878 "\006", len = 101}
>>>>>>         leg_s = {s = 0x0, len = <optimized out>}
>>>>>>         extra_s = {s = 0x0, len = <optimized out>}
>>>>>>         send = 0x0
>>>>>>         offset = <optimized out>
>>>>>>         av_type = 32563
>>>>>>         r_stat = <optimized out>
>>>>>>         locked = 0
>>>>>>         duration = 1338791072
>>>>>>         ms_duration = 0
>>>>>>         extra = <optimized out>
>>>>>>         error = <optimized out>
>>>>>>         __FUNCTION__ = "acc_aaa_cdrs"
>>>>>> #2  0x00007f334e078ade in acc_cdr_cb (t=0x0, type=5, 
>>>>>> ps=0x7ffdb12e09e0)
>>>>>>     at /build/opensips-3.4.2/modules/acc/acc_logic.c:986
>>>>>>         ctx = 0x7f334fcc52c8
>>>>>>         dlg = 0x7f334fcc54e0
>>>>>>         __FUNCTION__ = "acc_cdr_cb"
>>>>>> [...]
>>>>>>
>>>>>>
>>>>>> On 08.12.23 15:16, Bogdan-Andrei Iancu wrote:
>>>>>>> Simon, I do not need the corefile, usually it is huge - as per 
>>>>>>> web instructions (see the prev link), extract the backtrace 
>>>>>>> (using gdb) and share it with me.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Bogdan-Andrei Iancu
>>>>>>>
>>>>>>> OpenSIPS Founder and Developer
>>>>>>> https://www.opensips-solutions.com
>>>>>>> https://www.siphub.com
>>>>>>>
>>>>>>> On 08.12.2023 16:13, Simon Gajski wrote:
>>>>>>>> Hi Bogdan
>>>>>>>>
>>>>>>>> you were right
>>>>>>>> we have the core file now
>>>>>>>>
>>>>>>>> Please let me know where to send it (gzipped is approx 2MB)
>>>>>>>>
>>>>>>>>
>>>>>>>> BR
>>>>>>>> Simon
>>>>>>>>
>>>>>>>> Bogdan-Andrei Iancu je 08.12.2023 ob 14:17 napisal:
>>>>>>>>> Hi Simon,
>>>>>>>>>
>>>>>>>>> Maybe you have some apport service running on the machine, 
>>>>>>>>> moving the core file.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>>
>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>> https://www.opensips-solutions.com
>>>>>>>>> https://www.siphub.com
>>>>>>>>>
>>>>>>>>> On 08.12.2023 13:35, Neven Grzancic wrote:
>>>>>>>>>> Dear Bogdan,
>>>>>>>>>>
>>>>>>>>>> we tried following 
>>>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash and 
>>>>>>>>>> trying different things, and even though the syslog shows 
>>>>>>>>>> that the core file was dumped:
>>>>>>>>>>
>>>>>>>>>> Dec  8 12:25:13 sbc2 /usr/sbin/opensips[4363]: 
>>>>>>>>>> CRITICAL:core:sig_usr: segfault in process pid: 4363, id: 7
>>>>>>>>>> Dec  8 12:25:13 sbc2 kernel: [ 3394.269733] opensips[4363]: 
>>>>>>>>>> segfault at 0 ip 0000000000000000 sp 00007ffdc458f6a8 error 
>>>>>>>>>> 14 in opensips[55816fbd0000+1f000]
>>>>>>>>>> Dec  8 12:25:18 sbc2 mariadbd[922]: 2023-12-08 12:25:18 400 
>>>>>>>>>> [Warning] Aborted connection 400 to db: 'opensips' user: 
>>>>>>>>>> 'opensips' host: 'localhost' (Got an error reading 
>>>>>>>>>> communication packets)
>>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>>> INFO:core:handle_sigs: child process 4363 exited by a signal 11
>>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4356]: 
>>>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4359]: 
>>>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>>>> Dec  8 12:25:18 sbc2 /usr/sbin/opensips[4360]: 
>>>>>>>>>> INFO:core:sig_usr: signal 15 received
>>>>>>>>>>
>>>>>>>>>> the core does not get generated, or at least not in the 
>>>>>>>>>> directory provided via options at runtime (-w /tmp). The 
>>>>>>>>>> issue is always repeatable (the daemon crashes after every 
>>>>>>>>>> finished call), if there are more active calls at the moment 
>>>>>>>>>> of the crash, whose calls remain active and proceed normally 
>>>>>>>>>> until termination (which again causes a crash). We also tried 
>>>>>>>>>> enabling debug mode, but in that case the process does not 
>>>>>>>>>> start successfully and runs into a timeout. In any case, any 
>>>>>>>>>> additional help or suggestion on how to successfully generate 
>>>>>>>>>> the core dump would be much appreciated, as we seem to have 
>>>>>>>>>> ran into a wall here...
>>>>>>>>>>
>>>>>>>>>> On 08.12.23 12:26, Simon Gajski wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -------- Posredovano sporočilo --------
>>>>>>>>>>> Zadeva:     Re: [OpenSIPS-Users] opensips is restarting 
>>>>>>>>>>> after call is finished
>>>>>>>>>>> Datum:     Thu, 7 Dec 2023 17:52:37 +0200
>>>>>>>>>>> Od:     Bogdan-Andrei Iancu <bogdan at opensips.org>
>>>>>>>>>>> Za:     Simon Gajski <simon at softnet.si>, OpenSIPS users 
>>>>>>>>>>> mailling list <users at lists.opensips.org>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi Simon,
>>>>>>>>>>>
>>>>>>>>>>> Well, the log is very self explanatory:
>>>>>>>>>>> Dec 7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>>> INFO:core:handle_sigs: child process 28495 exited by a 
>>>>>>>>>>> signal 11
>>>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>>> INFO:core:handle_sigs: core was generated
>>>>>>>>>>> Dec  7 15:59:47 sbc2 /usr/sbin/opensips[28488]: 
>>>>>>>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>>>>>>>>
>>>>>>>>>>> Or shortly, you opensips just crashed :). So see 
>>>>>>>>>>> https://opensips.org/Documentation/TroubleShooting-Crash for 
>>>>>>>>>>> how to report further.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>>>>
>>>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>>>> https://www.opensips-solutions.com
>>>>>>>>>>> https://www.siphub.com
>>>>>>>>>>>
>>>>>>>>>>> On 07.12.2023 17:17, Simon Gajski via Users wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi
>>>>>>>>>>>>
>>>>>>>>>>>> we are running opensips 3.4.2
>>>>>>>>>>>> on Ubuntu 22.04.3 LTS
>>>>>>>>>>>> and also use RTPengine Version: 10.5.0.0+0~mr10.5.0.0 
>>>>>>>>>>>> git-master-74075f63
>>>>>>>>>>>>
>>>>>>>>>>>> Opensips acts as SBC with RTP engine enabled.
>>>>>>>>>>>>
>>>>>>>>>>>> Calls are working fine, however after each call is 
>>>>>>>>>>>> finished, bellow action happens.
>>>>>>>>>>>>
>>>>>>>>>>>> We had same problem with opensips 3.2 and Ubuntu 20. So we 
>>>>>>>>>>>> did upgrade to latest stable release, and it is the same.
>>>>>>>>>>>>
>>>>>>>>>>>> Is this opensips script configuration issue or a bug? And 
>>>>>>>>>>>> how could I fix it?
>>>>>>>>>>>>
>>>>>>>>>>>> [....]
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks for all tips.
>>>>>>>>>>>>
>>>>>>>>>>>> BR
>>>>>>>>>>>> Simon
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231211/a87290b7/attachment-0001.html>

From spanda at 3clogic.com  Tue Dec 12 08:48:02 2023
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 12 Dec 2023 14:18:02 +0530
Subject: [OpenSIPS-Users] Facing some issue with opensips while
	configuration .
Message-ID: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>

HI All ,

I have RedHat machine : VERSION_ID="8.7"
I am trying to install opensips 2.2 .

I have installed mysql
Name         : mysql-server : Version      : 8.0.32
Name         : mysql-devel : Version      : 8.0.32
Name         : mysql-libs: Version      : 8.0.32

*These are all installed still when I am running make command on opensips
its giving some error while building mysql module . *

make[1]: Entering directory '/home/ec2-user/opensips-2.2/modules/db_mysql'
Compiling row.c
Compiling my_con.c
In file included from row.c:29:
my_con.h:36:2: error: unknown type name ‘my_bool’
  my_bool null;
  ^~~~~~~

Is there any compatibility issue of opensips with mysql ? What version of
mysql I should use ?

*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/20231212/fc4319e6/attachment.html>

From bogdan at opensips.org  Tue Dec 12 09:39:37 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 12 Dec 2023 11:39:37 +0200
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
Message-ID: <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>

Hi Sasmita?

Why the old 2.2? Try 3.4 version, this may be fixed.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 12.12.2023 10:48, Sasmita Panda wrote:
> HI All ,
>
> I have RedHat machine : VERSION_ID="8.7"
> I am trying to install opensips 2.2 .
>
> I have installed mysql
> Name         : mysql-server : Version      : 8.0.32
> Name         : mysql-devel : Version    : 8.0.32
> Name         : mysql-libs: Version  : 8.0.32*/
> /*
> */
> /*
> */These are all installed still when I am running make command on 
> opensips its giving some error while building mysql module . /*
> */
> /*
> make[1]: Entering directory '/home/ec2-user/opensips-2.2/modules/db_mysql'
> Compiling row.c
> Compiling my_con.c
> In file included from row.c:29:
> my_con.h:36:2: error: unknown type name ‘my_bool’
>   my_bool null;
>   ^~~~~~~
>
> Is there any compatibility issue of opensips with mysql ? What version 
> of mysql I should use ?
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
> _______________________________________________
> 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/20231212/bda2de67/attachment.html>

From rvg at rvgeerligs.nl  Tue Dec 12 12:22:32 2023
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Tue, 12 Dec 2023 12:22:32 +0000
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
References: <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
Message-ID: <eae29285eb091b29e1875e6447e9b9c7db8bdabb@rvgeerligs.nl>

Hi,

Your OCP OpenSIPS Control Panel will not work! Please downgrade to version 7.4.

Ronald Geerligs



December 12, 2023 at 6:39 AM, "Bogdan-Andrei Iancu" <bogdan at opensips.org> wrote:


> 
> Hi Sasmita?
>  
>  Why the old 2.2? Try 3.4 version, this may be fixed.
>  
>  Regards,
>   
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>  https://www.opensips-solutions.com https://www.opensips-solutions.com/ 
>  https://www.siphub.com https://www.siphub.com/ 
>  
> On 12.12.2023 10:48, Sasmita Panda wrote: 
>  
> 
> > 
> > HI All ,  
> >  
> >  
> > I have RedHat machine : VERSION_ID="8.7" 
> >  
> > I am trying to install opensips 2.2 .
> >  
> >  
> >  
> > I have installed mysql 
> >  
> > Name         : mysql-server : Version      : 8.0.32
> >  
> >  
> >  
> >  
> >  
> > Name         : mysql-devel : Version      : 8.0.32 
> >  
> > Name         : mysql-libs: Version      : 8.0.32 
> >  
> >  
> >  
> > **These are all installed still when I am running make command on opensips its giving some error while building mysql module . **
> >  
> >  
> >  
> > make[1]: Entering directory '/home/ec2-user/opensips-2.2/modules/db_mysql'
> >  Compiling row.c
> >  Compiling my_con.c
> >  In file included from row.c:29:
> >  my_con.h:36:2: error: unknown type name ‘my_bool’
> >    my_bool null;
> >    ^~~~~~~ 
> > 
> >  
> >  
> >  
> > Is there any compatibility issue of opensips with mysql ? What version of mysql I should use ?
> >  
> >  
> >  
> > **Thanks & Regards** 
> > *Sasmita Panda*
> >  
> > *Senior Network Testing and Software Engineer*
> >  
> > *3CLogic , ph:07827611765*
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> >  
> >  
> > _______________________________________________
> > 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/20231212/b7cd217d/attachment.html>

From spanda at 3clogic.com  Tue Dec 12 12:37:48 2023
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 12 Dec 2023 18:07:48 +0530
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <eae29285eb091b29e1875e6447e9b9c7db8bdabb@rvgeerligs.nl>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <eae29285eb091b29e1875e6447e9b9c7db8bdabb@rvgeerligs.nl>
Message-ID: <CALf-Q45tjn875OAgF58bv=dw+yj0CqDrVBuG4xPs0y3CjFBEog@mail.gmail.com>

I am not installing the opensips control panel . I am trying opensips-cli .
I hope both are different .  The control panel provides the GUI here. I
don't need that .

I am getting the above error while connecting to the cli interface .

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


On Tue, Dec 12, 2023 at 5:52 PM <rvg at rvgeerligs.nl> wrote:

> Hi,
>
> Your OCP OpenSIPS Control Panel will not work! Please downgrade to version
> 7.4.
>
> Ronald Geerligs
>
> December 12, 2023 at 6:39 AM, "Bogdan-Andrei Iancu" <bogdan at opensips.org
> <bogdan at opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>>
> wrote:
>
> Hi Sasmita?
>
> Why the old 2.2? Try 3.4 version, this may be fixed.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 12.12.2023 10:48, Sasmita Panda wrote:
>
> HI All ,
> I have RedHat machine : VERSION_ID="8.7"
> I am trying to install opensips 2.2 .
> I have installed mysql
> Name         : mysql-server : Version      : 8.0.32
> Name         : mysql-devel : Version      : 8.0.32
> Name         : mysql-libs: Version      : 8.0.32
> *These are all installed still when I am running make command on opensips
> its giving some error while building mysql module . *
> make[1]: Entering directory '/home/ec2-user/opensips-2.2/modules/db_mysql'
> Compiling row.c
> Compiling my_con.c
> In file included from row.c:29:
> my_con.h:36:2: error: unknown type name ‘my_bool’
>   my_bool null;
>   ^~~~~~~
> Is there any compatibility issue of opensips with mysql ? What version of
> mysql I should use ?
> *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/20231212/68e6815f/attachment.html>

From bogdan at opensips.org  Tue Dec 12 14:42:01 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 12 Dec 2023 16:42:01 +0200
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q44Zm3-2sfDMG8BLPY635=b4_EPMEsmOsE5LKe06kY7bdw@mail.gmail.com>
 <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
Message-ID: <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>

What is the exact version of Python you have?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 12.12.2023 13:42, Sasmita Panda wrote:
> I am trying to install opensips-cli on the same version of linux but 
> facing some issue while connecting to the cli interface .
>
>
> Steps I have followed :
> sudo yum install python3 python3-pip python3-devel gcc
> sudo yum install  python3-sqlalchemy python3-pyOpenSSL
> git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
> cd /root/src/opensips-cli/
> sudo python3 setup.py install clean
>
> */usr/local/bin/opensips-cli
> Traceback (most recent call last):
>   File "/usr/local/bin/opensips-cli", line 4, in <module>
> __import__('pkg_resources').run_script('opensipscli==0.2.0', 
> 'opensips-cli')
>   File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", 
> line 654, in run_script
>     self.require(requires)[0].run_script(script_name, ns)
>   File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", 
> line 1434, in run_script
>     exec(code, namespace, namespace)
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli", 
> line 3, in <module>
>     from opensipscli import main
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py", 
> line 22, in <module>
>     from opensipscli import cli, defaults, version
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py", 
> line 32, in <module>
>     from opensipscli.modules import *
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py", 
> line 24, in <module>
>     __import__(modname)
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py", 
> line 23, in <module>
>     from opensipscli.db import (
>   File 
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py", 
> line 37, in <module>
>     import sqlalchemy_utils
>   File 
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py", 
> line 1, in <module>
>     from .aggregates import aggregated  # noqa
>   File 
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py", 
> line 374, in <module>
>     from .compat import _select_args, get_scalar_subquery
>   File 
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py", 
> line 7, in <module>
>     from importlib_metadata import metadata
>   File 
> "/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py", 
> line 7, in <module>
>     import zipp
>   File 
> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py", 
> line 9, in <module>
>     from .py310compat import text_encoding
>   File 
> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py", 
> line 5
>     def _text_encoding(encoding, stacklevel=2, /):  # pragma: no cover*
>
>
> How should I proceed ?
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Tue, Dec 12, 2023 at 4:30 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>     Thanks for the reply . I tried opensips 3.2 and the issue didn't
>     come .  opensips 3.4 we have not tested yet . Will do that soon .
>
>     Thank you once again .
>
>     */Thanks & Regards/*
>     /Sasmita Panda/
>     /Senior Network Testing and Software Engineer/
>     /3CLogic , ph:07827611765/
>
>
>     On Tue, Dec 12, 2023 at 3:09 PM Bogdan-Andrei Iancu
>     <bogdan at opensips.org> wrote:
>
>         Hi Sasmita?
>
>         Why the old 2.2? Try 3.4 version, this may be fixed.
>
>         Regards,
>
>         Bogdan-Andrei Iancu
>
>         OpenSIPS Founder and Developer
>            https://www.opensips-solutions.com
>            https://www.siphub.com
>
>         On 12.12.2023 10:48, Sasmita Panda wrote:
>>         HI All ,
>>
>>         I have RedHat machine : VERSION_ID="8.7"
>>         I am trying to install opensips 2.2 .
>>
>>         I have installed mysql
>>         Name         : mysql-server : Version      : 8.0.32
>>         Name         : mysql-devel : Version      : 8.0.32
>>         Name         : mysql-libs: Version      : 8.0.32*/
>>         /*
>>         */
>>         /*
>>         */These are all installed still when I am running make
>>         command on opensips its giving some error while building
>>         mysql module . /*
>>         */
>>         /*
>>         make[1]: Entering directory
>>         '/home/ec2-user/opensips-2.2/modules/db_mysql'
>>         Compiling row.c
>>         Compiling my_con.c
>>         In file included from row.c:29:
>>         my_con.h:36:2: error: unknown type name ‘my_bool’
>>           my_bool null;
>>           ^~~~~~~
>>
>>         Is there any compatibility issue of opensips with mysql ?
>>         What version of mysql I should use ?
>>
>>         */Thanks & Regards/*
>>         /Sasmita Panda/
>>         /Senior Network Testing and Software Engineer/
>>         /3CLogic , ph:07827611765/
>>
>>         _______________________________________________
>>         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/20231212/4460e117/attachment-0001.html>

From spanda at 3clogic.com  Wed Dec 13 06:45:29 2023
From: spanda at 3clogic.com (Sasmita Panda)
Date: Wed, 13 Dec 2023 12:15:29 +0530
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q44Zm3-2sfDMG8BLPY635=b4_EPMEsmOsE5LKe06kY7bdw@mail.gmail.com>
 <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
 <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>
Message-ID: <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>

python3 -V
Python 3.6.8

This is the exact version I have .

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


On Tue, Dec 12, 2023 at 8:12 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> What is the exact version of Python you have?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 12.12.2023 13:42, Sasmita Panda wrote:
>
> I am trying to install opensips-cli on the same version of linux but
> facing some issue while connecting to the cli interface .
>
>
> Steps I have followed :
> sudo yum install python3 python3-pip python3-devel gcc
> sudo yum install  python3-sqlalchemy python3-pyOpenSSL
> git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
> cd /root/src/opensips-cli/
> sudo python3 setup.py install clean
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> */usr/local/bin/opensips-cli Traceback (most recent call last):   File
> "/usr/local/bin/opensips-cli", line 4, in <module>
> __import__('pkg_resources').run_script('opensipscli==0.2.0',
> 'opensips-cli')   File
> "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 654, in
> run_script     self.require(requires)[0].run_script(script_name, ns)   File
> "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1434, in
> run_script     exec(code, namespace, namespace)   File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
> line 3, in <module>     from opensipscli import main   File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py",
> line 22, in <module>     from opensipscli import cli, defaults, version
> File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py",
> line 32, in <module>     from opensipscli.modules import *   File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py",
> line 24, in <module>     __import__(modname)   File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py",
> line 23, in <module>     from opensipscli.db import (   File
> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py",
> line 37, in <module>     import sqlalchemy_utils   File
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py",
> line 1, in <module>     from .aggregates import aggregated  # noqa   File
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py",
> line 374, in <module>     from .compat import _select_args,
> get_scalar_subquery   File
> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py",
> line 7, in <module>     from importlib_metadata import metadata   File
> "/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py",
> line 7, in <module>     import zipp   File
> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py",
> line 9, in <module>     from .py310compat import text_encoding   File
> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py",
> line 5     def _text_encoding(encoding, stacklevel=2, /):  # pragma: no
> cover*
>
>
> How should I proceed ?
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Tue, Dec 12, 2023 at 4:30 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>
>> Thanks for the reply . I tried opensips 3.2 and the issue didn't come .
>> opensips 3.4 we have not tested yet . Will do that soon .
>>
>> Thank you once again .
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
>> On Tue, Dec 12, 2023 at 3:09 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi Sasmita?
>>>
>>> Why the old 2.2? Try 3.4 version, this may be fixed.
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>>   https://www.siphub.com
>>>
>>> On 12.12.2023 10:48, Sasmita Panda wrote:
>>>
>>> HI All ,
>>>
>>> I have RedHat machine : VERSION_ID="8.7"
>>> I am trying to install opensips 2.2 .
>>>
>>> I have installed mysql
>>> Name         : mysql-server : Version      : 8.0.32
>>> Name         : mysql-devel : Version      : 8.0.32
>>> Name         : mysql-libs: Version      : 8.0.32
>>>
>>> *These are all installed still when I am running make command on
>>> opensips its giving some error while building mysql module . *
>>>
>>> make[1]: Entering directory
>>> '/home/ec2-user/opensips-2.2/modules/db_mysql'
>>> Compiling row.c
>>> Compiling my_con.c
>>> In file included from row.c:29:
>>> my_con.h:36:2: error: unknown type name ‘my_bool’
>>>   my_bool null;
>>>   ^~~~~~~
>>>
>>> Is there any compatibility issue of opensips with mysql ? What version
>>> of mysql I should use ?
>>>
>>> *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/20231213/25ed2c75/attachment.html>

From bogdan at opensips.org  Wed Dec 13 07:57:50 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 13 Dec 2023 09:57:50 +0200
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q44Zm3-2sfDMG8BLPY635=b4_EPMEsmOsE5LKe06kY7bdw@mail.gmail.com>
 <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
 <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>
 <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>
Message-ID: <fa1120dd-6218-458a-abb0-133cd491bece@opensips.org>

Please just open a report here 
https://github.com/OpenSIPS/opensips-cli/issues

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 13.12.2023 08:45, Sasmita Panda wrote:
> python3 -V
> Python 3.6.8
>
> This is the exact version I have .
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Tue, Dec 12, 2023 at 8:12 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     What is the exact version of Python you have?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 12.12.2023 13:42, Sasmita Panda wrote:
>>     I am trying to install opensips-cli on the same version of linux
>>     but facing some issue while connecting to the cli interface .
>>
>>
>>     Steps I have followed :
>>     sudo yum install python3 python3-pip python3-devel gcc
>>     sudo yum install  python3-sqlalchemy python3-pyOpenSSL
>>     git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
>>     cd /root/src/opensips-cli/
>>     sudo python3 setup.py install clean
>>
>>     */usr/local/bin/opensips-cli
>>     Traceback (most recent call last):
>>       File "/usr/local/bin/opensips-cli", line 4, in <module>
>>     __import__('pkg_resources').run_script('opensipscli==0.2.0',
>>     'opensips-cli')
>>       File
>>     "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
>>     line 654, in run_script
>>     self.require(requires)[0].run_script(script_name, ns)
>>       File
>>     "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
>>     line 1434, in run_script
>>         exec(code, namespace, namespace)
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
>>     line 3, in <module>
>>         from opensipscli import main
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py",
>>     line 22, in <module>
>>         from opensipscli import cli, defaults, version
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py",
>>     line 32, in <module>
>>         from opensipscli.modules import *
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py",
>>     line 24, in <module>
>>         __import__(modname)
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py",
>>     line 23, in <module>
>>         from opensipscli.db import (
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py",
>>     line 37, in <module>
>>         import sqlalchemy_utils
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py",
>>     line 1, in <module>
>>         from .aggregates import aggregated  # noqa
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py",
>>     line 374, in <module>
>>         from .compat import _select_args, get_scalar_subquery
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py",
>>     line 7, in <module>
>>         from importlib_metadata import metadata
>>       File
>>     "/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py",
>>     line 7, in <module>
>>         import zipp
>>       File
>>     "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py",
>>     line 9, in <module>
>>         from .py310compat import text_encoding
>>       File
>>     "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py",
>>     line 5
>>         def _text_encoding(encoding, stacklevel=2, /):  # pragma: no
>>     cover*
>>
>>
>>     How should I proceed ?
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Senior Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>>
>>
>>     On Tue, Dec 12, 2023 at 4:30 PM Sasmita Panda
>>     <spanda at 3clogic.com> wrote:
>>
>>         Thanks for the reply . I tried opensips 3.2 and the issue
>>         didn't come .  opensips 3.4 we have not tested yet . Will do
>>         that soon .
>>
>>         Thank you once again .
>>
>>         */Thanks & Regards/*
>>         /Sasmita Panda/
>>         /Senior Network Testing and Software Engineer/
>>         /3CLogic , ph:07827611765/
>>
>>
>>         On Tue, Dec 12, 2023 at 3:09 PM Bogdan-Andrei Iancu
>>         <bogdan at opensips.org> wrote:
>>
>>             Hi Sasmita?
>>
>>             Why the old 2.2? Try 3.4 version, this may be fixed.
>>
>>             Regards,
>>
>>             Bogdan-Andrei Iancu
>>
>>             OpenSIPS Founder and Developer
>>                https://www.opensips-solutions.com
>>                https://www.siphub.com
>>
>>             On 12.12.2023 10:48, Sasmita Panda wrote:
>>>             HI All ,
>>>
>>>             I have RedHat machine : VERSION_ID="8.7"
>>>             I am trying to install opensips 2.2 .
>>>
>>>             I have installed mysql
>>>             Name         : mysql-server : Version    : 8.0.32
>>>             Name         : mysql-devel : Version      : 8.0.32
>>>             Name         : mysql-libs: Version      : 8.0.32*/
>>>             /*
>>>             */
>>>             /*
>>>             */These are all installed still when I am running make
>>>             command on opensips its giving some error while building
>>>             mysql module . /*
>>>             */
>>>             /*
>>>             make[1]: Entering directory
>>>             '/home/ec2-user/opensips-2.2/modules/db_mysql'
>>>             Compiling row.c
>>>             Compiling my_con.c
>>>             In file included from row.c:29:
>>>             my_con.h:36:2: error: unknown type name ‘my_bool’
>>>               my_bool null;
>>>               ^~~~~~~
>>>
>>>             Is there any compatibility issue of opensips with mysql
>>>             ? What version of mysql I should use ?
>>>
>>>             */Thanks & Regards/*
>>>             /Sasmita Panda/
>>>             /Senior Network Testing and Software Engineer/
>>>             /3CLogic , ph:07827611765/
>>>
>>>             _______________________________________________
>>>             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/20231213/1c544b55/attachment-0001.html>

From rvg at rvgeerligs.nl  Fri Dec 15 19:38:57 2023
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Fri, 15 Dec 2023 19:38:57 +0000
Subject: [OpenSIPS-Users] opensips and NAT
Message-ID: <df5dbe863bf2e3ffd6d70adef11d7f44368224d7@rvgeerligs.nl>

Hi

I use opensips 3.4 and I have NAT problems with 2 devices behind the same NAT (called party hears nothing).
The A party is softphone on iPhone (linphone) the B (called)party is Polycom310. The other way around works (Polycom calls linphone).

Actually I tested this in two different NAT locations. 
The first location repeatedly works. The second location gives the problem. Both locations have changing public IP addresses and DHCP on 192.168 network.
Both locations have one FX number assigned to them. No SIP ALG active. 

I use nat_uac_test(diff-ip-src-contact).

There is a table:
1.5.5.  nat_uac_test(flags)
Tries to guess if client's request originated behind a nat. The parameter determines what heuristics is used.

Meaning of the flags (string) parameter is as follows:

private-contact - (old 1 flag) Contact header field is searched for occurrence of RFC1918 / RFC6598 addresses.

diff-ip-src-via - (old 2 flag) the "received" test is used: address in Via is compared against source IP address of signaling

private-via - (old 4 flag) Top Most VIA is searched for occurrence of RFC1918 / RFC6598 addresses

private-sdp - (old 8 flag) SDP is searched for occurrence of RFC1918 / RFC6598 addresses

diff-port-src-via - (old 16 flag) test if the source port is different from the port in Via

diff-ip-src-contact - (old 32 flag) address in Contact is compared against source IP address of signaling. <<<<

diff-port-src-contact - (old 64 flag) Port in Contact is compared against source port of signaling <<<<

carrier-grade-nat - (old 128 flag) also include RFC 6333 addresses in the checks for ct, via and sdp flags.

A CSV of the above flags can be provided, the test returns true if any of the tests identified a NAT.


Currently I use old flag 32.

I read that using the equivalent of 19 might help but I dont see that in the table.


Any advice is appreciated.

Regards,


Ronald Geerligs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231215/3058b054/attachment.html>

From rvg at rvgeerligs.nl  Fri Dec 15 21:05:12 2023
From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl)
Date: Fri, 15 Dec 2023 21:05:12 +0000
Subject: [OpenSIPS-Users] opensips and NAT
In-Reply-To: <df5dbe863bf2e3ffd6d70adef11d7f44368224d7@rvgeerligs.nl>
References: <df5dbe863bf2e3ffd6d70adef11d7f44368224d7@rvgeerligs.nl>
Message-ID: <8ce7ab40f00ea0a4b9ad7a6dabbe88e990feb499@rvgeerligs.nl>

Hi,

Should I try something like

 nat_uac_test(diff-ip-src-contact || private-contact || diff-ip-src-via || diff-port-src-via)?

Any ideas?

Regards,

Ronald




December 15, 2023 at 4:38 PM, rvg at rvgeerligs.nl wrote:


> 
> Hi
> 
> I use opensips 3.4 and I have NAT problems with 2 devices behind the same NAT (called party hears nothing).
> The A party is softphone on iPhone (linphone) the B (called)party is Polycom310. The other way around works (Polycom calls linphone).
> 
> Actually I tested this in two different NAT locations. 
> The first location repeatedly works. The second location gives the problem. Both locations have changing public IP addresses and DHCP on 192.168 network.
> Both locations have one FX number assigned to them. No SIP ALG active. 
> 
> I use nat_uac_test(diff-ip-src-contact).
> 
> There is a table:
> 1.5.5.  nat_uac_test(flags)
> Tries to guess if client's request originated behind a nat. The parameter determines what heuristics is used.
> 
> Meaning of the flags (string) parameter is as follows:
> 
> private-contact - (old 1 flag) Contact header field is searched for occurrence of RFC1918 / RFC6598 addresses.
> 
> diff-ip-src-via - (old 2 flag) the "received" test is used: address in Via is compared against source IP address of signaling
> 
> private-via - (old 4 flag) Top Most VIA is searched for occurrence of RFC1918 / RFC6598 addresses
> 
> private-sdp - (old 8 flag) SDP is searched for occurrence of RFC1918 / RFC6598 addresses
> 
> diff-port-src-via - (old 16 flag) test if the source port is different from the port in Via
> 
> diff-ip-src-contact - (old 32 flag) address in Contact is compared against source IP address of signaling. <<<<
> 
> diff-port-src-contact - (old 64 flag) Port in Contact is compared against source port of signaling <<<<
> 
> carrier-grade-nat - (old 128 flag) also include RFC 6333 addresses in the checks for ct, via and sdp flags.
> 
> A CSV of the above flags can be provided, the test returns true if any of the tests identified a NAT.
> 
> Currently I use old flag 32.
> 
> I read that using the equivalent of 19 might help but I dont see that in the table.
> 
> Any advice is appreciated.
> 
> Regards,
> 
> Ronald Geerligs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231215/8995e1d7/attachment.html>

From bogdan at opensips.org  Mon Dec 18 10:26:13 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 18 Dec 2023 12:26:13 +0200
Subject: [OpenSIPS-Users] [WG-IMS] Technical Requirements - RFC
In-Reply-To: <b6d8d1a3-792e-423e-9dd1-1cbb4d8271eb@opensips.org>
References: <b6d8d1a3-792e-423e-9dd1-1cbb4d8271eb@opensips.org>
Message-ID: <13ce34f7-cf46-44c7-8d5c-51d5125a23ed@opensips.org>

Hi all,

A quick reminder on this, as we should try to wrap up this stage by the 
end of this week (before the holiday). This will help us to stay on 
tracks with the 3.5 release.

So, if you have any input on the tech requirements topic, please 
contribute :)

Thanks and regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 12.12.2023 12:56, Bogdan-Andrei Iancu wrote:
> Hi all,
>
> As the scoping process was successfully completed last week (see the 
> conclusions here 
> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Scope>), 
> the next milestone is to explore the technical details and 
> implications of each IMS component to be addressed.
> Here we are heavily relying on the input (as expertise) from people 
> already involved in the IMS world, so please contribute as much as 
> possible :).
>
> A first list of technical requirements is already compiled here 
> <https://github.com/OpenSIPS/opensips/wiki/IMS-Working-Group-Requirements> 
> - I tried to group the requirements around the components we have 
> scoped as to be addressed.
>
> Now, what we need to do here:
>
> * verify and complete the list of requirements, to be sure nothing is 
> missing in order to properly implement the IMS support.
>
> * comments or details about the items on the list are welcome - as 
> many details/info as better
>
> * a "weak" item on the list is the Presence server - even if the SIP 
> flows are clear, what is not yet 100% clear (at least for me) is what 
> "event"'s are needed here - for sure the "presence" and as far as I 
> heard the "reg" (RFC3680). But anyone can throw more light here ?
>
>
> Thanks and regards,
> -- 
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
>
> _______________________________________________
> Wg-ims mailing list
> Wg-ims at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231218/1a49ad49/attachment.html>

From liviu at opensips.org  Mon Dec 18 18:49:18 2023
From: liviu at opensips.org (Liviu Chircu)
Date: Mon, 18 Dec 2023 20:49:18 +0200
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q44Zm3-2sfDMG8BLPY635=b4_EPMEsmOsE5LKe06kY7bdw@mail.gmail.com>
 <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
 <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>
 <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>
Message-ID: <84295952-474c-46db-8f8c-2008c0350954@opensips.org>

Hi folks,

An explanation + solution for this specific CLI issue related to *Python 
3.6* + the *zipp* package version can be found on the CLI tracker, part 
of issue #113 
<https://github.com/OpenSIPS/opensips-cli/issues/113#issuecomment-1861311868>

Hope this helps,

On 13.12.2023 08:45, Sasmita Panda wrote:
> python3 -V
> Python 3.6.8
>
> This is the exact version I have .
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Tue, Dec 12, 2023 at 8:12 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     What is the exact version of Python you have?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 12.12.2023 13:42, Sasmita Panda wrote:
>>     I am trying to install opensips-cli on the same version of linux
>>     but facing some issue while connecting to the cli interface .
>>
>>
>>     Steps I have followed :
>>     sudo yum install python3 python3-pip python3-devel gcc
>>     sudo yum install  python3-sqlalchemy python3-pyOpenSSL
>>     git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
>>     cd /root/src/opensips-cli/
>>     sudo python3 setup.py install clean
>>
>>     */usr/local/bin/opensips-cli
>>     Traceback (most recent call last):
>>       File "/usr/local/bin/opensips-cli", line 4, in <module>
>>     __import__('pkg_resources').run_script('opensipscli==0.2.0',
>>     'opensips-cli')
>>       File
>>     "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
>>     line 654, in run_script
>>     self.require(requires)[0].run_script(script_name, ns)
>>       File
>>     "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
>>     line 1434, in run_script
>>         exec(code, namespace, namespace)
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
>>     line 3, in <module>
>>         from opensipscli import main
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py",
>>     line 22, in <module>
>>         from opensipscli import cli, defaults, version
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py",
>>     line 32, in <module>
>>         from opensipscli.modules import *
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py",
>>     line 24, in <module>
>>         __import__(modname)
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py",
>>     line 23, in <module>
>>         from opensipscli.db import (
>>       File
>>     "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py",
>>     line 37, in <module>
>>         import sqlalchemy_utils
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py",
>>     line 1, in <module>
>>         from .aggregates import aggregated  # noqa
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py",
>>     line 374, in <module>
>>         from .compat import _select_args, get_scalar_subquery
>>       File
>>     "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py",
>>     line 7, in <module>
>>         from importlib_metadata import metadata
>>       File
>>     "/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py",
>>     line 7, in <module>
>>         import zipp
>>       File
>>     "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py",
>>     line 9, in <module>
>>         from .py310compat import text_encoding
>>       File
>>     "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py",
>>     line 5
>>         def _text_encoding(encoding, stacklevel=2, /):  # pragma: no
>>     cover*
>>
>>
>>     How should I proceed ?
>>
>>     */Thanks & Regards/*
>>     /Sasmita Panda/
>>     /Senior Network Testing and Software Engineer/
>>     /3CLogic , ph:07827611765/
>

-- 
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp, Nov 6-17 |www.opensips.org/training
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231218/2480aafd/attachment.html>

From spanda at 3clogic.com  Tue Dec 19 05:33:10 2023
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 19 Dec 2023 11:03:10 +0530
Subject: [OpenSIPS-Users] Facing some issue with opensips while
 configuration .
In-Reply-To: <84295952-474c-46db-8f8c-2008c0350954@opensips.org>
References: <CALf-Q45e4e-iCcSXvjoY74LUNhQthwF6x0am_7EU3HnpmgQ2mg@mail.gmail.com>
 <a5ba21c6-b30b-4f03-a095-169700b8bb7f@opensips.org>
 <CALf-Q44Zm3-2sfDMG8BLPY635=b4_EPMEsmOsE5LKe06kY7bdw@mail.gmail.com>
 <CALf-Q47GaiY=7H7raRzJCz0QP059VqYF7hQFR2WwBaTumYyGig@mail.gmail.com>
 <edb7d866-bd14-47d6-92df-883de09d5b61@opensips.org>
 <CALf-Q44t40ZFk4CqTiTYDGVEd57jahPitLThSH56mZQ9GnPK2g@mail.gmail.com>
 <84295952-474c-46db-8f8c-2008c0350954@opensips.org>
Message-ID: <CALf-Q47eUdU9VpD+O+iE1uWzJvtJEtRapuhem2znUZ-wK0xwxQ@mail.gmail.com>

Thank you for the help .

I built CLI with python 3.8 on the  redhat 8 machine and that works for me
.

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


On Tue, Dec 19, 2023 at 12:22 AM Liviu Chircu <liviu at opensips.org> wrote:

> Hi folks,
>
> An explanation + solution for this specific CLI issue related to *Python
> 3.6* + the *zipp* package version can be found on the CLI tracker, part
> of issue #113
> <https://github.com/OpenSIPS/opensips-cli/issues/113#issuecomment-1861311868>
>
> Hope this helps,
>
> On 13.12.2023 08:45, Sasmita Panda wrote:
>
> python3 -V
> Python 3.6.8
>
> This is the exact version I have .
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Tue, Dec 12, 2023 at 8:12 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> What is the exact version of Python you have?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 12.12.2023 13:42, Sasmita Panda wrote:
>>
>> I am trying to install opensips-cli on the same version of linux but
>> facing some issue while connecting to the cli interface .
>>
>>
>> Steps I have followed :
>> sudo yum install python3 python3-pip python3-devel gcc
>> sudo yum install  python3-sqlalchemy python3-pyOpenSSL
>> git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
>> cd /root/src/opensips-cli/
>> sudo python3 setup.py install clean
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> */usr/local/bin/opensips-cli Traceback (most recent call last):   File
>> "/usr/local/bin/opensips-cli", line 4, in <module>
>> __import__('pkg_resources').run_script('opensipscli==0.2.0',
>> 'opensips-cli')   File
>> "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 654, in
>> run_script     self.require(requires)[0].run_script(script_name, ns)   File
>> "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1434, in
>> run_script     exec(code, namespace, namespace)   File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
>> line 3, in <module>     from opensipscli import main   File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py",
>> line 22, in <module>     from opensipscli import cli, defaults, version
>> File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py",
>> line 32, in <module>     from opensipscli.modules import *   File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py",
>> line 24, in <module>     __import__(modname)   File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py",
>> line 23, in <module>     from opensipscli.db import (   File
>> "/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py",
>> line 37, in <module>     import sqlalchemy_utils   File
>> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py",
>> line 1, in <module>     from .aggregates import aggregated  # noqa   File
>> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py",
>> line 374, in <module>     from .compat import _select_args,
>> get_scalar_subquery   File
>> "/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py",
>> line 7, in <module>     from importlib_metadata import metadata   File
>> "/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py",
>> line 7, in <module>     import zipp   File
>> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py",
>> line 9, in <module>     from .py310compat import text_encoding   File
>> "/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py",
>> line 5     def _text_encoding(encoding, stacklevel=2, /):  # pragma: no
>> cover*
>>
>>
>> How should I proceed ?
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS eBootcamp, Nov 6-17 | www.opensips.org/training
>
> _______________________________________________
> 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/20231219/02aee975/attachment-0001.html>

From bogdan at opensips.org  Tue Dec 19 14:28:12 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 19 Dec 2023 16:28:12 +0200
Subject: [OpenSIPS-Users] OpenSIPS Summit 2024 - Valencia, Spain
Message-ID: <33607ac7-c6a9-438b-af09-f39e7b8b88ba@opensips.org>

<https://www.opensips.org/events/Summit-2024Valencia>


  OpenSIPS Summit


  May 14th - 17th, 2024

Valencia, Spain


*Bridging people, bridging technologies, bridging experiences
*

The OpenSIPS Summit 
<https://www.opensips.org/events/Summit-2024Valencia> is the meeting 
place for the OpenSIPS community, for experts, developers and users from 
all over the world, looking to learn and gain knowledge. The OpenSIPS 
Summit is a melting pot for discussion on new technology, for sharing 
experiences, for brainstorming on new trends, for building bridges in 
the Open-Source VoIP & RTC ecosystem.

*Some Great Reasons to Attend*

  * Access the latest news, knowledge and experience in the VoIP & RTC world
  * Learn about upcoming 3.5 OpenSIPS release and how you can leverage it
  * Attend unique presentations and interactive technical workshops
  * Meet FOSS developers and community to share experience and comments
  * Get solutions consultancy during the Free Design Clinics
  * Become an Expert attending the OpenSIPS Advanced Training


*Summit Agenda*

  * Two full days of presentations given by key speakers
  * Open Discussions with key people from OpenSIPS and other OSS projects
  * One full day of Interactive Demos and Showcases
  * One full day of Design Clinics to validate your OpenSIPS deployments
  * One full day OpenSIPS Training (limited seats!)
  * Social events in the beautiful Valencia


*Attend to learn* - the registration process is already open, for both 
online and in-person participants. Note that the training and Design 
Clinics options are available only for the in-person participants. 
The/*Corporate Package*/ is available with an attractive discount.

Register now <https://www.opensips.org/events/Summit-2024Valencia/#pricing>

*Speak to share* - the Call for Papers is open for in-person and online 
speakers. Our speaker will enjoy free admission to the event, covering 
lunches and evening events.

Submit your paper now <https://www.papercall.io/opensips-summit-2024>

*Sponsor to help* - we welcome any help in making the Summit such a 
great event. Sponsoring is a natural way of saying "Thank you" for the 
Open Source code you are using within your businesses.

Become a sponsor 
<https://www.opensips.org/events/Summit-2024Valencia/#sponsors>

Interested? Please contact 
<https://www.opensips.org/events/Summit-2024Valencia/#contact-map> our 
team or email <mailto:summit at opensips.org?subject=OpenSIPS%20Summit> us!


**


	
	

	
	


-- 
Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231219/385ed383/attachment.html>

From nzdealshelp at gmail.com  Wed Dec 20 10:38:49 2023
From: nzdealshelp at gmail.com (nz deals)
Date: Wed, 20 Dec 2023 23:38:49 +1300
Subject: [OpenSIPS-Users] uac_replace_from in CANCEL
Message-ID: <CALOQYivKCFZYHHxE_TxUyD4dM22BSPA6Y6h_ORzZxh9UK52t_g@mail.gmail.com>

Hi,
I've been attempting to modify the From header in the CANCEL, but it seems
the changes aren't taking effect. I've also experimented with remove_hf and
append_hf, but unfortunately, these methods didn't work either. Could
someone kindly offer suggestions if I might be overlooking something?

This is in the main request route

        if (is_method("CANCEL")) {
                uac_replace_from("","sip:test at test.com");
                if (t_check_trans())
                        t_relay(8);
                exit;
        }




Regards,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231220/7e41ac66/attachment.html>

From liviu at opensips.org  Wed Dec 20 12:25:08 2023
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 20 Dec 2023 14:25:08 +0200
Subject: [OpenSIPS-Users] [OpenSIPS-Devel] [Release] OpenSIPS 3.4.3, 3.3.9
 and 3.2.16 Minor Releases; EoL for OpenSIPS 3.3!
In-Reply-To: <0028dc2d-9686-4fc2-827f-2469b83ddc53@opensips.org>
References: <0028dc2d-9686-4fc2-827f-2469b83ddc53@opensips.org>
Message-ID: <457e18e1-9f6f-4e8d-8691-a3a7ea9ff8f7@opensips.org>

Hello!

It is my pleasure to announce a new round of stable minor releases: 
*3.4.3*, *3.3.9* and *3.2.16*.

Do make sure to schedule an update, as they contain important fixes, to 
name a few:
   * dialog: fix PKG memory fragmentation issues around 'dlg_list' (a 
long-awaited fix for a mysterious, constantly-recurring problem)
   * rest_client: async timeouts now work as intended;  dangling 
requests, due to no response from server, should no longer be possible 
and should always time out
   * B2B: fixes on UAC side (fix To URI vs. R-URI construction;  fix BYE 
generation for dangling entities)
   * drouting: allow rule fallback even across prefixless rules (prefix: "")

Note that OpenSIPS *3.3* has reached its *end-of-life*, according to the 
release policy <https://www.opensips.org/Development/Development>.  It 
will no longer receive any more fixes, with *3.2 LTS *and *3.4 LTS* 
being the currently supported stable versions.

Full changelogs:

https://opensips.org/pub/opensips/3.4.3/ChangeLog
https://opensips.org/pub/opensips/3.3.9/ChangeLog
https://opensips.org/pub/opensips/3.2.16/ChangeLog

Happy Holidays!
OpenSIPS Team

On 27.11.2023 18:07, Liviu Chircu wrote:
>
> Hi, everyone!
>
> The 3.4.3, 3.3.9 and 3.2.16 OpenSIPS minor versions are scheduled for 
> release on *Wednesday, Dec 20th*.
>
> In preparation for the releases, starting *Wednesday, Dec 6th*, we 
> will impose the usual *freeze* on any significant fixes (as 
> complexity) on these stable branches, in order to ensure a /two-week 
> safe window/ for testing.
>
> So please make sure to ping any outstanding issues on the GitHub issue 
> tracker <https://github.com/OpenSIPS/opensips/issues> that may have 
> skipped our attention.  And thank you in advance!
>
> Best regards,
>
> -- 
> Liviu Chircu
> www.twitter.com/liviuchircu  |www.opensips-solutions.com
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231220/2a9e065c/attachment.html>

From bogdan at opensips.org  Wed Dec 20 13:31:02 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 20 Dec 2023 15:31:02 +0200
Subject: [OpenSIPS-Users] uac_replace_from in CANCEL
In-Reply-To: <CALOQYivKCFZYHHxE_TxUyD4dM22BSPA6Y6h_ORzZxh9UK52t_g@mail.gmail.com>
References: <CALOQYivKCFZYHHxE_TxUyD4dM22BSPA6Y6h_ORzZxh9UK52t_g@mail.gmail.com>
Message-ID: <7a5cd98b-4123-40d2-8dd2-32b23131d7bd@opensips.org>

Hi Jason,

In transactional stateful SIP, the CANCEL requests are hop by hop - each 
hop in the path is generating its own CANCEL requests to the next hop, 
which consumes it; there is no actual relaying of the CANCELs. So, the 
replacing (which works in relaying mode only) doesn't fit here.

Even more, the RFC3261 gives a rigorous way for building the CANCEL 
requests, they are to be built 100% based on the INVITE request only 
(nothing more). OpenSIPS internally builds the CANCEL in accordance to 
the corresponding INVITE, so you should not need any such changes.

May you detail why you think you need this FROM replacement?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 20.12.2023 12:38, nz deals wrote:
> Hi,
> I've been attempting to modify the From header in the CANCEL, but it 
> seems the changes aren't taking effect. I've also experimented with 
> remove_hf and append_hf, but unfortunately, these methods didn't work 
> either. Could someone kindly offer suggestions if I might be 
> overlooking something?
>
> This is in the main request route
>
>         if (is_method("CANCEL")) {
>                 uac_replace_from("","sip:test at test.com 
> <mailto:sip%3Atest at test.com>");
>                 if (t_check_trans())
>                         t_relay(8);
>                 exit;
>         }
>
>
>
> Regards,
> Jason
>
> _______________________________________________
> 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/20231220/04cee59c/attachment.html>

From thesipguy at gmail.com  Sun Dec 17 17:23:54 2023
From: thesipguy at gmail.com (S.Rosenberg)
Date: Sun, 17 Dec 2023 12:23:54 -0500
Subject: [OpenSIPS-Users] uac_auth DB support
In-Reply-To: <CAMtj7Ro2uxqebdNL=QDDp8JwLkOEkS2vPbcvqz8UwWGPQSA-dg@mail.gmail.com>
References: <CAMtj7Ro2uxqebdNL=QDDp8JwLkOEkS2vPbcvqz8UwWGPQSA-dg@mail.gmail.com>
Message-ID: <CAMtj7RpNK1mWbyGSvObJLa5FCKKAsEpk8cNTCCZ0PGMy2uGoqA@mail.gmail.com>

I ended up doing it the manually, I'm posting it so others who need it can
try my method,  I'm using cache_store in the startup route to avoid db
lookups for every call, I use an attribute in the the dr_gateways to
identify the row ID of the carrier in the registrar table I want to use.

In the startup_route I added the following, I will make a route to reload
this so I don't need to restart opensips whenever I add a carrier.

avp_db_query("select id, registrar, proxy, aor, third_party_registrant,
username, password, binding_URI, binding_params, expiry, forced_socket,
state from registrant","$avp(reg_id); $avp(reg_registrar); $avp(reg_proxy);
$avp(reg_aor); $avp(reg_third_party_registrant); $avp(reg_username);
$avp(reg_password); $avp(reg_binding_URI); $avp(reg_binding_params);
$avp(reg_expiry); $avp(reg_forced_socket); $avp(reg_state)");

 $var(i) = 0;

set_count($avp(reg_id),$var(reg_counter));

  while ($var(i) < $var(reg_counter)) {
         cache_store("local", "registrar_username_$(avp(reg_id)[$var(i)])",
"$(avp(reg_username)[$var(i)])");
         cache_store("local", "registrar_password_$(avp(reg_id)[$var(i)])",
"$(avp(reg_password)[$var(i)])");
  }

in the main route I run the following on the INVITE:

        if($(var(gw_attributes){s.substr,0,4})=="auth")    #if auth is set
in attributes it should be something like auth=10 where 10 is the id of the
row in the registrar table
        {
                $var(regAuthId)=$(var(gw_attributes){s.select,1,=});
 #pull the id from the attribute

cache_fetch("local","registrar_username_$var(regAuthId)",$var(registrar_username));

uac_replace_from("","sip:$var(registrar_username)@$socket_in(ip)");
 #replace the from field
                t_on_failure("dr");
                t_on_reply("dr");
        }

In my "dr" failure route I added the following
             if(t_check_status("407")){
                if($(avp(gw_attributes){s.substr,0,4})=="auth")
                {
                        $var(regAuthId)=$(avp(gw_attributes){s.select,1,=});

 cache_fetch("local","registrar_username_$var(regAuthId)",$var(registrar_username));

cache_fetch("local","registrar_password_$var(regAuthId)",$var(registrar_password));

                        if ($(<reply>hdr(Proxy-Authenticate)))
                        {
                                $var(raw_auth) =
$(<reply>hdr(Proxy-Authenticate));
                        }
                        if ($(<reply>hdr(WWW-Authenticate)))
                        {
                                $var(raw_auth) =
$(<reply>hdr(WWW-Authenticate));
                        }
                        $var(reg_start) = "/(.*?)realm=\"//g";
                        $var(reg_end) = "/\"(.*)//g";
                        $var(raw_auth) =
$(var(raw_auth){re.subst,$var(reg_start)});
                        $var(raw_auth) =
$(var(raw_auth){re.subst,$var(reg_end)});
                        $avp(uac_realm)=$var(raw_auth);
                        $avp(uac_username)=$var(registrar_username);
                        $avp(uac_password)=$var(registrar_password);
                        uac_auth();
                        if(!t_relay()){
                                t_reply (503, "Service not available");
                        }
                }
        }




On Wed, Dec 6, 2023 at 9:18 AM S.Rosenberg <thesipguy at gmail.com> wrote:

> Hi, I'm using the uac_auth to send calls to carriers that require
> username/password credentials, until now I only had a handful of carriers
> that don't support IP authentication so I hard coded the credentials, I was
> thinking of pulling it from the  registrant table as most of the time I
> would want to register to them anyway.
>
> I would like to know if OpenSIPS has a way to pull the registrant info via
> code without manually doing a DB query?
>
> S. Rosenberg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231217/a714317d/attachment-0001.html>

From abjordaan at gmail.com  Wed Dec 20 10:46:01 2023
From: abjordaan at gmail.com (Andre Jordaan)
Date: Wed, 20 Dec 2023 10:46:01 +0000
Subject: [OpenSIPS-Users] Rate Limit Pipes Replication Issue
Message-ID: <AS1PR10MB55307F35399DC84E8F781128AD96A@AS1PR10MB5530.EURPRD10.PROD.OUTLOOK.COM>

Hi,

Facing an issue with RATELIMIT replication where I want to rate limit a customer throughout the entire cluster. I have 2 standalone OpenSIPs nodes, node_id=1 and node_id=3 and rate limit pipes do not seem to replicate.

Cluster is up, ratelimit-pipe-repl enabled and OK. When I make a call via node1 the rate limit shows correctly however this information is not replicated to node3

[root at node1 ~]# opensips-cli -x mi rl_list
{
    "Pipes": [
        {
            "id": "TEST",
            "algorithm": "RED",
            "limit": 1,
            "counter": 1
        }
    ],
    "drop_rate": 0
}

[root at node3 ~]# opensips-cli -x mi rl_list
{
    "Pipes": [],
    "drop_rate": 0
}

Config of Node 1:

#### PROTO_BIN Module
loadmodule "proto_bin.so"
modparam("proto_bin", "bin_port", 5555)
modparam("proto_bin", "bin_send_timeout", 200)

modparam("proto_bin", "bin_max_msg_chunks", 8)
modparam("proto_bin", "bin_async", 0)
modparam("proto_bin", "bin_async_max_postponed_chunks", 16)

#### CLUSTERER Module
loadmodule "clusterer.so"
modparam("clusterer", "my_node_id", 1)
modparam("clusterer", "db_mode", 1)
modparam("clusterer", "db_url","mysql://opensips:opensipsrw at localhost/opensips")

#### RATELIMIT  Module
loadmodule "ratelimit.so"
modparam("ratelimit", "pipe_replication_cluster", 1)
modparam("ratelimit", "limit_per_interval", 0) # limit per-second

Config of Node 3:
#### PROTO_BIN Module
loadmodule "proto_bin.so"
modparam("proto_bin", "bin_port", 5555)
modparam("proto_bin", "bin_send_timeout", 200)
modparam("proto_bin", "bin_max_msg_chunks", 8)
modparam("proto_bin", "bin_async", 0)
modparam("proto_bin", "bin_async_max_postponed_chunks", 16)

#### CLUSTERER Module
loadmodule "clusterer.so"
modparam("clusterer", "my_node_id", 3)
modparam("clusterer", "db_mode", 1)
modparam("clusterer", "db_url","mysql://opensips:opensipsrw at localhost/opensips")

#### ratelimit Module
loadmodule "ratelimit.so"
modparam("ratelimit", "pipe_replication_cluster", 1)
modparam("ratelimit", "limit_per_interval", 0) # limit per-second


mysql> select * from clusterer;
+----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+---------------------+
| id | cluster_id | node_id | url                  | state | no_ping_retries | priority | sip_addr | flags | description         |
+----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+---------------------+
|  1 |          1 |       1 | bin:10.0.208.20:5555 |     1 |               3 |       50 | NULL     | seed  | PKL OpenSIPS Node 1 |
|  3 |          1 |       3 | bin:10.0.210.20:5555 |     1 |               3 |       50 | NULL     | NULL  | CPT OpenSIPS Node 1 |
+----+------------+---------+----------------------+-------+-----------------+----------+----------+-------+---------------------+

Below is the details of the cluster state:

Cluster Topology:

opensips-cli -x mi clusterer_list_topology
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Nodes": [
                {
                    "node_id": 1,
                    "Neighbours": [
                        3
                    ]
                },
                {
                    "node_id": 3,
                    "Neighbours": [
                        1
                    ]
                }
            ]
        }
    ]
}

Cluster List:

[root at node1~]# opensips-cli -x mi clusterer_list
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Nodes": [
                {
                    "node_id": 3,
                    "db_id": 3,
                    "url": "bin:10.0.210.20:5555",
                    "link_state": "Up",
                    "state": "enabled",
                    "next_hop": "3",
                    "description": "CPT OpenSIPS Node 1"
                }
            ]
        }
    ]
}

[root at node3 ~]# opensips-cli -x mi clusterer_list
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Nodes": [
                {
                    "node_id": 1,
                    "db_id": 1,
                    "url": "bin:10.0.208.20:5555",
                    "link_state": "Up",
                    "state": "enabled",
                    "next_hop": "1",
                    "description": "PKL OpenSIPS Node 1"
                }
            ]
        }
    ]
}

Cluster Capability:
opensips-cli -x mi clusterer_list_cap
{
    "Clusters": [
        {
            "cluster_id": 1,
            "Capabilities": [
                {
                    "name": "ratelimit-pipe-repl",
                    "state": "Ok",
                    "enabled": "yes"
                }
            ]
        }
    ]
}

Any samples or previous posts that I can reference?

Andre


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

From prathibhab.tvm at gmail.com  Sun Dec 24 09:15:25 2023
From: prathibhab.tvm at gmail.com (Prathibha B)
Date: Sun, 24 Dec 2023 09:15:25 +0000
Subject: [OpenSIPS-Users] Ringing time
Message-ID: <SI2PR06MB400970BBBFE4D153DF5EFBC7FC9AA@SI2PR06MB4009.apcprd06.prod.outlook.com>

How to increase the ringing time?

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231224/36654d68/attachment.html>

From david.villasmil.work at gmail.com  Sun Dec 24 10:34:40 2023
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Sun, 24 Dec 2023 11:34:40 +0100
Subject: [OpenSIPS-Users] Ringing time
In-Reply-To: <SI2PR06MB400970BBBFE4D153DF5EFBC7FC9AA@SI2PR06MB4009.apcprd06.prod.outlook.com>
References: <SI2PR06MB400970BBBFE4D153DF5EFBC7FC9AA@SI2PR06MB4009.apcprd06.prod.outlook.com>
Message-ID: <CAFGRPVpGYf6UjS2yMj-ahwdZvMRUnWE9_8O5vYcRpv7_HTb=Vg@mail.gmail.com>

Timeout? If so then
https://opensips.org/html/docs/modules/2.3.x/tm.html#fr_timeout


Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337


On Sun, 24 Dec 2023 at 10:15, Prathibha B <prathibhab.tvm at gmail.com> wrote:

> How to increase the ringing time?
>
> Sent from Outlook for Android <https://aka.ms/AAb9ysg>
> _______________________________________________
> 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/20231224/a6fdda8f/attachment.html>

From nzdealshelp at gmail.com  Sun Dec 24 11:33:50 2023
From: nzdealshelp at gmail.com (nz deals)
Date: Mon, 25 Dec 2023 00:33:50 +1300
Subject: [OpenSIPS-Users] uac_replace_from in CANCEL
In-Reply-To: <7a5cd98b-4123-40d2-8dd2-32b23131d7bd@opensips.org>
References: <CALOQYivKCFZYHHxE_TxUyD4dM22BSPA6Y6h_ORzZxh9UK52t_g@mail.gmail.com>
 <7a5cd98b-4123-40d2-8dd2-32b23131d7bd@opensips.org>
Message-ID: <CALOQYisg-g=6xx=OJ_+1eQHPRE3BFFC9vswYso41wChzLXXZ6g@mail.gmail.com>

Hi Bogdan,
Agreed that the RFC3261 CANCEL is truly built using INVITE. In my case,
somehow CANCEL is not the same as the initial INVITE. Due to the complexity
of my case I have hard times to fix the issue. Let me explain a bit.
On the INVITE i change the From Header, which i can see has also been
changed during Authorization.
If i CANCEL then the From header is different (it's the same as i have
before making my change).

I am also using topology_hiding().



under the main route i change the From header for INVITE

        set_advertised_address("104.13.xx.xx "); # same as i have used in
the advertised_address
        # this is my cancel processing
        if (is_method("CANCEL")) {
                if (t_check_trans())
                        t_relay(8);
                exit;
        }
        if (has_totag()) {
            if(topology_hiding_match())  {
                                   # remove and add a custom one
                                   remove_hf("From");
                                   append_hf("From: \"$fU\"<sip:$fU@
$td;custom=$var(custom)>;tag=$ft\r\n");

 force_send_socket("tls:192.xx.xx.xx:5061");
             }
        }

My opensips version is 3.4.2
My listening socket is socket=tls:ens192:5061 tag ens192     (its the same
192.xx.xx.xx IP that you see in the force_send_socket)
I am also using public ip as follows
advertised_address=104.13.xx.xx
alias=104.13.xx.xx


Regards,
Jason

On Thu, 21 Dec 2023 at 02:31, Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Jason,
>
> In transactional stateful SIP, the CANCEL requests are hop by hop - each
> hop in the path is generating its own CANCEL requests to the next hop,
> which consumes it; there is no actual relaying of the CANCELs. So, the
> replacing (which works in relaying mode only) doesn't fit here.
>
> Even more, the RFC3261 gives a rigorous way for building the CANCEL
> requests, they are to be built 100% based on the INVITE request only
> (nothing more). OpenSIPS internally builds the CANCEL in accordance to the
> corresponding INVITE, so you should not need any such changes.
>
> May you detail why you think you need this FROM replacement?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 20.12.2023 12:38, nz deals wrote:
>
> Hi,
> I've been attempting to modify the From header in the CANCEL, but it seems
> the changes aren't taking effect. I've also experimented with remove_hf and
> append_hf, but unfortunately, these methods didn't work either. Could
> someone kindly offer suggestions if I might be overlooking something?
>
> This is in the main request route
>
>         if (is_method("CANCEL")) {
>                 uac_replace_from("","sip:test at test.com");
>                 if (t_check_trans())
>                         t_relay(8);
>                 exit;
>         }
>
>
>
>
> Regards,
> Jason
>
> _______________________________________________
> 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/20231225/49f4419f/attachment.html>

From sj6502621 at gmail.com  Tue Dec 26 20:54:41 2023
From: sj6502621 at gmail.com (James Seer)
Date: Tue, 26 Dec 2023 21:54:41 +0100
Subject: [OpenSIPS-Users] replicate to HEP using the advertised address -
	OPENSIPS 3.3.9
Message-ID: <CAAALedoQVm0KNqJX5mWmr1fz-xdem+dXHVu-kSbUrMOmZiWiHg@mail.gmail.com>

Aaaa the good old days before commit 4bd50335a (2023-12-12 by Vlad Paiu),
life was simpler when my vip network interface and VIP itself were just one
happy entity in HOMER's eyes :P

This recent commit with its replication to HEP using the advertised address
has complicated things in homer heplify by treating them as two different
entities in the sip sequence (precisely during ACKs CANCEL and BYEs). Any
chance we could make this an optional feature?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20231226/894daaa8/attachment.html>

From iamhalje at gmail.com  Wed Dec 27 09:38:42 2023
From: iamhalje at gmail.com (Dmitry Ponomaryov)
Date: Wed, 27 Dec 2023 14:38:42 +0500
Subject: [OpenSIPS-Users] mid_register and its possible bad actions with
	De-REGISTER
Message-ID: <716391af-fb1a-01a9-e440-34a6e31ec45d@gmail.com>

Hello, opensips community, let's imagine default situations where we 
have dynamic users who can move and change FREQUENTLY! ip-address on 
phone, and re-send the registration, and at the same time we have in the 
configs:

mid_registrar_save("location","c1f");

in this case, we receive with any new registration from the user, the 
old registration will be deleted:

PQsendQuery(delete from location where contact_id=...) 
mid_registrar:reg_tm_cback: >> [REPLY] UNREGISTER !

this is in Contact throttling, reflected by contact_id.

and each deletion of a contact from the location table leads to a 
De-REGISTER, and a new register, is such a De-REGISTER needed?? which if 
this all happens in throttling mode, and OpenSIPS knows about all 
contacts, and let the final server be Asterisk , the main thing is to 
send INVITE to OpenSIPS for further work.

All this to say, it might make sense to add the ability to disable this 
De-REGISTER, because with a new registration, we will still send it a 
registration with an updated contact before the main registrar times 
out, and there will be no problems, that is, for example, the following 
settings:

modparam("mid_registrar", "outgoing_expires", 600) 
modparam("mid_registrar", "default_expires", 300)

 From doc mid_registrar:

A common occurrence is for some SIP User Agents to lose their network 
connection (especially when dealing with mobile devices), hence they do 
not properly de-register from the mid-registrar. In this case, in order 
to avoid stale registrations on the main registrar (which contains SIP 
contacts with greatly extended lifetimes!), the mid-registrar will 
appropriately generate De-REGISTER requests and remove these contacts 
from the main registrar's location service as soon as it considers them 
to have expired.

Thank you in advance!



From johan at democon.be  Wed Dec 27 09:47:01 2023
From: johan at democon.be (johan)
Date: Wed, 27 Dec 2023 10:47:01 +0100
Subject: [OpenSIPS-Users] mid_register and its possible bad actions with
 De-REGISTER
In-Reply-To: <716391af-fb1a-01a9-e440-34a6e31ec45d@gmail.com>
References: <716391af-fb1a-01a9-e440-34a6e31ec45d@gmail.com>
Message-ID: <b7fc427c-c3d5-43c6-b621-6fa951b6dbdf@democon.be>

So

either your client's dhcp config sucks, or the client's internet line is 
not good or you don't support push notifications.

In any case, I would limit the contacts stored in location to one.

That will limit the traffic much more then kicking out deregistrations.

On 27/12/2023 10:38, Dmitry Ponomaryov wrote:
> De-REGISTER needed?? which if this all happens in throttling mode, and 
> OpenSIPS knows about all contacts, and let the final server be 
> Asterisk , the main thing is to send INVITE to OpenSIPS for further work.
>
> All this to say, it might make sense to add the ability to disable 
> this De-REGISTER, because with a new registration, we will still send 
> it a registration with an upda


From iamhalje at gmail.com  Wed Dec 27 09:55:53 2023
From: iamhalje at gmail.com (Dmitry Ponomaryov)
Date: Wed, 27 Dec 2023 14:55:53 +0500
Subject: [OpenSIPS-Users] [mid_register and its possible bad actions
	with De-REGISTER]
Message-ID: <ffb73460-bb4c-5966-c8a8-328094974809@gmail.com>

Hello, well, okay if we are limited to one contact, the port for example 
of a contact changes conditionally on average every ~300sec, because of 
this, with a new registration we force it with the "f" flag, and thereby 
making De-REGISTER towards the main register, then there is each new 
registration that deletes an entry in "location", thereby creating a 
De-REGISTER before/after REGISTER.



From iamhalje at gmail.com  Wed Dec 27 10:07:40 2023
From: iamhalje at gmail.com (Dmitry Ponomaryov)
Date: Wed, 27 Dec 2023 15:07:40 +0500
Subject: [OpenSIPS-Users] [mid_register and its possible bad actions
	with De-REGISTER]
Message-ID: <f6aa953d-ab2a-aa6f-9d4f-c0d6ffbd9d12@gmail.com>

and we also have an unpleasant situation with the interfaces from which 
this same De-REGISTER comes, in the latest versions 3.2, we get from the 
interface that was first written in the socket, and not from which the 
registration on the main registrar.

was this planned? maybe it’s better to put it in modparam of module 
mid_registrar?