From marcin at voipplus.net  Tue Nov  2 19:25:41 2021
From: marcin at voipplus.net (Marcin Groszek)
Date: Tue, 2 Nov 2021 14:25:41 -0500
Subject: [OpenSIPS-Users] drouting WARNING
Message-ID: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>

I see a WARNING at opensips start/restart : verion 3.1.5

WARNING:drouting:parse_destination_list: destination ID <cr2> was not found

I check my database and :

dr_rules has a prefix and gwlist shows cr2 ;  not #cr2

in dr_carriers I see carrierid cr2 and corresponding gwlist has a gw3

in dr_gateways i see gwid gw3 and valid address sip:10.0.0.111:5060 with 
state 0

What am I missing here?





From a.martin at alphalink.fr  Wed Nov  3 08:00:54 2021
From: a.martin at alphalink.fr (Adrien Martin)
Date: Wed, 3 Nov 2021 09:00:54 +0100
Subject: [OpenSIPS-Users] drouting WARNING
In-Reply-To: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
References: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
Message-ID: <cae610d8-4e8b-3e2e-2692-5b20ba04292a@alphalink.fr>

Hello,

> dr_rules has a prefix and gwlist shows cr2 ;  not #cr2
> ...
> What am I missing here?


I think it is what you wrote in the comment.
Carrier ids are prefixed by '#' in dr_rules.
Without this prefix it use gateways directly without carriers.


From bogdan at opensips.org  Wed Nov  3 08:26:51 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 3 Nov 2021 10:26:51 +0200
Subject: [OpenSIPS-Users] Opensips 3.1Debian constantly crashing
In-Reply-To: <CA+B81WJffT3-zWUcTYDW0RahuvH3f596d_Z42b0RtdXxoPv40w@mail.gmail.com>
References: <CA+B81WJnrRjH5Z2A3B96QVZHhrx0O+hrWNtQh_HZqVhPp5Ap+w@mail.gmail.com>
 <CA+B81WLWGxjuh2JT-9wJfHT_HcD1Z6MUim-8PSp1UfQ9ZfFU8g@mail.gmail.com>
 <CALXCt0qyJQ4Yk-WmkbGnjuVoDgbGnxOaxiCFmPhRYYzV_-Ppzw@mail.gmail.com>
 <CA+B81WKmM46tLqGd4jku=f69eLK6NogvDytfTuRB0pFhrmQWZQ@mail.gmail.com>
 <4ef987b6-f967-1bf4-29b7-bdc0c76a6c4e@opensips.org>
 <CA+B81W+=3LDqwWV_4DBZu6SQtG4bMGDq54kOeAKVBrfut6tbFQ@mail.gmail.com>
 <36a2c8e6-b965-d994-ef2e-897aaa0eaf20@opensips.org>
 <CA+B81WJffT3-zWUcTYDW0RahuvH3f596d_Z42b0RtdXxoPv40w@mail.gmail.com>
Message-ID: <38282605-e59e-abe3-a639-91fea1796e0e@opensips.org>

Hi Mario,

As a way about from such situation, I just added a new script function 
get_updated_body_part() [1] that allows you to fetch the body, with all 
the existing changes, into a variable, so you can pass it further to 
rtpengine

[1] 
https://opensips.org/html/docs/modules/3.3.x/sipmsgops.html#func_get_updated_body_part

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 10/22/21 6:26 AM, Mario San Vicente wrote:
> Hello Bogdan-Andrei,
>
> I ran some traffic without rtpengine and with the codec operations, i 
> did not got any core files.  I will take care of not combining those 
> commands.
>
>
> Thanks and regards.
> Mario
>
> On Thu, Oct 21, 2021 at 7:26 AM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Mario,
>
>     So you do both rtpengine ops and codecs ops in your cfg. This is a
>     bit of a receipt for disaster (as both are independently changing
>     the SDP), still not for a crash.
>
>     Could you try to run both codec ops, but without rtpengine, just
>     to see if ok ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS eBootcamp 2021
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 10/19/21 7:20 PM, Mario San Vicente wrote:
>>     Hello Bogdan-Andrei,
>>
>>     I removed the following lines and it is working fine now.  Not
>>     sure if the issue was one or the combination of those 2 lines
>>     that made opensips crash.
>>
>>                   #codec_delete_re("PCMA|PCMU");
>>                   #codec_delete_except_re("speex");
>>
>>     The reason for using those lines was that opensips was doing
>>     transcoding and after a while it stops doing the transcode, it
>>     just was bypassing the original codec offer.   This is also
>>     solved, the problem is that the rtpengine_offer was not closing
>>     properly and then i ran out of ports.     The solution was to
>>     add rtpengine_delete(); at the failure route.
>>
>>
>>     Thank you all for your help!
>>
>>     Regards.
>>     Mario
>>
>>     On Tue, Oct 19, 2021 at 2:01 AM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hi Mario,
>>
>>         What is the codec relate operation you do from the script? As
>>         it looks it is crashing there.
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>         OpenSIPS eBootcamp 2021
>>            https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>>
>>         On 10/19/21 12:15 AM, Mario San Vicente wrote:
>>>         Thank you Giovany .
>>>
>>>         I got some info, but I'm not sure how to proceed....  Looks
>>>         like an issue assigning core vars..  Here the whole info in
>>>         a txt file.
>>>
>>>
>>>         {rs = {s = 0x6dc2d4a3fa5df100 <error: Cannot access memory
>>>         at address 0x6dc2d4a3fa5df100>,
>>>         sval = {s = 0x100000002 <error: Cannot access memory at
>>>         address 0x100000002>, len = -1510612476}
>>>
>>>         Thank your comments.
>>>
>>>         On Mon, Oct 18, 2021 at 12:39 PM Giovanni Maruzzelli
>>>         <gmaruzz at gmail.com <mailto:gmaruzz at gmail.com>> wrote:
>>>
>>>             On Mon, Oct 18, 2021 at 7:01 PM Mario San Vicente
>>>             <mrsanvicente at gmail.com <mailto:mrsanvicente at gmail.com>>
>>>             wrote:
>>>
>>>                 Hello Ovidiu,
>>>
>>>                 That works for getting the core files.  Then i run
>>>                 the command bt full and got the following:
>>>
>>>
>>>             You must install the opensips-dbg debian package, it
>>>             contains the symbols, then restart opensips, then retake
>>>             the core and you'll see info in it.
>>>
>>>             -giovanni
>>>
>>>             -- 
>>>             Sincerely,
>>>
>>>             Giovanni Maruzzelli
>>>             OpenTelecom.IT
>>>             cell: +39 347 266 56 18
>>>
>>>             _______________________________________________
>>>             Users mailing list
>>>             Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>             http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>             <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>>
>>>
>>>
>>>         -- 
>>>         Mario San Vicente
>>>         Cheers!
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>
>>
>>
>>     -- 
>>     Mario San Vicente
>>     Cheers!
>
>
>
> -- 
> Mario San Vicente
> Cheers!

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

From aronp at guaranteedplus.com  Thu Nov  4 01:17:57 2021
From: aronp at guaranteedplus.com (Podrigal, Aron)
Date: Wed, 3 Nov 2021 20:17:57 -0500
Subject: [OpenSIPS-Users] Opensips segfault after adding acc_extra field
Message-ID: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>

Hi

I added another field to my acc_extra and after restarting opensips, it
kept crashing right away after the restart.

Here are the relevant log lines

I got a thousand lines saying
Nov 03 20:48:03 snap-p1 opensips-snap[1636]: WARNING:acc:restore_extra:
extra tags were added/removed since last run!won't restore values!

Then 2 - 3 lines afterwards

Nov 03 20:48:04 p1 opensips[1651]: CRITICAL:core:sig_usr: segfault in
process pid: 1651, id: 7
Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: child process
1651 exited by a signal 11
Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: core was not
generated
Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: terminating due
to SIGCHLD
Nov 03 20:48:04 p1 opensips[1643]: INFO:core:sig_usr: signal 15 received
Nov 03 20:48:04 p1 opensips[1642]: INFO:core:sig_usr: signal 15 received

I use opensips version 3.1 Rev 5cdfedebbe0

Any idea what can be causing this?

I have 2 acc targets one db and one log. And I added the acc_extra field
only to the log.


Thanks


-- 

-
Aron Podrigal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211103/3e24b953/attachment.html>

From kingsley at dns99.co.uk  Thu Nov  4 10:56:59 2021
From: kingsley at dns99.co.uk (Kingsley Tart)
Date: Thu, 04 Nov 2021 10:56:59 +0000
Subject: [OpenSIPS-Users] one node in 3 node cluster thinks all gateways are
	down
Message-ID: <af0413d5b90e3a09fdb7088fb6ab9b1aca695d03.camel@dns99.co.uk>

Hi,

I have a 3 node cluster of OpenSIPS 3.1.6 with VIPs maintained by
keepalived. Each has its own preferred VIP but will take on others if
other nodes become unavailable. Primarily, node A has 'vip-a', node B
has 'vip-b', and node C has 'vip-c'.

Node A is normally the one doing gateway probing:

modparam("drouting", "cluster_sharing_tag", "vip-a")

Right now, node A still has vip-a and is doing the gateway probing.
Node A and node B both consider all gateways active, but node C
considers them all inactive.

Node C is still receiving messages from the cluster, so I don't
understand why this is, given that it's only node A that's doing the
probing (I've verified this with ngrep) - only node A is originating
OPTIONS messages).

Any clues?

Cheers,
Kingsley.



From marcin at voipplus.net  Thu Nov  4 23:55:55 2021
From: marcin at voipplus.net (Marcin Groszek)
Date: Thu, 4 Nov 2021 18:55:55 -0500
Subject: [OpenSIPS-Users] restart_persistency Permission denied
In-Reply-To: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
References: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
Message-ID: <22930130-c147-80ef-4459-d1b53c4b6c33@voipplus.net>

Centos 7 opensips verion 3.1.5

I attempted to setup drouting restart_persistency but as soon as I add 
these 2 lines:

restart_persistency_size = 512

modparam("drouting", "enable_restart_persistency", yes)

opensips does not start.

The logs shows:

ERROR:core:rpm_init_mem: could not initialize restart persistent memory!
ERROR:drouting:dr_init: could not initilize restart persistency memory!
ERROR:core:init_mod: failed to initialize module drouting
ERROR:core:main: error while initializing modules
ERROR:core:init_rpm_mallocs: could not create the restart persistency 
memory file .restart_persistency.cache (13: Permission denied)

Thank you.




From marcin at voipplus.net  Fri Nov  5 00:14:12 2021
From: marcin at voipplus.net (Marcin Groszek)
Date: Thu, 4 Nov 2021 19:14:12 -0500
Subject: [OpenSIPS-Users] restart_persistency Permission denied
In-Reply-To: <22930130-c147-80ef-4459-d1b53c4b6c33@voipplus.net>
References: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
 <22930130-c147-80ef-4459-d1b53c4b6c33@voipplus.net>
Message-ID: <2f2c5b3c-3717-1b20-577e-e73349e2876a@voipplus.net>

I have started the opensips as root and the file 
.restart_persistency.cache was created under /

after I changed the ownership of the .restart_persistency.cache to 
opensips I was able to start daemon as opensips user.

Is this proper way of doing this or just a poor workaround?


On 11/4/2021 6:55 PM, Marcin Groszek wrote:
> Centos 7 opensips verion 3.1.5
>
> I attempted to setup drouting restart_persistency but as soon as I add 
> these 2 lines:
>
> restart_persistency_size = 512
>
> modparam("drouting", "enable_restart_persistency", yes)
>
> opensips does not start.
>
> The logs shows:
>
> ERROR:core:rpm_init_mem: could not initialize restart persistent memory!
> ERROR:drouting:dr_init: could not initilize restart persistency memory!
> ERROR:core:init_mod: failed to initialize module drouting
> ERROR:core:main: error while initializing modules
> ERROR:core:init_rpm_mallocs: could not create the restart persistency 
> memory file .restart_persistency.cache (13: Permission denied)
>
> Thank you.
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Best Regards:
Marcin Groszek
Business Voip Resource.
http://www.voipplus.net



From liviu at opensips.org  Fri Nov  5 09:47:10 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Fri, 5 Nov 2021 11:47:10 +0200
Subject: [OpenSIPS-Users] restart_persistency Permission denied
In-Reply-To: <2f2c5b3c-3717-1b20-577e-e73349e2876a@voipplus.net>
References: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
 <22930130-c147-80ef-4459-d1b53c4b6c33@voipplus.net>
 <2f2c5b3c-3717-1b20-577e-e73349e2876a@voipplus.net>
Message-ID: <6a2c49fc-c028-3827-d05d-b59fe0accaaf@opensips.org>

On 05.11.2021 02:14, Marcin Groszek wrote:
> after I changed the ownership of the .restart_persistency.cache to 
> opensips I was able to start daemon as opensips user.
>
> Is this proper way of doing this or just a poor workaround?

Hi Marcin,

This is an interesting report and although it looks like the devs could 
do something to improve your experience, ultimately I think this is a 
sysadmin runtime configuration error.  Here is my reasoning:

* by default, OpenSIPS starts as "root" user, with work directory "/".  
So drouting should work fine, as there is full permission to write to 
the "/" directory.

* in your case, you are downgrading permissions from "root" user to 
"opensips" user, but you are not customizing the "-w" work directory 
option, which remains "/". So, of course the "opensips" user cannot 
write to "/".

Hope this helps,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training



From marcin at voipplus.net  Fri Nov  5 11:52:46 2021
From: marcin at voipplus.net (Marcin Groszek)
Date: Fri, 5 Nov 2021 06:52:46 -0500
Subject: [OpenSIPS-Users] restart_persistency Permission denied
In-Reply-To: <6a2c49fc-c028-3827-d05d-b59fe0accaaf@opensips.org>
References: <f26aea8c-984e-30dd-59f0-944688f3e6bc@voipplus.net>
 <22930130-c147-80ef-4459-d1b53c4b6c33@voipplus.net>
 <2f2c5b3c-3717-1b20-577e-e73349e2876a@voipplus.net>
 <6a2c49fc-c028-3827-d05d-b59fe0accaaf@opensips.org>
Message-ID: <1893d37b-407b-a389-1661-7c201cda2add@voipplus.net>

Thank you. I do have 2 more questions regarding restart_persistency.

How do I estimate the size of cache file needed for my instant?

Calls that are ringing do not survive the restart, is this normal behavior?

ngrep shows no respond from opensips to 200 upon answer.


On 11/5/2021 4:47 AM, Liviu Chircu wrote:
> On 05.11.2021 02:14, Marcin Groszek wrote:
>> after I changed the ownership of the .restart_persistency.cache to 
>> opensips I was able to start daemon as opensips user.
>>
>> Is this proper way of doing this or just a poor workaround?
>
> Hi Marcin,
>
> This is an interesting report and although it looks like the devs 
> could do something to improve your experience, ultimately I think this 
> is a sysadmin runtime configuration error.  Here is my reasoning:
>
> * by default, OpenSIPS starts as "root" user, with work directory 
> "/".  So drouting should work fine, as there is full permission to 
> write to the "/" directory.
>
> * in your case, you are downgrading permissions from "root" user to 
> "opensips" user, but you are not customizing the "-w" work directory 
> option, which remains "/". So, of course the "opensips" user cannot 
> write to "/".
>
> Hope this helps,
>


From fengz.strong at gmail.com  Sun Nov  7 05:01:50 2021
From: fengz.strong at gmail.com (=?utf-8?B?5byg5rC46ZSL?=)
Date: Sun, 7 Nov 2021 13:01:50 +0800
Subject: [OpenSIPS-Users] Log err when reload qrouting module
Message-ID: <2F5EBF13-DCB4-45C8-B2D4-80C058B7AFB1@gmail.com>

OpenSIPS version you are running

version: opensips 3.2.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: f953b30a0
main.c compiled on 16:23:54 Nov  3 2021 with gcc 8
Describe the bug

I want to use qrouting module, but somehow, I reload drouting when i use cmd 'mi dr_reload' (or when opensips starts), I saw this log.

Nov  5 11:44:59 localhost opensips[68317]: WARNING:qrouting:qr_set_profile: profile '365012441' not found
Nov  5 11:44:59 localhost opensips[68317]: ERROR:qrouting:qr_rld_create_rule: failed to set profile 365012441 for rule 1
If I make a call, opensips will crash.

And, below is my db info:
mysql> select * from qr_profiles\G
*************************** 1. row ***************************
id: 3
profile_name: test
warn_threshold_asr: -1
warn_threshold_ccr: -1
warn_threshold_pdd: -1
warn_threshold_ast: -1
warn_threshold_acd: -1
crit_threshold_asr: -1
crit_threshold_ccr: -1
crit_threshold_pdd: -1
crit_threshold_ast: -1
crit_threshold_acd: -1
warn_penalty_asr: 0.5
warn_penalty_ccr: 0.5
warn_penalty_pdd: 0.5
warn_penalty_ast: 0.5
warn_penalty_acd: 0.5
crit_penalty_asr: 0.05
crit_penalty_ccr: 0.05
crit_penalty_pdd: 0.05
crit_penalty_ast: 0.05
crit_penalty_acd: 0.05
1 row in set (0.00 sec)

mysql> select * from dr_gateways\G
*************************** 1. row ***************************
id: 1
gwid: fs_01
type: 1
address: 192.168.88.131:5080
strip: 0
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
*************************** 2. row ***************************
id: 2
gwid: outbound_01
type: 2
address: 192.168.88.132:5080
strip: 3
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
*************************** 3. row ***************************
id: 3
gwid: outbound_02
type: 2
address: 192.168.88.132:5080
strip: 3
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
3 rows in set (0.00 sec)

mysql> select * from dr_rules\G
*************************** 1. row ***************************
ruleid: 1
groupid: 1
prefix: 123
timerec: NULL
priority: 0
routeid: NULL
gwlist: outbound_01,outbound_02
sort_alg: Q
sort_profile: NULL
attrs: NULL
description: NULL
1 row in set (0.01 sec)

And opensips-cli info:
(opensips-cli): mi qr_status

{
    "Partitions": [
        {
            "Name": "Default",
            "Rules": [
                {
                    "Id": 1,
                    "Destinations": [
                        {
                            "Gateway": {
                                "GWID": "outbound_01",
                                "ASR": "-1.00/0",
                                "CCR": "-1.00/0",
                                "PDD": "-1.00/0",
                                "AST": "-1.00/0",
                                "ACD": "-1.00/0"
                            }
                        },
                        {
                            "Gateway": {
                                "GWID": "outbound_02",
                                "ASR": "-1.00/0",
                                "CCR": "-1.00/0",
                                "PDD": "-1.00/0",
                                "AST": "-1.00/0",
                                "ACD": "-1.00/0"
                            }
                        }
                    ]
                }
            ]
        }
    ]
}
Can anyone help me, thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211107/3a120787/attachment.html>

From fengz.strong at gmail.com  Sun Nov  7 05:10:59 2021
From: fengz.strong at gmail.com (=?utf-8?B?5byg5rC46ZSL?=)
Date: Sun, 7 Nov 2021 13:10:59 +0800
Subject: [OpenSIPS-Users] Log err when reload qrouting module
Message-ID: <E9B4F0E9-00B4-4F60-9E15-928DD910096D@gmail.com>

OpenSIPS version you are running

version: opensips 3.2.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: f953b30a0
main.c compiled on 16:23:54 Nov  3 2021 with gcc 8
Describe the bug

I want to use qrouting module, but somehow, I reload drouting when i use cmd 'mi dr_reload' (or when opensips starts), I saw this log.

Nov  5 11:44:59 localhost opensips[68317]: WARNING:qrouting:qr_set_profile: profile '365012441' not found
Nov  5 11:44:59 localhost opensips[68317]: ERROR:qrouting:qr_rld_create_rule: failed to set profile 365012441 for rule 1
If I make a call, opensips will crash.

And, below is my db info:
mysql> select * from qr_profiles\G
*************************** 1. row ***************************
id: 3
profile_name: test
warn_threshold_asr: -1
warn_threshold_ccr: -1
warn_threshold_pdd: -1
warn_threshold_ast: -1
warn_threshold_acd: -1
crit_threshold_asr: -1
crit_threshold_ccr: -1
crit_threshold_pdd: -1
crit_threshold_ast: -1
crit_threshold_acd: -1
warn_penalty_asr: 0.5
warn_penalty_ccr: 0.5
warn_penalty_pdd: 0.5
warn_penalty_ast: 0.5
warn_penalty_acd: 0.5
crit_penalty_asr: 0.05
crit_penalty_ccr: 0.05
crit_penalty_pdd: 0.05
crit_penalty_ast: 0.05
crit_penalty_acd: 0.05
1 row in set (0.00 sec)

mysql> select * from dr_gateways\G
*************************** 1. row ***************************
id: 1
gwid: fs_01
type: 1
address: 192.168.88.131:5080
strip: 0
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
*************************** 2. row ***************************
id: 2
gwid: outbound_01
type: 2
address: 192.168.88.132:5080
strip: 3
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
*************************** 3. row ***************************
id: 3
gwid: outbound_02
type: 2
address: 192.168.88.132:5080
strip: 3
pri_prefix: NULL
attrs: NULL
probe_mode: 1
state: 0
socket: NULL
description: NULL
3 rows in set (0.00 sec)

mysql> select * from dr_rules\G
*************************** 1. row ***************************
ruleid: 1
groupid: 1
prefix: 123
timerec: NULL
priority: 0
routeid: NULL
gwlist: outbound_01,outbound_02
sort_alg: Q
sort_profile: NULL
attrs: NULL
description: NULL
1 row in set (0.01 sec)

And opensips-cli info:
(opensips-cli): mi qr_status

{
    "Partitions": [
        {
            "Name": "Default",
            "Rules": [
                {
                    "Id": 1,
                    "Destinations": [
                        {
                            "Gateway": {
                                "GWID": "outbound_01",
                                "ASR": "-1.00/0",
                                "CCR": "-1.00/0",
                                "PDD": "-1.00/0",
                                "AST": "-1.00/0",
                                "ACD": "-1.00/0"
                            }
                        },
                        {
                            "Gateway": {
                                "GWID": "outbound_02",
                                "ASR": "-1.00/0",
                                "CCR": "-1.00/0",
                                "PDD": "-1.00/0",
                                "AST": "-1.00/0",
                                "ACD": "-1.00/0"
                            }
                        }
                    ]
                }
            ]
        }
    ]
}
Can anyone help me, thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211107/39317a1c/attachment-0001.html>

From mrsanvicente at gmail.com  Mon Nov  8 12:39:02 2021
From: mrsanvicente at gmail.com (mrsanvicente)
Date: Mon, 8 Nov 2021 06:39:02 -0600
Subject: [OpenSIPS-Users] Opensips 3.1Debian constantly crashing
In-Reply-To: <38282605-e59e-abe3-a639-91fea1796e0e@opensips.org>
References: <38282605-e59e-abe3-a639-91fea1796e0e@opensips.org>
Message-ID: <4536E336-24A4-44F4-A61C-FA249606EBBA@gmail.com>

Hello Bogda-Andrei,

Thansk for the new functionality.  I will test it asap.

Regards 

Cheers
Mario San Vicente


> El 3 nov 2021, a la(s) 2:27, Bogdan-Andrei Iancu <bogdan at opensips.org> escribió:
> 
>  Hi Mario,
> 
> As a way about from such situation, I just added a new script function get_updated_body_part() [1] that allows you to fetch the body, with all the existing changes, into a variable, so you can pass it further to rtpengine 
> 
> [1] https://opensips.org/html/docs/modules/3.3.x/sipmsgops.html#func_get_updated_body_part
> 
> Best regards,
>  Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021 
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> On 10/22/21 6:26 AM, Mario San Vicente wrote:
>> Hello Bogdan-Andrei,
>> 
>> I ran some traffic without rtpengine and with the codec operations, i did not got any core files.  I will take care of not combining those commands.
>> 
>> 
>> Thanks and regards.
>> Mario
>> 
>> On Thu, Oct 21, 2021 at 7:26 AM Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
>>> Hi Mario,
>>> 
>>> So you do both rtpengine ops and codecs ops in your cfg. This is a bit of a receipt for disaster (as both are independently changing the SDP), still not for a crash.
>>> 
>>> Could you try to run both codec ops, but without rtpengine, just to see if ok ?
>>> 
>>> Regards,
>>>  Bogdan-Andrei Iancu
>>> 
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>> OpenSIPS eBootcamp 2021 
>>>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>> On 10/19/21 7:20 PM, Mario San Vicente wrote:
>>>> Hello Bogdan-Andrei,
>>>> 
>>>> I removed the following lines and it is working fine now.  Not sure if the issue was one or the combination of those 2 lines that made opensips crash.
>>>> 
>>>>               #codec_delete_re("PCMA|PCMU");
>>>>               #codec_delete_except_re("speex");
>>>> 
>>>> The reason for using those lines was that opensips was doing transcoding and after a while it stops doing the transcode, it just was bypassing the original codec offer.   This is also solved, the problem is that the rtpengine_offer was not closing properly and then i ran out of ports.     The solution was to add rtpengine_delete(); at the failure route.
>>>> 
>>>> 
>>>> Thank you all for your help!
>>>> 
>>>> Regards.
>>>> Mario
>>>> 
>>>> On Tue, Oct 19, 2021 at 2:01 AM Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
>>>>> Hi Mario,
>>>>> 
>>>>> What is the codec relate operation you do from the script? As it looks it is crashing there.
>>>>> 
>>>>> Regards,
>>>>>  Bogdan-Andrei Iancu
>>>>> 
>>>>> OpenSIPS Founder and Developer
>>>>>   https://www.opensips-solutions.com
>>>>> OpenSIPS eBootcamp 2021 
>>>>>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>>>> On 10/19/21 12:15 AM, Mario San Vicente wrote:
>>>>>> Thank you Giovany .
>>>>>> 
>>>>>> I got some info, but I'm not sure how to proceed....  Looks like an issue assigning core vars..  Here the whole info in a txt file.
>>>>>> 
>>>>>> 
>>>>>> {rs = {s = 0x6dc2d4a3fa5df100 <error: Cannot access memory at address 0x6dc2d4a3fa5df100>,
>>>>>> sval = {s = 0x100000002 <error: Cannot access memory at address 0x100000002>, len = -1510612476}
>>>>>> 
>>>>>> Thank your comments.
>>>>>> 
>>>>>> On Mon, Oct 18, 2021 at 12:39 PM Giovanni Maruzzelli <gmaruzz at gmail.com> wrote:
>>>>>>> On Mon, Oct 18, 2021 at 7:01 PM Mario San Vicente <mrsanvicente at gmail.com> wrote:
>>>>>>>> Hello Ovidiu,
>>>>>>>> 
>>>>>>>> That works for getting the core files.  Then i run the command bt full and got the following:
>>>>>>>> 
>>>>>>> 
>>>>>>> You must install the opensips-dbg debian package, it contains the symbols, then restart opensips, then retake the core and you'll see info in it.
>>>>>>> 
>>>>>>> -giovanni
>>>>>>> 
>>>>>>> -- 
>>>>>>> Sincerely,
>>>>>>> 
>>>>>>> Giovanni Maruzzelli
>>>>>>> OpenTelecom.IT
>>>>>>> cell: +39 347 266 56 18
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Users mailing list
>>>>>>> Users at lists.opensips.org
>>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> Mario San Vicente
>>>>>> Cheers!
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Mario San Vicente
>>>> Cheers!
>>> 
>> 
>> 
>> -- 
>> Mario San Vicente
>> Cheers!
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211108/4d4ecaaf/attachment.html>

From fengz.strong at gmail.com  Tue Nov  9 08:43:42 2021
From: fengz.strong at gmail.com (=?utf-8?B?5byg5rC46ZSL?=)
Date: Tue, 9 Nov 2021 16:43:42 +0800
Subject: [OpenSIPS-Users] Log err when reload qrouting module
Message-ID: <27D8F089-C72B-4354-8644-DA9478A0C2AA@gmail.com>

> OpenSIPS version you are running
> 
> version: opensips 3.2.3 (x86_64/linux)
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, > > > FAST_LOCK-ADAPTIVE_WAIT
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535
> poll method support: poll, epoll, sigio_rt, select.
> git revision: f953b30a0
> main.c compiled on 16:23:54 Nov  3 2021 with gcc 8
> Describe the bug

> I want to use qrouting module, but somehow, I reload drouting when i use cmd 'mi dr_reload' (or when opensips starts), I saw this log.

> Nov  5 11:44:59 localhost opensips[68317]: WARNING:qrouting:qr_set_profile: profile '365012441' not found
> Nov  5 11:44:59 localhost opensips[68317]: ERROR:qrouting:qr_rld_create_rule: failed to set profile 365012441 for rule 1
> If I make a call, opensips will crash.
> …

Sorry, it’s my fault. I did not set sort_profile in table dr_rules, if set this value, everyting looks fine!

From devang.dhandhalya at ecosmob.com  Tue Nov  9 11:05:34 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Tue, 9 Nov 2021 16:35:34 +0530
Subject: [OpenSIPS-Users] TLS Handshake fail issue
Message-ID: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>

Hi All

I Am Trying to Implement opensips with TLS support in a local machine . I
generate TLS server (rootCA) and TLS Client (user) certificates using
opensips-cli  .
softphone : Blink version : 5.1.7
opensips version : 3.2.2
Registration with tls is working fine for TLS ,  at the time of calling
getting below error . I check in logs at DBG level
>From User A to opensips server tls handshake is working fine but from
opensips to User B tls handshake is going to fail please suggest how to
resolve this .


INFO level Logs :

ERROR:core:tcp_async_connect: poll error: flags 1c
ERROR:core:tcp_async_connect: failed to retrieve SO_ERROR [server=
1.2.3.4:40945] (111) Connection refused
ERROR:proto_tls:proto_tls_send: async TCP connect failed
ERROR:tm:msg_send: send() to 1.2.3.4:40945 for proto tls/3 failed
ERROR:tm:t_forward_nonack: sending request failed
ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
1.2.3.4:34463 failed
ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
err=Success(0)
ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure
ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!

DBG level Logs :

DBG:core:parse_msg: SIP Request:
DBG:core:parse_msg:  method:  <INVITE>
DBG:core:parse_msg:  uri:     <sip:14682973 at 1.2.3.4:34463;transport=tls>
DBG:core:parse_msg:  version: <SIP/2.0>
DBG:core:parse_headers: flags=ffffffffffffffff
DBG:core:parse_via_param: found param type 232, <branch> =
<z9hG4bK14b8.6a972877.0>; state=6
DBG:core:parse_via_param: found param type 236, <i> = <d7b6e394>; state=16
DBG:core:parse_via: end of header reached, state=5
DBG:core:parse_headers: via found, flags=ffffffffffffffff
DBG:core:parse_headers: this is the first via
DBG:core:parse_via_param: found param type 234, <received> = <1.2.3.4>;
state=6
DBG:core:parse_via_param: found param type 235, <rport> = <38119>; state=6
DBG:core:parse_via_param: found param type 232, <branch> =
<z9hG4bKPja1ee2137-d7f4-4744-89e1-ff53b4b0b06b>; state=6
DBG:core:parse_via_param: found param type 237, <alias> = <n/a>; state=16
DBG:core:parse_via: end of header reached, state=5
DBG:core:parse_headers: via found, flags=ffffffffffffffff
DBG:core:parse_headers: parse_headers: this is the second via
DBG:core:_parse_to: end of header reached, state=10
DBG:core:_parse_to: display={}, ruri={sip:1001 at 1.2.3.4}
DBG:core:get_hdr_field: <To> [26]; uri=[sip:1001 at 1.2.3.4]
DBG:core:get_hdr_field: to body [<sip:1001 at 1.2.3.4>#015#012]
DBG:core:get_hdr_field: cseq <CSeq>: <14318> <INVITE>
DBG:core:get_hdr_field: content_length=717
DBG:core:get_hdr_field: found end of header
DBG:core:parse_headers: flags=ffffffffffffffff
DBG:proto_tls:proto_tls_send: no open tcp connection found, opening new
one, async = 1
DBG:core:probe_max_sock_buff: getsockopt: snd is initially 16384
DBG:core:probe_max_sock_buff: using snd buffer of 416 kb
DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 141
DBG:core:print_ip: tcpconn_new: new tcp connection to: 1.2.3.4
DBG:core:tcpconn_new: on port 34463, proto 3
DBG:tls_mgm:tls_find_client_domain: found TLS client domain: dom2
DBG:tls_openssl:openssl_tls_conn_init: Creating a whole new ssl connection
DBG:tls_openssl:openssl_tls_conn_init: Setting in CONNECT mode (client)
DBG:proto_tls:proto_tls_send: Successfully connected from interface
1.2.3.4:34463 to 1.2.3.4:36463!
DBG:proto_tls:proto_tls_send: First TCP connect attempt succeeded in less
than 100ms, proceed to TLS connect
DBG:tls_openssl:openssl_tls_update_fd: New fd is 141
DBG:core:handle_worker: read response= 7f83eb6b5118, 2, fd 119 from 8
(17254)
DBG:core:tcpconn_add: hashes: 607, 894
DBG:core:io_watch_add: [TCP_main] io_watch_add op (119 on 5)
(0x55fd3f789ae0, 119, 19, 0x7f83eb6b5118,1), fd_no=27/1024
DBG:core:handle_tcpconn_ev: data available on 0x7f83eb6b5118 119
DBG:core:io_watch_del: [TCP_main] io_watch_del op on index 2 119
(0x55fd3f789ae0, 119, 2, 0x0,0x1) fd_no=28 called
DBG:core:send2worker: to tcp worker 1 (0), 0x7f83eb6b5118 rw 1
DBG:core:handle_io: We have received conn 0x7f83eb6b5118 with rw 1 on fd 5
DBG:core:io_watch_add: [TCP_worker] io_watch_add op (5 on 102)
(0x55fd3f789ae0, 5, 19, 0x7f83eb6b5118,1), fd_no=4/1024
DBG:proto_tls:tls_read_req: Using the global ( per process ) buff
DBG:tls_openssl:openssl_tls_async_connect: handshake timeout for connection
0x7f83eb6b5118 10ms elapsed
DBG:tls_openssl:openssl_tls_update_fd: New fd is 5

ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
1.2.3.4:34463 failed
ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
err=Success(0)
ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure
ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!

DBG:proto_tls:proto_tls_send: Successfully started async SSL connection
DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 0 5
(0x55fd3f789ae0, 5, 0, 0x10,0x3) fd_no=5 called
DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -2, fd=5,
id=1228827518
DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
DBG:tm:insert_timer_unsafe: [0]: 0x7f83eb6a9320 (12)
DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -3, fd=-1,
id=1228827518
DBG:tm:t_relay_to: new transaction fwd'ed
DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
DBG:tm:do_t_cleanup: transaction 0x7f83eb6a90d0 already updated! Skipping
update!
DBG:tm:t_unref: UNREF_UNSAFE: [0x7f83eb6a90d0] after is 0
DBG:core:destroy_avp_list: destroying list (nil)
DBG:core:receive_msg: cleaning up
DBG:proto_tls:tls_read_req: tls_read_req end
DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -3 from tcp worker 0 (1)
DBG:core:tcpconn_destroy: delaying (0x7f83eb6b5118, flags 0038) ref = 1 ...
DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -2 from tcp worker 0 (0)
DBG:core:tcpconn_destroy: destroying connection 0x7f83eb6b5118, flags 0038
DBG:tls_openssl:openssl_tls_update_fd: New fd is 119
DBG:tm:utimer_routine: timer routine:4,tl=0x7f83eb6a5d18 next=(nil),
timeout=7700000
DBG:tm:retransmission_handler: retransmission_handler : request resending
(t=0x7f83eb6a5af8, PUBLISH s ... )
root at devang-MS-7817:/usr/local/etc/opensips/range#

I am following this OpenSIPS TLS config:

socket=udp:1.2.3.4: <http://192.168.0.105:506/>5060

socket=tcp:1.2.3.4: <http://192.168.0.105:506/>5060

socket=tls:1.2.3.4: <http://192.168.0.105:506>5061

loadmodule "tls_openssl.so"


loadmodule "tls_mgm.so"
# -------- TLS SERVER Certificate ---------#
modparam("tls_mgm", "server_domain", "dom1")
modparam("tls_mgm", "match_sip_domain", "[dom1]devang.com")
modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5061")
modparam("tls_mgm", "verify_cert", "[dom1]0")
modparam("tls_mgm", "require_cert", "[dom1]0")
modparam("tls_mgm", "tls_method", "[dom1]-")
modparam("tls_mgm", "certificate",
"[dom1]/usr/local/etc/opensips/tls/rootCA/ca_cert.pem")
modparam("tls_mgm", "private_key",
"[dom1]/usr/local/etc/opensips/tls/rootCA/private_key.pem")

# --------- TLS CLIENT CERTIFICATE --------#
modparam("tls_mgm", "client_domain", "dom2")
modparam("tls_mgm", "match_sip_domain", "[dom2]*")
modparam("tls_mgm", "match_ip_address", "[dom2]*")
modparam("tls_mgm", "verify_cert", "[dom2]0")
modparam("tls_mgm", "require_cert", "[dom2]0")
modparam("tls_mgm", "tls_method", "[dom2]-")
modparam("tls_mgm", "certificate",
"[dom2]/usr/local/etc/opensips/tls/user/user-cert.pem")
modparam("tls_mgm", "private_key",
"[dom2]/usr/local/etc/opensips/tls/user/user-privkey.pem")
modparam("tls_mgm", "ca_list",
"[dom2]/usr/local/etc/opensips/tls/user/user-calist.pem")


loadmodule "proto_tls.so"

checking the connection with s_client shows below :

openssl s_client -showcerts -debug -connect 1.2.3.4:5061 -bugs
CONNECTED(00000005)
140510082113984:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 517 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)


Can anyone tell me what I might be missing for tls config or Please advise
how to resolve this SSL handshake failure.


Many Thanks
Devang


                                                        70,1          15%

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211109/02e7acc1/attachment-0001.html>

From farmorg at gmail.com  Tue Nov  9 14:43:04 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Tue, 9 Nov 2021 14:43:04 +0000
Subject: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine
In-Reply-To: <c2ecf4bf-26f2-f90b-bc81-f4644561672e@opensips.org>
References: <15a401d748b4$fb1b9140$f152b3c0$@web.de>
 <02b701d74ca2$574e6f50$05eb4df0$@web.de>
 <0e9c01d75208$6e827b60$4b877220$@web.de>
 <CAFGRPVrEEhtK=4-wyLXQZ+OmkFU2rN5-nMbkzUDgN=2fa=5Cvg@mail.gmail.com>
 <c2ecf4bf-26f2-f90b-bc81-f4644561672e@opensips.org>
Message-ID: <CAOvQDetX7D1bCuM12DJPt5+LZcO10LQHeA4b4KxnAv5QhxM6jA@mail.gmail.com>

Hi Razvan/Everyone!

I too would love to see examples where people have done this. I am using
RTPEngine and am looking at using the B2BUA module to handle REFER's.

With regards to using the keys in subsequent requests/replies - are you
suggesting to use the extra_hrds() & extra_hdr_bodies() variables to
reconstruct the to/from/call-id headers before sending the request out?

Best regards
Mark.




On Wed, 2 Jun 2021 at 08:47, Răzvan Crainea <razvan at opensips.org> wrote:

> Hi, Xaled!
>
> You can engange RTPengine for a B2B session, however you will have to
> make sure that you are using the correct callid/from-tag/to-tag for the
> entire communication to RTPengine. To do so, I would recommend you start
> with a rtengine_offer() for the initial invite, then store the
> callid/from-tag/to-tag in the $b2b_logic.ctx [1], and use those keys in
> all the sequential requests/replies.
>
> [1] https://opensips.org/docs/modules/3.2.x/b2b_logic.html#b2b_logic.ctx
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Core Developer
> http://www.opensips-solutions.com
>
> On 5/26/21 12:27 PM, David Villasmil wrote:
> > Are you 100% sure opensips can “talk” to rtpengine? How do you know?
> >
> > On Wed, 26 May 2021 at 09:24, <xaled at web.de <mailto:xaled at web.de>>
> wrote:
> >
> >     Apologies for keep on bugging on this issue, but would really
> >     appreciate any hints.
> >
> >     -----Original Message-----
> >     From: Users <users-bounces at lists.opensips.org
> >     <mailto:users-bounces at lists.opensips.org>> On Behalf Of xaled at web.de
> >     <mailto:xaled at web.de>
> >     Sent: Wednesday, May 19, 2021 1:30 PM
> >     To: 'OpenSIPS users mailling list' <users at lists.opensips.org
> >     <mailto:users at lists.opensips.org>>
> >     Subject: Re: [OpenSIPS-Users] opensips 3.2 B2B module and
> >     RTPProxy/RTPEngine
> >
> >     Hi
> >
> >     Would appreciate any hints on how to run the new 3.2 B2B module with
> >     RTPProxy or RTPEngine.
> >
> >     Thanks,
> >     Xaled
> >     -----Original Message-----
> >     From: Users <users-bounces at lists.opensips.org
> >     <mailto:users-bounces at lists.opensips.org>> On Behalf Of xaled at web.de
> >     <mailto:xaled at web.de>
> >     Sent: Friday, May 14, 2021 1:34 PM
> >     To: 'OpenSIPS users mailling list' <users at lists.opensips.org
> >     <mailto:users at lists.opensips.org>>
> >     Subject: [OpenSIPS-Users] opensips 3.2 B2B module and
> RTPProxy/RTPEngine
> >
> >     Hi,
> >
> >     Are the any examples of using the new B2B module in 3.2 with
> >     RTPProxy or RTPEngine? I tried adding _offer and _answer call
> >     accordingly but never saw RTPProxy or RTPEngine engaged.
> >
> >     Even a simple example for A-B call with B2B and RTPEngine would be
> >     much appreciated.
> >
> >     Thanks,
> >     Xaled
> >
> >
> >     _______________________________________________
> >     Users mailing list
> >     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> >     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >     <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
> >     <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
> >     <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
> >
> > --
> > Regards,
> >
> > David Villasmil
> > email: david.villasmil.work at gmail.com
> > <mailto:david.villasmil.work at gmail.com>
> > phone: +34669448337
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


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

From david.villasmil.work at gmail.com  Wed Nov 10 00:35:48 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Wed, 10 Nov 2021 00:35:48 +0000
Subject: [OpenSIPS-Users] drouting gw list
Message-ID: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>

Hello folks,

i have the following gw_list

PrimaryGW=100,SecondaryGW=10

I'm seeing calls going to the SecondaryGW.
How should i set this if i only want the SecondaryGW to be used for
failover?

Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211110/07d5882b/attachment.html>

From Ben.Newlin at genesys.com  Wed Nov 10 02:55:30 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Wed, 10 Nov 2021 02:55:30 +0000
Subject: [OpenSIPS-Users] drouting gw list
In-Reply-To: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
References: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
Message-ID: <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>

David,

Is this gw_list defined on a dr_rule or a dr_carrier? What is the value of the sort_alg column for that dr_rule/dr_carrier? If the sort_alg is set to W, then the assigned values are interpreted as weights. So with this configuration it would send 100 out of 110 calls to PrimaryGW and 10 out of 110 calls to SecondaryGW.

If you don’t want to use the SecondaryGW except for failover you should not use weighted routing, so you should set the sort_alg column to N.

https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of David Villasmil <david.villasmil.work at gmail.com>
Date: Tuesday, November 9, 2021 at 7:37 PM
To: users at lists.opensips.org <users at lists.opensips.org>
Subject: [OpenSIPS-Users] drouting gw list
Hello folks,

i have the following gw_list

PrimaryGW=100,SecondaryGW=10

I'm seeing calls going to the SecondaryGW.
How should i set this if i only want the SecondaryGW to be used for failover?

Regards,

David Villasmil
email: david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211110/b78ee7ab/attachment.html>

From fengz.strong at gmail.com  Wed Nov 10 11:53:16 2021
From: fengz.strong at gmail.com (=?utf-8?B?5byg5rC46ZSL?=)
Date: Wed, 10 Nov 2021 19:53:16 +0800
Subject: [OpenSIPS-Users] Event E_QROUTING_BAD_DST will not be triggered
Message-ID: <09EBB86E-762A-4452-8A4B-98499C3709CF@gmail.com>

Hi, guys

I use module qrouting of opensips which version is 3.2.3.
Now I have two problems and need help.

1. Event E_QROUTING_BAD_DST will not be triggered.
2. If a call ends by 480, ASR(Answer Serizure Ratio) and CCR(Call Completion Ratio) will be counted twice.

About question 2, use cmd "opensips-cli -x mi qr_status"
(opensips-cli): mi qr_status
{
    "Partitions": [
        {
            "Name": "Default",
            "Rules": [
                {
                    "Id": 1,
                    "Destinations": [
                        {
                            "Gateway": {
                                "GWID": "outbound_03",
                                "ASR": "-1.00/2", // I only made one call, so I expect it to be counted only once
                                "CCR": "-1.00/2",
                                "PDD": "-1.00/0",
                                "AST": "-1.00/0",
                                "ACD": "-1.00/0"
                            }
                        }
                    ]
                }
            ]
        }
    ]
}
And，this call is request from gateway which is not outbound_03. In other words, inbound and outbound gw are different.

Some configuration files are as follows:
...
115 loadmodule "qrouting.so"
116 modparam("qrouting", "db_url", "mysql://opensips:opensipsrw at 192.168.88.130:3306/opensips")
117 modparam("qrouting", "event_bad_dst_threshold", "1")
...
126 route {
...
243     # dynamic routing
244     xlog("before: $ru\n");
245     if (!do_routing(1)) {
246         # do lookup with method filtering
247         if (!lookup("location","m")) {
248             t_reply(404, "Not Found");
249             exit;
250         }
251     } else {
252         xlog("after: $ru\n");
253     }
258 }

299 event_route[E_QROUTING_BAD_DST] {
300     xlog("test\n");
301 }

Any suggestions will be thankful.

From david.villasmil.work at gmail.com  Wed Nov 10 12:49:36 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Wed, 10 Nov 2021 12:49:36 +0000
Subject: [OpenSIPS-Users] drouting gw list
In-Reply-To: <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>
References: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
 <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>
Message-ID: <CAFGRPVoL+sHr=Fc2dNXGeET9gh2MzqdX0u8GzhA4+8fa_0+3tA@mail.gmail.com>

Sorry,

it's defined in cr_carriers, that's the list of gws which are then defined
on dr_gateways.
The "flags" field is "1", which i take to mean weight-based (this is
opensips 2.4)
So i would need to set the flags to "2"?
Regards,

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


On Wed, Nov 10, 2021 at 2:56 AM Ben Newlin <Ben.Newlin at genesys.com> wrote:

> David,
>
>
>
> Is this gw_list defined on a dr_rule or a dr_carrier? What is the value of
> the sort_alg column for that dr_rule/dr_carrier? If the sort_alg is set to
> W, then the assigned values are interpreted as weights. So with this
> configuration it would send 100 out of 110 calls to PrimaryGW and 10 out of
> 110 calls to SecondaryGW.
>
>
>
> If you don’t want to use the SecondaryGW except for failover you should
> not use weighted routing, so you should set the sort_alg column to N.
>
>
>
> https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of David
> Villasmil <david.villasmil.work at gmail.com>
> *Date: *Tuesday, November 9, 2021 at 7:37 PM
> *To: *users at lists.opensips.org <users at lists.opensips.org>
> *Subject: *[OpenSIPS-Users] drouting gw list
>
> Hello folks,
>
>
>
> i have the following gw_list
>
>
>
> PrimaryGW=100,SecondaryGW=10
>
>
>
> I'm seeing calls going to the SecondaryGW.
>
> How should i set this if i only want the SecondaryGW to be used for
> failover?
>
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.work at gmail.com
>
> phone: +34669448337
> _______________________________________________
> 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/20211110/e4d67bb4/attachment-0001.html>

From Ben.Newlin at genesys.com  Wed Nov 10 14:05:35 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Wed, 10 Nov 2021 14:05:35 +0000
Subject: [OpenSIPS-Users] drouting gw list
In-Reply-To: <CAFGRPVoL+sHr=Fc2dNXGeET9gh2MzqdX0u8GzhA4+8fa_0+3tA@mail.gmail.com>
References: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
 <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>
 <CAFGRPVoL+sHr=Fc2dNXGeET9gh2MzqdX0u8GzhA4+8fa_0+3tA@mail.gmail.com>
Message-ID: <BN0PR10MB52084B36DFC55EACDBDD682795939@BN0PR10MB5208.namprd10.prod.outlook.com>

Yes, in 2.4 it is controlled by the flags. If you set it to 2 it will only ever use the first gateway and there will be no failover. If you want to allow for failover and use the gateways in the order they are defined you should not set any flags.

https://opensips.org/docs/modules/2.4.x/drouting.html#idp163040

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of David Villasmil <david.villasmil.work at gmail.com>
Date: Wednesday, November 10, 2021 at 7:50 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] drouting gw list
Sorry,

it's defined in cr_carriers, that's the list of gws which are then defined on dr_gateways.
The "flags" field is "1", which i take to mean weight-based (this is opensips 2.4)
So i would need to set the flags to "2"?
Regards,

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


On Wed, Nov 10, 2021 at 2:56 AM Ben Newlin <Ben.Newlin at genesys.com<mailto:Ben.Newlin at genesys.com>> wrote:
David,

Is this gw_list defined on a dr_rule or a dr_carrier? What is the value of the sort_alg column for that dr_rule/dr_carrier? If the sort_alg is set to W, then the assigned values are interpreted as weights. So with this configuration it would send 100 out of 110 calls to PrimaryGW and 10 out of 110 calls to SecondaryGW.

If you don’t want to use the SecondaryGW except for failover you should not use weighted routing, so you should set the sort_alg column to N.

https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES<https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES>

Ben Newlin

From: Users <users-bounces at lists.opensips.org<mailto:users-bounces at lists.opensips.org>> on behalf of David Villasmil <david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>>
Date: Tuesday, November 9, 2021 at 7:37 PM
To: users at lists.opensips.org<mailto:users at lists.opensips.org> <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: [OpenSIPS-Users] drouting gw list
Hello folks,

i have the following gw_list

PrimaryGW=100,SecondaryGW=10

I'm seeing calls going to the SecondaryGW.
How should i set this if i only want the SecondaryGW to be used for failover?

Regards,

David Villasmil
email: david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>
phone: +34669448337
_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211110/9bffe85d/attachment.html>

From david.villasmil.work at gmail.com  Wed Nov 10 16:11:44 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Wed, 10 Nov 2021 16:11:44 +0000
Subject: [OpenSIPS-Users] drouting gw list
In-Reply-To: <BN0PR10MB52084B36DFC55EACDBDD682795939@BN0PR10MB5208.namprd10.prod.outlook.com>
References: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
 <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>
 <CAFGRPVoL+sHr=Fc2dNXGeET9gh2MzqdX0u8GzhA4+8fa_0+3tA@mail.gmail.com>
 <BN0PR10MB52084B36DFC55EACDBDD682795939@BN0PR10MB5208.namprd10.prod.outlook.com>
Message-ID: <CAFGRPVq-1AHWbY2+5N8MtK7eG_DAdTgB6EAtHZ5Aa6JmznqG8A@mail.gmail.com>

Thanks again Ben,

I'm still not understanding: Setting it to <NULL> (as is, nothing)
would then only send to the first gw, and only to the second on failure?

Regards,

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


On Wed, Nov 10, 2021 at 2:06 PM Ben Newlin <Ben.Newlin at genesys.com> wrote:

> Yes, in 2.4 it is controlled by the flags. If you set it to 2 it will only
> ever use the first gateway and there will be no failover. If you want to
> allow for failover and use the gateways in the order they are defined you
> should not set any flags.
>
>
>
> https://opensips.org/docs/modules/2.4.x/drouting.html#idp163040
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of David
> Villasmil <david.villasmil.work at gmail.com>
> *Date: *Wednesday, November 10, 2021 at 7:50 AM
> *To: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] drouting gw list
>
> Sorry,
>
>
>
> it's defined in cr_carriers, that's the list of gws which are then defined
> on dr_gateways.
>
> The "flags" field is "1", which i take to mean weight-based (this is
> opensips 2.4)
>
> So i would need to set the flags to "2"?
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.work at gmail.com
>
> phone: +34669448337
>
>
>
>
>
> On Wed, Nov 10, 2021 at 2:56 AM Ben Newlin <Ben.Newlin at genesys.com> wrote:
>
> David,
>
>
>
> Is this gw_list defined on a dr_rule or a dr_carrier? What is the value of
> the sort_alg column for that dr_rule/dr_carrier? If the sort_alg is set to
> W, then the assigned values are interpreted as weights. So with this
> configuration it would send 100 out of 110 calls to PrimaryGW and 10 out of
> 110 calls to SecondaryGW.
>
>
>
> If you don’t want to use the SecondaryGW except for failover you should
> not use weighted routing, so you should set the sort_alg column to N.
>
>
>
> https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of David
> Villasmil <david.villasmil.work at gmail.com>
> *Date: *Tuesday, November 9, 2021 at 7:37 PM
> *To: *users at lists.opensips.org <users at lists.opensips.org>
> *Subject: *[OpenSIPS-Users] drouting gw list
>
> Hello folks,
>
>
>
> i have the following gw_list
>
>
>
> PrimaryGW=100,SecondaryGW=10
>
>
>
> I'm seeing calls going to the SecondaryGW.
>
> How should i set this if i only want the SecondaryGW to be used for
> failover?
>
>
> Regards,
>
>
>
> David Villasmil
>
> email: david.villasmil.work at gmail.com
>
> phone: +34669448337
>
> _______________________________________________
> 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/20211110/6eeffeec/attachment-0001.html>

From Ben.Newlin at genesys.com  Wed Nov 10 16:16:00 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Wed, 10 Nov 2021 16:16:00 +0000
Subject: [OpenSIPS-Users] drouting gw list
In-Reply-To: <CAFGRPVq-1AHWbY2+5N8MtK7eG_DAdTgB6EAtHZ5Aa6JmznqG8A@mail.gmail.com>
References: <CAFGRPVqYUVLANOsEuj+NTa_xJW2rd1A2RcEqwJvYC94543GHBw@mail.gmail.com>
 <BN0PR10MB52089B10B860420036A072E095939@BN0PR10MB5208.namprd10.prod.outlook.com>
 <CAFGRPVoL+sHr=Fc2dNXGeET9gh2MzqdX0u8GzhA4+8fa_0+3tA@mail.gmail.com>
 <BN0PR10MB52084B36DFC55EACDBDD682795939@BN0PR10MB5208.namprd10.prod.outlook.com>
 <CAFGRPVq-1AHWbY2+5N8MtK7eG_DAdTgB6EAtHZ5Aa6JmznqG8A@mail.gmail.com>
Message-ID: <BN0PR10MB5208AD7BA572374B80F63CEE95939@BN0PR10MB5208.namprd10.prod.outlook.com>

Yes, the default behavior without any flags is to use the GWs in the order they are defined in the DB. So if they are in the DB as

primaryGW,secondaryGW

then the primaryGW will always be selected first, and secondaryGW will only be used if you perform failover in the script, with something like use_next_gw().

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of David Villasmil <david.villasmil.work at gmail.com>
Date: Wednesday, November 10, 2021 at 11:14 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] drouting gw list
Thanks again Ben,

I'm still not understanding: Setting it to <NULL> (as is, nothing) would then only send to the first gw, and only to the second on failure?

Regards,

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


On Wed, Nov 10, 2021 at 2:06 PM Ben Newlin <Ben.Newlin at genesys.com<mailto:Ben.Newlin at genesys.com>> wrote:
Yes, in 2.4 it is controlled by the flags. If you set it to 2 it will only ever use the first gateway and there will be no failover. If you want to allow for failover and use the gateways in the order they are defined you should not set any flags.

https://opensips.org/docs/modules/2.4.x/drouting.html#idp163040<https://opensips.org/docs/modules/2.4.x/drouting.html#idp163040>

Ben Newlin

From: Users <users-bounces at lists.opensips.org<mailto:users-bounces at lists.opensips.org>> on behalf of David Villasmil <david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>>
Date: Wednesday, November 10, 2021 at 7:50 AM
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] drouting gw list
Sorry,

it's defined in cr_carriers, that's the list of gws which are then defined on dr_gateways.
The "flags" field is "1", which i take to mean weight-based (this is opensips 2.4)
So i would need to set the flags to "2"?
Regards,

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


On Wed, Nov 10, 2021 at 2:56 AM Ben Newlin <Ben.Newlin at genesys.com<mailto:Ben.Newlin at genesys.com>> wrote:
David,

Is this gw_list defined on a dr_rule or a dr_carrier? What is the value of the sort_alg column for that dr_rule/dr_carrier? If the sort_alg is set to W, then the assigned values are interpreted as weights. So with this configuration it would send 100 out of 110 calls to PrimaryGW and 10 out of 110 calls to SecondaryGW.

If you don’t want to use the SecondaryGW except for failover you should not use weighted routing, so you should set the sort_alg column to N.

https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES<https://www.opensips.org/Documentation/Install-DBSchema-3-2#GEN-DB-DR-RULES>

Ben Newlin

From: Users <users-bounces at lists.opensips.org<mailto:users-bounces at lists.opensips.org>> on behalf of David Villasmil <david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>>
Date: Tuesday, November 9, 2021 at 7:37 PM
To: users at lists.opensips.org<mailto:users at lists.opensips.org> <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: [OpenSIPS-Users] drouting gw list
Hello folks,

i have the following gw_list

PrimaryGW=100,SecondaryGW=10

I'm seeing calls going to the SecondaryGW.
How should i set this if i only want the SecondaryGW to be used for failover?

Regards,

David Villasmil
email: david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>
phone: +34669448337
_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<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<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211110/07e741c9/attachment.html>

From rosenberg11219 at gmail.com  Wed Nov 10 19:16:17 2021
From: rosenberg11219 at gmail.com (Schneur Rosenberg)
Date: Wed, 10 Nov 2021 21:16:17 +0200
Subject: [OpenSIPS-Users] Load balancer probing_method INVITE not sending
	contact header
Message-ID: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>

Hi, I'm using load balancer with probing_method INVITE, it worked fine
for many years with my Asterisk and Freeswitch servers, I'm migrating
my asterisk server from chan_sip to pjsip and now asterisk is
rejecting all the probing requests with a 400 Missing Contact header,
I checked the modparams for the  "load_balancer" module but couldn't
find how to have OpenSIPs add the contact header.

S. Rosenberg


From vasilios.tzanoudakis at voiceland.gr  Wed Nov 10 19:36:33 2021
From: vasilios.tzanoudakis at voiceland.gr (Vasilios Tzanoudakis)
Date: Wed, 10 Nov 2021 21:36:33 +0200
Subject: [OpenSIPS-Users] Load balancer probing_method INVITE not
 sending contact header
In-Reply-To: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>
References: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>
Message-ID: <CADTki+DVudMCFSFPP2HCuDjeEYjz-qrnNiwyRHyAWdvaxOvq5Q@mail.gmail.com>

Have you tried adding the extra contact header in local_route?

Στις Τετ, 10 Νοε 2021, 21:18 ο χρήστης Schneur Rosenberg <
rosenberg11219 at gmail.com> έγραψε:

> Hi, I'm using load balancer with probing_method INVITE, it worked fine
> for many years with my Asterisk and Freeswitch servers, I'm migrating
> my asterisk server from chan_sip to pjsip and now asterisk is
> rejecting all the probing requests with a 400 Missing Contact header,
> I checked the modparams for the  "load_balancer" module but couldn't
> find how to have OpenSIPs add the contact header.
>
> S. Rosenberg
>
> _______________________________________________
> 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/20211110/48f1aadb/attachment.html>

From rosenberg11219 at gmail.com  Wed Nov 10 19:47:08 2021
From: rosenberg11219 at gmail.com (Schneur Rosenberg)
Date: Wed, 10 Nov 2021 21:47:08 +0200
Subject: [OpenSIPS-Users] Load balancer probing_method INVITE not
 sending contact header
In-Reply-To: <CADTki+DVudMCFSFPP2HCuDjeEYjz-qrnNiwyRHyAWdvaxOvq5Q@mail.gmail.com>
References: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>
 <CADTki+DVudMCFSFPP2HCuDjeEYjz-qrnNiwyRHyAWdvaxOvq5Q@mail.gmail.com>
Message-ID: <CANvjR0WJbcezLfLAwSAO8vR_8Ebh0jKnedC7K4FaQaStgx-M=w@mail.gmail.com>

No, I'll try and keep you posted.

On Wed, Nov 10, 2021 at 9:39 PM Vasilios Tzanoudakis
<vasilios.tzanoudakis at voiceland.gr> wrote:
>
> Have you tried adding the extra contact header in local_route?
>
> Στις Τετ, 10 Νοε 2021, 21:18 ο χρήστης Schneur Rosenberg <rosenberg11219 at gmail.com> έγραψε:
>>
>> Hi, I'm using load balancer with probing_method INVITE, it worked fine
>> for many years with my Asterisk and Freeswitch servers, I'm migrating
>> my asterisk server from chan_sip to pjsip and now asterisk is
>> rejecting all the probing requests with a 400 Missing Contact header,
>> I checked the modparams for the  "load_balancer" module but couldn't
>> find how to have OpenSIPs add the contact header.
>>
>> S. Rosenberg
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From aronp at guaranteedplus.com  Wed Nov 10 19:57:00 2021
From: aronp at guaranteedplus.com (Podrigal, Aron)
Date: Wed, 10 Nov 2021 13:57:00 -0600
Subject: [OpenSIPS-Users] Opensips segfault after adding acc_extra field
In-Reply-To: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>
References: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>
Message-ID: <CANJp-yi6w2O1sqCHtycATJa8Ve3Xq6gYDujcBFtC0im4KrQPZg@mail.gmail.com>

Hi Core Devs,

Any idea or direction on how to handle this?


For now,
I think of the best way to handle this as a workaround, to spin up a new
instance and reroute all traffic temporarily until all ongoing dialogs are
completed, and then restart.

But this is really important, as it makes it very difficult to deploy
changes to acc...


On Wed, Nov 3, 2021, 8:17 PM Podrigal, Aron <aronp at guaranteedplus.com>
wrote:

> Hi
>
> I added another field to my acc_extra and after restarting opensips, it
> kept crashing right away after the restart.
>
> Here are the relevant log lines
>
> I got a thousand lines saying
> Nov 03 20:48:03 snap-p1 opensips-snap[1636]: WARNING:acc:restore_extra:
> extra tags were added/removed since last run!won't restore values!
>
> Then 2 - 3 lines afterwards
>
> Nov 03 20:48:04 p1 opensips[1651]: CRITICAL:core:sig_usr: segfault in
> process pid: 1651, id: 7
> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: child process
> 1651 exited by a signal 11
> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: core was not
> generated
> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: terminating due
> to SIGCHLD
> Nov 03 20:48:04 p1 opensips[1643]: INFO:core:sig_usr: signal 15 received
> Nov 03 20:48:04 p1 opensips[1642]: INFO:core:sig_usr: signal 15 received
>
> I use opensips version 3.1 Rev 5cdfedebbe0
>
> Any idea what can be causing this?
>
> I have 2 acc targets one db and one log. And I added the acc_extra field
> only to the log.
>
>
> Thanks
>
>
> --
>
> -
> Aron Podrigal
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211110/a8557b5b/attachment.html>

From fengz.strong at gmail.com  Thu Nov 11 09:41:52 2021
From: fengz.strong at gmail.com (=?UTF-8?B?5byg5rC46ZSL?=)
Date: Thu, 11 Nov 2021 17:41:52 +0800
Subject: [OpenSIPS-Users] Event E_QROUTING_BAD_DST will not be triggered
Message-ID: <CAJZ_pShYrOfyonH+z-O5exbePJLjRO6-ZFybdkZNsjvHmOfnsg@mail.gmail.com>

Hi, guys

Why the tm module's callback registered at grouting is triggered twice？
Will this cause ASR and CCR to be counted twice？

Below is some logs:

Nov 11 16:45:38 [128103] DBG:core:parse_headers: flags=18
Nov 11 16:45:38 [128103] DBG:tm:build_local: using FROM=<From: "" <
sip:lexin at 192.168.88.128:5060>;tag=HByBDaar568Fg
>, TO=<To: <sip:123123 at 192.168.88.128:5060>;tag=jmQ4e5tU2FZ2B
>, CSEQ_N=<CSeq: 43756375>
Nov 11 16:45:38 [128103] DBG:tm:run_trans_callbacks: trans=0x7f3f73f10a80,
callback type 2, id 4 entered
*!!!!!!!!!!!!!!!!!!!Nov 11 16:45:38 [128103]
DBG:qrouting:qr_check_reply_tmcb: tm reply (480) from gw outbound_03*
Nov 11 16:45:38 [128103] DBG:tm:run_trans_callbacks: trans=0x7f3f73f10a80,
callback type 2, id 0 entered
Nov 11 16:45:38 [128103] DBG:core:parse_headers: flags=8
Nov 11 16:45:38 [128103] incoming reply
Nov 11 16:45:38 [128103] DBG:tm:t_should_relay_response: T_code=100,
new_code=480
Nov 11 16:45:38 [128103] DBG:tm:t_pick_branch: picked branch 0, code 480
(prio=680)
Nov 11 16:45:38 [128103] DBG:tm:is_3263_failure: dns-failover test:
branch=0, last_recv=480, flags=2
Nov 11 16:45:38 [128103] DBG:tm:run_trans_callbacks: trans=0x7f3f73f10a80,
callback type 32, id 4 entered
*!!!!!!!!!!!!!!!!!!Nov 11 16:45:38 [128103]
DBG:qrouting:qr_check_reply_tmcb: tm reply (480) from gw outbound_03*
Nov 11 16:45:38 [128103] DBG:tm:run_trans_callbacks: trans=0x7f3f73f10a80,
callback type 32, id 0 entered
Nov 11 16:45:38 [128103] DBG:acc:acc_log_request: no legs
Nov 11 16:45:38 [128103] ACC: call missed:
timestamp=1636620338;created=0;setuptime=1636620338;method=INVITE;from_tag=HByBDaar568Fg;to_tag=jmQ4e5tU2FZ2B;call_id=9413f61e-bd6e-123a-9693-000c2953568c;code=480;reason=Temporarily
Unavailable
Nov 11 16:45:38 [128103] DBG:tm:clean_msg_clone: removing hdr->parsed 7
Nov 11 16:45:38 [128103] DBG:tm:relay_reply: T_state=4, branch=0, save=0,
relay=0, cancel_BM=0
Nov 11 16:45:38 [128103] DBG:tm:run_trans_callbacks: trans=0x7f3f73f10a80,
callback type 8, id 1 entered
Nov 11 16:45:38 [128103] DBG:dialog:push_reply_in_dialog: 0x7f3f73f12f10
totag in rpl 480 is <jmQ4e5tU2FZ2B> (13)
Nov 11 16:45:38 [128103] DBG:dialog:push_reply_in_dialog: new branch with
tag <jmQ4e5tU2FZ2B>, leg_idx=1
Nov 11 16:45:38 [128103] DBG:dialog:update_leg_info: route_set , contact ,
cseq 43756375 and bind_addr udp:192.168.88.128:5060
Nov 11 16:45:38 [128103] DBG:core:parse_headers: flags=ffffffffffffffff
Nov 11 16:45:38 [128103] DBG:dialog:dlg_update_leg_info: set leg 1 for
0x7f3f73f12f10: tag=<jmQ4e5tU2FZ2B> rcseq=<43756375>
Nov 11 16:45:38 [128103] DBG:core:parse_headers: flags=ffffffffffffffff
Nov 11 16:45:38 [128103] DBG:core:build_res_buf_from_sip_res:  old size:
873, new size: 805
Nov 11 16:45:38 [128103] DBG:core:build_res_buf_from_sip_res: copied size:
orig:105, new: 805, rest: 768 msg=

Best regards,

byron zhang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211111/23a82585/attachment-0001.html>

From rosenberg11219 at gmail.com  Thu Nov 11 11:38:16 2021
From: rosenberg11219 at gmail.com (Schneur Rosenberg)
Date: Thu, 11 Nov 2021 13:38:16 +0200
Subject: [OpenSIPS-Users] Load balancer probing_method INVITE not
 sending contact header
In-Reply-To: <CANvjR0WJbcezLfLAwSAO8vR_8Ebh0jKnedC7K4FaQaStgx-M=w@mail.gmail.com>
References: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>
 <CADTki+DVudMCFSFPP2HCuDjeEYjz-qrnNiwyRHyAWdvaxOvq5Q@mail.gmail.com>
 <CANvjR0WJbcezLfLAwSAO8vR_8Ebh0jKnedC7K4FaQaStgx-M=w@mail.gmail.com>
Message-ID: <CANvjR0VawtvEP5A291vrGUMdM4F1=N-0Eb+fdK95mqBD0BcENg@mail.gmail.com>

Hi, thank you very much that fixed the error but then it's complained with
a 484 Address Incomplete, I fixed the RURI too and now it's working fine.

Scott

On Wed, Nov 10, 2021, 21:47 Schneur Rosenberg <rosenberg11219 at gmail.com>
wrote:

> No, I'll try and keep you posted.
>
> On Wed, Nov 10, 2021 at 9:39 PM Vasilios Tzanoudakis
> <vasilios.tzanoudakis at voiceland.gr> wrote:
> >
> > Have you tried adding the extra contact header in local_route?
> >
> > Στις Τετ, 10 Νοε 2021, 21:18 ο χρήστης Schneur Rosenberg <
> rosenberg11219 at gmail.com> έγραψε:
> >>
> >> Hi, I'm using load balancer with probing_method INVITE, it worked fine
> >> for many years with my Asterisk and Freeswitch servers, I'm migrating
> >> my asterisk server from chan_sip to pjsip and now asterisk is
> >> rejecting all the probing requests with a 400 Missing Contact header,
> >> I checked the modparams for the  "load_balancer" module but couldn't
> >> find how to have OpenSIPs add the contact header.
> >>
> >> S. Rosenberg
> >>
> >> _______________________________________________
> >> 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/20211111/c2876610/attachment.html>

From greg at switchtel.co.za  Thu Nov 11 13:56:21 2021
From: greg at switchtel.co.za (Gregory Massel)
Date: Thu, 11 Nov 2021 15:56:21 +0200
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
Message-ID: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>

I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.

With WolfSSL it segfaults:

Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
ef 5b 48 8d 3d d7
Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.

With OpenSSL it remains running, however, is still extremely unhappy:

Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0

I didn't have these issues with OpenSIPS 3.1, however, am not sure how 
to downgrade as, when I do, it complains that the database table 
structure is not suitable and there does not appear to be a migration 
script to revert to an older version.


-- 
Regards
*Gregory Massel*
*T* +27 87 550 0000
*F* +27 11 783 4877
*W* www.switchtel.co.za <http://www.switchtel.co.za/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211111/775638c4/attachment-0001.html>

From greg at switchtel.co.za  Thu Nov 11 14:30:38 2021
From: greg at switchtel.co.za (Gregory Massel)
Date: Thu, 11 Nov 2021 16:30:38 +0200
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
Message-ID: <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>

I've managed to downgrade to 3.2.2 and all is working again. So this 
appears to be a bug introduced in 3.2.3.

Environment is:

Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22 
09:25:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

The downgrade/fix was with:

apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1 
opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1 
opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1 
opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1 
opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1

--Greg

On 2021-11-11 15:56, Gregory Massel wrote:
>
> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>
> With WolfSSL it segfaults:
>
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
> ef 5b 48 8d 3d d7
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
> With OpenSSL it remains running, however, is still extremely unhappy:
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>
> I didn't have these issues with OpenSIPS 3.1, however, am not sure how 
> to downgrade as, when I do, it complains that the database table 
> structure is not suitable and there does not appear to be a migration 
> script to revert to an older version.
>
>
> -- 
> Regards
> *Gregory Massel*
> *T* +27 87 550 0000
> *F* +27 11 783 4877
> *W* www.switchtel.co.za <http://www.switchtel.co.za/>
>
> _______________________________________________
> 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/20211111/cf576ff5/attachment.html>

From farmorg at gmail.com  Thu Nov 11 14:51:02 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 11 Nov 2021 14:51:02 +0000
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
Message-ID: <CAOvQDeta6Vhb+c1QUt_QCprd6oRU+kez4Enm7WYjQfA6K6+AxQ@mail.gmail.com>

Weirdly I started seeing this yesterday and I have not found a solution yet.
I am trying to get a core dump which is not working for some reason but
this is the sanitized log from my server:

INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to
52.114.75.24:5061 established
NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
ERROR:core:io_watch_add: [TCP_main] epoll_ctl ADD failed: Bad file
descriptor [9]
INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to
52.114.132.46:5061 established
CRITICAL:core:sig_usr: segfault in process pid: 6055, id: 12
NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to
52.114.32.169:5061 established
NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from
52.114.132.46:7040 accepted
INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate
subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft
Corporation/CN=Microsoft RSA TLS CA 02
request_route: Received OPTIONS from 52.114.132.46
request_route: - checking 52.114.132.46:7040
request_route: - OPTIONS FROM Microsoft
request_route: sip OPTIONS from Microsoft, logging contact header
request_route: Contact Header = <sip:sip-du-a-us.pstnhub.microsoft.com:5061>
request_route: Logging Message Buffer: OPTIONS
sip:my.domain.com:5061;transport=tls
SIP/2.0#015#012FROM:
<sip:sip-du-a-us.pstnhub.microsoft.com:5061>;tag=9ca48371-0c0f-4526-a573-078118b77b12#015#012TO:
<sip:my.domain.com:5061;transport=tls>#0
15#012CSEQ: 1 OPTIONS#015#012CALL-ID:
28694205-553a-402e-998e-e0aa5c36edea#015#012MAX-FORWARDS: 69#015#012VIA:
SIP/2.0/TLS 52.114.132.46:5061;branch=z9hG4bKce3091ed#015#012CONTACT: <sip:
sip-du-a-us.pstnhub.microsoft.com:5061>#015#012CONTENT-LENGTH:
0#015#012USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2021.11.2.11 i.USEA
.3#015#012ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY#015#012#015
request_route: OPTIONS from tls:52.114.132.46:7040 Sending reply 200 OK
INFO:core:handle_sigs: child process 6055 exited by a signal 11
INFO:core:handle_sigs: core was generated
INFO:core:handle_sigs: terminating due to SIGCHLD
INFO:core:sig_usr: signal 15 received
INFO:core:shutdown_opensips: process 2(6045) [MI FIFO] terminated, still
waiting for 13 more
INFO:core:sig_usr: signal 15 received
INFO:core:shutdown_opensips: process 4(6047) [time_keeper] terminated,
still waiting for 12 more
INFO:core:shutdown_opensips: process 3(6046) [HTTPD INADDR_ANY:8080]
terminated, still waiting for 11 more
INFO:core:shutdown_opensips: process 13(6056) [TCP receiver] terminated,
still waiting for 10 more
INFO:core:shutdown_opensips: process 5(6048) [timer] terminated, still
waiting for 9 more
INFO:core:shutdown_opensips: process 10(6053) [TCP receiver] terminated,
still waiting for 8 more
INFO:core:shutdown_opensips: process 7(6050) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 7 more
INFO:core:shutdown_opensips: process 11(6054) [TCP receiver] terminated,
still waiting for 6 more
INFO:core:shutdown_opensips: process 14(6058) [Timer handler] terminated,
still waiting for 5 more
INFO:core:shutdown_opensips: process 6(6049) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 4 more
INFO:core:shutdown_opensips: process 15(6059) [TCP main] terminated, still
waiting for 3 more
INFO:core:shutdown_opensips: process 8(6051) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 2 more
INFO:core:shutdown_opensips: process 1(6044) [SNMP AgentX] terminated,
still waiting for 1 more
INFO:core:shutdown_opensips: process 9(6052) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 0 more
INFO:core:cleanup: cleanup
INFO:snmpstats:mod_destroy: The SNMPStats module got the kill signal
INFO:snmpstats:mod_destroy: Shutting down the AgentX Sub-Agent!
INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
CRITICAL:core:sig_usr: segfault in attendant (starter) process!


Mark.


On Thu, 11 Nov 2021 at 13:59, Gregory Massel <greg at switchtel.co.za> wrote:

> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>
> With WolfSSL it segfaults:
>
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
> ef 5b 48 8d 3d d7
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
>
> With OpenSSL it remains running, however, is still extremely unhappy:
>
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>
>
> I didn't have these issues with OpenSIPS 3.1, however, am not sure how to
> downgrade as, when I do, it complains that the database table structure is
> not suitable and there does not appear to be a migration script to revert
> to an older version.
>
>
> --
> Regards
> *Gregory Massel*
> *T* +27 87 550 0000
> *F* +27 11 783 4877
> *W* www.switchtel.co.za
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


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

From farmorg at gmail.com  Thu Nov 11 14:53:30 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 11 Nov 2021 14:53:30 +0000
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
Message-ID: <CAOvQDeu1OQdRnLfLn836_pbgSy8+AoEzAWzXttANa-m3Hm2wyw@mail.gmail.com>

My version info:

opensips -V
version: opensips 3.2.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC,
F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: f953b30a0
main.c compiled on 16:54:35 Nov  3 2021 with gcc 9


On Thu, 11 Nov 2021 at 14:33, Gregory Massel <greg at switchtel.co.za> wrote:

> I've managed to downgrade to 3.2.2 and all is working again. So this
> appears to be a bug introduced in 3.2.3.
>
> Environment is:
>
> Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22 09:25:04
> UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> The downgrade/fix was with:
>
> apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1
> opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
> opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1
> opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1
> opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1
>
> --Greg
> On 2021-11-11 15:56, Gregory Massel wrote:
>
> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>
> With WolfSSL it segfaults:
>
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
> ef 5b 48 8d 3d d7
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
>
> With OpenSSL it remains running, however, is still extremely unhappy:
>
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>
>
> I didn't have these issues with OpenSIPS 3.1, however, am not sure how to
> downgrade as, when I do, it complains that the database table structure is
> not suitable and there does not appear to be a migration script to revert
> to an older version.
>
>
> --
> Regards
> *Gregory Massel*
> *T* +27 87 550 0000
> *F* +27 11 783 4877
> *W* www.switchtel.co.za
>
> _______________________________________________
> 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
>


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

From farmorg at gmail.com  Thu Nov 11 15:06:45 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 11 Nov 2021 15:06:45 +0000
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
Message-ID: <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>

Confirmed here too, 3.2.2 is running fine.

There does seem to be a bug report about this:

https://github.com/OpenSIPS/opensips/issues/2667


On Thu, 11 Nov 2021 at 14:33, Gregory Massel <greg at switchtel.co.za> wrote:

> I've managed to downgrade to 3.2.2 and all is working again. So this
> appears to be a bug introduced in 3.2.3.
>
> Environment is:
>
> Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22 09:25:04
> UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> The downgrade/fix was with:
>
> apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1
> opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
> opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1
> opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1
> opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1
>
> --Greg
> On 2021-11-11 15:56, Gregory Massel wrote:
>
> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>
> With WolfSSL it segfaults:
>
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
> ef 5b 48 8d 3d d7
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
>
> With OpenSSL it remains running, however, is still extremely unhappy:
>
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>
>
> I didn't have these issues with OpenSIPS 3.1, however, am not sure how to
> downgrade as, when I do, it complains that the database table structure is
> not suitable and there does not appear to be a migration script to revert
> to an older version.
>
>
> --
> Regards
> *Gregory Massel*
> *T* +27 87 550 0000
> *F* +27 11 783 4877
> *W* www.switchtel.co.za
>
> _______________________________________________
> 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
>


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

From greg at switchtel.co.za  Thu Nov 11 15:28:06 2021
From: greg at switchtel.co.za (Gregory Massel)
Date: Thu, 11 Nov 2021 17:28:06 +0200
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
 <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
Message-ID: <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>

Thanks.

This report lists it as a bug in WolfSSL, however, given that I'm got 
similar errors (although not a segfault) when changing to OpenSSL, it 
would appear more likely that it's in proto_tls or tls_mgm.

--Greg

On 2021-11-11 17:06, Mark Farmer wrote:
> Confirmed here too, 3.2.2 is running fine.
>
> There does seem to be a bug report about this:
>
> https://github.com/OpenSIPS/opensips/issues/2667
>
>
> On Thu, 11 Nov 2021 at 14:33, Gregory Massel <greg at switchtel.co.za> wrote:
>
>     I've managed to downgrade to 3.2.2 and all is working again. So
>     this appears to be a bug introduced in 3.2.3.
>
>     Environment is:
>
>     Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22
>     09:25:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>
>     The downgrade/fix was with:
>
>     apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1
>     opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
>     opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1
>     opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1
>     opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1
>
>     --Greg
>
>     On 2021-11-11 15:56, Gregory Massel wrote:
>>
>>     I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL
>>     connections.
>>
>>     With WolfSSL it segfaults:
>>
>>     Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.75.24:5061  <http://52.114.75.24:5061>  established
>>     Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.132.46:5061  <http://52.114.132.46:5061>  established
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
>>     Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>     Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
>>     ef 5b 48 8d 3d d7
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from52.114.75.24:17152  <http://52.114.75.24:17152>  accepted
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com  <http://sip.pstnhub.microsoft.com>, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
>>     Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to54.171.127.194:5061  <http://54.171.127.194:5061>  established
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
>>     Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>     Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.14.70:5061  <http://52.114.14.70:5061>  established
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to54.172.60.3:5061  <http://54.172.60.3:5061>  established
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 26 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 25 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 22 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 15 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 14 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 12 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 8 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 4 more
>>     Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
>>     Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
>>     Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
>>     Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
>>     Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
>>     Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
>>     Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
>>     Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
>>     Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
>>     Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>>
>>     With OpenSSL it remains running, however, is still extremely unhappy:
>>     Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>     Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>     Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>     Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>>
>>     I didn't have these issues with OpenSIPS 3.1, however, am not
>>     sure how to downgrade as, when I do, it complains that the
>>     database table structure is not suitable and there does not
>>     appear to be a migration script to revert to an older version.
>>
>>
>>     -- 
>>     Regards
>>     *Gregory Massel*
>>     *T* +27 87 550 0000
>>     *F* +27 11 783 4877
>>     *W* www.switchtel.co.za <http://www.switchtel.co.za/>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> -- 
> Mark Farmer
> farmorg at gmail.com
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-- 
Regards
*Gregory Massel*
*T* +27 87 550 0000
*F* +27 11 783 4877
*W* www.switchtel.co.za <http://www.switchtel.co.za/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211111/3e7fad71/attachment-0001.html>

From rob.dyck at telus.net  Thu Nov 11 20:34:03 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Thu, 11 Nov 2021 12:34:03 -0800
Subject: [OpenSIPS-Users] Some questions regarding configuring msilo
Message-ID: <1963995.0S5aU1g85B@blacky>

The module documentation for msilo gives us an example of configuration to deploy the 
service.
In a block staring with "if(!lookup("location"))" we see the following --

      # if the downstream UA does not support MESSAGE requests 
       # go to failure_route[1] 
       t_on_if (!db_does_uri_exist("$ru","subscriber"))failure("1"); 
       t_relay(); 
       exit;
We didn't actually establish that the lookup failed because Message is unsupported. 
Lookup has only one failure return code -1. This does not tell us if the lookup failure was 
due to an non-existant AOR, no UAs registered or method not supported.

In the statement "t_on_if (db_does_uri_exist("$ru","subscriber"))failure("1"); " t_on_if is not 
documented. Does it mean we should immediately go to the failure route if the AOR does 
not exist.

If the AOR does not exist why would we do ---
   if (m_store("$ou")) 
   { 
       log("MSILO: offline message stored\n"); 
       t_reply("202", "Accepted"); 
   }else{ 
       log("MSILO: offline message NOT stored\n"); 
       t_reply("503", "Service Unavailable"); 
   };

Some clarification would be appreciated.
Rob


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

From saurabhc at 3clogic.com  Fri Nov 12 04:42:17 2021
From: saurabhc at 3clogic.com (Saurabh Chopra)
Date: Fri, 12 Nov 2021 10:12:17 +0530
Subject: [OpenSIPS-Users] Help in pike Module
Message-ID: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>

Hi Opensips team,

We are testing the pike module in opensips 3.1, but need some help with our
requirement. We are using the gw IP's added in the routing table for
incoming requests to our production SER's.
As per the documentation from pike, is there any way that gateway IP added
in our routing table could be monitored by Pike?

Best Regards
Saurabh Chopra
+918861979979
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211112/3bf341c0/attachment.html>

From andrew at rwts.com.au  Fri Nov 12 11:09:54 2021
From: andrew at rwts.com.au (Andrew Yager)
Date: Fri, 12 Nov 2021 22:09:54 +1100
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
 <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
 <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>
Message-ID: <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>

Do you have a core dump with the backtrace when it dies?

There are a few fixes in the nightly releases around some TLS things, and
we've found these to be a better choice for SSL performance.

Thanks,
Andrew

On Fri, 12 Nov 2021 at 02:30, Gregory Massel <greg at switchtel.co.za> wrote:

> Thanks.
>
> This report lists it as a bug in WolfSSL, however, given that I'm got
> similar errors (although not a segfault) when changing to OpenSSL, it would
> appear more likely that it's in proto_tls or tls_mgm.
>
> --Greg
> On 2021-11-11 17:06, Mark Farmer wrote:
>
> Confirmed here too, 3.2.2 is running fine.
>
> There does seem to be a bug report about this:
>
> https://github.com/OpenSIPS/opensips/issues/2667
>
>
> On Thu, 11 Nov 2021 at 14:33, Gregory Massel <greg at switchtel.co.za> wrote:
>
>> I've managed to downgrade to 3.2.2 and all is working again. So this
>> appears to be a bug introduced in 3.2.3.
>>
>> Environment is:
>>
>> Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22
>> 09:25:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>
>> The downgrade/fix was with:
>>
>> apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1
>> opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
>> opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1
>> opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1
>> opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1
>>
>> --Greg
>> On 2021-11-11 15:56, Gregory Massel wrote:
>>
>> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>>
>> With WolfSSL it segfaults:
>>
>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
>> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
>> ef 5b 48 8d 3d d7
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
>> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
>> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
>> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
>> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
>> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
>> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
>> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>>
>>
>> With OpenSSL it remains running, however, is still extremely unhappy:
>>
>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>>
>>
>> I didn't have these issues with OpenSIPS 3.1, however, am not sure how to
>> downgrade as, when I do, it complains that the database table structure is
>> not suitable and there does not appear to be a migration script to revert
>> to an older version.
>>
>>
>> --
>> Regards
>> *Gregory Massel*
>> *T* +27 87 550 0000
>> *F* +27 11 783 4877
>> *W* www.switchtel.co.za
>>
>> _______________________________________________
>> 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
>>
>
>
> --
> Mark Farmer
> farmorg at gmail.com
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> --
> Regards
> *Gregory Massel*
> *T* +27 87 550 0000
> *F* +27 11 783 4877
> *W* www.switchtel.co.za
> _______________________________________________
> 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/20211112/c2264f61/attachment-0001.html>

From farmorg at gmail.com  Fri Nov 12 12:00:32 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Fri, 12 Nov 2021 12:00:32 +0000
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
 <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
 <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>
 <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>
Message-ID: <CAOvQDeu7ga6nGxLBms=pJWCj3DWvX_T7W8UHQCmQgHsQYXXexA@mail.gmail.com>

Sadly I have not got my core dumps working yet.
However, I have just cloned & compiled the 3.2 branch and I can confirm
that the issue remains.

opensips -V
version: opensips 3.2.3 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC,
F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: 4ec0f086c
main.c compiled on 11:30:39 Nov 12 2021 with gcc 9

INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to
52.114.132.46:5061 established
NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
reply_route: Received reply 200 from tls:52.114.75.24:5061
CRITICAL:core:sig_usr: segfault in process pid: 32583, id: 12
INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to
52.114.32.169:5061 established
CRITICAL:core:sig_usr: segfault in process pid: 32584, id: 13
NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
CRITICAL:core:sig_usr: segfault in process pid: 32581, id: 10
request_route: Received OPTIONS from x.x.x.x
request_route: - checking x.x.x.x:5060
request_route: Received OPTIONS from x.x.x.x
request_route: - checking x.x.x.x:5060
request_route: Received OPTIONS from x.x.x.x
request_route: - checking x.x.x.x:5060
INFO:core:handle_sigs: child process 32581 exited by a signal 11
INFO:core:handle_sigs: core was generated
INFO:core:handle_sigs: terminating due to SIGCHLD
INFO:core:sig_usr: signal 15 received
INFO:core:sig_usr: signal 15 received
INFO:core:shutdown_opensips: process 3(32574) [HTTPD INADDR_ANY:8080]
terminated, still waiting for 13 more
INFO:core:shutdown_opensips: process 1(32572) [SNMP AgentX] terminated,
still waiting for 12 more
INFO:core:shutdown_opensips: process 14(32585) [Timer handler] terminated,
still waiting for 11 more
INFO:core:shutdown_opensips: process 5(32576) [timer] terminated, still
waiting for 10 more
INFO:core:shutdown_opensips: process 8(32579) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 9 more
INFO:core:shutdown_opensips: process 2(32573) [MI FIFO] terminated, still
waiting for 8 more
INFO:core:shutdown_opensips: process 4(32575) [time_keeper] terminated,
still waiting for 7 more
INFO:core:shutdown_opensips: process 11(32582) [TCP receiver] terminated,
still waiting for 6 more
INFO:core:shutdown_opensips: process 13(32584) [TCP receiver] terminated,
still waiting for 5 more
INFO:core:shutdown_opensips: process 12(32583) [TCP receiver] terminated,
still waiting for 4 more
INFO:core:cleanup: cleanup
CRITICAL:core:sig_usr: segfault in attendant (starter) process!


On Fri, 12 Nov 2021 at 11:13, Andrew Yager <andrew at rwts.com.au> wrote:

> Do you have a core dump with the backtrace when it dies?
>
> There are a few fixes in the nightly releases around some TLS things, and
> we've found these to be a better choice for SSL performance.
>
> Thanks,
> Andrew
>
> On Fri, 12 Nov 2021 at 02:30, Gregory Massel <greg at switchtel.co.za> wrote:
>
>> Thanks.
>>
>> This report lists it as a bug in WolfSSL, however, given that I'm got
>> similar errors (although not a segfault) when changing to OpenSSL, it would
>> appear more likely that it's in proto_tls or tls_mgm.
>>
>> --Greg
>> On 2021-11-11 17:06, Mark Farmer wrote:
>>
>> Confirmed here too, 3.2.2 is running fine.
>>
>> There does seem to be a bug report about this:
>>
>> https://github.com/OpenSIPS/opensips/issues/2667
>>
>>
>> On Thu, 11 Nov 2021 at 14:33, Gregory Massel <greg at switchtel.co.za>
>> wrote:
>>
>>> I've managed to downgrade to 3.2.2 and all is working again. So this
>>> appears to be a bug introduced in 3.2.3.
>>>
>>> Environment is:
>>>
>>> Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri Oct 22
>>> 09:25:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> The downgrade/fix was with:
>>>
>>> apt-get install opensips=3.2.2-1 opensips-dialplan-module=3.2.2-1
>>> opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
>>> opensips-presence-modules=3.2.2-1 opensips-regex-module=3.2.2-1
>>> opensips-tls-module=3.2.2-1 opensips-tls-openssl-module=3.2.2-1
>>> opensips-tls-wolfssl-module=3.2.2-1 opensips-tlsmgm-module=3.2.2-1
>>>
>>> --Greg
>>> On 2021-11-11 15:56, Gregory Massel wrote:
>>>
>>> I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections.
>>>
>>> With WolfSSL it segfaults:
>>>
>>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.75.24:5061 established
>>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.132.46:5061 established
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
>>> Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>> Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
>>> ef 5b 48 8d 3d d7
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from 52.114.75.24:17152 accepted
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
>>> Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.171.127.194:5061 established
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
>>> Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>> Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 52.114.14.70:5061 established
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to 54.172.60.3:5061 established
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 26 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 25 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 22 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 15 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 14 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 12 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060] terminated, still waiting for 8 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060] terminated, still waiting for 4 more
>>> Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
>>> Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
>>> Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
>>> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
>>> Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
>>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
>>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
>>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
>>> Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
>>> Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>>>
>>>
>>> With OpenSSL it remains running, however, is still extremely unhappy:
>>>
>>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it at https://github.com/OpenSIPS/opensips/issues
>>> Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>>>
>>>
>>> I didn't have these issues with OpenSIPS 3.1, however, am not sure how
>>> to downgrade as, when I do, it complains that the database table structure
>>> is not suitable and there does not appear to be a migration script to
>>> revert to an older version.
>>>
>>>
>>> --
>>> Regards
>>> *Gregory Massel*
>>> *T* +27 87 550 0000
>>> *F* +27 11 783 4877
>>> *W* www.switchtel.co.za
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> --
>> Mark Farmer
>> farmorg at gmail.com
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> --
>> Regards
>> *Gregory Massel*
>> *T* +27 87 550 0000
>> *F* +27 11 783 4877
>> *W* www.switchtel.co.za
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


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

From greg at switchtel.co.za  Fri Nov 12 12:44:51 2021
From: greg at switchtel.co.za (Gregory Massel)
Date: Fri, 12 Nov 2021 14:44:51 +0200
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
 <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
 <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>
 <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>
Message-ID: <0d4f4824-7beb-6059-8627-f42cd89e0eb8@switchtel.co.za>

Sorry, I do have the core files, however, my /usr/sbin/opensips is now 
3.2.2 and the core dumps were taken against 3.2.3.

I should have thought to get the backtrace before downgrading.

This is a production server, however, I will try and schedule some 
downtime and then restore 3.2.3 to generate the backtrace and will try 
out the nightly release.

--Greg

On 2021-11-12 13:09, Andrew Yager wrote:
> Do you have a core dump with the backtrace when it dies?
>
> There are a few fixes in the nightly releases around some TLS things, 
> and we've found these to be a better choice for SSL performance.
>
> Thanks,
> Andrew
>
> On Fri, 12 Nov 2021 at 02:30, Gregory Massel <greg at switchtel.co.za> wrote:
>
>     Thanks.
>
>     This report lists it as a bug in WolfSSL, however, given that I'm
>     got similar errors (although not a segfault) when changing to
>     OpenSSL, it would appear more likely that it's in proto_tls or
>     tls_mgm.
>
>     --Greg
>
>     On 2021-11-11 17:06, Mark Farmer wrote:
>>     Confirmed here too, 3.2.2 is running fine.
>>
>>     There does seem to be a bug report about this:
>>
>>     https://github.com/OpenSIPS/opensips/issues/2667
>>
>>
>>     On Thu, 11 Nov 2021 at 14:33, Gregory Massel
>>     <greg at switchtel.co.za> wrote:
>>
>>         I've managed to downgrade to 3.2.2 and all is working again.
>>         So this appears to be a bug introduced in 3.2.3.
>>
>>         Environment is:
>>
>>         Linux msteams 5.4.0-90-generic #101~18.04.1-Ubuntu SMP Fri
>>         Oct 22 09:25:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>
>>         The downgrade/fix was with:
>>
>>         apt-get install opensips=3.2.2-1
>>         opensips-dialplan-module=3.2.2-1
>>         opensips-http-modules=3.2.2-1 opensips-mysql-module=3.2.2-1
>>         opensips-presence-modules=3.2.2-1
>>         opensips-regex-module=3.2.2-1 opensips-tls-module=3.2.2-1
>>         opensips-tls-openssl-module=3.2.2-1
>>         opensips-tls-wolfssl-module=3.2.2-1
>>         opensips-tlsmgm-module=3.2.2-1
>>
>>         --Greg
>>
>>         On 2021-11-11 15:56, Gregory Massel wrote:
>>>
>>>         I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL
>>>         connections.
>>>
>>>         With WolfSSL it segfaults:
>>>
>>>         Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.75.24:5061  <http://52.114.75.24:5061>  established
>>>         Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.132.46:5061  <http://52.114.132.46:5061>  established
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15328]: CRITICAL:core:sig_usr: segfault in process pid: 15328, id: 25
>>>         Nov 11 11:52:05 msteams kernel: [22403546.537543] opensips[15328]: segfault at 35 ip 00007ff7b4b3f790 sp 00007fff48dd0a30 error 4 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>>         Nov 11 11:52:05 msteams kernel: [22403546.537549] Code: ff ff e9 5b ff ff ff 0f 1f 00 53 48 8d 3d 08 40 3b 00 e8 53 09 00 00 85 c0 75 4f 48 8b 3d 50 40 3b 00 48 85 ff 74 14 0f 1f 00 <48> 8b 5f 08 e8 87 36 f7 ff 48 85 db 48 89 df 75
>>>         ef 5b 48 8d 3d d7
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:_wolfssl_tls_accept: New TLS connection from52.114.75.24:17152  <http://52.114.75.24:17152>  accepted
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15322]: INFO:tls_wolfssl:tls_dump_cert_info: tls_accept: client TLS certificate subject: /CN=sip.pstnhub.microsoft.com  <http://sip.pstnhub.microsoft.com>, issuer: /C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15329]: CRITICAL:core:sig_usr: segfault in process pid: 15329, id: 26
>>>         Nov 11 11:52:05 msteams kernel: [22403546.732270] traps: opensips[15329] general protection fault ip:7ff7b4b0953d sp:7fff48dd0760 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to54.171.127.194:5061  <http://54.171.127.194:5061>  established
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15330]: CRITICAL:core:sig_usr: segfault in process pid: 15330, id: 27
>>>         Nov 11 11:52:05 msteams kernel: [22403546.801626] traps: opensips[15330] general protection fault ip:7ff7b4b3f790 sp:7fff48dd0a30 error:0 in tls_wolfssl.so[7ff7b4a71000+1e3000]
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success
>>>         Nov 11 11:52:05 msteams /usr/sbin/opensips[15326]: NOTICE:tls_wolfssl:verify_callback: depth = 0, verify success
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to52.114.14.70:5061  <http://52.114.14.70:5061>  established
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15325]: INFO:tls_wolfssl:_wolfssl_tls_async_connect: new TLS connection to54.172.60.3:5061  <http://54.172.60.3:5061>  established
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: child process 15328 exited by a signal 11
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: core was generated
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:handle_sigs: terminating due to SIGCHLD
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15296]: INFO:core:sig_usr: signal 15 received
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15297]: INFO:core:sig_usr: signal 15 received
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 3(15296) [time_keeper] terminated, still waiting for 28 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 4(15297) [timer] terminated, still waiting for 27 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 5(15298) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 26 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 6(15299) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 25 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 14(15308) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 24 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 30(15333) [TCP main] terminated, still waiting for 23 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 9(15302) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 22 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 15(15310) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 21 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 19(15319) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 20 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 29(15332) [Timer handler] terminated, still waiting for 19 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 1(15294) [MI FIFO] terminated, still waiting for 18 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 21(15322) [TCP receiver] terminated, still waiting for 17 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 20(15320) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 16 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 11(15304) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 15 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 8(15301) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 14 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 2(15295) [HTTPD INADDR_ANY:8888] terminated, still waiting for 13 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 10(15303) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 12 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 13(15307) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 11 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 16(15311) [SIP receiver udp:[0:0:0:0:0:0:0:1]:5060] terminated, still waiting for 10 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 22(15323) [TCP receiver] terminated, still waiting for 9 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 12(15305) [SIP receiver udp:196.216.192.19:5060  <http://196.216.192.19:5060>] terminated, still waiting for 8 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 18(15317) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 7 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 17(15315) [SIP receiver udp:[2001:43F8:BC0:1:0:0:0:1019]:5060] terminated, still waiting for 6 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 24(15326) [TCP receiver] terminated, still waiting for 5 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 7(15300) [SIP receiver udp:127.0.0.1:5060  <http://127.0.0.1:5060>] terminated, still waiting for 4 more
>>>         Nov 11 11:52:06 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 23(15325) [TCP receiver] terminated, still waiting for 3 more
>>>         Nov 11 11:52:09 msteams /usr/sbin/opensips[15293]: INFO:core:shutdown_opensips: process 26(15329) [TCP receiver] terminated, still waiting for 2 more
>>>         Nov 11 11:52:11 msteams /usr/sbin/opensips[15293]: INFO:core:cleanup: cleanup
>>>         Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: INFO:tls_wolfssl:mod_destroy: destroying tls_wolfssl module
>>>         Nov 11 11:52:12 msteams /usr/sbin/opensips[15293]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7ff7badd7878), first free: (null): (null)(0) - aborting!
>>>         Nov 11 11:52:18 msteams systemd[1]: opensips.service: Main process exited, code=dumped, status=6/ABRT
>>>         Nov 11 11:52:18 msteams systemd[1]: opensips.service: Failed with result 'core-dump'.
>>>         Nov 11 11:52:18 msteams systemd[1]: opensips.service: Service hold-off time over, scheduling restart.
>>>         Nov 11 11:52:18 msteams systemd[1]: opensips.service: Scheduled restart job, restart counter is at 1.
>>>         Nov 11 11:52:18 msteams systemd[1]: Stopped OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>>>
>>>         With OpenSSL it remains running, however, is still extremely
>>>         unhappy:
>>>         Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> fd_array idx 8 (fd=236) points to bogus map (fd=-1,type=0,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>>         Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> used fd map fd=227 is not present in fd_array (fd=227,type=19,flags=80000002,data=0x7f4b4e12eb80)#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>>         Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: #012>>> unused fd_map fd=236 has bogus data (fd=-1,flags=20000000,data=(nil))#012#012It seems you have hit a programming bug.#012Please help us make OpenSIPS better by reporting it athttps://github.com/OpenSIPS/opensips/issues
>>>         Nov 11 15:46:35 msteams /usr/sbin/opensips[5044]: CRITICAL:core:io_watch_add: [TCP_main] check failed after successful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0
>>>
>>>         I didn't have these issues with OpenSIPS 3.1, however, am
>>>         not sure how to downgrade as, when I do, it complains that
>>>         the database table structure is not suitable and there does
>>>         not appear to be a migration script to revert to an older
>>>         version.
>>>
>>>
>>>         -- 
>>>         Regards
>>>         *Gregory Massel*
>>>         *T* +27 87 550 0000
>>>         *F* +27 11 783 4877
>>>         *W* www.switchtel.co.za <http://www.switchtel.co.za/>
>>>
>>>         _______________________________________________
>>>         Users mailing list
>>>         Users at lists.opensips.org
>>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>         _______________________________________________
>>         Users mailing list
>>         Users at lists.opensips.org
>>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>     -- 
>>     Mark Farmer
>>     farmorg at gmail.com
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     -- 
>     Regards
>     *Gregory Massel*
>     *T* +27 87 550 0000
>     *F* +27 11 783 4877
>     *W* www.switchtel.co.za <http://www.switchtel.co.za/>
>     _______________________________________________
>     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/20211112/d1a90c8f/attachment-0001.html>

From rob.dyck at telus.net  Fri Nov 12 22:12:44 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Fri, 12 Nov 2021 14:12:44 -0800
Subject: [OpenSIPS-Users] msilo module offline message time stamp
Message-ID: <2270103.OYXXYNVTWy@blacky>

How does one set the time stamp that openips prefixes to an offline message that 
is sent when the UA registers?

2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ] HI THERE"

Thanks, Rob




From kurgan-rus at inbox.ru  Mon Nov 15 05:41:27 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Mon, 15 Nov 2021 08:41:27 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?Help_in_pike_Module?=
In-Reply-To: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>
References: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>
Message-ID: <1636954887.265553175@f468.i.mail.ru>


Hi Saurabh,
not clear from your message what routing table do you mean —
either Linux kernel routing table or drouting [1] module.
 
Anyway, you may use ratelimit [2] module or pike [3] modules
specifying the IP addresses as the source address to check/not to check
the requests coming from it.
 
I have some experience with both of modules,
maybe my notes [4], [5] can also be useful to you.
 
[1]  https://opensips.org/docs/modules/3.1.x/drouting.html
[2]  https://opensips.org/docs/modules/3.1.x/ratelimit.html
[3]  https://opensips.org/docs/modules/3.1.x/pike.html
[4]  https://alexeyka.zantsev.com/?p=1275
[5]  https://alexeyka.zantsev.com/?p=1194
 
-----------------------------------------------
BR, Alexey
https://alexeyka.zantsev.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211115/5e99762c/attachment.html>

From m.putra77 at outlook.com  Mon Nov 15 07:39:21 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Mon, 15 Nov 2021 07:39:21 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
Message-ID: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

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

From m.putra77 at outlook.com  Tue Nov 16 00:48:54 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Tue, 16 Nov 2021 00:48:54 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
In-Reply-To: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <SI2PR03MB556107A508660217552C3CC3FD999@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

The reason I'm asking is because one of the interface need to be in DHCP  so I need the IP address information for serthostport() and socket_out() to relay SIP/RTP to other interface.

Thanks

From: Muhamad Putra Abdullah
Sent: Monday, 15 November, 2021 3:39 PM
To: users at lists.opensips.org
Subject: How to get all listening socket IP address as variable

Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

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

From spanda at 3clogic.com  Tue Nov 16 06:26:11 2021
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 16 Nov 2021 11:56:11 +0530
Subject: [OpenSIPS-Users] Help in pike Module
In-Reply-To: <1636954887.265553175@f468.i.mail.ru>
References: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>
 <1636954887.265553175@f468.i.mail.ru>
Message-ID: <CALf-Q44XrSjbMEdoX4gRwqMHFVkw1XX+b7mTetLjmU+-9Lbtmw@mail.gmail.com>

Hi Alexey ,

Saurabh is talking about drouting dr_gateways table .

We have some trusted IPs which are added in the dr_gateways table . We
don't want to monitor these IPs  .
 Rather than these IPs every other IPs should get monitor to block the
traffic if it's overflooded . We don't want to add these IPs in the config
file . Because the table used to get updated .

If we add these IPs in the config file to check for the PIKE module , then
every time we will add a new IP we have to restart the service , which we
don't want .

How will we do this ?


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


On Mon, Nov 15, 2021 at 11:14 AM Alexey Kazantsev via Users <
users at lists.opensips.org> wrote:

> Hi Saurabh,
> not clear from your message what routing table do you mean —
> either Linux kernel routing table or drouting [1] module.
>
> Anyway, you may use ratelimit [2] module or pike [3] modules
> specifying the IP addresses as the source address to check/not to check
> the requests coming from it.
>
> I have some experience with both of modules,
> maybe my notes [4], [5] can also be useful to you.
>
> [1] https://opensips.org/docs/modules/3.1.x/drouting.html
> [2] https://opensips.org/docs/modules/3.1.x/ratelimit.html
> [3] https://opensips.org/docs/modules/3.1.x/pike.html
> <https://opensips.org/docs/modules/3.1.x/pike.html#overview>
> [4] https://alexeyka.zantsev.com/?p=1275
> [5] https://alexeyka.zantsev.com/?p=1194
>
> -----------------------------------------------
> BR, Alexey
> https://alexeyka.zantsev.com/
>
> _______________________________________________
> 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/20211116/9ec1ee04/attachment.html>

From kurgan-rus at inbox.ru  Tue Nov 16 07:03:15 2021
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Tue, 16 Nov 2021 10:03:15 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?Help_in_pike_Module?=
In-Reply-To: <CALf-Q44XrSjbMEdoX4gRwqMHFVkw1XX+b7mTetLjmU+-9Lbtmw@mail.gmail.com>
References: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>
 <1636954887.265553175@f468.i.mail.ru>
 <CALf-Q44XrSjbMEdoX4gRwqMHFVkw1XX+b7mTetLjmU+-9Lbtmw@mail.gmail.com>
Message-ID: <1637046195.807210110@f170.i.mail.ru>


Hi Sasmita,
 
if there’s not too much IP addresses (not hundreds or thousands) in your dr_gatewas table,
you still can add them to the config file and re-read it with reload_routes [1] function.
There should not be service interruption according to the documentation.
 
So, you may try to add trusted addresses to the check_route [2] of the pike module.
 
[1]  https://www.opensips.org/Documentation/Interface-CoreMI-3-1#toc8
[2]  https://opensips.org/docs/modules/3.1.x/pike.html#param_check_route
 
-----------------------------------------------
BR, Alexey
https://alexeyka.zantsev.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211116/93905b88/attachment-0001.html>

From eremina.net at gmail.com  Tue Nov 16 07:10:47 2021
From: eremina.net at gmail.com (Pavel Eremin)
Date: Tue, 16 Nov 2021 12:10:47 +0500
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
In-Reply-To: <SI2PR03MB556107A508660217552C3CC3FD999@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <SI2PR03MB556107A508660217552C3CC3FD999@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <CAF3UBt2gaByV_w7Uw7VnhhZTFUnZ-8bTWUc8tOOP3krzusL+4g@mail.gmail.com>

Hey,
to relay with specific interface i suppose you have use function
force_send_socket();
i am sure only about that scenario:
"""""""""""""
socket=udp:eth0:5060 as 1.1.1.1  #dhcp interface with external ip
socket=udp:2.2.2.2:5061
...
force_send_socket("udp:1.1.1.1:5060");
t_relay();
""""""""""""""

вт, 16 нояб. 2021 г. в 05:51, Muhamad Putra Abdullah <m.putra77 at outlook.com
>:

> Hi,
>
>
>
> The reason I’m asking is because one of the interface need to be in DHCP
>  so I need the IP address information for serthostport() and socket_out()
> to relay SIP/RTP to other interface.
>
>
>
> Thanks
>
>
>
> *From:* Muhamad Putra Abdullah
> *Sent:* Monday, 15 November, 2021 3:39 PM
> *To:* users at lists.opensips.org
> *Subject:* How to get all listening socket IP address as variable
>
>
>
> Hi,
>
>
>
> I have 2 listening interface for opensips 3.2. How do I get both IP
> address to be used as variable in opensips config file? I try to use
> socket_in/ socket_out but failed to get the other interface IP address.
>
>
>
> Thanks
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows
>
>
> _______________________________________________
> 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/20211116/73e9090c/attachment.html>

From bogdan at opensips.org  Tue Nov 16 10:45:26 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 12:45:26 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>

Hi,

via the socket_xx() vars you can get only the sockets relative to/used 
by that call, you cannot iterate thru the listening sockets.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
> I have 2 listening interface for opensips 3.2. How do I get both IP 
> address to be used as variable in opensips config file? I try to use 
> socket_in/ socket_out but failed to get the other interface IP address.
>
> Thanks
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
> Windows
>
>
> _______________________________________________
> 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/20211116/d153824f/attachment.html>

From bogdan at opensips.org  Tue Nov 16 10:50:15 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 12:50:15 +0200
Subject: [OpenSIPS-Users] Help in pike Module
In-Reply-To: <CALf-Q44XrSjbMEdoX4gRwqMHFVkw1XX+b7mTetLjmU+-9Lbtmw@mail.gmail.com>
References: <CAAmwJvG2k5X755mrJ8KVQvf9Ji_1vDhWj8vcFEc+1-5oVPOxig@mail.gmail.com>
 <1636954887.265553175@f468.i.mail.ru>
 <CALf-Q44XrSjbMEdoX4gRwqMHFVkw1XX+b7mTetLjmU+-9Lbtmw@mail.gmail.com>
Message-ID: <2b94cf2a-58e6-4318-3431-e1d942d8ff74@opensips.org>

Hi Sasmita,

You should use the `check_route` modparam [1] and in there use 
`is_from_gw()` with `drop` in order to avoid the GW related traffic to 
be monitored by pike.

[1] https://opensips.org/html/docs/modules/3.2.x/pike.html#param_check_route

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/16/21 8:26 AM, Sasmita Panda wrote:
> Hi Alexey ,
>
> Saurabh is talking about drouting dr_gateways table .
>
> We have some trusted IPs which are added in the dr_gateways table . We 
> don't want to monitor these IPs  .
>  Rather than these IPs every other IPs should get monitor to block the 
> traffic if it's overflooded . We don't want to add these IPs in the 
> config file . Because the table used to get updated .
>
> If we add these IPs in the config file to check for the PIKE module , 
> then every time we will add a new IP we have to restart the service , 
> which we don't want .
>
> How will we do this ?
>
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
>
> On Mon, Nov 15, 2021 at 11:14 AM Alexey Kazantsev via Users 
> <users at lists.opensips.org <mailto:users at lists.opensips.org>> wrote:
>
>     Hi Saurabh,
>     not clear from your message what routing table do you mean —
>     either Linux kernel routing table or drouting [1] module.
>     Anyway, you may use ratelimit [2] module or pike [3] modules
>     specifying the IP addresses as the source address to check/not to
>     check
>     the requests coming from it.
>     I have some experience with both of modules,
>     maybe my notes [4], [5] can also be useful to you.
>     [1] https://opensips.org/docs/modules/3.1.x/drouting.html
>     <https://opensips.org/docs/modules/3.1.x/drouting.html>
>     [2] https://opensips.org/docs/modules/3.1.x/ratelimit.html
>     <https://opensips.org/docs/modules/3.1.x/ratelimit.html>
>     [3] https://opensips.org/docs/modules/3.1.x/pike.html
>     <https://opensips.org/docs/modules/3.1.x/pike.html#overview>
>     [4] https://alexeyka.zantsev.com/?p=1275
>     <https://alexeyka.zantsev.com/?p=1275>
>     [5] https://alexeyka.zantsev.com/?p=1194
>     <https://alexeyka.zantsev.com/?p=1194>
>     -----------------------------------------------
>     BR, Alexey
>     https://alexeyka.zantsev.com/ <https://alexeyka.zantsev.com/>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     <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/20211116/01aa0930/attachment.html>

From bogdan at opensips.org  Tue Nov 16 10:54:02 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 12:54:02 +0200
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <2270103.OYXXYNVTWy@blacky>
References: <2270103.OYXXYNVTWy@blacky>
Message-ID: <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>

Hi Robert,

What OpenSIPS version are you using? Asking as I remember of a recent 
fix in that area [1]

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

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/13/21 12:12 AM, Robert Dyck wrote:
> How does one set the time stamp that openips prefixes to an offline message that
> is sent when the UA registers?
>
> 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ] HI THERE"
>
> Thanks, Rob
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From bogdan at opensips.org  Tue Nov 16 11:32:49 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 13:32:49 +0200
Subject: [OpenSIPS-Users] Load balancer probing_method INVITE not
 sending contact header
In-Reply-To: <CANvjR0VawtvEP5A291vrGUMdM4F1=N-0Eb+fdK95mqBD0BcENg@mail.gmail.com>
References: <CANvjR0V_UQRo6VVT3tz-qHre6Za4dsPeNAc1iBc2nYL-82bVoA@mail.gmail.com>
 <CADTki+DVudMCFSFPP2HCuDjeEYjz-qrnNiwyRHyAWdvaxOvq5Q@mail.gmail.com>
 <CANvjR0WJbcezLfLAwSAO8vR_8Ebh0jKnedC7K4FaQaStgx-M=w@mail.gmail.com>
 <CANvjR0VawtvEP5A291vrGUMdM4F1=N-0Eb+fdK95mqBD0BcENg@mail.gmail.com>
Message-ID: <97435ae4-b20c-78e3-cba1-5c0e0491273d@opensips.org>

Schneur,

As a note here, using INVITE as probing method is a bit dangerous, as an 
INVITE creates a session (what kind of session do you do here, as I 
guess there is no SDP), a session that has to be confirmed by ACK and 
closed by a BYE.

Just saying you are twisting SIP ;)

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/11/21 1:38 PM, Schneur Rosenberg wrote:
> Hi, thank you very much that fixed the error but then it's complained 
> with a 484 Address Incomplete, I fixed the RURI too and now it's 
> working fine.
>
> Scott
>
> On Wed, Nov 10, 2021, 21:47 Schneur Rosenberg 
> <rosenberg11219 at gmail.com <mailto:rosenberg11219 at gmail.com>> wrote:
>
>     No, I'll try and keep you posted.
>
>     On Wed, Nov 10, 2021 at 9:39 PM Vasilios Tzanoudakis
>     <vasilios.tzanoudakis at voiceland.gr
>     <mailto:vasilios.tzanoudakis at voiceland.gr>> wrote:
>     >
>     > Have you tried adding the extra contact header in local_route?
>     >
>     > Στις Τετ, 10 Νοε 2021, 21:18 ο χρήστης Schneur Rosenberg
>     <rosenberg11219 at gmail.com <mailto:rosenberg11219 at gmail.com>> έγραψε:
>     >>
>     >> Hi, I'm using load balancer with probing_method INVITE, it
>     worked fine
>     >> for many years with my Asterisk and Freeswitch servers, I'm
>     migrating
>     >> my asterisk server from chan_sip to pjsip and now asterisk is
>     >> rejecting all the probing requests with a 400 Missing Contact
>     header,
>     >> I checked the modparams for the  "load_balancer" module but
>     couldn't
>     >> find how to have OpenSIPs add the contact header.
>     >>
>     >> S. Rosenberg
>     >>
>     >> _______________________________________________
>     >> Users mailing list
>     >> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>     <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
>     <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/20211116/7d39f8b3/attachment.html>

From bogdan at opensips.org  Tue Nov 16 11:34:35 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 13:34:35 +0200
Subject: [OpenSIPS-Users] Opensips segfault after adding acc_extra field
In-Reply-To: <CANJp-yi6w2O1sqCHtycATJa8Ve3Xq6gYDujcBFtC0im4KrQPZg@mail.gmail.com>
References: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>
 <CANJp-yi6w2O1sqCHtycATJa8Ve3Xq6gYDujcBFtC0im4KrQPZg@mail.gmail.com>
Message-ID: <8ae76bce-19ac-e157-d2ba-c9b783c8df5e@opensips.org>

Hi Aron,

Could you try to get a corefile and back trace here ?

https://opensips.org/Documentation/TroubleShooting-Crash

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/10/21 9:57 PM, Podrigal, Aron wrote:
> Hi Core Devs,
>
> Any idea or direction on how to handle this?
>
>
> For now,
> I think of the best way to handle this as a workaround, to spin up a 
> new instance and reroute all traffic temporarily until all ongoing 
> dialogs are completed, and then restart.
>
> But this is really important, as it makes it very difficult to deploy 
> changes to acc...
>
>
> On Wed, Nov 3, 2021, 8:17 PM Podrigal, Aron <aronp at guaranteedplus.com 
> <mailto:aronp at guaranteedplus.com>> wrote:
>
>     Hi
>
>     I added another field to my acc_extra and after restarting
>     opensips, it kept crashing right away after the restart.
>
>     Here are the relevant log lines
>
>     I got a thousand lines saying
>     Nov 03 20:48:03 snap-p1 opensips-snap[1636]:
>     WARNING:acc:restore_extra: extra tags were added/removed since
>     last run!won't restore values!
>
>     Then 2 - 3 lines afterwards
>
>     Nov 03 20:48:04 p1 opensips[1651]: CRITICAL:core:sig_usr: segfault
>     in process pid: 1651, id: 7
>     Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: child
>     process 1651 exited by a signal 11
>     Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: core was
>     not generated
>     Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs:
>     terminating due to SIGCHLD
>     Nov 03 20:48:04 p1 opensips[1643]: INFO:core:sig_usr: signal 15
>     received
>     Nov 03 20:48:04 p1 opensips[1642]: INFO:core:sig_usr: signal 15
>     received
>
>     I use opensips version 3.1 Rev 5cdfedebbe0
>
>     Any idea what can be causing this?
>
>     I have 2 acc targets one db and one log. And I added the acc_extra
>     field only to the log.
>
>
>     Thanks
>
>
>     -- 
>
>     -
>     Aron Podrigal
>
>
> _______________________________________________
> 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/20211116/a3b57308/attachment.html>

From rob.dyck at telus.net  Tue Nov 16 15:42:10 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Tue, 16 Nov 2021 07:42:10 -0800
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>
References: <2270103.OYXXYNVTWy@blacky>
 <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>
Message-ID: <3143550.44csPzL39Z@blacky>

Still on 3.2.2. I saw reports of difficulty with 3.2.3.
Should I be recompiling?
Thanks, Rob

On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu wrote:
> Hi Robert,
> 
> What OpenSIPS version are you using? Asking as I remember of a recent
> fix in that area [1]
> 
> [1]
> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309ddb5ba
> b889bf56
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> 
> On 11/13/21 12:12 AM, Robert Dyck wrote:
> > How does one set the time stamp that openips prefixes to an offline
> > message that is sent when the UA registers?
> > 
> > 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ] HI
> > THERE"
> > 
> > Thanks, Rob
> > 
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users






From bogdan at opensips.org  Tue Nov 16 15:52:26 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 17:52:26 +0200
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <3143550.44csPzL39Z@blacky>
References: <2270103.OYXXYNVTWy@blacky>
 <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>
 <3143550.44csPzL39Z@blacky>
Message-ID: <2cdd72ce-2235-5c27-b591-a1c5c1d2a982@opensips.org>

What kind of difficulties with 3.2.3 ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/16/21 5:42 PM, Robert Dyck wrote:
> Still on 3.2.2. I saw reports of difficulty with 3.2.3.
> Should I be recompiling?
> Thanks, Rob
>
> On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu wrote:
>> Hi Robert,
>>
>> What OpenSIPS version are you using? Asking as I remember of a recent
>> fix in that area [1]
>>
>> [1]
>> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309ddb5ba
>> b889bf56
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>     https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 2021
>>     https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>
>> On 11/13/21 12:12 AM, Robert Dyck wrote:
>>> How does one set the time stamp that openips prefixes to an offline
>>> message that is sent when the UA registers?
>>>
>>> 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ] HI
>>> THERE"
>>>
>>> Thanks, Rob
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>



From rob.dyck at telus.net  Tue Nov 16 15:54:38 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Tue, 16 Nov 2021 07:54:38 -0800
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <2cdd72ce-2235-5c27-b591-a1c5c1d2a982@opensips.org>
References: <2270103.OYXXYNVTWy@blacky> <3143550.44csPzL39Z@blacky>
 <2cdd72ce-2235-5c27-b591-a1c5c1d2a982@opensips.org>
Message-ID: <9983551.nUPlyArG6x@blacky>

I think I saw a report of a seg fault.

On Tuesday, November 16, 2021 7:52:26 A.M. PST Bogdan-Andrei Iancu wrote:
> What kind of difficulties with 3.2.3 ?
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> 
> On 11/16/21 5:42 PM, Robert Dyck wrote:
> > Still on 3.2.2. I saw reports of difficulty with 3.2.3.
> > Should I be recompiling?
> > Thanks, Rob
> > 
> > On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu wrote:
> >> Hi Robert,
> >> 
> >> What OpenSIPS version are you using? Asking as I remember of a recent
> >> fix in that area [1]
> >> 
> >> [1]
> >> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309ddb
> >> 5ba b889bf56
> >> 
> >> Regards,
> >> 
> >> Bogdan-Andrei Iancu
> >> 
> >> OpenSIPS Founder and Developer
> >> 
> >>     https://www.opensips-solutions.com
> >> 
> >> OpenSIPS eBootcamp 2021
> >> 
> >>     https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> >> 
> >> On 11/13/21 12:12 AM, Robert Dyck wrote:
> >>> How does one set the time stamp that openips prefixes to an offline
> >>> message that is sent when the UA registers?
> >>> 
> >>> 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ]
> >>> HI
> >>> THERE"
> >>> 
> >>> Thanks, Rob
> >>> 
> >>> 
> >>> 
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at lists.opensips.org
> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users






From bogdan at opensips.org  Tue Nov 16 15:58:12 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 16 Nov 2021 17:58:12 +0200
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <9983551.nUPlyArG6x@blacky>
References: <2270103.OYXXYNVTWy@blacky> <3143550.44csPzL39Z@blacky>
 <2cdd72ce-2235-5c27-b591-a1c5c1d2a982@opensips.org>
 <9983551.nUPlyArG6x@blacky>
Message-ID: <3181683e-11fa-933c-2432-42316371a123@opensips.org>

oky...could you point me to that report?

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/16/21 5:54 PM, Robert Dyck wrote:
> I think I saw a report of a seg fault.
>
> On Tuesday, November 16, 2021 7:52:26 A.M. PST Bogdan-Andrei Iancu wrote:
>> What kind of difficulties with 3.2.3 ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>     https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 2021
>>     https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>
>> On 11/16/21 5:42 PM, Robert Dyck wrote:
>>> Still on 3.2.2. I saw reports of difficulty with 3.2.3.
>>> Should I be recompiling?
>>> Thanks, Rob
>>>
>>> On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu wrote:
>>>> Hi Robert,
>>>>
>>>> What OpenSIPS version are you using? Asking as I remember of a recent
>>>> fix in that area [1]
>>>>
>>>> [1]
>>>> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309ddb
>>>> 5ba b889bf56
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>
>>>>      https://www.opensips-solutions.com
>>>>
>>>> OpenSIPS eBootcamp 2021
>>>>
>>>>      https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>>>
>>>> On 11/13/21 12:12 AM, Robert Dyck wrote:
>>>>> How does one set the time stamp that openips prefixes to an offline
>>>>> message that is sent when the UA registers?
>>>>>
>>>>> 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ]
>>>>> HI
>>>>> THERE"
>>>>>
>>>>> Thanks, Rob
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>



From rob.dyck at telus.net  Tue Nov 16 16:06:12 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Tue, 16 Nov 2021 08:06:12 -0800
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <3181683e-11fa-933c-2432-42316371a123@opensips.org>
References: <2270103.OYXXYNVTWy@blacky> <9983551.nUPlyArG6x@blacky>
 <3181683e-11fa-933c-2432-42316371a123@opensips.org>
Message-ID: <1874455.PYKUYFuaPT@blacky>

tls_wolfssl last week.

On Tuesday, November 16, 2021 7:58:12 A.M. PST Bogdan-Andrei Iancu wrote:
> oky...could you point me to that report?
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> 
> On 11/16/21 5:54 PM, Robert Dyck wrote:
> > I think I saw a report of a seg fault.
> > 
> > On Tuesday, November 16, 2021 7:52:26 A.M. PST Bogdan-Andrei Iancu wrote:
> >> What kind of difficulties with 3.2.3 ?
> >> 
> >> Regards,
> >> 
> >> Bogdan-Andrei Iancu
> >> 
> >> OpenSIPS Founder and Developer
> >> 
> >>     https://www.opensips-solutions.com
> >> 
> >> OpenSIPS eBootcamp 2021
> >> 
> >>     https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> >> 
> >> On 11/16/21 5:42 PM, Robert Dyck wrote:
> >>> Still on 3.2.2. I saw reports of difficulty with 3.2.3.
> >>> Should I be recompiling?
> >>> Thanks, Rob
> >>> 
> >>> On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu 
wrote:
> >>>> Hi Robert,
> >>>> 
> >>>> What OpenSIPS version are you using? Asking as I remember of a recent
> >>>> fix in that area [1]
> >>>> 
> >>>> [1]
> >>>> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309d
> >>>> db
> >>>> 5ba b889bf56
> >>>> 
> >>>> Regards,
> >>>> 
> >>>> Bogdan-Andrei Iancu
> >>>> 
> >>>> OpenSIPS Founder and Developer
> >>>> 
> >>>>      https://www.opensips-solutions.com
> >>>> 
> >>>> OpenSIPS eBootcamp 2021
> >>>> 
> >>>>      https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> >>>> 
> >>>> On 11/13/21 12:12 AM, Robert Dyck wrote:
> >>>>> How does one set the time stamp that openips prefixes to an offline
> >>>>> message that is sent when the UA registers?
> >>>>> 
> >>>>> 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ]
> >>>>> HI
> >>>>> THERE"
> >>>>> 
> >>>>> Thanks, Rob
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> _______________________________________________
> >>>>> Users mailing list
> >>>>> Users at lists.opensips.org
> >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users






From m.putra77 at outlook.com  Wed Nov 17 00:19:08 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Wed, 17 Nov 2021 00:19:08 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
Message-ID: <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
  https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows




_______________________________________________
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/20211117/ab1a058a/attachment.html>

From david.villasmil.work at gmail.com  Wed Nov 17 02:33:56 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Wed, 17 Nov 2021 02:33:56 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
In-Reply-To: <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <CAFGRPVpjgNVgyAd0rcR9nBgtXd_EP8xYagod6454uya0RV1Xtg@mail.gmail.com>

You can pass it to opensips as a variable on startup.

On Wed, 17 Nov 2021 at 00:19, Muhamad Putra Abdullah <m.putra77 at outlook.com>
wrote:

> Hi,
>
> Is there a way to get the IP address of DHCP interface to use in the
> script? I can get the call go through if I set both the interface as static.
>
> Regards
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> ------------------------------
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Tuesday, November 16, 2021, 6:45 PM
> *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
> Hi,
>
> via the socket_xx() vars you can get only the sockets relative to/used by
> that call, you cannot iterate thru the listening sockets.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> I have 2 listening interface for opensips 3.2. How do I get both IP
> address to be used as variable in opensips config file? I try to use
> socket_in/ socket_out but failed to get the other interface IP address.
>
>
>
> Thanks
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows
>
>
>
> _______________________________________________
> 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
>
-- 
Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/ab643b4e/attachment.html>

From m.putra77 at outlook.com  Wed Nov 17 03:20:37 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Wed, 17 Nov 2021 03:20:37 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address
	as	variable
In-Reply-To: <CAFGRPVpjgNVgyAd0rcR9nBgtXd_EP8xYagod6454uya0RV1Xtg@mail.gmail.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <CAFGRPVpjgNVgyAd0rcR9nBgtXd_EP8xYagod6454uya0RV1Xtg@mail.gmail.com>
Message-ID: <SI2PR03MB5561058BD55A3E8D4186F572FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

Sorry. I’m new to opensips. How can I do this?

Regards

From: Users <users-bounces at lists.opensips.org> On Behalf Of David Villasmil
Sent: Wednesday, 17 November, 2021 10:34 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

You can pass it to opensips as a variable on startup.

On Wed, 17 Nov 2021 at 00:19, Muhamad Putra Abdullah <m.putra77 at outlook.com<mailto:m.putra77 at outlook.com>> wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows



_______________________________________________

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
--
Regards,

David Villasmil
email: david.villasmil.work at gmail.com<mailto:david.villasmil.work at gmail.com>
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/9132cdf8/attachment-0001.html>

From devang.dhandhalya at ecosmob.com  Wed Nov 17 06:07:20 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 17 Nov 2021 11:37:20 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter not
	working .
Message-ID: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>

Hi All

I configured the e164 strict mode module parameter as 0 (disabled) . but
still i am getting errors related to its e164 format .While if orig/dest
number is not in e164 format then also opensips have to accept it but it is
not accepting .  I have a user like extension123 for this function I have
to perform authentication service . if i have a user extension123 is it
possible to perform authenticate service for this kind of user ?

I think this is a bug for the e164 strict mode  module parameter . I am
getting the below error .

opensips version : 3.2.2

ERROR :
 ERROR:stir_shaken:check_passport_phonenum: number is not in E.164 format:
extension123
 ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
(extension123)


loadmodule "stir_shaken.so"
modparam("stir_shaken", "auth_date_freshness", 300)
modparam("stir_shaken", "verify_date_freshness", 300)
modparam("stir_shaken", "require_date_hdr", 0)
modparam("stir_shaken", "e164_strict_mode", 0)

$var(orig) = $fU;
$var(dest) = $tU
 $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
"$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");

Please suggest a solution to this .

Many Thanks
Devang

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/8e01eeb0/attachment.html>

From devang.dhandhalya at ecosmob.com  Wed Nov 17 06:13:57 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 17 Nov 2021 11:43:57 +0530
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>
References: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>
Message-ID: <CAP0uOe-4qGrQEtYR35qe9Bz3BDuMw7+i2oEwm0ssh2_20Au2mw@mail.gmail.com>

It's the 9th day still not getting any response . Please can Anyone suggest
a solution to this issue ?

Many Thanks
Devang

On Tue, Nov 9, 2021 at 4:35 PM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hi All
>
> I Am Trying to Implement opensips with TLS support in a local machine . I
> generate TLS server (rootCA) and TLS Client (user) certificates using
> opensips-cli  .
> softphone : Blink version : 5.1.7
> opensips version : 3.2.2
> Registration with tls is working fine for TLS ,  at the time of calling
> getting below error . I check in logs at DBG level
> From User A to opensips server tls handshake is working fine but from
> opensips to User B tls handshake is going to fail please suggest how to
> resolve this .
>
>
> INFO level Logs :
>
> ERROR:core:tcp_async_connect: poll error: flags 1c
> ERROR:core:tcp_async_connect: failed to retrieve SO_ERROR [server=
> 1.2.3.4:40945] (111) Connection refused
> ERROR:proto_tls:proto_tls_send: async TCP connect failed
> ERROR:tm:msg_send: send() to 1.2.3.4:40945 for proto tls/3 failed
> ERROR:tm:t_forward_nonack: sending request failed
> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
> 1.2.3.4:34463 failed
> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
> err=Success(0)
> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
> routines:ssl3_read_bytes:sslv3 alert handshake failure
> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
> DBG level Logs :
>
> DBG:core:parse_msg: SIP Request:
> DBG:core:parse_msg:  method:  <INVITE>
> DBG:core:parse_msg:  uri:     <sip:14682973 at 1.2.3.4:34463;transport=tls>
> DBG:core:parse_msg:  version: <SIP/2.0>
> DBG:core:parse_headers: flags=ffffffffffffffff
> DBG:core:parse_via_param: found param type 232, <branch> =
> <z9hG4bK14b8.6a972877.0>; state=6
> DBG:core:parse_via_param: found param type 236, <i> = <d7b6e394>; state=16
> DBG:core:parse_via: end of header reached, state=5
> DBG:core:parse_headers: via found, flags=ffffffffffffffff
> DBG:core:parse_headers: this is the first via
> DBG:core:parse_via_param: found param type 234, <received> = <1.2.3.4>;
> state=6
> DBG:core:parse_via_param: found param type 235, <rport> = <38119>; state=6
> DBG:core:parse_via_param: found param type 232, <branch> =
> <z9hG4bKPja1ee2137-d7f4-4744-89e1-ff53b4b0b06b>; state=6
> DBG:core:parse_via_param: found param type 237, <alias> = <n/a>; state=16
> DBG:core:parse_via: end of header reached, state=5
> DBG:core:parse_headers: via found, flags=ffffffffffffffff
> DBG:core:parse_headers: parse_headers: this is the second via
> DBG:core:_parse_to: end of header reached, state=10
> DBG:core:_parse_to: display={}, ruri={sip:1001 at 1.2.3.4}
> DBG:core:get_hdr_field: <To> [26]; uri=[sip:1001 at 1.2.3.4]
> DBG:core:get_hdr_field: to body [<sip:1001 at 1.2.3.4>#015#012]
> DBG:core:get_hdr_field: cseq <CSeq>: <14318> <INVITE>
> DBG:core:get_hdr_field: content_length=717
> DBG:core:get_hdr_field: found end of header
> DBG:core:parse_headers: flags=ffffffffffffffff
> DBG:proto_tls:proto_tls_send: no open tcp connection found, opening new
> one, async = 1
> DBG:core:probe_max_sock_buff: getsockopt: snd is initially 16384
> DBG:core:probe_max_sock_buff: using snd buffer of 416 kb
> DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 141
> DBG:core:print_ip: tcpconn_new: new tcp connection to: 1.2.3.4
> DBG:core:tcpconn_new: on port 34463, proto 3
> DBG:tls_mgm:tls_find_client_domain: found TLS client domain: dom2
> DBG:tls_openssl:openssl_tls_conn_init: Creating a whole new ssl connection
> DBG:tls_openssl:openssl_tls_conn_init: Setting in CONNECT mode (client)
> DBG:proto_tls:proto_tls_send: Successfully connected from interface
> 1.2.3.4:34463 to 1.2.3.4:36463!
> DBG:proto_tls:proto_tls_send: First TCP connect attempt succeeded in less
> than 100ms, proceed to TLS connect
> DBG:tls_openssl:openssl_tls_update_fd: New fd is 141
> DBG:core:handle_worker: read response= 7f83eb6b5118, 2, fd 119 from 8
> (17254)
> DBG:core:tcpconn_add: hashes: 607, 894
> DBG:core:io_watch_add: [TCP_main] io_watch_add op (119 on 5)
> (0x55fd3f789ae0, 119, 19, 0x7f83eb6b5118,1), fd_no=27/1024
> DBG:core:handle_tcpconn_ev: data available on 0x7f83eb6b5118 119
> DBG:core:io_watch_del: [TCP_main] io_watch_del op on index 2 119
> (0x55fd3f789ae0, 119, 2, 0x0,0x1) fd_no=28 called
> DBG:core:send2worker: to tcp worker 1 (0), 0x7f83eb6b5118 rw 1
> DBG:core:handle_io: We have received conn 0x7f83eb6b5118 with rw 1 on fd 5
> DBG:core:io_watch_add: [TCP_worker] io_watch_add op (5 on 102)
> (0x55fd3f789ae0, 5, 19, 0x7f83eb6b5118,1), fd_no=4/1024
> DBG:proto_tls:tls_read_req: Using the global ( per process ) buff
> DBG:tls_openssl:openssl_tls_async_connect: handshake timeout for
> connection 0x7f83eb6b5118 10ms elapsed
> DBG:tls_openssl:openssl_tls_update_fd: New fd is 5
>
> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
> 1.2.3.4:34463 failed
> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
> err=Success(0)
> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
> routines:ssl3_read_bytes:sslv3 alert handshake failure
> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
> DBG:proto_tls:proto_tls_send: Successfully started async SSL connection
> DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 0 5
> (0x55fd3f789ae0, 5, 0, 0x10,0x3) fd_no=5 called
> DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -2, fd=5,
> id=1228827518
> DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
> DBG:tm:insert_timer_unsafe: [0]: 0x7f83eb6a9320 (12)
> DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -3, fd=-1,
> id=1228827518
> DBG:tm:t_relay_to: new transaction fwd'ed
> DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
> DBG:tm:do_t_cleanup: transaction 0x7f83eb6a90d0 already updated! Skipping
> update!
> DBG:tm:t_unref: UNREF_UNSAFE: [0x7f83eb6a90d0] after is 0
> DBG:core:destroy_avp_list: destroying list (nil)
> DBG:core:receive_msg: cleaning up
> DBG:proto_tls:tls_read_req: tls_read_req end
> DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -3 from tcp worker 0
> (1)
> DBG:core:tcpconn_destroy: delaying (0x7f83eb6b5118, flags 0038) ref = 1 ...
> DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -2 from tcp worker 0
> (0)
> DBG:core:tcpconn_destroy: destroying connection 0x7f83eb6b5118, flags 0038
> DBG:tls_openssl:openssl_tls_update_fd: New fd is 119
> DBG:tm:utimer_routine: timer routine:4,tl=0x7f83eb6a5d18 next=(nil),
> timeout=7700000
> DBG:tm:retransmission_handler: retransmission_handler : request resending
> (t=0x7f83eb6a5af8, PUBLISH s ... )
> root at devang-MS-7817:/usr/local/etc/opensips/range#
>
> I am following this OpenSIPS TLS config:
>
> socket=udp:1.2.3.4: <http://192.168.0.105:506/>5060
>
> socket=tcp:1.2.3.4: <http://192.168.0.105:506/>5060
>
> socket=tls:1.2.3.4: <http://192.168.0.105:506>5061
>
> loadmodule "tls_openssl.so"
>
>
> loadmodule "tls_mgm.so"
> # -------- TLS SERVER Certificate ---------#
> modparam("tls_mgm", "server_domain", "dom1")
> modparam("tls_mgm", "match_sip_domain", "[dom1]devang.com")
> modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5061")
> modparam("tls_mgm", "verify_cert", "[dom1]0")
> modparam("tls_mgm", "require_cert", "[dom1]0")
> modparam("tls_mgm", "tls_method", "[dom1]-")
> modparam("tls_mgm", "certificate",
> "[dom1]/usr/local/etc/opensips/tls/rootCA/ca_cert.pem")
> modparam("tls_mgm", "private_key",
> "[dom1]/usr/local/etc/opensips/tls/rootCA/private_key.pem")
>
> # --------- TLS CLIENT CERTIFICATE --------#
> modparam("tls_mgm", "client_domain", "dom2")
> modparam("tls_mgm", "match_sip_domain", "[dom2]*")
> modparam("tls_mgm", "match_ip_address", "[dom2]*")
> modparam("tls_mgm", "verify_cert", "[dom2]0")
> modparam("tls_mgm", "require_cert", "[dom2]0")
> modparam("tls_mgm", "tls_method", "[dom2]-")
> modparam("tls_mgm", "certificate",
> "[dom2]/usr/local/etc/opensips/tls/user/user-cert.pem")
> modparam("tls_mgm", "private_key",
> "[dom2]/usr/local/etc/opensips/tls/user/user-privkey.pem")
> modparam("tls_mgm", "ca_list",
> "[dom2]/usr/local/etc/opensips/tls/user/user-calist.pem")
>
>
> loadmodule "proto_tls.so"
>
> checking the connection with s_client shows below :
>
> openssl s_client -showcerts -debug -connect 1.2.3.4:5061 -bugs
> CONNECTED(00000005)
> 140510082113984:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
> no peer certificate available
> ---
> No client certificate CA names sent
> ---
> SSL handshake has read 7 bytes and written 517 bytes
> Verification: OK
> ---
> New, (NONE), Cipher is (NONE)
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> No ALPN negotiated
> Early data was not sent
> Verify return code: 0 (ok)
>
>
> Can anyone tell me what I might be missing for tls config or Please
> advise how to resolve this SSL handshake failure.
>
>
> Many Thanks
> Devang
>
>
>                                                           70,1          15%
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/e86f1832/attachment-0001.html>

From bogdan at opensips.org  Wed Nov 17 07:54:41 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 17 Nov 2021 09:54:41 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one 
related to the DHCP interface)

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
> Hi,
>
> Is there a way to get the IP address of DHCP interface to use in the 
> script? I can get the call go through if I set both the interface as 
> static.
>
> Regards
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
> ------------------------------------------------------------------------
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Tuesday, November 16, 2021, 6:45 PM
> *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP 
> address as variable
>
> Hi,
>
> via the socket_xx() vars you can get only the sockets relative to/used 
> by that call, you cannot iterate thru the listening sockets.
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>>
>> Hi,
>>
>> I have 2 listening interface for opensips 3.2. How do I get both IP 
>> address to be used as variable in opensips config file? I try to use 
>> socket_in/ socket_out but failed to get the other interface IP address.
>>
>> Thanks
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
>> Windows
>>
>>
>> _______________________________________________
>> 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/20211117/6c4707d0/attachment.html>

From bogdan at opensips.org  Wed Nov 17 07:57:11 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 17 Nov 2021 09:57:11 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
Message-ID: <c2551c1f-77d6-4004-a68b-4bf65d3d81e7@opensips.org>

Oh, I see what you mean.....well, you can define the listen socket with 
the name of the interface, not necessarily with its IP.

Like:
socket = udp:eth0:5060

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/17/21 9:54 AM, Bogdan-Andrei Iancu wrote:
> Hi,
>
> How do you define the listening socket in OpenSIPs cfg ? (the one 
> related to the DHCP interface)
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>> Hi,
>>
>> Is there a way to get the IP address of DHCP interface to use in the 
>> script? I can get the call go through if I set both the interface as 
>> static.
>>
>> Regards
>>
>> Get Outlook for Android <https://aka.ms/AAb9ysg>
>>
>> ------------------------------------------------------------------------
>> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>> *Sent:* Tuesday, November 16, 2021, 6:45 PM
>> *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
>> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP 
>> address as variable
>>
>> Hi,
>>
>> via the socket_xx() vars you can get only the sockets relative 
>> to/used by that call, you cannot iterate thru the listening sockets.
>>
>> Regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 2021
>>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>> On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>>>
>>> Hi,
>>>
>>> I have 2 listening interface for opensips 3.2. How do I get both IP 
>>> address to be used as variable in opensips config file? I try to use 
>>> socket_in/ socket_out but failed to get the other interface IP address.
>>>
>>> Thanks
>>>
>>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
>>> Windows
>>>
>>>
>>> _______________________________________________
>>> 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/20211117/5b765dc6/attachment.html>

From bogdan at opensips.org  Wed Nov 17 08:02:35 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 17 Nov 2021 10:02:35 +0200
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <CAP0uOe-4qGrQEtYR35qe9Bz3BDuMw7+i2oEwm0ssh2_20Au2mw@mail.gmail.com>
References: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>
 <CAP0uOe-4qGrQEtYR35qe9Bz3BDuMw7+i2oEwm0ssh2_20Au2mw@mail.gmail.com>
Message-ID: <895fa3cb-5649-1a00-e3b7-c10714af0261@opensips.org>

It is quite impolite and rude to put pressure here. This is a public, 
free list where people are voluntarily offer help as they can, with no 
obligation at all.

Now, in terms of your issue - with a bit of an effort, you can read the 
logs which tell you what the problem is "Connection refused", or, the 
party you are trying to connect to (1.2.3.4:40945) is not accepting your 
connection.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/17/21 8:13 AM, Devang Dhandhalya wrote:
> It's the 9th day still not getting any response . Please can Anyone 
> suggest a solution to this issue ?
>
> Many Thanks
> Devang
>
> On Tue, Nov 9, 2021 at 4:35 PM Devang Dhandhalya 
> <devang.dhandhalya at ecosmob.com <mailto:devang.dhandhalya at ecosmob.com>> 
> wrote:
>
>     Hi All
>
>     I Am Trying to Implement opensips with TLS support in a local
>     machine . I generate TLS server (rootCA) and TLS Client (user)
>     certificates using opensips-cli  .
>     softphone : Blink version : 5.1.7
>     opensips version : 3.2.2
>     Registration with tls is working fine for TLS ,  at the time of
>     calling getting below error . I check in logs at DBG level
>     From User A to opensips server tls handshake is working fine but
>     from opensips to User B tls handshake is going to fail please
>     suggest how to resolve this .
>
>     INFO level Logs :
>
>     ERROR:core:tcp_async_connect: poll error: flags 1c
>     ERROR:core:tcp_async_connect: failed to retrieve SO_ERROR
>     [server=1.2.3.4:40945 <http://1.2.3.4:40945>] (111) Connection refused
>     ERROR:proto_tls:proto_tls_send: async TCP connect failed
>     ERROR:tm:msg_send: send() to 1.2.3.4:40945 <http://1.2.3.4:40945>
>     for proto tls/3 failed
>     ERROR:tm:t_forward_nonack: sending request failed
>     ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
>     1.2.3.4:34463 <http://1.2.3.4:34463> failed
>     ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
>     err=Success(0)
>     ERROR:tls_openssl:tls_print_errstack: TLS errstack:
>     error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
>     failure
>     ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
>     DBG level Logs :
>
>     DBG:core:parse_msg: SIP Request:
>     DBG:core:parse_msg:  method:  <INVITE>
>     DBG:core:parse_msg:  uri: <sip:14682973 at 1.2.3.4:34463;transport=tls>
>     DBG:core:parse_msg:  version: <SIP/2.0>
>     DBG:core:parse_headers: flags=ffffffffffffffff
>     DBG:core:parse_via_param: found param type 232, <branch> =
>     <z9hG4bK14b8.6a972877.0>; state=6
>     DBG:core:parse_via_param: found param type 236, <i> = <d7b6e394>;
>     state=16
>     DBG:core:parse_via: end of header reached, state=5
>     DBG:core:parse_headers: via found, flags=ffffffffffffffff
>     DBG:core:parse_headers: this is the first via
>     DBG:core:parse_via_param: found param type 234, <received> =
>     <1.2.3.4>; state=6
>     DBG:core:parse_via_param: found param type 235, <rport> = <38119>;
>     state=6
>     DBG:core:parse_via_param: found param type 232, <branch> =
>     <z9hG4bKPja1ee2137-d7f4-4744-89e1-ff53b4b0b06b>; state=6
>     DBG:core:parse_via_param: found param type 237, <alias> = <n/a>;
>     state=16
>     DBG:core:parse_via: end of header reached, state=5
>     DBG:core:parse_headers: via found, flags=ffffffffffffffff
>     DBG:core:parse_headers: parse_headers: this is the second via
>     DBG:core:_parse_to: end of header reached, state=10
>     DBG:core:_parse_to: display={}, ruri={sip:1001 at 1.2.3.4
>     <mailto:sip%3A1001 at 1.2.3.4>}
>     DBG:core:get_hdr_field: <To> [26]; uri=[sip:1001 at 1.2.3.4
>     <mailto:sip%3A1001 at 1.2.3.4>]
>     DBG:core:get_hdr_field: to body [<sip:1001 at 1.2.3.4
>     <mailto:sip%3A1001 at 1.2.3.4>>#015#012]
>     DBG:core:get_hdr_field: cseq <CSeq>: <14318> <INVITE>
>     DBG:core:get_hdr_field: content_length=717
>     DBG:core:get_hdr_field: found end of header
>     DBG:core:parse_headers: flags=ffffffffffffffff
>     DBG:proto_tls:proto_tls_send: no open tcp connection found,
>     opening new one, async = 1
>     DBG:core:probe_max_sock_buff: getsockopt: snd is initially 16384
>     DBG:core:probe_max_sock_buff: using snd buffer of 416 kb
>     DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 141
>     DBG:core:print_ip: tcpconn_new: new tcp connection to: 1.2.3.4
>     DBG:core:tcpconn_new: on port 34463, proto 3
>     DBG:tls_mgm:tls_find_client_domain: found TLS client domain: dom2
>     DBG:tls_openssl:openssl_tls_conn_init: Creating a whole new ssl
>     connection
>     DBG:tls_openssl:openssl_tls_conn_init: Setting in CONNECT mode
>     (client)
>     DBG:proto_tls:proto_tls_send: Successfully connected from
>     interface 1.2.3.4:34463 <http://1.2.3.4:34463> to 1.2.3.4:36463
>     <http://1.2.3.4:36463>!
>     DBG:proto_tls:proto_tls_send: First TCP connect attempt succeeded
>     in less than 100ms, proceed to TLS connect
>     DBG:tls_openssl:openssl_tls_update_fd: New fd is 141
>     DBG:core:handle_worker: read response= 7f83eb6b5118, 2, fd 119
>     from 8 (17254)
>     DBG:core:tcpconn_add: hashes: 607, 894
>     DBG:core:io_watch_add: [TCP_main] io_watch_add op (119 on 5)
>     (0x55fd3f789ae0, 119, 19, 0x7f83eb6b5118,1), fd_no=27/1024
>     DBG:core:handle_tcpconn_ev: data available on 0x7f83eb6b5118 119
>     DBG:core:io_watch_del: [TCP_main] io_watch_del op on index 2 119
>     (0x55fd3f789ae0, 119, 2, 0x0,0x1) fd_no=28 called
>     DBG:core:send2worker: to tcp worker 1 (0), 0x7f83eb6b5118 rw 1
>     DBG:core:handle_io: We have received conn 0x7f83eb6b5118 with rw 1
>     on fd 5
>     DBG:core:io_watch_add: [TCP_worker] io_watch_add op (5 on 102)
>     (0x55fd3f789ae0, 5, 19, 0x7f83eb6b5118,1), fd_no=4/1024
>     DBG:proto_tls:tls_read_req: Using the global ( per process ) buff
>     DBG:tls_openssl:openssl_tls_async_connect: handshake timeout for
>     connection 0x7f83eb6b5118 10ms elapsed
>     DBG:tls_openssl:openssl_tls_update_fd: New fd is 5
>
>     ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
>     1.2.3.4:34463 <http://1.2.3.4:34463> failed
>     ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
>     err=Success(0)
>     ERROR:tls_openssl:tls_print_errstack: TLS errstack:
>     error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
>     failure
>     ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
>     DBG:proto_tls:proto_tls_send: Successfully started async SSL
>     connection
>     DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 0 5
>     (0x55fd3f789ae0, 5, 0, 0x10,0x3) fd_no=5 called
>     DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -2,
>     fd=5, id=1228827518
>     DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
>     DBG:tm:insert_timer_unsafe: [0]: 0x7f83eb6a9320 (12)
>     DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -3,
>     fd=-1, id=1228827518
>     DBG:tm:t_relay_to: new transaction fwd'ed
>     DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
>     DBG:tm:do_t_cleanup: transaction 0x7f83eb6a90d0 already updated!
>     Skipping update!
>     DBG:tm:t_unref: UNREF_UNSAFE: [0x7f83eb6a90d0] after is 0
>     DBG:core:destroy_avp_list: destroying list (nil)
>     DBG:core:receive_msg: cleaning up
>     DBG:proto_tls:tls_read_req: tls_read_req end
>     DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -3 from tcp
>     worker 0 (1)
>     DBG:core:tcpconn_destroy: delaying (0x7f83eb6b5118, flags 0038)
>     ref = 1 ...
>     DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -2 from tcp
>     worker 0 (0)
>     DBG:core:tcpconn_destroy: destroying connection 0x7f83eb6b5118,
>     flags 0038
>     DBG:tls_openssl:openssl_tls_update_fd: New fd is 119
>     DBG:tm:utimer_routine: timer routine:4,tl=0x7f83eb6a5d18
>     next=(nil), timeout=7700000
>     DBG:tm:retransmission_handler: retransmission_handler : request
>     resending (t=0x7f83eb6a5af8, PUBLISH s ... )
>     root at devang-MS-7817:/usr/local/etc/opensips/range#
>
>     I am following this OpenSIPS TLS config:
>
>     socket=udp:1.2.3.4: <http://192.168.0.105:506/>5060
>
>     socket=tcp:1.2.3.4: <http://192.168.0.105:506/>5060
>
>     socket=tls:1.2.3.4: <http://192.168.0.105:506>5061
>
>     loadmodule "tls_openssl.so"
>
>
>     loadmodule "tls_mgm.so"
>     # -------- TLS SERVER Certificate ---------#
>     modparam("tls_mgm", "server_domain", "dom1")
>     modparam("tls_mgm", "match_sip_domain", "[dom1]devang.com
>     <http://devang.com>")
>     modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5061
>     <http://1.2.3.4:5061>")
>     modparam("tls_mgm", "verify_cert", "[dom1]0")
>     modparam("tls_mgm", "require_cert", "[dom1]0")
>     modparam("tls_mgm", "tls_method", "[dom1]-")
>     modparam("tls_mgm", "certificate",
>     "[dom1]/usr/local/etc/opensips/tls/rootCA/ca_cert.pem")
>     modparam("tls_mgm", "private_key",
>     "[dom1]/usr/local/etc/opensips/tls/rootCA/private_key.pem")
>
>     # --------- TLS CLIENT CERTIFICATE --------#
>     modparam("tls_mgm", "client_domain", "dom2")
>     modparam("tls_mgm", "match_sip_domain", "[dom2]*")
>     modparam("tls_mgm", "match_ip_address", "[dom2]*")
>     modparam("tls_mgm", "verify_cert", "[dom2]0")
>     modparam("tls_mgm", "require_cert", "[dom2]0")
>     modparam("tls_mgm", "tls_method", "[dom2]-")
>     modparam("tls_mgm", "certificate",
>     "[dom2]/usr/local/etc/opensips/tls/user/user-cert.pem")
>     modparam("tls_mgm", "private_key",
>     "[dom2]/usr/local/etc/opensips/tls/user/user-privkey.pem")
>     modparam("tls_mgm", "ca_list",
>     "[dom2]/usr/local/etc/opensips/tls/user/user-calist.pem")
>
>
>     loadmodule "proto_tls.so"
>
>     checking the connection with s_client shows below :
>
>     openssl s_client -showcerts -debug -connect 1.2.3.4:5061
>     <http://1.2.3.4:5061> -bugs
>     CONNECTED(00000005)
>     140510082113984:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
>     unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert
>     number 112
>     no peer certificate available
>     ---
>     No client certificate CA names sent
>     ---
>     SSL handshake has read 7 bytes and written 517 bytes
>     Verification: OK
>     ---
>     New, (NONE), Cipher is (NONE)
>     Secure Renegotiation IS NOT supported
>     Compression: NONE
>     Expansion: NONE
>     No ALPN negotiated
>     Early data was not sent
>     Verify return code: 0 (ok)
>
>
>     Can anyone tell me what I might be missing for tls config or
>     Please advise how to resolve this SSL handshake failure.
>
>
>     Many Thanks
>     Devang
>
>                                 70,1          15%
>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our 
> website, any views or opinions presented in this email are solely 
> those of the originator and do not necessarily represent those of the 
> Company or its sister concerns. Any liability (in negligence, contract 
> or otherwise) arising from any third party taking any action, or 
> refraining from taking any action on the basis of any of the 
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for 
> the use of the addressee(s) and contains information that is 
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
> distribution, or copying of this communication is prohibited. Please 
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of 
> viruses, trojans, similar or new contaminants/malware, interceptions 
> or interference, and may not be compatible with your systems. You 
> shall carry out virus/malware scanning on your own before opening any 
> attachment to this e-mail. The sender of this e-mail and Company 
> including its sister concerns shall not be liable for any damage that 
> may incur to you as a result of viruses, incompleteness of this 
> message, a delay in receipt of this message or any other computer 
> problems.
>
> _______________________________________________
> 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/20211117/5cc05c5f/attachment-0001.html>

From m.putra77 at outlook.com  Wed Nov 17 08:21:07 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Wed, 17 Nov 2021 08:21:07 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
Message-ID: <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME

My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use tag to test something.

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 3:55 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one related to the DHCP interface)

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows




_______________________________________________

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/20211117/252661d2/attachment.html>

From devang.dhandhalya at ecosmob.com  Wed Nov 17 08:33:32 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 17 Nov 2021 14:03:32 +0530
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <895fa3cb-5649-1a00-e3b7-c10714af0261@opensips.org>
References: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>
 <CAP0uOe-4qGrQEtYR35qe9Bz3BDuMw7+i2oEwm0ssh2_20Au2mw@mail.gmail.com>
 <895fa3cb-5649-1a00-e3b7-c10714af0261@opensips.org>
Message-ID: <CAP0uOe_rjjrZnF_-TvUwSoAmObQGT4J7GPg56Q5omDnOy-d85Q@mail.gmail.com>

Hello Bogdan

 I Just casually write , My intention was not rude or anything else , still
it's my bad if any one feeling hurts .

as you say the party you are trying to connect to (1.2.3.4:40945) is not
accepting your connection. i check that but can you please tell me what
type of thing i have to check . means from opensips side or blink user
configuration i have add tls certificate also in user configuration .

In the opensips module parameter any configuration wrong for TLS service ?

Many Thanks
Devang



On Wed, Nov 17, 2021 at 1:32 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> It is quite impolite and rude to put pressure here. This is a public, free
> list where people are voluntarily offer help as they can, with no
> obligation at all.
>
> Now, in terms of your issue - with a bit of an effort, you can read the
> logs which tell you what the problem is "Connection refused", or, the party
> you are trying to connect to (1.2.3.4:40945) is not accepting your
> connection.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/17/21 8:13 AM, Devang Dhandhalya wrote:
>
> It's the 9th day still not getting any response . Please can Anyone
> suggest a solution to this issue ?
>
> Many Thanks
> Devang
>
> On Tue, Nov 9, 2021 at 4:35 PM Devang Dhandhalya <
> devang.dhandhalya at ecosmob.com> wrote:
>
>> Hi All
>>
>> I Am Trying to Implement opensips with TLS support in a local machine . I
>> generate TLS server (rootCA) and TLS Client (user) certificates using
>> opensips-cli  .
>> softphone : Blink version : 5.1.7
>> opensips version : 3.2.2
>> Registration with tls is working fine for TLS ,  at the time of calling
>> getting below error . I check in logs at DBG level
>> From User A to opensips server tls handshake is working fine but from
>> opensips to User B tls handshake is going to fail please suggest how to
>> resolve this .
>>
>>
>> INFO level Logs :
>>
>> ERROR:core:tcp_async_connect: poll error: flags 1c
>> ERROR:core:tcp_async_connect: failed to retrieve SO_ERROR [server=
>> 1.2.3.4:40945] (111) Connection refused
>> ERROR:proto_tls:proto_tls_send: async TCP connect failed
>> ERROR:tm:msg_send: send() to 1.2.3.4:40945 for proto tls/3 failed
>> ERROR:tm:t_forward_nonack: sending request failed
>> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
>> 1.2.3.4:34463 failed
>> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
>> err=Success(0)
>> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
>> routines:ssl3_read_bytes:sslv3 alert handshake failure
>> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>>
>> DBG level Logs :
>>
>> DBG:core:parse_msg: SIP Request:
>> DBG:core:parse_msg:  method:  <INVITE>
>> DBG:core:parse_msg:  uri:     <sip:14682973 at 1.2.3.4:34463;transport=tls>
>> DBG:core:parse_msg:  version: <SIP/2.0>
>> DBG:core:parse_headers: flags=ffffffffffffffff
>> DBG:core:parse_via_param: found param type 232, <branch> =
>> <z9hG4bK14b8.6a972877.0>; state=6
>> DBG:core:parse_via_param: found param type 236, <i> = <d7b6e394>; state=16
>> DBG:core:parse_via: end of header reached, state=5
>> DBG:core:parse_headers: via found, flags=ffffffffffffffff
>> DBG:core:parse_headers: this is the first via
>> DBG:core:parse_via_param: found param type 234, <received> = <1.2.3.4>;
>> state=6
>> DBG:core:parse_via_param: found param type 235, <rport> = <38119>; state=6
>> DBG:core:parse_via_param: found param type 232, <branch> =
>> <z9hG4bKPja1ee2137-d7f4-4744-89e1-ff53b4b0b06b>; state=6
>> DBG:core:parse_via_param: found param type 237, <alias> = <n/a>; state=16
>> DBG:core:parse_via: end of header reached, state=5
>> DBG:core:parse_headers: via found, flags=ffffffffffffffff
>> DBG:core:parse_headers: parse_headers: this is the second via
>> DBG:core:_parse_to: end of header reached, state=10
>> DBG:core:_parse_to: display={}, ruri={sip:1001 at 1.2.3.4}
>> DBG:core:get_hdr_field: <To> [26]; uri=[sip:1001 at 1.2.3.4]
>> DBG:core:get_hdr_field: to body [<sip:1001 at 1.2.3.4>#015#012]
>> DBG:core:get_hdr_field: cseq <CSeq>: <14318> <INVITE>
>> DBG:core:get_hdr_field: content_length=717
>> DBG:core:get_hdr_field: found end of header
>> DBG:core:parse_headers: flags=ffffffffffffffff
>> DBG:proto_tls:proto_tls_send: no open tcp connection found, opening new
>> one, async = 1
>> DBG:core:probe_max_sock_buff: getsockopt: snd is initially 16384
>> DBG:core:probe_max_sock_buff: using snd buffer of 416 kb
>> DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 141
>> DBG:core:print_ip: tcpconn_new: new tcp connection to: 1.2.3.4
>> DBG:core:tcpconn_new: on port 34463, proto 3
>> DBG:tls_mgm:tls_find_client_domain: found TLS client domain: dom2
>> DBG:tls_openssl:openssl_tls_conn_init: Creating a whole new ssl connection
>> DBG:tls_openssl:openssl_tls_conn_init: Setting in CONNECT mode (client)
>> DBG:proto_tls:proto_tls_send: Successfully connected from interface
>> 1.2.3.4:34463 to 1.2.3.4:36463!
>> DBG:proto_tls:proto_tls_send: First TCP connect attempt succeeded in less
>> than 100ms, proceed to TLS connect
>> DBG:tls_openssl:openssl_tls_update_fd: New fd is 141
>> DBG:core:handle_worker: read response= 7f83eb6b5118, 2, fd 119 from 8
>> (17254)
>> DBG:core:tcpconn_add: hashes: 607, 894
>> DBG:core:io_watch_add: [TCP_main] io_watch_add op (119 on 5)
>> (0x55fd3f789ae0, 119, 19, 0x7f83eb6b5118,1), fd_no=27/1024
>> DBG:core:handle_tcpconn_ev: data available on 0x7f83eb6b5118 119
>> DBG:core:io_watch_del: [TCP_main] io_watch_del op on index 2 119
>> (0x55fd3f789ae0, 119, 2, 0x0,0x1) fd_no=28 called
>> DBG:core:send2worker: to tcp worker 1 (0), 0x7f83eb6b5118 rw 1
>> DBG:core:handle_io: We have received conn 0x7f83eb6b5118 with rw 1 on fd 5
>> DBG:core:io_watch_add: [TCP_worker] io_watch_add op (5 on 102)
>> (0x55fd3f789ae0, 5, 19, 0x7f83eb6b5118,1), fd_no=4/1024
>> DBG:proto_tls:tls_read_req: Using the global ( per process ) buff
>> DBG:tls_openssl:openssl_tls_async_connect: handshake timeout for
>> connection 0x7f83eb6b5118 10ms elapsed
>> DBG:tls_openssl:openssl_tls_update_fd: New fd is 5
>>
>> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
>> 1.2.3.4:34463 failed
>> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
>> err=Success(0)
>> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
>> routines:ssl3_read_bytes:sslv3 alert handshake failure
>> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>>
>> DBG:proto_tls:proto_tls_send: Successfully started async SSL connection
>> DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 0 5
>> (0x55fd3f789ae0, 5, 0, 0x10,0x3) fd_no=5 called
>> DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -2, fd=5,
>> id=1228827518
>> DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
>> DBG:tm:insert_timer_unsafe: [0]: 0x7f83eb6a9320 (12)
>> DBG:core:tcpconn_release:  releasing con 0x7f83eb6b5118, state -3, fd=-1,
>> id=1228827518
>> DBG:tm:t_relay_to: new transaction fwd'ed
>> DBG:core:tcpconn_release:  extra_data 0x7f83eb6bdd50
>> DBG:tm:do_t_cleanup: transaction 0x7f83eb6a90d0 already updated! Skipping
>> update!
>> DBG:tm:t_unref: UNREF_UNSAFE: [0x7f83eb6a90d0] after is 0
>> DBG:core:destroy_avp_list: destroying list (nil)
>> DBG:core:receive_msg: cleaning up
>> DBG:proto_tls:tls_read_req: tls_read_req end
>> DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -3 from tcp worker 0
>> (1)
>> DBG:core:tcpconn_destroy: delaying (0x7f83eb6b5118, flags 0038) ref = 1
>> ...
>> DBG:core:handle_tcp_worker: response= 7f83eb6b5118, -2 from tcp worker 0
>> (0)
>> DBG:core:tcpconn_destroy: destroying connection 0x7f83eb6b5118, flags 0038
>> DBG:tls_openssl:openssl_tls_update_fd: New fd is 119
>> DBG:tm:utimer_routine: timer routine:4,tl=0x7f83eb6a5d18 next=(nil),
>> timeout=7700000
>> DBG:tm:retransmission_handler: retransmission_handler : request resending
>> (t=0x7f83eb6a5af8, PUBLISH s ... )
>> root at devang-MS-7817:/usr/local/etc/opensips/range#
>>
>> I am following this OpenSIPS TLS config:
>>
>> socket=udp:1.2.3.4: <http://192.168.0.105:506/>5060
>>
>> socket=tcp:1.2.3.4: <http://192.168.0.105:506/>5060
>>
>> socket=tls:1.2.3.4: <http://192.168.0.105:506>5061
>>
>> loadmodule "tls_openssl.so"
>>
>>
>> loadmodule "tls_mgm.so"
>> # -------- TLS SERVER Certificate ---------#
>> modparam("tls_mgm", "server_domain", "dom1")
>> modparam("tls_mgm", "match_sip_domain", "[dom1]devang.com")
>> modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5061")
>> modparam("tls_mgm", "verify_cert", "[dom1]0")
>> modparam("tls_mgm", "require_cert", "[dom1]0")
>> modparam("tls_mgm", "tls_method", "[dom1]-")
>> modparam("tls_mgm", "certificate",
>> "[dom1]/usr/local/etc/opensips/tls/rootCA/ca_cert.pem")
>> modparam("tls_mgm", "private_key",
>> "[dom1]/usr/local/etc/opensips/tls/rootCA/private_key.pem")
>>
>> # --------- TLS CLIENT CERTIFICATE --------#
>> modparam("tls_mgm", "client_domain", "dom2")
>> modparam("tls_mgm", "match_sip_domain", "[dom2]*")
>> modparam("tls_mgm", "match_ip_address", "[dom2]*")
>> modparam("tls_mgm", "verify_cert", "[dom2]0")
>> modparam("tls_mgm", "require_cert", "[dom2]0")
>> modparam("tls_mgm", "tls_method", "[dom2]-")
>> modparam("tls_mgm", "certificate",
>> "[dom2]/usr/local/etc/opensips/tls/user/user-cert.pem")
>> modparam("tls_mgm", "private_key",
>> "[dom2]/usr/local/etc/opensips/tls/user/user-privkey.pem")
>> modparam("tls_mgm", "ca_list",
>> "[dom2]/usr/local/etc/opensips/tls/user/user-calist.pem")
>>
>>
>> loadmodule "proto_tls.so"
>>
>> checking the connection with s_client shows below :
>>
>> openssl s_client -showcerts -debug -connect 1.2.3.4:5061 -bugs
>> CONNECTED(00000005)
>> 140510082113984:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
>> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
>> no peer certificate available
>> ---
>> No client certificate CA names sent
>> ---
>> SSL handshake has read 7 bytes and written 517 bytes
>> Verification: OK
>> ---
>> New, (NONE), Cipher is (NONE)
>> Secure Renegotiation IS NOT supported
>> Compression: NONE
>> Expansion: NONE
>> No ALPN negotiated
>> Early data was not sent
>> Verify return code: 0 (ok)
>>
>>
>> Can anyone tell me what I might be missing for tls config or Please
>> advise how to resolve this SSL handshake failure.
>>
>>
>> Many Thanks
>> Devang
>>
>>
>>                                                           70,1          15%
>>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/76358701/attachment-0001.html>

From solarmon at one-n.co.uk  Wed Nov 17 10:08:26 2021
From: solarmon at one-n.co.uk (solarmon)
Date: Wed, 17 Nov 2021 10:08:26 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
In-Reply-To: <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <CAOXfywMd2TxvAq_sUb6qV-QMD3s0=jULSv=kbcbVRWAtZKNWKQ@mail.gmail.com>

An alternative method is to use m4 to feed in the detected IP address into
a templated version of the opensips config file.



On Wed, 17 Nov 2021, 08:23 Muhamad Putra Abdullah, <m.putra77 at outlook.com>
wrote:

> Hi,
>
>
>
> socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
>
> socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME
>
>
>
> My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use
> tag to test something.
>
>
>
> Regards
>
>
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, 17 November, 2021 3:55 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
>
>
> Hi,
>
> How do you define the listening socket in OpenSIPs cfg ? (the one related
> to the DHCP interface)
>
> Regards,
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
> OpenSIPS eBootcamp 2021
>
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> Is there a way to get the IP address of DHCP interface to use in the
> script? I can get the call go through if I set both the interface as static.
>
>
>
> Regards
>
>
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
>
> ------------------------------
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org> <bogdan at opensips.org>
> *Sent:* Tuesday, November 16, 2021, 6:45 PM
> *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
>
> Hi,
>
> via the socket_xx() vars you can get only the sockets relative to/used by
> that call, you cannot iterate thru the listening sockets.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
> OpenSIPS eBootcamp 2021
>
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> I have 2 listening interface for opensips 3.2. How do I get both IP
> address to be used as variable in opensips config file? I try to use
> socket_in/ socket_out but failed to get the other interface IP address.
>
>
>
> Thanks
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows
>
>
>
>
>
> _______________________________________________
>
> 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/20211117/28d6a5a7/attachment.html>

From bogdan at opensips.org  Wed Nov 17 12:24:16 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 17 Nov 2021 14:24:16 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>

If so, when you receive a request on the external IP, the $socket_in(ip) 
should return the actual DHCP IP.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
> socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
>
> socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME
>
> My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just 
> use tag to test something.
>
> Regards
>
> *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, 17 November, 2021 3:55 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users 
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP 
> address as variable
>
> Hi,
>
> How do you define the listening socket in OpenSIPs cfg ? (the one 
> related to the DHCP interface)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
> On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>
>     Hi,
>
>     Is there a way to get the IP address of DHCP interface to use in
>     the script? I can get the call go through if I set both the
>     interface as static.
>
>     Regards
>
>     Get Outlook for Android <https://aka.ms/AAb9ysg>
>
>     ------------------------------------------------------------------------
>
>     *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Sent:* Tuesday, November 16, 2021, 6:45 PM
>     *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
>     *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
>     address as variable
>
>
>     Hi,
>
>     via the socket_xx() vars you can get only the sockets relative
>     to/used by that call, you cannot iterate thru the listening sockets.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>     OpenSIPS eBootcamp 2021
>
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
>         Hi,
>
>         I have 2 listening interface for opensips 3.2. How do I get
>         both IP address to be used as variable in opensips config
>         file? I try to use socket_in/ socket_out but failed to get the
>         other interface IP address.
>
>         Thanks
>
>         Sent from Mail
>         <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
>
>
>
>         _______________________________________________
>
>         Users mailing list
>
>         Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>

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

From devang.dhandhalya at ecosmob.com  Wed Nov 17 15:22:10 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 17 Nov 2021 20:52:10 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
Message-ID: <CAP0uOe_3ZzGevZs+aoRiEzjkjCTvqAayTbEpuCbcO9AXkJFyZg@mail.gmail.com>

hello all


Above E.164 Error still getting .Right now I'm getting the below error .
Can anyone tell me why I am getting this error ? as far as i know this
error for x5u parameter in stir_shaken_auth function , this issue coming
for certificate path or certificate file format .


I check the certificate file with .der and .cer format also .



ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal
format

ERROR:stir_shaken:w_stir_auth: Failed to add Identity header

STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1


On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hi All
>
> I configured the e164 strict mode module parameter as 0 (disabled) . but
> still i am getting errors related to its e164 format .While if orig/dest
> number is not in e164 format then also opensips have to accept it but it is
> not accepting .  I have a user like extension123 for this function I have
> to perform authentication service . if i have a user extension123 is it
> possible to perform authenticate service for this kind of user ?
>
> I think this is a bug for the e164 strict mode  module parameter . I am
> getting the below error .
>
> opensips version : 3.2.2
>
> ERROR :
>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164 format:
> extension123
>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
> (extension123)
>
>
> loadmodule "stir_shaken.so"
> modparam("stir_shaken", "auth_date_freshness", 300)
> modparam("stir_shaken", "verify_date_freshness", 300)
> modparam("stir_shaken", "require_date_hdr", 0)
> modparam("stir_shaken", "e164_strict_mode", 0)
>
> $var(orig) = $fU;
> $var(dest) = $tU
>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
> "$var(pkey)","http://localhost/certificate.pem
> ","$var(orig)","$var(dest)");
>
> Please suggest a solution to this .
>
> Many Thanks
> Devang
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/42f1a7d7/attachment.html>

From devang.dhandhalya at ecosmob.com  Wed Nov 17 15:27:51 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 17 Nov 2021 20:57:51 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
Message-ID: <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>

hello all


Above E.164 Error still getting .Right now I'm getting the below error .
Can anyone tell me why I am getting this error ? as far as i know this
error for x5u parameter in stir_shaken_auth function , this issue coming
for certificate path or certificate file format .


I check the certificate file with .der and .cer format also .

Here is the code snippet used .

$var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
"$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");


Below Error i am getting .


ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format

ERROR:stir_shaken:w_stir_auth: Failed to add Identity header

STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1


Kindly let me know if there is something wrong that I could be doing.

Many Thanks
Devang Dhandhalya


On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hi All
>
> I configured the e164 strict mode module parameter as 0 (disabled) . but
> still i am getting errors related to its e164 format .While if orig/dest
> number is not in e164 format then also opensips have to accept it but it is
> not accepting .  I have a user like extension123 for this function I have
> to perform authentication service . if i have a user extension123 is it
> possible to perform authenticate service for this kind of user ?
>
> I think this is a bug for the e164 strict mode  module parameter . I am
> getting the below error .
>
> opensips version : 3.2.2
>
> ERROR :
>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164 format:
> extension123
>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
> (extension123)
>
>
> loadmodule "stir_shaken.so"
> modparam("stir_shaken", "auth_date_freshness", 300)
> modparam("stir_shaken", "verify_date_freshness", 300)
> modparam("stir_shaken", "require_date_hdr", 0)
> modparam("stir_shaken", "e164_strict_mode", 0)
>
> $var(orig) = $fU;
> $var(dest) = $tU
>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
> "$var(pkey)","http://localhost/certificate.pem
> ","$var(orig)","$var(dest)");
>
> Please suggest a solution to this .
>
> Many Thanks
> Devang
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/6ea98fdd/attachment.html>

From david.villasmil.work at gmail.com  Wed Nov 17 16:07:58 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Wed, 17 Nov 2021 16:07:58 +0000
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
 not working .
In-Reply-To: <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
Message-ID: <CAFGRPVpneQo8KLo2i1xR=AYSDQ5=SadBYQWjBP_w3ydTnCGdhw@mail.gmail.com>

Hello,

What does the orig/dest look like in the payload?

On Wed, 17 Nov 2021 at 15:28, Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> hello all
>
>
> Above E.164 Error still getting .Right now I'm getting the below error .
> Can anyone tell me why I am getting this error ? as far as i know this
> error for x5u parameter in stir_shaken_auth function , this issue coming
> for certificate path or certificate file format .
>
>
> I check the certificate file with .der and .cer format also .
>
> Here is the code snippet used .
>
> $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)", "$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");
>
>
> Below Error i am getting .
>
>
> ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>
> ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>
> STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>
>
> Kindly let me know if there is something wrong that I could be doing.
>
> Many Thanks
>
>
> Devang Dhandhalya
>
>
> On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
> devang.dhandhalya at ecosmob.com> wrote:
>
>> Hi All
>>
>> I configured the e164 strict mode module parameter as 0 (disabled) . but
>> still i am getting errors related to its e164 format .While if orig/dest
>> number is not in e164 format then also opensips have to accept it but it is
>> not accepting .  I have a user like extension123 for this function I have
>> to perform authentication service . if i have a user extension123 is it
>> possible to perform authenticate service for this kind of user ?
>>
>> I think this is a bug for the e164 strict mode  module parameter . I am
>> getting the below error .
>>
>> opensips version : 3.2.2
>>
>> ERROR :
>>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164
>> format: extension123
>>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
>> (extension123)
>>
>>
>> loadmodule "stir_shaken.so"
>> modparam("stir_shaken", "auth_date_freshness", 300)
>> modparam("stir_shaken", "verify_date_freshness", 300)
>> modparam("stir_shaken", "require_date_hdr", 0)
>> modparam("stir_shaken", "e164_strict_mode", 0)
>>
>> $var(orig) = $fU;
>> $var(dest) = $tU
>>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
>> "$var(pkey)","http://localhost/certificate.pem
>> ","$var(orig)","$var(dest)");
>>
>> Please suggest a solution to this .
>>
>> Many Thanks
>> Devang
>>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/80d3a6a1/attachment-0001.html>

From aronp at guaranteedplus.com  Wed Nov 17 19:20:20 2021
From: aronp at guaranteedplus.com (Podrigal, Aron)
Date: Wed, 17 Nov 2021 13:20:20 -0600
Subject: [OpenSIPS-Users] Opensips segfault after adding acc_extra field
In-Reply-To: <8ae76bce-19ac-e157-d2ba-c9b783c8df5e@opensips.org>
References: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>
 <CANJp-yi6w2O1sqCHtycATJa8Ve3Xq6gYDujcBFtC0im4KrQPZg@mail.gmail.com>
 <8ae76bce-19ac-e157-d2ba-c9b783c8df5e@opensips.org>
Message-ID: <CANJp-yhb4WmFqboMAV4h9B7XFf-3dFZcCSQpM70s6vieXRUVNA@mail.gmail.com>

Hi Bogdan-Andrei

I opened a github issue
https://github.com/OpenSIPS/opensips/issues/2691

On Tue, Nov 16, 2021 at 5:34 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Aron,
>
> Could you try to get a corefile and back trace here ?
>
> https://opensips.org/Documentation/TroubleShooting-Crash
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/10/21 9:57 PM, Podrigal, Aron wrote:
>
> Hi Core Devs,
>
> Any idea or direction on how to handle this?
>
>
> For now,
> I think of the best way to handle this as a workaround, to spin up a new
> instance and reroute all traffic temporarily until all ongoing dialogs are
> completed, and then restart.
>
> But this is really important, as it makes it very difficult to deploy
> changes to acc...
>
>
> On Wed, Nov 3, 2021, 8:17 PM Podrigal, Aron <aronp at guaranteedplus.com>
> wrote:
>
>> Hi
>>
>> I added another field to my acc_extra and after restarting opensips, it
>> kept crashing right away after the restart.
>>
>> Here are the relevant log lines
>>
>> I got a thousand lines saying
>> Nov 03 20:48:03 snap-p1 opensips-snap[1636]: WARNING:acc:restore_extra:
>> extra tags were added/removed since last run!won't restore values!
>>
>> Then 2 - 3 lines afterwards
>>
>> Nov 03 20:48:04 p1 opensips[1651]: CRITICAL:core:sig_usr: segfault in
>> process pid: 1651, id: 7
>> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: child process
>> 1651 exited by a signal 11
>> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: core was not
>> generated
>> Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs: terminating
>> due to SIGCHLD
>> Nov 03 20:48:04 p1 opensips[1643]: INFO:core:sig_usr: signal 15 received
>> Nov 03 20:48:04 p1 opensips[1642]: INFO:core:sig_usr: signal 15 received
>>
>> I use opensips version 3.1 Rev 5cdfedebbe0
>>
>> Any idea what can be causing this?
>>
>> I have 2 acc targets one db and one log. And I added the acc_extra field
>> only to the log.
>>
>>
>> Thanks
>>
>>
>> --
>>
>> -
>> Aron Podrigal
>>
>>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

-- 

-
Aron Podrigal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211117/dc8c89e6/attachment.html>

From rob.dyck at telus.net  Wed Nov 17 19:55:37 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Wed, 17 Nov 2021 11:55:37 -0800
Subject: [OpenSIPS-Users] msilo module offline message time stamp
In-Reply-To: <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>
References: <2270103.OYXXYNVTWy@blacky>
 <9c73e663-3c1a-e470-130a-ce2c74457607@opensips.org>
Message-ID: <2668757.mvXUDI8C0e@blacky>

Found the patches. Applied, recompiled, and reinstalled the module.
All good now.
Thanks

On Tuesday, November 16, 2021 2:54:02 A.M. PST Bogdan-Andrei Iancu wrote:
> Hi Robert,
> 
> What OpenSIPS version are you using? Asking as I remember of a recent
> fix in that area [1]
> 
> [1]
> https://github.com/OpenSIPS/opensips/commit/cc20f738b83f5a9c7f24630309ddb5ba
> b889bf56
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> 
> On 11/13/21 12:12 AM, Robert Dyck wrote:
> > How does one set the time stamp that openips prefixes to an offline
> > message that is sent when the UA registers?
> > 
> > 2021-11-12 14:06 from 5 "[Offline message - Wed Dec 31 16:00:00 1969 ] HI
> > THERE"
> > 
> > Thanks, Rob
> > 
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users






From m.putra77 at outlook.com  Thu Nov 18 02:50:23 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Thu, 18 Nov 2021 02:50:23 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
Message-ID: <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

Ok. I'm totally in learning process.
Let me explain my test deployment. I have 2 separate network that connected via opensips server.

Internal SIP Server                                       Opensips Server (2 NIC)                                             External SIP Server
(User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |   (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)

What my intension is to relay calls between Internal and External SIP server via Opensips server.
I use this method to achieve this:

               socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)
               .
               .
               # From Internal to External
               # Testing one number only first 634 to 605
              if ($rU=~"^605") {
                              sethostport("EXTERNAL_IP:5060");
                               $socket_out = "udp:EXTERNAL_IP:5060";
                               rtpproxy_engage("ier");
                               route(relay);
                               exit;
               }

               # From External to internal
               # Testing one number only first 605 to 634
if ($rU=~"^634"){
                              sethostport("192.168.1.2:5060");
                               $socket_out = "udp:192.168.1.2:5060";
                               rtpproxy_engage("eir");
                               route(relay);
                               exit;
               }

I have no problem on call from external to internal because I know the IP address of internal opensips server, the problem is call from internal to external.
Is there better solutions than this?

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 8:24 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

If so, when you receive a request on the external IP, the $socket_in(ip) should return the actual DHCP IP.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
Hi,

socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME

My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use tag to test something.

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 3:55 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one related to the DHCP interface)

Regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows





_______________________________________________

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/20211118/0a8ce342/attachment-0001.html>

From eremina.net at gmail.com  Thu Nov 18 05:58:32 2021
From: eremina.net at gmail.com (Pavel Eremin)
Date: Thu, 18 Nov 2021 10:58:32 +0500
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
	variable
In-Reply-To: <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <CAF3UBt1qFMuZZpghBOnFPbO7xHFzPg_6SSBE2XkK6Gqn1DpK+A@mail.gmail.com>

I am not sure, but seems you are sending calls to the same IP that you have
on Opensips? like SIP -> IP_A (opensips) -> IP_B(OPensips).
if you want to send a call through an external interface just send call to
some external IP (like sethost("ANY EXTERNAL IP");) and opensips will do
that with an interface like unix do.


socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)

socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)

               .

               .

               # From Internal to External

               # Testing one number only first 634 to 605

              if ($rU=~"^605") {

                              sethostport("EXTERNAL_IP:5060");

                               $socket_out = "udp:EXTERNAL_IP:5060";

...



               # From External to internal

               # Testing one number only first 605 to 634

if ($rU=~"^634"){

                              sethostport("192.168.1.2:5060");

                               $socket_out = "udp:192.168.1.2:5060";

...

чт, 18 нояб. 2021 г. в 07:53, Muhamad Putra Abdullah <m.putra77 at outlook.com
>:

> Hi,
>
>
>
> Ok. I’m totally in learning process.
>
> Let me explain my test deployment. I have 2 separate network that
> connected via opensips server.
>
>
>
> Internal SIP Server                                       Opensips Server
> (2 NIC)                                             External SIP Server
>
> (User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |   (EXTERNAL_IP)
> DHCP IP - - - - - - - - 172.16.16.1 (User 605)
>
>
>
> What my intension is to relay calls between Internal and External SIP
> server via Opensips server.
>
> I use this method to achieve this:
>
>
>
>                socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
>
> socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)
>
>                .
>
>                .
>
>                # From Internal to External
>
>                # Testing one number only first 634 to 605
>
>               if ($rU=~"^605") {
>
>                               sethostport("EXTERNAL_IP:5060");
>
>                                $socket_out = "udp:EXTERNAL_IP:5060";
>
>                                rtpproxy_engage("ier");
>
>                                route(relay);
>
>                                exit;
>
>                }
>
>
>
>                # From External to internal
>
>                # Testing one number only first 605 to 634
>
> if ($rU=~"^634"){
>
>                               sethostport("192.168.1.2:5060");
>
>                                $socket_out = "udp:192.168.1.2:5060";
>
>                                rtpproxy_engage("eir");
>
>                                route(relay);
>
>                                exit;
>
>                }
>
>
>
> I have no problem on call from external to internal because I know the IP
> address of internal opensips server, the problem is call from internal to
> external.
>
> Is there better solutions than this?
>
>
>
> Regards
>
>
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, 17 November, 2021 8:24 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
>
>
> If so, when you receive a request on the external IP, the $socket_in(ip)
> should return the actual DHCP IP.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
> OpenSIPS eBootcamp 2021
>
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
>
> socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME
>
>
>
> My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use
> tag to test something.
>
>
>
> Regards
>
>
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org> <bogdan at opensips.org>
> *Sent:* Wednesday, 17 November, 2021 3:55 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>
> <m.putra77 at outlook.com>; OpenSIPS users mailling list
> <users at lists.opensips.org> <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
>
>
> Hi,
>
> How do you define the listening socket in OpenSIPs cfg ? (the one related
> to the DHCP interface)
>
> Regards,
>
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
> OpenSIPS eBootcamp 2021
>
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> Is there a way to get the IP address of DHCP interface to use in the
> script? I can get the call go through if I set both the interface as static.
>
>
>
> Regards
>
>
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
>
>
> ------------------------------
>
> *From:* Bogdan-Andrei Iancu <bogdan at opensips.org> <bogdan at opensips.org>
> *Sent:* Tuesday, November 16, 2021, 6:45 PM
> *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
> address as variable
>
>
> Hi,
>
> via the socket_xx() vars you can get only the sockets relative to/used by
> that call, you cannot iterate thru the listening sockets.
>
> Regards,
>
>
> Bogdan-Andrei Iancu
>
>
>
> OpenSIPS Founder and Developer
>
>   https://www.opensips-solutions.com
>
> OpenSIPS eBootcamp 2021
>
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
>
>
> I have 2 listening interface for opensips 3.2. How do I get both IP
> address to be used as variable in opensips config file? I try to use
> socket_in/ socket_out but failed to get the other interface IP address.
>
>
>
> Thanks
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows
>
>
>
>
>
>
> _______________________________________________
>
> 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/20211118/ba6717b0/attachment-0001.html>

From bogdan at opensips.org  Thu Nov 18 09:47:38 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 18 Nov 2021 11:47:38 +0200
Subject: [OpenSIPS-Users] Opensips segfault after adding acc_extra field
In-Reply-To: <CANJp-yhb4WmFqboMAV4h9B7XFf-3dFZcCSQpM70s6vieXRUVNA@mail.gmail.com>
References: <CANJp-yj1ambV8Y7Uuw2ttkdFVK9=MTVAEnju=hQrFrY1kOR=YA@mail.gmail.com>
 <CANJp-yi6w2O1sqCHtycATJa8Ve3Xq6gYDujcBFtC0im4KrQPZg@mail.gmail.com>
 <8ae76bce-19ac-e157-d2ba-c9b783c8df5e@opensips.org>
 <CANJp-yhb4WmFqboMAV4h9B7XFf-3dFZcCSQpM70s6vieXRUVNA@mail.gmail.com>
Message-ID: <f43b9580-2a64-e350-de39-68933c4ae793@opensips.org>

Thanks Aron,

I will check over there.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/17/21 9:20 PM, Podrigal, Aron wrote:
> Hi Bogdan-Andrei
>
> I opened a github issue
> https://github.com/OpenSIPS/opensips/issues/2691 
> <https://github.com/OpenSIPS/opensips/issues/2691>
>
> On Tue, Nov 16, 2021 at 5:34 AM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Aron,
>
>     Could you try to get a corefile and back trace here ?
>
>     https://opensips.org/Documentation/TroubleShooting-Crash
>     <https://opensips.org/Documentation/TroubleShooting-Crash>
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS eBootcamp 2021
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 11/10/21 9:57 PM, Podrigal, Aron wrote:
>>     Hi Core Devs,
>>
>>     Any idea or direction on how to handle this?
>>
>>
>>     For now,
>>     I think of the best way to handle this as a workaround, to spin
>>     up a new instance and reroute all traffic temporarily until all
>>     ongoing dialogs are completed, and then restart.
>>
>>     But this is really important, as it makes it very difficult to
>>     deploy changes to acc...
>>
>>
>>     On Wed, Nov 3, 2021, 8:17 PM Podrigal, Aron
>>     <aronp at guaranteedplus.com <mailto:aronp at guaranteedplus.com>> wrote:
>>
>>         Hi
>>
>>         I added another field to my acc_extra and after restarting
>>         opensips, it kept crashing right away after the restart.
>>
>>         Here are the relevant log lines
>>
>>         I got a thousand lines saying
>>         Nov 03 20:48:03 snap-p1 opensips-snap[1636]:
>>         WARNING:acc:restore_extra: extra tags were added/removed
>>         since last run!won't restore values!
>>
>>         Then 2 - 3 lines afterwards
>>
>>         Nov 03 20:48:04 p1 opensips[1651]: CRITICAL:core:sig_usr:
>>         segfault in process pid: 1651, id: 7
>>         Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs:
>>         child process 1651 exited by a signal 11
>>         Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs:
>>         core was not generated
>>         Nov 03 20:48:04 p1 opensips[1636]: INFO:core:handle_sigs:
>>         terminating due to SIGCHLD
>>         Nov 03 20:48:04 p1 opensips[1643]: INFO:core:sig_usr: signal
>>         15 received
>>         Nov 03 20:48:04 p1 opensips[1642]: INFO:core:sig_usr: signal
>>         15 received
>>
>>         I use opensips version 3.1 Rev 5cdfedebbe0
>>
>>         Any idea what can be causing this?
>>
>>         I have 2 acc targets one db and one log. And I added the
>>         acc_extra field only to the log.
>>
>>
>>         Thanks
>>
>>
>>         -- 
>>
>>         -
>>         Aron Podrigal
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
>
>
> -- 
>
> -
> Aron Podrigal
>

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

From pkelly at gmail.com  Thu Nov 18 10:02:14 2021
From: pkelly at gmail.com (Pete Kelly)
Date: Thu, 18 Nov 2021 10:02:14 +0000
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
Message-ID: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>

Hi

I notice that the timerec format has been updated in 3.2, specifically for
the drouting module.

The migration document mentions that there are a number of changes to the
format.

Migration document:
https://www.opensips.org/Documentation/Migration-3-1-0-to-3-2-0#toc18

However the format is documented the same way in both 3.1 and 3.2 within
the "More on time recurrence" section

3.1: https://opensips.org/html/docs/modules/3.1.x/drouting.html
3.2: https://opensips.org/html/docs/modules/3.2.x/drouting.html

Should the 3.2 version be updated to reference the new format?

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

From liviu at opensips.org  Thu Nov 18 10:04:11 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 18 Nov 2021 12:04:11 +0200
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
Message-ID: <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>

On 18.11.2021 12:02, Pete Kelly wrote:
> However the format is documented the same way in both 3.1 and 3.2 
> within the "More on time recurrence" section
>
> 3.1: https://opensips.org/html/docs/modules/3.1.x/drouting.html 
> <https://opensips.org/html/docs/modules/3.1.x/drouting.html>
> 3.2: https://opensips.org/html/docs/modules/3.2.x/drouting.html 
> <https://opensips.org/html/docs/modules/3.2.x/drouting.html>
>
> Should the 3.2 version be updated to reference the new format?

Hi Pete,

Good catch, thanks!  That section definitely slipped through the cracks 
and needs to be updated as well.

Best Regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

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

From pkelly at gmail.com  Thu Nov 18 10:09:44 2021
From: pkelly at gmail.com (Pete Kelly)
Date: Thu, 18 Nov 2021 10:09:44 +0000
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
 <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
Message-ID: <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>

Cool, it's not just me then!

It looks like there are quite a few inconsistencies on the drouting
documentation page versus the docs here
https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec -
so maybe just a link or reference to check_time_rec would work for
consistency?

Pete

On Thu, 18 Nov 2021 at 10:04, Liviu Chircu <liviu at opensips.org> wrote:

> On 18.11.2021 12:02, Pete Kelly wrote:
>
> However the format is documented the same way in both 3.1 and 3.2 within
> the "More on time recurrence" section
>
> 3.1: https://opensips.org/html/docs/modules/3.1.x/drouting.html
> 3.2: https://opensips.org/html/docs/modules/3.2.x/drouting.html
>
> Should the 3.2 version be updated to reference the new format?
>
> Hi Pete,
>
> Good catch, thanks!  That section definitely slipped through the cracks
> and needs to be updated as well.
>
> Best Regards,
>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS eBootcamp 2021: www.opensips.org/training
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211118/25388a90/attachment-0001.html>

From liviu at opensips.org  Thu Nov 18 10:13:21 2021
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 18 Nov 2021 12:13:21 +0200
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
 <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
 <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>
Message-ID: <fa916322-8b1c-1c05-742f-a4aba3dd39ff@opensips.org>

On 18.11.2021 12:09, Pete Kelly wrote:
> It looks like there are quite a few inconsistencies on the drouting 
> documentation page versus the docs here 
> https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec 
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec> 
> - so maybe just a link or reference to check_time_rec would work for 
> consistency?

Most likely, any timerec-related info on that page is outdated.  Will 
double-check all the content when I get to this task.  I like the idea 
to link to check_time_rec(), as it will future-proof the drouting docs 
against changes to the core, common function.

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training



From Ben.Newlin at genesys.com  Thu Nov 18 14:04:07 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Thu, 18 Nov 2021 14:04:07 +0000
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <fa916322-8b1c-1c05-742f-a4aba3dd39ff@opensips.org>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
 <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
 <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>
 <fa916322-8b1c-1c05-742f-a4aba3dd39ff@opensips.org>
Message-ID: <BN0PR10MB5208EA4C8F78BD464B631516959B9@BN0PR10MB5208.namprd10.prod.outlook.com>

While you are in the drouting module docs, there are multiple places in there where the changes from flags to sort_alg were not documented, especially for dr_carriers routing.

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Liviu Chircu <liviu at opensips.org>
Date: Thursday, November 18, 2021 at 5:14 AM
To: pkelly at gmail.com <pkelly at gmail.com>
Cc: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
On 18.11.2021 12:09, Pete Kelly wrote:
> It looks like there are quite a few inconsistencies on the drouting
> documentation page versus the docs here
> https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec>
> - so maybe just a link or reference to check_time_rec would work for
> consistency?

Most likely, any timerec-related info on that page is outdated.  Will
double-check all the content when I get to this task.  I like the idea
to link to check_time_rec(), as it will future-proof the drouting docs
against changes to the core, common function.

--
Liviu Chircu
www.twitter.com/liviuchircu<http://www.twitter.com/liviuchircu> | www.opensips-solutions.com<http://www.opensips-solutions.com>
OpenSIPS eBootcamp 2021: www.opensips.org/training<http://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/20211118/db34e256/attachment.html>

From ag at ag-projects.com  Thu Nov 18 19:09:53 2021
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 18 Nov 2021 16:09:53 -0300
Subject: [OpenSIPS-Users] Offline messaging server
Message-ID: <229ABC04-E8E3-4480-A2BE-E04F83DA31A7@ag-projects.com>

You can now use Sylk Server as SIP messaging server, is very use to use (zero configuration) and should interoperate easy with any SIP client or Proxy. The functionality is similar to what WhatsApp and Telegram offer with the difference that both client and server software are fully open source and based on open standards.

Integration guide with OpenSIPS is available at:

https://sylkserver.com/sipwebrtc-messaging-server/

Regards,
Adrian



From vasilios.tzanoudakis at voiceland.gr  Thu Nov 18 19:39:13 2021
From: vasilios.tzanoudakis at voiceland.gr (Vasilios Tzanoudakis)
Date: Thu, 18 Nov 2021 21:39:13 +0200
Subject: [OpenSIPS-Users] Offline messaging server
In-Reply-To: <229ABC04-E8E3-4480-A2BE-E04F83DA31A7@ag-projects.com>
References: <229ABC04-E8E3-4480-A2BE-E04F83DA31A7@ag-projects.com>
Message-ID: <CADTki+B1a7o=ei-R0TNGa_9NCebTHbvVPrrYADxBhg-H=NUA_w@mail.gmail.com>

Thank you once again for sharing another great opensource project Adrian!!!


Στις Πέμ, 18 Νοε 2021, 21:11 ο χρήστης Adrian Georgescu <ag at ag-projects.com>
έγραψε:

> You can now use Sylk Server as SIP messaging server, is very use to use
> (zero configuration) and should interoperate easy with any SIP client or
> Proxy. The functionality is similar to what WhatsApp and Telegram offer
> with the difference that both client and server software are fully open
> source and based on open standards.
>
> Integration guide with OpenSIPS is available at:
>
> https://sylkserver.com/sipwebrtc-messaging-server/
>
> Regards,
> Adrian
>
>
> _______________________________________________
> 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/20211118/3a1b1232/attachment.html>

From vladp at opensips.org  Thu Nov 18 21:36:16 2021
From: vladp at opensips.org (Vlad Patrascu)
Date: Thu, 18 Nov 2021 23:36:16 +0200
Subject: [OpenSIPS-Users] 3.2.3 TLS issue
In-Reply-To: <0d4f4824-7beb-6059-8627-f42cd89e0eb8@switchtel.co.za>
References: <94f96f03-117b-2bbf-ac64-965eb7123a6d@switchtel.co.za>
 <32fbef45-d1dd-e29a-eec8-19fd96aac0c3@switchtel.co.za>
 <CAOvQDevwnYtdyqL=v69GNpyGPKvgYsnPoC38o+h-5aeS02bhaA@mail.gmail.com>
 <44251a97-5413-b95a-415e-8e12a412cbb6@switchtel.co.za>
 <CAEX38CMHzJsiiA6ZWtR0gwUEUQzQ5gKZCbKAfSEk6Sp-Eu6kUA@mail.gmail.com>
 <0d4f4824-7beb-6059-8627-f42cd89e0eb8@switchtel.co.za>
Message-ID: <2d78003c-0463-8456-391f-56187d46ae13@opensips.org>

Hi Gregory,

It is difficult to draw any conclusions without a backtrace so I'm 
hoping you'll be able to get the proper core dumps again in order to 
investigate this further.

Regards,

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

On 12.11.2021 14:44, Gregory Massel wrote:
>
> Sorry, I do have the core files, however, my /usr/sbin/opensips is now 
> 3.2.2 and the core dumps were taken against 3.2.3.
>
> I should have thought to get the backtrace before downgrading.
>
> This is a production server, however, I will try and schedule some 
> downtime and then restore 3.2.3 to generate the backtrace and will try 
> out the nightly release.
>
> --Greg
>
>
>
> _______________________________________________
> 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/20211118/f4bc29c7/attachment.html>

From vladp at opensips.org  Thu Nov 18 22:13:07 2021
From: vladp at opensips.org (Vlad Patrascu)
Date: Fri, 19 Nov 2021 00:13:07 +0200
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
 not working .
In-Reply-To: <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
Message-ID: <0d7e402a-5074-376f-ab1a-5caf3dfd0dd3@opensips.org>

Hi Devang,

The error:

ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format

may be a bit misleading as the private key and certificate must be 
provided in PEM format to the stir_shaken_auth() function. The DER 
format that the error refers to is used only internally, for an 
intermediary step. On the other hand, you may get the same error if the 
private key is not generated as an "prime256v1" EC key.

Regarding the e164_strict_mode module parameter, the orig/dest number 
should still be in E.164 format, except the leading '+' sign, which is 
not required when the parameter is turned off. The parameter is also 
related to the type of URI required (tel URI / sip URI with the 
"user=phone" parameter).

Regards,

Vlad

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

On 17.11.2021 17:27, Devang Dhandhalya wrote:
> hello all
>
>
> Above E.164 Error still getting .Right now I'm getting the below error .
> Can anyone tell me why I am getting this error ? as far as i know this
> error for x5u parameter in stir_shaken_auth function , this issue coming
> for certificate path or certificate file format .
>
>
> I check the certificate file with .der and .cer format also .
>
> Here is the code snippet used .
>
>
> $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)", 
> "$var(pkey)","http://localhost/certificate.pem 
> <http://localhost/certificate.pem>","$var(orig)","$var(dest)");
>
> Below Error i am getting .
>
>
> ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>
> ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>
> STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>
> Kindly let me know if there is something wrong that I could be doing. 
> Many Thanks Devang Dhandhalya
>
>
> On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya 
> <devang.dhandhalya at ecosmob.com <mailto:devang.dhandhalya at ecosmob.com>> 
> wrote:
>
>     Hi All
>
>     I configured the e164 strict mode module parameter as 0 (disabled)
>     . but still i am getting errors related to its e164 format .While
>     if orig/dest number is not in e164 format then also opensips have
>     to accept it but it is not accepting .  I have a user like
>     extension123 for this function I have to perform authentication
>     service . if i have a user extension123 is it possible to perform
>     authenticate service for this kind of user ?
>
>     I think this is a bug for the e164 strict mode  module parameter .
>     I am getting the below error .
>
>     opensips version : 3.2.2
>
>     ERROR :
>      ERROR:stir_shaken:check_passport_phonenum: number is not in E.164
>     format: extension123
>      ERROR:stir_shaken:w_stir_auth: failed to validate Originator
>     number (extension123)
>
>
>     loadmodule "stir_shaken.so"
>     modparam("stir_shaken", "auth_date_freshness", 300)
>     modparam("stir_shaken", "verify_date_freshness", 300)
>     modparam("stir_shaken", "require_date_hdr", 0)
>     modparam("stir_shaken", "e164_strict_mode", 0)
>
>     $var(orig) = $fU;
>     $var(dest) = $tU
>      $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
>     "$var(pkey)","http://localhost/certificate.pem
>     <http://localhost/certificate.pem>","$var(orig)","$var(dest)");
>
>     Please suggest a solution to this .
>
>     Many Thanks
>     Devang
>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our 
> website, any views or opinions presented in this email are solely 
> those of the originator and do not necessarily represent those of the 
> Company or its sister concerns. Any liability (in negligence, contract 
> or otherwise) arising from any third party taking any action, or 
> refraining from taking any action on the basis of any of the 
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for 
> the use of the addressee(s) and contains information that is 
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
> distribution, or copying of this communication is prohibited. Please 
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of 
> viruses, trojans, similar or new contaminants/malware, interceptions 
> or interference, and may not be compatible with your systems. You 
> shall carry out virus/malware scanning on your own before opening any 
> attachment to this e-mail. The sender of this e-mail and Company 
> including its sister concerns shall not be liable for any damage that 
> may incur to you as a result of viruses, incompleteness of this 
> message, a delay in receipt of this message or any other computer 
> problems.
>
> _______________________________________________
> 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/20211119/9e015801/attachment-0001.html>

From vladp at opensips.org  Thu Nov 18 22:20:45 2021
From: vladp at opensips.org (Vlad Patrascu)
Date: Fri, 19 Nov 2021 00:20:45 +0200
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <CAP0uOe_rjjrZnF_-TvUwSoAmObQGT4J7GPg56Q5omDnOy-d85Q@mail.gmail.com>
References: <CAP0uOe_a2Du7RQHdBfmaVs5MR65CJhFkjWofF+WTbXB9WkD8-Q@mail.gmail.com>
 <CAP0uOe-4qGrQEtYR35qe9Bz3BDuMw7+i2oEwm0ssh2_20Au2mw@mail.gmail.com>
 <895fa3cb-5649-1a00-e3b7-c10714af0261@opensips.org>
 <CAP0uOe_rjjrZnF_-TvUwSoAmObQGT4J7GPg56Q5omDnOy-d85Q@mail.gmail.com>
Message-ID: <33edae53-f10f-0c3c-3570-b6224ffbe999@opensips.org>

Hi Devang,

The tls_mgm module configuration looks OK. Have you also tried to 
connect with openssl s_client to the TLS endpoint?

Regards,

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

On 17.11.2021 10:33, Devang Dhandhalya wrote:
> Hello Bogdan
>
>  I Just casually write , My intention was not rude or anything else , 
> still it's my bad if any one feeling hurts .
>
> as you say the party you are trying to connect to (1.2.3.4:40945 
> <http://1.2.3.4:40945/>) is not accepting your connection. i check 
> that but can you please tell me what type of thing i have to check . 
> means from opensips side or blink user configuration i have add tls 
> certificate also in user configuration .
>
> In the opensips module parameter any configuration wrong for TLS 
> service ?
>
> Many Thanks
> Devang
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our 
> website, any views or opinions presented in this email are solely 
> those of the originator and do not necessarily represent those of the 
> Company or its sister concerns. Any liability (in negligence, contract 
> or otherwise) arising from any third party taking any action, or 
> refraining from taking any action on the basis of any of the 
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for 
> the use of the addressee(s) and contains information that is 
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
> distribution, or copying of this communication is prohibited. Please 
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of 
> viruses, trojans, similar or new contaminants/malware, interceptions 
> or interference, and may not be compatible with your systems. You 
> shall carry out virus/malware scanning on your own before opening any 
> attachment to this e-mail. The sender of this e-mail and Company 
> including its sister concerns shall not be liable for any damage that 
> may incur to you as a result of viruses, incompleteness of this 
> message, a delay in receipt of this message or any other computer 
> problems.
>
> _______________________________________________
> 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/20211119/6d5c635b/attachment.html>

From jehanzaib.kiani at gmail.com  Fri Nov 19 04:04:09 2021
From: jehanzaib.kiani at gmail.com (Jehanzaib Younis)
Date: Fri, 19 Nov 2021 17:04:09 +1300
Subject: [OpenSIPS-Users] Syntax in 3.2
Message-ID: <CAKrJzCyRAQEY-yLcEFfJtEHfrkWUQnxpKpPnrXF-gqmexqKmCA@mail.gmail.com>

Hi experts,

I have just upgraded my old opensips to 3.2 version. Getting quite a few
syntax errors. Running out of time, so thought maybe someone can quickly
help out .

The error comes at if(status=~"[12][0-9][0-9]")
May be someone can write us the correct syntax for status code checking?

Thank you in advance

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

From bogdan at opensips.org  Fri Nov 19 07:11:01 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 19 Nov 2021 09:11:01 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>

Hi,

I see, you start listening on an interface (enp2s0), which translates 
into the DHCP IP, but you can not use the socket/listener to do a force 
send socket ....as there is no way to reference it. Unfortunately 
something like that is not possible right now, but I see it as a 
valuable addition.

For the moment, what you can do is to use some pre-processing (see [1]) 
in order to fill in your CFG the actual IP - and do an IP detection from 
the opensips init.d / startup script.


[1] https://www.opensips.org/Documentation/Templating-Config-Files-3-0

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/18/21 4:50 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
> Ok. I’m totally in learning process.
>
> Let me explain my test deployment. I have 2 separate network that 
> connected via opensips server.
>
> Internal SIP Server                                       Opensips 
> Server (2 NIC)                         External SIP Server
>
> (User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    | 
> (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)
>
> What my intension is to relay calls between Internal and External SIP 
> server via Opensips server.
>
> I use this method to achieve this:
>
> socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
>
> socket=udp:enp2s0:5060 # EXTERNAL_INTERFACE (DHCP)
>
> .
>
> .
>
> # From Internal to External
>
> # Testing one number only first 634 to 605
>
> if ($rU=~"^605") {
>
>                sethostport("EXTERNAL_IP:5060");
>
> $socket_out = "udp:EXTERNAL_IP:5060";
>
> rtpproxy_engage("ier");
>
> route(relay);
>
> exit;
>
> }
>
> # From External to internal
>
> # Testing one number only first 605 to 634
>
> if ($rU=~"^634"){
>
>                sethostport("192.168.1.2:5060");
>
> $socket_out = "udp:192.168.1.2:5060";
>
> rtpproxy_engage("eir");
>
> route(relay);
>
> exit;
>
> }
>
> I have no problem on call from external to internal because I know the 
> IP address of internal opensips server, the problem is call from 
> internal to external.
>
> Is there better solutions than this?
>
> Regards
>
> *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Wednesday, 17 November, 2021 8:24 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users 
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP 
> address as variable
>
> If so, when you receive a request on the external IP, the 
> $socket_in(ip) should return the actual DHCP IP.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
> On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
>
>     Hi,
>
>     socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
>
>     socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME
>
>     My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I
>     just use tag to test something.
>
>     Regards
>
>     *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Sent:* Wednesday, 17 November, 2021 3:55 PM
>     *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>
>     <mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list
>     <users at lists.opensips.org> <mailto:users at lists.opensips.org>
>     *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
>     address as variable
>
>     Hi,
>
>     How do you define the listening socket in OpenSIPs cfg ? (the one
>     related to the DHCP interface)
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>       
>
>     OpenSIPS Founder and Developer
>
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>     OpenSIPS eBootcamp 2021
>
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>
>         Hi,
>
>         Is there a way to get the IP address of DHCP interface to use
>         in the script? I can get the call go through if I set both the
>         interface as static.
>
>         Regards
>
>         Get Outlook for Android <https://aka.ms/AAb9ysg>
>
>         ------------------------------------------------------------------------
>
>         *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>         <mailto:bogdan at opensips.org>
>         *Sent:* Tuesday, November 16, 2021, 6:45 PM
>         *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
>         *Subject:* Re: [OpenSIPS-Users] How to get all listening
>         socket IP address as variable
>
>
>         Hi,
>
>         via the socket_xx() vars you can get only the sockets relative
>         to/used by that call, you cannot iterate thru the listening
>         sockets.
>
>         Regards,
>
>
>         Bogdan-Andrei Iancu
>
>           
>
>         OpenSIPS Founder and Developer
>
>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>         OpenSIPS eBootcamp 2021
>
>            https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>         On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
>             Hi,
>
>             I have 2 listening interface for opensips 3.2. How do I
>             get both IP address to be used as variable in opensips
>             config file? I try to use socket_in/ socket_out but failed
>             to get the other interface IP address.
>
>             Thanks
>
>             Sent from Mail
>             <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
>
>
>
>
>             _______________________________________________
>
>             Users mailing list
>
>             Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>
>             http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>

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

From bogdan at opensips.org  Fri Nov 19 07:13:13 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 19 Nov 2021 09:13:13 +0200
Subject: [OpenSIPS-Users] Syntax in 3.2
In-Reply-To: <CAKrJzCyRAQEY-yLcEFfJtEHfrkWUQnxpKpPnrXF-gqmexqKmCA@mail.gmail.com>
References: <CAKrJzCyRAQEY-yLcEFfJtEHfrkWUQnxpKpPnrXF-gqmexqKmCA@mail.gmail.com>
Message-ID: <9bf7d7bf-6cee-2d25-c2b0-c1ad337bf3ee@opensips.org>

Hi Jehanzaib,

the "status" keyword was dropped for a long time [1], use $rs instead.

[1] https://www.opensips.org/Documentation/Migration-2-3-0-to-2-4-0#toc4

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/19/21 6:04 AM, Jehanzaib Younis wrote:
> Hi experts,
>
> I have just upgraded my old opensips to 3.2 version. Getting quite a 
> few syntax errors. Running out of time, so thought maybe someone can 
> quickly help out .
>
> The error comes at if(status=~"[12][0-9][0-9]")
> May be someone can write us the correct syntax for status code checking?
>
> Thank you in advance
>
> Regards,
> Jehanzaib
>
> _______________________________________________
> 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/20211119/0296a820/attachment.html>

From bogdan at opensips.org  Fri Nov 19 07:39:08 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 19 Nov 2021 09:39:08 +0200
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <BN0PR10MB5208EA4C8F78BD464B631516959B9@BN0PR10MB5208.namprd10.prod.outlook.com>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
 <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
 <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>
 <fa916322-8b1c-1c05-742f-a4aba3dd39ff@opensips.org>
 <BN0PR10MB5208EA4C8F78BD464B631516959B9@BN0PR10MB5208.namprd10.prod.outlook.com>
Message-ID: <6a15fab7-bab0-b93d-445d-50495033bd4d@opensips.org>

Hi Ben,

Fixes what I found on this matter, see [1]. Do you see any of these 
leftovers left in the current doc ?

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

Thanks and regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/18/21 4:04 PM, Ben Newlin wrote:
>
> While you are in the drouting module docs, there are multiple places 
> in there where the changes from flags to sort_alg were not documented, 
> especially for dr_carriers routing.
>
> Ben Newlin
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Liviu 
> Chircu <liviu at opensips.org>
> *Date: *Thursday, November 18, 2021 at 5:14 AM
> *To: *pkelly at gmail.com <pkelly at gmail.com>
> *Cc: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] Drouting /timerec documentation for 
> 3.2 vs 3.1
>
> On 18.11.2021 12:09, Pete Kelly wrote:
> > It looks like there are quite a few inconsistencies on the drouting
> > documentation page versus the docs here
> > 
> https://protect-us.mimecast.com/s/qxwMCPN5YqtYDkRgHzA2QW?domain=opensips.org 
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec> 
>
> > 
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec 
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec>> 
>
> > - so maybe just a link or reference to check_time_rec would work for
> > consistency?
>
> Most likely, any timerec-related info on that page is outdated.  Will
> double-check all the content when I get to this task.  I like the idea
> to link to check_time_rec(), as it will future-proof the drouting docs
> against changes to the core, common function.
>
> -- 
> Liviu Chircu
> www.twitter.com/liviuchircu <http://www.twitter.com/liviuchircu> | 
> www.opensips-solutions.com <http://www.opensips-solutions.com>
> OpenSIPS eBootcamp 2021: www.opensips.org/training 
> <http://www.opensips.org/training>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
> <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/20211119/1375b738/attachment.html>

From bogdan at opensips.org  Fri Nov 19 07:48:29 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 19 Nov 2021 09:48:29 +0200
Subject: [OpenSIPS-Users] Some questions regarding configuring msilo
In-Reply-To: <1963995.0S5aU1g85B@blacky>
References: <1963995.0S5aU1g85B@blacky>
Message-ID: <ac9c480f-27a6-6b1a-2b76-0635b1fcf3aa@opensips.org>

Hi Robert,

I guess you are talking about his 
https://opensips.org/html/docs/modules/3.2.x/msilo.html#idp5708384 ? 
Which looks like it was not updated since ages.....it is not even 3.2 
compatible actually.

The "# if the downstream UA does not support MESSAGE requests" block is 
outside the "if(!lookup("location")) ", so it is done when the lookup() 
succeeded. And to be honest I do not see that "t_on_if()" anywhere .....

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/11/21 10:34 PM, Robert Dyck wrote:
>
> The module documentation for msilo gives us an example of 
> configuration to deploy the service.
>
> In a block staring with "if(!lookup("location"))" we see the following --
>
>
>       # if the downstream UA does not support MESSAGE requests
>        # go to failure_route[1]
>        t_on_if (!db_does_uri_exist("$ru","subscriber"))failure("1");
>        t_relay();
>        exit;
> We didn't actually establish that the lookup failed because Message is 
> unsupported. Lookup has only one failure return code -1. This does not 
> tell us if the lookup failure was due to an non-existant AOR, no UAs 
> registered or method not supported.
>
>
> In the statement "t_on_if 
> (db_does_uri_exist("$ru","subscriber"))failure("1"); " t_on_if is not 
> documented. Does it mean we should immediately go to the failure route 
> if the AOR does not exist.
>
>
> If the AOR does not exist why would we do ---
>
>    if (m_store("$ou"))
>    {
>        log("MSILO: offline message stored\n");
>        t_reply("202", "Accepted");
>    }else{
>        log("MSILO: offline message NOT stored\n");
>        t_reply("503", "Service Unavailable");
>    };
>
>
> Some clarification would be appreciated.
>
> Rob
>
>
> _______________________________________________
> 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/20211119/17d70eb2/attachment.html>

From jehanzaib.kiani at gmail.com  Fri Nov 19 08:53:04 2021
From: jehanzaib.kiani at gmail.com (Jehanzaib Younis)
Date: Fri, 19 Nov 2021 21:53:04 +1300
Subject: [OpenSIPS-Users] Syntax in 3.2
In-Reply-To: <9bf7d7bf-6cee-2d25-c2b0-c1ad337bf3ee@opensips.org>
References: <CAKrJzCyRAQEY-yLcEFfJtEHfrkWUQnxpKpPnrXF-gqmexqKmCA@mail.gmail.com>
 <9bf7d7bf-6cee-2d25-c2b0-c1ad337bf3ee@opensips.org>
Message-ID: <CAKrJzCyjSiOKZqNifGD2rtpgW1uu7XUXqCC75s_xkGJPkBYwdw@mail.gmail.com>

Thank you so much Bogdan,


Regards,
Jehanzaib


On Fri, Nov 19, 2021 at 8:13 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Jehanzaib,
>
> the "status" keyword was dropped for a long time [1], use $rs instead.
>
> [1] https://www.opensips.org/Documentation/Migration-2-3-0-to-2-4-0#toc4
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/19/21 6:04 AM, Jehanzaib Younis wrote:
>
> Hi experts,
>
> I have just upgraded my old opensips to 3.2 version. Getting quite a few
> syntax errors. Running out of time, so thought maybe someone can quickly
> help out .
>
> The error comes at if(status=~"[12][0-9][0-9]")
> May be someone can write us the correct syntax for status code checking?
>
> Thank you in advance
>
> Regards,
> Jehanzaib
>
> _______________________________________________
> 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/20211119/839fc551/attachment-0001.html>

From m.putra77 at outlook.com  Fri Nov 19 09:31:42 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Fri, 19 Nov 2021 09:31:42 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>
Message-ID: <SI2PR03MB5561EF0D03DA171799A02C63FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

Thank you so much for the info.

Best regards,
Putra

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Friday, 19 November, 2021 3:11 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

I see, you start listening on an interface (enp2s0), which translates into the DHCP IP, but you can not use the socket/listener to do a force send socket ....as there is no way to reference it. Unfortunately something like that is not possible right now, but I see it as a valuable addition.

For the moment, what you can do is to use some pre-processing  (see [1]) in order to fill in your CFG the actual IP - and do an IP detection from the opensips init.d / startup script.


[1] https://www.opensips.org/Documentation/Templating-Config-Files-3-0

Best regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/18/21 4:50 AM, Muhamad Putra Abdullah wrote:
Hi,

Ok. I'm totally in learning process.
Let me explain my test deployment. I have 2 separate network that connected via opensips server.

Internal SIP Server                                       Opensips Server (2 NIC)                                             External SIP Server
(User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |   (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)

What my intension is to relay calls between Internal and External SIP server via Opensips server.
I use this method to achieve this:

               socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)
               .
               .
               # From Internal to External
               # Testing one number only first 634 to 605
              if ($rU=~"^605") {
                              sethostport("EXTERNAL_IP:5060");
                               $socket_out = "udp:EXTERNAL_IP:5060";
                               rtpproxy_engage("ier");
                               route(relay);
                               exit;
               }

               # From External to internal
               # Testing one number only first 605 to 634
if ($rU=~"^634"){
                              sethostport("192.168.1.2:5060");
                               $socket_out = "udp:192.168.1.2:5060";
                               rtpproxy_engage("eir");
                               route(relay);
                               exit;
               }

I have no problem on call from external to internal because I know the IP address of internal opensips server, the problem is call from internal to external.
Is there better solutions than this?

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 8:24 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

If so, when you receive a request on the external IP, the $socket_in(ip) should return the actual DHCP IP.

Regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
Hi,

socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME

My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use tag to test something.

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 3:55 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one related to the DHCP interface)

Regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows






_______________________________________________

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/20211119/8ca88b46/attachment-0001.html>

From devang.dhandhalya at ecosmob.com  Fri Nov 19 09:46:45 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Fri, 19 Nov 2021 15:16:45 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
Message-ID: <CAP0uOe8tW+16jCHy4473KouEQXiDb91drHsj0nh6jrrnetZ7yw@mail.gmail.com>

Hello Vlad

Thanks for your response . Authentication service works .

Regards ,
Devang Dhandhalya


On Wed, Nov 17, 2021 at 8:57 PM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> hello all
>
>
> Above E.164 Error still getting .Right now I'm getting the below error .
> Can anyone tell me why I am getting this error ? as far as i know this
> error for x5u parameter in stir_shaken_auth function , this issue coming
> for certificate path or certificate file format .
>
>
> I check the certificate file with .der and .cer format also .
>
> Here is the code snippet used .
>
> $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)", "$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");
>
>
> Below Error i am getting .
>
>
> ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>
> ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>
> STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>
>
> Kindly let me know if there is something wrong that I could be doing.
>
> Many Thanks
> Devang Dhandhalya
>
>
> On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
> devang.dhandhalya at ecosmob.com> wrote:
>
>> Hi All
>>
>> I configured the e164 strict mode module parameter as 0 (disabled) . but
>> still i am getting errors related to its e164 format .While if orig/dest
>> number is not in e164 format then also opensips have to accept it but it is
>> not accepting .  I have a user like extension123 for this function I have
>> to perform authentication service . if i have a user extension123 is it
>> possible to perform authenticate service for this kind of user ?
>>
>> I think this is a bug for the e164 strict mode  module parameter . I am
>> getting the below error .
>>
>> opensips version : 3.2.2
>>
>> ERROR :
>>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164
>> format: extension123
>>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
>> (extension123)
>>
>>
>> loadmodule "stir_shaken.so"
>> modparam("stir_shaken", "auth_date_freshness", 300)
>> modparam("stir_shaken", "verify_date_freshness", 300)
>> modparam("stir_shaken", "require_date_hdr", 0)
>> modparam("stir_shaken", "e164_strict_mode", 0)
>>
>> $var(orig) = $fU;
>> $var(dest) = $tU
>>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
>> "$var(pkey)","http://localhost/certificate.pem
>> ","$var(orig)","$var(dest)");
>>
>> Please suggest a solution to this .
>>
>> Many Thanks
>> Devang
>>
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211119/6557bf92/attachment.html>

From bogdan at opensips.org  Fri Nov 19 10:35:28 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 19 Nov 2021 12:35:28 +0200
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB5561EF0D03DA171799A02C63FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>
 <SI2PR03MB5561EF0D03DA171799A02C63FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <c640a35a-8abe-e03e-5f64-d28a5d662bd6@opensips.org>

Hi Putra,

Actually a recent fix should allow in the latest 3.2 version to use the 
socket's tag when setting the outbound socket, like :

socket=udp:enp1s0:5060 TAG internal   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060 TAG external   # EXTERNAL_INTERFACE (DHCP)
...
....
$socket_out = "external";

But use the latest 3.2, git or nightly builds.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/19/21 11:31 AM, Muhamad Putra Abdullah wrote:
>
> Hi,
>
> Thank you so much for the info.
>
> Best regards,
>
> Putra
>
> *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Sent:* Friday, 19 November, 2021 3:11 PM
> *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users 
> mailling list <users at lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP 
> address as variable
>
> Hi,
>
> I see, you start listening on an interface (enp2s0), which translates 
> into the DHCP IP, but you can not use the socket/listener to do a 
> force send socket ....as there is no way to reference it. 
> Unfortunately something like that is not possible right now, but I see 
> it as a valuable addition.
>
> For the moment, what you can do is to use some pre-processing  (see 
> [1]) in order to fill in your CFG the actual IP - and do an IP 
> detection from the opensips init.d / startup script.
>
>
> [1] https://www.opensips.org/Documentation/Templating-Config-Files-3-0 
> <https://www.opensips.org/Documentation/Templating-Config-Files-3-0>
>
> Best regards,
>
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
> On 11/18/21 4:50 AM, Muhamad Putra Abdullah wrote:
>
>     Hi,
>
>     Ok. I’m totally in learning process.
>
>     Let me explain my test deployment. I have 2 separate network that
>     connected via opensips server.
>
>     Internal SIP Server                                       Opensips
>     Server (2 NIC)                         External SIP Server
>
>     (User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |
>     (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)
>
>     What my intension is to relay calls between Internal and External
>     SIP server via Opensips server.
>
>     I use this method to achieve this:
>
>     socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
>
>     socket=udp:enp2s0:5060 # EXTERNAL_INTERFACE (DHCP)
>
>     .
>
>     .
>
>     # From Internal to External
>
>     # Testing one number only first 634 to 605
>
>     if ($rU=~"^605") {
>
>                    sethostport("EXTERNAL_IP:5060");
>
>     $socket_out = "udp:EXTERNAL_IP:5060";
>
>     rtpproxy_engage("ier");
>
>     route(relay);
>
>     exit;
>
>     }
>
>     # From External to internal
>
>     # Testing one number only first 605 to 634
>
>     if ($rU=~"^634"){
>
>                    sethostport("192.168.1.2:5060");
>
>     $socket_out = "udp:192.168.1.2:5060";
>
>     rtpproxy_engage("eir");
>
>     route(relay);
>
>     exit;
>
>     }
>
>     I have no problem on call from external to internal because I know
>     the IP address of internal opensips server, the problem is call
>     from internal to external.
>
>     Is there better solutions than this?
>
>     Regards
>
>     *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
>     <mailto:bogdan at opensips.org>
>     *Sent:* Wednesday, 17 November, 2021 8:24 PM
>     *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>
>     <mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list
>     <users at lists.opensips.org> <mailto:users at lists.opensips.org>
>     *Subject:* Re: [OpenSIPS-Users] How to get all listening socket IP
>     address as variable
>
>     If so, when you receive a request on the external IP, the
>     $socket_in(ip) should return the actual DHCP IP.
>
>     Regards,
>
>
>     Bogdan-Andrei Iancu
>
>       
>
>     OpenSIPS Founder and Developer
>
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>     OpenSIPS eBootcamp 2021
>
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
>
>         Hi,
>
>         socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
>
>         socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME
>
>         My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I
>         just use tag to test something.
>
>         Regards
>
>         *From:*Bogdan-Andrei Iancu <bogdan at opensips.org>
>         <mailto:bogdan at opensips.org>
>         *Sent:* Wednesday, 17 November, 2021 3:55 PM
>         *To:* Muhamad Putra Abdullah <m.putra77 at outlook.com>
>         <mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list
>         <users at lists.opensips.org> <mailto:users at lists.opensips.org>
>         *Subject:* Re: [OpenSIPS-Users] How to get all listening
>         socket IP address as variable
>
>         Hi,
>
>         How do you define the listening socket in OpenSIPs cfg ? (the
>         one related to the DHCP interface)
>
>         Regards,
>
>
>
>         Bogdan-Andrei Iancu
>
>           
>
>         OpenSIPS Founder and Developer
>
>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>         OpenSIPS eBootcamp 2021
>
>            https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>         On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
>
>             Hi,
>
>             Is there a way to get the IP address of DHCP interface to
>             use in the script? I can get the call go through if I set
>             both the interface as static.
>
>             Regards
>
>             Get Outlook for Android <https://aka.ms/AAb9ysg>
>
>             ------------------------------------------------------------------------
>
>             *From:* Bogdan-Andrei Iancu <bogdan at opensips.org>
>             <mailto:bogdan at opensips.org>
>             *Sent:* Tuesday, November 16, 2021, 6:45 PM
>             *To:* OpenSIPS users mailling list; Muhamad Putra Abdullah
>             *Subject:* Re: [OpenSIPS-Users] How to get all listening
>             socket IP address as variable
>
>
>             Hi,
>
>             via the socket_xx() vars you can get only the sockets
>             relative to/used by that call, you cannot iterate thru the
>             listening sockets.
>
>             Regards,
>
>
>
>             Bogdan-Andrei Iancu
>
>               
>
>             OpenSIPS Founder and Developer
>
>                https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>
>             OpenSIPS eBootcamp 2021
>
>                https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>             On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
>
>                 Hi,
>
>                 I have 2 listening interface for opensips 3.2. How do
>                 I get both IP address to be used as variable in
>                 opensips config file? I try to use socket_in/
>                 socket_out but failed to get the other interface IP
>                 address.
>
>                 Thanks
>
>                 Sent from Mail
>                 <https://go.microsoft.com/fwlink/?LinkId=550986> for
>                 Windows
>
>
>
>
>
>                 _______________________________________________
>
>                 Users mailing list
>
>                 Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>
>                 http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>

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

From m.putra77 at outlook.com  Fri Nov 19 13:49:54 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Fri, 19 Nov 2021 13:49:54 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <c640a35a-8abe-e03e-5f64-d28a5d662bd6@opensips.org>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>
 <SI2PR03MB5561EF0D03DA171799A02C63FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c640a35a-8abe-e03e-5f64-d28a5d662bd6@opensips.org>
Message-ID: <SI2PR03MB55617EE9182FC8C5B0C4A8A7FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

Nice to hear that. I'll try it out later. Thanks

Regards
Putra

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Sent: Friday, 19 November, 2021 6:35 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi Putra,

Actually a recent fix should allow in the latest 3.2 version to use the socket's tag when setting the outbound socket, like :

socket=udp:enp1s0:5060 TAG internal   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060 TAG external   # EXTERNAL_INTERFACE (DHCP)
...
....
$socket_out = "external";

But use the latest 3.2, git or nightly builds.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/19/21 11:31 AM, Muhamad Putra Abdullah wrote:
Hi,

Thank you so much for the info.

Best regards,
Putra

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Friday, 19 November, 2021 3:11 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

I see, you start listening on an interface (enp2s0), which translates into the DHCP IP, but you can not use the socket/listener to do a force send socket ....as there is no way to reference it. Unfortunately something like that is not possible right now, but I see it as a valuable addition.

For the moment, what you can do is to use some pre-processing  (see [1]) in order to fill in your CFG the actual IP - and do an IP detection from the opensips init.d / startup script.


[1] https://www.opensips.org/Documentation/Templating-Config-Files-3-0

Best regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/18/21 4:50 AM, Muhamad Putra Abdullah wrote:
Hi,

Ok. I'm totally in learning process.
Let me explain my test deployment. I have 2 separate network that connected via opensips server.

Internal SIP Server                                       Opensips Server (2 NIC)                                             External SIP Server
(User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |   (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)

What my intension is to relay calls between Internal and External SIP server via Opensips server.
I use this method to achieve this:

               socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)
               .
               .
               # From Internal to External
               # Testing one number only first 634 to 605
              if ($rU=~"^605") {
                              sethostport("EXTERNAL_IP:5060");
                               $socket_out = "udp:EXTERNAL_IP:5060";
                               rtpproxy_engage("ier");
                               route(relay);
                               exit;
               }

               # From External to internal
               # Testing one number only first 605 to 634
if ($rU=~"^634"){
                              sethostport("192.168.1.2:5060");
                               $socket_out = "udp:192.168.1.2:5060";
                               rtpproxy_engage("eir");
                               route(relay);
                               exit;
               }

I have no problem on call from external to internal because I know the IP address of internal opensips server, the problem is call from internal to external.
Is there better solutions than this?

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 8:24 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

If so, when you receive a request on the external IP, the $socket_in(ip) should return the actual DHCP IP.

Regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
Hi,

socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME

My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use tag to test something.

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 3:55 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one related to the DHCP interface)

Regards,





Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,





Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows







_______________________________________________

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/20211119/bd55a191/attachment-0001.html>

From Ben.Newlin at genesys.com  Fri Nov 19 14:26:37 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Fri, 19 Nov 2021 14:26:37 +0000
Subject: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
In-Reply-To: <6a15fab7-bab0-b93d-445d-50495033bd4d@opensips.org>
References: <CAEWH9M8=rT0CZEwdaRBjrs3BG-U05yd_4sappg_vB34T+S94Jg@mail.gmail.com>
 <d869d86f-1f1f-5c1f-90a8-eaa128989b0c@opensips.org>
 <CAEWH9M9ZeK5b_+46vFt5LyWUt-N3Ge+MiiNAUobQVSs=LJx_kQ@mail.gmail.com>
 <fa916322-8b1c-1c05-742f-a4aba3dd39ff@opensips.org>
 <BN0PR10MB5208EA4C8F78BD464B631516959B9@BN0PR10MB5208.namprd10.prod.outlook.com>
 <6a15fab7-bab0-b93d-445d-50495033bd4d@opensips.org>
Message-ID: <BN0PR10MB5208DA42532945862C374ABD959C9@BN0PR10MB5208.namprd10.prod.outlook.com>

No, I think that was the only place. Thank you!

Ben Newlin

From: Bogdan-Andrei Iancu <bogdan at opensips.org>
Date: Friday, November 19, 2021 at 2:39 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>, Ben Newlin <Ben.Newlin at genesys.com>, pkelly at gmail.com <pkelly at gmail.com>
Subject: Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
Hi Ben,

Fixes what I found on this matter, see [1]. Do you see any of these leftovers left in the current doc ?

[1] https://github.com/OpenSIPS/opensips/commit/394ba080486f97f44afaf794fa82aba1f630b186<https://github.com/OpenSIPS/opensips/commit/394ba080486f97f44afaf794fa82aba1f630b186>

Thanks and regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com<https://www.opensips-solutions.com>

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/<https://opensips.org/training/OpenSIPS_eBootcamp_2021>
On 11/18/21 4:04 PM, Ben Newlin wrote:
While you are in the drouting module docs, there are multiple places in there where the changes from flags to sort_alg were not documented, especially for dr_carriers routing.

Ben Newlin

From: Users <users-bounces at lists.opensips.org><mailto:users-bounces at lists.opensips.org> on behalf of Liviu Chircu <liviu at opensips.org><mailto:liviu at opensips.org>
Date: Thursday, November 18, 2021 at 5:14 AM
To: pkelly at gmail.com<mailto:pkelly at gmail.com> <pkelly at gmail.com><mailto:pkelly at gmail.com>
Cc: OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1
On 18.11.2021 12:09, Pete Kelly wrote:
> It looks like there are quite a few inconsistencies on the drouting
> documentation page versus the docs here
> https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec<https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec>
> <https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec<https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec>>
> - so maybe just a link or reference to check_time_rec would work for
> consistency?

Most likely, any timerec-related info on that page is outdated.  Will
double-check all the content when I get to this task.  I like the idea
to link to check_time_rec(), as it will future-proof the drouting docs
against changes to the core, common function.

--
Liviu Chircu
www.twitter.com/liviuchircu<http://www.twitter.com/liviuchircu> | www.opensips-solutions.com<http://www.opensips-solutions.com>
OpenSIPS eBootcamp 2021: www.opensips.org/training<http://www.opensips.org/training>


_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users<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<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>

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

From rob.dyck at telus.net  Fri Nov 19 16:13:23 2021
From: rob.dyck at telus.net (Robert Dyck)
Date: Fri, 19 Nov 2021 08:13:23 -0800
Subject: [OpenSIPS-Users] Some questions regarding configuring msilo
In-Reply-To: <ac9c480f-27a6-6b1a-2b76-0635b1fcf3aa@opensips.org>
References: <1963995.0S5aU1g85B@blacky>
 <ac9c480f-27a6-6b1a-2b76-0635b1fcf3aa@opensips.org>
Message-ID: <3016088.CbtlEUcBR6@blacky>

How very odd. I revisited the documentation and the code snippet I was 
referencing indeed does not exist. The snippet shown in my previous email was 
a copy and paste.
Thank you for investigating.
Rob

On Thursday, November 18, 2021 11:48:29 P.M. PST Bogdan-Andrei Iancu wrote:
> Hi Robert,
> 
> I guess you are talking about his
> https://opensips.org/html/docs/modules/3.2.x/msilo.html#idp5708384 ?
> Which looks like it was not updated since ages.....it is not even 3.2
> compatible actually.
> 
> The "# if the downstream UA does not support MESSAGE requests" block is
> outside the "if(!lookup("location")) ", so it is done when the lookup()
> succeeded. And to be honest I do not see that "t_on_if()" anywhere .....
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>    https://opensips.org/training/OpenSIPS_eBootcamp_2021/
> 
> On 11/11/21 10:34 PM, Robert Dyck wrote:
> > The module documentation for msilo gives us an example of
> > configuration to deploy the service.
> > 
> > In a block staring with "if(!lookup("location"))" we see the following --
> > 
> > 
> >       # if the downstream UA does not support MESSAGE requests
> >        # go to failure_route[1]
> >        t_on_if (!db_does_uri_exist("$ru","subscriber"))failure("1");
> >        t_relay();
> >        exit;
> > We didn't actually establish that the lookup failed because Message is
> > unsupported. Lookup has only one failure return code -1. This does not
> > tell us if the lookup failure was due to an non-existant AOR, no UAs
> > registered or method not supported.
> > 
> > 
> > In the statement "t_on_if
> > (db_does_uri_exist("$ru","subscriber"))failure("1"); " t_on_if is not
> > documented. Does it mean we should immediately go to the failure route
> > if the AOR does not exist.
> > 
> > 
> > If the AOR does not exist why would we do ---
> > 
> >    if (m_store("$ou"))
> >    {
> >        log("MSILO: offline message stored\n");
> >        t_reply("202", "Accepted");
> >    }else{
> >        log("MSILO: offline message NOT stored\n");
> >        t_reply("503", "Service Unavailable");
> >    };
> > 
> > 
> > Some clarification would be appreciated.
> > 
> > Rob
> > 
> > 
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users






From devang.dhandhalya at ecosmob.com  Mon Nov 22 12:41:49 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Mon, 22 Nov 2021 18:11:49 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <CAP0uOe8tW+16jCHy4473KouEQXiDb91drHsj0nh6jrrnetZ7yw@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
 <CAP0uOe8tW+16jCHy4473KouEQXiDb91drHsj0nh6jrrnetZ7yw@mail.gmail.com>
Message-ID: <CAP0uOe97m+PFhhRJRhTH=YuB8=quXVwG_5jexxA60+sBrbTOAA@mail.gmail.com>

Hello Vlad

Authentication service works fine. Now I am getting an error in the
stir_shaken_verify function , after fetching a certificate, I am getting
below error . I generated private keys and X509 certificates using
prime256v1" EC.
After fetching the certificate I am getting var(found) = -2 can you please
tell me about this too .

OpenSIPS Logs :





*var(found) = [-2]INFO:stir_shaken:validate_certificate: The certificate is
missing the TnAuthList extensionINFO:stir_shaken:w_stir_verify: Invalid
certificatereturn code : [-8] stir_shaken_verify() failed:437, Unsupported
Credential*
below opensips script snippet :

$var(found) = cache_fetch("local",$identity(x5u),$var(cert));


if (!$var(found) || !stir_shaken_check_cert("$var(cert)")) {
                        rest_get("$identity(x5u)",$var(cert),$var(ctype),
$var(http_rc));
                        if ($rc<0 ) {
                                send_reply(436, "Bad Identity Info");
                                exit;
                        }
cache_store("local", $identity(x5u),"$var(cert)");
                }


$var(rc_verify)= stir_shaken_verify($var(cert),
$var(err_sip_code),$var(err_sip_reason),"$var(orig)","$var(dest)");
                if ($var(rc_verify) < 0) {

                        send_reply(
$var(err_sip_code),$var(err_sip_reason));
                        exit;
                }

Kindly inform me why I am getting this error . Please suggest a solution to
this .


Regards
Devang Dhandhalya


On Fri, Nov 19, 2021 at 3:16 PM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hello Vlad
>
> Thanks for your response . Authentication service works .
>
> Regards ,
> Devang Dhandhalya
>
>
> On Wed, Nov 17, 2021 at 8:57 PM Devang Dhandhalya <
> devang.dhandhalya at ecosmob.com> wrote:
>
>> hello all
>>
>>
>> Above E.164 Error still getting .Right now I'm getting the below error .
>> Can anyone tell me why I am getting this error ? as far as i know this
>> error for x5u parameter in stir_shaken_auth function , this issue coming
>> for certificate path or certificate file format .
>>
>>
>> I check the certificate file with .der and .cer format also .
>>
>> Here is the code snippet used .
>>
>> $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)", "$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");
>>
>>
>> Below Error i am getting .
>>
>>
>> ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>>
>> ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>>
>> STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>>
>>
>> Kindly let me know if there is something wrong that I could be doing.
>>
>> Many Thanks
>> Devang Dhandhalya
>>
>>
>> On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
>> devang.dhandhalya at ecosmob.com> wrote:
>>
>>> Hi All
>>>
>>> I configured the e164 strict mode module parameter as 0 (disabled) . but
>>> still i am getting errors related to its e164 format .While if orig/dest
>>> number is not in e164 format then also opensips have to accept it but it is
>>> not accepting .  I have a user like extension123 for this function I have
>>> to perform authentication service . if i have a user extension123 is it
>>> possible to perform authenticate service for this kind of user ?
>>>
>>> I think this is a bug for the e164 strict mode  module parameter . I am
>>> getting the below error .
>>>
>>> opensips version : 3.2.2
>>>
>>> ERROR :
>>>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164
>>> format: extension123
>>>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
>>> (extension123)
>>>
>>>
>>> loadmodule "stir_shaken.so"
>>> modparam("stir_shaken", "auth_date_freshness", 300)
>>> modparam("stir_shaken", "verify_date_freshness", 300)
>>> modparam("stir_shaken", "require_date_hdr", 0)
>>> modparam("stir_shaken", "e164_strict_mode", 0)
>>>
>>> $var(orig) = $fU;
>>> $var(dest) = $tU
>>>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
>>> "$var(pkey)","http://localhost/certificate.pem
>>> ","$var(orig)","$var(dest)");
>>>
>>> Please suggest a solution to this .
>>>
>>> Many Thanks
>>> Devang
>>>
>>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211122/268a36e8/attachment.html>

From devang.dhandhalya at ecosmob.com  Mon Nov 22 12:57:39 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Mon, 22 Nov 2021 18:27:39 +0530
Subject: [OpenSIPS-Users] TLS Handshake fail issue
Message-ID: <CAP0uOe97Ygva2+u2VUQgYWXv0E9_ZXf0uQKfHBc+Qs3D5R85Fw@mail.gmail.com>

Hello vlad

Thanks for your response ,I used this command to check connection :openssl
s_client -showcerts -debug -connect 192.168.0.105:5071 -bugs .
Please let me know if there are any other commands to  check .

CONNECTED(00000005)
write to 0x561a52aa46b0 [0x561a52ab4eb0] (517 bytes => 517 (0x205))
140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 517 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

In this TLS  connection i am getting one error :
140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112

Can you please give some suggestions on this .

OpenSIPS starts successfully without errors and the following command shows
listening on the correct port:
netstat -tapen | grep 5071
tcp        0      0 192.168.0.105:5071      0.0.0.0:*               LISTEN
     0          87130      9179/opensips

I made some changes in the tls configuration . other than this same as
before .

socket=udp:192.168.0.105:5060 as devang.com:5060
socket=tcp:192.168.0.105:5060 as devang.com:5060
socket=tls:192.168.0.105:5071 as devang.com:5071

modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5071")


At the time of calling, I get this error .

ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
192.168.0.105:44853 failed
ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
err=Success(0)
ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
routines:ssl3_read_bytes:sslv3 alert handshake failure
ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!

I tried setting all the tls version methods as 'tls_method' in opensips
config but the same error occurred.  Please advise how to resolve this
SSL23 handshake failure.

Regards
Devang Dhandhalya

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211122/2e662bfd/attachment-0001.html>

From jehanzaib.kiani at gmail.com  Mon Nov 22 21:09:44 2021
From: jehanzaib.kiani at gmail.com (Jehanzaib Younis)
Date: Tue, 23 Nov 2021 10:09:44 +1300
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <CAP0uOe97Ygva2+u2VUQgYWXv0E9_ZXf0uQKfHBc+Qs3D5R85Fw@mail.gmail.com>
References: <CAP0uOe97Ygva2+u2VUQgYWXv0E9_ZXf0uQKfHBc+Qs3D5R85Fw@mail.gmail.com>
Message-ID: <CAKrJzCw4q_PqwW_rgGy0F0MYk_=haeP36UNTDfLoEHCP2NLtow@mail.gmail.com>

Looks like the domain name you are using is not matching with the
certificate name.
I have also noticed you are using tlsv1, better to generate the certificate
with tlsv1.2 or tlsv1.3


Regards,
Jehanzaib


On Tue, Nov 23, 2021 at 1:58 AM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hello vlad
>
> Thanks for your response ,I used this command to check connection :openssl
> s_client -showcerts -debug -connect 192.168.0.105:5071 -bugs .
> Please let me know if there are any other commands to  check .
>
> CONNECTED(00000005)
> write to 0x561a52aa46b0 [0x561a52ab4eb0] (517 bytes => 517 (0x205))
> 140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
> ---
> no peer certificate available
> ---
> No client certificate CA names sent
> ---
> SSL handshake has read 7 bytes and written 517 bytes
> Verification: OK
> ---
> New, (NONE), Cipher is (NONE)
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> No ALPN negotiated
> Early data was not sent
> Verify return code: 0 (ok)
> ---
>
> In this TLS  connection i am getting one error :
> 140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
>
> Can you please give some suggestions on this .
>
> OpenSIPS starts successfully without errors and the following command
> shows listening on the correct port:
> netstat -tapen | grep 5071
> tcp        0      0 192.168.0.105:5071      0.0.0.0:*
> LISTEN      0          87130      9179/opensips
>
> I made some changes in the tls configuration . other than this same as
> before .
>
> socket=udp:192.168.0.105:5060 as devang.com:5060
> socket=tcp:192.168.0.105:5060 as devang.com:5060
> socket=tls:192.168.0.105:5071 as devang.com:5071
>
> modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5071")
>
>
> At the time of calling, I get this error .
>
> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
> 192.168.0.105:44853 failed
> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
> err=Success(0)
> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
> routines:ssl3_read_bytes:sslv3 alert handshake failure
> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
> I tried setting all the tls version methods as 'tls_method' in opensips
> config but the same error occurred.  Please advise how to resolve this
> SSL23 handshake failure.
>
> Regards
> Devang Dhandhalya
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
> _______________________________________________
> 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/20211123/2c0e53c5/attachment.html>

From m.putra77 at outlook.com  Tue Nov 23 05:53:01 2021
From: m.putra77 at outlook.com (Muhamad Putra Abdullah)
Date: Tue, 23 Nov 2021 05:53:01 +0000
Subject: [OpenSIPS-Users] How to get all listening socket IP address as
 variable
In-Reply-To: <SI2PR03MB55617EE9182FC8C5B0C4A8A7FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
References: <SI2PR03MB55617D43EAB6F53AC75ACAF3FD989@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <66bd544e-b624-e630-dc15-ffbaa3afdc25@opensips.org>
 <SI2PR03MB556139C218B9E2A6B736870BFD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c5e0500b-4e28-383f-190c-294c61698ea6@opensips.org>
 <SI2PR03MB55614113946B55C832F247A2FD9A9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <24c12b5a-f1dd-96a4-bd83-8a8e5cbe6a5a@opensips.org>
 <SI2PR03MB556159D004A15DC829E7D2EBFD9B9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <4cb85511-eca2-ff34-9200-269f85c47f54@opensips.org>
 <SI2PR03MB5561EF0D03DA171799A02C63FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
 <c640a35a-8abe-e03e-5f64-d28a5d662bd6@opensips.org>
 <SI2PR03MB55617EE9182FC8C5B0C4A8A7FD9C9@SI2PR03MB5561.apcprd03.prod.outlook.com>
Message-ID: <SI2PR03MB556128C3AF5DCF83D37974ECFD609@SI2PR03MB5561.apcprd03.prod.outlook.com>

Hi,

This is my update. Using nightly revision: git : 79eb24e38, I can use "tag" (small cap) to refer to NICs IP address. Upper case TAG not working like in documentation.

socket=udp:enp2s0:5060 tag EXTERNAL_IP # CUSTOMIZE ME

I can use the tag reference in $socket_out(). Just small issue, I cannot use the reference in xlog to output the value.

In the end I used template style solution using python to scan NICs IP address and generate config file.
Thank for the help and guide.

Regards
Putra


From: Users <users-bounces at lists.opensips.org> On Behalf Of Muhamad Putra Abdullah
Sent: Friday, 19 November, 2021 9:50 PM
To: Bogdan-Andrei Iancu <bogdan at opensips.org>; OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

Nice to hear that. I'll try it out later. Thanks

Regards
Putra

From: Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>>
Sent: Friday, 19 November, 2021 6:35 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com<mailto:m.putra77 at outlook.com>>; OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi Putra,

Actually a recent fix should allow in the latest 3.2 version to use the socket's tag when setting the outbound socket, like :

socket=udp:enp1s0:5060 TAG internal   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060 TAG external   # EXTERNAL_INTERFACE (DHCP)
...
....
$socket_out = "external";

But use the latest 3.2, git or nightly builds.

Regards,

Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/19/21 11:31 AM, Muhamad Putra Abdullah wrote:
Hi,

Thank you so much for the info.

Best regards,
Putra

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Friday, 19 November, 2021 3:11 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

I see, you start listening on an interface (enp2s0), which translates into the DHCP IP, but you can not use the socket/listener to do a force send socket ....as there is no way to reference it. Unfortunately something like that is not possible right now, but I see it as a valuable addition.

For the moment, what you can do is to use some pre-processing  (see [1]) in order to fill in your CFG the actual IP - and do an IP detection from the opensips init.d / startup script.


[1] https://www.opensips.org/Documentation/Templating-Config-Files-3-0

Best regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/18/21 4:50 AM, Muhamad Putra Abdullah wrote:
Hi,

Ok. I'm totally in learning process.
Let me explain my test deployment. I have 2 separate network that connected via opensips server.

Internal SIP Server                                       Opensips Server (2 NIC)                                             External SIP Server
(User 634) 192.168.1.1  - - - - - - - -  192.168.1.2    |   (EXTERNAL_IP) DHCP IP - - - - - - - - 172.16.16.1 (User 605)

What my intension is to relay calls between Internal and External SIP server via Opensips server.
I use this method to achieve this:

               socket=udp:enp1s0:5060   # INTERNAL_INTERFACE (192.168.1.2)
socket=udp:enp2s0:5060   # EXTERNAL_INTERFACE (DHCP)
               .
               .
               # From Internal to External
               # Testing one number only first 634 to 605
              if ($rU=~"^605") {
                              sethostport("EXTERNAL_IP:5060");
                               $socket_out = "udp:EXTERNAL_IP:5060";
                               rtpproxy_engage("ier");
                               route(relay);
                               exit;
               }

               # From External to internal
               # Testing one number only first 605 to 634
if ($rU=~"^634"){
                              sethostport("192.168.1.2:5060");
                               $socket_out = "udp:192.168.1.2:5060";
                               rtpproxy_engage("eir");
                               route(relay);
                               exit;
               }

I have no problem on call from external to internal because I know the IP address of internal opensips server, the problem is call from internal to external.
Is there better solutions than this?

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 8:24 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

If so, when you receive a request on the external IP, the $socket_in(ip) should return the actual DHCP IP.

Regards,



Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 10:21 AM, Muhamad Putra Abdullah wrote:
Hi,

socket=udp:enp1s0:5060 tag INTERNAL_IP  # CUSTOMIZE ME
socket=udp:enp2s0:5060 tag EXTERNAL_IP  # CUSTOMIZE ME

My INTERNAL_IP is set to static and EXTERNAL_IP set to DHCP. I just use tag to test something.

Regards

From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Wednesday, 17 November, 2021 3:55 PM
To: Muhamad Putra Abdullah <m.putra77 at outlook.com><mailto:m.putra77 at outlook.com>; OpenSIPS users mailling list <users at lists.opensips.org><mailto:users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

How do you define the listening socket in OpenSIPs cfg ? (the one related to the DHCP interface)

Regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/17/21 2:19 AM, Muhamad Putra Abdullah wrote:
Hi,

Is there a way to get the IP address of DHCP interface to use in the script? I can get the call go through if I set both the interface as static.

Regards

Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________
From: Bogdan-Andrei Iancu <bogdan at opensips.org><mailto:bogdan at opensips.org>
Sent: Tuesday, November 16, 2021, 6:45 PM
To: OpenSIPS users mailling list; Muhamad Putra Abdullah
Subject: Re: [OpenSIPS-Users] How to get all listening socket IP address as variable

Hi,

via the socket_xx() vars you can get only the sockets relative to/used by that call, you cannot iterate thru the listening sockets.

Regards,




Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

OpenSIPS eBootcamp 2021

  https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/15/21 9:39 AM, Muhamad Putra Abdullah wrote:
Hi,

I have 2 listening interface for opensips 3.2. How do I get both IP address to be used as variable in opensips config file? I try to use socket_in/ socket_out but failed to get the other interface IP address.

Thanks

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows






_______________________________________________

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/20211123/312960f9/attachment-0001.html>

From vladp at opensips.org  Tue Nov 23 17:02:36 2021
From: vladp at opensips.org (Vlad Patrascu)
Date: Tue, 23 Nov 2021 19:02:36 +0200
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <CAP0uOe97m+PFhhRJRhTH=YuB8=quXVwG_5jexxA60+sBrbTOAA@mail.gmail.com>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
 <CAP0uOe8tW+16jCHy4473KouEQXiDb91drHsj0nh6jrrnetZ7yw@mail.gmail.com>
 <CAP0uOe97m+PFhhRJRhTH=YuB8=quXVwG_5jexxA60+sBrbTOAA@mail.gmail.com>
Message-ID: <835fff2d-f83a-4fe6-174e-2bdd574652bf@opensips.org>

Hello Devang,

The cache_fetch() functions returns -2 when the key is not found so it's 
normal when getting the certificate the first time.

STIR/SHAKEN requires that the certificates have the TnAuthList 
extension. You can check out some examples on how to generate such 
certificates in this document [1] at Appendix A or this script [2].

[1] 
https://cstga.ca/wp-content/uploads/2020/07/ATIS-1000080.v002_SHAKEN-Governance-Model.pdf

[2] 
https://github.com/OpenSIPIt/OpenSIPIt_00/blob/master/STIR_SHAKEN/Certgen/gencert.sh

Regards,

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

On 22.11.2021 14:41, Devang Dhandhalya wrote:
> Hello Vlad
>
> Authentication service works fine. Now I am getting an error in the 
> stir_shaken_verify function , after fetching a certificate, I am 
> getting below error . I generated private keys and X509 certificates 
> using prime256v1" EC.
> After fetching the certificate I am getting var(found) = -2 can you 
> please tell me about this too .
>
> OpenSIPS Logs :
> *
> *
> *var(found) = [-2]
> INFO:stir_shaken:validate_certificate: The certificate is missing the 
> TnAuthList extension
> INFO:stir_shaken:w_stir_verify: Invalid certificate
> return code : [-8] stir_shaken_verify() failed:437, Unsupported Credential
> *
> below opensips script snippet :
>
> $var(found) = cache_fetch("local",$identity(x5u),$var(cert));
>
>
> if (!$var(found) || !stir_shaken_check_cert("$var(cert)")) {
> rest_get("$identity(x5u)",$var(cert),$var(ctype), $var(http_rc));
>                         if ($rc<0 ) {
>                                 send_reply(436, "Bad Identity Info");
>                                 exit;
>                         }
> cache_store("local", $identity(x5u),"$var(cert)");
>                 }
>
>
> $var(rc_verify)= stir_shaken_verify($var(cert), 
> $var(err_sip_code),$var(err_sip_reason),"$var(orig)","$var(dest)");
>                 if ($var(rc_verify) < 0) {
>
>                         send_reply( 
> $var(err_sip_code),$var(err_sip_reason));
>                         exit;
>                 }
>
> Kindly inform me why I am getting this error . Please suggest a 
> solution to this .
>
>
> Regards
> Devang Dhandhalya
>
>
> On Fri, Nov 19, 2021 at 3:16 PM Devang Dhandhalya 
> <devang.dhandhalya at ecosmob.com <mailto:devang.dhandhalya at ecosmob.com>> 
> wrote:
>
>     Hello Vlad
>
>     Thanks for your response . Authentication service works .
>
>     Regards ,
>     Devang Dhandhalya
>
>     On Wed, Nov 17, 2021 at 8:57 PM Devang Dhandhalya
>     <devang.dhandhalya at ecosmob.com
>     <mailto:devang.dhandhalya at ecosmob.com>> wrote:
>
>         hello all
>
>
>         Above E.164 Error still getting .Right now I'm getting the below error .
>         Can anyone tell me why I am getting this error ? as far as i know this
>         error for x5u parameter in stir_shaken_auth function , this issue coming
>         for certificate path or certificate file format .
>
>
>         I check the certificate file with .der and .cer format also .
>
>         Here is the code snippet used .
>
>
>         $var(rc_auth)=stir_shaken_auth("A",
>         "GWID-123456","$var(cert)",
>         "$var(pkey)","http://localhost/certificate.pem
>         <http://localhost/certificate.pem>","$var(orig)","$var(dest)");
>
>         Below Error i am getting .
>
>
>         ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>
>         ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>
>         STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>
>         Kindly let me know if there is something wrong that I could be
>         doing. Many Thanks Devang Dhandhalya
>
>
>         On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya
>         <devang.dhandhalya at ecosmob.com
>         <mailto:devang.dhandhalya at ecosmob.com>> wrote:
>
>             Hi All
>
>             I configured the e164 strict mode module parameter as 0
>             (disabled) . but still i am getting errors related to its
>             e164 format .While if orig/dest number is not in e164
>             format then also opensips have to accept it but it is not
>             accepting .  I have a user like extension123 for this
>             function I have to perform authentication service . if i
>             have a user extension123 is it possible to perform
>             authenticate service for this kind of user ?
>
>             I think this is a bug for the e164 strict mode  module
>             parameter . I am getting the below error .
>
>             opensips version : 3.2.2
>
>             ERROR :
>              ERROR:stir_shaken:check_passport_phonenum: number is not
>             in E.164 format: extension123
>              ERROR:stir_shaken:w_stir_auth: failed to validate
>             Originator number (extension123)
>
>
>             loadmodule "stir_shaken.so"
>             modparam("stir_shaken", "auth_date_freshness", 300)
>             modparam("stir_shaken", "verify_date_freshness", 300)
>             modparam("stir_shaken", "require_date_hdr", 0)
>             modparam("stir_shaken", "e164_strict_mode", 0)
>
>             $var(orig) = $fU;
>             $var(dest) = $tU
>              $var(rc_auth)=stir_shaken_auth("A",
>             "GWID-123456","$var(cert)",
>             "$var(pkey)","http://localhost/certificate.pem
>             <http://localhost/certificate.pem>","$var(orig)","$var(dest)");
>
>             Please suggest a solution to this .
>
>             Many Thanks
>             Devang
>
>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our 
> website, any views or opinions presented in this email are solely 
> those of the originator and do not necessarily represent those of the 
> Company or its sister concerns. Any liability (in negligence, contract 
> or otherwise) arising from any third party taking any action, or 
> refraining from taking any action on the basis of any of the 
> information contained in this email is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for 
> the use of the addressee(s) and contains information that is 
> PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, 
> distribution, or copying of this communication is prohibited. Please 
> inform originator if you have received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of 
> viruses, trojans, similar or new contaminants/malware, interceptions 
> or interference, and may not be compatible with your systems. You 
> shall carry out virus/malware scanning on your own before opening any 
> attachment to this e-mail. The sender of this e-mail and Company 
> including its sister concerns shall not be liable for any damage that 
> may incur to you as a result of viruses, incompleteness of this 
> message, a delay in receipt of this message or any other computer 
> problems.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211123/d6a96a04/attachment.html>

From devang.dhandhalya at ecosmob.com  Wed Nov 24 12:57:00 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Wed, 24 Nov 2021 18:27:00 +0530
Subject: [OpenSIPS-Users] STIR/SHAKEN E.164 strict mode module parameter
	not working .
In-Reply-To: <835fff2d-f83a-4fe6-174e-2bdd574652bf@opensips.org>
References: <CAP0uOe9OpN2eQ2CMWgeiyHD9XxzgfCaBe378AEp89fw9zokyvw@mail.gmail.com>
 <CAP0uOe-qniAG4G7vFYGB41C2jbg4ZCfk6Gsd7BSNoNNiF-YNXw@mail.gmail.com>
 <CAP0uOe8tW+16jCHy4473KouEQXiDb91drHsj0nh6jrrnetZ7yw@mail.gmail.com>
 <CAP0uOe97m+PFhhRJRhTH=YuB8=quXVwG_5jexxA60+sBrbTOAA@mail.gmail.com>
 <835fff2d-f83a-4fe6-174e-2bdd574652bf@opensips.org>
Message-ID: <CAP0uOe-Xk1gKcRZzQMy+HSB3g4=hNqMRreMhigS-aeDqz84CBQ@mail.gmail.com>

Hello vlad

Thank you so much For your response , Verification Service works using
those certificates .

Regards,
Devang Dhandhalya

On Tue, Nov 23, 2021 at 10:32 PM Vlad Patrascu <vladp at opensips.org> wrote:

> Hello Devang,
>
> The cache_fetch() functions returns -2 when the key is not found so it's
> normal when getting the certificate the first time.
>
> STIR/SHAKEN requires that the certificates have the TnAuthList extension.
> You can check out some examples on how to generate such certificates in
> this document [1] at Appendix A or this script [2].
>
> [1]
> https://cstga.ca/wp-content/uploads/2020/07/ATIS-1000080.v002_SHAKEN-Governance-Model.pdf
>
> [2]
> https://github.com/OpenSIPIt/OpenSIPIt_00/blob/master/STIR_SHAKEN/Certgen/gencert.sh
>
> Regards,
>
> --
> Vlad Patrascu
> OpenSIPS Core Developerhttp://www.opensips-solutions.com
>
> On 22.11.2021 14:41, Devang Dhandhalya wrote:
>
> Hello Vlad
>
> Authentication service works fine. Now I am getting an error in the
> stir_shaken_verify function , after fetching a certificate, I am getting
> below error . I generated private keys and X509 certificates using
> prime256v1" EC.
> After fetching the certificate I am getting var(found) = -2 can you please
> tell me about this too .
>
> OpenSIPS Logs :
>
>
>
>
>
> *var(found) = [-2] INFO:stir_shaken:validate_certificate: The certificate
> is missing the TnAuthList extension INFO:stir_shaken:w_stir_verify: Invalid
> certificate return code : [-8] stir_shaken_verify() failed:437, Unsupported
> Credential *
> below opensips script snippet :
>
> $var(found) = cache_fetch("local",$identity(x5u),$var(cert));
>
>
> if (!$var(found) || !stir_shaken_check_cert("$var(cert)")) {
>                         rest_get("$identity(x5u)",$var(cert),$var(ctype),
> $var(http_rc));
>                         if ($rc<0 ) {
>                                 send_reply(436, "Bad Identity Info");
>                                 exit;
>                         }
> cache_store("local", $identity(x5u),"$var(cert)");
>                 }
>
>
> $var(rc_verify)= stir_shaken_verify($var(cert),
> $var(err_sip_code),$var(err_sip_reason),"$var(orig)","$var(dest)");
>                 if ($var(rc_verify) < 0) {
>
>                         send_reply(
> $var(err_sip_code),$var(err_sip_reason));
>                         exit;
>                 }
>
> Kindly inform me why I am getting this error . Please suggest a solution
> to this .
>
>
> Regards
> Devang Dhandhalya
>
>
> On Fri, Nov 19, 2021 at 3:16 PM Devang Dhandhalya <
> devang.dhandhalya at ecosmob.com> wrote:
>
>> Hello Vlad
>>
>> Thanks for your response . Authentication service works .
>>
>> Regards ,
>> Devang Dhandhalya
>>
>>
>> On Wed, Nov 17, 2021 at 8:57 PM Devang Dhandhalya <
>> devang.dhandhalya at ecosmob.com> wrote:
>>
>>> hello all
>>>
>>>
>>> Above E.164 Error still getting .Right now I'm getting the below error .
>>> Can anyone tell me why I am getting this error ? as far as i know this
>>> error for x5u parameter in stir_shaken_auth function , this issue coming
>>> for certificate path or certificate file format .
>>>
>>>
>>> I check the certificate file with .der and .cer format also .
>>>
>>> Here is the code snippet used .
>>> $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)", "$var(pkey)","http://localhost/certificate.pem","$var(orig)","$var(dest)");
>>>
>>> Below Error i am getting .
>>>
>>>
>>> ERROR:stir_shaken:add_identity_hf: Failed to convert from DER to internal format
>>>
>>> ERROR:stir_shaken:w_stir_auth: Failed to add Identity header
>>>
>>> STIR_SHAKEN AUTHENTICATION SERVICE  return code : -1
>>>
>>>
>>> Kindly let me know if there is something wrong that I could be doing.
>>>
>>> Many Thanks
>>> Devang Dhandhalya
>>>
>>>
>>> On Wed, Nov 17, 2021 at 11:37 AM Devang Dhandhalya <
>>> devang.dhandhalya at ecosmob.com> wrote:
>>>
>>>> Hi All
>>>>
>>>> I configured the e164 strict mode module parameter as 0 (disabled) .
>>>> but still i am getting errors related to its e164 format .While if
>>>> orig/dest number is not in e164 format then also opensips have to accept it
>>>> but it is not accepting .  I have a user like extension123 for this
>>>> function I have to perform authentication service . if i have a user
>>>> extension123 is it possible to perform authenticate service for this kind
>>>> of user ?
>>>>
>>>> I think this is a bug for the e164 strict mode  module parameter . I am
>>>> getting the below error .
>>>>
>>>> opensips version : 3.2.2
>>>>
>>>> ERROR :
>>>>  ERROR:stir_shaken:check_passport_phonenum: number is not in E.164
>>>> format: extension123
>>>>  ERROR:stir_shaken:w_stir_auth: failed to validate Originator number
>>>> (extension123)
>>>>
>>>>
>>>> loadmodule "stir_shaken.so"
>>>> modparam("stir_shaken", "auth_date_freshness", 300)
>>>> modparam("stir_shaken", "verify_date_freshness", 300)
>>>> modparam("stir_shaken", "require_date_hdr", 0)
>>>> modparam("stir_shaken", "e164_strict_mode", 0)
>>>>
>>>> $var(orig) = $fU;
>>>> $var(dest) = $tU
>>>>  $var(rc_auth)=stir_shaken_auth("A", "GWID-123456","$var(cert)",
>>>> "$var(pkey)","http://localhost/certificate.pem
>>>> ","$var(orig)","$var(dest)");
>>>>
>>>> Please suggest a solution to this .
>>>>
>>>> Many Thanks
>>>> Devang
>>>>
>>>
> *Disclaimer*
> In addition to generic Disclaimer which you have agreed on our website,
> any views or opinions presented in this email are solely those of the
> originator and do not necessarily represent those of the Company or its
> sister concerns. Any liability (in negligence, contract or otherwise)
> arising from any third party taking any action, or refraining from taking
> any action on the basis of any of the information contained in this email
> is hereby excluded.
>
> *Confidentiality*
> This communication (including any attachment/s) is intended only for the
> use of the addressee(s) and contains information that is PRIVILEGED AND
> CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying
> of this communication is prohibited. Please inform originator if you have
> received it in error.
>
> *Caution for viruses, malware etc.*
> This communication, including any attachments, may not be free of viruses,
> trojans, similar or new contaminants/malware, interceptions or
> interference, and may not be compatible with your systems. You shall carry
> out virus/malware scanning on your own before opening any attachment to
> this e-mail. The sender of this e-mail and Company including its sister
> concerns shall not be liable for any damage that may incur to you as a
> result of viruses, incompleteness of this message, a delay in receipt of
> this message or any other computer problems.
>
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211124/ceb70421/attachment.html>

From devang.dhandhalya at ecosmob.com  Thu Nov 25 06:55:42 2021
From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya)
Date: Thu, 25 Nov 2021 12:25:42 +0530
Subject: [OpenSIPS-Users] TLS Handshake fail issue
In-Reply-To: <CAP0uOe97Ygva2+u2VUQgYWXv0E9_ZXf0uQKfHBc+Qs3D5R85Fw@mail.gmail.com>
References: <CAP0uOe97Ygva2+u2VUQgYWXv0E9_ZXf0uQKfHBc+Qs3D5R85Fw@mail.gmail.com>
Message-ID: <CAP0uOe9GgEkcFmoaKxM+oUyZuFdakh7TuSCNfX7D8RyZRdt=aw@mail.gmail.com>

Hello Jehanzaib

Thanks For Your Response , Actually I generate TLS server (rootCA) and TLS
Client (user) certificates using opensips-cli  .
softphone : Blink version : 5.1.7
opensips version : 3.2.2

I generate certificates using the devang.com domain . I am implementing
this TLS support in a local machine . Can you please tell me how you know
that  I generate certificates using tlsv1 .

here is my first issue for tls hanshake with opensips configuration and dbg
lvl logs :
http://lists.opensips.org/pipermail/users/2021-November/045320.html
and Can you please tell me how to generate certificate with tlsv1.2 or
tlsv1.3

Regards,
Devang Dhandhalya

On Mon, Nov 22, 2021 at 6:27 PM Devang Dhandhalya <
devang.dhandhalya at ecosmob.com> wrote:

> Hello vlad
>
> Thanks for your response ,I used this command to check connection :openssl
> s_client -showcerts -debug -connect 192.168.0.105:5071 -bugs .
> Please let me know if there are any other commands to  check .
>
> CONNECTED(00000005)
> write to 0x561a52aa46b0 [0x561a52ab4eb0] (517 bytes => 517 (0x205))
> 140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
> ---
> no peer certificate available
> ---
> No client certificate CA names sent
> ---
> SSL handshake has read 7 bytes and written 517 bytes
> Verification: OK
> ---
> New, (NONE), Cipher is (NONE)
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> No ALPN negotiated
> Early data was not sent
> Verify return code: 0 (ok)
> ---
>
> In this TLS  connection i am getting one error :
> 140663188505024:error:14094458:SSL routines:ssl3_read_bytes:tlsv1
> unrecognized name:../ssl/record/rec_layer_s3.c:1528:SSL alert number 112
>
> Can you please give some suggestions on this .
>
> OpenSIPS starts successfully without errors and the following command
> shows listening on the correct port:
> netstat -tapen | grep 5071
> tcp        0      0 192.168.0.105:5071      0.0.0.0:*
> LISTEN      0          87130      9179/opensips
>
> I made some changes in the tls configuration . other than this same as
> before .
>
> socket=udp:192.168.0.105:5060 as devang.com:5060
> socket=tcp:192.168.0.105:5060 as devang.com:5060
> socket=tls:192.168.0.105:5071 as devang.com:5071
>
> modparam("tls_mgm", "match_ip_address", "[dom1]1.2.3.4:5071")
>
>
> At the time of calling, I get this error .
>
> ERROR:tls_openssl:openssl_tls_async_connect: New TLS connection to
> 192.168.0.105:44853 failed
> ERROR:tls_openssl:openssl_tls_async_connect: TLS error: 1 (ret=-1)
> err=Success(0)
> ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:14094410:SSL
> routines:ssl3_read_bytes:sslv3 alert handshake failure
> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!
>
> I tried setting all the tls version methods as 'tls_method' in opensips
> config but the same error occurred.  Please advise how to resolve this
> SSL23 handshake failure.
>
> Regards
> Devang Dhandhalya
>

-- 
*Disclaimer*
In addition to generic Disclaimer which you have agreed on our 
website, any views or opinions presented in this email are solely those of 
the originator and do not necessarily represent those of the Company or its 
sister concerns. Any liability (in negligence, contract or otherwise) 
arising from any third party taking any action, or refraining from taking 
any action on the basis of any of the information contained in this email 
is hereby excluded.



*Confidentiality*
This communication (including any 
attachment/s) is intended only for the use of the addressee(s) and contains 
information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, 
dissemination, distribution, or copying of this communication is 
prohibited. Please inform originator if you have received it in error.


*Caution for viruses, malware etc.*
This communication, including any 
attachments, may not be free of viruses, trojans, similar or new 
contaminants/malware, interceptions or interference, and may not be 
compatible with your systems. You shall carry out virus/malware scanning on 
your own before opening any attachment to this e-mail. The sender of this 
e-mail and Company including its sister concerns shall not be liable for 
any damage that may incur to you as a result of viruses, incompleteness of 
this message, a delay in receipt of this message or any other computer 
problems. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211125/285dcfbb/attachment.html>

From farmorg at gmail.com  Thu Nov 25 12:52:29 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 25 Nov 2021 12:52:29 +0000
Subject: [OpenSIPS-Users] Change probing_from() in script
Message-ID: <CAOvQDesfz57=9WW52VgJjc+M8SUpg+_jXzpdJ4dRQawESoECWA@mail.gmail.com>

Hi everyone

I have 2 interfaces (udp:internal & a natted tls:external as
xxx.xxx.xxx.xxx) and using drouting() to send sip OPTIONS to endpoints via
both.

I have been using the 'probing_from' parameter but I would like to change
the from URI depending on which interface the OPTIONS request will be sent
from.

Is this possible? I am using 3.2

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

From bogdan at opensips.org  Thu Nov 25 15:31:29 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 25 Nov 2021 17:31:29 +0200
Subject: [OpenSIPS-Users] Change probing_from() in script
In-Reply-To: <CAOvQDesfz57=9WW52VgJjc+M8SUpg+_jXzpdJ4dRQawESoECWA@mail.gmail.com>
References: <CAOvQDesfz57=9WW52VgJjc+M8SUpg+_jXzpdJ4dRQawESoECWA@mail.gmail.com>
Message-ID: <119c7c5d-fab5-f5e1-e5b6-43f590947089@opensips.org>

Hi Mark,

I'm afraid there is no way to do that.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/25/21 2:52 PM, Mark Farmer wrote:
> Hi everyone
>
> I have 2 interfaces (udp:internal & a natted tls:external as 
> xxx.xxx.xxx.xxx) and using drouting() to send sip OPTIONS to endpoints 
> via both.
>
> I have been using the 'probing_from' parameter but I would like to 
> change the from URI depending on which interface the OPTIONS request 
> will be sent from.
>
> Is this possible? I am using 3.2
>
> Many thanks
> Mark.
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

From farmorg at gmail.com  Thu Nov 25 16:40:05 2021
From: farmorg at gmail.com (Mark Farmer)
Date: Thu, 25 Nov 2021 16:40:05 +0000
Subject: [OpenSIPS-Users] Change probing_from() in script
In-Reply-To: <119c7c5d-fab5-f5e1-e5b6-43f590947089@opensips.org>
References: <CAOvQDesfz57=9WW52VgJjc+M8SUpg+_jXzpdJ4dRQawESoECWA@mail.gmail.com>
 <119c7c5d-fab5-f5e1-e5b6-43f590947089@opensips.org>
Message-ID: <CAOvQDeu=k5yyN3kC3u88D8pof3zxvQVXmN04LjDvX8URK7iYhg@mail.gmail.com>

Thanks Bogdan.

I did work around it in local_route by removing and re-adding the From:
header based on a specific destination.

Mark.

On Thu, 25 Nov 2021 at 15:31, Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Mark,
>
> I'm afraid there is no way to do that.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 11/25/21 2:52 PM, Mark Farmer wrote:
>
> Hi everyone
>
> I have 2 interfaces (udp:internal & a natted tls:external as
> xxx.xxx.xxx.xxx) and using drouting() to send sip OPTIONS to endpoints via
> both.
>
> I have been using the 'probing_from' parameter but I would like to change
> the from URI depending on which interface the OPTIONS request will be sent
> from.
>
> Is this possible? I am using 3.2
>
> Many thanks
> Mark.
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>

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

From david.villasmil.work at gmail.com  Fri Nov 26 01:48:09 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Fri, 26 Nov 2021 01:48:09 +0000
Subject: [OpenSIPS-Users] Forwarding ACK to 200 OK to itself.
Message-ID: <CAFGRPVoNJNj_8SCT5yqX4S1p9upYqOCRQ+P+5Vq4B_OGNZXa5g@mail.gmail.com>

Hello folks,

I'm facing this issue on this scenario:

[ 1] USER---INVITE--->OPENSIPS
[ 2]                  OPENSIPS---INVITE-->STIR/SHAKEN (OPENSIPS)
[ 3]                  OPENSIPS<--- 302 ---STIR/SHAKEN
[ 4]                  OPENSIPS<--- ACK ---STIR/SHAKEN
[ 5]                  OPENSIPS-----------INVITE--------->TERMINATION
[ 6]                  OPENSIPS<----------  180 ----------TERMINATION
[ 7]                  OPENSIPS<----------  183 ----------TERMINATION
[ 8]                  OPENSIPS<----------  200 ----------TERMINATION
[ 9] USER<-- 200 -----OPENSIPS
[10] USER--- ACK ---->OPENSIPS
[11]                  OPENSIPS--- ACK
[12]                  OPENSIPS<-- ACK
[13]                  OPENSIPS<----------  200 ----------TERMINATION
[14] USER<-- 200 -----OPENSIPS
[15] USER--- ACK ---->OPENSIPS
[16]                  OPENSIPS--- ACK
[17]                  OPENSIPS<-- ACK


This only happens when I enable that STIR/SHAKEN functionality and use the
302, when OpenSIPS sends out the INVITE [

The 200 OK has this as a record route:
Record-Route:<sip:10.241.40.144;lr=on;did=277.5664>,<sip:OPENSIPS_PRIVATE_IP:4060;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PUBLIC_IP:6070;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PRIVATE_IP:4060;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PUBLIC_IP:6070;r2=on;lr;ftag=gK0467de76>

what do i need to do to remove those duplicated record-routes after
receiving the 302?

Thanks alot for your help!

Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211126/cccf1b2d/attachment.html>

From bogdan at opensips.org  Fri Nov 26 07:02:28 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 26 Nov 2021 09:02:28 +0200
Subject: [OpenSIPS-Users] Change probing_from() in script
In-Reply-To: <CAOvQDeu=k5yyN3kC3u88D8pof3zxvQVXmN04LjDvX8URK7iYhg@mail.gmail.com>
References: <CAOvQDesfz57=9WW52VgJjc+M8SUpg+_jXzpdJ4dRQawESoECWA@mail.gmail.com>
 <119c7c5d-fab5-f5e1-e5b6-43f590947089@opensips.org>
 <CAOvQDeu=k5yyN3kC3u88D8pof3zxvQVXmN04LjDvX8URK7iYhg@mail.gmail.com>
Message-ID: <0ec37226-6eb5-1296-6c96-828087dc3df6@opensips.org>

Hi Mark,

The per-msg FROM changing will break the SIP , as the FROM hdr is dialog 
persistent (as value). But you have a point here, that probing OPTIONS 
is not creating any SIP dialog, so you should be good with that.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/

On 11/25/21 6:40 PM, Mark Farmer wrote:
> Thanks Bogdan.
>
> I did work around it in local_route by removing and re-adding the 
> From: header based on a specific destination.
>
> Mark.
>
> On Thu, 25 Nov 2021 at 15:31, Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>> wrote:
>
>     Hi Mark,
>
>     I'm afraid there is no way to do that.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS eBootcamp 2021
>        https://opensips.org/training/OpenSIPS_eBootcamp_2021/  <https://opensips.org/training/OpenSIPS_eBootcamp_2021/>
>
>     On 11/25/21 2:52 PM, Mark Farmer wrote:
>>     Hi everyone
>>
>>     I have 2 interfaces (udp:internal & a natted tls:external as
>>     xxx.xxx.xxx.xxx) and using drouting() to send sip OPTIONS to
>>     endpoints via both.
>>
>>     I have been using the 'probing_from' parameter but I would like
>>     to change the from URI depending on which interface the OPTIONS
>>     request will be sent from.
>>
>>     Is this possible? I am using 3.2
>>
>>     Many thanks
>>     Mark.
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org  <mailto:Users at lists.opensips.org>
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users  <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>
>
>
> -- 
> Mark Farmer
> farmorg at gmail.com <mailto:farmorg at gmail.com>

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

From david.villasmil.work at gmail.com  Fri Nov 26 13:38:08 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Fri, 26 Nov 2021 13:38:08 +0000
Subject: [OpenSIPS-Users] Forwarding ACK to 200 OK to itself.
In-Reply-To: <CAFGRPVoNJNj_8SCT5yqX4S1p9upYqOCRQ+P+5Vq4B_OGNZXa5g@mail.gmail.com>
References: <CAFGRPVoNJNj_8SCT5yqX4S1p9upYqOCRQ+P+5Vq4B_OGNZXa5g@mail.gmail.com>
Message-ID: <CAFGRPVqPaFBLLKaxPF4yXA8ijC3MA4P_YH24vvzzPufHr0kKxA@mail.gmail.com>

Hello folks,

So, the way the script is, it's adding a record_route() before doing the
STSH stuff, and that's adding that route for the rest of the flow...
I wonder if there's any way of removing it.

Regards,

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


On Fri, Nov 26, 2021 at 1:48 AM David Villasmil <
david.villasmil.work at gmail.com> wrote:

> Hello folks,
>
> I'm facing this issue on this scenario:
>
> [ 1] USER---INVITE--->OPENSIPS
> [ 2]                  OPENSIPS---INVITE-->STIR/SHAKEN (OPENSIPS)
> [ 3]                  OPENSIPS<--- 302 ---STIR/SHAKEN
> [ 4]                  OPENSIPS<--- ACK ---STIR/SHAKEN
> [ 5]                  OPENSIPS-----------INVITE--------->TERMINATION
> [ 6]                  OPENSIPS<----------  180 ----------TERMINATION
> [ 7]                  OPENSIPS<----------  183 ----------TERMINATION
> [ 8]                  OPENSIPS<----------  200 ----------TERMINATION
> [ 9] USER<-- 200 -----OPENSIPS
> [10] USER--- ACK ---->OPENSIPS
> [11]                  OPENSIPS--- ACK
> [12]                  OPENSIPS<-- ACK
> [13]                  OPENSIPS<----------  200 ----------TERMINATION
> [14] USER<-- 200 -----OPENSIPS
> [15] USER--- ACK ---->OPENSIPS
> [16]                  OPENSIPS--- ACK
> [17]                  OPENSIPS<-- ACK
>
>
> This only happens when I enable that STIR/SHAKEN functionality and use the
> 302, when OpenSIPS sends out the INVITE [
>
> The 200 OK has this as a record route:
>
> Record-Route:<sip:10.241.40.144;lr=on;did=277.5664>,<sip:OPENSIPS_PRIVATE_IP:4060;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PUBLIC_IP:6070;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PRIVATE_IP:4060;r2=on;lr;ftag=gK0467de76>,<sip:OPENSIPS_PUBLIC_IP:6070;r2=on;lr;ftag=gK0467de76>
>
> what do i need to do to remove those duplicated record-routes after
> receiving the 302?
>
> Thanks alot for your help!
>
> Regards,
>
> David Villasmil
> email: david.villasmil.work at gmail.com
> phone: +34669448337
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211126/f50201f2/attachment-0001.html>

From virendra at cloud-connect.in  Mon Nov 29 11:50:33 2021
From: virendra at cloud-connect.in (Virendra Bhati)
Date: Mon, 29 Nov 2021 17:20:33 +0530
Subject: [OpenSIPS-Users] Opensips 3.2 install issue with WolfSSL in CentOS7
Message-ID: <CAB=dTEc0k-UN5HzUQvJ2p6Pzm_kOwbG6yHasrcFsZjr6U8EvbQ@mail.gmail.com>

Dear Team,
I am not able to install Opensips 3.2. I am facing an issue with Automake
requiring version 1.14.1but CentOS 7.x have 1.13.X

Please suggest the best way to overcome this problem.

Linking avpops.so
make[2]: Leaving directory `/usr/src/bhati/opensips-3.2/modules/avpops'


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


--
Regards
Virendra Bhati
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211129/fa951b37/attachment.html>

From mickael.monsieur at gmail.com  Mon Nov 29 12:22:20 2021
From: mickael.monsieur at gmail.com (Mickael MONSIEUR)
Date: Mon, 29 Nov 2021 13:22:20 +0100
Subject: [OpenSIPS-Users] Parse P-Asserted-Identity
Message-ID: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>

Hello,

My provider add to my INVITE's :

P-Asserted-Identity: "Anonymous"
<sip:+xxxxxxx at sbc.provider.com>;party=calling;privacy=yes;screen=no

Whether the call should be Anonymized to end-users.

How to get the value of "privacy" ?

I try:

if( $(ai{privacy}) == "yes" )

But it does not work. (error when starting opensips)

Thanks


From david.villasmil.work at gmail.com  Mon Nov 29 12:30:30 2021
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Mon, 29 Nov 2021 12:30:30 +0000
Subject: [OpenSIPS-Users] Parse P-Asserted-Identity
In-Reply-To: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>
References: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>
Message-ID: <CAFGRPVpcHXHwQqUivH8431kybgskRa5n-xh739xGZtAVqo2S5w@mail.gmail.com>

https://www.opensips.org/Documentation/Script-Tran-2-4#toc60

Regards,

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


On Mon, Nov 29, 2021 at 12:22 PM Mickael MONSIEUR <
mickael.monsieur at gmail.com> wrote:

> Hello,
>
> My provider add to my INVITE's :
>
> P-Asserted-Identity: "Anonymous"
> <sip:+xxxxxxx at sbc.provider.com>;party=calling;privacy=yes;screen=no
>
> Whether the call should be Anonymized to end-users.
>
> How to get the value of "privacy" ?
>
> I try:
>
> if( $(ai{privacy}) == "yes" )
>
> But it does not work. (error when starting opensips)
>
> Thanks
>
> _______________________________________________
> 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/20211129/f06fc894/attachment.html>

From mickael.monsieur at gmail.com  Mon Nov 29 12:44:57 2021
From: mickael.monsieur at gmail.com (Mickael MONSIEUR)
Date: Mon, 29 Nov 2021 13:44:57 +0100
Subject: [OpenSIPS-Users] Parse P-Asserted-Identity
In-Reply-To: <CAFGRPVpcHXHwQqUivH8431kybgskRa5n-xh739xGZtAVqo2S5w@mail.gmail.com>
References: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>
 <CAFGRPVpcHXHwQqUivH8431kybgskRa5n-xh739xGZtAVqo2S5w@mail.gmail.com>
Message-ID: <CAK2CCpcOxezfhRasxA+D=TYSx4PNWY2PE-J-4N6DoO8MnUzXFA@mail.gmail.com>

Hello,

xlog("L_NOTICE","P-Asserted-Identity params = $(ai{param.value,privacy})\n");

Nov 29 13:43:34 [15988] P-Asserted-Identity params = <null>

Le lun. 29 nov. 2021 à 13:32, David Villasmil
<david.villasmil.work at gmail.com> a écrit :
>
> https://www.opensips.org/Documentation/Script-Tran-2-4#toc60
>
> Regards,
>
> David Villasmil
> email: david.villasmil.work at gmail.com
> phone: +34669448337
>
>
> On Mon, Nov 29, 2021 at 12:22 PM Mickael MONSIEUR <mickael.monsieur at gmail.com> wrote:
>>
>> Hello,
>>
>> My provider add to my INVITE's :
>>
>> P-Asserted-Identity: "Anonymous"
>> <sip:+xxxxxxx at sbc.provider.com>;party=calling;privacy=yes;screen=no
>>
>> Whether the call should be Anonymized to end-users.
>>
>> How to get the value of "privacy" ?
>>
>> I try:
>>
>> if( $(ai{privacy}) == "yes" )
>>
>> But it does not work. (error when starting opensips)
>>
>> Thanks
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From mickael.monsieur at gmail.com  Mon Nov 29 14:31:24 2021
From: mickael.monsieur at gmail.com (Mickael MONSIEUR)
Date: Mon, 29 Nov 2021 15:31:24 +0100
Subject: [OpenSIPS-Users] Parse P-Asserted-Identity
In-Reply-To: <CAK2CCpcOxezfhRasxA+D=TYSx4PNWY2PE-J-4N6DoO8MnUzXFA@mail.gmail.com>
References: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>
 <CAFGRPVpcHXHwQqUivH8431kybgskRa5n-xh739xGZtAVqo2S5w@mail.gmail.com>
 <CAK2CCpcOxezfhRasxA+D=TYSx4PNWY2PE-J-4N6DoO8MnUzXFA@mail.gmail.com>
Message-ID: <CAK2CCpco2Dtr368j=oqBjj-tjhGq=gA-mhZ1=it67oO080bLdw@mail.gmail.com>

No more result with:
xlog("L_NOTICE","P-Asserted-Identity param =
$(hdr(P-Asserted-Identity){param.value,privacy})\n");

Nov 29 14:17:13 [16103] P-Asserted-Identity param = <null>

Le lun. 29 nov. 2021 à 13:44, Mickael MONSIEUR
<mickael.monsieur at gmail.com> a écrit :
>
> Hello,
>
> xlog("L_NOTICE","P-Asserted-Identity params = $(ai{param.value,privacy})\n");
>
> Nov 29 13:43:34 [15988] P-Asserted-Identity params = <null>
>
> Le lun. 29 nov. 2021 à 13:32, David Villasmil
> <david.villasmil.work at gmail.com> a écrit :
> >
> > https://www.opensips.org/Documentation/Script-Tran-2-4#toc60
> >
> > Regards,
> >
> > David Villasmil
> > email: david.villasmil.work at gmail.com
> > phone: +34669448337
> >
> >
> > On Mon, Nov 29, 2021 at 12:22 PM Mickael MONSIEUR <mickael.monsieur at gmail.com> wrote:
> >>
> >> Hello,
> >>
> >> My provider add to my INVITE's :
> >>
> >> P-Asserted-Identity: "Anonymous"
> >> <sip:+xxxxxxx at sbc.provider.com>;party=calling;privacy=yes;screen=no
> >>
> >> Whether the call should be Anonymized to end-users.
> >>
> >> How to get the value of "privacy" ?
> >>
> >> I try:
> >>
> >> if( $(ai{privacy}) == "yes" )
> >>
> >> But it does not work. (error when starting opensips)
> >>
> >> Thanks
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users


From Ben.Newlin at genesys.com  Mon Nov 29 14:39:48 2021
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Mon, 29 Nov 2021 14:39:48 +0000
Subject: [OpenSIPS-Users] Parse P-Asserted-Identity
In-Reply-To: <CAK2CCpco2Dtr368j=oqBjj-tjhGq=gA-mhZ1=it67oO080bLdw@mail.gmail.com>
References: <CAK2CCpet3xNyqR+0h9mkZSWkXwS_JsnmbQgkDgEQENuzEabGmA@mail.gmail.com>
 <CAFGRPVpcHXHwQqUivH8431kybgskRa5n-xh739xGZtAVqo2S5w@mail.gmail.com>
 <CAK2CCpcOxezfhRasxA+D=TYSx4PNWY2PE-J-4N6DoO8MnUzXFA@mail.gmail.com>
 <CAK2CCpco2Dtr368j=oqBjj-tjhGq=gA-mhZ1=it67oO080bLdw@mail.gmail.com>
Message-ID: <BN0PR10MB5208CB687199D70E0ACB7A5395669@BN0PR10MB5208.namprd10.prod.outlook.com>

Mickael,

The PAI header is not just a parameter list, so you can’t use that transformation directly. The PAI header follows the name-addr spec and the params are part of the URI. So it would be something like one of the following.

$(ai{uri.param,privacy}) [1]
$(ai{nameaddr.param, privacy}) [2]

You may even have to combine the two if the parameters are associated with the uri in the name-addr:

$(ai{nameaddr.uri}{uri.param,privacy})

You should try printing out things like $(ai{nameaddr.uri}) or $(ai{uri.params}) to see what you get and help narrow down where the parameters are located. I always get confused by uri params vs host params vs name-addr params.

I will point out that the P-Asserted-Identity spec doesn’t actually define a privacy parameter like this. Privacy for PAI is indicated by the Privacy header, which is a separate header. For indicating privacy of the PAI header contents, the Privacy header should have a value of “id”. In fact, these parameters all seem to be ones typically used with the Remote-Party-ID (RPID) header, not the PAI header. [3] [4] [5]

You can check the presence and value of the Privacy header with something like this:

if (is_present_hf("Privacy") && ($hdr(Privacy) =~ "id|user")) {
  // do stuff
}

[1] https://www.opensips.org/Documentation/Script-Tran-3-2#toc38
[2] https://www.opensips.org/Documentation/Script-Tran-3-2#toc70
[3] https://datatracker.ietf.org/doc/html/rfc3325
[4] https://datatracker.ietf.org/doc/html/rfc3323
[5] https://datatracker.ietf.org/doc/html/draft-ietf-sip-privacy-04

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Mickael MONSIEUR <mickael.monsieur at gmail.com>
Date: Monday, November 29, 2021 at 9:32 AM
To: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] Parse P-Asserted-Identity
No more result with:
xlog("L_NOTICE","P-Asserted-Identity param =
$(hdr(P-Asserted-Identity){param.value,privacy})\n");

Nov 29 14:17:13 [16103] P-Asserted-Identity param = <null>

Le lun. 29 nov. 2021 à 13:44, Mickael MONSIEUR
<mickael.monsieur at gmail.com> a écrit :
>
> Hello,
>
> xlog("L_NOTICE","P-Asserted-Identity params = $(ai{param.value,privacy})\n");
>
> Nov 29 13:43:34 [15988] P-Asserted-Identity params = <null>
>
> Le lun. 29 nov. 2021 à 13:32, David Villasmil
> <david.villasmil.work at gmail.com> a écrit :
> >
> > https://www.opensips.org/Documentation/Script-Tran-2-4#toc60
> >
> > Regards,
> >
> > David Villasmil
> > email: david.villasmil.work at gmail.com
> > phone: +34669448337
> >
> >
> > On Mon, Nov 29, 2021 at 12:22 PM Mickael MONSIEUR <mickael.monsieur at gmail.com> wrote:
> >>
> >> Hello,
> >>
> >> My provider add to my INVITE's :
> >>
> >> P-Asserted-Identity: "Anonymous"
> >> <sip:+xxxxxxx at sbc.provider.com>;party=calling;privacy=yes;screen=no
> >>
> >> Whether the call should be Anonymized to end-users.
> >>
> >> How to get the value of "privacy" ?
> >>
> >> I try:
> >>
> >> if( $(ai{privacy}) == "yes" )
> >>
> >> But it does not work. (error when starting opensips)
> >>
> >> Thanks
> >>
> >> _______________________________________________
> >> 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/20211129/ef46182b/attachment.html>

From callum.guy at x-on.co.uk  Mon Nov 29 20:26:03 2021
From: callum.guy at x-on.co.uk (Callum Guy)
Date: Mon, 29 Nov 2021 20:26:03 +0000
Subject: [OpenSIPS-Users] Opensips 3.2 install issue with WolfSSL in
	CentOS7
In-Reply-To: <CAB=dTEc0k-UN5HzUQvJ2p6Pzm_kOwbG6yHasrcFsZjr6U8EvbQ@mail.gmail.com>
References: <CAB=dTEc0k-UN5HzUQvJ2p6Pzm_kOwbG6yHasrcFsZjr6U8EvbQ@mail.gmail.com>
Message-ID: <CAFjCFzkYPYgrtpLJ8cgz9M4-mugyJ7AVQi7rPx5cp2vK7Cea-w@mail.gmail.com>

You could try to install the required version?

https://centos.pkgs.org/7/okey-x86_64/automake-1.14-1.el7.x86_64.rpm.html

On Mon, 29 Nov 2021 at 11:52, Virendra Bhati via Users <
users at lists.opensips.org> wrote:

> Dear Team,
> I am not able to install Opensips 3.2. I am facing an issue with Automake
> requiring version 1.14.1but CentOS 7.x have 1.13.X
>
> Please suggest the best way to overcome this problem.
>
> Linking avpops.so
> make[2]: Leaving directory `/usr/src/bhati/opensips-3.2/modules/avpops'
>
>
> make[2]: Entering directory
> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
> make[2]: Leaving directory
> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
> make[2]: Entering directory
> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
> configure: error: cannot find install-sh, install.sh, or shtool in
> build-aux "."/build-aux
> make[2]: *** [lib/lib/libwolfssl.a] Error 1
> make[2]: Leaving directory
> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/src/bhati/opensips-3.2'
>
>
> --
> Regards
> Virendra Bhati
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

-- 






*0333 332 0000  |  x-on.co.uk <https://www.x-on.co.uk>  |   ** 
<https://www.linkedin.com/company/x-on>   <https://www.facebook.com/XonTel> 
  <https://twitter.com/xonuk> **  |  Coronavirus 
<https://www.x-on.co.uk/service/surgery-connect/coronavirus.htm>**  |  
Practice Index Reviews <https://practiceindex.co.uk/gp/x-on>*


THE ITSPA 
AWARDS 2020 <http://www.itspa.org.uk/itspa-awards> AND Best ITSP - Mid 
Market, Best Software and Best Vertical Solution are trade marks of the 
Internet Telephony Services Providers' Association, used under licence.

*Our new office address: 22 Riduna Park, Melton IP12 1QT.*

X-on
is a 
trading name of Storacall Technology Ltd a limited company registered in
England and Wales.

Registered Office : Avaland House, 110 London Road, 
Apsley, Hemel Hempstead,
Herts, HP3 9SD. Company Registration No. 2578478.

The information in this e-mail is confidential and for use by the 
addressee(s)
only. If you are not the intended recipient, please notify 
X-on immediately on +44(0)333 332 0000 and delete the
message from your 
computer. If you are not a named addressee you must not use,
disclose, 
disseminate, distribute, copy, print or reply to this email. Views
or 
opinions expressed by an individual
within this email may not necessarily
reflect the views of X-on or its associated companies. Although X-on 
routinely
screens for viruses, addressees should scan this email and any 
attachments
for
viruses. X-on makes no representation or warranty as to the 
absence of viruses
in this email or any attachments.










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

From virendra at cloud-connect.in  Tue Nov 30 05:37:08 2021
From: virendra at cloud-connect.in (Virendra Bhati)
Date: Tue, 30 Nov 2021 11:07:08 +0530
Subject: [OpenSIPS-Users] Opensips 3.2 install issue with WolfSSL in
	CentOS7
In-Reply-To: <CAFjCFzkYPYgrtpLJ8cgz9M4-mugyJ7AVQi7rPx5cp2vK7Cea-w@mail.gmail.com>
References: <CAB=dTEc0k-UN5HzUQvJ2p6Pzm_kOwbG6yHasrcFsZjr6U8EvbQ@mail.gmail.com>
 <CAFjCFzkYPYgrtpLJ8cgz9M4-mugyJ7AVQi7rPx5cp2vK7Cea-w@mail.gmail.com>
Message-ID: <CAB=dTEftTRJnhr4nNnb+cCXPgrALjPGHKQo4y_3MKpPtZ03A4g@mail.gmail.com>

Thank you Callum for providing information of automake custom RPM.  Now I
installed required CentOS 7 automake-1.14 with the help of below commands

[opensips-3.2]# rpm -ivh
http://repo.okay.com.mx/centos/7/x86_64/release/automake-1.14-1.el7.x86_64.rpm

[opensips-3.2]# yum install automake libtool


But still opensips 3.2 is not installed due to tls_wolfssl error.


make[2]: Entering directory
`/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
make[2]: Leaving directory `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
make[2]: Entering directory
`/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
configure: error: cannot find install-sh, install.sh, or shtool in
build-aux "."/build-aux
make[2]: *** [lib/lib/libwolfssl.a] Error 1
make[2]: Leaving directory `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/bhati/opensips-3.2'
Press any key to return to menuconfig

I have all files of WolfSSL in directory

[root at ip-172-31-7-46 tls_wolfssl]# ls
doc  Makefile  wolfssl_api.h  wolfssl_config.c  wolfssl_conn_ops.c
 wolfssl.d  wolfssl_tls_vars.c  wolfssl_trace.h
lib  README    wolfssl.c      wolfssl_config.d  wolfssl_conn_ops.d
 wolfssl.h  wolfssl_tls_vars.d
*Please suggest it to me.*

--
Regards



On Tue, Nov 30, 2021 at 1:56 AM Callum Guy <callum.guy at x-on.co.uk> wrote:

> You could try to install the required version?
>
> https://centos.pkgs.org/7/okey-x86_64/automake-1.14-1.el7.x86_64.rpm.html
>
> On Mon, 29 Nov 2021 at 11:52, Virendra Bhati via Users <
> users at lists.opensips.org> wrote:
>
>> Dear Team,
>> I am not able to install Opensips 3.2. I am facing an issue with Automake
>> requiring version 1.14.1but CentOS 7.x have 1.13.X
>>
>> Please suggest the best way to overcome this problem.
>>
>> Linking avpops.so
>> make[2]: Leaving directory `/usr/src/bhati/opensips-3.2/modules/avpops'
>>
>>
>> make[2]: Entering directory
>> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
>> make[2]: Leaving directory
>> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
>> make[2]: Entering directory
>> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
>> configure: error: cannot find install-sh, install.sh, or shtool in
>> build-aux "."/build-aux
>> make[2]: *** [lib/lib/libwolfssl.a] Error 1
>> make[2]: Leaving directory
>> `/usr/src/bhati/opensips-3.2/modules/tls_wolfssl'
>> make[1]: *** [modules] Error 2
>> make[1]: Leaving directory `/usr/src/bhati/opensips-3.2'
>>
>>
>> --
>> Regards
>> Virendra Bhati
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
>
>
> *0333 332 0000  |  x-on.co.uk <https://www.x-on.co.uk>  |   **
> <https://www.linkedin.com/company/x-on>   <https://www.facebook.com/XonTel>
>   <https://twitter.com/xonuk> **  |  Coronavirus
> <https://www.x-on.co.uk/service/surgery-connect/coronavirus.htm>**
> |  Practice Index Reviews <https://practiceindex.co.uk/gp/x-on>*
>
> THE ITSPA AWARDS 2020 <http://www.itspa.org.uk/itspa-awards> AND Best
> ITSP - Mid Market, Best Software and Best Vertical Solution are trade marks
> of the Internet Telephony Services Providers' Association, used under
> licence.
>
> *Our new office address: 22 Riduna Park, Melton IP12 1QT.*
>
> X-on is a trading name of Storacall Technology Ltd a limited company
> registered in England and Wales.
> Registered Office : Avaland House, 110 London Road, Apsley, Hemel
> Hempstead, Herts, HP3 9SD. Company Registration No. 2578478.
> The information in this e-mail is confidential and for use by the
> addressee(s) only. If you are not the intended recipient, please notify
> X-on immediately on +44(0)333 332 0000 and delete the
> message from your computer. If you are not a named addressee you must not
> use, disclose, disseminate, distribute, copy, print or reply to this email. Views
> or opinions expressed by an individual
> within this email may not necessarily reflect the views of X-on or its
> associated companies. Although X-on routinely screens for viruses,
> addressees should scan this email and any attachments
> for viruses. X-on makes no representation or warranty as to the absence of
> viruses in this email or any attachments.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211130/bb806dd9/attachment-0001.html>

From bogdan at opensips.org  Tue Nov 30 12:07:43 2021
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 30 Nov 2021 14:07:43 +0200
Subject: [OpenSIPS-Users] Working out OpenSIPS 3.3 roadmap
Message-ID: <bae80fde-1004-b11b-c6b6-54ab36542473@opensips.org>

Hi OpenSIPSers !

So far so good, but progress is a life philosophy. So it is the time to 
start planing the next step, the OpenSIPS 3.3 -  to decide what should 
be the main area to focus on when developing OpenSIPS 3.3, to decide 
what ideas and features just be counted when putting together the 
roadmap for 3.3.

So, we want to take the community pulse on the upcoming 3.3. Any 
suggestions, ideas, opinions are (as always) more than welcome for us 
and for the project. So, make your statement and please fill in this 
short (but relevant) form :

https://bit.ly/3o6cxEt

Best regards,

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
   https://opensips.org/training/OpenSIPS_eBootcamp_2021/