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: 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 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 __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 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 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 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 __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 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 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 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 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 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 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 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 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 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: 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: References: 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 >     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: <053c52e8-8749-bd88-e480-bf91079e002b@opensips.org> Message-ID: 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 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 > > 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: 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: 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: 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: 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: References: Message-ID: 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 on behalf of David Villasmil Date: Thursday, August 4, 2022 at 1:54 PM To: 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 phone: +34669448337 -------------- next part -------------- An HTML attachment was scrubbed... URL: 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png Type: image/png Size: 8292 bytes Desc: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png URL: 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: 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: 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: References: 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: 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png Type: image/png Size: 8292 bytes Desc: not available URL: 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: References: Message-ID: 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: 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: References: 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 not found in module not found in module 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 not found in module июл 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 not found in module июл 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: References: Message-ID: 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: 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: References: Message-ID: 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: 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: References: Message-ID: 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 > > /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: 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: References: 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: 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: References: 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 > > > 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: 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: References: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org> 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 >: > > 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: 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: References: Message-ID: 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 : > 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: 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: References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> Message-ID: 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 > , 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: DB7D58DE644C44489200EED54502B4A4.png Type: image/png Size: 8292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png Type: image/png Size: 8292 bytes Desc: not available URL: 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: References: 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 >: > > 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: 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: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 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: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 > > 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 list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 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 > 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: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 > > 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 >> > 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 list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: 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: 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 ) and custom timeout (see “$DLG_timeout” - $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=(37), tt=(15), ft=(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: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 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 > 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 >> 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: 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: References: 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 > : > > > 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 > ) > and custom timeout (see“$DLG_timeout”-$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=(37), tt=(15), > ft=(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: 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: <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: 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: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org> Message-ID: Hello Bogdan! Thank you very much for your quick reply. ср, 10 авг. 2022 г. в 16:49, Bogdan-Andrei Iancu : > 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 > ) > and custom timeout (see “$DLG_timeout” - $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=(37), tt=(15), > ft=(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: 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: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org> Message-ID: 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 : > 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 > ) > and custom timeout (see “$DLG_timeout” - $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=(37), tt=(15), > ft=(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: 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: <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org> Message-ID: 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 : > 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 : > >> 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: 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: OpenSIPS Summit Sept 27th - 30th, 2022, Athens, Greece *Speaker's lineup & Schedule * We bring here the list of speakers and papers - great speakers presenting great topics to share experience and knowledge to a great audience. Explore here all the details... *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 ** -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: 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: References: <2e41dfdb-9d44-764f-2939-2b4ab6faa973@opensips.org> 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 >: > > 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 >> >: >> >> 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: 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: <1e34cf36-93e4-4f78-43ed-581ff062611a@opensips.org> <1660153195.783883178@f174.i.mail.ru> Message-ID: 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: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 > > 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 >> > 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 >>> > 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 list >>>> Users at lists.opensips.org >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: 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: 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: 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: References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> 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 > , 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 >>> , 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: D04BD69EB4754314AF257A93D3ADA588.png Type: image/png Size: 8292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DB7D58DE644C44489200EED54502B4A4.png Type: image/png Size: 8292 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png Type: image/png Size: 8292 bytes Desc: not available URL: 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: <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: 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: <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 > > 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? > > > _______________________________________________ > 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: 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: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: 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 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 > 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 >> 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 >>> 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: From Li.Cai at comtech.com Mon Aug 15 13:32:41 2022 From: Li.Cai at comtech.com (Li Cai) Date: Mon, 15 Aug 2022 13:32:41 +0000 Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in event header of NOTIFY(REFER) In-Reply-To: References: Message-ID: Hi Bogdan, Yes, I'm trying to figure out a way to implement correct Id in event header of NOTIFY for REFER. Can I ask for the suggestion on how to move forward? Thanks, Li From: Bogdan-Andrei Iancu Sent: August 9, 2022 5:00 AM To: OpenSIPS users mailling list ; Li Cai Subject: Re: [OpenSIPS-Users] About obstacles to implement the matched Id in event header of NOTIFY(REFER) WARNING: External Email: Exercise Caution 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: From bogdan at opensips.org Mon Aug 15 14:16:21 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 15 Aug 2022 17:16:21 +0300 Subject: [OpenSIPS-Users] call_center module on 3.3 In-Reply-To: <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org> References: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org> <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org> Message-ID: Hi Ivan, I did some more digging into this and I managed to reproduce the issue and understand it. The REJECT'ion even in B2B is triggered only in the sequential bridging's, but not in the original setup bridging. So, what you have to do it is to set a welcome message for sure in the queue - this fixed the issue for me for now. I will check further if this can be addressed in any other way, otherwise I will document it as a limitation. 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 4:55 PM, Bogdan-Andrei Iancu wrote: > 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 > >: >> >> 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 >> > > > _______________________________________________ > 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: From ryzhik.ivan at gmail.com Tue Aug 16 06:20:13 2022 From: ryzhik.ivan at gmail.com (Ryzhik Ivan) Date: Tue, 16 Aug 2022 09:20:13 +0300 Subject: [OpenSIPS-Users] call_center module on 3.3 In-Reply-To: References: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org> <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org> Message-ID: Thank you, Bogdan. I'm using message_flow_id uri already. That would be good if it was documented as a limitation. Regards, Ivan 15 aug 2022 г. в 17:16, Bogdan-Andrei Iancu : > Hi Ivan, > > I did some more digging into this and I managed to reproduce the issue and > understand it. The REJECT'ion even in B2B is triggered only in the > sequential bridging's, but not in the original setup bridging. > > So, what you have to do it is to set a welcome message for sure in the > queue - this fixed the issue for me for now. I will check further if this > can be addressed in any other way, otherwise I will document it as a > limitation. > > 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 4:55 PM, Bogdan-Andrei Iancu wrote: > > 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 : > >> 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 listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Aug 16 06:57:06 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 16 Aug 2022 09:57:06 +0300 Subject: [OpenSIPS-Users] call_center module on 3.3 In-Reply-To: References: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org> <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org> Message-ID: Ivan, not that one, but the |"message_welcome" URI ! 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/16/22 9:20 AM, Ryzhik Ivan wrote: > Thank you, Bogdan. > I'm using message_flow_id uri already. That would be good if it was > documented as a limitation. > Regards, > Ivan > > 15 aug 2022 г. в 17:16, Bogdan-Andrei Iancu >: > > Hi Ivan, > > I did some more digging into this and I managed to reproduce the > issue and understand it. The REJECT'ion even in B2B is triggered > only in the sequential bridging's, but not in the original setup > bridging. > > So, what you have to do it is to set a welcome message for sure in > the queue - this fixed the issue for me for now. I will check > further if this can be addressed in any other way, otherwise I > will document it as a limitation. > > 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 4:55 PM, Bogdan-Andrei Iancu wrote: >> 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 >>> >: >>> >>> 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 >>> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Aug 16 07:19:49 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 16 Aug 2022 10:19:49 +0300 Subject: [OpenSIPS-Users] DBAliases with Late SDP Negotiation In-Reply-To: References: <32744ecc-6aaf-ad21-0d3f-0ee0bf957e95@opensips.org> Message-ID: <61d58209-9cf3-05f5-eb63-a56dbab04906@opensips.org> Hi, In the failure route I see that the 408 is handled as the other reply codes that work (like 486). Put some xlogs in the failure route to understand why the t_relay() is not hit when you have a call timeout (or better use script_trace() [1]) [1] https://www.opensips.org/Documentation/Script-CoreFunctions-3-2#script_trace 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 1:11 PM, HS wrote: > 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 > > 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 >> > 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 >>> > 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 >>>> > 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 list >>>>> Users at lists.opensips.org >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Aug 16 07:30:04 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 16 Aug 2022 10:30:04 +0300 Subject: [OpenSIPS-Users] call_center module on 3.3 In-Reply-To: References: <8483a688-c9b5-3c6c-7a06-53274a1c09d1@opensips.org> <2b85f356-5b53-8a47-f383-db13feecb974@opensips.org> Message-ID: <1afca004-1de9-0b9d-dc3e-1e4aff6e62f2@opensips.org> Actually you are right, the message_flow_id would have the same effect there - the idea is to have an UAC B2B already established (to welcome, to flow_id, doesn;t matter) before having the UAC leg to agent (that may be rejected). 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/16/22 10:21 AM, Ryzhik Ivan wrote: > You are right. But message_flow_id (i did invite-200-bye with no real > rtp) fixed the issue for me for now too. Maybe it should be added to > FAQ or also as a limitation. > Thanks for great help. > Regards, Ivan. > вт, 16 авг. 2022 г. в 09:57, Bogdan-Andrei Iancu >: > > Ivan, not that one, but the |"message_welcome" URI ! > > 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/16/22 9:20 AM, Ryzhik Ivan wrote: >> Thank you, Bogdan. >> I'm using message_flow_id uri already. That would be good if it >> was documented as a limitation. >> Regards, >> Ivan >> >> 15 aug 2022 г. в 17:16, Bogdan-Andrei Iancu > >: >> >> Hi Ivan, >> >> I did some more digging into this and I managed to reproduce >> the issue and understand it. The REJECT'ion even in B2B is >> triggered only in the sequential bridging's, but not in the >> original setup bridging. >> >> So, what you have to do it is to set a welcome message for >> sure in the queue - this fixed the issue for me for now. I >> will check further if this can be addressed in any other way, >> otherwise I will document it as a limitation. >> >> 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 4:55 PM, Bogdan-Andrei Iancu wrote: >>> 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 >>>> >: >>>> >>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Aug 16 08:23:10 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 16 Aug 2022 11:23:10 +0300 Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in event header of NOTIFY(REFER) In-Reply-To: References: Message-ID: <4fcde0dd-da58-e9b6-8e3f-9cff228c250b@opensips.org> Vlad, haven't you looked into this some time ago? 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/15/22 4:32 PM, Li Cai wrote: > > Hi Bogdan, > > Yes, I’m trying to figure out a way to implement correct Id in event > header of NOTIFY for REFER. Can I ask for the suggestion on how to > move forward? > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > *Sent:* August 9, 2022 5:00 AM > *To:* OpenSIPS users mailling list ; Li Cai > > *Subject:* Re: [OpenSIPS-Users] About obstacles to implement the > matched Id in event header of NOTIFY(REFER) > > *WARNING: External Email: Exercise Caution* > > 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: From vladp at opensips.org Tue Aug 16 19:19:10 2022 From: vladp at opensips.org (Vlad Patrascu) Date: Tue, 16 Aug 2022 22:19:10 +0300 Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in event header of NOTIFY(REFER) In-Reply-To: References: Message-ID: <91e7202d-ac0f-9ab3-252e-49640130aae4@opensips.org> Hi Li, For passing around data between the b2b request route and local_route, in the context of an ongoing B2B session, you can use the $b2b_logic.ctx variable[1]. That would take care of transferring the Cseq from step 1 to step 2 and the id from step 3 to step 4. As for your cseq map, you can use the cachedb_local module, and maybe the $b2b_logic.key variable alongside Cseq2 for building a proper key. [1] https://opensips.org/docs/modules/3.3.x/b2b_logic.html#b2b_logic.key Regards, -- Vlad Patrascu OpenSIPS Core Developer http://www.opensips-solutions.com On 22.07.2022 23:02, 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: From bogdan at opensips.org Wed Aug 17 07:28:49 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 17 Aug 2022 10:28:49 +0300 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> Message-ID: <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> Hi Francisco, Please check https://github.com/OpenSIPS/opensips-cp/commit/1e738fd948fcc83004b0b99edb4f361c0a8b784c - update again and give it a try by adding "*" for the match_domain 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/16/22 11:32 PM, Francisco Neto wrote: > Hi Bogdan-Andrei! > > Actually I’ve tried with using sip domain as blank, with * it didn’t > let me press update on CP, and with the client certificate (fqdn and > domain part only) and in all scenarios the error is the same as > described below: > > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found > Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29a648a8 > Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket > Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed > Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.132.46:5061 for proto tls/3 failed > Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29b341a8 > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.76.76:5061 for proto tls/3 failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29a17ec8 > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.14.70:5061 for proto tls/3 failed > Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed > > Below is my actual config section about TLS > > loadmodule "proto_tls.so" > modparam("proto_tls","tls_max_msg_chunks", 8) > modparam("proto_tls","tls_handshake_timeout", 600) > modparam("proto_tls", "tls_send_timeout", 2000) > > > loadmodule "tls_openssl.so" > loadmodule "tls_mgm.so" > modparam("tls_mgm", > "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") > modparam("tls_mgm", "db_table", "tls_mgm") > modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") > > > Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu > , escreveu: >> 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 >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: F4F396411D0249C49A1BE4F226E20C17.png Type: image/png Size: 8292 bytes Desc: not available URL: From liviu at opensips.org Wed Aug 17 11:03:56 2022 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 17 Aug 2022 14:03:56 +0300 Subject: [OpenSIPS-Users] [Release] OpenSIPS 3.3.1, 3.2.8 and 3.1.11 minor releases In-Reply-To: References: Message-ID: On 03.08.2022 18:58, Liviu Chircu wrote: > 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, > Hello, As scheduled, the OpenSIPS 3.3.1, 3.2.8 and 3.1.11 minor releases are now available, packing important fixes of the past two months. Detailed changelogs are available on the website^[1][2][3] . [1]: https://opensips.org/pub/opensips/3.1.11/ChangeLog [2]: https://opensips.org/pub/opensips/3.2.8/ChangeLog [3]: https://opensips.org/pub/opensips/3.3.1/ChangeLog Happy Hacking! -- 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: From bogdan at opensips.org Wed Aug 17 16:17:02 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 17 Aug 2022 19:17:02 +0300 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> Message-ID: <3b9338c1-3744-453e-9d6e-927eec786a18@opensips.org> You can add extra methods in the combo, not a problem - the question is if opensips will understand it when loading from DB - do you see any errors on reload ? 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/17/22 5:52 PM, Francisco Neto wrote: > Hi Bogdan-Andrei!! > > I’ve made the changes on the code as you requested. On CP I could fill > the match_sip_domain With * and update the item, after that the errors > on log file have changed a lot now. > Below are the errors that are appearing to me now > > By the way, directly on the config file the SSL Method that works > better for me was “TLSv1-“. This option didn’t exist on > tviewer.inc.php, but I have created this option on the file. Does it > have any problem to add a new valid combo option?? > > Thanks! > > ERROR:proto_tls:proto_tls_send: failed to send > Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:msg_send: > send() to 52.114.76.76:5061 for proto tls/3 failed > Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:t_uac: > attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed > Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: > ERROR:tls_openssl:openssl_tls_connect: SSL_ERROR_SYSCALL err=Resource > temporarily unavailable(11) > Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: > ERROR:tls_openssl:openssl_tls_connect: New TLS connection to > 52.114.76.76:5061 failed > Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: > ERROR:tls_openssl:openssl_tls_connect: TLS error: 5 (ret=-1) > err=Resource temporarily unavailable(11) > Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: > ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! > Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: > ERROR:tls_openssl:openssl_tls_connect: New TLS connection to > 52.114.14.70:5061 failed > Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: > ERROR:tls_openssl:openssl_tls_connect: TLS error: 1 (ret=-1) > err=Success(0) > Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: > ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:1416F086:SSL > routines:tls_process_server_certificate:certificate verify failed > > > Em 17 de ago. de 2022 04:29 -0300, Bogdan-Andrei Iancu > , escreveu: >> Hi Francisco, >> >> Please check >> https://github.com/OpenSIPS/opensips-cp/commit/1e738fd948fcc83004b0b99edb4f361c0a8b784c >> - update again and give it a try by adding "*" for the match_domain >> >> 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/16/22 11:32 PM, Francisco Neto wrote: >>> Hi Bogdan-Andrei! >>> >>> Actually I’ve tried with using sip domain as blank, with * it didn’t >>> let me press update on CP, and with the client certificate (fqdn and >>> domain part only) and in all scenarios the error is the same as >>> described below: >>> >>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>> conn 0x7efe29a648a8 >>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket >>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>> ERROR:proto_tls:proto_tls_send: connect failed >>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >>> send() to 52.114.132.46:5061 for proto tls/3 failed >>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>> attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>> conn 0x7efe29b341a8 >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:proto_tls:proto_tls_send: connect failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >>> send() to 52.114.76.76:5061 for proto tls/3 failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>> attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>> conn 0x7efe29a17ec8 >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>> ERROR:proto_tls:proto_tls_send: connect failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >>> send() to 52.114.14.70:5061 for proto tls/3 failed >>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>> attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed >>> >>> Below is my actual config section about TLS >>> >>> loadmodule "proto_tls.so" >>> modparam("proto_tls","tls_max_msg_chunks", 8) >>> modparam("proto_tls","tls_handshake_timeout", 600) >>> modparam("proto_tls", "tls_send_timeout", 2000) >>> >>> >>> loadmodule "tls_openssl.so" >>> loadmodule "tls_mgm.so" >>> modparam("tls_mgm", >>> "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") >>> modparam("tls_mgm", "db_table", "tls_mgm") >>> modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") >>> >>> >>> Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu >>> , escreveu: >>>> 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 >>>>> >>>>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From Li.Cai at comtech.com Thu Aug 18 13:59:24 2022 From: Li.Cai at comtech.com (Li Cai) Date: Thu, 18 Aug 2022 13:59:24 +0000 Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in event Message-ID: Hi Vlad, Thank you very much for the suggestion. Sorry that I didn't mention our OpenSIPs version, we're with 2.4 which doesn't provide exported pseudo variables. Can I ask if there is similar way to do so in V2.4? Thanks, Li -----Original Message----- From: Users On Behalf Of users-request at lists.opensips.org Sent: August 17, 2022 3:29 AM To: users at lists.opensips.org Subject: Users Digest, Vol 169, Issue 25 WARNING: External Email: Exercise Caution Send Users mailing list submissions to users at lists.opensips.org To subscribe or unsubscribe via the World Wide Web, visit https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eN7ZRHTe3r03mOVKSiQdmxv8EEwIm7QS957iAccxudA%3D&reserved=0 or, via email, send a message with subject or body 'help' to users-request at lists.opensips.org You can reach the person managing the list at users-owner at lists.opensips.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." Today's Topics: 1. Re: About obstacles to implement the matched Id in event header of NOTIFY(REFER) (Vlad Patrascu) 2. Re: Bug on TLS Management Interface (Bogdan-Andrei Iancu) ---------------------------------------------------------------------- Message: 1 Date: Tue, 16 Aug 2022 22:19:10 +0300 From: Vlad Patrascu To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] About obstacles to implement the matched Id in event header of NOTIFY(REFER) Message-ID: <91e7202d-ac0f-9ab3-252e-49640130aae4 at opensips.org> Content-Type: text/plain; charset="utf-8"; Format="flowed" Hi Li, For passing around data between the b2b request route and local_route, in the context of an ongoing B2B session, you can use the $b2b_logic.ctx variable[1]. That would take care of transferring the Cseq from step 1 to step 2 and the id from step 3 to step 4. As for your cseq map, you can use the cachedb_local module, and maybe the $b2b_logic.key variable alongside Cseq2 for building a proper key. [1] https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Fdocs%2Fmodules%2F3.3.x%2Fb2b_logic.html%23b2b_logic.key&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6QxyCjy0NEZoKBkpyy2VYKakriwsEg6xrt%2FSV%2BisERk%3D&reserved=0 Regards, -- Vlad Patrascu OpenSIPS Core Developer https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dA%2Fa%2BWYy3xqc9qAGN3koDHWwBn5rWC1gRxG6PM5OebM%3D&reserved=0 On 22.07.2022 23:02, 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 > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists > .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01% > 7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696a > e040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbG > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% > 3D%7C3000%7C%7C%7C&sdata=eN7ZRHTe3r03mOVKSiQdmxv8EEwIm7QS957iAccxu > dA%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Wed, 17 Aug 2022 10:28:49 +0300 From: Bogdan-Andrei Iancu To: Francisco Neto , "users at lists.opensips.org" Subject: Re: [OpenSIPS-Users] Bug on TLS Management Interface Message-ID: <7b5da8ab-346f-3231-f73f-95d0211f3a4a at opensips.org> Content-Type: text/plain; charset="utf-8"; Format="flowed" Hi Francisco, Please check https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenSIPS%2Fopensips-cp%2Fcommit%2F1e738fd948fcc83004b0b99edb4f361c0a8b784c&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WFKEe%2Bog0e8sGKwPrG23OpjmyZG3R8Er7VGDTqE9krY%3D&reserved=0 - update again and give it a try by adding "*" for the match_domain Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3rS5RxmkxjbV9hR2k5jJ%2F1ojvkqdYqw5FDKG54TJOcY%3D&reserved=0 OpenSIPS Summit 27-30 Sept 2022, Athens https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7HvX9ki%2Bj7QuwBkT%2FuX2upmCyCxHkm9bR26YsIyCCVs%3D&reserved=0 On 8/16/22 11:32 PM, Francisco Neto wrote: > Hi Bogdan-Andrei! > > Actually I've tried with using sip domain as blank, with * it didn't > let me press update on CP, and with the client certificate (fqdn and > domain part only) and in all scenarios the error is the same as > described below: > > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 > 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the > socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser > /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 > bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 > 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 > 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the > socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser > /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 > bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 16 > 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 > 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_conn_create: failed to do proto 3 specific init for > conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the > socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: > ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser > /usr/sbin/opensips[1128]: ERROR:tm:msg_send: > send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 > bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: > attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed > > Below is my actual config section about TLS > > loadmodule "proto_tls.so" > modparam("proto_tls","tls_max_msg_chunks", 8) > modparam("proto_tls","tls_handshake_timeout", 600) > modparam("proto_tls", "tls_send_timeout", 2000) > > > loadmodule "tls_openssl.so" > loadmodule "tls_mgm.so" > modparam("tls_mgm", > "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") > modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", > "client_sip_domain_avp", "tls_sip_dom") > > > Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu > , escreveu: >> 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >> .opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C >> 502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7 >> C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM >> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& >> ;sdata=yp8rIlD05HWeQxkUb1ecaQtQLEdzoqz10UmhgzBTC7A%3D&reserved=0 >> OpenSIPS Summit 27-30 Sept 2022, Athens >> >> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >> .opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli.c >> ai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c >> 1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3 >> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% >> 7C3000%7C%7C%7C&sdata=7HvX9ki%2Bj7QuwBkT%2FuX2upmCyCxHkm9bR26YsIy >> CCVs%3D&reserved=0 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 >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: F4F396411D0249C49A1BE4F226E20C17.png Type: image/png Size: 8292 bytes Desc: not available URL: ------------------------------ Subject: Digest Footer _______________________________________________ Users mailing list Users at lists.opensips.org https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KCq%2BzVTAEtJVmV1aNhL%2FwSsbKwyE4n%2BHHmjrYhR7YQ8%3D&reserved=0 ------------------------------ End of Users Digest, Vol 169, Issue 25 ************************************** NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media. From vladp at opensips.org Thu Aug 18 15:28:13 2022 From: vladp at opensips.org (Vlad Patrascu) Date: Thu, 18 Aug 2022 18:28:13 +0300 Subject: [OpenSIPS-Users] About obstacles to implement the matched Id in event In-Reply-To: References: Message-ID: Hi Li, In 2.4 I think the only way is to use the same cachedb_local storage for everything you need to pass around. Regards, -- Vlad Patrascu OpenSIPS Core Developer http://www.opensips-solutions.com On 18.08.2022 16:59, Li Cai wrote: > Hi Vlad, > > Thank you very much for the suggestion. Sorry that I didn't mention our OpenSIPs version, we're with 2.4 which doesn't provide exported pseudo variables. Can I ask if there is similar way to do so in V2.4? > > > Thanks, > Li > > -----Original Message----- > From: Users On Behalf Of users-request at lists.opensips.org > Sent: August 17, 2022 3:29 AM > To: users at lists.opensips.org > Subject: Users Digest, Vol 169, Issue 25 > > > WARNING: External Email: Exercise Caution > > Send Users mailing list submissions to > users at lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eN7ZRHTe3r03mOVKSiQdmxv8EEwIm7QS957iAccxudA%3D&reserved=0 > or, via email, send a message with subject or body 'help' to > users-request at lists.opensips.org > > You can reach the person managing the list at > users-owner at lists.opensips.org > > When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: About obstacles to implement the matched Id in event > header of NOTIFY(REFER) (Vlad Patrascu) > 2. Re: Bug on TLS Management Interface (Bogdan-Andrei Iancu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Aug 2022 22:19:10 +0300 > From: Vlad Patrascu > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] About obstacles to implement the matched > Id in event header of NOTIFY(REFER) > Message-ID: <91e7202d-ac0f-9ab3-252e-49640130aae4 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Li, > > For passing around data between the b2b request route and local_route, in the context of an ongoing B2B session, you can use the $b2b_logic.ctx variable[1]. That would take care of transferring the Cseq from step 1 to step 2 and the id from step 3 to step 4. > > As for your cseq map, you can use the cachedb_local module, and maybe the $b2b_logic.key variable alongside Cseq2 for building a proper key. > > [1] https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Fdocs%2Fmodules%2F3.3.x%2Fb2b_logic.html%23b2b_logic.key&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6QxyCjy0NEZoKBkpyy2VYKakriwsEg6xrt%2FSV%2BisERk%3D&reserved=0 > > Regards, > > -- > Vlad Patrascu > OpenSIPS Core Developer > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dA%2Fa%2BWYy3xqc9qAGN3koDHWwBn5rWC1gRxG6PM5OebM%3D&reserved=0 > > On 22.07.2022 23:02, 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 >> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists >> .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01% >> 7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696a >> e040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbG >> Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% >> 3D%7C3000%7C%7C%7C&sdata=eN7ZRHTe3r03mOVKSiQdmxv8EEwIm7QS957iAccxu >> dA%3D&reserved=0 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Wed, 17 Aug 2022 10:28:49 +0300 > From: Bogdan-Andrei Iancu > To: Francisco Neto , "users at lists.opensips.org" > > Subject: Re: [OpenSIPS-Users] Bug on TLS Management Interface > Message-ID: <7b5da8ab-346f-3231-f73f-95d0211f3a4a at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Francisco, > > Please check > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenSIPS%2Fopensips-cp%2Fcommit%2F1e738fd948fcc83004b0b99edb4f361c0a8b784c&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WFKEe%2Bog0e8sGKwPrG23OpjmyZG3R8Er7VGDTqE9krY%3D&reserved=0 > - update again and give it a try by adding "*" for the match_domain > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3rS5RxmkxjbV9hR2k5jJ%2F1ojvkqdYqw5FDKG54TJOcY%3D&reserved=0 > OpenSIPS Summit 27-30 Sept 2022, Athens > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7HvX9ki%2Bj7QuwBkT%2FuX2upmCyCxHkm9bR26YsIyCCVs%3D&reserved=0 > > On 8/16/22 11:32 PM, Francisco Neto wrote: >> Hi Bogdan-Andrei! >> >> Actually I've tried with using sip domain as blank, with * it didn't >> let me press update on CP, and with the client certificate (fqdn and >> domain part only) and in all scenarios the error is the same as >> described below: >> >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 >> 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed >> >> Below is my actual config section about TLS >> >> loadmodule "proto_tls.so" >> modparam("proto_tls","tls_max_msg_chunks", 8) >> modparam("proto_tls","tls_handshake_timeout", 600) >> modparam("proto_tls", "tls_send_timeout", 2000) >> >> >> loadmodule "tls_openssl.so" >> loadmodule "tls_mgm.so" >> modparam("tls_mgm", >> "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") >> modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", >> "client_sip_domain_avp", "tls_sip_dom") >> >> >> Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu >> , escreveu: >>> 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >>> .opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C >>> 502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7 >>> C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM >>> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C& >>> ;sdata=yp8rIlD05HWeQxkUb1ecaQtQLEdzoqz10UmhgzBTC7A%3D&reserved=0 >>> OpenSIPS Summit 27-30 Sept 2022, Athens >>> >>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww >>> .opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli.c >>> ai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c >>> 1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3 >>> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% >>> 7C3000%7C%7C%7C&sdata=7HvX9ki%2Bj7QuwBkT%2FuX2upmCyCxHkm9bR26YsIy >>> CCVs%3D&reserved=0 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 >>>> >>>> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: F4F396411D0249C49A1BE4F226E20C17.png > Type: image/png > Size: 8292 bytes > Desc: not available > URL: > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KCq%2BzVTAEtJVmV1aNhL%2FwSsbKwyE4n%2BHHmjrYhR7YQ8%3D&reserved=0 > > > ------------------------------ > > End of Users Digest, Vol 169, Issue 25 > ************************************** > NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From napadailo at kolesa.kz Fri Aug 12 12:12:35 2022 From: napadailo at kolesa.kz (=?UTF-8?B?0K/RgNC+0YHQu9Cw0LIg0J3QsNC/0LDQtNCw0LnQu9C+?=) Date: Fri, 12 Aug 2022 18:12:35 +0600 Subject: [OpenSIPS-Users] STOP waiting for new branches and close transaction by t_wait_no_more_branches() Message-ID: Hi everybody! I'm writing script with Push Notification mechanism using TM module and t_wait_for_new_branches() function and EBR. Here example in docs https://opensips.org/docs/modules/3.2.x/event_routing.html#idp5576704 My is: route { ... t_newtran(); .... create_dialog(); ... t_on_reply("HANDLE_REPLY"); t_wait_for_new_branches(); .... notify_on_event("E_UL_CONTACT_INSERT", $avp(filter), "fork_call", $var(ttl)); } onreply_route[HANDLE_REPLY] { xlog("L_DBG", "received reply $rs $rr"); switch($rs) { case "486": xlog("L_DBG", "wait no more branches DLG_DID=$DLG_did"); t_wait_no_more_branches(); t_cancel_branch("a"); break; default: } } route[fork_call] { xlog("L_DBG", "[$ci] user $avp(aor) registered a new contact $avp(uri), injecting"); t_inject_branches("event"); } First, I create dialog. Then, call t_wait_for_new_branches() and set notify_on_event() handler. Then I'm waiting for new REGISTERs. When new contacts register to usrloc, I'm injecting received contacts as new branches to current transaction. I do all things as described in docs. Now I want to control negative replies from ongoing branches. By default, OS ignores negative replies and continue waiting for new branches. For example, I want to ignore 480, but handle 486. I try handle 486, calling t_wait_no_more_branches(). I expect that OS will stop waiting for new branches and t_inject_branches will not add anymore. Also I expect that OS stop PHONY branch, which is created first when calling t_wait_for_new_branches(), and sends final response (486 in my case) to caller. But in real next things happen: 1. t_wait_no_more_branches() doesn't affect adding new branches. If 1st callee reject call, then 2nd callee register new contact, t_inject_branches() adds new branch all the same 2. If no other branches added, caller hears ringing until FR_INV_TIMEOUT expires. And only when FR_INV_TIMEOUT expires, OS sends final response to caller. WIDW?? How to stop transaction immeditially when at least one ongoing branch reply 486 code and to wait no more for any branches? Thx for answers -- Regards, Yaroslav Napadilo -------------- next part -------------- An HTML attachment was scrubbed... URL: From fneto at sothis.com.br Tue Aug 16 20:32:58 2022 From: fneto at sothis.com.br (Francisco Neto) Date: Tue, 16 Aug 2022 20:32:58 +0000 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> Message-ID: <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> Hi Bogdan-Andrei! Actually I’ve tried with using sip domain as blank, with * it didn’t let me press update on CP, and with the client certificate (fqdn and domain part only) and in all scenarios the error is the same as described below: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed Below is my actual config section about TLS loadmodule "proto_tls.so" modparam("proto_tls","tls_max_msg_chunks", 8) modparam("proto_tls","tls_handshake_timeout", 600) modparam("proto_tls", "tls_send_timeout", 2000) loadmodule "tls_openssl.so" loadmodule "tls_mgm.so" modparam("tls_mgm", "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") [cid:F4F396411D0249C49A1BE4F226E20C17] Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu , escreveu: 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 [cid:part1.785A2611.F166D4B1 at opensips.org] Em 10 de ago. de 2022 04:50 -0300, Bogdan-Andrei Iancu , 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! [cid:part5.FD9717CC.4C36158D at opensips.org] Em 9 de ago. de 2022 05:39 -0300, Bogdan-Andrei Iancu , 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! [cid:part9.0C13D810.9ABAE774 at opensips.org] _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: F4F396411D0249C49A1BE4F226E20C17.png Type: image/png Size: 8292 bytes Desc: F4F396411D0249C49A1BE4F226E20C17.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: D04BD69EB4754314AF257A93D3ADA588.png Type: image/png Size: 8292 bytes Desc: D04BD69EB4754314AF257A93D3ADA588.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DB7D58DE644C44489200EED54502B4A4.png Type: image/png Size: 8292 bytes Desc: DB7D58DE644C44489200EED54502B4A4.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png Type: image/png Size: 8292 bytes Desc: 4D4E11AC4AD945D9B0DAB9AFC951BF99.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de Tela 2022-08-16 às 17.25.27.png Type: image/png Size: 39030 bytes Desc: Captura de Tela 2022-08-16 às 17.25.27.png URL: From kennedy4260 at gmail.com Wed Aug 17 19:18:52 2022 From: kennedy4260 at gmail.com (Kevin Kennedy) Date: Wed, 17 Aug 2022 12:18:52 -0700 Subject: [OpenSIPS-Users] Loadbalancer for Registrations and calls Message-ID: I am looking for a configuration to be able to front end multiple SBC's to load balance Registrations and keep track of them to send INVITE's to the corresponding SBC. I am thinking of using a combination of Dispatcher and midregister, but not sure how to set this up correctly. Any thoughts? Thank you. Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From fneto at sothis.com.br Wed Aug 17 14:52:20 2022 From: fneto at sothis.com.br (Francisco Neto) Date: Wed, 17 Aug 2022 14:52:20 +0000 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> Message-ID: Hi Bogdan-Andrei!! I’ve made the changes on the code as you requested. On CP I could fill the match_sip_domain With * and update the item, after that the errors on log file have changed a lot now. Below are the errors that are appearing to me now By the way, directly on the config file the SSL Method that works better for me was “TLSv1-“. This option didn’t exist on tviewer.inc.php, but I have created this option on the file. Does it have any problem to add a new valid combo option?? Thanks! ERROR:proto_tls:proto_tls_send: failed to send Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:t_uac: attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: SSL_ERROR_SYSCALL err=Resource temporarily unavailable(11) Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: New TLS connection to 52.114.76.76:5061 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: TLS error: 5 (ret=-1) err=Resource temporarily unavailable(11) Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:openssl_tls_connect: New TLS connection to 52.114.14.70:5061 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:openssl_tls_connect: TLS error: 1 (ret=-1) err=Success(0) Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed [cid:47283D8C944B42F3A02401A5B7B37B70] Em 17 de ago. de 2022 04:29 -0300, Bogdan-Andrei Iancu , escreveu: Hi Francisco, Please check https://github.com/OpenSIPS/opensips-cp/commit/1e738fd948fcc83004b0b99edb4f361c0a8b784c - update again and give it a try by adding "*" for the match_domain 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/16/22 11:32 PM, Francisco Neto wrote: Hi Bogdan-Andrei! Actually I’ve tried with using sip domain as blank, with * it didn’t let me press update on CP, and with the client certificate (fqdn and domain part only) and in all scenarios the error is the same as described below: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed Below is my actual config section about TLS loadmodule "proto_tls.so" modparam("proto_tls","tls_max_msg_chunks", 8) modparam("proto_tls","tls_handshake_timeout", 600) modparam("proto_tls", "tls_send_timeout", 2000) loadmodule "tls_openssl.so" loadmodule "tls_mgm.so" modparam("tls_mgm", "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") [cid:part1.ED5D83CE.3FE8C575 at opensips.org] Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu , escreveu: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 47283D8C944B42F3A02401A5B7B37B70.png Type: image/png Size: 8292 bytes Desc: 47283D8C944B42F3A02401A5B7B37B70.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: F4F396411D0249C49A1BE4F226E20C17.png Type: image/png Size: 8292 bytes Desc: F4F396411D0249C49A1BE4F226E20C17.png URL: From fneto at sothis.com.br Wed Aug 17 16:55:08 2022 From: fneto at sothis.com.br (Francisco Neto) Date: Wed, 17 Aug 2022 16:55:08 +0000 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: <3b9338c1-3744-453e-9d6e-927eec786a18@opensips.org> References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> <3b9338c1-3744-453e-9d6e-927eec786a18@opensips.org> Message-ID: <753ef653-2cc2-4a28-9777-4770a163e682@Spark> About the parameter "TLSv1-“ is everything ok, after the reload. No DB errors. I’ve found another difficulties, but with the changes below open sips is running fine with tls_mgm on db now. First I have change the memory parameter and start open sips with 256mb of memory and package memory Them the error has changed again, and I discover that on the conf file I have informed the “CA Directory”, so I fill it on the CP too and all errors have disappeared. Now my difficult is to correctly establishes the communication with microsoft teams. I don’t know what I’m doing wrong but MS are not identifying my SIP options…. [cid:A1273B7034F144E0939B236096040012] Em 17 de ago. de 2022 13:17 -0300, Bogdan-Andrei Iancu , escreveu: You can add extra methods in the combo, not a problem - the question is if opensips will understand it when loading from DB - do you see any errors on reload ? 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/17/22 5:52 PM, Francisco Neto wrote: Hi Bogdan-Andrei!! I’ve made the changes on the code as you requested. On CP I could fill the match_sip_domain With * and update the item, after that the errors on log file have changed a lot now. Below are the errors that are appearing to me now By the way, directly on the config file the SSL Method that works better for me was “TLSv1-“. This option didn’t exist on tviewer.inc.php, but I have created this option on the file. Does it have any problem to add a new valid combo option?? Thanks! ERROR:proto_tls:proto_tls_send: failed to send Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:t_uac: attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: SSL_ERROR_SYSCALL err=Resource temporarily unavailable(11) Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: New TLS connection to 52.114.76.76:5061 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:tls_openssl:openssl_tls_connect: TLS error: 5 (ret=-1) err=Resource temporarily unavailable(11) Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:openssl_tls_connect: New TLS connection to 52.114.14.70:5061 failed Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:openssl_tls_connect: TLS error: 1 (ret=-1) err=Success(0) Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tls_openssl:tls_print_errstack: TLS errstack: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed Em 17 de ago. de 2022 04:29 -0300, Bogdan-Andrei Iancu , escreveu: Hi Francisco, Please check https://github.com/OpenSIPS/opensips-cp/commit/1e738fd948fcc83004b0b99edb4f361c0a8b784c - update again and give it a try by adding "*" for the match_domain 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/16/22 11:32 PM, Francisco Neto wrote: Hi Bogdan-Andrei! Actually I’ve tried with using sip domain as blank, with * it didn’t let me press update on CP, and with the client certificate (fqdn and domain part only) and in all scenarios the error is the same as described below: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:msg_send: send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed Below is my actual config section about TLS loadmodule "proto_tls.so" modparam("proto_tls","tls_max_msg_chunks", 8) modparam("proto_tls","tls_handshake_timeout", 600) modparam("proto_tls", "tls_send_timeout", 2000) loadmodule "tls_openssl.so" loadmodule "tls_mgm.so" modparam("tls_mgm", "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu , escreveu: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: A1273B7034F144E0939B236096040012.png Type: image/png Size: 8292 bytes Desc: A1273B7034F144E0939B236096040012.png URL: From bogdan at opensips.org Thu Aug 18 11:32:41 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 18 Aug 2022 14:32:41 +0300 Subject: [OpenSIPS-Users] Bug on TLS Management Interface In-Reply-To: <753ef653-2cc2-4a28-9777-4770a163e682@Spark> References: <43949522-7b09-4b79-bd4c-c973ff6c875f@Spark> <86d5afe7-8236-42eb-948a-3e0432b25bf8@Spark> <6d4d3609-059f-6ac3-4b6b-fd796bc31299@opensips.org> <0735b42a-5fe4-86a9-0721-7e1378017a85@opensips.org> <16c92b38-4306-411c-bf35-b62f88cd2975@Spark> <7b5da8ab-346f-3231-f73f-95d0211f3a4a@opensips.org> <3b9338c1-3744-453e-9d6e-927eec786a18@opensips.org> <753ef653-2cc2-4a28-9777-4770a163e682@Spark> Message-ID: <5c9c3781-d7dd-fcdd-f9f4-02cc7214a80f@opensips.org> Hi Francisco, OK, the CP and TLS part now working ok, you moved into a different area, the MST one :P . have you checked https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ ? 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/17/22 7:55 PM, Francisco Neto wrote: > About the parameter "TLSv1-“ is everything ok, after the reload. No DB > errors. > > I’ve found another difficulties, but with the changes below open sips > is running fine with tls_mgm on db now. > > First I have change the memory parameter and start open sips with > 256mb of memory and package memory > > Them the error has changed again, and I discover that on the conf file > I have informed the “CA Directory”, so I fill it on the CP too and all > errors have disappeared. > > Now my difficult is to correctly establishes the communication with > microsoft teams. I don’t know what I’m doing wrong but MS are not > identifying my SIP options…. > > > > > Em 17 de ago. de 2022 13:17 -0300, Bogdan-Andrei Iancu > , escreveu: >> You can add extra methods in the combo, not a problem - the question >> is if opensips will understand it when loading from DB - do you see >> any errors on reload ? >> >> 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/17/22 5:52 PM, Francisco Neto wrote: >>> Hi Bogdan-Andrei!! >>> >>> I’ve made the changes on the code as you requested. On CP I could >>> fill the match_sip_domain With * and update the item, after that the >>> errors on log file have changed a lot now. >>> Below are the errors that are appearing to me now >>> >>> By the way, directly on the config file the SSL Method that works >>> better for me was “TLSv1-“. This option didn’t exist on >>> tviewer.inc.php, but I have created this option on the file. Does it >>> have any problem to add a new valid combo option?? >>> >>> Thanks! >>> >>> ERROR:proto_tls:proto_tls_send: failed to send >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:msg_send: >>> send() to 52.114.76.76:5061 for proto tls/3 failed >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: ERROR:tm:t_uac: >>> attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: >>> ERROR:tls_openssl:openssl_tls_connect: SSL_ERROR_SYSCALL >>> err=Resource temporarily unavailable(11) >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: >>> ERROR:tls_openssl:openssl_tls_connect: New TLS connection to >>> 52.114.76.76:5061 failed >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: >>> ERROR:tls_openssl:openssl_tls_connect: TLS error: 5 (ret=-1) >>> err=Resource temporarily unavailable(11) >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1948]: >>> ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: >>> ERROR:tls_openssl:openssl_tls_connect: New TLS connection to >>> 52.114.14.70:5061 failed >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: >>> ERROR:tls_openssl:openssl_tls_connect: TLS error: 1 (ret=-1) >>> err=Success(0) >>> Aug 17 11:49:15 bowser /usr/sbin/opensips[1958]: >>> ERROR:tls_openssl:tls_print_errstack: TLS errstack: >>> error:1416F086:SSL >>> routines:tls_process_server_certificate:certificate verify failed >>> >>> >>> Em 17 de ago. de 2022 04:29 -0300, Bogdan-Andrei Iancu >>> , escreveu: >>>> Hi Francisco, >>>> >>>> Please check >>>> https://github.com/OpenSIPS/opensips-cp/commit/1e738fd948fcc83004b0b99edb4f361c0a8b784c >>>> - update again and give it a try by adding "*" for the match_domain >>>> >>>> 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/16/22 11:32 PM, Francisco Neto wrote: >>>>> Hi Bogdan-Andrei! >>>>> >>>>> Actually I’ve tried with using sip domain as blank, with * it >>>>> didn’t let me press update on CP, and with the client certificate >>>>> (fqdn and domain part only) and in all scenarios the error is the >>>>> same as described below: >>>>> >>>>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>>>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>>>> conn 0x7efe29a648a8 >>>>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >>>>> socket >>>>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:proto_tls:proto_tls_send: connect failed >>>>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:tm:msg_send: send() to 52.114.132.46:5061 for proto tls/3 failed >>>>> Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>>>> attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>>>> conn 0x7efe29b341a8 >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >>>>> socket >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:proto_tls:proto_tls_send: connect failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:tm:msg_send: send() to 52.114.76.76:5061 for proto tls/3 failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>>>> attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >>>>> conn 0x7efe29a17ec8 >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >>>>> socket >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:proto_tls:proto_tls_send: connect failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >>>>> ERROR:tm:msg_send: send() to 52.114.14.70:5061 for proto tls/3 failed >>>>> Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >>>>> attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed >>>>> >>>>> Below is my actual config section about TLS >>>>> >>>>> loadmodule "proto_tls.so" >>>>> modparam("proto_tls","tls_max_msg_chunks", 8) >>>>> modparam("proto_tls","tls_handshake_timeout", 600) >>>>> modparam("proto_tls", "tls_send_timeout", 2000) >>>>> >>>>> >>>>> loadmodule "tls_openssl.so" >>>>> loadmodule "tls_mgm.so" >>>>> modparam("tls_mgm", >>>>> "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") >>>>> modparam("tls_mgm", "db_table", "tls_mgm") >>>>> modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") >>>>> >>>>> >>>>> Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu >>>>> , escreveu: >>>>>> 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 >>>>>>> >>>>>>> >>>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: A1273B7034F144E0939B236096040012.png Type: image/png Size: 8292 bytes Desc: not available URL: From ayakimkin at gmail.com Thu Aug 18 16:04:54 2022 From: ayakimkin at gmail.com (=?UTF-8?B?0JDQu9C10LrRgdC10Lkg0K/QutC40LzQutC40L0=?=) Date: Thu, 18 Aug 2022 19:04:54 +0300 Subject: [OpenSIPS-Users] Fwd: Mid_registrar wrong expires, and how to list saved contacts? In-Reply-To: References: Message-ID: Hello, I tried to set up the mid_registrar module. -- loadmodule "usrloc.so" modparam("usrloc", "nat_bflag", "NAT") modparam("usrloc", "working_mode_preset", "single-instance-no-db") loadmodule "mid_registrar.so" modparam("mid_registrar", "mode", 1) modparam("mid_registrar", "outgoing_expires", 7200) modparam("mid_registrar", "default_expires", 1800) ... if (is_method("REGISTER")) { mid_registrar_save("location"); xdbg("mid_registrar_save location 112211 $retcode \n"); switch ($retcode) { case 1: add_path_received(); xlog("forwarding REGISTER to main registrar ($$ci=$ci)\n"); $ru = "sip:172.19.19.120:5060"; route(relay); break; case 2: xlog("absorbing REGISTER! ($$ci=$ci)\n"); break; default: xlog("failed to save registration! ($$ci=$ci)\n"); } exit; } -- 1. I use outgoing_expires 7200. UA makes Register with Expires: 60 every 60sec. Opensips forwards all Register requests. And sometimes inserts Expires: 60 in forwarded Register request. 2. To my mind opensips was set up to store contact fields in memory. How can I list successful registered UAs from memory? Or I have to store contacts to DB? Maybe I did something wrong. -- Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From Li.Cai at comtech.com Thu Aug 18 16:41:46 2022 From: Li.Cai at comtech.com (Li Cai) Date: Thu, 18 Aug 2022 16:41:46 +0000 Subject: [OpenSIPS-Users] About obstacles to implement the matched Message-ID: Hi Vlad, Thanks for the reply, I'll give it a try. For now, I'm working on V2.4 source to implement, can I ask if it's not necessary and OpenSIPs 2.4 can do the function all by script? Thanks, Can I ask https://www.opensips.org/Documentation/Development-Tutorials -----Original Message----- From: Users On Behalf Of users-request at lists.opensips.org Sent: August 18, 2022 11:35 AM To: users at lists.opensips.org Subject: Users Digest, Vol 169, Issue 29 WARNING: External Email: Exercise Caution Send Users mailing list submissions to users at lists.opensips.org To subscribe or unsubscribe via the World Wide Web, visit https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964337652145158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=dhGsDxKcn2b7Lg2R9AVxUEJXcKkxFRC8oEvz6OgTuls%3D&reserved=0 or, via email, send a message with subject or body 'help' to users-request at lists.opensips.org You can reach the person managing the list at users-owner at lists.opensips.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." Today's Topics: 1. Re: About obstacles to implement the matched Id in event (Vlad Patrascu) 2. STOP waiting for new branches and close transaction by t_wait_no_more_branches() (Ярослав Нападайло) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Aug 2022 18:28:13 +0300 From: Vlad Patrascu To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] About obstacles to implement the matched Id in event Message-ID: Content-Type: text/plain; charset=UTF-8; format=flowed Hi Li, In 2.4 I think the only way is to use the same cachedb_local storage for everything you need to pass around. Regards, -- Vlad Patrascu OpenSIPS Core Developer https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964337652145158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f%2BoWZ0jIHjPq7sb4XRZXjjK0w0uPxGjzAR7aU0%2FLPPQ%3D&reserved=0 On 18.08.2022 16:59, Li Cai wrote: > Hi Vlad, > > Thank you very much for the suggestion. Sorry that I didn't mention our OpenSIPs version, we're with 2.4 which doesn't provide exported pseudo variables. Can I ask if there is similar way to do so in V2.4? > > > Thanks, > Li > > -----Original Message----- > From: Users On Behalf Of > users-request at lists.opensips.org > Sent: August 17, 2022 3:29 AM > To: users at lists.opensips.org > Subject: Users Digest, Vol 169, Issue 25 > > > WARNING: External Email: Exercise Caution > > Send Users mailing list submissions to > users at lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists > .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01% > 7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696a > e040c1bd801ca6cc677828%7C0%7C0%7C637964337652145158%7CUnknown%7CTWFpbG > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% > 3D%7C3000%7C%7C%7C&sdata=dhGsDxKcn2b7Lg2R9AVxUEJXcKkxFRC8oEvz6OgTu > ls%3D&reserved=0 or, via email, send a message with subject or > body 'help' to > users-request at lists.opensips.org > > You can reach the person managing the list at > users-owner at lists.opensips.org > > When replying, please edit your Subject line so it is more specific than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Re: About obstacles to implement the matched Id in event > header of NOTIFY(REFER) (Vlad Patrascu) > 2. Re: Bug on TLS Management Interface (Bogdan-Andrei Iancu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Aug 2022 22:19:10 +0300 > From: Vlad Patrascu > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] About obstacles to implement the matched > Id in event header of NOTIFY(REFER) > Message-ID: <91e7202d-ac0f-9ab3-252e-49640130aae4 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Li, > > For passing around data between the b2b request route and local_route, in the context of an ongoing B2B session, you can use the $b2b_logic.ctx variable[1]. That would take care of transferring the Cseq from step 1 to step 2 and the id from step 3 to step 4. > > As for your cseq map, you can use the cachedb_local module, and maybe the $b2b_logic.key variable alongside Cseq2 for building a proper key. > > [1] > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopen > sips.org%2Fdocs%2Fmodules%2F3.3.x%2Fb2b_logic.html%23b2b_logic.key& > ;data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5ad > f%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964337652145158%7CUn > known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW > wiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vnGjPkRw2UUd7GyN%2FlF1vAdqf > z%2BEF2Yo43Hb3pF8VW4%3D&reserved=0 > > Regards, > > -- > Vlad Patrascu > OpenSIPS Core Developer > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.o > pensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C49b > 812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7 > C0%7C637964337652145158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC > JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > =f%2BoWZ0jIHjPq7sb4XRZXjjK0w0uPxGjzAR7aU0%2FLPPQ%3D&reserved=0 > > On 22.07.2022 23:02, 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 >> https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flist >> s >> .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01 >> % >> 7Cli.cai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696 >> a >> e040c1bd801ca6cc677828%7C0%7C0%7C637963181666956869%7CUnknown%7CTWFpb >> G >> Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0 >> % >> 3D%7C3000%7C%7C%7C&sdata=eN7ZRHTe3r03mOVKSiQdmxv8EEwIm7QS957iAccx >> u >> dA%3D&reserved=0 > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > s.opensips.org%2Fpipermail%2Fusers%2Fattachments%2F20220816%2F8eef3031 > %2Fattachment-0001.html&data=05%7C01%7Cli.cai%40comtech.com%7C49b8 > 12e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C > 0%7C637964337652145158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ > QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata= > kVUBOjMwScxOV9qf32nQuFP%2BjJhmyroGXUBDmyAv7GA%3D&reserved=0> > > ------------------------------ > > Message: 2 > Date: Wed, 17 Aug 2022 10:28:49 +0300 > From: Bogdan-Andrei Iancu > To: Francisco Neto , "users at lists.opensips.org" > > Subject: Re: [OpenSIPS-Users] Bug on TLS Management Interface > Message-ID: <7b5da8ab-346f-3231-f73f-95d0211f3a4a at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Francisco, > > Please check > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2FOpenSIPS%2Fopensips-cp%2Fcommit%2F1e738fd948fcc83004b0b99edb4 > f361c0a8b784c&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada442 > 7660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964 > 337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM > zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6%2FL1VuTm > HD9xKn8z%2FtohNEAVTTH7OSxffrwmoIfS1ac%3D&reserved=0 > - update again and give it a try by adding "*" for the match_domain > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7C49 > b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0% > 7C0%7C637964337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL > CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat > a=%2FT58YDeqLR%2BPizwW%2BflydhlS7MNUxx79NfC%2BwcAvaBU%3D&reserved= > 0 OpenSIPS Summit 27-30 Sept 2022, Athens > > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli.cai > %40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd > 801ca6cc677828%7C0%7C0%7C637964337652301390%7CUnknown%7CTWFpbGZsb3d8ey > JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > 0%7C%7C%7C&sdata=W2gn8TaGQiE5xetB5r2KLDEryFqks%2BCd8gBW%2FfMtORQ%3 > D&reserved=0 > > On 8/16/22 11:32 PM, Francisco Neto wrote: >> Hi Bogdan-Andrei! >> >> Actually I've tried with using sip domain as blank, with * it didn't >> let me press update on CP, and with the client certificate (fqdn and >> domain part only) and in all scenarios the error is the same as >> described below: >> >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug >> 16 >> 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29a648a8 Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:30 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:30 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.132.46:5061 for proto tls/3 failed Aug 16 17:29:30 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip.pstnhub.microsoft.com:5061' failed Aug 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug >> 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29b341a8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.76.76:5061 for proto tls/3 failed Aug 16 17:29:31 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip2.pstnhub.microsoft.com:5061' failed Aug >> 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found Aug >> 16 >> 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_conn_create: failed to do proto 3 specific init for >> conn 0x7efe29a17ec8 Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the >> socket Aug 16 17:29:31 bowser /usr/sbin/opensips[1128]: >> ERROR:proto_tls:proto_tls_send: connect failed Aug 16 17:29:31 bowser >> /usr/sbin/opensips[1128]: ERROR:tm:msg_send: >> send() to 52.114.14.70:5061 for proto tls/3 failed Aug 16 17:29:31 >> bowser /usr/sbin/opensips[1128]: ERROR:tm:t_uac: >> attempt to send to 'sip:sip3.pstnhub.microsoft.com:5061' failed >> >> Below is my actual config section about TLS >> >> loadmodule "proto_tls.so" >> modparam("proto_tls","tls_max_msg_chunks", 8) >> modparam("proto_tls","tls_handshake_timeout", 600) >> modparam("proto_tls", "tls_send_timeout", 2000) >> >> >> loadmodule "tls_openssl.so" >> loadmodule "tls_mgm.so" >> modparam("tls_mgm", >> "db_url","mysql://opensips:XXXXXXXXXX at localhost/opensips") >> modparam("tls_mgm", "db_table", "tls_mgm") modparam("tls_mgm", >> "client_sip_domain_avp", "tls_sip_dom") >> >> >> Em 11 de ago. de 2022 12:59 -0300, Bogdan-Andrei Iancu >> , escreveu: >>> 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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww >>> w >>> .opensips-solutions.com%2F&data=05%7C01%7Cli.cai%40comtech.com%7 >>> C >>> 502ac1e5f328416b934908da80223535%7Ca9a26e696ae040c1bd801ca6cc677828% >>> 7 >>> C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw >>> M >>> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&am >>> p >>> ;sdata=yp8rIlD05HWeQxkUb1ecaQtQLEdzoqz10UmhgzBTC7A%3D&reserved=0 >>> OpenSIPS Summit 27-30 Sept 2022, Athens >>> >>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww >>> w >>> .opensips.org%2Fevents%2FSummit-2022Athens%2F&data=05%7C01%7Cli. >>> c >>> ai%40comtech.com%7C502ac1e5f328416b934908da80223535%7Ca9a26e696ae040 >>> c >>> 1bd801ca6cc677828%7C0%7C0%7C637963181667269467%7CUnknown%7CTWFpbGZsb >>> 3 >>> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D >>> % >>> 7C3000%7C%7C%7C&sdata=7HvX9ki%2Bj7QuwBkT%2FuX2upmCyCxHkm9bR26YsI >>> y >>> CCVs%3D&reserved=0 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 >>>> >>>> > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > s.opensips.org%2Fpipermail%2Fusers%2Fattachments%2F20220817%2Fbbe12cad > %2Fattachment.html&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9a > da4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C6 > 37964337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi > V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GyFtv > tIuADNsGUfFzSqOO%2FvLxrT63H%2BegQe%2Bivlgfn8%3D&reserved=0> > -------------- next part -------------- A non-text attachment was > scrubbed... > Name: F4F396411D0249C49A1BE4F226E20C17.png > Type: image/png > Size: 8292 bytes > Desc: not available > URL: > s.opensips.org%2Fpipermail%2Fusers%2Fattachments%2F20220817%2Fbbe12cad > %2Fattachment.png&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ad > a4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C63 > 7964337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QJuYBo > 7QMoZuK6aoNLk3bYRSBHocp54BNLT5CZsTcZM%3D&reserved=0> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists > .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01% > 7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696a > e040c1bd801ca6cc677828%7C0%7C0%7C637964337652301390%7CUnknown%7CTWFpbG > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% > 3D%7C3000%7C%7C%7C&sdata=wN7P70KRsejGBHYGtEeneYrffV2HdbabEHGNjmIm2 > k0%3D&reserved=0 > > > ------------------------------ > > End of Users Digest, Vol 169, Issue 25 > ************************************** > NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and / or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists > .opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01% > 7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696a > e040c1bd801ca6cc677828%7C0%7C0%7C637964337652301390%7CUnknown%7CTWFpbG > Zsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0% > 3D%7C3000%7C%7C%7C&sdata=wN7P70KRsejGBHYGtEeneYrffV2HdbabEHGNjmIm2 > k0%3D&reserved=0 ------------------------------ Message: 2 Date: Fri, 12 Aug 2022 18:12:35 +0600 From: Ярослав Нападайло To: users at lists.opensips.org Subject: [OpenSIPS-Users] STOP waiting for new branches and close transaction by t_wait_no_more_branches() Message-ID: Content-Type: text/plain; charset="utf-8" Hi everybody! I'm writing script with Push Notification mechanism using TM module and t_wait_for_new_branches() function and EBR. Here example in docs https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensips.org%2Fdocs%2Fmodules%2F3.2.x%2Fevent_routing.html%23idp5576704&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=H%2F9rI%2Fvl%2FIPxuDHOj%2BAMYfzTa28bXb%2Bc4ykpkKZzhoY%3D&reserved=0 My is: route { ... t_newtran(); .... create_dialog(); ... t_on_reply("HANDLE_REPLY"); t_wait_for_new_branches(); .... notify_on_event("E_UL_CONTACT_INSERT", $avp(filter), "fork_call", $var(ttl)); } onreply_route[HANDLE_REPLY] { xlog("L_DBG", "received reply $rs $rr"); switch($rs) { case "486": xlog("L_DBG", "wait no more branches DLG_DID=$DLG_did"); t_wait_no_more_branches(); t_cancel_branch("a"); break; default: } } route[fork_call] { xlog("L_DBG", "[$ci] user $avp(aor) registered a new contact $avp(uri), injecting"); t_inject_branches("event"); } First, I create dialog. Then, call t_wait_for_new_branches() and set notify_on_event() handler. Then I'm waiting for new REGISTERs. When new contacts register to usrloc, I'm injecting received contacts as new branches to current transaction. I do all things as described in docs. Now I want to control negative replies from ongoing branches. By default, OS ignores negative replies and continue waiting for new branches. For example, I want to ignore 480, but handle 486. I try handle 486, calling t_wait_no_more_branches(). I expect that OS will stop waiting for new branches and t_inject_branches will not add anymore. Also I expect that OS stop PHONY branch, which is created first when calling t_wait_for_new_branches(), and sends final response (486 in my case) to caller. But in real next things happen: 1. t_wait_no_more_branches() doesn't affect adding new branches. If 1st callee reject call, then 2nd callee register new contact, t_inject_branches() adds new branch all the same 2. If no other branches added, caller hears ringing until FR_INV_TIMEOUT expires. And only when FR_INV_TIMEOUT expires, OS sends final response to caller. WIDW?? How to stop transaction immeditially when at least one ongoing branch reply 486 code and to wait no more for any branches? Thx for answers -- Regards, Yaroslav Napadilo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Users mailing list Users at lists.opensips.org https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opensips.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fusers&data=05%7C01%7Cli.cai%40comtech.com%7C49b812e9ada4427660e208da812f5adf%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637964337652301390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wN7P70KRsejGBHYGtEeneYrffV2HdbabEHGNjmIm2k0%3D&reserved=0 ------------------------------ End of Users Digest, Vol 169, Issue 29 ************************************** From bogdan at opensips.org Fri Aug 19 14:29:33 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 19 Aug 2022 17:29:33 +0300 Subject: [OpenSIPS-Users] STOP waiting for new branches and close transaction by t_wait_no_more_branches() In-Reply-To: References: Message-ID: Hi, So recap'ing the scenario here: When you get the initial incoming INVITE, you do not send out any branch. All the outbound branches are created via the t_inject, right ? So INVITE come in, nothing, then the REGISTER triggeres a new branch, and this new branch gets replied with 486. And you want to stop the waiting at this point, right ? 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/12/22 3:12 PM, Ярослав Нападайло via Users wrote: > Hi everybody! > > I'm writing script with Push Notification mechanism using TM module > and t_wait_for_new_branches() function and EBR. > Here example in docs > https://opensips.org/docs/modules/3.2.x/event_routing.html#idp5576704 > > > My  is: > > route { >       ... >       t_newtran(); >       .... >       create_dialog(); >       ... >       t_on_reply("HANDLE_REPLY"); >       t_wait_for_new_branches(); >       .... >       notify_on_event("E_UL_CONTACT_INSERT", $avp(filter), > "fork_call", $var(ttl)); > } > > onreply_route[HANDLE_REPLY] { >   xlog("L_DBG", "received reply $rs $rr"); >   switch($rs) { >     case "486": >       xlog("L_DBG", "wait no more branches DLG_DID=$DLG_did"); >       t_wait_no_more_branches(); >       t_cancel_branch("a"); >       break; >     default: >   } > } > > route[fork_call] { >   xlog("L_DBG", "[$ci] user $avp(aor) registered a new contact > $avp(uri), injecting"); >   t_inject_branches("event"); > } > > First, I create dialog. Then, call t_wait_for_new_branches() and set > notify_on_event() handler. > Then I'm waiting for new REGISTERs. When new contacts register to > usrloc, I'm injecting received contacts as new branches to current > transaction. > I do all things as described in docs. > Now I want to control negative replies from ongoing branches. By > default, OS ignores negative replies and continue waiting for new > branches. For example, I want to ignore 480, but handle 486. > I try handle 486, calling t_wait_no_more_branches(). > I expect that OS will stop waiting for new branches and > t_inject_branches  will not add anymore. > Also I expect that OS stop PHONY branch, which is created first when > calling t_wait_for_new_branches(), and sends final response (486 in my > case) to caller. > But in real next things happen: > 1. t_wait_no_more_branches() doesn't affect adding new branches. If > 1st callee reject call, then 2nd callee register new contact, > t_inject_branches() adds new branch all the same > 2. If no other branches added, caller hears ringing until > FR_INV_TIMEOUT expires. And only when FR_INV_TIMEOUT expires, OS sends > final response to caller. > > WIDW?? > > How to stop transaction immeditially when at least one ongoing branch > reply 486 code and to wait no more for any branches? > Thx for answers > > -- > Regards, > Yaroslav Napadilo > > _______________________________________________ > 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: From ayakimkin at gmail.com Fri Aug 19 15:12:18 2022 From: ayakimkin at gmail.com (Alex) Date: Fri, 19 Aug 2022 18:12:18 +0300 Subject: [OpenSIPS-Users] b2bua top hiding behind NAT Message-ID: Hello, My opensips is behind NAT in cloud internet - (1.1.1.1)Cone_NAT - port_5060__10.130.0.23(opensips)__port_5070 - main_registrar_sip_server So I made 2 sockets socket=udp:10.130.0.23:5070 # for LAN socket=udp:10.130.0.23:5060 as 1.1.1.1:5060 #for Internet I try to make call from lan to Tel provider with using b2bua. Is any way to setup b2bua with more than one socket? loadmodule "b2b_entities.so" loadmodule "b2b_logic.so" modparam("b2b_logic", "custom_headers", "P-Asserted-Identity") #"User-Agent;Date") #modparam("b2b_logic", "contact_user", 1) modparam("b2b_logic", "server_address", "sip:1234567 at 1.1.1.1") #force_send_socket("udp:10.130.23:5060"); b2b_server_new("server1",$avp(b2b_hdrs), $avp(b2b_hdr_bodies)); force_send_socket("udp:10.130.23:5060"); b2b_client_new("Unistar"," sip:09876543322 at provider.com","sip:provider","test","sip:1234567 at 1.1.1.1"); #force_send_socket("udp:10.130.23:5070"); b2b_init_request("top hiding"); exit; I use this construction in route[relay]. And I`ve tried to insert in before b2b_server_new. But it didn`t help if ($socket_in == "udp:10.130.0.23:5070") { $socket_out = "udp:10.130.0.23:5060"; } else { $socket_out = "udp:10.130.0.23:5070"; } 1) with force_send_socket I made to send requests from :5070 to :5060 . But my provider`s Udpates and re-Invites go to my LAN directly from socket :5060 . They don`t go through :5070 2) I can`t change contact in request to provider. Default contact looks like this Contact: . I whant to change to "sip:1234567 at 1.1.1.1 " -- С уважением, Якимкин Алексей -------------- next part -------------- An HTML attachment was scrubbed... URL: From ayakimkin at gmail.com Fri Aug 19 15:43:31 2022 From: ayakimkin at gmail.com (Alex) Date: Fri, 19 Aug 2022 18:43:31 +0300 Subject: [OpenSIPS-Users] Loadbalancer for Registrations and calls In-Reply-To: References: Message-ID: Hello, setup mid registrar easy with this instruction. https://www.opensips.org/Documentation/Tutorials-MidRegistrar There is link to config But It relays every Registration request every 60sec on my server. Please let me know if you could set up like on picture in instruction. чт, 18 авг. 2022 г. в 18:37, Kevin Kennedy : > I am looking for a configuration to be able to front end multiple SBC's to > load balance Registrations and keep track of them to send INVITE's to the > corresponding SBC. > > I am thinking of using a combination of Dispatcher and midregister, but > not sure how to set this up correctly. > > Any thoughts? > > Thank you. > > Kevin > _______________________________________________ > 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: From spanda at 3clogic.com Mon Aug 22 05:44:24 2022 From: spanda at 3clogic.com (Sasmita Panda) Date: Mon, 22 Aug 2022 11:14:24 +0530 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . Message-ID: Hi All , I am using opensips 3.2 for fullsharing_cachedb clustering . Here I am using mongo DB as the cache db . I have 2 mongodb clusters , One is primary (read/write) and second is secondary (read replicas )cluster . modparam("usrloc", "cachedb_url","mongodb:// docdb:cccl0g1c at primay-cluster.i3clogic.com:27017, secondary-cluster.i3clogic.com:27017/opensipsDB.userlocation?replicaSet=rs0&readPreference=secondaryPreferred&retryWrites=false ") When I am configuring 2 connectionstrings here , that means 1. Opensips will always honor the 1st one as primary and 2nd one as secondary ? 2. If the 1st one will get down and 2nd one becomes primary , what will happen to opensips ? Will that keep the 2nd one as primary automatically or I have to switch the domain in the config ? 3. How does opensips decide which one is primary and which is secondary ? Please help me out . I am stuck in the middle of something here . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingsley at dns99.co.uk Mon Aug 22 16:54:06 2022 From: kingsley at dns99.co.uk (Kingsley Tart) Date: Mon, 22 Aug 2022 17:54:06 +0100 Subject: [OpenSIPS-Users] high res timestamps in /var/log/opensips log entries Message-ID: Hi, is it possible to get log entries in /var/log/opensips.log to include high res timestamps? I'm not talking about log entries that I create myself with xlog(), but ones that OpenSIPS itself generates when something fails, for example. I would find it useful to check more precise timing of errors to the high res timestamps available when looking at packet times in a pcap. Cheers, Kingsley. From bogdan at opensips.org Tue Aug 23 09:35:20 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 23 Aug 2022 12:35:20 +0300 Subject: [OpenSIPS-Users] high res timestamps in /var/log/opensips log entries In-Reply-To: References: Message-ID: <46237ab3-1b6f-13bb-6793-be770947356d@opensips.org> Hi Kingsly, The logging is done via syslog and the date / time part is actually added by the syslog service, not by OpenSIPS. 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/22/22 7:54 PM, Kingsley Tart wrote: > Hi, > > is it possible to get log entries in /var/log/opensips.log to include > high res timestamps? > > I'm not talking about log entries that I create myself with xlog(), but > ones that OpenSIPS itself generates when something fails, for example. > > I would find it useful to check more precise timing of errors to the > high res timestamps available when looking at packet times in a pcap. > > Cheers, > Kingsley. > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Tue Aug 23 09:43:53 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 23 Aug 2022 12:43:53 +0300 Subject: [OpenSIPS-Users] b2bua top hiding behind NAT In-Reply-To: References: Message-ID: <914ddad5-357f-bf99-4321-9f9649f3ec24@opensips.org> Hi Alex, Have you tried something like this (for calls from Internet) : b2b_server_new("server1",$avp(b2b_hdrs), $avp(b2b_hdr_bodies)); force_send_socket("udp:10.130.23:5070"); b2b_client_new("Unistar","sip:09876543322 at provider.com ","sip:provider","test","sip:1234567 at 1.1.1.1 "); b2b_init_request("top hiding"); 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/19/22 6:12 PM, Alex wrote: > Hello, > > My opensips is behind NAT in cloud > internet - (1.1.1.1)Cone_NAT - > port_5060__10.130.0.23(opensips)__port_5070 - main_registrar_sip_server > > So I made 2 sockets > socket=udp:10.130.0.23:5070   # for LAN > socket=udp:10.130.0.23:5060 as 1.1.1.1:5060 > #for Internet > > I try to make call from lan to Tel provider with using b2bua. > > Is any way to setup b2bua with more than one socket? > > loadmodule "b2b_entities.so" > loadmodule "b2b_logic.so" > modparam("b2b_logic", "custom_headers", "P-Asserted-Identity") > #"User-Agent;Date") > #modparam("b2b_logic", "contact_user", 1) > modparam("b2b_logic", "server_address", "sip:1234567 at 1.1.1.1 > ") > > > #force_send_socket("udp:10.130.23:5060"); > b2b_server_new("server1",$avp(b2b_hdrs), $avp(b2b_hdr_bodies)); > force_send_socket("udp:10.130.23:5060"); > b2b_client_new("Unistar","sip:09876543322 at provider.com > ","sip:provider","test","sip:1234567 at 1.1.1.1 > "); > #force_send_socket("udp:10.130.23:5070"); > b2b_init_request("top hiding"); > exit; > > I use this construction in route[relay]. And I`ve tried to insert in > before b2b_server_new. But  it didn`t help > if ($socket_in == "udp:10.130.0.23:5070 ") { >                 $socket_out = "udp:10.130.0.23:5060 > "; >         } else { >                 $socket_out = "udp:10.130.0.23:5070 > "; >         } > > 1) with force_send_socket I made to send requests from :5070 to :5060 > . But my provider`s Udpates and re-Invites go to my LAN directly from > socket :5060 . They don`t go  through :5070 > 2) I can`t change contact in request to provider. Default contact > looks like this Contact: . I whant to change to > "sip:1234567 at 1.1.1.1 " > > -- > С уважением, > Якимкин Алексей > > _______________________________________________ > 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: From liviu at opensips.org Tue Aug 23 10:01:51 2022 From: liviu at opensips.org (Liviu Chircu) Date: Tue, 23 Aug 2022 13:01:51 +0300 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: References: Message-ID: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> On 22.08.2022 08:44, Sasmita Panda wrote: > > When I am configuring 2 connectionstrings here , that means > 1. Opensips will always honor the 1st one as primary and 2nd one as > secondary ? > > 2. If the 1st one will get down and 2nd one becomes primary , what > will happen to opensips ? Will that keep the 2nd one as primary > automatically or I have to switch the domain in the config ? > > 3. How does opensips decide which one is primary and which is secondary ? > > Please help me out . I am stuck in the middle of something here . Hi Sasmita, This has more to do with the libmongoc library behavior, rather than OpenSIPS.  First, the multi-host replica set syntax is part of the MongoDB connection string syntax[1], so everything that you can read on the Mongo website also applies to the "cachedb_mongodb" module. 1. This means that once you include the "replicaSet=rs0" component, the library will automatically establish who is the PRIMARY node on each query.  If the PRIMARY should ever change (either due to system failure, manual switch, etc.), the library will be able to switch to the new PRIMARY, whichever that may become (imagine you have a 5-node replica set). 2. no need to change the config string. The library will always know which is the PRIMARY (writer) node. 3. I cannot say... I image the library will connect to each node and run an "isMaster()"[2] command?  I suggest you do an ngrep or even a PCAP capture - that should give you more info on libmongoc behavior. [1]: https://www.mongodb.com/docs/v5.2/reference/connection-string/ [2]: https://www.mongodb.com/docs/v4.2/reference/command/isMaster/ Best regards, -- Liviu Chircu www.twitter.com/liviuchircu | www.opensips-solutions.com OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events From bogdan at opensips.org Tue Aug 23 14:09:13 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 23 Aug 2022 17:09:13 +0300 Subject: [OpenSIPS-Users] OpenSIPS Summit - the thrill of re-connecting Message-ID: <5224b993-8d84-0dca-ae0b-e714bb78aa5a@opensips.org> I'm so anxious to participate again to an in-person conference, to re-connect with all the people around, to chat and brainstorm..... there are so many reasons to look forward to be in Athens for OpenSIPS Summit... https://blog.opensips.org/2022/08/23/opensips-summit-the-thrill-of-re-connecting/ Re-connect with you in Athens! -- 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/ From Li.Cai at comtech.com Tue Aug 23 19:34:39 2022 From: Li.Cai at comtech.com (Li Cai) Date: Tue, 23 Aug 2022 19:34:39 +0000 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module Message-ID: Hi, I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the function is supported or if it has been supported in the later versions. We have used the MI command b2b_bridge to bridge existing calls from one entity to another and it works, the scenario is the same as expected. While besides this, we also need to modify one of the headers of the INVITEs sending to the new destination in this scenario, our scripts in the opensips.cfg can't take any effect. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hunterj91 at hotmail.com Tue Aug 23 21:24:52 2022 From: hunterj91 at hotmail.com (Jonathan Hunter) Date: Tue, 23 Aug 2022 21:24:52 +0000 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment Message-ID: Hi All, I have a query around dispatcher behaviour, I am running 3.2 in a k8s environment. I have 2 freeswitch instances defined in a destination set, both of which are pods. As people may be aware its fun implementing in k8s as pods can restart and disappear at times so I ideally want this reflected in the cache and output of opensips-cli -x mi ds_list where I was hoping the freeswitch entries would be defined but with a state of probing or inactive. With my current setup, when restarting opensips for example, I have the dispatcher table populated in postgres db , and if opensips cant resolve the URI it wont load it into cache, like wise if opensips is running and freeswitch pod drops, I see this in the logs; Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add destination in group 10 I therefore don’t see it listed in cache when I run ds_list. Does anyone know if its possible to tweak dispatcher to always load the database entries into cache at startup, and also set their status to probing/inactive if not reachable due to a resolving issue as above? My dispatcher settings are; #### Dynamic routing loadmodule "dispatcher.so" modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold", 1) modparam("dispatcher", "persistent_state", 0) modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "cluster_id", 1) Hope that makes sense! Many thanks Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: From spanda at 3clogic.com Wed Aug 24 08:56:58 2022 From: spanda at 3clogic.com (Sasmita Panda) Date: Wed, 24 Aug 2022 14:26:58 +0530 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> References: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> Message-ID: Hi Liviu , I have mapped a domain in AWS route53 primary-clsuter.xyz.com to mongodb primary cluster connection string . Now my primary cluster goes down so my secondary cluster becomes primary . I have updated the connection string against the domain in route53 . Now *primary-cluster.xzy.com * is pointed to the new primary custer connection string . While creating a connection from the console through the mongo shell it's getting connected . But opensips is not able to switch the connecting string somehow . still it's trying to connect to the previous primary connection string . It seems like opensips has cached the connection string and is trying to connect to the same even after I have updated the string from the backend . Once I restart the opensips service everything starts working and the connection string was updated to the latest primary cluster connection string . How will I manage this ? *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Tue, Aug 23, 2022 at 3:31 PM Liviu Chircu wrote: > On 22.08.2022 08:44, Sasmita Panda wrote: > > > > When I am configuring 2 connectionstrings here , that means > > 1. Opensips will always honor the 1st one as primary and 2nd one as > > secondary ? > > > > 2. If the 1st one will get down and 2nd one becomes primary , what > > will happen to opensips ? Will that keep the 2nd one as primary > > automatically or I have to switch the domain in the config ? > > > > 3. How does opensips decide which one is primary and which is secondary ? > > > > Please help me out . I am stuck in the middle of something here . > > Hi Sasmita, > > This has more to do with the libmongoc library behavior, rather than > OpenSIPS. First, the multi-host replica set syntax is part of the > MongoDB connection string syntax[1], so everything that you can read on > the Mongo website also applies to the "cachedb_mongodb" module. > > 1. This means that once you include the "replicaSet=rs0" component, the > library will automatically establish who is the PRIMARY node on each > query. If the PRIMARY should ever change (either due to system failure, > manual switch, etc.), the library will be able to switch to the new > PRIMARY, whichever that may become (imagine you have a 5-node replica set). > > 2. no need to change the config string. The library will always know > which is the PRIMARY (writer) node. > > 3. I cannot say... I image the library will connect to each node and run > an "isMaster()"[2] command? I suggest you do an ngrep or even a PCAP > capture - that should give you more info on libmongoc behavior. > > [1]: https://www.mongodb.com/docs/v5.2/reference/connection-string/ > [2]: https://www.mongodb.com/docs/v4.2/reference/command/isMaster/ > > 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: From liviu at opensips.org Wed Aug 24 10:00:01 2022 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 24 Aug 2022 13:00:01 +0300 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: References: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> Message-ID: On 24.08.2022 11:56, Sasmita Panda wrote: > > Now my primary cluster goes down so my secondary cluster becomes > primary . I have updated the connection string against the domain in > route53 . Now > *primary-cluster.xzy.com * is pointed > to the new primary custer connection string . > > While creating a connection from the console through the mongo shell > it's getting connected . But opensips is not able to switch the > connecting string somehow . still it's trying to connect to the > previous primary connection string . > > It seems like opensips has cached the connection string and is trying > to connect to the same even after I have updated the string from the > backend . libmongo will try each node in your CSV of nodes, there is no going around this.  Now, while your usage of two completely different clusters in the same connection string seems to be *non-conventional* (I don't recall any documentation advising this, all Mongo docs talk about connecting to either a *replica set*, or to a *list of* *mongos* servers), I still think it could work.  Maybe just configure the "connectionTimeousMS" parameters (or others??) and see if you can get libmongoc to time out faster on your 1st cluster, when it goes down. 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: From johan at democon.be Wed Aug 24 10:16:59 2022 From: johan at democon.be (johan) Date: Wed, 24 Aug 2022 12:16:59 +0200 Subject: [OpenSIPS-Users] opensips-cli debian 11 Message-ID: Liviu, is there already a repo for opensips-cli on debian 11 ? Secondly, if the old repo would work on debian 11, can  you please put a pub key ? Get:4 https://apt.opensips.org jammy InRelease [21.9 kB] Err:4 https://apt.opensips.org jammy InRelease   The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 81CE21E7049AD65B Reading package lists... Done W: GPG error: https://apt.opensips.org jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 81CE21E7049AD65B E: The repository 'https://apt.opensips.org jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. wkr, wkr, From johan at democon.be Wed Aug 24 10:42:16 2022 From: johan at democon.be (johan) Date: Wed, 24 Aug 2022 12:42:16 +0200 Subject: [OpenSIPS-Users] opensips-cli debian 11 In-Reply-To: References: Message-ID: <056fcb3a-c92a-daf2-0647-a97bc802ca75@democon.be> the old repo gives errors on bullseye. root at sipp:/etc/apt/sources.list.d# apt install opensips-cli Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed:   libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel   python3-cffi python3-cffi-backend python3-cryptography python3-dateutil   python3-infinity python3-mysqldb python3-openssl python3-ply   python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy   python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz Suggested packages:   python-arrow-doc python-cryptography-doc python3-cryptography-vectors   python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc   python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql   python3-psycopg2 python-sqlalchemy-utils-doc The following NEW packages will be installed:   libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow   python3-babel python3-cffi python3-cffi-backend python3-cryptography   python3-dateutil python3-infinity python3-mysqldb python3-openssl   python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql   python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils   python3-tz 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. Need to get 7,133 kB of archives. After this operation, 38.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64 13.7-0+deb11u1 [180 kB] Get:2 http://deb.debian.org/debian bullseye/main amd64 python3-sqlalchemy all 1.3.22+ds1-1 [795 kB] Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all 0.1~20220822~a480e53-1 [41.3 kB] Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson all 0.3.3-2 [8,196 B] Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil all 2.8.1-6 [79.2 kB] Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all 0.17.0-1 [50.7 kB] Get:7 http://deb.debian.org/debian bullseye/main amd64 python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB] Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all 2021.1-1 [34.8 kB] Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all 2.8.0+dfsg.1-7 [100 kB] Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity all 1.5-2 [4,364 B] Get:11 http://deb.debian.org/debian bullseye/main amd64 python3-cffi-backend amd64 1.14.5-1 [85.8 kB] Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all 3.11-4 [65.5 kB] Get:13 http://deb.debian.org/debian bullseye/main amd64 python3-pycparser all 2.20-3 [74.5 kB] Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all 1.14.5-1 [87.9 kB] Get:15 http://deb.debian.org/debian bullseye/main amd64 python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB] Get:16 http://deb.debian.org/debian bullseye/main amd64 python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB] Get:17 http://deb.debian.org/debian bullseye/main amd64 python3-cryptography amd64 3.3.2-1 [223 kB] Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl all 20.0.1-1 [53.7 kB] Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb amd64 1.4.4-2+b3 [57.0 kB] Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql all 0.9.3-2 [43.4 kB] Get:21 http://deb.debian.org/debian bullseye/main amd64 python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB] Fetched 7,133 kB in 14s (519 kB/s)                                              Selecting previously unselected package libpq5:amd64. (Reading database ... 163371 files and directories currently installed.) Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ... Unpacking libpq5:amd64 (13.7-0+deb11u1) ... Selecting previously unselected package python3-sqlalchemy. Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ... Unpacking python3-sqlalchemy (1.3.22+ds1-1) ... Selecting previously unselected package python3-anyjson. Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ... Unpacking python3-anyjson (0.3.3-2) ... Selecting previously unselected package python3-dateutil. Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ... Unpacking python3-dateutil (2.8.1-6) ... Selecting previously unselected package python3-arrow. Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ... Unpacking python3-arrow (0.17.0-1) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ... Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ... Selecting previously unselected package python3-tz. Preparing to unpack .../06-python3-tz_2021.1-1_all.deb ... Unpacking python3-tz (2021.1-1) ... Selecting previously unselected package python3-babel. Preparing to unpack .../07-python3-babel_2.8.0+dfsg.1-7_all.deb ... Unpacking python3-babel (2.8.0+dfsg.1-7) ... Selecting previously unselected package python3-infinity. Preparing to unpack .../08-python3-infinity_1.5-2_all.deb ... Unpacking python3-infinity (1.5-2) ... Selecting previously unselected package python3-cffi-backend:amd64. Preparing to unpack .../09-python3-cffi-backend_1.14.5-1_amd64.deb ... Unpacking python3-cffi-backend:amd64 (1.14.5-1) ... Selecting previously unselected package python3-ply. Preparing to unpack .../10-python3-ply_3.11-4_all.deb ... Unpacking python3-ply (3.11-4) ... Selecting previously unselected package python3-pycparser. Preparing to unpack .../11-python3-pycparser_2.20-3_all.deb ... Unpacking python3-pycparser (2.20-3) ... Selecting previously unselected package python3-cffi. Preparing to unpack .../12-python3-cffi_1.14.5-1_all.deb ... Unpacking python3-cffi (1.14.5-1) ... Selecting previously unselected package python3-psycopg2cffi. Preparing to unpack .../13-python3-psycopg2cffi_2.8.1-2_amd64.deb ... Unpacking python3-psycopg2cffi (2.8.1-2) ... Selecting previously unselected package python3-sqlalchemy-utils. Preparing to unpack .../14-python3-sqlalchemy-utils_0.36.8-4_all.deb ... Unpacking python3-sqlalchemy-utils (0.36.8-4) ... Selecting previously unselected package python3-cryptography. Preparing to unpack .../15-python3-cryptography_3.3.2-1_amd64.deb ... Unpacking python3-cryptography (3.3.2-1) ... Selecting previously unselected package python3-openssl. Preparing to unpack .../16-python3-openssl_20.0.1-1_all.deb ... Unpacking python3-openssl (20.0.1-1) ... Selecting previously unselected package python3-mysqldb. Preparing to unpack .../17-python3-mysqldb_1.4.4-2+b3_amd64.deb ... Unpacking python3-mysqldb (1.4.4-2+b3) ... Selecting previously unselected package python3-pymysql. Preparing to unpack .../18-python3-pymysql_0.9.3-2_all.deb ... Unpacking python3-pymysql (0.9.3-2) ... dpkg-deb: error: archive '/tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220 822~a480e53-1_all.deb' uses unknown compression for member 'control.tar.zst', gi ving up dpkg: error processing archive /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~ 20220822~a480e53-1_all.deb (--unpack):  dpkg-deb --control subprocess returned error exit status 2 Selecting previously unselected package python3-sqlalchemy-ext:amd64. Preparing to unpack .../20-python3-sqlalchemy-ext_1.3.22+ds1-1_amd64.deb ... Unpacking python3-sqlalchemy-ext:amd64 (1.3.22+ds1-1) ... Errors were encountered while processing:  /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220822~a480e53-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) On 24/08/2022 12:16, johan wrote: > Liviu, > > is there already a repo for opensips-cli on debian 11 ? > > > Secondly, if the old repo would work on debian 11, can  you please put a > pub key ? > > Get:4 https://apt.opensips.org jammy InRelease [21.9 kB] > Err:4 https://apt.opensips.org jammy InRelease >   The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 81CE21E7049AD65B > Reading package lists... Done > W: GPG error: https://apt.opensips.org jammy InRelease: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 81CE21E7049AD65B > E: The repository 'https://apt.opensips.org jammy InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > > wkr, > > wkr, > From razvan at opensips.org Wed Aug 24 11:17:00 2022 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 24 Aug 2022 14:17:00 +0300 Subject: [OpenSIPS-Users] opensips-cli debian 11 In-Reply-To: <056fcb3a-c92a-daf2-0647-a97bc802ca75@democon.be> References: <056fcb3a-c92a-daf2-0647-a97bc802ca75@democon.be> Message-ID: <89e7f6ca-56ca-0bcc-1fd2-a60f7bbfea33@opensips.org> Hi, Johan! Are you trying to install on Debian 11 or on Ubuntu 22? Because I see that the sources list is jammy, but then you are fetching bullseye. Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 8/24/22 13:42, johan wrote: > the old repo gives errors on bullseye. > > root at sipp:/etc/apt/sources.list.d# apt install opensips-cli > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > The following additional packages will be installed: >   libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel >   python3-cffi python3-cffi-backend python3-cryptography python3-dateutil >   python3-infinity python3-mysqldb python3-openssl python3-ply >   python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy >   python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz > Suggested packages: >   python-arrow-doc python-cryptography-doc python3-cryptography-vectors >   python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc >   python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql >   python3-psycopg2 python-sqlalchemy-utils-doc > The following NEW packages will be installed: >   libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow >   python3-babel python3-cffi python3-cffi-backend python3-cryptography >   python3-dateutil python3-infinity python3-mysqldb python3-openssl >   python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql >   python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils >   python3-tz > 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. > Need to get 7,133 kB of archives. > After this operation, 38.5 MB of additional disk space will be used. > Do you want to continue? [Y/n] y > Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64 > 13.7-0+deb11u1 [180 kB] > Get:2 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy all 1.3.22+ds1-1 [795 kB] > Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all > 0.1~20220822~a480e53-1 [41.3 kB] > Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson > all 0.3.3-2 [8,196 B] > Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil > all 2.8.1-6 [79.2 kB] > Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all > 0.17.0-1 [50.7 kB] > Get:7 http://deb.debian.org/debian bullseye/main amd64 > python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB] > Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all > 2021.1-1 [34.8 kB] > Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all > 2.8.0+dfsg.1-7 [100 kB] > Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity > all 1.5-2 [4,364 B] > Get:11 http://deb.debian.org/debian bullseye/main amd64 > python3-cffi-backend amd64 1.14.5-1 [85.8 kB] > Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all > 3.11-4 [65.5 kB] > Get:13 http://deb.debian.org/debian bullseye/main amd64 > python3-pycparser all 2.20-3 [74.5 kB] > Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all > 1.14.5-1 [87.9 kB] > Get:15 http://deb.debian.org/debian bullseye/main amd64 > python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB] > Get:16 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB] > Get:17 http://deb.debian.org/debian bullseye/main amd64 > python3-cryptography amd64 3.3.2-1 [223 kB] > Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl > all 20.0.1-1 [53.7 kB] > Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb > amd64 1.4.4-2+b3 [57.0 kB] > Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql > all 0.9.3-2 [43.4 kB] > Get:21 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB] > Fetched 7,133 kB in 14s (519 > kB/s) > Selecting previously unselected package libpq5:amd64. > (Reading database ... 163371 files and directories currently installed.) > Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ... > Unpacking libpq5:amd64 (13.7-0+deb11u1) ... > Selecting previously unselected package python3-sqlalchemy. > Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ... > Unpacking python3-sqlalchemy (1.3.22+ds1-1) ... > Selecting previously unselected package python3-anyjson. > Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ... > Unpacking python3-anyjson (0.3.3-2) ... > Selecting previously unselected package python3-dateutil. > Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ... > Unpacking python3-dateutil (2.8.1-6) ... > Selecting previously unselected package python3-arrow. > Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ... > Unpacking python3-arrow (0.17.0-1) ... > Selecting previously unselected package python-babel-localedata. > Preparing to unpack > .../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ... > Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ... > Selecting previously unselected package python3-tz. > Preparing to unpack .../06-python3-tz_2021.1-1_all.deb ... > Unpacking python3-tz (2021.1-1) ... > Selecting previously unselected package python3-babel. > Preparing to unpack .../07-python3-babel_2.8.0+dfsg.1-7_all.deb ... > Unpacking python3-babel (2.8.0+dfsg.1-7) ... > Selecting previously unselected package python3-infinity. > Preparing to unpack .../08-python3-infinity_1.5-2_all.deb ... > Unpacking python3-infinity (1.5-2) ... > Selecting previously unselected package python3-cffi-backend:amd64. > Preparing to unpack .../09-python3-cffi-backend_1.14.5-1_amd64.deb ... > Unpacking python3-cffi-backend:amd64 (1.14.5-1) ... > Selecting previously unselected package python3-ply. > Preparing to unpack .../10-python3-ply_3.11-4_all.deb ... > Unpacking python3-ply (3.11-4) ... > Selecting previously unselected package python3-pycparser. > Preparing to unpack .../11-python3-pycparser_2.20-3_all.deb ... > Unpacking python3-pycparser (2.20-3) ... > Selecting previously unselected package python3-cffi. > Preparing to unpack .../12-python3-cffi_1.14.5-1_all.deb ... > Unpacking python3-cffi (1.14.5-1) ... > Selecting previously unselected package python3-psycopg2cffi. > Preparing to unpack .../13-python3-psycopg2cffi_2.8.1-2_amd64.deb ... > Unpacking python3-psycopg2cffi (2.8.1-2) ... > Selecting previously unselected package python3-sqlalchemy-utils. > Preparing to unpack .../14-python3-sqlalchemy-utils_0.36.8-4_all.deb ... > Unpacking python3-sqlalchemy-utils (0.36.8-4) ... > Selecting previously unselected package python3-cryptography. > Preparing to unpack .../15-python3-cryptography_3.3.2-1_amd64.deb ... > Unpacking python3-cryptography (3.3.2-1) ... > Selecting previously unselected package python3-openssl. > Preparing to unpack .../16-python3-openssl_20.0.1-1_all.deb ... > Unpacking python3-openssl (20.0.1-1) ... > Selecting previously unselected package python3-mysqldb. > Preparing to unpack .../17-python3-mysqldb_1.4.4-2+b3_amd64.deb ... > Unpacking python3-mysqldb (1.4.4-2+b3) ... > Selecting previously unselected package python3-pymysql. > Preparing to unpack .../18-python3-pymysql_0.9.3-2_all.deb ... > Unpacking python3-pymysql (0.9.3-2) ... > dpkg-deb: error: archive > '/tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220 > 822~a480e53-1_all.deb' uses unknown compression for member > 'control.tar.zst', gi > ving up > dpkg: error processing archive > /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~ > 20220822~a480e53-1_all.deb (--unpack): >  dpkg-deb --control subprocess returned error exit status 2 > Selecting previously unselected package python3-sqlalchemy-ext:amd64. > Preparing to unpack .../20-python3-sqlalchemy-ext_1.3.22+ds1-1_amd64.deb ... > Unpacking python3-sqlalchemy-ext:amd64 (1.3.22+ds1-1) ... > Errors were encountered while processing: >  /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220822~a480e53-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > On 24/08/2022 12:16, johan wrote: >> Liviu, >> >> is there already a repo for opensips-cli on debian 11 ? >> >> >> Secondly, if the old repo would work on debian 11, can  you please put a >> pub key ? >> >> Get:4 https://apt.opensips.org jammy InRelease [21.9 kB] >> Err:4 https://apt.opensips.org jammy InRelease >>   The following signatures couldn't be verified because the public key >> is not available: NO_PUBKEY 81CE21E7049AD65B >> Reading package lists... Done >> W: GPG error: https://apt.opensips.org jammy InRelease: The following >> signatures couldn't be verified because the public key is not available: >> NO_PUBKEY 81CE21E7049AD65B >> E: The repository 'https://apt.opensips.org jammy InRelease' is not signed. >> N: Updating from such a repository can't be done securely, and is >> therefore disabled by default. >> >> wkr, >> >> wkr, >> > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Wed Aug 24 11:18:04 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 24 Aug 2022 14:18:04 +0300 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: Message-ID: Hi Li, Have you tried to use the local_route in order to do custom changes on the outgoing requests generated by the B2B bridging ? 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/23/22 10:34 PM, Li Cai wrote: > > Hi, > > I’m working on a change for a B2BUA based on OpenSIPs 2.4, but not > sure if the function is supported or if it has been supported in the > later versions. > > We have used the MI command b2b_bridge to bridge existing calls from > one entity to another and it works, the scenario is the same as > expected. While besides this, we also need to modify one of the > headers of the INVITEs sending to the new destination in this > scenario,  our scripts in the opensips.cfg can’t take any effect. > > 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: From bogdan at opensips.org Wed Aug 24 11:29:02 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 24 Aug 2022 14:29:02 +0300 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment In-Reply-To: References: Message-ID: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> Hi Jonathan, I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit in Athens - I think this is the 3rd time in the last week coming across it :) Unfortunately there is no way to skip at the moment that DNS failure when loading the destinations :(....even more, there some code that relies on the fact that there is an "IP" attached to any destination.....And I just checked, a local error in sending the ping (like the DNS err) does not results in marking the destination as failed or so..... so it is not so straight as ignoring the DNS error. 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/24/22 12:24 AM, Jonathan Hunter wrote: > > Hi All, > > I have a query around dispatcher behaviour, I am running 3.2 in a k8s > environment. > > I have 2 freeswitch instances defined in a destination set, both of > which are pods. > > As people may be aware its fun implementing in k8s as pods can restart > and disappear at times so I ideally want this reflected in the cache > and output of opensips-cli -x mi ds_list where I was hoping the > freeswitch entries would be defined but with a state of probing or > inactive. > > With my current setup, when restarting opensips for example, I have > the dispatcher table populated in postgres db , and if opensips cant > resolve the URI it wont load it into cache, like wise if opensips is > running and freeswitch pod drops, I see this in the logs; > > Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve > freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it > > Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add > destination > > in group 10 > > I therefore don’t see it listed in cache when I run ds_list. > > Does anyone know if its possible to tweak dispatcher to always load > the database entries into cache at startup, and also set their status > to probing/inactive if not reachable due to a resolving issue as above? > > My dispatcher settings are; > > #### Dynamic routing > > loadmodule "dispatcher.so" > > modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") > > modparam("dispatcher", "ds_probing_mode", 1) > > modparam("dispatcher", "ds_probing_threshhold", 1) > > modparam("dispatcher", "persistent_state", 0) > > modparam("dispatcher", "ds_ping_interval", 5) > > modparam("dispatcher", "table_name", "dispatcher") > > modparam("dispatcher", "cluster_id", 1) > > Hope that makes sense! > > Many thanks > > Jon > > > _______________________________________________ > 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: From johan at democon.be Wed Aug 24 11:36:48 2022 From: johan at democon.be (Johan De Clercq) Date: Wed, 24 Aug 2022 11:36:48 +0000 Subject: [OpenSIPS-Users] opensips-cli debian 11 In-Reply-To: <89e7f6ca-56ca-0bcc-1fd2-a60f7bbfea33@opensips.org> References: <056fcb3a-c92a-daf2-0647-a97bc802ca75@democon.be> <89e7f6ca-56ca-0bcc-1fd2-a60f7bbfea33@opensips.org> Message-ID: Debian 11 Outlook voor iOS downloaden ________________________________ Van: Users namens Răzvan Crainea Verzonden: Wednesday, August 24, 2022 1:17:00 PM Aan: users at lists.opensips.org Onderwerp: Re: [OpenSIPS-Users] opensips-cli debian 11 Hi, Johan! Are you trying to install on Debian 11 or on Ubuntu 22? Because I see that the sources list is jammy, but then you are fetching bullseye. Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 8/24/22 13:42, johan wrote: > the old repo gives errors on bullseye. > > root at sipp:/etc/apt/sources.list.d# apt install opensips-cli > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > The following additional packages will be installed: > libpq5 python-babel-localedata python3-anyjson python3-arrow python3-babel > python3-cffi python3-cffi-backend python3-cryptography python3-dateutil > python3-infinity python3-mysqldb python3-openssl python3-ply > python3-psycopg2cffi python3-pycparser python3-pymysql python3-sqlalchemy > python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz > Suggested packages: > python-arrow-doc python-cryptography-doc python3-cryptography-vectors > python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg python-ply-doc > python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql > python3-psycopg2 python-sqlalchemy-utils-doc > The following NEW packages will be installed: > libpq5 opensips-cli python-babel-localedata python3-anyjson python3-arrow > python3-babel python3-cffi python3-cffi-backend python3-cryptography > python3-dateutil python3-infinity python3-mysqldb python3-openssl > python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql > python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils > python3-tz > 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. > Need to get 7,133 kB of archives. > After this operation, 38.5 MB of additional disk space will be used. > Do you want to continue? [Y/n] y > Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64 > 13.7-0+deb11u1 [180 kB] > Get:2 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy all 1.3.22+ds1-1 [795 kB] > Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all > 0.1~20220822~a480e53-1 [41.3 kB] > Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson > all 0.3.3-2 [8,196 B] > Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil > all 2.8.1-6 [79.2 kB] > Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all > 0.17.0-1 [50.7 kB] > Get:7 http://deb.debian.org/debian bullseye/main amd64 > python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB] > Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all > 2021.1-1 [34.8 kB] > Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all > 2.8.0+dfsg.1-7 [100 kB] > Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity > all 1.5-2 [4,364 B] > Get:11 http://deb.debian.org/debian bullseye/main amd64 > python3-cffi-backend amd64 1.14.5-1 [85.8 kB] > Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all > 3.11-4 [65.5 kB] > Get:13 http://deb.debian.org/debian bullseye/main amd64 > python3-pycparser all 2.20-3 [74.5 kB] > Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all > 1.14.5-1 [87.9 kB] > Get:15 http://deb.debian.org/debian bullseye/main amd64 > python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB] > Get:16 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB] > Get:17 http://deb.debian.org/debian bullseye/main amd64 > python3-cryptography amd64 3.3.2-1 [223 kB] > Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl > all 20.0.1-1 [53.7 kB] > Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb > amd64 1.4.4-2+b3 [57.0 kB] > Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql > all 0.9.3-2 [43.4 kB] > Get:21 http://deb.debian.org/debian bullseye/main amd64 > python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB] > Fetched 7,133 kB in 14s (519 > kB/s) > Selecting previously unselected package libpq5:amd64. > (Reading database ... 163371 files and directories currently installed.) > Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ... > Unpacking libpq5:amd64 (13.7-0+deb11u1) ... > Selecting previously unselected package python3-sqlalchemy. > Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ... > Unpacking python3-sqlalchemy (1.3.22+ds1-1) ... > Selecting previously unselected package python3-anyjson. > Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ... > Unpacking python3-anyjson (0.3.3-2) ... > Selecting previously unselected package python3-dateutil. > Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ... > Unpacking python3-dateutil (2.8.1-6) ... > Selecting previously unselected package python3-arrow. > Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ... > Unpacking python3-arrow (0.17.0-1) ... > Selecting previously unselected package python-babel-localedata. > Preparing to unpack > .../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ... > Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ... > Selecting previously unselected package python3-tz. > Preparing to unpack .../06-python3-tz_2021.1-1_all.deb ... > Unpacking python3-tz (2021.1-1) ... > Selecting previously unselected package python3-babel. > Preparing to unpack .../07-python3-babel_2.8.0+dfsg.1-7_all.deb ... > Unpacking python3-babel (2.8.0+dfsg.1-7) ... > Selecting previously unselected package python3-infinity. > Preparing to unpack .../08-python3-infinity_1.5-2_all.deb ... > Unpacking python3-infinity (1.5-2) ... > Selecting previously unselected package python3-cffi-backend:amd64. > Preparing to unpack .../09-python3-cffi-backend_1.14.5-1_amd64.deb ... > Unpacking python3-cffi-backend:amd64 (1.14.5-1) ... > Selecting previously unselected package python3-ply. > Preparing to unpack .../10-python3-ply_3.11-4_all.deb ... > Unpacking python3-ply (3.11-4) ... > Selecting previously unselected package python3-pycparser. > Preparing to unpack .../11-python3-pycparser_2.20-3_all.deb ... > Unpacking python3-pycparser (2.20-3) ... > Selecting previously unselected package python3-cffi. > Preparing to unpack .../12-python3-cffi_1.14.5-1_all.deb ... > Unpacking python3-cffi (1.14.5-1) ... > Selecting previously unselected package python3-psycopg2cffi. > Preparing to unpack .../13-python3-psycopg2cffi_2.8.1-2_amd64.deb ... > Unpacking python3-psycopg2cffi (2.8.1-2) ... > Selecting previously unselected package python3-sqlalchemy-utils. > Preparing to unpack .../14-python3-sqlalchemy-utils_0.36.8-4_all.deb ... > Unpacking python3-sqlalchemy-utils (0.36.8-4) ... > Selecting previously unselected package python3-cryptography. > Preparing to unpack .../15-python3-cryptography_3.3.2-1_amd64.deb ... > Unpacking python3-cryptography (3.3.2-1) ... > Selecting previously unselected package python3-openssl. > Preparing to unpack .../16-python3-openssl_20.0.1-1_all.deb ... > Unpacking python3-openssl (20.0.1-1) ... > Selecting previously unselected package python3-mysqldb. > Preparing to unpack .../17-python3-mysqldb_1.4.4-2+b3_amd64.deb ... > Unpacking python3-mysqldb (1.4.4-2+b3) ... > Selecting previously unselected package python3-pymysql. > Preparing to unpack .../18-python3-pymysql_0.9.3-2_all.deb ... > Unpacking python3-pymysql (0.9.3-2) ... > dpkg-deb: error: archive > '/tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220 > 822~a480e53-1_all.deb' uses unknown compression for member > 'control.tar.zst', gi > ving up > dpkg: error processing archive > /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~ > 20220822~a480e53-1_all.deb (--unpack): > dpkg-deb --control subprocess returned error exit status 2 > Selecting previously unselected package python3-sqlalchemy-ext:amd64. > Preparing to unpack .../20-python3-sqlalchemy-ext_1.3.22+ds1-1_amd64.deb ... > Unpacking python3-sqlalchemy-ext:amd64 (1.3.22+ds1-1) ... > Errors were encountered while processing: > /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220822~a480e53-1_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > On 24/08/2022 12:16, johan wrote: >> Liviu, >> >> is there already a repo for opensips-cli on debian 11 ? >> >> >> Secondly, if the old repo would work on debian 11, can you please put a >> pub key ? >> >> Get:4 https://apt.opensips.org jammy InRelease [21.9 kB] >> Err:4 https://apt.opensips.org jammy InRelease >> The following signatures couldn't be verified because the public key >> is not available: NO_PUBKEY 81CE21E7049AD65B >> Reading package lists... Done >> W: GPG error: https://apt.opensips.org jammy InRelease: The following >> signatures couldn't be verified because the public key is not available: >> NO_PUBKEY 81CE21E7049AD65B >> E: The repository 'https://apt.opensips.org jammy InRelease' is not signed. >> N: Updating from such a repository can't be done securely, and is >> therefore disabled by default. >> >> wkr, >> >> wkr, >> > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Wed Aug 24 12:45:50 2022 From: johan at democon.be (johan) Date: Wed, 24 Aug 2022 14:45:50 +0200 Subject: [OpenSIPS-Users] opensips-cli debian 11 In-Reply-To: <89e7f6ca-56ca-0bcc-1fd2-a60f7bbfea33@opensips.org> References: <056fcb3a-c92a-daf2-0647-a97bc802ca75@democon.be> <89e7f6ca-56ca-0bcc-1fd2-a60f7bbfea33@opensips.org> Message-ID: <7a1721c6-3463-93e7-3932-e205467ba40f@democon.be> that worked, thank you razvan. On 24/08/2022 13:17, Răzvan Crainea wrote: > Hi, Johan! > > Are you trying to install on Debian 11 or on Ubuntu 22? > Because I see that the sources list is jammy, but then you are > fetching bullseye. > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > On 8/24/22 13:42, johan wrote: >> the old repo gives errors on bullseye. >> >> root at sipp:/etc/apt/sources.list.d# apt install opensips-cli >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> The following additional packages will be installed: >>    libpq5 python-babel-localedata python3-anyjson python3-arrow >> python3-babel >>    python3-cffi python3-cffi-backend python3-cryptography >> python3-dateutil >>    python3-infinity python3-mysqldb python3-openssl python3-ply >>    python3-psycopg2cffi python3-pycparser python3-pymysql >> python3-sqlalchemy >>    python3-sqlalchemy-ext python3-sqlalchemy-utils python3-tz >> Suggested packages: >>    python-arrow-doc python-cryptography-doc python3-cryptography-vectors >>    python3-mysqldb-dbg python-openssl-doc python3-openssl-dbg >> python-ply-doc >>    python-pymysql-doc python-sqlalchemy-doc python3-fdb python3-pymssql >>    python3-psycopg2 python-sqlalchemy-utils-doc >> The following NEW packages will be installed: >>    libpq5 opensips-cli python-babel-localedata python3-anyjson >> python3-arrow >>    python3-babel python3-cffi python3-cffi-backend python3-cryptography >>    python3-dateutil python3-infinity python3-mysqldb python3-openssl >>    python3-ply python3-psycopg2cffi python3-pycparser python3-pymysql >>    python3-sqlalchemy python3-sqlalchemy-ext python3-sqlalchemy-utils >>    python3-tz >> 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. >> Need to get 7,133 kB of archives. >> After this operation, 38.5 MB of additional disk space will be used. >> Do you want to continue? [Y/n] y >> Get:1 http://deb.debian.org/debian bullseye/main amd64 libpq5 amd64 >> 13.7-0+deb11u1 [180 kB] >> Get:2 http://deb.debian.org/debian bullseye/main amd64 >> python3-sqlalchemy all 1.3.22+ds1-1 [795 kB] >> Get:3 https://apt.opensips.org jammy/cli-nightly amd64 opensips-cli all >> 0.1~20220822~a480e53-1 [41.3 kB] >> Get:4 http://deb.debian.org/debian bullseye/main amd64 python3-anyjson >> all 0.3.3-2 [8,196 B] >> Get:5 http://deb.debian.org/debian bullseye/main amd64 python3-dateutil >> all 2.8.1-6 [79.2 kB] >> Get:6 http://deb.debian.org/debian bullseye/main amd64 python3-arrow all >> 0.17.0-1 [50.7 kB] >> Get:7 http://deb.debian.org/debian bullseye/main amd64 >> python-babel-localedata all 2.8.0+dfsg.1-7 [4,997 kB] >> Get:8 http://deb.debian.org/debian bullseye/main amd64 python3-tz all >> 2021.1-1 [34.8 kB] >> Get:9 http://deb.debian.org/debian bullseye/main amd64 python3-babel all >> 2.8.0+dfsg.1-7 [100 kB] >> Get:10 http://deb.debian.org/debian bullseye/main amd64 python3-infinity >> all 1.5-2 [4,364 B] >> Get:11 http://deb.debian.org/debian bullseye/main amd64 >> python3-cffi-backend amd64 1.14.5-1 [85.8 kB] >> Get:12 http://deb.debian.org/debian bullseye/main amd64 python3-ply all >> 3.11-4 [65.5 kB] >> Get:13 http://deb.debian.org/debian bullseye/main amd64 >> python3-pycparser all 2.20-3 [74.5 kB] >> Get:14 http://deb.debian.org/debian bullseye/main amd64 python3-cffi all >> 1.14.5-1 [87.9 kB] >> Get:15 http://deb.debian.org/debian bullseye/main amd64 >> python3-psycopg2cffi amd64 2.8.1-2 [64.1 kB] >> Get:16 http://deb.debian.org/debian bullseye/main amd64 >> python3-sqlalchemy-utils all 0.36.8-4 [66.6 kB] >> Get:17 http://deb.debian.org/debian bullseye/main amd64 >> python3-cryptography amd64 3.3.2-1 [223 kB] >> Get:18 http://deb.debian.org/debian bullseye/main amd64 python3-openssl >> all 20.0.1-1 [53.7 kB] >> Get:19 http://deb.debian.org/debian bullseye/main amd64 python3-mysqldb >> amd64 1.4.4-2+b3 [57.0 kB] >> Get:20 http://deb.debian.org/debian bullseye/main amd64 python3-pymysql >> all 0.9.3-2 [43.4 kB] >> Get:21 http://deb.debian.org/debian bullseye/main amd64 >> python3-sqlalchemy-ext amd64 1.3.22+ds1-1 [19.9 kB] >> Fetched 7,133 kB in 14s (519 >> kB/s) >> Selecting previously unselected package libpq5:amd64. >> (Reading database ... 163371 files and directories currently installed.) >> Preparing to unpack .../00-libpq5_13.7-0+deb11u1_amd64.deb ... >> Unpacking libpq5:amd64 (13.7-0+deb11u1) ... >> Selecting previously unselected package python3-sqlalchemy. >> Preparing to unpack .../01-python3-sqlalchemy_1.3.22+ds1-1_all.deb ... >> Unpacking python3-sqlalchemy (1.3.22+ds1-1) ... >> Selecting previously unselected package python3-anyjson. >> Preparing to unpack .../02-python3-anyjson_0.3.3-2_all.deb ... >> Unpacking python3-anyjson (0.3.3-2) ... >> Selecting previously unselected package python3-dateutil. >> Preparing to unpack .../03-python3-dateutil_2.8.1-6_all.deb ... >> Unpacking python3-dateutil (2.8.1-6) ... >> Selecting previously unselected package python3-arrow. >> Preparing to unpack .../04-python3-arrow_0.17.0-1_all.deb ... >> Unpacking python3-arrow (0.17.0-1) ... >> Selecting previously unselected package python-babel-localedata. >> Preparing to unpack >> .../05-python-babel-localedata_2.8.0+dfsg.1-7_all.deb ... >> Unpacking python-babel-localedata (2.8.0+dfsg.1-7) ... >> Selecting previously unselected package python3-tz. >> Preparing to unpack .../06-python3-tz_2021.1-1_all.deb ... >> Unpacking python3-tz (2021.1-1) ... >> Selecting previously unselected package python3-babel. >> Preparing to unpack .../07-python3-babel_2.8.0+dfsg.1-7_all.deb ... >> Unpacking python3-babel (2.8.0+dfsg.1-7) ... >> Selecting previously unselected package python3-infinity. >> Preparing to unpack .../08-python3-infinity_1.5-2_all.deb ... >> Unpacking python3-infinity (1.5-2) ... >> Selecting previously unselected package python3-cffi-backend:amd64. >> Preparing to unpack .../09-python3-cffi-backend_1.14.5-1_amd64.deb ... >> Unpacking python3-cffi-backend:amd64 (1.14.5-1) ... >> Selecting previously unselected package python3-ply. >> Preparing to unpack .../10-python3-ply_3.11-4_all.deb ... >> Unpacking python3-ply (3.11-4) ... >> Selecting previously unselected package python3-pycparser. >> Preparing to unpack .../11-python3-pycparser_2.20-3_all.deb ... >> Unpacking python3-pycparser (2.20-3) ... >> Selecting previously unselected package python3-cffi. >> Preparing to unpack .../12-python3-cffi_1.14.5-1_all.deb ... >> Unpacking python3-cffi (1.14.5-1) ... >> Selecting previously unselected package python3-psycopg2cffi. >> Preparing to unpack .../13-python3-psycopg2cffi_2.8.1-2_amd64.deb ... >> Unpacking python3-psycopg2cffi (2.8.1-2) ... >> Selecting previously unselected package python3-sqlalchemy-utils. >> Preparing to unpack .../14-python3-sqlalchemy-utils_0.36.8-4_all.deb ... >> Unpacking python3-sqlalchemy-utils (0.36.8-4) ... >> Selecting previously unselected package python3-cryptography. >> Preparing to unpack .../15-python3-cryptography_3.3.2-1_amd64.deb ... >> Unpacking python3-cryptography (3.3.2-1) ... >> Selecting previously unselected package python3-openssl. >> Preparing to unpack .../16-python3-openssl_20.0.1-1_all.deb ... >> Unpacking python3-openssl (20.0.1-1) ... >> Selecting previously unselected package python3-mysqldb. >> Preparing to unpack .../17-python3-mysqldb_1.4.4-2+b3_amd64.deb ... >> Unpacking python3-mysqldb (1.4.4-2+b3) ... >> Selecting previously unselected package python3-pymysql. >> Preparing to unpack .../18-python3-pymysql_0.9.3-2_all.deb ... >> Unpacking python3-pymysql (0.9.3-2) ... >> dpkg-deb: error: archive >> '/tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220 >> 822~a480e53-1_all.deb' uses unknown compression for member >> 'control.tar.zst', gi >> ving up >> dpkg: error processing archive >> /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~ >> 20220822~a480e53-1_all.deb (--unpack): >>   dpkg-deb --control subprocess returned error exit status 2 >> Selecting previously unselected package python3-sqlalchemy-ext:amd64. >> Preparing to unpack >> .../20-python3-sqlalchemy-ext_1.3.22+ds1-1_amd64.deb ... >> Unpacking python3-sqlalchemy-ext:amd64 (1.3.22+ds1-1) ... >> Errors were encountered while processing: >>   /tmp/apt-dpkg-install-D5gGDW/19-opensips-cli_0.1~20220822~a480e53-1_all.deb >> >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> >> On 24/08/2022 12:16, johan wrote: >>> Liviu, >>> >>> is there already a repo for opensips-cli on debian 11 ? >>> >>> >>> Secondly, if the old repo would work on debian 11, can  you please >>> put a >>> pub key ? >>> >>> Get:4 https://apt.opensips.org jammy InRelease [21.9 kB] >>> Err:4 https://apt.opensips.org jammy InRelease >>>    The following signatures couldn't be verified because the public key >>> is not available: NO_PUBKEY 81CE21E7049AD65B >>> Reading package lists... Done >>> W: GPG error: https://apt.opensips.org jammy InRelease: The following >>> signatures couldn't be verified because the public key is not >>> available: >>> NO_PUBKEY 81CE21E7049AD65B >>> E: The repository 'https://apt.opensips.org jammy InRelease' is not >>> signed. >>> N: Updating from such a repository can't be done securely, and is >>> therefore disabled by default. >>> >>> wkr, >>> >>> wkr, >>> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From Li.Cai at comtech.com Wed Aug 24 13:34:27 2022 From: Li.Cai at comtech.com (Li Cai) Date: Wed, 24 Aug 2022 13:34:27 +0000 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: Message-ID: Hi Bogdan, Yes, we have put the changes by calling remove_hf() and append_hf() in the 'local_route', those functions for new incoming INVITE but not the INVITE sent out by 'b2b_bridge'. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 7:18 AM To: OpenSIPS users mailling list ; Li Cai Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Have you tried to use the local_route in order to do custom changes on the outgoing requests generated by the B2B bridging ? 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/23/22 10:34 PM, Li Cai wrote: Hi, I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the function is supported or if it has been supported in the later versions. We have used the MI command b2b_bridge to bridge existing calls from one entity to another and it works, the scenario is the same as expected. While besides this, we also need to modify one of the headers of the INVITEs sending to the new destination in this scenario, our scripts in the opensips.cfg can't take any effect. 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: From spanda at 3clogic.com Wed Aug 24 13:36:53 2022 From: spanda at 3clogic.com (Sasmita Panda) Date: Wed, 24 Aug 2022 19:06:53 +0530 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: References: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> Message-ID: What exactly do I have? I have a global cluster of DocumentDB (AWS service ) which is mongodb compatible . In the global cluster , the primary cluster is in us-east and the secondary cluster is in us-west . I have 2 connection strings for both clusters , primary.xyz.com pointed to primary cluster , secondary.xyz.com pointed to secondary cluster (secondary cluster only has read replicas) . In opensips I have given both the domains like below . modparam("usrloc", "cachedb_url","mongodb//docdb:cccl0g1c@*primary.xyz.com:27017 *,*secondary.xyz.com:27017 * /opensipsDB.userlocation?&readPreference=secondaryPreferred&retryWrites=false") whenever my primary cluster goes down and secondary is promoted to primary , opensips throws an error of connection loss . Opensips at that point also trying to connect to the *primary.xyz.com *although that is down* . * *At this point , my expectation was , opensips must have automatically detect the the older primary cluster was down and secondary was became primary and work properly . * *But its not happening . Once I restart the service its works fine . * *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Wed, Aug 24, 2022 at 3:30 PM Liviu Chircu wrote: > On 24.08.2022 11:56, Sasmita Panda wrote: > > > Now my primary cluster goes down so my secondary cluster becomes primary . > I have updated the connection string against the domain in route53 . Now > *primary-cluster.xzy.com * is pointed to > the new primary custer connection string . > > While creating a connection from the console through the mongo shell it's > getting connected . But opensips is not able to switch the connecting > string somehow . still it's trying to connect to the previous primary > connection string . > > It seems like opensips has cached the connection string and is trying to > connect to the same even after I have updated the string from the backend . > > libmongo will try each node in your CSV of nodes, there is no going around > this. Now, while your usage of two completely different clusters in the > same connection string seems to be *non-conventional* (I don't recall any > documentation advising this, all Mongo docs talk about connecting to either > a *replica set*, or to a *list of* *mongos* servers), I still think it > could work. Maybe just configure the "connectionTimeousMS" parameters (or > others??) and see if you can get libmongoc to time out faster on your 1st > cluster, when it goes down. > > Best regards, > > -- > Liviu Chircuwww.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: From bogdan at opensips.org Wed Aug 24 14:32:33 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 24 Aug 2022 17:32:33 +0300 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: Message-ID: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> Hi Li, All SIP requests generated by `b2b_bridge` are to be visible in local_route. And on the contrary, the incoming (received) requests DO NOT trigger local route. 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/24/22 4:34 PM, Li Cai wrote: > > Hi Bogdan, > > Yes, we have put the changes by calling remove_hf() and append_hf() in > the ‘local_route’, those functions for new incoming INVITE but not the > INVITE sent out by ‘b2b_bridge’. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > *Sent:* August 24, 2022 7:18 AM > *To:* OpenSIPS users mailling list ; Li Cai > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after executing a > MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > Hi Li, > > Have you tried to use the local_route in order to do custom changes on > the outgoing requests generated by the B2B bridging ? > > 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/23/22 10:34 PM, Li Cai wrote: > > Hi, > > I’m working on a change for a B2BUA based on OpenSIPs 2.4, but not > sure if the function is supported or if it has been supported in > the later versions. > > We have used the MI command b2b_bridge to bridge existing calls > from one entity to another and it works, the scenario is the same > as expected. While besides this, we also need to modify one of the > headers of the INVITEs sending to the new destination in this > scenario,  our scripts in the opensips.cfg can’t take any effect. > > 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: From Li.Cai at comtech.com Wed Aug 24 15:50:46 2022 From: Li.Cai at comtech.com (Li Cai) Date: Wed, 24 Aug 2022 15:50:46 +0000 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> References: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> Message-ID: Hi Bogdan, Thanks for the explanation. I mean that the local_route can take effect for the forwarded INVITE(from incoming ones) in our proxy, but not after b2b_bridge. I'll do more debugging on it since the messages should be visible. Thank you very much. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 10:33 AM To: Li Cai ; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, All SIP requests generated by `b2b_bridge` are to be visible in local_route. And on the contrary, the incoming (received) requests DO NOT trigger local route. 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/24/22 4:34 PM, Li Cai wrote: Hi Bogdan, Yes, we have put the changes by calling remove_hf() and append_hf() in the 'local_route', those functions for new incoming INVITE but not the INVITE sent out by 'b2b_bridge'. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 7:18 AM To: OpenSIPS users mailling list ; Li Cai Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Have you tried to use the local_route in order to do custom changes on the outgoing requests generated by the B2B bridging ? 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/23/22 10:34 PM, Li Cai wrote: Hi, I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the function is supported or if it has been supported in the later versions. We have used the MI command b2b_bridge to bridge existing calls from one entity to another and it works, the scenario is the same as expected. While besides this, we also need to modify one of the headers of the INVITEs sending to the new destination in this scenario, our scripts in the opensips.cfg can't take any effect. 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: From johan at democon.be Wed Aug 24 16:41:20 2022 From: johan at democon.be (johan) Date: Wed, 24 Aug 2022 18:41:20 +0200 Subject: [OpenSIPS-Users] registrant. Message-ID: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> Is there somebody who has a db extract on how to fill in a record in registrar ? wkr, From bogdan at opensips.org Thu Aug 25 06:55:11 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 25 Aug 2022 09:55:11 +0300 Subject: [OpenSIPS-Users] registrant. In-Reply-To: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> References: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> Message-ID: Hi Johan, Take a look at https://www.opensips.org/Documentation/Install-DBSchema-3-2#AEN9219, it will definitely help you here. 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/24/22 7:41 PM, johan wrote: > Is there somebody who has a db extract on how to fill in a record in > registrar ? > > > wkr, > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Thu Aug 25 07:05:29 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 25 Aug 2022 10:05:29 +0300 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> Message-ID: <26c4237e-2432-7756-dfe6-d7f7afde7d0b@opensips.org> Hi Li, Somehow we are going in circles here :). So, could you post a pcap for call going via your B2B  (showing all in and out SIP messages) and mention which frame is the outgoing request you cannot modify ? 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/24/22 6:50 PM, Li Cai wrote: > > Hi Bogdan, > > Thanks for the explanation. I mean that the local_route can take > effect for the forwarded INVITE(from incoming ones) in our proxy, but > not after b2b_bridge. I’ll do more debugging on it since the messages > should be visible. Thank you very much. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > *Sent:* August 24, 2022 10:33 AM > *To:* Li Cai ; OpenSIPS users mailling list > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after executing a > MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > Hi Li, > > All SIP requests generated by `b2b_bridge` are to be visible in > local_route. And on the contrary, the incoming (received) requests DO > NOT trigger local route. > > 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/24/22 4:34 PM, Li Cai wrote: > > Hi Bogdan, > > Yes, we have put the changes by calling remove_hf() and > append_hf() in the ‘local_route’, those functions for new incoming > INVITE but not the INVITE sent out by ‘b2b_bridge’. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > > *Sent:* August 24, 2022 7:18 AM > *To:* OpenSIPS users mailling list > ; Li Cai > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after executing > a MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > > Hi Li, > > Have you tried to use the local_route in order to do custom > changes on the outgoing requests generated by the B2B bridging ? > > 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/23/22 10:34 PM, Li Cai wrote: > > Hi, > > I’m working on a change for a B2BUA based on OpenSIPs 2.4, but > not sure if the function is supported or if it has been > supported in the later versions. > > We have used the MI command b2b_bridge to bridge existing > calls from one entity to another and it works, the scenario is > the same as expected. While besides this, we also need to > modify one of the headers of the INVITEs sending to the new > destination in this scenario,  our scripts in the opensips.cfg > can’t take any effect. > > 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: From y.kirsanov at gmail.com Thu Aug 25 07:57:46 2022 From: y.kirsanov at gmail.com (Yury Kirsanov) Date: Thu, 25 Aug 2022 17:57:46 +1000 Subject: [OpenSIPS-Users] Autoscaler in 3.2.x Message-ID: Hi all, I've ran into a strange issue, if I enable autoscaler on OpenSIPS 3.2.x (tried 5,6,7 and now 8) on a server without any load using 'socket' statement like this: auto_scaling_profile = PROFILE_UDP_PRIV scale up to 16 on 30% for 4 cycles within 5 scale down to 2 on 10% for 5 cycles udp_workers=4 socket=udp:10.x.x.x:5060 use_auto_scaling_profile PROFILE_UDP_PRIV then after a while OpenSIPS load goes up to some high number, autoscaler starts to open new processes up to a maximum number specified in profile and them load stays at that number, for example: opensips-cli -x mi get_statistics load { "load:load": 60 } It never changes and looks just 'stuck'. Any ideas why this is happening in my case? Or should I file a bug report? Thanks. Regards, Yury. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hunterj91 at hotmail.com Thu Aug 25 08:50:58 2022 From: hunterj91 at hotmail.com (Jonathan Hunter) Date: Thu, 25 Aug 2022 08:50:58 +0000 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment In-Reply-To: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> References: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> Message-ID: Hi Bogdan, Yes it would appear K8s implementations would be a very good topic at the Summit that is for sure! I understand your comments on dispatcher, its unfortunate as everything else is working fine. There was a suggestion to add a loopback address for example and then update when DNS has updated and records resolve? Is there any benefit in using dr_routing instead or will this behaviour be the same in the event of a dns lookup failure? Thanks for the response! Jon Sent from Mail for Windows From: Bogdan-Andrei Iancu Sent: 24 August 2022 12:29 To: OpenSIPS users mailling list; Jonathan Hunter Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment Hi Jonathan, I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit in Athens - I think this is the 3rd time in the last week coming across it :) Unfortunately there is no way to skip at the moment that DNS failure when loading the destinations :(....even more, there some code that relies on the fact that there is an "IP" attached to any destination.....And I just checked, a local error in sending the ping (like the DNS err) does not results in marking the destination as failed or so..... so it is not so straight as ignoring the DNS error. 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/24/22 12:24 AM, Jonathan Hunter wrote: Hi All, I have a query around dispatcher behaviour, I am running 3.2 in a k8s environment. I have 2 freeswitch instances defined in a destination set, both of which are pods. As people may be aware its fun implementing in k8s as pods can restart and disappear at times so I ideally want this reflected in the cache and output of opensips-cli -x mi ds_list where I was hoping the freeswitch entries would be defined but with a state of probing or inactive. With my current setup, when restarting opensips for example, I have the dispatcher table populated in postgres db , and if opensips cant resolve the URI it wont load it into cache, like wise if opensips is running and freeswitch pod drops, I see this in the logs; Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add destination in group 10 I therefore don’t see it listed in cache when I run ds_list. Does anyone know if its possible to tweak dispatcher to always load the database entries into cache at startup, and also set their status to probing/inactive if not reachable due to a resolving issue as above? My dispatcher settings are; #### Dynamic routing loadmodule "dispatcher.so" modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold", 1) modparam("dispatcher", "persistent_state", 0) modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "cluster_id", 1) Hope that makes sense! Many thanks Jon _______________________________________________ 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: From spanda at 3clogic.com Thu Aug 25 09:43:08 2022 From: spanda at 3clogic.com (Sasmita Panda) Date: Thu, 25 Aug 2022 15:13:08 +0530 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: References: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> Message-ID: Hi , modparam("db_cachedb", "cachedb_url","mongodb:// docdb:cccl0g1c at oregon-cluster.xyz.com:27017,*east-cluster.xyz.com * :27017/opensipsDB.userlocation?readPreference=secondaryPreferred&retryWrites=false&serverSelectionTryOnce=false&connectionTimeoutMS=5000") I had this parameter in my config . from these two connection strings one is primary and 1 is secondary replica . When primary goes down and secondary becomes primary . I am getting the below error . ERROR:cachedb_mongodb:mongo_con_update: last error: 15.13053: No suitable servers found: `serverSelectionTimeoutMS` expired: [connection timeout calling ismaster on '*east-cluster.xyz.com * :27017'] At this point east-cluster.xyz.com is down . and oregon-cluster.xyz.com is the primary server . What should I configure for this? Will I set the parameter serverSelectionTimeoutMS , then what will be the value of this parameter ? Please advise . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Wed, Aug 24, 2022 at 7:06 PM Sasmita Panda wrote: > What exactly do I have? > > I have a global cluster of DocumentDB (AWS service ) which is mongodb > compatible . > > In the global cluster , the primary cluster is in us-east and the > secondary cluster is in us-west . > > I have 2 connection strings for both clusters , primary.xyz.com pointed > to primary cluster , secondary.xyz.com pointed to secondary cluster > (secondary cluster only has read replicas) . > > In opensips I have given both the domains like below . > > modparam("usrloc", "cachedb_url","mongodb//docdb:cccl0g1c@*primary.xyz.com:27017 > *,*secondary.xyz.com:27017 > * > /opensipsDB.userlocation?&readPreference=secondaryPreferred&retryWrites=false") > > whenever my primary cluster goes down and secondary is promoted to > primary , opensips throws an error of connection loss . Opensips at that > point also trying to connect to the *primary.xyz.com > *although that is down* . * > > *At this point , my expectation was , opensips must have automatically > detect the the older primary cluster was down and secondary was became > primary and work properly . * > > *But its not happening . Once I restart the service its works fine . * > > > > > > > *Thanks & Regards* > *Sasmita Panda* > *Senior Network Testing and Software Engineer* > *3CLogic , ph:07827611765* > > > On Wed, Aug 24, 2022 at 3:30 PM Liviu Chircu wrote: > >> On 24.08.2022 11:56, Sasmita Panda wrote: >> >> >> Now my primary cluster goes down so my secondary cluster becomes primary >> . I have updated the connection string against the domain in route53 . Now >> *primary-cluster.xzy.com * is pointed to >> the new primary custer connection string . >> >> While creating a connection from the console through the mongo shell it's >> getting connected . But opensips is not able to switch the connecting >> string somehow . still it's trying to connect to the previous primary >> connection string . >> >> It seems like opensips has cached the connection string and is trying to >> connect to the same even after I have updated the string from the backend . >> >> libmongo will try each node in your CSV of nodes, there is no going >> around this. Now, while your usage of two completely different clusters in >> the same connection string seems to be *non-conventional* (I don't >> recall any documentation advising this, all Mongo docs talk about >> connecting to either a *replica set*, or to a *list of* *mongos* >> servers), I still think it could work. Maybe just configure the >> "connectionTimeousMS" parameters (or others??) and see if you can get >> libmongoc to time out faster on your 1st cluster, when it goes down. >> >> Best regards, >> >> -- >> Liviu Chircuwww.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: From bogdan at opensips.org Thu Aug 25 10:23:56 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 25 Aug 2022 13:23:56 +0300 Subject: [OpenSIPS-Users] Autoscaler in 3.2.x In-Reply-To: References: Message-ID: <051e4ba9-58ba-cd75-020a-ea22065b72b5@opensips.org> Hi Yury, And when that scaling up happens, do you actually have traffic ? or your OpenSIPS is idle ? Also, could you run `opensips-cli -x mi get_statistics load:` (not the colon at the end). 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/25/22 10:57 AM, Yury Kirsanov wrote: > Hi all, > I've ran into a strange issue, if I enable autoscaler on OpenSIPS > 3.2.x (tried 5,6,7 and now 8) on a server without any load using > 'socket' statement like this: > > auto_scaling_profile = PROFILE_UDP_PRIV >      scale up to 16 on 30% for 4 cycles within 5 >      scale down to 2 on 10% for 5 cycles > > udp_workers=4 > > socket=udp:10.x.x.x:5060 use_auto_scaling_profile PROFILE_UDP_PRIV > > then after a while OpenSIPS load goes up to some high number, > autoscaler starts to open new processes up to a maximum number > specified in profile and them load stays at that number, for example: > > opensips-cli -x mi get_statistics load > { >     "load:load": 60 > } > > It never changes and looks just 'stuck'. > > Any ideas why this is happening in my case? Or should I file a bug > report? Thanks. > > Regards, > Yury. > > _______________________________________________ > 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: From Ben.Newlin at genesys.com Thu Aug 25 17:54:53 2022 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Thu, 25 Aug 2022 17:54:53 +0000 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment In-Reply-To: References: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> Message-ID: The drouting module has a parameter that allows you to disable the DNS lookup. https://opensips.org/docs/modules/3.2.x/drouting.html#param_force_dns Ben Newlin From: Users on behalf of Jonathan Hunter Date: Thursday, August 25, 2022 at 4:54 AM To: Bogdan-Andrei Iancu , OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment EXTERNAL EMAIL - Please use caution with links and attachments ________________________________ Hi Bogdan, Yes it would appear K8s implementations would be a very good topic at the Summit that is for sure! I understand your comments on dispatcher, its unfortunate as everything else is working fine. There was a suggestion to add a loopback address for example and then update when DNS has updated and records resolve? Is there any benefit in using dr_routing instead or will this behaviour be the same in the event of a dns lookup failure? Thanks for the response! Jon Sent from Mail for Windows From: Bogdan-Andrei Iancu Sent: 24 August 2022 12:29 To: OpenSIPS users mailling list; Jonathan Hunter Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment Hi Jonathan, I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit in Athens - I think this is the 3rd time in the last week coming across it :) Unfortunately there is no way to skip at the moment that DNS failure when loading the destinations :(....even more, there some code that relies on the fact that there is an "IP" attached to any destination.....And I just checked, a local error in sending the ping (like the DNS err) does not results in marking the destination as failed or so..... so it is not so straight as ignoring the DNS error. 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/24/22 12:24 AM, Jonathan Hunter wrote: Hi All, I have a query around dispatcher behaviour, I am running 3.2 in a k8s environment. I have 2 freeswitch instances defined in a destination set, both of which are pods. As people may be aware its fun implementing in k8s as pods can restart and disappear at times so I ideally want this reflected in the cache and output of opensips-cli -x mi ds_list where I was hoping the freeswitch entries would be defined but with a state of probing or inactive. With my current setup, when restarting opensips for example, I have the dispatcher table populated in postgres db , and if opensips cant resolve the URI it wont load it into cache, like wise if opensips is running and freeswitch pod drops, I see this in the logs; Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add destination in group 10 I therefore don’t see it listed in cache when I run ds_list. Does anyone know if its possible to tweak dispatcher to always load the database entries into cache at startup, and also set their status to probing/inactive if not reachable due to a resolving issue as above? My dispatcher settings are; #### Dynamic routing loadmodule "dispatcher.so" modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold", 1) modparam("dispatcher", "persistent_state", 0) modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "cluster_id", 1) Hope that makes sense! Many thanks Jon _______________________________________________ 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: From Li.Cai at comtech.com Thu Aug 25 19:57:58 2022 From: Li.Cai at comtech.com (Li Cai) Date: Thu, 25 Aug 2022 19:57:58 +0000 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> <26c4237e-2432-7756-dfe6-d7f7afde7d0b@opensips.org> Message-ID: [This email is resent for the last one is oversized] Hi Bodgan, Thanks a lot for the help, the pcap file is attached. The call flow is as - #11. INVITE from the caller on 10.10.8.131 to B2BProxy 10.10.9.205 #15. Forwarded INVITE from B2BProxy with the expected To header to SIP UA1 .. . the call is setup and then b2b_bridge is triggered ... #75. B2BProxy sent reINVITE to the caller #77. B2BProxy sent INVITE to SIP UA2 with the unaccepted To header #79. SIP UA2 rejected the call The step #77 And #79 shows the problem, that the call was rejected as the To header in INVITE is not using the UA2's IP instead of B2BProxy's IP as domain name, which is required in our system. In our opensips.cfg script, we have already included clauses like remove_hf("To") and append_hf("To ...") but seems like they only work before b2b_bridge occurs. Thanks, Li From: Bogdan-Andrei Iancu > Sent: August 25, 2022 3:05 AM To: Li Cai >; OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Somehow we are going in circles here :). So, could you post a pcap for call going via your B2B (showing all in and out SIP messages) and mention which frame is the outgoing request you cannot modify ? 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/24/22 6:50 PM, Li Cai wrote: Hi Bogdan, Thanks for the explanation. I mean that the local_route can take effect for the forwarded INVITE(from incoming ones) in our proxy, but not after b2b_bridge. I'll do more debugging on it since the messages should be visible. Thank you very much. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 10:33 AM To: Li Cai ; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, All SIP requests generated by `b2b_bridge` are to be visible in local_route. And on the contrary, the incoming (received) requests DO NOT trigger local route. 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/24/22 4:34 PM, Li Cai wrote: Hi Bogdan, Yes, we have put the changes by calling remove_hf() and append_hf() in the 'local_route', those functions for new incoming INVITE but not the INVITE sent out by 'b2b_bridge'. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 7:18 AM To: OpenSIPS users mailling list ; Li Cai Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Have you tried to use the local_route in order to do custom changes on the outgoing requests generated by the B2B bridging ? 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/23/22 10:34 PM, Li Cai wrote: Hi, I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the function is supported or if it has been supported in the later versions. We have used the MI command b2b_bridge to bridge existing calls from one entity to another and it works, the scenario is the same as expected. While besides this, we also need to modify one of the headers of the INVITEs sending to the new destination in this scenario, our scripts in the opensips.cfg can't take any effect. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: b2b_bridge_without_correct_ToHeader.zip Type: application/x-zip-compressed Size: 6820 bytes Desc: b2b_bridge_without_correct_ToHeader.zip URL: From kurgan-rus at inbox.ru Fri Aug 26 11:13:30 2022 From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=) Date: Fri, 26 Aug 2022 14:13:30 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?registrant=2E?= In-Reply-To: References: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> Message-ID: <1661512410.50851032@f107.i.mail.ru> Hi Johan ,   your SQL insert will look like this:   INSERT INTO registrant (registrar, aor, username, password, binding_URI, expiry) VALUES (‘sip:11.11.11.11’, ’sip:79993332211 at voip-isp.com’, ’79993332211’, ’PaSsWoRd’, ‘sip:79993332211 at 22.22.22.22’, 300);   where: - 11.11.11.11 is VoIP ISP IP address, - voip-isp.com is a domain you should use for authentication (depends on ISP settings, may be sip:79993332211 at 11.11.11.11), - 79993332211 is your username (usually equals to phone number, but also depends on ISP settings), - sip:79993332211 at 22.22.22.22 - this will form a Contact: header and must contain IP address of your OpenSIPS (obviously you can insert here some other IP address, and the calls from ISP proxy will go there, but in most cases it’s common to write here the IP address of your OpenSIPS), 300 is an registration expiration value in seconds, you ISP may require some other value.   ----------------------------------------------- BR, Alexey https://alexeyka.zantsev.com/   -------------- next part -------------- An HTML attachment was scrubbed... URL: From spanda at 3clogic.com Fri Aug 26 13:05:19 2022 From: spanda at 3clogic.com (Sasmita Panda) Date: Fri, 26 Aug 2022 18:35:19 +0530 Subject: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion . In-Reply-To: References: <3292ea03-8cb5-18d4-e2ad-37eaeb10bd63@opensips.org> Message-ID: Can you please suggest something here . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Thu, Aug 25, 2022 at 3:13 PM Sasmita Panda wrote: > Hi , > > modparam("db_cachedb", "cachedb_url","mongodb:// > docdb:cccl0g1c at oregon-cluster.xyz.com:27017,*east-cluster.xyz.com > * > :27017/opensipsDB.userlocation?readPreference=secondaryPreferred&retryWrites=false&serverSelectionTryOnce=false&connectionTimeoutMS=5000") > > > I had this parameter in my config . from these two connection strings one > is primary and 1 is secondary replica . When primary goes down and > secondary becomes primary . I am getting the below error . > > ERROR:cachedb_mongodb:mongo_con_update: last error: 15.13053: No suitable > servers found: `serverSelectionTimeoutMS` expired: [connection timeout > calling ismaster on '*east-cluster.xyz.com * > :27017'] > > At this point east-cluster.xyz.com is down . and oregon-cluster.xyz.com > is the primary server . What should I configure for this? Will I set the > parameter serverSelectionTimeoutMS , then what will be the value of this > parameter ? Please advise . > > > > *Thanks & Regards* > *Sasmita Panda* > *Senior Network Testing and Software Engineer* > *3CLogic , ph:07827611765* > > > On Wed, Aug 24, 2022 at 7:06 PM Sasmita Panda wrote: > >> What exactly do I have? >> >> I have a global cluster of DocumentDB (AWS service ) which is mongodb >> compatible . >> >> In the global cluster , the primary cluster is in us-east and the >> secondary cluster is in us-west . >> >> I have 2 connection strings for both clusters , primary.xyz.com pointed >> to primary cluster , secondary.xyz.com pointed to secondary cluster >> (secondary cluster only has read replicas) . >> >> In opensips I have given both the domains like below . >> >> modparam("usrloc", "cachedb_url","mongodb//docdb:cccl0g1c@*primary.xyz.com:27017 >> *,*secondary.xyz.com:27017 >> * >> /opensipsDB.userlocation?&readPreference=secondaryPreferred&retryWrites=false") >> >> whenever my primary cluster goes down and secondary is promoted to >> primary , opensips throws an error of connection loss . Opensips at that >> point also trying to connect to the *primary.xyz.com >> *although that is down* . * >> >> *At this point , my expectation was , opensips must have automatically >> detect the the older primary cluster was down and secondary was became >> primary and work properly . * >> >> *But its not happening . Once I restart the service its works fine . * >> >> >> >> >> >> >> *Thanks & Regards* >> *Sasmita Panda* >> *Senior Network Testing and Software Engineer* >> *3CLogic , ph:07827611765* >> >> >> On Wed, Aug 24, 2022 at 3:30 PM Liviu Chircu wrote: >> >>> On 24.08.2022 11:56, Sasmita Panda wrote: >>> >>> >>> Now my primary cluster goes down so my secondary cluster becomes primary >>> . I have updated the connection string against the domain in route53 . Now >>> *primary-cluster.xzy.com * is pointed >>> to the new primary custer connection string . >>> >>> While creating a connection from the console through the mongo shell >>> it's getting connected . But opensips is not able to switch the connecting >>> string somehow . still it's trying to connect to the previous primary >>> connection string . >>> >>> It seems like opensips has cached the connection string and is trying to >>> connect to the same even after I have updated the string from the backend . >>> >>> libmongo will try each node in your CSV of nodes, there is no going >>> around this. Now, while your usage of two completely different clusters in >>> the same connection string seems to be *non-conventional* (I don't >>> recall any documentation advising this, all Mongo docs talk about >>> connecting to either a *replica set*, or to a *list of* *mongos* >>> servers), I still think it could work. Maybe just configure the >>> "connectionTimeousMS" parameters (or others??) and see if you can get >>> libmongoc to time out faster on your 1st cluster, when it goes down. >>> >>> Best regards, >>> >>> -- >>> Liviu Chircuwww.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: From hunterj91 at hotmail.com Fri Aug 26 14:36:05 2022 From: hunterj91 at hotmail.com (Jonathan Hunter) Date: Fri, 26 Aug 2022 14:36:05 +0000 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment In-Reply-To: References: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> Message-ID: Hi Ben, Great thank you for that I may well switch for now to drouting. @Bogdan-Andrei Iancu is it worth me raising anything against dispatcher in terms of a change request for dns behaviour? Many thanks both. Jon Sent from Mail for Windows From: Ben Newlin Sent: 25 August 2022 18:57 To: OpenSIPS users mailling list; Bogdan-Andrei Iancu Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment The drouting module has a parameter that allows you to disable the DNS lookup. https://opensips.org/docs/modules/3.2.x/drouting.html#param_force_dns Ben Newlin From: Users on behalf of Jonathan Hunter Date: Thursday, August 25, 2022 at 4:54 AM To: Bogdan-Andrei Iancu , OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment EXTERNAL EMAIL - Please use caution with links and attachments Hi Bogdan, Yes it would appear K8s implementations would be a very good topic at the Summit that is for sure! I understand your comments on dispatcher, its unfortunate as everything else is working fine. There was a suggestion to add a loopback address for example and then update when DNS has updated and records resolve? Is there any benefit in using dr_routing instead or will this behaviour be the same in the event of a dns lookup failure? Thanks for the response! Jon Sent from Mail for Windows From: Bogdan-Andrei Iancu Sent: 24 August 2022 12:29 To: OpenSIPS users mailling list; Jonathan Hunter Subject: Re: [OpenSIPS-Users] Dispatcher within a K8s environment Hi Jonathan, I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit in Athens - I think this is the 3rd time in the last week coming across it :) Unfortunately there is no way to skip at the moment that DNS failure when loading the destinations :(....even more, there some code that relies on the fact that there is an "IP" attached to any destination.....And I just checked, a local error in sending the ping (like the DNS err) does not results in marking the destination as failed or so..... so it is not so straight as ignoring the DNS error. 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/24/22 12:24 AM, Jonathan Hunter wrote: Hi All, I have a query around dispatcher behaviour, I am running 3.2 in a k8s environment. I have 2 freeswitch instances defined in a destination set, both of which are pods. As people may be aware its fun implementing in k8s as pods can restart and disappear at times so I ideally want this reflected in the cache and output of opensips-cli -x mi ds_list where I was hoping the freeswitch entries would be defined but with a state of probing or inactive. With my current setup, when restarting opensips for example, I have the dispatcher table populated in postgres db , and if opensips cant resolve the URI it wont load it into cache, like wise if opensips is running and freeswitch pod drops, I see this in the logs; Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not resolve freeswitch-opensips-deployment-1.freeswitch-opensips, skipping it Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to add destination in group 10 I therefore don’t see it listed in cache when I run ds_list. Does anyone know if its possible to tweak dispatcher to always load the database entries into cache at startup, and also set their status to probing/inactive if not reachable due to a resolving issue as above? My dispatcher settings are; #### Dynamic routing loadmodule "dispatcher.so" modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshhold", 1) modparam("dispatcher", "persistent_state", 0) modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "cluster_id", 1) Hope that makes sense! Many thanks Jon _______________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6C8FCB656E874AC19425788EDEE1758D.png Type: image/png Size: 140 bytes Desc: 6C8FCB656E874AC19425788EDEE1758D.png URL: From voransoy at gmail.com Fri Aug 26 15:14:53 2022 From: voransoy at gmail.com (Volkan Oransoy) Date: Fri, 26 Aug 2022 16:14:53 +0100 Subject: [OpenSIPS-Users] TLS problem Message-ID: Hi all We are having an issue with TLS connections on our lab setup on EC2 and couldn't figure out a solution. Here are my logs and configs. WSS, UDP and TCP connections work fine. Honestly, I couldn't find a way to properly debug the problem other than logs. Thanks in advance for your help Cheers loadmodule "tls_mgm.so" loadmodule "tls_openssl.so" modparam("tls_mgm", "tls_library", "openssl") modparam("tls_mgm", "client_sip_domain_avp", "tls_sip_dom") modparam("tls_mgm", "server_domain", "test") modparam("tls_mgm", "match_ip_address", "[test]*") modparam("tls_mgm", "certificate", "[test]/etc/opensips/tls/server.crt") modparam("tls_mgm", "private_key", "[test]/etc/opensips/tls/server.key") modparam("tls_mgm", "tls_method", "[test]TLSv1-") modparam("tls_mgm", "verify_cert", "[test]0") modparam("tls_mgm", "require_cert", "[test]0") modparam("proto_tls", "tls_max_msg_chunks", 16) modparam("proto_tls", "tls_handshake_timeout", 200) ########################################################################### Aug 26 14:06:22 [1927] INFO:tls_openssl:openssl_tls_accept: New TLS connection from 11.22.33.44:9917 accepted Aug 26 14:06:22 [1927] DBG:tls_openssl:openssl_tls_accept: new TLS connection from 11.22.33.44:9917 using TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256 Aug 26 14:06:22 [1927] DBG:tls_openssl:openssl_tls_accept: local socket: 172.16.0.142:5061 Aug 26 14:06:22 [1927] INFO:tls_openssl:openssl_tls_accept: Client did not present a TLS certificate Aug 26 14:06:22 [1927] INFO:tls_openssl:tls_dump_cert_info: tls_accept: local TLS server certificate subject: /CN=*.example.com, issuer: /C=GB/ST=Greater Manchester/L=Salford/O=Sectigo Limited/CN=Sectigo RSA Domain Validation Secure Server CA Aug 26 14:06:22 [1927] DBG:tls_openssl:openssl_tls_update_fd: New fd is 4 Aug 26 14:06:22 [1927] DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request Aug 26 14:06:22 [1927] DBG:proto_tls:tls_read_req: tls_read_req end Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: Using the per connection buff Aug 26 14:06:23 [1927] DBG:tls_openssl:openssl_tls_update_fd: New fd is 4 Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: EOF received Aug 26 14:06:23 [1927] DBG:core:io_watch_del: [TCP_worker] io_watch_del op on index 0 4 (0x55ef6f9b8080, 4, 0, 0x10,0x3) fd_no=5 called Aug 26 14:06:23 [1927] DBG:core:tcpconn_release: releasing con 0x7f883464d580, state -1, fd=-1, id=73191278 Aug 26 14:06:23 [1927] DBG:core:tcpconn_release: extra_data 0x7f8834667ae0 Aug 26 14:06:23 [1929] DBG:core:handle_tcp_worker: response= 7f883464d580, -1 from tcp worker 0 (1) Aug 26 14:06:23 [1929] DBG:core:tcpconn_destroy: destroying connection 0x7f883464d580, flags 003c Aug 26 14:06:23 [1929] DBG:tls_openssl:openssl_tls_update_fd: New fd is 89 Aug 26 14:06:23 [1929] DBG:core:probe_max_sock_buff: getsockopt: snd is initially 425984 Aug 26 14:06:23 [1929] DBG:core:probe_max_sock_buff: using snd buffer of 416 kb Aug 26 14:06:23 [1929] DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 89 Aug 26 14:06:23 [1929] DBG:core:print_ip: tcpconn_new: new tcp connection to: 11.22.33.44 Aug 26 14:06:23 [1929] DBG:core:tcpconn_new: on port 43580, proto 3 Aug 26 14:06:23 [1929] DBG:core:tcpconn_add: hashes: 867, 879 Aug 26 14:06:23 [1929] DBG:core:handle_new_connect: new connection: 0x7f883464e098 89 flags: 001c Aug 26 14:06:23 [1929] DBG:core:send2worker: to tcp worker 1 (0), 0x7f883464e098 rw 1 Aug 26 14:06:23 [1927] DBG:proto_tls:proto_tls_conn_init: looking up TLS server domain [172.16.0.142:5061] Aug 26 14:06:23 [1927] DBG:tls_mgm:tls_find_server_domain: found TLS server domain: hcprod Aug 26 14:06:23 [1927] DBG:tls_openssl:openssl_tls_conn_init: Creating a whole new ssl connection Aug 26 14:06:23 [1927] DBG:tls_openssl:openssl_tls_conn_init: Setting in ACCEPT mode (server) Aug 26 14:06:23 [1927] DBG:core:handle_io: We have received conn 0x7f883464e098 with rw 1 on fd 4 Aug 26 14:06:23 [1927] DBG:core:io_watch_add: [TCP_worker] io_watch_add op (4 on 84) (0x55ef6f9b8080, 4, 19, 0x7f883464e098,1), fd_no=4/1024 Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: Using the global ( per process ) buff Aug 26 14:06:23 [1927] DBG:tls_openssl:openssl_tls_update_fd: New fd is 4 Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: SSL accept/connect still pending! Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: Using the global ( per process ) buff Aug 26 14:06:23 [1927] DBG:tls_openssl:openssl_tls_update_fd: New fd is 4 -- Volkan Oransoy -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Fri Aug 26 15:32:35 2022 From: johan at democon.be (johan) Date: Fri, 26 Aug 2022 17:32:35 +0200 Subject: [OpenSIPS-Users] registrant. In-Reply-To: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> References: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> Message-ID: Alexey, can you please resend your previous e mail ? wkr, On 24/08/2022 18:41, johan wrote: > Is there somebody who has a db extract on how to fill in a record in > registrar ? > > > wkr, > From suharik71 at gmail.com Mon Aug 29 12:35:04 2022 From: suharik71 at gmail.com (=?UTF-8?B?0JDQvdGC0L7QvSDQldGA0YjQvtCy?=) Date: Mon, 29 Aug 2022 15:35:04 +0300 Subject: [OpenSIPS-Users] dialplan out_var Message-ID: Hello friends! In version: opensips 3.2.8 (x86_64/linux) I observe strange behavior of the dialplan module. the value returned to the $var(out) variable is wrapped in quotes. In version 3.2.5 no such behavior was observed. this forces you to do additional work with the result obtained in order to use it further. my config if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { xlog("L_INFO", "$ci translated to var $var(dp_out) with attributes: '$var(dp_attrs)'\n"); ... } show in console /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 translated to var "000012345" with attributes: 'test' as you can see the value is wrapped in quotes if you try to use the value of the variable in some other place, for example in uac_replace. quotation marks are also present -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Mon Aug 29 13:43:34 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 29 Aug 2022 16:43:34 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: Hi, No quotes are added by the dialplan module at all. I think out value inherited the quotes from the input value, the From Display Name, which may be a quoted value. 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/29/22 3:35 PM, Антон Ершов wrote: > Hello friends! > > In version: opensips 3.2.8 (x86_64/linux) > I observe strange behavior of the dialplan module. the value returned > to the $var(out) variable is wrapped in quotes. In version 3.2.5 no > such behavior was observed. this forces you to do additional work with > the result obtained in order to use it further. > > my config > if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >       xlog("L_INFO", "$ci translated to var $var(dp_out) with > attributes: '$var(dp_attrs)'\n"); >       ... > } > > show in console > > /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 > translated to var "000012345" with attributes: 'test' > > as you can see the value is wrapped in quotes > if you try to use the value of the variable in some other place, for > example in uac_replace. quotation marks are also present > > _______________________________________________ > 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: From suharik71 at gmail.com Mon Aug 29 13:59:00 2022 From: suharik71 at gmail.com (=?UTF-8?B?0JDQvdGC0L7QvSDQldGA0YjQvtCy?=) Date: Mon, 29 Aug 2022 16:59:00 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: maybe it is so. but where can you go wrong with this simple rule "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" "repl_exp" "timerec" "disabled" "attrs" 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 partition is default /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is "00139939484" /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking with dpid 0 /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] "00139939484" /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator testing. Got result: 0 /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a matching rule 0x7f00fee33698: pr 0, match_exp .* /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's attrs are test /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied attributes are: test /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] "00139939484" /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[1] "00139939484" /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input "00139939484" with dpid 0 => output "00139939484" пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu : > Hi, > > No quotes are added by the dialplan module at all. I think out value > inherited the quotes from the input value, the From Display Name, which may > be a quoted value. > > 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/29/22 3:35 PM, Антон Ершов wrote: > > Hello friends! > > In version: opensips 3.2.8 (x86_64/linux) > I observe strange behavior of the dialplan module. the value returned to > the $var(out) variable is wrapped in quotes. In version 3.2.5 no such > behavior was observed. this forces you to do additional work with the > result obtained in order to use it further. > > my config > if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { > xlog("L_INFO", "$ci translated to var $var(dp_out) with attributes: > '$var(dp_attrs)'\n"); > ... > } > > show in console > > /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 translated > to var "000012345" with attributes: 'test' > > as you can see the value is wrapped in quotes > if you try to use the value of the variable in some other place, for > example in uac_replace. quotation marks are also present > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From h.menghani at cataleya.com Mon Aug 29 14:15:16 2022 From: h.menghani at cataleya.com (Hitesh Menghani) Date: Mon, 29 Aug 2022 14:15:16 +0000 Subject: [OpenSIPS-Users] opensips crash while using siprec module Message-ID: Hi All, opensips ver 2.4 Note: Same issue is there with opensips 3.3 ver We are trying to use siprec module and observed a crash while processing 200ok from remote while siprec module is being used. Below is the opensips config snapshot for using siprec if (is_method("INVITE")) { create_dialog(); rtpproxy_engage(); xlog("Engage SIPREC call recording to sip:10.57.1.110:5060 for $ci\n"); siprec_start_recording(sip:10.57.1.110:5060); b2b_init_request("b2bua", sip:sa at 10.57.1.198:5060); do_accounting("log"); exit; } Also find below backtrace of a crash - #0 0x00000000004dcc1a in parse_headers (msg=0xffffffffffffffff, flags=18446744073709551615, next=0) at parser/msg_parser.c:302 302 parser/msg_parser.c: No such file or directory. Missing separate debuginfos, use: debuginfo-install glibc-2.17-157.el7.x86_64 libuuid-2.23.2-33.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-17.el7.x86_64 (gdb) bt #0 0x00000000004dcc1a in parse_headers (msg=0xffffffffffffffff, flags=18446744073709551615, next=0) at parser/msg_parser.c:302 #1 0x00007f8bb9f271e1 in get_body () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so #2 0x00007f8bb9f2a430 in tm_start_recording () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so #3 0x00007f8bbc3dbd89 in run_trans_callbacks () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so #4 0x00007f8bbc3dc0af in run_trans_callbacks_locked () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so #5 0x00007f8bbc3a90de in _reply_light () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so #6 0x00007f8bbc3ad4d2 in t_reply_with_body () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so #7 0x00007f8bbae25de3 in b2b_send_reply () from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/b2b_entities.so #8 0x00007f8bbabf5931 in b2b_logic_notify_reply () ---Type to continue, or q to quit---q Thanks, Hitesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From kurgan-rus at inbox.ru Mon Aug 29 19:50:40 2022 From: kurgan-rus at inbox.ru (=?UTF-8?B?QWxleGV5IEthemFudHNldg==?=) Date: Mon, 29 Aug 2022 22:50:40 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?registrant=2E?= In-Reply-To: References: <64e2ade4-8424-9ca7-6fe0-da25a87e05f8@democon.be> Message-ID: <1661802640.672137940@f135.i.mail.ru> Hi Johan, sure I can   maybe you were confused because the ‘ @ ‘ symbol had been substituted in e-mail by ‘at’ word   I’ll try to post SQL insert once again, let’s have a look what will happen   INSERT INTO registrant (registrar, aor, username, password, binding_URI, expiry) VALUES (‘sip:11.11.11.11’, ’sip:79993332211 @ voip-isp.com’, ’79993332211’, ’PaSsWoRd’, ‘sip:79993332211 @ 22.22.22.22’, 300);   where: - 11.11.11.11 is VoIP ISP IP address, - voip-isp.com is a domain you should use for authentication (depends on ISP settings, may be sip:79993332211 @ 11.11.11.11), - 79993332211 is your username (usually equals to phone number, but also depends on ISP settings), - sip:79993332211 @ 22.22.22.22 - this will form a Contact: header and must contain IP address of your OpenSIPS (obviously you can insert here some other IP address, and the calls from ISP proxy will go there, but in most cases it’s common to write here the IP address of your OpenSIPS), 300 is an registration expiration value in seconds, you ISP may require some other value.   ----------------------------------------------- BR, Alexey https://alexeyka.zantsev.com/   -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Aug 30 06:26:02 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 30 Aug 2022 09:26:02 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: Your DP rule is doing nothing, as transformation - it is matching everything and returning it as output..so not sure what are your expectations here. 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/29/22 4:59 PM, Антон Ершов wrote: > maybe it is so. > but where can you go wrong with this simple rule > > "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" > "repl_exp" "timerec" "disabled" "attrs" > 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" > > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 > partition is default > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking with > dpid 0 > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator > testing. Got result: 0 > /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a matching > rule 0x7f00fee33698: pr 0, match_exp .* > /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's attrs > are test > /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied > attributes are: test > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[1] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input > "00139939484" with dpid 0 => output "00139939484" > > пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu >: > > Hi, > > No quotes are added by the dialplan module at all. I think out > value inherited the quotes from the input value, the From Display > Name, which may be a quoted value. > > 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/29/22 3:35 PM, Антон Ершов wrote: >> Hello friends! >> >> In version: opensips 3.2.8 (x86_64/linux) >> I observe strange behavior of the dialplan module. the value >> returned to the $var(out) variable is wrapped in quotes. In >> version 3.2.5 no such behavior was observed. this forces you to >> do additional work with the result obtained in order to use it >> further. >> >> my config >> if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >>       xlog("L_INFO", "$ci translated to var $var(dp_out) with >> attributes: '$var(dp_attrs)'\n"); >>       ... >> } >> >> show in console >> >> /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 >> translated to var "000012345" with attributes: 'test' >> >> as you can see the value is wrapped in quotes >> if you try to use the value of the variable in some other place, >> for example in uac_replace. quotation marks are also present >> >> _______________________________________________ >> 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: From suharik71 at gmail.com Tue Aug 30 07:18:59 2022 From: suharik71 at gmail.com (=?UTF-8?B?0JDQvdGC0L7QvSDQldGA0YjQvtCy?=) Date: Tue, 30 Aug 2022 10:18:59 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: that's the point. there are no conversions, but quotes appear вт, 30 авг. 2022 г. в 09:26, Bogdan-Andrei Iancu : > Your DP rule is doing nothing, as transformation - it is matching > everything and returning it as output..so not sure what are your > expectations here. > > 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/29/22 4:59 PM, Антон Ершов wrote: > > maybe it is so. > but where can you go wrong with this simple rule > > "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" > "repl_exp" "timerec" "disabled" "attrs" > 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" > > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 > partition is default > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking with dpid > 0 > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator testing. > Got result: 0 > /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a matching rule > 0x7f00fee33698: pr 0, match_exp .* > /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's attrs are > test > /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied attributes > are: test > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[1] > "00139939484" > /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input > "00139939484" with dpid 0 => output "00139939484" > > пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu : > >> Hi, >> >> No quotes are added by the dialplan module at all. I think out value >> inherited the quotes from the input value, the From Display Name, which may >> be a quoted value. >> >> 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/29/22 3:35 PM, Антон Ершов wrote: >> >> Hello friends! >> >> In version: opensips 3.2.8 (x86_64/linux) >> I observe strange behavior of the dialplan module. the value returned to >> the $var(out) variable is wrapped in quotes. In version 3.2.5 no such >> behavior was observed. this forces you to do additional work with the >> result obtained in order to use it further. >> >> my config >> if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >> xlog("L_INFO", "$ci translated to var $var(dp_out) with attributes: >> '$var(dp_attrs)'\n"); >> ... >> } >> >> show in console >> >> /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 >> translated to var "000012345" with attributes: 'test' >> >> as you can see the value is wrapped in quotes >> if you try to use the value of the variable in some other place, for >> example in uac_replace. quotation marks are also present >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Aug 30 07:25:20 2022 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 30 Aug 2022 10:25:20 +0300 Subject: [OpenSIPS-Users] opensips crash while using siprec module In-Reply-To: References: Message-ID: <1de86bf1-e155-a2b8-ac3f-98d6a44a4da3@opensips.org> Hi, Hitesh! You are using both dialog and B2B for the same call - this is not supported in OpenSIPS. Moreover, SIPREC is not working with B2B. So you either have a setup with dialog (where siprec can be enabled) or b2b (siprec is not available). Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 8/29/22 17:15, Hitesh Menghani wrote: > Hi All, > > opensips ver 2.4 > > Note: Same issue is there with opensips 3.3 ver > > We are trying to use siprec module and observed a crash while processing > 200ok from remote while siprec module is being used. > > Below is the opensips config snapshot for using siprec > > if (is_method("INVITE")) { > >                               create_dialog(); > >                               rtpproxy_engage(); > >                               xlog("Engage SIPREC call recording to > sip:10.57.1.110:5060 for $ci\n"); > > > siprec_start_recording(sip:10.57.1.110:5060 ); > >                               b2b_init_request("b2bua", > sip:sa at 10.57.1.198:5060 ); > >                               do_accounting("log"); > >                               exit; > >                } > > Also find below backtrace of a crash – > > #0  0x00000000004dcc1a in parse_headers (msg=0xffffffffffffffff, > >     flags=18446744073709551615, next=0) at parser/msg_parser.c:302 > > 302        parser/msg_parser.c: No such file or directory. > > Missing separate debuginfos, use: debuginfo-install > glibc-2.17-157.el7.x86_64 libuuid-2.23.2-33.el7.x86_64 > libxml2-2.9.1-6.el7_2.3.x86_64 xz-libs-5.2.2-1.el7.x86_64 > zlib-1.2.7-17.el7.x86_64 > > (gdb) bt > > #0  0x00000000004dcc1a in parse_headers (msg=0xffffffffffffffff, > >     flags=18446744073709551615, next=0) at parser/msg_parser.c:302 > > #1  0x00007f8bb9f271e1 in get_body () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so > > #2  0x00007f8bb9f2a430 in tm_start_recording () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/siprec.so > > #3  0x00007f8bbc3dbd89 in run_trans_callbacks () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so > > #4  0x00007f8bbc3dc0af in run_trans_callbacks_locked () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so > > #5  0x00007f8bbc3a90de in _reply_light () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so > > #6  0x00007f8bbc3ad4d2 in t_reply_with_body () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/tm.so > > #7  0x00007f8bbae25de3 in b2b_send_reply () > >    from /opt/esbc/opensips-2.4.11/lib64/opensips/modules/b2b_entities.so > > #8  0x00007f8bbabf5931 in b2b_logic_notify_reply () > > ---Type to continue, or q to quit---q > > Thanks, > > Hitesh > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Tue Aug 30 07:52:08 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 30 Aug 2022 10:52:08 +0300 Subject: [OpenSIPS-Users] Dispatcher within a K8s environment In-Reply-To: References: <41808745-ca5c-c0b2-1613-1b06e58b89d2@opensips.org> Message-ID: <4181b79f-b3d6-0bba-e5f8-c0911a2ae7d8@opensips.org> Hi Jonathan, You mean something similar to that option in drouting ? If so, yes, it would make sense IMO. 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/26/22 5:36 PM, Jonathan Hunter wrote: > > Hi Ben, > > Great thank you for that I may well switch for now to drouting. > > @Bogdan-Andrei Iancu is it worth me > raising anything against dispatcher in terms of a change request for > dns behaviour? > > Many thanks both. > > Jon > > Sent from Mail for > Windows > > *From: *Ben Newlin > *Sent: *25 August 2022 18:57 > *To: *OpenSIPS users mailling list ; > Bogdan-Andrei Iancu > *Subject: *Re: [OpenSIPS-Users] Dispatcher within a K8s environment > > The drouting module has a parameter that allows you to disable the DNS > lookup. > > https://opensips.org/docs/modules/3.2.x/drouting.html#param_force_dns > > > Ben Newlin > > *From: *Users on behalf of Jonathan > Hunter > *Date: *Thursday, August 25, 2022 at 4:54 AM > *To: *Bogdan-Andrei Iancu , OpenSIPS users > mailling list > *Subject: *Re: [OpenSIPS-Users] Dispatcher within a K8s environment > > * EXTERNAL EMAIL - Please use caution with links and attachments * > > Hi Bogdan, > > Yes it would appear K8s implementations would be a very good topic at > the Summit that is for sure! > > I understand your comments on dispatcher, its unfortunate as > everything else is working fine. > > There was a suggestion to add a loopback address for example and then > update  when DNS has updated and records resolve? > > Is there any benefit in using dr_routing instead or will this > behaviour be the same in the event of a dns lookup failure? > > Thanks for the response! > > Jon > > Sent from Mail > > for Windows > > *From: *Bogdan-Andrei Iancu > *Sent: *24 August 2022 12:29 > *To: *OpenSIPS users mailling list ; > Jonathan Hunter > *Subject: *Re: [OpenSIPS-Users] Dispatcher within a K8s environment > > Hi Jonathan, > > I guess this will be a good topic (DS and K8S) for the OpenSIPS Summit > in Athens - I think this is the 3rd time in the last week coming > across it :) > > Unfortunately there is no way to skip at the moment that DNS failure > when loading the destinations :(....even more, there some code that > relies on the fact that there is an "IP" attached to any > destination.....And I just checked, a local error in sending the ping > (like the DNS err) does not results in marking the destination as > failed or so..... so it is not so straight as ignoring the DNS error. > > 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/24/22 12:24 AM, Jonathan Hunter wrote: > > Hi All, > > I have a query around dispatcher behaviour, I am running 3.2 in a > k8s environment. > > I have 2 freeswitch instances defined in a destination set, both > of which are pods. > > As people may be aware its fun implementing in k8s as pods can > restart and disappear at times so I ideally want this reflected in > the cache and output of opensips-cli -x mi ds_list where I was > hoping the freeswitch entries would be defined but with a state of > probing or inactive. > > With my current setup, when restarting opensips for example, I > have the dispatcher table populated in postgres db , and if > opensips cant resolve the URI it wont load it into cache, like > wise if opensips is running and freeswitch pod drops, I see this > in the logs; > > Aug 23 21:22:01 [55] ERROR:dispatcher:add_dest2list: could not > resolve freeswitch-opensips-deployment-1.freeswitch-opensips, > skipping it > > Aug 23 21:22:01 [55] WARNING:dispatcher:ds_load_data: failed to > add destination > > > in group 10 > > I therefore don’t see it listed in cache when I run ds_list. > > Does anyone know if its possible to tweak dispatcher to always > load the database entries into cache at startup, and also set > their status to probing/inactive if not reachable due to a > resolving issue as above? > > My dispatcher settings are; > > #### Dynamic routing > > loadmodule "dispatcher.so" > > modparam("dispatcher", "db_url", "postgres://x.x.x.x/opensips") > > modparam("dispatcher", "ds_probing_mode", 1) > > modparam("dispatcher", "ds_probing_threshhold", 1) > > modparam("dispatcher", "persistent_state", 0) > > modparam("dispatcher", "ds_ping_interval", 5) > > modparam("dispatcher", "table_name", "dispatcher") > > modparam("dispatcher", "cluster_id", 1) > > Hope that makes sense! > > Many thanks > > Jon > > > > _______________________________________________ > > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 6C8FCB656E874AC19425788EDEE1758D.png Type: image/png Size: 140 bytes Desc: not available URL: From bogdan at opensips.org Tue Aug 30 12:56:37 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 30 Aug 2022 15:56:37 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: Again, your DP rule is performing NO change over the input. The whole input, as received, it provided as output. And the quotes you see in the output value are part of the input value. 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/30/22 10:18 AM, Антон Ершов wrote: > that's the point. there are no conversions, but quotes appear > > вт, 30 авг. 2022 г. в 09:26, Bogdan-Andrei Iancu >: > > Your DP rule is doing nothing, as transformation - it is matching > everything and returning it as output..so not sure what are your > expectations here. > > 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/29/22 4:59 PM, Антон Ершов wrote: >> maybe it is so. >> but where can you go wrong with this simple rule >> >> "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" >> "repl_exp" "timerec" "disabled" "attrs" >> 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" >> >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 >> partition is default >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is >> "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking >> with dpid 0 >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: >> test_match:[0] "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator >> testing. Got result: 0 >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a >> matching rule 0x7f00fee33698: pr 0, match_exp .* >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's >> attrs are test >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied >> attributes are: test >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: >> test_match:[0] "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: >> test_match:[1] "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input >> "00139939484" with dpid 0 => output "00139939484" >> >> пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu >> >: >> >> Hi, >> >> No quotes are added by the dialplan module at all. I think >> out value inherited the quotes from the input value, the From >> Display Name, which may be a quoted value. >> >> 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/29/22 3:35 PM, Антон Ершов wrote: >>> Hello friends! >>> >>> In version: opensips 3.2.8 (x86_64/linux) >>> I observe strange behavior of the dialplan module. the value >>> returned to the $var(out) variable is wrapped in quotes. In >>> version 3.2.5 no such behavior was observed. this forces you >>> to do additional work with the result obtained in order to >>> use it further. >>> >>> my config >>> if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >>>       xlog("L_INFO", "$ci translated to var $var(dp_out) >>> with attributes: '$var(dp_attrs)'\n"); >>>       ... >>> } >>> >>> show in console >>> >>> /usr/sbin/opensips[30318]: >>> 287b5bea-26c4-11ed-abcd-016f252b0962 translated to var >>> "000012345" with attributes: 'test' >>> >>> as you can see the value is wrapped in quotes >>> if you try to use the value of the variable in some other >>> place, for example in uac_replace. quotation marks are also >>> present >>> >>> _______________________________________________ >>> 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: From bogdan at opensips.org Tue Aug 30 13:20:11 2022 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 30 Aug 2022 16:20:11 +0300 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: References: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> <26c4237e-2432-7756-dfe6-d7f7afde7d0b@opensips.org> Message-ID: <5451cbeb-55f1-3e4d-ec0e-c6526cb13a90@opensips.org> Hi Li, The INVITE in #77 is an initial INVITE, connecting to a new party (as a result of the bridging), so the TO hdr in that INVITE is dictated by the B2B logic - as you can see the TO URI is the same as RURI, pointing to the new party in the bridging. 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/25/22 10:57 PM, Li Cai wrote: > > [This email is resent for the last one is oversized] > > Hi Bodgan, > > Thanks a lot for the help, the pcap file is attached.  The call flow > is as – > >    #11.                 INVITE from the caller on 10.10.8.131 to > B2BProxy 10.10.9.205 > >    #15.                 Forwarded INVITE from B2BProxy with the > expected To header to SIP UA1 > >     .. . the call is setup and then b2b_bridge is triggered  … > >    #75.                 B2BProxy sent reINVITE to the caller > >    #77.                 B2BProxy sent INVITE to SIP UA2 with the > unaccepted To header > >    #79.                 SIP UA2 rejected the call > > The step #77 And #79 shows the problem, that the call was rejected as > the To header in INVITE is not using the UA2’s IP instead of > B2BProxy’s IP as domain name, which is required in our system. > > In our opensips.cfg script, we have already included clauses like > remove_hf(“To”) and append_hf(“To …”) but seems like they only work > before b2b_bridge occurs. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > > *Sent:* August 25, 2022 3:05 AM > *To:* Li Cai >; > OpenSIPS users mailling list > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after executing a > MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > Hi Li, > > Somehow we are going in circles here :). So, could you post a pcap for > call going via your B2B  (showing all in and out SIP messages) and > mention which frame is the outgoing request you cannot modify ? > > 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/24/22 6:50 PM, Li Cai wrote: > > Hi Bogdan, > > Thanks for the explanation. I mean that the local_route can take > effect for the forwarded INVITE(from incoming ones) in our proxy, > but not after b2b_bridge. I’ll do more debugging on it since the > messages should be visible. Thank you very much. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > > *Sent:* August 24, 2022 10:33 AM > *To:* Li Cai ; > OpenSIPS users mailling list > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after executing > a MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > Hi Li, > > All SIP requests generated by `b2b_bridge` are to be visible in > local_route. And on the contrary, the incoming (received) requests > DO NOT trigger local route. > > 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/24/22 4:34 PM, Li Cai wrote: > > Hi Bogdan, > > Yes, we have put the changes by calling remove_hf() and > append_hf() in the ‘local_route’, those functions for new > incoming INVITE but not the INVITE sent out by ‘b2b_bridge’. > > Thanks, > > Li > > *From:*Bogdan-Andrei Iancu > > *Sent:* August 24, 2022 7:18 AM > *To:* OpenSIPS users mailling list > ; Li Cai > > *Subject:* Re: [OpenSIPS-Users] Modify the headers after > executing a MI function in B2B_LOGIC module > > *WARNING: External Email: Exercise Caution* > > > Hi Li, > > Have you tried to use the local_route in order to do custom > changes on the outgoing requests generated by the B2B bridging ? > > 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/23/22 10:34 PM, Li Cai wrote: > > Hi, > > I’m working on a change for a B2BUA based on OpenSIPs 2.4, > but not sure if the function is supported or if it has > been supported in the later versions. > > We have used the MI command b2b_bridge to bridge existing > calls from one entity to another and it works, the > scenario is the same as expected. While besides this, we > also need to modify one of the headers of the INVITEs > sending to the new destination in this scenario,  our > scripts in the opensips.cfg can’t take any effect. > > 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: From Li.Cai at comtech.com Tue Aug 30 13:32:03 2022 From: Li.Cai at comtech.com (Li Cai) Date: Tue, 30 Aug 2022 13:32:03 +0000 Subject: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module In-Reply-To: <5451cbeb-55f1-3e4d-ec0e-c6526cb13a90@opensips.org> References: <3d1df756-871c-312d-6214-4072b48be44d@opensips.org> <26c4237e-2432-7756-dfe6-d7f7afde7d0b@opensips.org> <5451cbeb-55f1-3e4d-ec0e-c6526cb13a90@opensips.org> Message-ID: Hi Bogdan, Thank you very much for the help, I have located the issue in our script. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 30, 2022 9:20 AM To: Li Cai ; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, The INVITE in #77 is an initial INVITE, connecting to a new party (as a result of the bridging), so the TO hdr in that INVITE is dictated by the B2B logic - as you can see the TO URI is the same as RURI, pointing to the new party in the bridging. 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/25/22 10:57 PM, Li Cai wrote: [This email is resent for the last one is oversized] Hi Bodgan, Thanks a lot for the help, the pcap file is attached. The call flow is as - #11. INVITE from the caller on 10.10.8.131 to B2BProxy 10.10.9.205 #15. Forwarded INVITE from B2BProxy with the expected To header to SIP UA1 .. . the call is setup and then b2b_bridge is triggered ... #75. B2BProxy sent reINVITE to the caller #77. B2BProxy sent INVITE to SIP UA2 with the unaccepted To header #79. SIP UA2 rejected the call The step #77 And #79 shows the problem, that the call was rejected as the To header in INVITE is not using the UA2's IP instead of B2BProxy's IP as domain name, which is required in our system. In our opensips.cfg script, we have already included clauses like remove_hf("To") and append_hf("To ...") but seems like they only work before b2b_bridge occurs. Thanks, Li From: Bogdan-Andrei Iancu > Sent: August 25, 2022 3:05 AM To: Li Cai >; OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Somehow we are going in circles here :). So, could you post a pcap for call going via your B2B (showing all in and out SIP messages) and mention which frame is the outgoing request you cannot modify ? 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/24/22 6:50 PM, Li Cai wrote: Hi Bogdan, Thanks for the explanation. I mean that the local_route can take effect for the forwarded INVITE(from incoming ones) in our proxy, but not after b2b_bridge. I'll do more debugging on it since the messages should be visible. Thank you very much. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 10:33 AM To: Li Cai ; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, All SIP requests generated by `b2b_bridge` are to be visible in local_route. And on the contrary, the incoming (received) requests DO NOT trigger local route. 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/24/22 4:34 PM, Li Cai wrote: Hi Bogdan, Yes, we have put the changes by calling remove_hf() and append_hf() in the 'local_route', those functions for new incoming INVITE but not the INVITE sent out by 'b2b_bridge'. Thanks, Li From: Bogdan-Andrei Iancu Sent: August 24, 2022 7:18 AM To: OpenSIPS users mailling list ; Li Cai Subject: Re: [OpenSIPS-Users] Modify the headers after executing a MI function in B2B_LOGIC module WARNING: External Email: Exercise Caution Hi Li, Have you tried to use the local_route in order to do custom changes on the outgoing requests generated by the B2B bridging ? 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/23/22 10:34 PM, Li Cai wrote: Hi, I'm working on a change for a B2BUA based on OpenSIPs 2.4, but not sure if the function is supported or if it has been supported in the later versions. We have used the MI command b2b_bridge to bridge existing calls from one entity to another and it works, the scenario is the same as expected. While besides this, we also need to modify one of the headers of the INVITEs sending to the new destination in this scenario, our scripts in the opensips.cfg can't take any effect. 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: From staskobzar at gmail.com Tue Aug 30 14:11:57 2022 From: staskobzar at gmail.com (Stas Kobzar) Date: Tue, 30 Aug 2022 10:11:57 -0400 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: Hi, $fn is from name and name maybe quoted in the header value. Try to use $fU to have username part (actual number) On Tue, Aug 30, 2022 at 9:00 AM Bogdan-Andrei Iancu wrote: > Again, > > your DP rule is performing NO change over the input. The whole input, as > received, it provided as output. And the quotes you see in the output value > are part of the input value. > > 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/30/22 10:18 AM, Антон Ершов wrote: > > that's the point. there are no conversions, but quotes appear > > вт, 30 авг. 2022 г. в 09:26, Bogdan-Andrei Iancu : > >> Your DP rule is doing nothing, as transformation - it is matching >> everything and returning it as output..so not sure what are your >> expectations here. >> >> 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/29/22 4:59 PM, Антон Ершов wrote: >> >> maybe it is so. >> but where can you go wrong with this simple rule >> >> "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" >> "repl_exp" "timerec" "disabled" "attrs" >> 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" >> >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 >> partition is default >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is >> "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking with >> dpid 0 >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] >> "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator >> testing. Got result: 0 >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a matching rule >> 0x7f00fee33698: pr 0, match_exp .* >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's attrs are >> test >> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied attributes >> are: test >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] >> "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[1] >> "00139939484" >> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input >> "00139939484" with dpid 0 => output "00139939484" >> >> пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu : >> >>> Hi, >>> >>> No quotes are added by the dialplan module at all. I think out value >>> inherited the quotes from the input value, the From Display Name, which may >>> be a quoted value. >>> >>> 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/29/22 3:35 PM, Антон Ершов wrote: >>> >>> Hello friends! >>> >>> In version: opensips 3.2.8 (x86_64/linux) >>> I observe strange behavior of the dialplan module. the value returned to >>> the $var(out) variable is wrapped in quotes. In version 3.2.5 no such >>> behavior was observed. this forces you to do additional work with the >>> result obtained in order to use it further. >>> >>> my config >>> if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >>> xlog("L_INFO", "$ci translated to var $var(dp_out) with >>> attributes: '$var(dp_attrs)'\n"); >>> ... >>> } >>> >>> show in console >>> >>> /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 >>> translated to var "000012345" with attributes: 'test' >>> >>> as you can see the value is wrapped in quotes >>> if you try to use the value of the variable in some other place, for >>> example in uac_replace. quotation marks are also present >>> >>> _______________________________________________ >>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From suharik71 at gmail.com Tue Aug 30 14:14:31 2022 From: suharik71 at gmail.com (=?UTF-8?B?0JDQvdGC0L7QvSDQldGA0YjQvtCy?=) Date: Tue, 30 Aug 2022 17:14:31 +0300 Subject: [OpenSIPS-Users] dialplan out_var In-Reply-To: References: Message-ID: Yes. exactly I apologize for my stupidity вт, 30 авг. 2022 г. в 17:12, Stas Kobzar : > Hi, > $fn is from name and name maybe quoted in the header value. > Try to use $fU to have username part (actual number) > > On Tue, Aug 30, 2022 at 9:00 AM Bogdan-Andrei Iancu > wrote: > >> Again, >> >> your DP rule is performing NO change over the input. The whole input, as >> received, it provided as output. And the quotes you see in the output value >> are part of the input value. >> >> 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/30/22 10:18 AM, Антон Ершов wrote: >> >> that's the point. there are no conversions, but quotes appear >> >> вт, 30 авг. 2022 г. в 09:26, Bogdan-Andrei Iancu : >> >>> Your DP rule is doing nothing, as transformation - it is matching >>> everything and returning it as output..so not sure what are your >>> expectations here. >>> >>> 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/29/22 4:59 PM, Антон Ершов wrote: >>> >>> maybe it is so. >>> but where can you go wrong with this simple rule >>> >>> "id" "dpid" "pr" "match_op" "match_exp" "match_flags" "subst_exp" >>> "repl_exp" "timerec" "disabled" "attrs" >>> 1 0 0 1 ".*" 0 "^(.*)$" "\1" 0 "test" >>> >>> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: dpid is 0 >>> partition is default >>> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input is >>> "00139939484" >>> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: checking with >>> dpid 0 >>> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] >>> "00139939484" >>> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Regex operator >>> testing. Got result: 0 >>> /usr/sbin/opensips[30317]: DBG:dialplan:translate: Found a matching rule >>> 0x7f00fee33698: pr 0, match_exp .* >>> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the rule's attrs are >>> test >>> /usr/sbin/opensips[30317]: DBG:dialplan:translate: the copied attributes >>> are: test >>> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[0] >>> "00139939484" >>> /usr/sbin/opensips[30317]: DBG:dialplan:test_match: test_match:[1] >>> "00139939484" >>> /usr/sbin/opensips[30317]: DBG:dialplan:dp_translate_f: input >>> "00139939484" with dpid 0 => output "00139939484" >>> >>> пн, 29 авг. 2022 г. в 16:43, Bogdan-Andrei Iancu : >>> >>>> Hi, >>>> >>>> No quotes are added by the dialplan module at all. I think out value >>>> inherited the quotes from the input value, the From Display Name, which may >>>> be a quoted value. >>>> >>>> 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/29/22 3:35 PM, Антон Ершов wrote: >>>> >>>> Hello friends! >>>> >>>> In version: opensips 3.2.8 (x86_64/linux) >>>> I observe strange behavior of the dialplan module. the value returned >>>> to the $var(out) variable is wrapped in quotes. In version 3.2.5 no such >>>> behavior was observed. this forces you to do additional work with the >>>> result obtained in order to use it further. >>>> >>>> my config >>>> if (dp_translate(0, $fn, $var(dp_out), $var(dp_attrs))) { >>>> xlog("L_INFO", "$ci translated to var $var(dp_out) with >>>> attributes: '$var(dp_attrs)'\n"); >>>> ... >>>> } >>>> >>>> show in console >>>> >>>> /usr/sbin/opensips[30318]: 287b5bea-26c4-11ed-abcd-016f252b0962 >>>> translated to var "000012345" with attributes: 'test' >>>> >>>> as you can see the value is wrapped in quotes >>>> if you try to use the value of the variable in some other place, for >>>> example in uac_replace. quotation marks are also present >>>> >>>> _______________________________________________ >>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>>> >>> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pavel.ekshine at gmail.com Tue Aug 30 18:31:08 2022 From: pavel.ekshine at gmail.com (Pavel Ekshin) Date: Tue, 30 Aug 2022 21:31:08 +0300 Subject: [OpenSIPS-Users] OpenSIPS 3.2.7 tracer module for sip dialogs leads to an endless loop Message-ID: Hi there, I try very basic scenario with tracing sip dialogs in OpenSIPS 3.2.7, and this scenario leads in an endless loop inside Opensips for SIP messages. Maybe someone is similarly affected or can point to the error on the route scenario? I use out of box residential configuration. I read the tracer module doc (https://opensips.org/docs/modules/devel/tracer.html), but dialog examples from doc also lead to loops. I also tried with transactions, but they are looped too. Trace for messages works fine. I think I miss some points. MariaDB [opensips]> select method,COUNT(*) from sip_trace group by method; +--------+----------+ | method | COUNT(*) | +--------+----------+ | ACK | 2625 | | BYE | 2270 | | INVITE | 219 | +--------+----------+ Below my config: # This script was generated via "make menuconfig", from # the "Residential" scenario. ####### Global Parameters ######### /* uncomment the following lines to enable debugging */ #debug_mode=yes log_level=4 xlog_level=4 log_stderror=no log_facility=LOG_LOCAL0 udp_workers=4 /* uncomment the next line to enable the auto temporary blacklisting of not available destinations (default disabled) */ #disable_dns_blacklist=no /* uncomment the next line to enable IPv6 lookup after IPv4 dns lookup failures (default disabled) */ #dns_try_ipv6=yes socket=udp:172.16.34.91:5060 # CUSTOMIZE ME socket=tcp:172.16.34.91:5060 # CUSTOMIZE ME ####### Modules Section ######## #set module path mpath="/usr/lib64/opensips/modules" #### AVPOPS module loadmodule "avpops.so" modparam("avpops", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### HTTPD module loadmodule "httpd.so" modparam("httpd", "port", 8888) modparam("httpd", "ip", "127.0.0.1") #### MI_HTTP module loadmodule "mi_http.so" modparam("mi_http", "root", "mi") #### JSON module loadmodule "json.so" #### SIGNALING module loadmodule "signaling.so" #### StateLess module loadmodule "sl.so" #### Transaction Module loadmodule "tm.so" modparam("tm", "fr_timeout", 5) modparam("tm", "fr_inv_timeout", 30) modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "onreply_avp_mode", 1) #### Record Route Module loadmodule "rr.so" /* do not append from tag to the RR (no need for this script) */ modparam("rr", "append_fromtag", 0) #modparam("rr", "append_fromtag", 1) # DL #### MAX ForWarD module loadmodule "maxfwd.so" #### SIP MSG OPerationS module loadmodule "sipmsgops.so" #### FIFO Management Interface loadmodule "mi_fifo.so" modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo") modparam("mi_fifo", "fifo_mode", 0666) #### MYSQL module loadmodule "db_mysql.so" #### PERMISSIONS module loadmodule "permissions.so" modparam("permissions", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### USeR LOCation module loadmodule "usrloc.so" modparam("usrloc", "nat_bflag", "NAT") modparam("usrloc", "working_mode_preset", "single-instance-sql-write-back") modparam("usrloc", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### REGISTRAR module loadmodule "registrar.so" modparam("registrar", "tcp_persistent_flag", "TCP_PERSISTENT") /* uncomment the next line not to allow more than 10 contacts per AOR */ #modparam("registrar", "max_contacts", 10) #### ACCounting module loadmodule "acc.so" /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_cancels", 0) /* by default we do not adjust the direct of the sequential requests. if you enable this parameter, be sure to enable "append_fromtag" in "rr" module */ modparam("acc", "detect_direction", 0) modparam("acc", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### AUTHentication modules loadmodule "auth.so" loadmodule "auth_db.so" modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME modparam("auth_db", "load_credentials", "") #### ALIAS module loadmodule "alias_db.so" modparam("alias_db", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### DOMAIN module loadmodule "domain.so" modparam("domain", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME modparam("domain", "db_mode", 1) # Use caching modparam("auth_db|usrloc", "use_domain", 1) #### DIALOG module loadmodule "dialog.so" modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "default_timeout", 21600) # 6 hours timeout modparam("dialog", "db_mode", 2) modparam("dialog", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### DIALPLAN module loadmodule "dialplan.so" modparam("dialplan", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME #### DYNAMMIC ROUTING module loadmodule "drouting.so" modparam("drouting", "db_url", "mysql://opensips:opensipsrw at localhost/opensips") # CUSTOMIZE ME modparam("drouting", "use_partitions", 0) #### TRACE module loadmodule "tracer.so" modparam("tracer", "trace_on", 1) modparam("tracer", "trace_id","[tid]uri=mysql://opensips:opensipsrw at localhost /opensips;table=sip_trace;") modparam("tracer", "trace_id","[tid]uri=sip:172.16.34.91:5060") modparam("tracer", "trace_local_ip", "172.16.34.91") #### TCP/UDP socket module loadmodule "proto_udp.so" loadmodule "proto_tcp.so" ####### Routing Logic ######## # main request routing logic route{ if (!has_totag()) { if(is_method("INVITE") ) { # We need to use the dialog module to have the outgoing ACK traced trace("tid", "d", "sip"); } } else { match_dialog(); } # if (!is_method("INVITE,ACK,BYE,PRACK")) { # # Requests that are not part of an established dialog will be transaction base traced # trace("tid", "t", "sip"); #xlog("Message not in dialog - $rm\n"); # } # trace("tid", "t", "sip"); if (!mf_process_maxfwd_header(10)) { send_reply(483,"Too Many Hops"); exit; } #if (has_totag()) { # loose_route(); # if($DLG_status!=NULL) # if(!validate_dialog()) # fix_route_dialog(); #} if (has_totag()) { # handle hop-by-hop ACK (no routing required) if ( is_method("ACK") && t_check_trans() ) { t_relay(); exit; } # sequential request within a dialog should # take the path determined by record-routing if ( !loose_route() ) { # we do record-routing for all our traffic, so we should not # receive any sequential requests without Route hdr. send_reply(404,"Not here"); exit; } # validate the sequential request against dialog if ( $DLG_status!=NULL && !validate_dialog() ) { xlog("In-Dialog $rm from $si (callid=$ci) is not valid according to dialog\n"); ## exit; } if (is_method("BYE")) { # do accounting even if the transaction fails do_accounting("db","failed"); } # route it out to whatever destination was set by loose_route() # in $du (destination URI). route(relay); exit; } # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } # absorb retransmissions, but do not create transaction t_check_trans(); if ( !(is_method("REGISTER") || is_from_gw() ) ) { if (is_from_local()) { # authenticate if from local subscriber # authenticate all initial non-REGISTER request that pretend to be # generated by local subscriber (domain from FROM URI is local) if (!proxy_authorize("", "subscriber")) { proxy_challenge("", "auth"); exit; } if ($au!=$fU) { send_reply(403,"Forbidden auth ID"); exit; } consume_credentials(); # caller authenticated } else { # if caller is not local, then called number must be local if (!is_uri_host_local()) { send_reply(403,"Relay Forbidden"); exit; } } } # preloaded route checking if (loose_route()) { xlog("L_ERR", "Attempt to route with preloaded Route's [$fu/$tu/$ru/$ci]"); if (!is_method("ACK")) send_reply(403,"Preload Route denied"); exit; } # record routing if (!is_method("REGISTER|MESSAGE")) record_route(); # account only INVITEs if (is_method("INVITE")) { # create dialog with timeout if ( !create_dialog("B") ) { send_reply(500,"Internal Server Error"); exit; } do_accounting("db"); } if (!is_uri_host_local()) { append_hf("P-hint: outbound\r\n"); route(relay); } # requests for my domain if (is_method("PUBLISH|SUBSCRIBE")) { send_reply(503, "Service Unavailable"); exit; } if (is_method("REGISTER")) { # authenticate the REGISTER requests if (!www_authorize("", "subscriber")) { www_challenge("", "auth"); exit; } if ($au!=$tU) { send_reply(403,"Forbidden auth ID"); exit; } if ($socket_in(proto) == "tcp") setflag("TCP_PERSISTENT"); # store the registration and generate a SIP reply if (!save("location")) xlog("failed to register AoR $tu\n"); exit; } if ($rU==NULL) { # request with no Username in RURI send_reply(484,"Address Incomplete"); exit; } # apply DB based aliases alias_db_lookup("dbaliases"); # apply transformations from dialplan table $avp(src) = $rU; dp_translate(10, "$rU", $rU, $var(attrs)); xlog("Successfully translate from $avp(src) to $rU attr = $var(attrs)\n"); if (dp_translate(10,"$rU/$rU") ) { #strip(1); if (!do_routing(0)) { send_reply(500,"No PSTN Route found"); exit; } route(relay); exit; } # do lookup with method filtering if (!lookup("location","m")) { if (!db_does_uri_exist("$ru","subscriber")) { send_reply(420,"Bad Extension"); exit; } t_reply(404, "Not Found"); exit; } # when routing via usrloc, log the missed calls also do_accounting("db","missed"); route(relay); } route[relay] { # for INVITEs enable some additional helper routes # check_source_address(0) - mean any sources in address table if (is_method("INVITE") && check_source_address(0)) { t_on_branch("per_branch_ops"); t_on_reply("handle_nat"); t_on_failure("missed_call"); } if (is_method("INVITE") && !check_source_address(0)) { send_reply(403,"Forbidden"); } if (!t_relay()) { send_reply(500,"Internal Error"); } exit; } branch_route[per_branch_ops] { xlog("new branch at $ru\n"); } onreply_route[handle_nat] { xlog("incoming reply\n"); } failure_route[missed_call] { if (t_was_cancelled()) { exit; } # uncomment the following lines if you want to block client # redirect based on 3xx replies. ##if (t_check_status("3[0-9][0-9]")) { ##t_reply(404,"Not found"); ## exit; ##} } BR, Pavel -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob at digilink.net Wed Aug 31 01:31:08 2022 From: bob at digilink.net (Bob Atkins) Date: Tue, 30 Aug 2022 18:31:08 -0700 Subject: [OpenSIPS-Users] Cannot get registration to work with v3.2.8?? Message-ID: Hi. Have been a long time OpenSER user in a production environment. I managed to convert to OpenSIPS v3.2.8 on a CentOS 7 system and is working based on IP authentication however, I just cannot get sip registrations to work that used to work fine with OpenSER. I'm using a SPA112 running 1.4.1(SR5) as a test device. This device registers just fine with Asterisk and OpenSER v1.1 with exactly the same credentials but no matter what I have tried it just won't register with OpenSIPS v3.2.8. I am using auth_db and mysql. I have verified that all sql data is correct. I have been banging my head against the screen for hours to no avail. In reviewing the debug and log output I can clearly see that something is wrong because the user name and domain are both ? www_authorize returns [-4] which means (no credentials) - credentials were not found in request. There is no reason why the credentials should not be there - they have certainly not been consumed before this point. This same device registers just fine with /_*exactly *_/the same credentials to both OpenSER v1.1 and asterisk servers. Would be grateful if anyone can shed some light on this because it seems to me that something inside auth or auth_db is broken and not extracting the registration credentials from the REGISTER message. This code worked just fine in OpenSER v1.1 if (method=="REGISTER") {    #xlog("L_INFO","[$rm][$ft][$tt] Processing registration");    if (!www_authorize("digilink.net", "subscriber")) {    #xlog("L_INFO","[$rm][$ft][$tt] Challenging peer");     www_challenge("digilink.net", "0");     exit; }; xlog("L_INFO","[$rm][$ft][$tt] Registered $fu from $si"); save("location"); exit; }; This is the code in the OpenSIPS 3.2.8 config that is failing: Here are the module loads and various defines: loadmodule "options.so" loadmodule "textops.so" #### SIGNALING module loadmodule "signaling.so" #### StateLess module loadmodule "sl.so" #### Transaction Module loadmodule "tm.so" modparam("tm", "enable_stats", 1) modparam("tm", "fr_timeout", 9) modparam("tm", "fr_inv_timeout", 120) modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "onreply_avp_mode", 1) #### Record Route Module loadmodule "rr.so" /* do not append from tag to the RR */ modparam("rr", "append_fromtag", 1) loadmodule "uac.so" #modparam("uac","restore_mode","auto") modparam("uac","rr_from_store_param","dns_uac_param") modparam("uac","restore_mode","none") #### MAX ForWarD module loadmodule "maxfwd.so" #### SIP MSG OPerationS module loadmodule "sipmsgops.so" #### FIFO Management Interface loadmodule "mi_fifo.so" modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo") modparam("mi_fifo", "fifo_mode", 0666) #### USeR LOCation module loadmodule "usrloc.so" modparam("usrloc", "nat_bflag", "NAT") modparam("usrloc", "working_mode_preset", "single-instance-sql-write-back") modparam("usrloc", "db_url", "mysql://opensips:??????@localhost/opensips") loadmodule "nathelper.so" modparam("nathelper", "received_avp", "$avp(rcv)") modparam("nathelper", "natping_interval", 30) # Ping interval 30 s modparam("nathelper", "ping_nated_only", 1)    # Ping only clients behind NAT #### MYSQL module loadmodule "db_mysql.so" loadmodule "avpops.so" #### AUTH Db module loadmodule "auth.so" loadmodule "auth_db.so" modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "user_column", "username") modparam("auth_db", "password_column", "password") modparam("auth_db", "use_domain", 0) modparam("auth_db", "db_url", "mysql://opensips:??????@localhost/opensips") modparam("auth_db", "load_credentials", "") #### REGISTRAR module loadmodule "registrar.so" modparam("registrar", "tcp_persistent_flag", "TCP_PERSISTENT") modparam("registrar", "min_expires", 120) modparam("registrar", "max_expires", 3600) modparam("registrar", "default_expires", 3600) modparam("registrar", "max_contacts", 5) modparam("registrar", "received_avp", "$avp(rcv)") #### Pike DOS protection loadmodule "pike.so" modparam("pike", "sampling_time_unit", 3) modparam("pike", "reqs_density_per_unit", 20) #### DIALOG module loadmodule "dialog.so" modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "default_timeout", 21600)  # 6 hours timeout modparam("dialog", "db_mode", 0) modparam("dialog", "profiles_with_value", "trunkCalls") #### ACCounting module loadmodule "acc.so" /* what special events should be accounted ? */ modparam("acc", "report_cancels", 1) modparam("acc", "early_media", 1) /* by default we do not adjust the direct of the sequential requests.    if you enable this parameter, be sure to enable "append_fromtag"    in "rr" module */ modparam("acc", "detect_direction", 0) modparam("acc", "acc_callid_column", "sip_callid") modparam("acc", "acc_sip_code_column", "sip_status") modparam("acc", "acc_method_column", "sip_method") modparam("acc", "acc_to_tag_column", "totag") modparam("acc", "acc_from_tag_column", "fromtag") modparam("acc", "extra_fields", "db:sip_from; sip_to; in_uri; out_uri; username; from_uri; to_uri; domain; du") modparam("acc", "db_url", "mysql://opensips:??????@localhost/opensips") loadmodule "proto_udp.so" ---- [snip] ---- if (is_method("REGISTER")) {     xlog("L_INFO", "REGISTER: [$tu] request");     xlog("L_INFO","[$rm][$ft][$tt] Processing registration");     $var(x)=www_authorize("digilink.net", "subscriber");     xlog("L_INFO", "REGISTER: www_authorize returned [$var(x)] to authenticate with [$rU]$ru credential");     if (!$var(x)) {         xlog("L_INFO","[$rm][$ft][$tt] Challenging peer");         www_challenge("digilink.net", "auth,auth-int", "MD5,MD5-sess,SHA-256,SHA-256-sess");         exit;     } else {         xlog("L_ALERT", "REGISTER: URI [$tu] - FAILED");         xlog("L_ALERT", "REGISTER: URI [$tu] - FAILED! User is not authorized to authenticate with [$rU]$ru credential");         exit;     }     xlog("L_INFO", "REGISTER: URI [$tu] - Succeeded");     xlog("L_INFO","[$rm][$ft][$tt] Registered $fu from $si");     save("location");     exit; } Debug out shows: Aug 30 18:19:05 [17809] DBG:core:parse_msg: SIP Request: Aug 30 18:19:05 [17809] DBG:core:parse_msg:  method: Aug 30 18:19:05 [17809] DBG:core:parse_msg:  uri: Aug 30 18:19:05 [17809] DBG:core:parse_msg:  version: Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=ffffffffffffffff Aug 30 18:19:05 [17809] DBG:core:parse_via_param: found param type 232, = ; state=16 Aug 30 18:19:05 [17809] DBG:core:parse_via: end of header reached, state=5 Aug 30 18:19:05 [17809] DBG:core:parse_headers: via found, flags=ffffffffffffffff Aug 30 18:19:05 [17809] DBG:core:parse_headers: this is the first via Aug 30 18:19:05 [17809] DBG:core:_parse_to: end of header reached, state=10 Aug 30 18:19:05 [17809] DBG:core:_parse_to: display={"PPC Fax"}, ruri={sip:3105738133 at 23.253.166.155} Aug 30 18:19:05 [17809] DBG:core:get_hdr_field: [43]; uri=[sip:3105738133 at 23.253.166.155] Aug 30 18:19:05 [17809] DBG:core:get_hdr_field: to body ["PPC Fax" ] Aug 30 18:19:05 [17809] DBG:core:get_hdr_field: cseq : <86682> Aug 30 18:19:05 [17809] DBG:core:get_hdr_field: content_length=0 Aug 30 18:19:05 [17809] DBG:core:get_hdr_field: found end of header Aug 30 18:19:05 [17809] DBG:core:receive_msg: After parse_msg... Aug 30 18:19:05 [17809] DBG:core:receive_msg: preparing to run routing scripts... Aug 30 18:19:05 [17809] DBG:pike:mark_node: search on branch 205 (top=0x7fde48de8f80) Aug 30 18:19:05 [17809] DBG:pike:mark_node: only first 1 were matched! Aug 30 18:19:05 [17809] DBG:pike:pike_check_req: src IP [205.147.62.19],node=0x7fde48de8f80; hits=[3,1],[0,0] node_flags=2 func_flags=8 Aug 30 18:19:05 [17809] DBG:maxfwd:is_maxfwd_present: value = 70 Aug 30 18:19:05 [17809] DBG:core:parse_to_param: tag=1584d16f8a45809ao1 Aug 30 18:19:05 [17809] DBG:core:parse_to_param: end of header reached, state=11 Aug 30 18:19:05 [17809] DBG:core:_parse_to: end of header reached, state=29 Aug 30 18:19:05 [17809] DBG:core:_parse_to: display={"PPC Fax"}, ruri={sip:3105738133 at 23.253.166.155} Aug 30 18:19:05 [17809] SIP message size: 572 bytesAug 30 18:19:05 [17809] DBG:core:comp_scriptvar: int 27: 572 / 2048 Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=78 Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=200 Aug 30 18:19:05 [17809] DBG:rr:find_first_route: No Route headers found Aug 30 18:19:05 [17809] DBG:rr:loose_route: There is no Route HF Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:comp_scriptvar: ip 20: 205.147.62.19 Aug 30 18:19:05 [17809] Unknown source [205.147.62.19]: [sip:3105738133 at 23.253.166.155] request Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=ffffffffffffffff Aug 30 18:19:05 [17809] DBG:core:parse_params: Parsing params for:[expires=300] Aug 30 18:19:05 [17809] REGISTER: [sip:3105738133 at 23.253.166.155] request from sip:23.253.166.155 at 205.147.62.19 Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=14000 Aug 30 18:19:05 [17809] DBG:core:pv_get_authattr: no [Proxy-]Authorization header Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=14000 Aug 30 18:19:05 [17809] DBG:core:pv_get_authattr: no [Proxy-]Authorization header Aug 30 18:19:05 [17809] [REGISTER][1584d16f8a45809ao1][]@[] - Processing registration Aug 30 18:19:05 [17809] DBG:core:parse_headers: flags=4000 Aug 30 18:19:05 [17809] DBG:auth:pre_auth: credentials with given realm not found Aug 30 18:19:05 [17809] REGISTER: www_authorize returned [-4] to authenticate with []sip:23.253.166.155 credential Aug 30 18:19:05 [17809] REGISTER: URI [sip:3105738133 at 23.253.166.155] - FAILEDAug 30 18:19:05 [17809] REGISTER: URI [sip:3105738133 at 23.253.166.155] - FAILED! User is not authorized to authenticate with []sip:23.253.166.155 credential Aug 30 18:19:05 [17809] DBG:core:destroy_avp_list: destroying list (nil) Aug 30 18:19:05 [17809] DBG:core:receive_msg: cleaning up ---- Thank you, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From sparklezou at 126.com Fri Aug 26 05:31:30 2022 From: sparklezou at 126.com (SparkleZou) Date: Fri, 26 Aug 2022 13:31:30 +0800 (CST) Subject: [OpenSIPS-Users] How to set auth_db module & db_mysql module work on opensips 3.3 Message-ID: <31b082cc.1f07.182d8a24a5a.Coremail.sparklezou@126.com> Hi All, I'm just start to use OpenSips. Already checked the manual. Step by Step, here I need help. Thanks! ^_^ 1. Already install Opensips 3.3 successfully refer to OpenSIPS 3.1/3.2 Installation Instructions | VoIP School 2. apt install mariadb-server opensips-cli -x database create opensips root at opensips:/etc/opensips# mysql opensips -e "show tables" +--------------------+ | Tables_in_opensips | +--------------------+ | acc | | address | | clusterer | | dbaliases | | dialog | | dialplan | | dispatcher | | domain | | dr_carriers | | dr_gateways | | dr_groups | | dr_partitions | | dr_rules | | grp | | load_balancer | | location | | missed_calls | | re_grp | | rtpengine | | rtpproxy_sockets | | silo | | speed_dial | | subscriber | | tls_mgm | | uri | | usr_preferences | | version | +--------------------+ MariaDB [opensips]> select * FROM subscriber; +----+----------+--------------+----------+---------------+----------------------------------+------------------------------------------------------------------+------------------------------------------------------------------+------+ | id | username | domain | password | email_address | ha1 | ha1_sha256 | ha1_sha512t256 | rpid | +----+----------+--------------+----------+---------------+----------------------------------+------------------------------------------------------------------+------------------------------------------------------------------+------+ | 1 | 1000 | 192.168.3.53 | | | 1c77bd7afa5414714be613363977341f | a821eb87519b53a8e505184a8798b9300dd1788c32ce59026c6f047d5f0eb717 | 1947492ee9de11818d8a54cc5969bd87e5622f412e1b3e1a117ce8c44b936b5d | NULL | | 2 | 1001 | 192.168.3.53 | | | c3d0ccc517e752190644392e7f0c5d93 | b4efb98003f1e5f75ad6ca5ce320a367a430415b9e304ef384e19b969e14ea44 | 49a9a44fbb296fed9c7fe9b4e86ef113642d2e911fe34e93742cc249de261d5a | NULL | +----+----------+--------------+----------+---------------+----------------------------------+------------------------------------------------------------------+------------------------------------------------------------------+------+ 2 rows in set (0.000 sec) accounts 1000 & 1001 are already created in db. run /usr/sbin/osipsconfig select ENABLE_TCP & USE_AUTH, generate the CFG file. ____________________________________________ | | | [*] ENABLE_TCP | | [ ] ENABLE_TLS | | [ ] USE_ALIASES | | [*] USE_AUTH | | [ ] USE_DBACC | | [ ] USE_DBUSRLOC | | [ ] USE_DIALOG | | [ ] USE_MULTIDOMAIN | | [ ] USE_NAT | | [ ] USE_PRESENCE | | [ ] USE_DIALPLAN | | [ ] VM_DIVERSION | | [ ] HAVE_INBOUND_PSTN | | [ ] HAVE_OUTBOUND_PSTN | | [ ] USE_DR_PSTN | | [ ] USE_HTTP_MANAGEMENT_INTERFACE | |____________________________________________| Then start the opensips. But REGISTER get 401 fail message. REGISTER sip:192.168.3.53 SIP/2.0 Via: SIP/2.0/UDP 10.120.100.250:39720;branch=z9hG4bK-d87543-ec515058dd0d9227-1--d87543-;rport Max-Forwards: 70 Contact: To: "1000" From: "1000";tag=a16e1263 Call-ID: ZTY2NDZlYjc1ZTE3MGE4ZjI5YzhhZjA4M2IzYTIyZTc. CSeq: 1 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1011s stamp 41150 Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.120.100.250:39720;received=192.168.3.250;branch=z9hG4bK-d87543-ec515058dd0d9227-1--d87543-;rport=39720 To: "1000";tag=a42c.30207dd1fda47907656684ceecd519a5 From: "1000";tag=a16e1263 Call-ID: ZTY2NDZlYjc1ZTE3MGE4ZjI5YzhhZjA4M2IzYTIyZTc. CSeq: 1 REGISTER WWW-Authenticate: Digest realm="192.168.3.53", nonce="Tx723UFoxz9VG6/4szaVxWNyEKleCmoNQbbunbDRcdAA", qop="auth" Server: OpenSIPS (3.3.1 (x86_64/linux)) Content-Length: 0 The opensips.cfg is attached. Please help check where is the problem. Thanks! BR, SparkleZou -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opensips.cfg Type: application/octet-stream Size: 6726 bytes Desc: not available URL: