From tito at xsvoce.com  Tue Aug  2 05:01:59 2022
From: tito at xsvoce.com (Tito Cumpen)
Date: Mon, 1 Aug 2022 22:01:59 -0700
Subject: [OpenSIPS-Users] Issues running opensips-cli
Message-ID: <CANZPVB61PZVgeobNH4ZDHRYspy2omJwOEZ5=_vexu50nbNNcfQ@mail.gmail.com>

Group,

I am having issues running opensips-cli from the latest git pull. I am
attempting to create the db but noticed that running the cli tool alone
throws an error.

$ opensips-cli
Traceback (most recent call last):
  File
"/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_compat.py",
line 9, in <module>
    from typing import Protocol
ImportError: cannot import name 'Protocol'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/opensips-cli", line 4, in <module>
    __import__('pkg_resources').run_script('opensipscli==0.1.0',
'opensips-cli')
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line
654, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line
1434, in run_script
    exec(code, namespace, namespace)
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
line 3, in <module>
    from opensipscli import main
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/opensipscli/main.py",
line 22, in <module>
    from opensipscli import cli, defaults
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/opensipscli/cli.py",
line 31, in <module>
    from opensipscli.modules import *
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/opensipscli/modules/__init__.py",
line 24, in <module>
    __import__(modname)
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/opensipscli/modules/database.py",
line 23, in <module>
    from opensipscli.db import (
  File
"/home/azureuser/.local/lib/python3.6/site-packages/opensipscli-0.1.0-py3.6.egg/opensipscli/db.py",
line 37, in <module>
    import sqlalchemy_utils
  File
"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.38.3-py3.6.egg/sqlalchemy_utils/__init__.py",
line 1, in <module>
    from .aggregates import aggregated  # noqa
  File
"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.38.3-py3.6.egg/sqlalchemy_utils/aggregates.py",
line 374, in <module>
    from .compat import _select_args, get_scalar_subquery
  File
"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.38.3-py3.6.egg/sqlalchemy_utils/compat.py",
line 6, in <module>
    from importlib_metadata import metadata
  File
"/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/__init__.py",
line 17, in <module>
    from . import _adapters, _meta
  File
"/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_meta.py",
line 1, in <module>
    from ._compat import Protocol
  File
"/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_compat.py",
line 12, in <module>
    from typing_extensions import Protocol  # type: ignore
  File
"/usr/local/lib/python3.6/site-packages/typing_extensions-4.3.0-py3.6.egg/typing_extensions.py",
line 160, in <module>
    class _FinalForm(typing._SpecialForm, _root=True):
AttributeError: module 'typing' has no attribute '_SpecialForm'

I'm not very familiar with python so I am not sure if this is a dependency
issue.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220801/82579ab4/attachment.html>

From liviu at opensips.org  Tue Aug  2 15:01:27 2022
From: liviu at opensips.org (Liviu Chircu)
Date: Tue, 2 Aug 2022 18:01:27 +0300
Subject: [OpenSIPS-Users] Issues running opensips-cli
In-Reply-To: <CANZPVB61PZVgeobNH4ZDHRYspy2omJwOEZ5=_vexu50nbNNcfQ@mail.gmail.com>
References: <CANZPVB61PZVgeobNH4ZDHRYspy2omJwOEZ5=_vexu50nbNNcfQ@mail.gmail.com>
Message-ID: <053c52e8-8749-bd88-e480-bf91079e002b@opensips.org>

On 02.08.2022 08:01, Tito Cumpen wrote:
>
> I am having issues running opensips-cli from the latest git pull. I am 
> attempting to create the db but noticed that running the cli tool 
> alone throws an error.
>
> $ opensips-cli
> Traceback (most recent call last):
>   File 
> "/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_compat.py", 
> line 9, in <module>
>     from typing import Protocol
> ImportError: cannot import name 'Protocol'

Hi Tito,

Can you teach us how to reproduce the issue?

* what OS are you using?
* are you using your stock OS Python3.6 or a custom build?
* what commands did you use to install your "opensips-cli"?

Best regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events



From tito at xsvoce.com  Tue Aug  2 18:06:06 2022
From: tito at xsvoce.com (Tito Cumpen)
Date: Tue, 2 Aug 2022 11:06:06 -0700
Subject: [OpenSIPS-Users] Issues running opensips-cli
In-Reply-To: <053c52e8-8749-bd88-e480-bf91079e002b@opensips.org>
References: <CANZPVB61PZVgeobNH4ZDHRYspy2omJwOEZ5=_vexu50nbNNcfQ@mail.gmail.com>
 <053c52e8-8749-bd88-e480-bf91079e002b@opensips.org>
Message-ID: <CANZPVB5ePBWaf80LegpF9XJEYFE8N+D7GA=BTmCJuOe+9uyG7w@mail.gmail.com>

Hi Liviu,


Thanks for your reply

I am using centos 7.9

I used the following commands to install:

sudo yum install python36 python36-pip python36-devel gcc mysql-devel \
                 python36-mysql python36-sqlalchemy python36-pyOpenSSL

it looks like the default repos couldn't find these libs

No package python36-mysql available.
No package python36-sqlalchemy available.
No package python36-pyOpenSSL available.
Nothing to do

so I then proceeded by installing them with

sudo pip3 install mysqlclient sqlalchemy sqlalchemy-utils pyOpenSSL
I used the single user install
python3 setup.py install --user clean

Here is the info on the version of python and it looks like the deps are
available too
 python3 -V
Python 3.6.8
[azureuser at sip1-dev ~]$  pip3 freeze
cffi==1.15.1
cryptography==37.0.4
importlib-metadata==4.12.0
mypy==0.971
mypy-extensions==0.4.3
mysqlclient==1.3.14
opensipscli==0.1.0
protocol==0.1.0
pycparser==2.21
pyOpenSSL==22.0.0
SQLAlchemy==1.3.3
SQLAlchemy-Utils==0.38.3
tomli==1.2.3
typed-ast==1.5.4
typing_extensions==4.3.0
zipp==3.8.1

Thank You,
Tito

On Tue, Aug 2, 2022 at 8:01 AM Liviu Chircu <liviu at opensips.org> wrote:

> On 02.08.2022 08:01, Tito Cumpen wrote:
> >
> > I am having issues running opensips-cli from the latest git pull. I am
> > attempting to create the db but noticed that running the cli tool
> > alone throws an error.
> >
> > $ opensips-cli
> > Traceback (most recent call last):
> >   File
> >
> "/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_compat.py",
>
> > line 9, in <module>
> >     from typing import Protocol
> > ImportError: cannot import name 'Protocol'
>
> Hi Tito,
>
> Can you teach us how to reproduce the issue?
>
> * what OS are you using?
> * are you using your stock OS Python3.6 or a custom build?
> * what commands did you use to install your "opensips-cli"?
>
> Best regards,
>
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
> OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220802/a63a29bd/attachment.html>

From liviu at opensips.org  Wed Aug  3 15:58:06 2022
From: liviu at opensips.org (Liviu Chircu)
Date: Wed, 3 Aug 2022 18:58:06 +0300
Subject: [OpenSIPS-Users] [Release] OpenSIPS 3.1.11 and 3.2.8 minor releases
Message-ID: <c603cb27-0320-3dbb-4c6a-33adfbbc1129@opensips.org>

Hi, everyone!

The 3.1.11 and 3.2.8 OpenSIPS minor versions are scheduled for release 
on Wed, August 17th -- that's two weeks from now.

In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.

Happy testing,

-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events



From david.villasmil.work at gmail.com  Thu Aug  4 17:52:43 2022
From: david.villasmil.work at gmail.com (David Villasmil)
Date: Thu, 4 Aug 2022 19:52:43 +0200
Subject: [OpenSIPS-Users] $param?
Message-ID: <CAFGRPVpPZyHWTCxgASXAD9XOHj01bSYqGhxGb2uv=94E+WxzQQ@mail.gmail.com>

Hello folks,

It's been a while since i've worked with OpenSIPS, and I'm seeing a script
using

$var(addPrefix) = $param(1);

I don't really know what that $param does, can anyone help me out here?

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/20220804/a258d9bb/attachment.html>

From Ben.Newlin at genesys.com  Thu Aug  4 19:56:53 2022
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Thu, 4 Aug 2022 19:56:53 +0000
Subject: [OpenSIPS-Users] $param?
In-Reply-To: <CAFGRPVpPZyHWTCxgASXAD9XOHj01bSYqGhxGb2uv=94E+WxzQQ@mail.gmail.com>
References: <CAFGRPVpPZyHWTCxgASXAD9XOHj01bSYqGhxGb2uv=94E+WxzQQ@mail.gmail.com>
Message-ID: <BN0PR10MB5208CC0F6153B324FA861FA2959F9@BN0PR10MB5208.namprd10.prod.outlook.com>

It is used to access parameters that were passed to a custom route. $param(1) is the first passed parameter.

https://www.opensips.org/Documentation/Script-CoreVar-3-3#toc60

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of David Villasmil <david.villasmil.work at gmail.com>
Date: Thursday, August 4, 2022 at 1:54 PM
To: users at lists.opensips.org <users at lists.opensips.org>
Subject: [OpenSIPS-Users] $param?
 EXTERNAL EMAIL - Please use caution with links and attachments

________________________________
Hello folks,

It's been a while since i've worked with OpenSIPS, and I'm seeing a script using

$var(addPrefix) = $param(1);

I don't really know what that $param does, can anyone help me out here?

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/20220804/1820bb27/attachment.html>

From fneto at sothis.com.br  Wed Aug  3 18:27:20 2022
From: fneto at sothis.com.br (Francisco Neto)
Date: Wed, 3 Aug 2022 18:27:20 +0000
Subject: [OpenSIPS-Users] Bug on TLS Management Interface
References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark>
Message-ID: <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark>

Hi All!

I’ve just installed open sips and everything is working ok, except the TLS Management interface.

When I try to add ou update any entry, it only accept “Network Address” as “*”.

If I type the IP address as x.x.x.x:port or “x.x.x.x:port” or ‘x.x.x.x:port’ it always complain with the following message: Failed to validate input for match_ip_address

Can someone give me a tip of how should I write the IP address or if it a bug?

Thanks!

[cid:4D4E11AC4AD945D9B0DAB9AFC951BF99]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220803/43d0a05f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png
Type: image/png
Size: 8292 bytes
Desc: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png
URL: <http://lists.opensips.org/pipermail/users/attachments/20220803/43d0a05f/attachment.png>

From ryzhik.ivan at gmail.com  Mon Aug  8 08:48:29 2022
From: ryzhik.ivan at gmail.com (Ryzhik Ivan)
Date: Mon, 8 Aug 2022 11:48:29 +0300
Subject: [OpenSIPS-Users] call_center module on 3.3
Message-ID: <CAG9R00pAS2_-pg4vK6VTuB=2GE95Q8zvpw0MfGTbxxi0VFKnew@mail.gmail.com>

Hi @All.
I have a simple flow with 2 agents. When call entering queue
by cc_handle_call("600")
and the first agent rejects call (busy or decline) - queue also rejects
call with same reason and does not proceed to second agent.
I looked at sources  - negative replies processed only
in B2B_BRIDGING_STATE. But for that time i have B2B_NOTDEF_STATE only.
What am I doing wrong?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220808/c5e1fd1b/attachment.html>

From bogdan at opensips.org  Tue Aug  9 08:36:19 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 11:36:19 +0300
Subject: [OpenSIPS-Users] call_center module on 3.3
In-Reply-To: <CAG9R00pAS2_-pg4vK6VTuB=2GE95Q8zvpw0MfGTbxxi0VFKnew@mail.gmail.com>
References: <CAG9R00pAS2_-pg4vK6VTuB=2GE95Q8zvpw0MfGTbxxi0VFKnew@mail.gmail.com>
Message-ID: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org>

Hi,

In such a case, in `b2bl_callback_customer()` you should get a 
B2B_REJECT_CB event.

Could you post here the logs in log_level 4 (debug) for your test call ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/8/22 11:48 AM, Ryzhik Ivan wrote:
> Hi @All.
> I have a simple flow with 2 agents. When call entering queue 
> by cc_handle_call("600")
> and the first agent rejects call (busy or decline) - queue also 
> rejects call with same reason and does not proceed to second agent.
> I looked at sources  - negative replies processed only 
> in B2B_BRIDGING_STATE. But for that time i have B2B_NOTDEF_STATE only.
> What am I doing wrong?
>
>
>
>
> _______________________________________________
> 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/20220809/6ad39df8/attachment.html>

From bogdan at opensips.org  Tue Aug  9 08:39:04 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 11:39:04 +0300
Subject: [OpenSIPS-Users] Bug on TLS Management Interface
In-Reply-To: <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark>
References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark>
 <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark>
Message-ID: <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org>

Hi Francisco,

I guess you are talking about managing certificates via the Control 
Panel, right ? if so, what version of OpenSIPS and OpenSIPS CP are you 
using ? Also, could you provide a screenshot of the add / update form, 
showing the issue? IF you have any sensitive data, please send the 
screenshot privately to me.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/3/22 9:27 PM, Francisco Neto via Users wrote:
> Hi All!
>
> I’ve just installed open sips and everything is working ok, except the 
> TLS Management interface.
>
> When I try to add ou update any entry, it only accept “Network 
> Address” as “*”.
>
> If I type the IP address as x.x.x.x:port or “x.x.x.x:port” or 
> ‘x.x.x.x:port’ it always complain with the following message: Failed 
> to validate input for match_ip_address
>
> Can someone give me a tip of how should I write the IP address or if 
> it a bug?
>
> 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/20220809/c41ad458/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220809/c41ad458/attachment.png>

From bogdan at opensips.org  Tue Aug  9 08:42:02 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 11:42:02 +0300
Subject: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
In-Reply-To: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
References: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
Message-ID: <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>

Hi Artiom,

Do you use any proto TCP or TLS specific tracing (like [1]), or only 
pure SIP TLS tracing ?

[1] 
https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 7/25/22 11:20 AM, Artiom Druz wrote:
> Hello Everyone.
> I have a problem with monitoring SIPS/TLS based on tls_wolfssl module 
> via proto_hep (target monitoring service is Homer 7).
> My opensips config works ok with SIP/UDP, but when I make a call via 
> TLS (OpenSIPS convert TLS from VoIP provider to internal SIP/UDP 
> software PBX) in dump file on Homer 7 side I see that all packets in 
> HEP3 payload has this info:
>
> HEP3 Protocol
>     HEP Version: HEP3
>     HEP Packet Size (Bytes): 152
>     IP family: IPv4
>     Ingested Transport Protocol: IPv4
>     Source port: 0
>     Destination port: 0
>     Unix Timestamp: 1658731857
>     Timestamp µs: 106136
>     Application Protocol: Unknown Application Protocol
>     Capture Node ID: 1301
>     Source IPv4 address: 127.0.0.2
>     Destination IPv4 address: 127.0.0.2
>     Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>     Correlation ID: 350784072629638188
>
> Only unix timestamp and capture node id is correct.
> As you can see in encapsulated payload I have an error with read. What 
> can be wrong?
>
> OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>
> _______________________________________________
> 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/20220809/d664bd2c/attachment-0001.html>

From bogdan at opensips.org  Tue Aug  9 08:45:29 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 11:45:29 +0300
Subject: [OpenSIPS-Users] TLS_MGM
In-Reply-To: <B9561A20-DD6D-4669-8D21-C1EFC7FD4594@icloud.com>
References: <B9561A20-DD6D-4669-8D21-C1EFC7FD4594@icloud.com>
Message-ID: <2d1d6b2a-a7b2-801c-d730-d01eb125747a@opensips.org>

Hi Vadim,

This log looks weird :

июл 19 21:11:32 proxy-01 opensips[13765]: CRITICAL:core:yyerror: parse error in /etc/opensips/opensips.cfg:110:21-22: Parameter <certificate> not found in module <tls

it should be like:

июл 19 21:11:32 proxy-01 opensips[13765]: CRITICAL:core:yyerror: parse error in /etc/opensips/opensips.cfg:110:21-22: Parameter <certificate> not found in module <tls_mgm>

So, check the modparam line for any typos or weird chars in the name of the module.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 7/20/22 12:35 AM, Vadim Dumalekov via Users wrote:
> Hello!
>
> I have installed the OpenSIPS-3.2.7. I'm trying to set up the WSS-proto. It requires the tls_mgm module be loaded. I have the following settings for this module:
>
> loadmodule "tls_mgm.so"
>          modparam("tls_mgm", "tls_library", "openssl")
>          modparam("tls_mgm", "certificate", "/etc/opensips/tls/rootCA/cacert.pem")
>          modparam("tls_mgm", "private_key", "/etc/opensips/tls/rootCA/private/cakey.pem")
>
> But when i triy to run opensips I have this problem:
>
> июл 19 21:11:32 proxy-01 opensips[13765]: CRITICAL:core:yyerror: parse error in /etc/opensips/opensips.cfg:110:21-22: Parameter <certificate> not found in module <tls
> июл 19 21:11:32 proxy-01 opensips[13765]: loadmodule "tls_mgm.so"
> июл 19 21:11:32 proxy-01 opensips[13765]:         modparam("tls_mgm", "tls_library", "openssl")
> июл 19 21:11:32 proxy-01 opensips[13765]:         modparam("tls_mgm", "certificate", "/etc/opensips/tls/rootCA/cacert.pem")
> июл 19 21:11:32 proxy-01 opensips[13765]:         ^~
> июл 19 21:11:32 proxy-01 opensips[13765]:         modparam("tls_mgm", "private_key", "/etc/opensips/tls/rootCA/private/cakey.pem")
> июл 19 21:11:32 proxy-01 opensips[13765]:
> июл 19 21:11:32 proxy-01 opensips[13765]: ERROR:tls_mgm:split_param_val: No TLS domain name
> июл 19 21:11:32 proxy-01 opensips[13765]: CRITICAL:core:yyerror: parse error in /etc/opensips/opensips.cfg:111:21-22: Parameter <private_key> not found in module <tls
> июл 19 21:11:32 proxy-01 opensips[13765]: ERROR:core:parse_opensips_cfg: bad config file (2 errors)
> июл 19 21:11:32 proxy-01 opensips[13765]: ERROR:core:main: failed to parse config file /etc/opensips/opensips.cfg
> июл 19 21:11:32 proxy-01 opensips[13765]: NOTICE:core:main: Exiting....
> июл 19 21:11:32 proxy-01 systemd[1]: opensips.service: control process exited, code=exited status=255
> июл 19 21:11:32 proxy-01 systemd[1]: Failed to start OpenSIPS is a very fast and flexible SIP (RFC3261) server.
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



From bogdan at opensips.org  Tue Aug  9 09:00:25 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 12:00:25 +0300
Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in
 event header of NOTIFY(REFER)
In-Reply-To: <SA1PR09MB80004620A34C1A7EE463113E8E909@SA1PR09MB8000.namprd09.prod.outlook.com>
References: <SA1PR09MB80004620A34C1A7EE463113E8E909@SA1PR09MB8000.namprd09.prod.outlook.com>
Message-ID: <bcbf4e1f-709e-36ec-dc68-509ac0ad925b@opensips.org>

Hi Li,

If I understand correctly, you try to improve the b2b support in 
OpenSIPS in order to properly handle that NOTIFY for REFER, right ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 7/22/22 11:02 PM, Li Cai wrote:
>
> Hi experts,
>
> I’m working on the implementation for ‘2.4.6 Multiple REFER Requests 
> in a Dialog’ of RFC3515 in a B2B SIP Proxy. Right now, I got stuck 
> with two problems in the solution. Please see the paragraph from RFC-
>
>    A REFER creates an implicit subscription sharing the dialog
>
> identifiers in the REFER request.  If more than one REFER is issued
>
>    in the same dialog (a second attempt at transferring a call for
>
> example), the dialog identifiers do not provide enough information to
>
> associate the resulting NOTIFYs with the proper REFER.
>
>    Thus, for the second and subsequent REFER requests a UA receives in a
>
>    given dialog, it MUST include an id parameter[2] in the Event header
>
>    field of each NOTIFY containing the sequence number (the number from
>
>    the CSeq header field value) of the REFER this NOTIFY is associated
>
>    with. This id parameter MAY be included in NOTIFYs to the first
>
>    REFER a UA receives in a given dialog.  A SUBSCRIBE sent to refresh
>
>    or terminate this subscription MUST contain this id parameter.
>
> Different from the definition in RFC, the NOTIFY forwarded by the 
> proxy contains the same Id in Event header as the other side. Please 
> see the below chart –
>
>                    B2BProxy
>
>                                            |
>
>                 <- REFER 2 (Cseq=2) |                  <-REFER 1 
>  (Cseq=1003)
>
>                            . . .                  | . . .
>
> ->NOTIFY 1 (event:*id=2*)         |  ->NOTIFY 2 (_event*:id=2*)_
>
> The current problem is, the above NOTIFY on the right side should 
> _include ‘id=1003’ instead of ‘id=2’_.
>
> The solution I’m trying is as in the following flow –
>
>       1.         get CSeq 1 of REFER 1 in route[b2b_request]{}  ->
>
>       2.         get CSeq 2 of REFER 2 in local_route{},  then save 
> the pair(key=CSeq2, value=CSeq1) in a map set->
>
>       3.         get Id  from NOTIFY 1 event in route[b2b_request]{}  ->
>
>       4.         use Id  as key then get matched CSeq1 from the map 
> set, use remove_hf() and append_hf() to modify the event header in 
> local_route{}
>
> My two questions are:
>
>  1. To transfer Cseq 1 from step1 to step2, I tried a variable in the
>     AVP type but it didn’t work. The script variable can work but it
>     doesn’t fit because the processing is based on per request.  Can I
>     ask if you have any suggest on how to transfer the value from
>     route[b2b_request]{} to local_route{}?
>  2. In the step2, I tried to create and operate a JSON map set to save
>     the CSeq pairs. But the JSON data didn’t work for me.
>
>             My source :
>
>                                     $json(csList) = ””;       # 
> Initialize the data set, not sure if it’s correct
>
> $json(csList/”$cs”) = “$avp(csNum)”;
>
>             The error I got:
>
> ERROR:core:do_assign: setting PV failed
>
> ERROR:core:do_assign: error at /usr/local//et/opensips/opensips.cfg:531
>
> Thank you very much for the help! Any your suggests are very welcomed.
>
> Thanks,
>
> Li
>
> NOTICE TO RECIPIENT: This email, including attachments, may contain 
> information which is confidential, proprietary, attorney-client 
> privileged and / or controlled under U.S. export laws and regulations 
> and may be restricted from disclosure by applicable State and Federal 
> law. Nothing in this email shall create any legal binding agreement 
> between the parties unless expressly stated herein and provided by an 
> authorized representative of Comtech Telecommunications Corp. or its 
> subsidiaries. If you are not the intended recipient of this message, 
> be advised that any dissemination, distribution, or use of the 
> contents of this message is strictly prohibited. If you received this 
> message in error, please notify us immediately by return email and 
> permanently delete all copies of the original email and any attached 
> documentation from any computer or other media.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

From bogdan at opensips.org  Tue Aug  9 09:05:20 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 12:05:20 +0300
Subject: [OpenSIPS-Users] Dialog ping question
In-Reply-To: <CAEZrhoMzfEjuPr41GAwH+wT2z67dgnSGXndwEbRt+nvV5-DBtw@mail.gmail.com>
References: <CAEZrhoMzfEjuPr41GAwH+wT2z67dgnSGXndwEbRt+nvV5-DBtw@mail.gmail.com>
Message-ID: <bc0b40c2-39c1-91be-2848-bfae3a22925d@opensips.org>

Hi MS,

You can use the Call-ID to correlate with the dialog. For example, use 
the localcache to store (when creating the dialog) a record having as 
key the call-id of the call and as value the time to start. In the 
generic on_reply you can look for that records into localcache and to 
the math for the duration.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 7/10/22 9:23 PM, M S wrote:
> Hi all,
> I need to catch the replies to OPTIONS (ping) packets that 
> Create_dialog("Pp") sends to both sides, and then based on response 
> code and some other transaction information, i.e. I need to calculate 
> the call length (from pick up till that moment) to send 
> Interim-Updates to RADIUS.
> My questions are:
> 1. How do I  check for those internal OPTIONS replies? I can see 
> replies in a global onreply_route, but there is no transaction level 
> information there
> 2. How do I calculate the call length? I assume if #1 above is fixed, 
> I can store answer time in a variable and then calculate length in 
> onreply.
>
> Thank you!
>
> _______________________________________________
> 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/20220809/ccde26ce/attachment-0001.html>

From bogdan at opensips.org  Tue Aug  9 09:35:03 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 12:35:03 +0300
Subject: [OpenSIPS-Users] Why is rest_get truncating pem in the output
 var?
In-Reply-To: <CAPY59GypSUsAKEw2jZwdkBUjHuZom_hAtNtDN1QA_Rqe5BWCCg@mail.gmail.com>
References: <CAPY59GypSUsAKEw2jZwdkBUjHuZom_hAtNtDN1QA_Rqe5BWCCg@mail.gmail.com>
Message-ID: <ba7497ca-4a3a-f029-aa8c-c195c0a20b71@opensips.org>

Hi Joshua,

The xlogging is truncated by default to 4K, see 
https://www.opensips.org/Documentation/Script-CoreParameters-3-2#xlog_buf_size.

Still, the printing only of the first line is strange :-/, unless some 
special chars are in the certificate. You can try to print what is after 
that first line, by using the substr() transformation , skip the first 
28/29 chars of the "-----BEGIN CERTIFICATE-----"...just to see what's in 
there.

Now regarding on the failure of the verification, have you tried to run 
in debug level (set log_level to 4), to see what the function does, 
maybe there are some clues there.

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 7/1/22 7:59 PM, Joshua Young via Users wrote:
> Hello OpenSIPS,
>
> I'm trying to implement the stir_shaken_verify() function, and I have 
> a feeling the rest_get() is truncating output variable...
>
> I have these for the modules
>
> ...
> # STIR/SHAKEN modules
> loadmodule "rest_client.so"
> loadmodule "stir_shaken.so"
> modparam("stir_shaken", "require_date_hdr", 0)
> modparam("stir_shaken", "verify_date_freshness", 300)
> loadmodule "cfgutils.so"
> modparam("cfgutils", "shvset", "stirshaken=s:enable")
> modparam("stir_shaken", "ca_list", "/etc/opensips/tls/calist.pem")
> ...
>
> and then I'm using something like this to do the verifying
>
> ...
>     $var(rc) = rest_get( "$identity(x5u)", $var(cert), $var(ctype), 
> $var(http_rc));
>     if ($var(rc) < 0) {
>         xlog("L_ERR", "rest_get() FAILED\n");
>        send_reply(436, "Bad Identity Info");
>        exit;
>     } else {
>         $var(len) = $(var(cert){s.len});
>         $var(cert_full) = $(var(cert){s.escape.common});
>         xlog("L_ERR","cert full = $var(cert_full)");
>         xlog("L_ERR", "length $$var(cert) = $var(len)\n");
>         xlog("L_ERR", "rest_get() PASSED:  $$var(cert) = $var(cert)");
>     }
>
>     xlog("L_ERR","$$identity(x5u) = $identity(x5u)");
>     $var(rc) = stir_shaken_verify("$var(cert)", $var(err_code), 
> $var(err_reason), $identity(orig), $identity(dest));
>     if ($var(rc) < -1) {
>         xlog("L_ERR", "stir_shaken_verify() FAILED\n");
>         send_reply($var(err_code), $var(err_reason));
>         exit;
>     } else {
>         xlog("L_ERR", "stir_shaken_verify() PASSED\n");
>     }
> ...
>
>
> my output xlogs are showing
> ...
> /usr/local/sbin/opensips[113989]: cert full = -----BEGIN CERTIFICATE-----
> /usr/local/sbin/opensips[113989]: length $var(cert) = 2367
> /usr/local/sbin/opensips[113989]: rest_get() PASSED:  $var(cert) = 
> -----BEGIN CERTIFICATE-----
> /usr/local/sbin/opensips[113989]: cached $var(cert) is still good
> /usr/local/sbin/opensips[113989]: $identity(x5u) = 
> https://cr.sansay.com/star2star-prod-stirshaken 
> <https://cr.sansay.com/star2star-prod-stirshaken>
> /usr/local/sbin/opensips[113989]: INFO:stir_shaken:verify_callback: 
> certificate validation failed: certificate signature failure
> /usr/local/sbin/opensips[113989]: INFO:stir_shaken:w_stir_verify: 
> Invalid certificate
> /usr/local/sbin/opensips[113989]: stir_shaken_verify() FAILED
> ...
>
> the variable is showing 2367 bytes
>
> $var(len) = $(var(cert){s.len});
> xlog("L_ERR", "length $$var(cert) = $var(len)\n");
> /usr/local/sbin/opensips[113989]: length $var(cert) = 2367
>
> but regardless what I try to print, it only printing the first line
>
> $var(cert_full) = $(var(cert){s.escape.common});
> xlog("L_ERR","cert full = $var(cert_full)");
> /usr/local/sbin/opensips[113989]: cert full = -----BEGIN CERTIFICATE-----
>
>  xlog("L_ERR", "rest_get() PASSED:  $$var(cert) = $var(cert)");
> /usr/local/sbin/opensips[113989]: rest_get() PASSED:  $var(cert) = 
> -----BEGIN CERTIFICATE-----
> ....
>
> Perhaps this isnt the issue after all, but I am unable to determine 
> why the stir_shaken_verify() is failing
>
> /usr/local/sbin/opensips[113989]: INFO:stir_shaken:verify_callback: 
> certificate validation failed: certificate signature failure
> /usr/local/sbin/opensips[113989]: INFO:stir_shaken:w_stir_verify: 
> Invalid certificate
>
> I feel like the $var(cert) is being truncated which i why it's 
> failing... but I have no clue...
>
> Can you provide pointers?
> 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/20220809/4d3ba6b6/attachment.html>

From bogdan at opensips.org  Tue Aug  9 09:37:49 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 12:37:49 +0300
Subject: [OpenSIPS-Users] OpenSIPS CP 9.3.2 password mode ha1_sha256 for
 adding new user
In-Reply-To: <SY4P282MB225298502B23FA55E420CBB2C0BB9@SY4P282MB2252.AUSP282.PROD.OUTLOOK.COM>
References: <SY4P282MB225298502B23FA55E420CBB2C0BB9@SY4P282MB2252.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <413690b6-5374-79be-9c41-247e410906b1@opensips.org>

Hi Bela,

The OCP does not support ha1_sha256 AFAIK. Consider opening a feature 
request here https://github.com/OpenSIPS/opensips-cp/issues

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 6/29/22 9:10 AM, Bela H wrote:
>
> Hi all,
>
> Is there any way to add new subscriber from OpenSIPS CP 9.3.2 using 
> password mode ha1_sha256?
>
> The ha1 (MD5(username:realm:password)) works fine but I had no luck 
> with the value generation for the ha1_sha256 field in “subscriber” table.
>
> I have this setting:
>
> modparam("auth_db", "calculate_ha1", 0)
>
> modparam("auth_db", "password_column", "ha1_sha256")
>
> Thanks!
>
> Bela
>
>
> _______________________________________________
> 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/20220809/8d9b17e8/attachment.html>

From bogdan at opensips.org  Tue Aug  9 09:44:56 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 12:44:56 +0300
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
Message-ID: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>

Hi HS,

The aliases and late SDP negotiation has noting in common.

And the mentioned script has no support for aliase - I guess you added 
such support ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 6/20/22 5:21 PM, HS wrote:
> Hi all.
>
> Just wondering if anyone has "dbaliases" working with the Late SDP 
> negotiation script below:
>
> https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg 
> <https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg>
>
> If we call an alias, it works fine if the user is online. However, in 
> case of offline users I want the call to be forwarded to another 
> instance/server. If we use the ID (from subscriber table) calls are 
> being forwarded. But not if we dial an alias.
>
> Appreciate the help.
>
> _______________________________________________
> 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/20220809/f8742bd8/attachment.html>

From bogdan at opensips.org  Tue Aug  9 13:55:24 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 9 Aug 2022 16:55:24 +0300
Subject: [OpenSIPS-Users] call_center module on 3.3
In-Reply-To: <CAG9R00qPmyDK1rBFn5=JDKkBATH=eGFUuydPATkn0W=Ls0tzBg@mail.gmail.com>
References: <CAG9R00pAS2_-pg4vK6VTuB=2GE95Q8zvpw0MfGTbxxi0VFKnew@mail.gmail.com>
 <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org>
 <CAG9R00qPmyDK1rBFn5=JDKkBATH=eGFUuydPATkn0W=Ls0tzBg@mail.gmail.com>
Message-ID: <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org>

Thanks Ivan,

The relevant log is

DBG:call_center:b2bl_callback_customer:  call (0x7f0a08e95a00) has event 4

But the event 4 (B2B leg destroyed) is a wrong one in this case, it 
should have been 2 (B2B leg rejected). It seems the problem is in the 
B2B logic somewhere.

Let me do some digging there.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/9/22 3:04 PM, Ryzhik Ivan wrote:
> Hi,
> thank you for your reply.
>
> There is no B2B_REJECT_CB in my case. See log below, only B2B_DESTROY_CB
>
>     2022-08-09T11:44:27.788721+00:00
>      DBG:call_center:b2bl_callback_customer:  call (0x7f0a08e95a00)
>     has event 4,
>     2022-08-09T11:44:27.788767+00:00
>      DBG:call_center:b2bl_callback_customer: A delete in b2blogic,
>     call->state=6, 0x7f0a08e95a00
>
>
> Negative reply processed in _b2b_handle_reply, but the tuple->state is 
> not in B2B_BRIDGING_STATE and process_bridge_negreply doesn't called 
> with cbf(&cb_params, B2B_REJECT_CB);.
>
>     2022-08-09T11:44:27.769757+00:00 DBG:b2b_logic:_b2b_handle_reply:
>     Negative reply [486] - delete[0x7f0a08e95b28]
>     2022-08-09T11:44:27.769808+00:00  DBG:b2b_logic:b2b_mark_todel:
>     0x7f0a08e95b28
>
>
> P.S. But with message_flow_id uri in db (its do simple 200/bye on 
> invite) - all works fine , because negative reply is in  
> B2B_BRIDGING_STATE. But this is not a good way.
>
> Thank you very much.
>
> log:
>
>     [....]
>
>
> вт, 9 авг. 2022 г. в 11:36, Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>:
>
>     Hi,
>
>     In such a case, in `b2bl_callback_customer()` you should get a
>     B2B_REJECT_CB event.
>
>     Could you post here the logs in log_level 4 (debug) for your test
>     call ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 8/8/22 11:48 AM, Ryzhik Ivan wrote:
>>     Hi @All.
>>     I have a simple flow with 2 agents. When call entering queue
>>     by cc_handle_call("600")
>>     and the first agent rejects call (busy or decline) - queue also
>>     rejects call with same reason and does not proceed to second agent.
>>     I looked at sources  - negative replies processed only
>>     in B2B_BRIDGING_STATE. But for that time i have B2B_NOTDEF_STATE
>>     only.
>>     What am I doing wrong?
>>
>>
>>
>>
>>     _______________________________________________
>>     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/20220809/6f4b8723/attachment.html>

From artiom.druz at gmail.com  Wed Aug 10 02:44:46 2022
From: artiom.druz at gmail.com (Artiom Druz)
Date: Wed, 10 Aug 2022 07:44:46 +0500
Subject: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
In-Reply-To: <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>
References: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
 <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>
Message-ID: <CAEBOSMQZCFPmL1fckQ6w+tBHaoA=wF-ieY-S9T9B0EXfMiFCyw@mail.gmail.com>

Hi Bogdan.
I use trace_on parameter of proto_tls module and subroute for sending
messages to Homer.

I enabled trace_on parameter for proto_tcp module and now it works correct.
I'm not sure if this is the only fix I made because it may have been a
misconfiguration in the script logic.

вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu <bogdan at opensips.org>:

> Hi Artiom,
>
> Do you use any proto TCP or TLS specific tracing (like [1]), or only pure
> SIP TLS tracing ?
>
> [1]
> https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 7/25/22 11:20 AM, Artiom Druz wrote:
>
> Hello Everyone.
> I have a problem with monitoring SIPS/TLS based on tls_wolfssl module via
> proto_hep (target monitoring service is Homer 7).
> My opensips config works ok with SIP/UDP, but when I make a call via TLS
> (OpenSIPS convert TLS from VoIP provider to internal SIP/UDP software PBX)
> in dump file on Homer 7 side I see that all packets in HEP3 payload has
> this info:
>
> HEP3 Protocol
>     HEP Version: HEP3
>     HEP Packet Size (Bytes): 152
>     IP family: IPv4
>     Ingested Transport Protocol: IPv4
>     Source port: 0
>     Destination port: 0
>     Unix Timestamp: 1658731857
>     Timestamp µs: 106136
>     Application Protocol: Unknown Application Protocol
>     Capture Node ID: 1301
>     Source IPv4 address: 127.0.0.2
>     Destination IPv4 address: 127.0.0.2
>     Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>     Correlation ID: 350784072629638188
>
> Only unix timestamp and capture node id is correct.
> As you can see in encapsulated payload I have an error with read. What can
> be wrong?
>
> OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>
> _______________________________________________
> 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/20220810/4cb95e2c/attachment.html>

From bogdan at opensips.org  Wed Aug 10 07:49:48 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 10 Aug 2022 10:49:48 +0300
Subject: [OpenSIPS-Users] Bug on TLS Management Interface
In-Reply-To: <f66ea8e9-2233-4d72-a00c-816053e9be68@Spark>
References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark>
 <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark>
 <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org>
 <f66ea8e9-2233-4d72-a00c-816053e9be68@Spark>
Message-ID: <ec829521-ef18-69c2-2735-707b84ef6f77@opensips.org>

Hi Francisco,

Thanks for the info, it seems it was an issue with the validation 
regexp, see 
https://github.com/OpenSIPS/opensips-cp/commit/7558bc7e36c03293858c7086edfc724d56a2b9b4

So please update from GIT or TAR and give it a try (or simply do a 
manual change as per the diff link).

Let me know if it works now.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/9/22 11:46 PM, Francisco Neto wrote:
> Hi Bogdan-Andrei! How are you!
>
> Below is all the information that you have request ok, fell free to 
> ask me if you need something more!
>
> *version: opensips 3.2.5 (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.
> main.c compiled on with gcc 10
>
> *Opensips Control Panel 9.3.2*
>
> *Debian Version 11.2*
>
>
> Thank you very much for the help!
>
>
>
> Em 9 de ago. de 2022 05:39 -0300, Bogdan-Andrei Iancu 
> <bogdan at opensips.org>, escreveu:
>> Hi Francisco,
>>
>> I guess you are talking about managing certificates via the Control 
>> Panel, right ? if so, what version of OpenSIPS and OpenSIPS CP are 
>> you using ? Also, could you provide a screenshot of the add / update 
>> form, showing the issue? IF you have any sensitive data, please send 
>> the screenshot privately to me.
>>
>> Best regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>    https://www.opensips.org/events/Summit-2022Athens/
>> On 8/3/22 9:27 PM, Francisco Neto via Users wrote:
>>> Hi All!
>>>
>>> I’ve just installed open sips and everything is working ok, except 
>>> the TLS Management interface.
>>>
>>> When I try to add ou update any entry, it only accept “Network 
>>> Address” as “*”.
>>>
>>> If I type the IP address as x.x.x.x:port or “x.x.x.x:port” or 
>>> ‘x.x.x.x:port’ it always complain with the following message: Failed 
>>> to validate input for match_ip_address
>>>
>>> Can someone give me a tip of how should I write the IP address or if 
>>> it a bug?
>>>
>>> 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/20220810/245f0204/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DB7D58DE644C44489200EED54502B4A4.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220810/245f0204/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220810/245f0204/attachment-0003.png>

From bogdan at opensips.org  Wed Aug 10 07:53:40 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 10 Aug 2022 10:53:40 +0300
Subject: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
In-Reply-To: <CAEBOSMQZCFPmL1fckQ6w+tBHaoA=wF-ieY-S9T9B0EXfMiFCyw@mail.gmail.com>
References: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
 <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>
 <CAEBOSMQZCFPmL1fckQ6w+tBHaoA=wF-ieY-S9T9B0EXfMiFCyw@mail.gmail.com>
Message-ID: <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org>

Hi Artiom,

So you initially had only the trace_on set in the proto_tls module, 
generating some HEP packages which were not understood by HOMER, right ?

And after setting the trace_on in the proto_tcp module, the issue went 
away? but do you get HEP packages about about the TCP and TLS events in 
OpenSIPS - I'm asking as I have to say this part was not tested by some 
time :-/

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 5:44 AM, Artiom Druz wrote:
> Hi Bogdan.
> I use trace_on parameter of proto_tls module and subroute for sending 
> messages to Homer.
>
> I enabled trace_on parameter for proto_tcp module and now it works 
> correct. I'm not sure if this is the only fix I made because it may 
> have been a misconfiguration in the script logic.
>
> вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>:
>
>     Hi Artiom,
>
>     Do you use any proto TCP or TLS specific tracing (like [1]), or
>     only pure SIP TLS tracing ?
>
>     [1]
>     https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on
>     <https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on>
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 7/25/22 11:20 AM, Artiom Druz wrote:
>>     Hello Everyone.
>>     I have a problem with monitoring SIPS/TLS based on tls_wolfssl
>>     module via proto_hep (target monitoring service is Homer 7).
>>     My opensips config works ok with SIP/UDP, but when I make a call
>>     via TLS (OpenSIPS convert TLS from VoIP provider to internal
>>     SIP/UDP software PBX) in dump file on Homer 7 side I see that all
>>     packets in HEP3 payload has this info:
>>
>>     HEP3 Protocol
>>         HEP Version: HEP3
>>         HEP Packet Size (Bytes): 152
>>         IP family: IPv4
>>         Ingested Transport Protocol: IPv4
>>         Source port: 0
>>         Destination port: 0
>>         Unix Timestamp: 1658731857
>>         Timestamp µs: 106136
>>         Application Protocol: Unknown Application Protocol
>>         Capture Node ID: 1301
>>         Source IPv4 address: 127.0.0.2
>>         Destination IPv4 address: 127.0.0.2
>>         Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>>         Correlation ID: 350784072629638188
>>
>>     Only unix timestamp and capture node id is correct.
>>     As you can see in encapsulated payload I have an error with read.
>>     What can be wrong?
>>
>>     OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>>
>>     _______________________________________________
>>     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/20220810/7dd1fcd3/attachment.html>

From bullehs at gmail.com  Wed Aug 10 10:28:43 2022
From: bullehs at gmail.com (HS)
Date: Wed, 10 Aug 2022 15:28:43 +0500
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
Message-ID: <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>

Hi again Bogdan,

Thanks for responding. I *tried* to add support for aliases. What is
interesting is that the following snippet works fine on decline (but not
otherwise):

if (t_check_status("487|408|486|480|603")){
rewritehostport("INT.IP.XX.XXX:5091");
                t_relay();
                exit;

Any thoughts on how to fix please?

Thanks.

On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi HS,
>
> The aliases and late SDP negotiation has noting in common.
>
> And the mentioned script has no support for aliase - I guess you added
> such support ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 6/20/22 5:21 PM, HS wrote:
>
> Hi all.
>
> Just wondering if anyone has "dbaliases" working with the Late SDP
> negotiation script below:
>
> https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>
> If we call an alias, it works fine if the user is online. However, in case
> of offline users I want the call to be forwarded to another
> instance/server. If we use the ID (from subscriber table) calls are being
> forwarded. But not if we dial an alias.
>
> Appreciate the help.
>
> _______________________________________________
> 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/20220810/1ce58ba5/attachment.html>

From bogdan at opensips.org  Wed Aug 10 10:31:07 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 10 Aug 2022 13:31:07 +0300
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
Message-ID: <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>

Hi,

Could you share the cfg WITH the dbaliases support, to check where the 
alias lookup was inserted in the cfg logic ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 1:28 PM, HS wrote:
> Hi again Bogdan,
>
> Thanks for responding. I *tried* to add support for aliases. What is 
> interesting is that the following snippet works fine on decline (but 
> not otherwise):
>
> if (t_check_status("487|408|486|480|603")){
> rewritehostport("INT.IP.XX.XXX:5091");
>                 t_relay();
>                 exit;
>
> Any thoughts on how to fix please?
>
> Thanks.
>
> On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi HS,
>
>     The aliases and late SDP negotiation has noting in common.
>
>     And the mentioned script has no support for aliase - I guess you
>     added such support ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 6/20/22 5:21 PM, HS wrote:
>>     Hi all.
>>
>>     Just wondering if anyone has "dbaliases" working with the Late
>>     SDP negotiation script below:
>>
>>     https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>     <https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg>
>>
>>     If we call an alias, it works fine if the user is online.
>>     However, in case of offline users I want the call to be forwarded
>>     to another instance/server. If we use the ID (from subscriber
>>     table) calls are being forwarded. But not if we dial an alias.
>>
>>     Appreciate the help.
>>
>>     _______________________________________________
>>     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/20220810/1600b006/attachment-0001.html>

From bullehs at gmail.com  Wed Aug 10 10:51:53 2022
From: bullehs at gmail.com (HS)
Date: Wed, 10 Aug 2022 15:51:53 +0500
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
 <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
Message-ID: <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>

Hi again.

Thanks a lot for the quick response. My cfg is a bit of a trial-and-error
based, hence will email it (if that's ok). However, dbaliases support is
inserted as per default residential script:

if ($rU==NULL) {
# request with no Username in RURI
send_reply(484,"Address Incomplete");
exit;
}

# apply DB based aliases
alias_db_lookup("dbaliases");

Thanks again.

HS.

On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> Could you share the cfg WITH the dbaliases support, to check where the
> alias lookup was inserted in the cfg logic ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 1:28 PM, HS wrote:
>
> Hi again Bogdan,
>
> Thanks for responding. I *tried* to add support for aliases. What is
> interesting is that the following snippet works fine on decline (but not
> otherwise):
>
> if (t_check_status("487|408|486|480|603")){
> rewritehostport("INT.IP.XX.XXX:5091");
>                 t_relay();
>                 exit;
>
> Any thoughts on how to fix please?
>
> Thanks.
>
> On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi HS,
>>
>> The aliases and late SDP negotiation has noting in common.
>>
>> And the mentioned script has no support for aliase - I guess you added
>> such support ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>   https://www.opensips.org/events/Summit-2022Athens/
>>
>> On 6/20/22 5:21 PM, HS wrote:
>>
>> Hi all.
>>
>> Just wondering if anyone has "dbaliases" working with the Late SDP
>> negotiation script below:
>>
>> https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>
>> If we call an alias, it works fine if the user is online. However, in
>> case of offline users I want the call to be forwarded to another
>> instance/server. If we use the ID (from subscriber table) calls are being
>> forwarded. But not if we dial an alias.
>>
>> Appreciate the help.
>>
>> _______________________________________________
>> 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/20220810/ddf74fb1/attachment.html>

From bogdan at opensips.org  Wed Aug 10 12:25:24 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 10 Aug 2022 15:25:24 +0300
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
 <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
 <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>
Message-ID: <be32b1ff-a940-1741-935b-ae939eb8d960@opensips.org>

Hi,

So, your issue is that, after the call to user's device is rejected, and 
redirecting to VM (via failure route) you have some wrong RURI, right ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 1:51 PM, HS wrote:
> Hi again.
>
> Thanks a lot for the quick response. My cfg is a bit of a 
> trial-and-error based, hence will email it (if that's ok). However, 
> dbaliases support is inserted as per default residential script:
>
> if ($rU==NULL) {
> # request with no Username in RURI
> send_reply(484,"Address Incomplete");
> exit;
> }
>
> # apply DB based aliases
> alias_db_lookup("dbaliases");
>
> Thanks again.
>
> HS.
>
> On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi,
>
>     Could you share the cfg WITH the dbaliases support, to check where
>     the alias lookup was inserted in the cfg logic ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 8/10/22 1:28 PM, HS wrote:
>>     Hi again Bogdan,
>>
>>     Thanks for responding. I *tried* to add support for aliases. What
>>     is interesting is that the following snippet works fine on
>>     decline (but not otherwise):
>>
>>     if (t_check_status("487|408|486|480|603")){
>>     rewritehostport("INT.IP.XX.XXX:5091");
>>                     t_relay();
>>                     exit;
>>
>>     Any thoughts on how to fix please?
>>
>>     Thanks.
>>
>>     On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hi HS,
>>
>>         The aliases and late SDP negotiation has noting in common.
>>
>>         And the mentioned script has no support for aliase - I guess
>>         you added such support ?
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>         OpenSIPS Summit 27-30 Sept 2022, Athens
>>            https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>>
>>         On 6/20/22 5:21 PM, HS wrote:
>>>         Hi all.
>>>
>>>         Just wondering if anyone has "dbaliases" working with the
>>>         Late SDP negotiation script below:
>>>
>>>         https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>>         <https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg>
>>>
>>>         If we call an alias, it works fine if the user is online.
>>>         However, in case of offline users I want the call to be
>>>         forwarded to another instance/server. If we use the ID (from
>>>         subscriber table) calls are being forwarded. But not if we
>>>         dial an alias.
>>>
>>>         Appreciate the help.
>>>
>>>         _______________________________________________
>>>         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/20220810/9c9095de/attachment.html>

From andrey at voip.ninja  Wed Aug 10 12:57:11 2022
From: andrey at voip.ninja (Andrey F)
Date: Wed, 10 Aug 2022 15:57:11 +0300
Subject: [OpenSIPS-Users] 401 Unauthorized on BYE request
Message-ID: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>

Hello team!
Maybe anyone knows, is there a way to process a situation like this?

Scheme:
SIP Softphone A <-> OpenSIPS 3.1 <-> SIP Softphone B

Steps:
1) SIP softphone B sent BYE request;
2) SIP softphone A receives BYE and tried to authorize it (sent 401
response);
3) SIP softphone B receives 401 and generates a new BYE with credentials;
4) OpenSIPS did not pass second BYE request, because dialog was terminated
on first BYE request.

As far as I understand, SIP dialog on opensips is automatically destroyed
after the first BYE was received.
>From https://opensips.org/docs/modules/3.1.x/dialog.html:

1.2. How it works
...
The dialog is automatically destroyed when a “BYE” is received. In case of
no “BYE”, the dialog lifetime is controlled via the default timeout (see
“default_timeout” - default_timeout
<https://opensips.org/docs/modules/3.1.x/dialog.html#param_default_timeout>)
and custom timeout (see “$DLG_timeout” - $DLG_timeout
<https://opensips.org/docs/modules/3.1.x/dialog.html#pv_DLG_timeout>).


The second BYE witch credentials arrived to opensips very quickly (just a
few ms).

My problem is that second BYE can not pass these procedures:
1) *if (topology_hiding_match())*
2)* if (t_check_trans())*


On first BYE I see this in logs, it is matched.
1)
*if (topology_hiding_match()) logs:*

DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
XXXXXXXXX
DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
DBG:dialog:lookup_dlg: dialog id=1424242860 found on entry 3032
DBG:core:parse_headers: flags=58
DBG:core:parse_to_param: tag=YYYYYYY
DBG:core:parse_to_param: end of header reached, state=11
DBG:core:_parse_to: end of header reached, state=29
DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
DBG:dialog:next_state_dlg: dialog 0x7f16b2b95cf8 changed from state 4 to
state 5, due event 7
DBG:dialog:init_dlg_term_reason: Setting DLG term reason to [Upstream BYE]


On second BYE I see this in logs, it is not matched.
2) *if (topology_hiding_match()) logs: *Dialog can not be matched

DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
XXXXXXXXX
DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
DBG:dialog:lookup_dlg: no dialog id=1424242860 found on entry 3032
DBG:dialog:dlg_onroute: unable to find dialog for BYE with route param
'XXXXXXXXX'
DBG:core:parse_headers: flags=58
DBG:core:parse_to_param: tag=TTTTTT
DBG:core:parse_to_param: end of header reached, state=11
DBG:core:_parse_to: end of header reached, state=29
DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
DBG:dialog:get_dlg: input ci=<CCCCCCCCCCC>(37), tt=<TTTTTT>(15),
ft=<FFFFFFFFF>(14)
DBG:dialog:get_dlg: no dialog callid='CCCCCCCCCCC' found
DBG:dialog:dlg_onroute: Callid 'CCCCCCCCCCC' not found


3)* if (t_check_trans()) **logs:* transaction can not be matched

DBG:core:parse_headers: flags=78
DBG:tm:t_lookup_request: start searching: hash=44043, isACK=0
DBG:tm:matching_3261: RFC3261 transaction matching failed
DBG:tm:t_lookup_request: no transaction found
DBG:core:parse_headers: flags=ffffffffffffffff


Finally, maybe anyone knows how to resolve this problem?
Thank you!

--
Best regards,
Andrey F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220810/e479dedb/attachment.html>

From bullehs at gmail.com  Wed Aug 10 13:20:04 2022
From: bullehs at gmail.com (HS)
Date: Wed, 10 Aug 2022 18:20:04 +0500
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <be32b1ff-a940-1741-935b-ae939eb8d960@opensips.org>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
 <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
 <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>
 <be32b1ff-a940-1741-935b-ae939eb8d960@opensips.org>
Message-ID: <CA+PgBoZNEz6mFzjpoB8jB+H7WYBOHJaWyv=+craD=Q1ALN1Mqw@mail.gmail.com>

Hi again.

Thanks. Exact opposite :) When using an alias, after the call to users
device is rejected, it is redirecting successfully to VM. However, in all
other cases it doesn't redirect to VM (when using an alias) and times out.
On the other hand, everything works as per snippet if using subscriber
table details.

Does that make sense please?

Thanks.

On Wed, Aug 10, 2022 at 5:25 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> So, your issue is that, after the call to user's device is rejected, and
> redirecting to VM (via failure route) you have some wrong RURI, right ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 1:51 PM, HS wrote:
>
> Hi again.
>
> Thanks a lot for the quick response. My cfg is a bit of a trial-and-error
> based, hence will email it (if that's ok). However, dbaliases support is
> inserted as per default residential script:
>
> if ($rU==NULL) {
> # request with no Username in RURI
> send_reply(484,"Address Incomplete");
> exit;
> }
>
> # apply DB based aliases
> alias_db_lookup("dbaliases");
>
> Thanks again.
>
> HS.
>
> On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi,
>>
>> Could you share the cfg WITH the dbaliases support, to check where the
>> alias lookup was inserted in the cfg logic ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>   https://www.opensips.org/events/Summit-2022Athens/
>>
>> On 8/10/22 1:28 PM, HS wrote:
>>
>> Hi again Bogdan,
>>
>> Thanks for responding. I *tried* to add support for aliases. What is
>> interesting is that the following snippet works fine on decline (but not
>> otherwise):
>>
>> if (t_check_status("487|408|486|480|603")){
>> rewritehostport("INT.IP.XX.XXX:5091");
>>                 t_relay();
>>                 exit;
>>
>> Any thoughts on how to fix please?
>>
>> Thanks.
>>
>> On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi HS,
>>>
>>> The aliases and late SDP negotiation has noting in common.
>>>
>>> And the mentioned script has no support for aliase - I guess you added
>>> such support ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>>   https://www.opensips.org/events/Summit-2022Athens/
>>>
>>> On 6/20/22 5:21 PM, HS wrote:
>>>
>>> Hi all.
>>>
>>> Just wondering if anyone has "dbaliases" working with the Late SDP
>>> negotiation script below:
>>>
>>> https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>>
>>> If we call an alias, it works fine if the user is online. However, in
>>> case of offline users I want the call to be forwarded to another
>>> instance/server. If we use the ID (from subscriber table) calls are being
>>> forwarded. But not if we dial an alias.
>>>
>>> Appreciate the help.
>>>
>>> _______________________________________________
>>> 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/20220810/846afccc/attachment-0001.html>

From bogdan at opensips.org  Wed Aug 10 13:49:04 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 10 Aug 2022 16:49:04 +0300
Subject: [OpenSIPS-Users] 401 Unauthorized on BYE request
In-Reply-To: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
References: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
Message-ID: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>

Hi Andrey,

What you say is correct and unfortunately I have the trick here for you 
- indeed, the dialog structure is destroyed upon the first BYE (on its 
reply actually), so the second one will not match the dialog.... :-|

Maybe we can have a feature request to actually have the dialog 
destroyed with a bit of a delay (similar to the transactions), but this 
is not so easy to implement.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 3:57 PM, Andrey F wrote:
> Hello team!
> Maybe anyone knows, is there a way to process a situation like this?
>
> Scheme:
> SIP Softphone A <-> OpenSIPS 3.1 <-> SIP Softphone B
>
> Steps:
> 1) SIP softphone B sent BYE request;
> 2) SIP softphone A receives BYE and tried to authorize it (sent 401 
> response);
> 3) SIP softphone B receives 401 and generates a new BYE with credentials;
> 4) OpenSIPS did not pass second BYE request, because dialog was 
> terminated on first BYE request.
>
> As far as I understand, SIP dialog on opensips is automatically 
> destroyed after the first BYE was received.
> From https://opensips.org/docs/modules/3.1.x/dialog.html 
> <https://opensips.org/docs/modules/3.1.x/dialog.html>:
>
>
>         1.2. How it works
>
>     ...
>     The dialog is automatically destroyed when a“BYE”is received. In
>     case of no“BYE”, the dialog lifetime is controlled via the default
>     timeout (see“default_timeout”-default_timeout
>     <https://opensips.org/docs/modules/3.1.x/dialog.html#param_default_timeout>)
>     and custom timeout (see“$DLG_timeout”-$DLG_timeout
>     <https://opensips.org/docs/modules/3.1.x/dialog.html#pv_DLG_timeout>).
>
>
>
> The second BYE witch credentials arrived to opensips very quickly 
> (just a few ms).
>
> My problem is that second BYE can not pass these procedures:
> 1) *if (topology_hiding_match())*
> 2)* if (t_check_trans())*
>
>
> On first BYE I see this in logs, it is matched.
> 1) *if (topology_hiding_match()) logs:
> *
>
>     DBG:dialog:api_match_dialog: We found DID param in R-URI with
>     value of XXXXXXXXX
>     DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
>     DBG:dialog:lookup_dlg: dialog id=1424242860 found on entry 3032
>     DBG:core:parse_headers: flags=58
>     DBG:core:parse_to_param: tag=YYYYYYY
>     DBG:core:parse_to_param: end of header reached, state=11
>     DBG:core:_parse_to: end of header reached, state=29
>     DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1
>     <http://sip:1 at 1.1.1.1:1/>}
>     DBG:dialog:next_state_dlg: dialog 0x7f16b2b95cf8 changed from
>     state 4 to state 5, due event 7
>     DBG:dialog:init_dlg_term_reason: Setting DLG term reason to
>     [Upstream BYE]
>
>
> On second BYE I see this in logs, it is not matched.
> 2) *if (topology_hiding_match()) logs: *Dialog can not be matched
>
>     DBG:dialog:api_match_dialog: We found DID param in R-URI with
>     value of XXXXXXXXX
>     DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
>     DBG:dialog:lookup_dlg: no dialog id=1424242860 found on entry 3032
>     DBG:dialog:dlg_onroute: unable to find dialog for BYE with route
>     param 'XXXXXXXXX'
>     DBG:core:parse_headers: flags=58
>     DBG:core:parse_to_param: tag=TTTTTT
>     DBG:core:parse_to_param: end of header reached, state=11
>     DBG:core:_parse_to: end of header reached, state=29
>     DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1
>     <http://sip:1 at 1.1.1.1:1/>}
>     DBG:dialog:get_dlg: input ci=<CCCCCCCCCCC>(37), tt=<TTTTTT>(15),
>     ft=<FFFFFFFFF>(14)
>     DBG:dialog:get_dlg: no dialog callid='CCCCCCCCCCC' found
>     DBG:dialog:dlg_onroute: Callid 'CCCCCCCCCCC' not found
>
> *
> *
> 3)* if (t_check_trans()) **logs:***transaction can not be matched
>
>     DBG:core:parse_headers: flags=78
>     DBG:tm:t_lookup_request: start searching: hash=44043, isACK=0
>     DBG:tm:matching_3261: RFC3261 transaction matching failed
>     DBG:tm:t_lookup_request: no transaction found
>     DBG:core:parse_headers: flags=ffffffffffffffff
>
>
> Finally, maybe anyone knows how to resolve this problem?
> Thank you!
>
> --
> Best regards,
> Andrey F
>
> _______________________________________________
> 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/20220810/83f156cc/attachment.html>

From kurgan-rus at inbox.ru  Wed Aug 10 17:39:55 2022
From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=)
Date: Wed, 10 Aug 2022 20:39:55 +0300
Subject: [OpenSIPS-Users] =?utf-8?q?401_Unauthorized_on_BYE_request?=
In-Reply-To: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
References: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
 <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
Message-ID: <1660153195.783883178@f174.i.mail.ru>


Hi list,
 
is it normal at all — to authenticate BYE requests?
 
I’ve checked RFC 3261 now, but haven’t found anything corresponding to this.
Neither if it’s normal, nor if it’s not normal.
 
-----------------------------------------------
BR, Alexey
https://alexeyka.zantsev.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220810/a1ea294a/attachment.html>

From andrey at voip.ninja  Wed Aug 10 21:04:02 2022
From: andrey at voip.ninja (Andrey F)
Date: Thu, 11 Aug 2022 00:04:02 +0300
Subject: [OpenSIPS-Users] 401 Unauthorized on BYE request
In-Reply-To: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
References: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
 <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
Message-ID: <CADtVBRRvG0XS5r-UHbnU2e037ejOYM=o5GdYcvwxLzX88_815A@mail.gmail.com>

Hello Bogdan!
Thank you very much for your quick reply.

ср, 10 авг. 2022 г. в 16:49, Bogdan-Andrei Iancu <bogdan at opensips.org>:

> Hi Andrey,
>
> What you say is correct and unfortunately I have the trick here for you -
> indeed, the dialog structure is destroyed upon the first BYE (on its reply
> actually), so the second one will not match the dialog.... :-|
>
> Maybe we can have a feature request to actually have the dialog destroyed
> with a bit of a delay (similar to the transactions), but this is not so
> easy to implement.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 3:57 PM, Andrey F wrote:
>
> Hello team!
> Maybe anyone knows, is there a way to process a situation like this?
>
> Scheme:
> SIP Softphone A <-> OpenSIPS 3.1 <-> SIP Softphone B
>
> Steps:
> 1) SIP softphone B sent BYE request;
> 2) SIP softphone A receives BYE and tried to authorize it (sent 401
> response);
> 3) SIP softphone B receives 401 and generates a new BYE with credentials;
> 4) OpenSIPS did not pass second BYE request, because dialog was terminated
> on first BYE request.
>
> As far as I understand, SIP dialog on opensips is automatically destroyed
> after the first BYE was received.
> From https://opensips.org/docs/modules/3.1.x/dialog.html:
>
> 1.2. How it works
> ...
> The dialog is automatically destroyed when a “BYE” is received. In case
> of no “BYE”, the dialog lifetime is controlled via the default timeout
> (see “default_timeout” - default_timeout
> <https://opensips.org/docs/modules/3.1.x/dialog.html#param_default_timeout>)
> and custom timeout (see “$DLG_timeout” - $DLG_timeout
> <https://opensips.org/docs/modules/3.1.x/dialog.html#pv_DLG_timeout>).
>
>
> The second BYE witch credentials arrived to opensips very quickly (just a
> few ms).
>
> My problem is that second BYE can not pass these procedures:
> 1) *if (topology_hiding_match())*
> 2)* if (t_check_trans())*
>
>
> On first BYE I see this in logs, it is matched.
> 1)
> *if (topology_hiding_match()) logs: *
>
> DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
> XXXXXXXXX
> DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
> DBG:dialog:lookup_dlg: dialog id=1424242860 found on entry 3032
> DBG:core:parse_headers: flags=58
> DBG:core:parse_to_param: tag=YYYYYYY
> DBG:core:parse_to_param: end of header reached, state=11
> DBG:core:_parse_to: end of header reached, state=29
> DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
> DBG:dialog:next_state_dlg: dialog 0x7f16b2b95cf8 changed from state 4 to
> state 5, due event 7
> DBG:dialog:init_dlg_term_reason: Setting DLG term reason to [Upstream BYE]
>
>
> On second BYE I see this in logs, it is not matched.
> 2) *if (topology_hiding_match()) logs: *Dialog can not be matched
>
> DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
> XXXXXXXXX
> DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
> DBG:dialog:lookup_dlg: no dialog id=1424242860 found on entry 3032
> DBG:dialog:dlg_onroute: unable to find dialog for BYE with route param
> 'XXXXXXXXX'
> DBG:core:parse_headers: flags=58
> DBG:core:parse_to_param: tag=TTTTTT
> DBG:core:parse_to_param: end of header reached, state=11
> DBG:core:_parse_to: end of header reached, state=29
> DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
> DBG:dialog:get_dlg: input ci=<CCCCCCCCCCC>(37), tt=<TTTTTT>(15),
> ft=<FFFFFFFFF>(14)
> DBG:dialog:get_dlg: no dialog callid='CCCCCCCCCCC' found
> DBG:dialog:dlg_onroute: Callid 'CCCCCCCCCCC' not found
>
>
> 3)* if (t_check_trans()) **logs:* transaction can not be matched
>
> DBG:core:parse_headers: flags=78
> DBG:tm:t_lookup_request: start searching: hash=44043, isACK=0
> DBG:tm:matching_3261: RFC3261 transaction matching failed
> DBG:tm:t_lookup_request: no transaction found
> DBG:core:parse_headers: flags=ffffffffffffffff
>
>
> Finally, maybe anyone knows how to resolve this problem?
> Thank you!
>
> --
> Best regards,
> Andrey F
>
> _______________________________________________
> 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/20220811/5bbd1ca0/attachment-0001.html>

From andrey at voip.ninja  Thu Aug 11 05:50:04 2022
From: andrey at voip.ninja (Andrey F)
Date: Thu, 11 Aug 2022 08:50:04 +0300
Subject: [OpenSIPS-Users] 401 Unauthorized on BYE request
In-Reply-To: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
References: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
 <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
Message-ID: <CADtVBRQ7NgeXV356sbqa9_-jjzDyOCm2HZLNDuO_iKj7f=hOHg@mail.gmail.com>

Hello Alexey. Yes, it is not usual SIP behaviour.
As I can see, for example, 3CX system can do this (separate option to
authorize incoming REGISTER, INVITE and BYE requests).

ср, 10 авг. 2022 г. в 16:49, Bogdan-Andrei Iancu <bogdan at opensips.org>:

> Hi Andrey,
>
> What you say is correct and unfortunately I have the trick here for you -
> indeed, the dialog structure is destroyed upon the first BYE (on its reply
> actually), so the second one will not match the dialog.... :-|
>
> Maybe we can have a feature request to actually have the dialog destroyed
> with a bit of a delay (similar to the transactions), but this is not so
> easy to implement.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 3:57 PM, Andrey F wrote:
>
> Hello team!
> Maybe anyone knows, is there a way to process a situation like this?
>
> Scheme:
> SIP Softphone A <-> OpenSIPS 3.1 <-> SIP Softphone B
>
> Steps:
> 1) SIP softphone B sent BYE request;
> 2) SIP softphone A receives BYE and tried to authorize it (sent 401
> response);
> 3) SIP softphone B receives 401 and generates a new BYE with credentials;
> 4) OpenSIPS did not pass second BYE request, because dialog was terminated
> on first BYE request.
>
> As far as I understand, SIP dialog on opensips is automatically destroyed
> after the first BYE was received.
> From https://opensips.org/docs/modules/3.1.x/dialog.html:
>
> 1.2. How it works
> ...
> The dialog is automatically destroyed when a “BYE” is received. In case
> of no “BYE”, the dialog lifetime is controlled via the default timeout
> (see “default_timeout” - default_timeout
> <https://opensips.org/docs/modules/3.1.x/dialog.html#param_default_timeout>)
> and custom timeout (see “$DLG_timeout” - $DLG_timeout
> <https://opensips.org/docs/modules/3.1.x/dialog.html#pv_DLG_timeout>).
>
>
> The second BYE witch credentials arrived to opensips very quickly (just a
> few ms).
>
> My problem is that second BYE can not pass these procedures:
> 1) *if (topology_hiding_match())*
> 2)* if (t_check_trans())*
>
>
> On first BYE I see this in logs, it is matched.
> 1)
> *if (topology_hiding_match()) logs: *
>
> DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
> XXXXXXXXX
> DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
> DBG:dialog:lookup_dlg: dialog id=1424242860 found on entry 3032
> DBG:core:parse_headers: flags=58
> DBG:core:parse_to_param: tag=YYYYYYY
> DBG:core:parse_to_param: end of header reached, state=11
> DBG:core:_parse_to: end of header reached, state=29
> DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
> DBG:dialog:next_state_dlg: dialog 0x7f16b2b95cf8 changed from state 4 to
> state 5, due event 7
> DBG:dialog:init_dlg_term_reason: Setting DLG term reason to [Upstream BYE]
>
>
> On second BYE I see this in logs, it is not matched.
> 2) *if (topology_hiding_match()) logs: *Dialog can not be matched
>
> DBG:dialog:api_match_dialog: We found DID param in R-URI with value of
> XXXXXXXXX
> DBG:dialog:dlg_onroute: route param is 'XXXXXXXXX' (len=12)
> DBG:dialog:lookup_dlg: no dialog id=1424242860 found on entry 3032
> DBG:dialog:dlg_onroute: unable to find dialog for BYE with route param
> 'XXXXXXXXX'
> DBG:core:parse_headers: flags=58
> DBG:core:parse_to_param: tag=TTTTTT
> DBG:core:parse_to_param: end of header reached, state=11
> DBG:core:_parse_to: end of header reached, state=29
> DBG:core:_parse_to: display={}, ruri={sip:1 at 1.1.1.1:1}
> DBG:dialog:get_dlg: input ci=<CCCCCCCCCCC>(37), tt=<TTTTTT>(15),
> ft=<FFFFFFFFF>(14)
> DBG:dialog:get_dlg: no dialog callid='CCCCCCCCCCC' found
> DBG:dialog:dlg_onroute: Callid 'CCCCCCCCCCC' not found
>
>
> 3)* if (t_check_trans()) **logs:* transaction can not be matched
>
> DBG:core:parse_headers: flags=78
> DBG:tm:t_lookup_request: start searching: hash=44043, isACK=0
> DBG:tm:matching_3261: RFC3261 transaction matching failed
> DBG:tm:t_lookup_request: no transaction found
> DBG:core:parse_headers: flags=ffffffffffffffff
>
>
> Finally, maybe anyone knows how to resolve this problem?
> Thank you!
>
> --
> Best regards,
> Andrey F
>
> _______________________________________________
> 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/20220811/a727461b/attachment.html>

From artiom.druz at gmail.com  Thu Aug 11 06:05:09 2022
From: artiom.druz at gmail.com (Artiom Druz)
Date: Thu, 11 Aug 2022 11:05:09 +0500
Subject: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
In-Reply-To: <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org>
References: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
 <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>
 <CAEBOSMQZCFPmL1fckQ6w+tBHaoA=wF-ieY-S9T9B0EXfMiFCyw@mail.gmail.com>
 <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org>
Message-ID: <CAEBOSMS56OecT0HtLL50jNRMV9PMB+WqA3Y_pWD5Bn0iF1GY7A@mail.gmail.com>

Hi Bogdan.
For now I see that Homer is catching info correctly, and I can see what was
happened inside TLS calls in Homer's web-interface.

ср, 10 авг. 2022 г., 12:53 Bogdan-Andrei Iancu <bogdan at opensips.org>:

> Hi Artiom,
>
> So you initially had only the trace_on set in the proto_tls module,
> generating some HEP packages which were not understood by HOMER, right ?
>
> And after setting the trace_on in the proto_tcp module, the issue went
> away? but do you get HEP packages about about the TCP and TLS events in
> OpenSIPS - I'm asking as I have to say this part was not tested by some
> time :-/
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 5:44 AM, Artiom Druz wrote:
>
> Hi Bogdan.
> I use trace_on parameter of proto_tls module and subroute for sending
> messages to Homer.
>
> I enabled trace_on parameter for proto_tcp module and now it works
> correct. I'm not sure if this is the only fix I made because it may have
> been a misconfiguration in the script logic.
>
> вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu <bogdan at opensips.org>:
>
>> Hi Artiom,
>>
>> Do you use any proto TCP or TLS specific tracing (like [1]), or only pure
>> SIP TLS tracing ?
>>
>> [1]
>> https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>   https://www.opensips.org/events/Summit-2022Athens/
>>
>> On 7/25/22 11:20 AM, Artiom Druz wrote:
>>
>> Hello Everyone.
>> I have a problem with monitoring SIPS/TLS based on tls_wolfssl module via
>> proto_hep (target monitoring service is Homer 7).
>> My opensips config works ok with SIP/UDP, but when I make a call via TLS
>> (OpenSIPS convert TLS from VoIP provider to internal SIP/UDP software PBX)
>> in dump file on Homer 7 side I see that all packets in HEP3 payload has
>> this info:
>>
>> HEP3 Protocol
>>     HEP Version: HEP3
>>     HEP Packet Size (Bytes): 152
>>     IP family: IPv4
>>     Ingested Transport Protocol: IPv4
>>     Source port: 0
>>     Destination port: 0
>>     Unix Timestamp: 1658731857
>>     Timestamp µs: 106136
>>     Application Protocol: Unknown Application Protocol
>>     Capture Node ID: 1301
>>     Source IPv4 address: 127.0.0.2
>>     Destination IPv4 address: 127.0.0.2
>>     Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>>     Correlation ID: 350784072629638188
>>
>> Only unix timestamp and capture node id is correct.
>> As you can see in encapsulated payload I have an error with read. What
>> can be wrong?
>>
>> OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>>
>> _______________________________________________
>> 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/20220811/c5b3f766/attachment-0001.html>

From bogdan at opensips.org  Thu Aug 11 12:10:43 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 11 Aug 2022 15:10:43 +0300
Subject: [OpenSIPS-Users] OpenSIPS Summit 2022 - Speaker's lineup
Message-ID: <b3dee350-fe81-9c4c-9989-e6312a86454a@opensips.org>

<http://www.opensips.org/events/Summit-2022Athens>


  OpenSIPS Summit


            Sept 27th - 30th, 2022, Athens, Greece


*Speaker's lineup & Schedule
*

We bring here the list of speakers and papers 
<https://www.opensips.org/events/Summit-2022Athens/#schedules> - great 
speakers presenting great topics to share experience and knowledge to a 
great audience. Explore here all the details...

<https://www.opensips.org/events/Summit-2022Athens/#schedules>

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

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

**


	
	

	
	


-- 
Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com

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

From bogdan at opensips.org  Thu Aug 11 15:02:41 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 11 Aug 2022 18:02:41 +0300
Subject: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl
In-Reply-To: <CAEBOSMS56OecT0HtLL50jNRMV9PMB+WqA3Y_pWD5Bn0iF1GY7A@mail.gmail.com>
References: <CAEBOSMT3w-sa-XYgL69idNeh7eAd0F3ySdPzVUpxGcmn=SH5_Q@mail.gmail.com>
 <b310a1e0-a638-ffea-e5f9-0b71af0bb761@opensips.org>
 <CAEBOSMQZCFPmL1fckQ6w+tBHaoA=wF-ieY-S9T9B0EXfMiFCyw@mail.gmail.com>
 <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org>
 <CAEBOSMS56OecT0HtLL50jNRMV9PMB+WqA3Y_pWD5Bn0iF1GY7A@mail.gmail.com>
Message-ID: <37eb19f4-cb05-3055-444c-78781d133177@opensips.org>

Right, and that's good :). Still I'm trying to understand what were the 
settings that were not properly working - trace_on only in TLS, but not 
in TCP? or?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/11/22 9:05 AM, Artiom Druz wrote:
> Hi Bogdan.
> For now I see that Homer is catching info correctly, and I can see 
> what was happened inside TLS calls in Homer's web-interface.
>
> ср, 10 авг. 2022 г., 12:53 Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>>:
>
>     Hi Artiom,
>
>     So you initially had only the trace_on set in the proto_tls
>     module, generating some HEP packages which were not understood by
>     HOMER, right ?
>
>     And after setting the trace_on in the proto_tcp module, the issue
>     went away? but do you get HEP packages about about the TCP and TLS
>     events in OpenSIPS - I'm asking as I have to say this part was not
>     tested by some time :-/
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 8/10/22 5:44 AM, Artiom Druz wrote:
>>     Hi Bogdan.
>>     I use trace_on parameter of proto_tls module and subroute for
>>     sending messages to Homer.
>>
>>     I enabled trace_on parameter for proto_tcp module and now it
>>     works correct. I'm not sure if this is the only fix I made
>>     because it may have been a misconfiguration in the script logic.
>>
>>     вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>>:
>>
>>         Hi Artiom,
>>
>>         Do you use any proto TCP or TLS specific tracing (like [1]),
>>         or only pure SIP TLS tracing ?
>>
>>         [1]
>>         https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on
>>         <https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on>
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>         OpenSIPS Summit 27-30 Sept 2022, Athens
>>            https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>>
>>         On 7/25/22 11:20 AM, Artiom Druz wrote:
>>>         Hello Everyone.
>>>         I have a problem with monitoring SIPS/TLS based on
>>>         tls_wolfssl module via proto_hep (target monitoring service
>>>         is Homer 7).
>>>         My opensips config works ok with SIP/UDP, but when I make a
>>>         call via TLS (OpenSIPS convert TLS from VoIP provider to
>>>         internal SIP/UDP software PBX) in dump file on Homer 7 side
>>>         I see that all packets in HEP3 payload has this info:
>>>
>>>         HEP3 Protocol
>>>             HEP Version: HEP3
>>>             HEP Packet Size (Bytes): 152
>>>             IP family: IPv4
>>>             Ingested Transport Protocol: IPv4
>>>             Source port: 0
>>>             Destination port: 0
>>>             Unix Timestamp: 1658731857
>>>             Timestamp µs: 106136
>>>             Application Protocol: Unknown Application Protocol
>>>             Capture Node ID: 1301
>>>             Source IPv4 address: 127.0.0.2
>>>             Destination IPv4 address: 127.0.0.2
>>>             Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
>>>             Correlation ID: 350784072629638188
>>>
>>>         Only unix timestamp and capture node id is correct.
>>>         As you can see in encapsulated payload I have an error with
>>>         read. What can be wrong?
>>>
>>>         OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.
>>>
>>>         _______________________________________________
>>>         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/20220811/cd836394/attachment.html>

From bogdan at opensips.org  Thu Aug 11 15:24:23 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 11 Aug 2022 18:24:23 +0300
Subject: [OpenSIPS-Users] 401 Unauthorized on BYE request
In-Reply-To: <1660153195.783883178@f174.i.mail.ru>
References: <CADtVBRQNO0pYD7NQM5bbd11z8JPqeY01NQSV7=aT1+3D_y8=oQ@mail.gmail.com>
 <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org>
 <1660153195.783883178@f174.i.mail.ru>
Message-ID: <e9e0e00b-d2b2-0b9f-fa0b-2a59f36ce561@opensips.org>

Hi Alexey,

The RFC3261 says that any requests with reply (so no ACK) can/may be 
subject to authentication. So SIP-wise, it is fine. In the real-life it 
is quite unusual, still not SF :).

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 8:39 PM, Alexey Kazantsev via Users wrote:
> Hi list,
> is it normal at all — to authenticate BYE requests?
> I’ve checked RFC 3261 now, but haven’t found anything corresponding to 
> this.
> Neither if it’s normal, nor if it’s not normal.
> -----------------------------------------------
> 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/20220811/17fd7fe3/attachment-0001.html>

From bogdan at opensips.org  Thu Aug 11 16:02:10 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 11 Aug 2022 19:02:10 +0300
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <CA+PgBoZNEz6mFzjpoB8jB+H7WYBOHJaWyv=+craD=Q1ALN1Mqw@mail.gmail.com>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
 <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
 <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>
 <be32b1ff-a940-1741-935b-ae939eb8d960@opensips.org>
 <CA+PgBoZNEz6mFzjpoB8jB+H7WYBOHJaWyv=+craD=Q1ALN1Mqw@mail.gmail.com>
Message-ID: <cf1c211f-abcd-9469-828c-2be97075377f@opensips.org>

Hi,

By "in all other cases" you mean "timeout upon ringing" ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 4:20 PM, HS wrote:
> Hi again.
>
> Thanks. Exact opposite :) When using an alias, after the call to users 
> device is rejected, it is redirecting successfully to VM. However, in 
> all other cases it doesn't redirect to VM (when using an alias) and 
> times out. On the other hand, everything works as per snippet if using 
> subscriber table details.
>
> Does that make sense please?
>
> Thanks.
>
> On Wed, Aug 10, 2022 at 5:25 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>     Hi,
>
>     So, your issue is that, after the call to user's device is
>     rejected, and redirecting to VM (via failure route) you have some
>     wrong RURI, right ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>     OpenSIPS Summit 27-30 Sept 2022, Athens
>        https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>
>     On 8/10/22 1:51 PM, HS wrote:
>>     Hi again.
>>
>>     Thanks a lot for the quick response. My cfg is a bit of a
>>     trial-and-error based, hence will email it (if that's ok).
>>     However, dbaliases support is inserted as per default residential
>>     script:
>>
>>     if ($rU==NULL) {
>>     # request with no Username in RURI
>>     send_reply(484,"Address Incomplete");
>>     exit;
>>     }
>>
>>     # apply DB based aliases
>>     alias_db_lookup("dbaliases");
>>
>>     Thanks again.
>>
>>     HS.
>>
>>     On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>
>>         Hi,
>>
>>         Could you share the cfg WITH the dbaliases support, to check
>>         where the alias lookup was inserted in the cfg logic ?
>>
>>         Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>         OpenSIPS Summit 27-30 Sept 2022, Athens
>>            https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>>
>>         On 8/10/22 1:28 PM, HS wrote:
>>>         Hi again Bogdan,
>>>
>>>         Thanks for responding. I *tried* to add support for aliases.
>>>         What is interesting is that the following snippet works fine
>>>         on decline (but not otherwise):
>>>
>>>         if (t_check_status("487|408|486|480|603")){
>>>         rewritehostport("INT.IP.XX.XXX:5091");
>>>                         t_relay();
>>>                         exit;
>>>
>>>         Any thoughts on how to fix please?
>>>
>>>         Thanks.
>>>
>>>         On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu
>>>         <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>>>
>>>             Hi HS,
>>>
>>>             The aliases and late SDP negotiation has noting in common.
>>>
>>>             And the mentioned script has no support for aliase - I
>>>             guess you added such support ?
>>>
>>>             Regards,
>>>
>>>             Bogdan-Andrei Iancu
>>>
>>>             OpenSIPS Founder and Developer
>>>                https://www.opensips-solutions.com  <https://www.opensips-solutions.com>
>>>             OpenSIPS Summit 27-30 Sept 2022, Athens
>>>                https://www.opensips.org/events/Summit-2022Athens/  <https://www.opensips.org/events/Summit-2022Athens/>
>>>
>>>             On 6/20/22 5:21 PM, HS wrote:
>>>>             Hi all.
>>>>
>>>>             Just wondering if anyone has "dbaliases" working with
>>>>             the Late SDP negotiation script below:
>>>>
>>>>             https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>>>             <https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg>
>>>>
>>>>             If we call an alias, it works fine if the user is
>>>>             online. However, in case of offline users I want the
>>>>             call to be forwarded to another instance/server. If we
>>>>             use the ID (from subscriber table) calls are being
>>>>             forwarded. But not if we dial an alias.
>>>>
>>>>             Appreciate the help.
>>>>
>>>>             _______________________________________________
>>>>             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/20220811/61197669/attachment.html>

From vadimd333 at me.com  Mon Aug  8 18:49:37 2022
From: vadimd333 at me.com (Vadim Dumalekov)
Date: Mon, 8 Aug 2022 21:49:37 +0300
Subject: [OpenSIPS-Users] SRTP connect error
Message-ID: <B7AE9C4D-C56F-4317-8B3F-9CE0E3F1CEE4@me.com>

Hello!

I have a problem with WebRTC-clients. In the log file i see the following line:

/usr/sbin/opensips[10580]: ERROR:rtpengine:parse_flags: error processing flag `trust-address': no more memory



Regards, Vadim!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220808/0f84c72b/attachment-0001.html>

From bogdan at opensips.org  Thu Aug 11 15:59:45 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 11 Aug 2022 18:59:45 +0300
Subject: [OpenSIPS-Users] Bug on TLS Management Interface
In-Reply-To: <d8ec8b2d-9ffb-4741-a3b4-63ff4f662376@Spark>
References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark>
 <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark>
 <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org>
 <f66ea8e9-2233-4d72-a00c-816053e9be68@Spark>
 <ec829521-ef18-69c2-2735-707b84ef6f77@opensips.org>
 <d8ec8b2d-9ffb-4741-a3b4-63ff4f662376@Spark>
Message-ID: <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org>

Hi Francisco,

So, if you use wildcard for match_sip_domain in the client TLS domain, 
doesn't work for you ?

Regards.

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 5:03 PM, Francisco Neto wrote:
> Hi Bogdan-Andrei!
>
> I’ve made the changes and now I can edit the TLS certificates normally 
> by control panel but I continue having a problem.
>
> If I configure the certificate directly on the configuration file the 
> connection with Microsoft Teams is correctly established, if I 
> configure through control panel, I receive on log the following messages:
>
> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for 
> conn 0x7f22a5f993d0
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:proto_tls:proto_tls_send: connect failed
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
> send() to 52.114.132.46:5061 for proto tls/3 failed
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
> attempt to send to 'sip:sip.pstnhub.microsoft.com' failed
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for 
> conn 0x7f22a5f91420
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
> ERROR:proto_tls:proto_tls_send: connect failed
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
> send() to 52.114.76.76:5061 for proto tls/3 failed
> Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
> attempt to send to 'sip:sip2.pstnhub.microsoft.com' failed
> Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_connect_blocking_timeout: connect timed out, 599667 us 
> elapsed out of 600000 us
> Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
> ERROR:core:tcp_sync_connect_fd: tcp_blocking_connect failed
> Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
> ERROR:proto_tls:proto_tls_send: connect failed
> Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
> send() to 52.114.32.169:5061 for proto tls/3 failed
> Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
> attempt to send to 'sip:sip3.pstnhub.microsoft.com' failed
> Aug 10 11:00:09 bowser /usr/sbin/opensips[55047]: 
> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
>
> I will send attached the screenshot of the control panel and below the 
> configuration that works.
>
> If it isn’t related to the same problem tell me and I send the message 
> to the open list ok!
>
> Thanks!
>
> # TLS CLIENT
> #modparam("tls_mgm", "client_domain", "sbcsothis")
> #modparam("tls_mgm", "match_sip_domain", "[sbcsothis]*")
> #modparam("tls_mgm", "match_ip_address", "[sbcsothis]*")
> #modparam("tls_mgm", "verify_cert", "[sbcsothis]1")
> #modparam("tls_mgm", "require_cert", "[sbcsothis]1")
> #modparam("tls_mgm", "tls_method", "[sbcsothis]TLSv1-")
> #modparam("tls_mgm", "certificate", 
> "[sbcsothis]/etc/opensips/tls/user/sothistelecom.com.crt")
> #modparam("tls_mgm", "private_key", 
> "[sbcsothis]/etc/opensips/tls/user/sothistelecom.com.key")
> #modparam("tls_mgm", "ca_list", 
> "[sbcsothis]/etc/ssl/certs/ca-certificates.crt")
> #modparam("tls_mgm", "ca_dir", "[sbcsothis]/etc/ssl/certs/")Config file
>
>
>
> Em 10 de ago. de 2022 04:50 -0300, Bogdan-Andrei Iancu 
> <bogdan at opensips.org>, escreveu:
>> Hi Francisco,
>>
>> Thanks for the info, it seems it was an issue with the validation 
>> regexp, see 
>> https://github.com/OpenSIPS/opensips-cp/commit/7558bc7e36c03293858c7086edfc724d56a2b9b4
>>
>> So please update from GIT or TAR and give it a try (or simply do a 
>> manual change as per the diff link).
>>
>> Let me know if it works now.
>>
>> Regards,
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>    https://www.opensips.org/events/Summit-2022Athens/
>> On 8/9/22 11:46 PM, Francisco Neto wrote:
>>> Hi Bogdan-Andrei! How are you!
>>>
>>> Below is all the information that you have request ok, fell free to 
>>> ask me if you need something more!
>>>
>>> *version: opensips 3.2.5 (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.
>>> main.c compiled on with gcc 10
>>>
>>> *Opensips Control Panel 9.3.2*
>>>
>>> *Debian Version 11.2*
>>>
>>>
>>> Thank you very much for the help!
>>>
>>>
>>>
>>> Em 9 de ago. de 2022 05:39 -0300, Bogdan-Andrei Iancu 
>>> <bogdan at opensips.org>, escreveu:
>>>> Hi Francisco,
>>>>
>>>> I guess you are talking about managing certificates via the Control 
>>>> Panel, right ? if so, what version of OpenSIPS and OpenSIPS CP are 
>>>> you using ? Also, could you provide a screenshot of the add / 
>>>> update form, showing the issue? IF you have any sensitive data, 
>>>> please send the screenshot privately to me.
>>>>
>>>> Best regards,
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>    https://www.opensips-solutions.com
>>>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>>>    https://www.opensips.org/events/Summit-2022Athens/
>>>> On 8/3/22 9:27 PM, Francisco Neto via Users wrote:
>>>>> Hi All!
>>>>>
>>>>> I’ve just installed open sips and everything is working ok, except 
>>>>> the TLS Management interface.
>>>>>
>>>>> When I try to add ou update any entry, it only accept “Network 
>>>>> Address” as “*”.
>>>>>
>>>>> If I type the IP address as x.x.x.x:port or “x.x.x.x:port” or 
>>>>> ‘x.x.x.x:port’ it always complain with the following message: 
>>>>> Failed to validate input for match_ip_address
>>>>>
>>>>> Can someone give me a tip of how should I write the IP address or 
>>>>> if it a bug?
>>>>>
>>>>> 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/20220811/a69cd9b3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D04BD69EB4754314AF257A93D3ADA588.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220811/a69cd9b3/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DB7D58DE644C44489200EED54502B4A4.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220811/a69cd9b3/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png
Type: image/png
Size: 8292 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20220811/a69cd9b3/attachment-0005.png>

From nukemania at naver.com  Fri Aug 12 02:21:10 2022
From: nukemania at naver.com (=?utf-8?B?7J207J6s7LKc?=)
Date: Fri, 12 Aug 2022 11:21:10 +0900
Subject: [OpenSIPS-Users] =?utf-8?q?What_are_the_possible_values_=E2=80=8B?=
	=?utf-8?q?=E2=80=8Bfor_the_modparam_parameter=3F?=
In-Reply-To: <97a0dabb5f1c9ed577e4df7b720834b@cweb006.nm.nfra.io>
References: <fbd7c765213c8f5f87ea8b846be4c7b@cweb001.nm.nfra.io>
 <97a0dabb5f1c9ed577e4df7b720834b@cweb006.nm.nfra.io>
Message-ID: <281cf4940464b641225f2b85a6b13@cweb018.nm.nfra.io>

What are the possible values ​​for the modparam parameter? 
 
Such as sipping_bflag in nathelper module,
 
a tutorial in Tutorials-Distributed-User-Location-Full-Sharing show
 
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE") 
 
and other sample in https://www.ictinnovations.com/opensips-as-load-balancer-and-register-with-asterisk-servers-integeration shows
 
modparam("nathelper", "sipping_bflag", "SIP_PING_FLAG"). 
 
So I searched for what is the possible value,
 
but the manual page in 3.2.x docs(https://opensips.org/docs/modules/3.2.x/nathelper.html) shows only that
 
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
 
and does not shows that what is the possible values and how it acts.
 
Where can I find the information?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220812/b4bded4c/attachment.html>

From bogdan at opensips.org  Fri Aug 12 07:14:11 2022
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 12 Aug 2022 10:14:11 +0300
Subject: [OpenSIPS-Users]
 =?utf-8?q?What_are_the_possible_values_=E2=80=8B?=
 =?utf-8?q?=E2=80=8Bfor_the_modparam_parameter=3F?=
In-Reply-To: <281cf4940464b641225f2b85a6b13@cweb018.nm.nfra.io>
References: <fbd7c765213c8f5f87ea8b846be4c7b@cweb001.nm.nfra.io>
 <97a0dabb5f1c9ed577e4df7b720834b@cweb006.nm.nfra.io>
 <281cf4940464b641225f2b85a6b13@cweb018.nm.nfra.io>
Message-ID: <580865b0-0608-b99e-1d52-a9ae2e2f9976@opensips.org>

Hi,

As per documentation, the value of that param is a FLAG or Branch FLAG - 
the flags are named by you, they are not predefined, see 
https://www.opensips.org/Documentation/Script-Flags-3-2

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/

On 8/12/22 5:21 AM, 이재천 wrote:
>
> What are the possible values ​​for the modparam parameter?
>
> Such as sipping_bflag in nathelper module,
>
> a tutorial in Tutorials-Distributed-User-Location-Full-Sharing show
>
> modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
>
> and other sample in 
> https://www.ictinnovations.com/opensips-as-load-balancer-and-register-with-asterisk-servers-integeration 
> <https://www.ictinnovations.com/opensips-as-load-balancer-and-register-with-asterisk-servers-integeration> 
> shows
>
> modparam("nathelper", "sipping_bflag", "SIP_PING_FLAG").
>
> So I searched for what is the possible value,
>
> but the manual page in 3.2.x 
> docs(https://opensips.org/docs/modules/3.2.x/nathelper.html 
> <https://opensips.org/docs/modules/3.2.x/nathelper.html>) shows only that
>
> modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
>
> and does not shows that what is the possible values and how it acts.
>
> Where can I find the information?
>
>
> _______________________________________________
> 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/20220812/c5774ff1/attachment.html>

From bullehs at gmail.com  Fri Aug 12 10:11:58 2022
From: bullehs at gmail.com (HS)
Date: Fri, 12 Aug 2022 15:11:58 +0500
Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation
In-Reply-To: <cf1c211f-abcd-9469-828c-2be97075377f@opensips.org>
References: <CA+PgBobQBR6unJaCi_mDs-GFiOWm1ojJLnVLNHepu3xGuK3VEg@mail.gmail.com>
 <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org>
 <CA+PgBoYOpOaegKa6DOZMjiA7C+goqy3M6J1ptcmDA9D11afTBw@mail.gmail.com>
 <d77afd0e-3c03-101c-731e-6fa460f48b4d@opensips.org>
 <CA+PgBob0qgeah0A7N4vLJ7AdqSLWDzfDAmCSLmVvWAP2Ja37QQ@mail.gmail.com>
 <be32b1ff-a940-1741-935b-ae939eb8d960@opensips.org>
 <CA+PgBoZNEz6mFzjpoB8jB+H7WYBOHJaWyv=+craD=Q1ALN1Mqw@mail.gmail.com>
 <cf1c211f-abcd-9469-828c-2be97075377f@opensips.org>
Message-ID: <CA+PgBoahtd-4=XYMs-LAUw-1AuPMzO2y0iTEH-oRTmjcjbzMNg@mail.gmail.com>

Bogdan-Andrei.

Thanks again for the help. Yes, it doesn't transfer to VM on "timeout upon
ringing" or "temporary unavailable".

Best wishes.

On Thu, Aug 11, 2022 at 9:02 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> By "in all other cases" you mean "timeout upon ringing" ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 27-30 Sept 2022, Athens
>   https://www.opensips.org/events/Summit-2022Athens/
>
> On 8/10/22 4:20 PM, HS wrote:
>
> Hi again.
>
> Thanks. Exact opposite :) When using an alias, after the call to users
> device is rejected, it is redirecting successfully to VM. However, in all
> other cases it doesn't redirect to VM (when using an alias) and times out.
> On the other hand, everything works as per snippet if using subscriber
> table details.
>
> Does that make sense please?
>
> Thanks.
>
> On Wed, Aug 10, 2022 at 5:25 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi,
>>
>> So, your issue is that, after the call to user's device is rejected, and
>> redirecting to VM (via failure route) you have some wrong RURI, right ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>   https://www.opensips.org/events/Summit-2022Athens/
>>
>> On 8/10/22 1:51 PM, HS wrote:
>>
>> Hi again.
>>
>> Thanks a lot for the quick response. My cfg is a bit of a trial-and-error
>> based, hence will email it (if that's ok). However, dbaliases support is
>> inserted as per default residential script:
>>
>> if ($rU==NULL) {
>> # request with no Username in RURI
>> send_reply(484,"Address Incomplete");
>> exit;
>> }
>>
>> # apply DB based aliases
>> alias_db_lookup("dbaliases");
>>
>> Thanks again.
>>
>> HS.
>>
>> On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi,
>>>
>>> Could you share the cfg WITH the dbaliases support, to check where the
>>> alias lookup was inserted in the cfg logic ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>   https://www.opensips-solutions.com
>>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>>   https://www.opensips.org/events/Summit-2022Athens/
>>>
>>> On 8/10/22 1:28 PM, HS wrote:
>>>
>>> Hi again Bogdan,
>>>
>>> Thanks for responding. I *tried* to add support for aliases. What is
>>> interesting is that the following snippet works fine on decline (but not
>>> otherwise):
>>>
>>> if (t_check_status("487|408|486|480|603")){
>>> rewritehostport("INT.IP.XX.XXX:5091");
>>>                 t_relay();
>>>                 exit;
>>>
>>> Any thoughts on how to fix please?
>>>
>>> Thanks.
>>>
>>> On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> wrote:
>>>
>>>> Hi HS,
>>>>
>>>> The aliases and late SDP negotiation has noting in common.
>>>>
>>>> And the mentioned script has no support for aliase - I guess you added
>>>> such support ?
>>>>
>>>> Regards,
>>>>
>>>> Bogdan-Andrei Iancu
>>>>
>>>> OpenSIPS Founder and Developer
>>>>   https://www.opensips-solutions.com
>>>> OpenSIPS Summit 27-30 Sept 2022, Athens
>>>>   https://www.opensips.org/events/Summit-2022Athens/
>>>>
>>>> On 6/20/22 5:21 PM, HS wrote:
>>>>
>>>> Hi all.
>>>>
>>>> Just wondering if anyone has "dbaliases" working with the Late SDP
>>>> negotiation script below:
>>>>
>>>> https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>>>
>>>> If we call an alias, it works fine if the user is online. However, in
>>>> case of offline users I want the call to be forwarded to another
>>>> instance/server. If we use the ID (from subscriber table) calls are being
>>>> forwarded. But not if we dial an alias.
>>>>
>>>> Appreciate the help.
>>>>
>>>> _______________________________________________
>>>> 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/20220812/3a2423e8/attachment-0001.html>