From venefax at gmail.com  Mon Mar  3 15:45:32 2025
From: venefax at gmail.com (Saint Michael)
Date: Mon, 3 Mar 2025 10:45:32 -0500
Subject: [OpenSIPS-Users] Failed compilation
Message-ID: <CAC9cSODWdLcAmj1j0vsGzWf9MVy2y929VOz2XD-Duq-LaCNQ0A@mail.gmail.com>

make[1]: Entering directory '/usr/src/opensips-3.4/menuconfig'
gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops
-falign-loops -ftree-vectorize -fno-common -mtune=nocona
-Wold-style-definition -Wmissing-field-initializers -Wredundant-decls -g
-Wall
-DMENUCONFIG_CFG_PATH=\"/usr/local//share/opensips//menuconfig_templates/\"
-DMENUCONFIG_GEN_PATH=\"/usr/local//etc/opensips/\"
-DMENUCONFIG_HAVE_SOURCES=0    -c -o cfg.o cfg.c
In file included from cfg.c:28:
main.h:39:8: error: unknown type name 'WINDOW'
   39 | extern WINDOW *menu_window;
      |        ^~~~~~
make[1]: *** [<builtin>: cfg.o] Error 1
make[1]: Leaving directory '/usr/src/opensips-3.4/menuconfig'
make: *** [Makefile:487: opensipsmc] Error 2
General
what steps should I take to understand this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250303/0b150a1b/attachment.html>

From liviu at opensips.org  Thu Mar  6 14:17:18 2025
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 6 Mar 2025 16:17:18 +0200
Subject: [OpenSIPS-Users] Failed compilation
In-Reply-To: <CAC9cSODWdLcAmj1j0vsGzWf9MVy2y929VOz2XD-Duq-LaCNQ0A@mail.gmail.com>
References: <CAC9cSODWdLcAmj1j0vsGzWf9MVy2y929VOz2XD-Duq-LaCNQ0A@mail.gmail.com>
Message-ID: <44ad8e28-7687-ed01-f24e-fd0f0d8dc258@opensips.org>

Make sure to install *libncurses5-dev *DEB package or equivalent for 
your OS, then try again.

On 03.03.2025 17:45, Saint Michael wrote:
> make[1]: Entering directory '/usr/src/opensips-3.4/menuconfig'
> gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops 
> -falign-loops -ftree-vectorize -fno-common -mtune=nocona 
> -Wold-style-definition -Wmissing-field-initializers -Wredundant-decls 
> -g -Wall 
> -DMENUCONFIG_CFG_PATH=\"/usr/local//share/opensips//menuconfig_templates/\" 
> -DMENUCONFIG_GEN_PATH=\"/usr/local//etc/opensips/\" 
> -DMENUCONFIG_HAVE_SOURCES=0 Â  Â -c -o cfg.o cfg.c
> In file included from cfg.c:28:
> main.h:39:8: error: unknown type name 'WINDOW'
> Â  Â 39 | extern WINDOW *menu_window;
> Â  Â  Â  | Â  Â  Â  Â ^~~~~~
> make[1]: *** [<builtin>: cfg.o] Error 1
> make[1]: Leaving directory '/usr/src/opensips-3.4/menuconfig'
> make: *** [Makefile:487: opensipsmc] Error 2
> General
> what steps should I take to understand this?
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-- 
Liviu Chircu
www.opensips-solutions.com  |www.siphub.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250306/f7a2d198/attachment.html>

From venefax at gmail.com  Thu Mar  6 15:24:46 2025
From: venefax at gmail.com (Saint Michael)
Date: Thu, 6 Mar 2025 10:24:46 -0500
Subject: [OpenSIPS-Users] Failed compilation
In-Reply-To: <44ad8e28-7687-ed01-f24e-fd0f0d8dc258@opensips.org>
References: <CAC9cSODWdLcAmj1j0vsGzWf9MVy2y929VOz2XD-Duq-LaCNQ0A@mail.gmail.com>
 <44ad8e28-7687-ed01-f24e-fd0f0d8dc258@opensips.org>
Message-ID: <CAC9cSOASG7C4Gv0HgAE+JHBG2bZ9O3pbEm0WrWzxPRE9EPTa2Q@mail.gmail.com>

I did, and after a lot of research, I had to do this
cd /usr/src/opensips-3.4/
git reset --hard HEAD
git pull
cd menuconfig/
rm -f curses.h
ln -sf /usr/src/merged_curses.h curses.h
cd ..

The file, merged_curses.h, attached, is a combination of the  system
curses.h and the opensips curses.h.
The compiler cannot find all the headers it needs on the native opensips
curses.h

My OS is
cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.2 LTS (Noble Numbat)"
VERSION_CODENAME=noble

Do you have any idea what can be possibly happening?

On Thu, Mar 6, 2025 at 9:19â€¯AM Liviu Chircu <liviu at opensips.org> wrote:

> Make sure to install *libncurses5-dev *DEB package or equivalent for your
> OS, then try again.
> On 03.03.2025 17:45, Saint Michael wrote:
>
> make[1]: Entering directory '/usr/src/opensips-3.4/menuconfig'
> gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops
> -falign-loops -ftree-vectorize -fno-common -mtune=nocona
> -Wold-style-definition -Wmissing-field-initializers -Wredundant-decls -g
> -Wall
> -DMENUCONFIG_CFG_PATH=\"/usr/local//share/opensips//menuconfig_templates/\"
> -DMENUCONFIG_GEN_PATH=\"/usr/local//etc/opensips/\"
> -DMENUCONFIG_HAVE_SOURCES=0    -c -o cfg.o cfg.c
> In file included from cfg.c:28:
> main.h:39:8: error: unknown type name 'WINDOW'
>    39 | extern WINDOW *menu_window;
>       |        ^~~~~~
> make[1]: *** [<builtin>: cfg.o] Error 1
> make[1]: Leaving directory '/usr/src/opensips-3.4/menuconfig'
> make: *** [Makefile:487: opensipsmc] Error 2
> General
> what steps should I take to understand this?
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> --
> Liviu Chircuwww.opensips-solutions.com | www.siphub.com
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250306/6df746d7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: merged_curses.h
Type: application/octet-stream
Size: 948 bytes
Desc: not available
URL: <http://lists.opensips.org/pipermail/users/attachments/20250306/6df746d7/attachment.obj>

From tlopes at unitedworldtelecom.com  Fri Mar  7 21:10:29 2025
From: tlopes at unitedworldtelecom.com (Thiago Lopes)
Date: Fri, 7 Mar 2025 18:10:29 -0300
Subject: [OpenSIPS-Users] MS Teams and SBC integration
Message-ID: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>

Hi everyone,

I'm trying to integrate Ms Teams and Opensips and I'm having some problems.

I tried to use self signed and Letsencrypt certificates, with no success. I
always receive a ''no TLS client domain found'.

 /usr/sbin/opensips[505412]: ERROR:proto_tls:proto_tls_conn_init: no TLS
client domain found
 /usr/sbin/opensips[505412]: ERROR:core:tcp_conn_create: failed to do proto
3 specific init for conn 0x7f7220f343b0
 /usr/sbin/opensips[505412]: ERROR:core:tcp_async_connect: tcp_conn_create
failed

Here my opensips.cfg:

loadmodule "tls_mgm.so"

/*#first the  server domain */
modparam("tls_mgm", "server_domain", "default")
modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/fullchain.pem")
modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/privkey.pem")
modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/inter.pem")
modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com")
modparam("tls_mgm", "verify_cert", "[default]0")
#modparam("tls_mgm", "require_cert", "[default]1")
#modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[default]SSLv23")

 # #and the client domain

modparam("tls_mgm", "client_domain", "client")
modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/fullchain.pem")
modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/privkey.pem")
modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/inter.pem")
#modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/")
modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")

modparam("tls_mgm", "verify_cert", "[client]0")
 # modparam("tls_mgm", "require_cert", "[client]1")
 # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[client]SSLv23")

I also changed the certificates, using self signed in "server domain" only
or "client domain" only. Same result.

Using the openssl the verify the certificates, I receive a OK in console:

fullchain.pem: OK

The inter.pem is the file with the root and intermediate Letsencrypt
certificates.

On the Ms Teams side, I checked the FQDN used, checked the firewall ports
etc.

I followed this tutorial:
https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/  , so I'm
using the Dynamic Routing module to send the OPTIONS packet. The opensips
start the communication using TLS, I see the packets using TLS in 5061
port, but when Opensips will answer, this message appears on the console
and the connection is closed.

/usr/sbin/opensips[505398]: ERROR:tm:t_uac: attempt to send to 'sip:
sip.pstnhub.microsoft.com' failed
/usr/sbin/opensips[505398]: ERROR:proto_tls:proto_tls_conn_init: no TLS
client domain found
/usr/sbin/opensips[505398]: ERROR:core:tcp_conn_create: failed to do proto
3 specific init for conn 0x7f7220f4df40

What I'm not seeing? Did someone pass through this problem?
Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250307/0f16ae53/attachment.html>

From bogdan at opensips.org  Mon Mar 10 07:33:21 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 09:33:21 +0200
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
Message-ID: <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>

Hi,

For the incoming TLS connections, the right TLS server domain is 
selected based either on the IP address (of OpenSIPS's listener), either 
on the SIP domain (if SNI is used).

So, maybe SNI is not used in your case, so you should define a 
match_ip_address:
https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_match_ip_address

Regards,

Bogdan-Andrei Iancu

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

On 07.03.2025 23:10, Thiago Lopes via Users wrote:
> Hi everyone,
>
> I'm trying to integrate Ms Teams and Opensips and I'm having some 
> problems.
>
> I tried to use self signedÂ and Letsencrypt certificates, withÂ no 
> success. I always receive a ''no TLS client domain found'.
>
> Â /usr/sbin/opensips[505412]: ERROR:proto_tls:proto_tls_conn_init: no 
> TLS client domain found
> Â /usr/sbin/opensips[505412]: ERROR:core:tcp_conn_create: failed to do 
> proto 3 specific init for conn 0x7f7220f343b0
> Â /usr/sbin/opensips[505412]: ERROR:core:tcp_async_connect: 
> tcp_conn_create failed
>
> Here my opensips.cfg:
>
> loadmodule "tls_mgm.so"
>
> /*#first the Â server domain */
> modparam("tls_mgm", "server_domain", "default")
> modparam("tls_mgm", "certificate", 
> "[default]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem 
> <http://sbc.mydomain.com/fullchain.pem>")
> modparam("tls_mgm", "private_key", 
> "[default]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem 
> <http://sbc.mydomain.com/privkey.pem>")
> modparam("tls_mgm", "ca_list", 
> "[default]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem 
> <http://sbc.mydomain.com/inter.pem>")
> modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com 
> <http://sbc.mydomain.com>")
> modparam("tls_mgm", "verify_cert", "[default]0")
> #modparam("tls_mgm", "require_cert", "[default]1")
> #modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[default]SSLv23")
>
>
> Â # #and the client domain
> modparam("tls_mgm", "client_domain", "client")
> modparam("tls_mgm", "certificate", 
> "[client]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem 
> <http://sbc.mydomain.com/fullchain.pem>")
> modparam("tls_mgm", "private_key", 
> "[client]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem 
> <http://sbc.mydomain.com/privkey.pem>")
> modparam("tls_mgm", "ca_list", 
> "[client]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem 
> <http://sbc.mydomain.com/inter.pem>")
> #modparam("tls_mgm", "ca_dir", 
> "[client]/etc/letsencrypt/live/sbc.mydomain.com/ 
> <http://sbc.mydomain.com/>")
> modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com 
> <http://sbc.mydomain.com>")
>
> modparam("tls_mgm", "verify_cert", "[client]0")
> Â # modparam("tls_mgm", "require_cert", "[client]1")
> Â # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[client]SSLv23")
>
> I also changed the certificates, using self signed in "server domain" 
> only or "client domain" only. Same result.
>
> Using the openssl the verify the certificates, I receive a OK in console:
>
> fullchain.pem: OK
>
> The inter.pem is the file with the root and intermediateÂ Letsencrypt 
> certificates.
>
> On the Ms Teams side, I checked the FQDN used, checked the firewall 
> ports etc.
>
> I followed this tutorial: 
> https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ , so 
> I'm using the Dynamic Routing module to send the OPTIONS packet. The 
> opensips start the communication using TLS, I see the packets using 
> TLS in 5061 port, but when Opensips will answer, this message appears 
> on the console and the connection is closed.
>
> /usr/sbin/opensips[505398]: ERROR:tm:t_uac: attempt to send to 
> 'sip:sip.pstnhub.microsoft.com <http://sip.pstnhub.microsoft.com>' failed
> /usr/sbin/opensips[505398]: ERROR:proto_tls:proto_tls_conn_init: no 
> TLS client domain found
> /usr/sbin/opensips[505398]: ERROR:core:tcp_conn_create: failed to do 
> proto 3 specific init for conn 0x7f7220f4df40
>
> What I'm not seeing? Did someone pass throughÂ this problem?
> Best regards
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/7aa9a59e/attachment.html>

From andrey55555 at gmail.com  Mon Mar 10 07:44:40 2025
From: andrey55555 at gmail.com (Andrew)
Date: Mon, 10 Mar 2025 10:44:40 +0300
Subject: [OpenSIPS-Users] New releases are not published to the repositories
	(both APT and YUM)
Message-ID: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>

Hi
Both release and nightly builds have not been published since the
beginning of February.
Could anyone please fix this?

Best regards, Andrew.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/4b76f70c/attachment.html>

From bogdan at opensips.org  Mon Mar 10 07:55:53 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 09:55:53 +0200
Subject: [OpenSIPS-Users] New releases are not published to the
 repositories (both APT and YUM)
In-Reply-To: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>
References: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>
Message-ID: <2b8feda6-7c63-40e7-963a-cc12caa54267@opensips.org>

Hi Andrew,

Thanks for the heads-up. Indeed, I see here:
 Â Â Â  https://apt.opensips.org/pool/bionic/3.5-releases/o/opensips/
we are still with the 3.5.3, the 3.5.4 is missing.

We will check what is going on.

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 09:44, Andrew wrote:
> Hi
> Both release and nightly builds have not been published since the 
> beginningÂ of February.
> Could anyone please fix this?
>
> Best regards, Andrew.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

From spanda at 3clogic.com  Mon Mar 10 09:59:59 2025
From: spanda at 3clogic.com (Sasmita Panda)
Date: Mon, 10 Mar 2025 15:29:59 +0530
Subject: [OpenSIPS-Users] I need to understand how opensips behave when its
 running on eks cluster .
Message-ID: <CALf-Q46sbsxds7axbNd1WPHTd-+r8648oYGZnc+VqUADSCEkww@mail.gmail.com>

Hi All ,

I have opensips 3.2 deployed on a node in eks cluster . Opensips is running
in a docker container with HostNetwork= True . I have configured the socket
on the 5060/UDP port . As for the expectation , the incoming and outgoing
traffic must be communicated with 5060 port.

I can see in outgoing requests , when the request reaches the far end , the
source port which get visible to them is a random port not 5060 . What are
the possible reasons for this ?

Is the deployment with HostNetwor : True wont work with Opensips ? Will I
need to try some other way around ? Please do suggest  . Thanks in advance
.

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

From trevor at webon.co.za  Mon Mar 10 14:02:12 2025
From: trevor at webon.co.za (trevor at webon.co.za)
Date: Mon, 10 Mar 2025 16:02:12 +0200
Subject: [OpenSIPS-Users] opensips-cli rpm repo issues
Message-ID: <2955508e7be1454c88f882a862aa4fe0b0dfc975.camel@webon.co.za>

Hi All, there seems to be an issue with opensips-cli repo as per below
404 not found even after dnf clean all

dnf download opensips-cli.noarch
OpenSIPS CLI tool - Open Source SIP proxy/server for el9 - x86_64 5.4
kB/s | 3.0 kB 00:00 
[MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
code: 404 for
https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
(IP:) 
[MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
code: 404 for
https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
(IP: ) 
[MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
code: 404 for
https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
(IP: ) 
[MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
code: 404 for
https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
(IP: ) 
[FAILED] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: No more
mirrors to try - All mirrors were already tried without success 

Regards
Trevor Steyn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/75fc7530/attachment.html>

From james at fivecats.org  Mon Mar 10 15:08:03 2025
From: james at fivecats.org (James Sharp)
Date: Mon, 10 Mar 2025 08:08:03 -0700
Subject: [OpenSIPS-Users] Memory leak bug or expected behavior with
	acc_extra?
Message-ID: <92fca2aa-3e48-4b12-a202-f8fbbabb7caa@fivecats.org>

I had been having some big issues with Opensips chewing its way through 
shared memory to the point of it running out and requiring a restart.

In my config script, I used to have some do_accounting() to write CDRs 
to a mysql table along with some $acc_extra variables for additional CDR 
data.  I had commented out the do_accounting() lines but didn't bother 
with the $acc_extras.   Turns out that was my smoking gun.  After I 
commented out the $acc_extra lines, my shared memory graphs went 
straight flat instead of slowly headed down.

Is this a memory leak bug or an expected behavior with the ACC system? 
I'm running Opensips 3.3 in a docker container.

From alain.bieuzent at free.fr  Mon Mar 10 15:31:25 2025
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Mon, 10 Mar 2025 16:31:25 +0100
Subject: [OpenSIPS-Users] trigger an action if the timer reaches the end
	fr_timeout
Message-ID: <0C041C3E-5191-45ED-AB53-DE4ED8784EAB@free.fr>

Hi all,

How I can run a rtpengine_delete() after expiration of the fr_timeout timer.

Thanks

Alain

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

From bogdan at opensips.org  Mon Mar 10 15:37:45 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 17:37:45 +0200
Subject: [OpenSIPS-Users] Request for Public Discussion - improving the
	contribution process
Message-ID: <b2a15805-f491-4d21-afc8-47d4e4f5b637@opensips.org>

Contributing is an important aspect of an Open Source project. Both for 
the project itself and for its community.

So, we want your feedback and to learn from you how do you see the 
current process of handling the contributions and if there is anything 
we can do to improve it. Keep in mind that the overall "contribution" 
process is a complex one, it is more than a patch only. By 
"contribution" we do cover eventual documentation/help in code 
understanding, support for brainstorming codes, generating Pull 
Requests, the reviewing process.

Any one is more then welcome to provide feedback on this topic - we 
scheduled a conference discussion (Google Meet) for 25th of March, 14:00 
GMT. In order to join, you have to register in advance [1]. This 
registration is just a formality (yeah, no worries, everyone is welcome) 
for managing the access to the conference bridge.

So, please register, we are looking forward to hear your feedback on 
this matter :)

[1] https://bit.ly/contribution_conf_registration

Best regards,

-- 
Bogdan-Andrei Iancu

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

From ihssanezammou at gmail.com  Mon Mar 10 16:09:25 2025
From: ihssanezammou at gmail.com (Ihssane Zammou)
Date: Mon, 10 Mar 2025 17:09:25 +0100
Subject: [OpenSIPS-Users] trigger an action if the timer reaches the end
	fr_timeout
In-Reply-To: <0C041C3E-5191-45ED-AB53-DE4ED8784EAB@free.fr>
References: <0C041C3E-5191-45ED-AB53-DE4ED8784EAB@free.fr>
Message-ID: <CAHVHhGDUej+aJxjZT6ay=qRhCWqoPZhko6KRG6QKiMYcjshm9A@mail.gmail.com>

Hello ,

A 408 timeout will trigger the failure_route.
You can add it there

Best regards!
z.ihssane

Le lun. 10 mars 2025, 16:33, Alain Bieuzent <alain.bieuzent at free.fr> a
Ã©crit :

> Hi all,
>
>
>
> How I can run a rtpengine_delete() after expiration of the fr_timeout
> timer.
>
>
>
> Thanks
>
>
>
> Alain
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/014fff58/attachment-0001.html>

From simon at softnet.si  Mon Mar 10 16:11:19 2025
From: simon at softnet.si (Simon Gajski)
Date: Mon, 10 Mar 2025 17:11:19 +0100
Subject: [OpenSIPS-Users] Call pickup issue in opensips 3.5
Message-ID: <4a4e5037-153c-410f-ab10-9502d8dadcc3@softnet.si>

Hello

I have an issue with call pickup after migration from opensips 3.2 to 3.5

I have been trying to use "1.6.2.Â  Call pickup" script from 
https://opensips.org/docs/modules/3.5.x/event_routing.html

and receiving this error that dont know how to deal with:
ERROR:core:fixup_named_flags: Unknown flag:
ERROR:core:reg_fixup_lookup_flags: Failed to parse flags
ERROR:core:fix_cmd: Fixup failed for param [2]
ERROR:core:fix_actions: Failed to fix command <lookup>
ERROR:core:fix_actions: fixing failed (code=-1) at 
/etc/opensips/opensips.cfg:1813
CRITICAL:core:fix_expr: fix_actions error
ERROR:core:main: failed to initialize routing lists!

opensips.cfg:1813 is pointing to line "if(lookup("location","", 
$avp(picker))) {" of bellow function

route[handle_pickup]{
 Â  Â  xlog("call picked by avp(picker): $avp(picker), fetching its 
contacts\n");
if(lookup("location","", $avp(picker))) {
# take the contacts retured by lookup() (for Charlie)
# and inject them into the original call, but also cancel
# any existing ongoing branch (ringing to Bob)
 Â  Â  Â  Â  t_inject_branches("msg","cancel");
 Â  Â  }
}

Thank you for any tips on how to fix this

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

From bogdan at opensips.org  Mon Mar 10 16:13:28 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 18:13:28 +0200
Subject: [OpenSIPS-Users] New releases are not published to the
 repositories (both APT and YUM)
In-Reply-To: <2b8feda6-7c63-40e7-963a-cc12caa54267@opensips.org>
References: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>
 <2b8feda6-7c63-40e7-963a-cc12caa54267@opensips.org>
Message-ID: <c2d108c3-e772-4bac-a7b1-3216f0f5787f@opensips.org>

Quick update - the issue was identified and fixed, the missing builds 
are work in progress (it takes a while the whole compiling). Tomorrow 
they should be available.

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 09:55, Bogdan-Andrei Iancu wrote:
> Hi Andrew,
>
> Thanks for the heads-up. Indeed, I see here:
> Â Â Â  https://apt.opensips.org/pool/bionic/3.5-releases/o/opensips/
> we are still with the 3.5.3, the 3.5.4 is missing.
>
> We will check what is going on.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
> Â  https://www.opensips-solutions.com
> Â  https://www.siphub.com
>
> On 10.03.2025 09:44, Andrew wrote:
>> Hi
>> Both release and nightly builds have not been published since the 
>> beginningÂ of February.
>> Could anyone please fix this?
>>
>> Best regards, Andrew.
>>
>> _______________________________________________
>> 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 bogdan at opensips.org  Mon Mar 10 16:15:29 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 18:15:29 +0200
Subject: [OpenSIPS-Users] I need to understand how opensips behave when
 its running on eks cluster .
In-Reply-To: <CALf-Q46sbsxds7axbNd1WPHTd-+r8648oYGZnc+VqUADSCEkww@mail.gmail.com>
References: <CALf-Q46sbsxds7axbNd1WPHTd-+r8648oYGZnc+VqUADSCEkww@mail.gmail.com>
Message-ID: <06b8fc51-a5d7-42c7-b43e-bbd29051761b@opensips.org>

Hi Sasmita,

Just as hint, to know where to dig further. 100% this has nothing to do 
with OpenSIPS, but with the network setup in your cloud.

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 11:59, Sasmita Panda wrote:
> Hi All ,
>
> I have opensips 3.2 deployed on a node in eks cluster . Opensips is 
> running in a docker container with HostNetwork= True . I have 
> configured the socket on the 5060/UDP port . As for the expectation , 
> the incoming and outgoing traffic must be communicated with 5060 port.
>
> I can see in outgoing requests , when the request reaches the far end 
> , the source port which get visible to them is a random port not 5060 
> . What areÂ  the possible reasons for this ?
>
> Is the deployment with HostNetworÂ : True wont work with Opensips ? 
> Will I need to try some other way around ? Please do suggestÂ  . Thanks 
> in advance .
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Senior Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/ab314fc6/attachment.html>

From bogdan at opensips.org  Mon Mar 10 16:17:06 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 18:17:06 +0200
Subject: [OpenSIPS-Users] opensips-cli rpm repo issues
In-Reply-To: <2955508e7be1454c88f882a862aa4fe0b0dfc975.camel@webon.co.za>
References: <2955508e7be1454c88f882a862aa4fe0b0dfc975.camel@webon.co.za>
Message-ID: <0eaf1d67-0889-4429-8756-7187c80e9c44@opensips.org>

Hi Trevor,

There was a problem (earlier reported here on the list) and indeed, some 
nightly builds failed to generate. The issue was addressed, the builds 
should be available by tomorrow.

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 16:02, trevor at webon.co.za wrote:
> Hi All, there seems to be an issue with opensips-cli repo as per below 
> 404 not found even after dnf clean all
>
> dnf download opensips-cli.noarch
> OpenSIPS CLI tool - Open Source SIP proxy/server for el9 - x86_64 5.4 
> kB/s | 3.0 kB 00:00
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status 
> code: 404 for 
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm 
> (IP:)
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status 
> code: 404 for 
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm 
> (IP: )
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status 
> code: 404 for 
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm 
> (IP: )
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status 
> code: 404 for 
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm 
> (IP: )
> [FAILED] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: No more 
> mirrors to try - All mirrors were already tried without success
>
>
> Regards
> Trevor Steyn
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/a5118c79/attachment-0001.html>

From bogdan at opensips.org  Mon Mar 10 16:17:57 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 18:17:57 +0200
Subject: [OpenSIPS-Users] Memory leak bug or expected behavior with
 acc_extra?
In-Reply-To: <92fca2aa-3e48-4b12-a202-f8fbbabb7caa@fivecats.org>
References: <92fca2aa-3e48-4b12-a202-f8fbbabb7caa@fivecats.org>
Message-ID: <fa8ab742-b69a-4f83-892b-14ec2ab7f307@opensips.org>

Hi James,

Take a look at this
 Â Â Â  https://opensips.org/Documentation/TroubleShooting-OutOfMem

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 17:08, James Sharp wrote:
> I had been having some big issues with Opensips chewing its way 
> through shared memory to the point of it running out and requiring a 
> restart.
>
> In my config script, I used to have some do_accounting() to write CDRs 
> to a mysql table along with some $acc_extra variables for additional 
> CDR data.Â  I had commented out the do_accounting() lines but didn't 
> bother with the $acc_extras.Â Â  Turns out that was my smoking gun.Â  
> After I commented out the $acc_extra lines, my shared memory graphs 
> went straight flat instead of slowly headed down.
>
> Is this a memory leak bug or an expected behavior with the ACC system? 
> I'm running Opensips 3.3 in a docker container.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

From bogdan at opensips.org  Mon Mar 10 16:20:03 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Mon, 10 Mar 2025 18:20:03 +0200
Subject: [OpenSIPS-Users] Call pickup issue in opensips 3.5
In-Reply-To: <4a4e5037-153c-410f-ab10-9502d8dadcc3@softnet.si>
References: <4a4e5037-153c-410f-ab10-9502d8dadcc3@softnet.si>
Message-ID: <ccb1430b-50cc-4eb5-ae74-b292c9ac30bd@opensips.org>

Hi Simon,

Instead of
 Â Â Â  if (lookup("location","", $avp(picker))) {

try
 Â Â Â  if (lookup("location", , $avp(picker))) {

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 18:11, Simon Gajski via Users wrote:
>
> Hello
>
> I have an issue with call pickup after migration from opensips 3.2 to 3.5
>
> I have been trying to use "1.6.2.Â  Call pickup" script from 
> https://opensips.org/docs/modules/3.5.x/event_routing.html
>
> and receiving this error that dont know how to deal with:
> ERROR:core:fixup_named_flags: Unknown flag:
> ERROR:core:reg_fixup_lookup_flags: Failed to parse flags
> ERROR:core:fix_cmd: Fixup failed for param [2]
> ERROR:core:fix_actions: Failed to fix command <lookup>
> ERROR:core:fix_actions: fixing failed (code=-1) at 
> /etc/opensips/opensips.cfg:1813
> CRITICAL:core:fix_expr: fix_actions error
> ERROR:core:main: failed to initialize routing lists!
>
> opensips.cfg:1813 is pointing to line "if(lookup("location","", 
> $avp(picker))) {" of bellow function
>
>
> route[handle_pickup]{
> Â  Â  xlog("call picked by avp(picker): $avp(picker), fetching its 
> contacts\n");
> if(lookup("location","", $avp(picker))) {
> # take the contacts retured by lookup() (for Charlie)
> # and inject them into the original call, but also cancel
> # any existing ongoing branch (ringing to Bob)
> Â  Â  Â  Â  t_inject_branches("msg","cancel");
> Â  Â  }
> }
>
>
> Thank you for any tips on how to fix this
>
> BR
> Simon
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/a3bd1ab9/attachment.html>

From alain.bieuzent at free.fr  Mon Mar 10 16:28:54 2025
From: alain.bieuzent at free.fr (Alain Bieuzent)
Date: Mon, 10 Mar 2025 17:28:54 +0100
Subject: [OpenSIPS-Users] trigger an action if the timer reaches the end
 fr_timeout
In-Reply-To: <CAHVHhGDUej+aJxjZT6ay=qRhCWqoPZhko6KRG6QKiMYcjshm9A@mail.gmail.com>
References: <0C041C3E-5191-45ED-AB53-DE4ED8784EAB@free.fr>
 <CAHVHhGDUej+aJxjZT6ay=qRhCWqoPZhko6KRG6QKiMYcjshm9A@mail.gmail.com>
Message-ID: <06CAEEA7-33DB-4625-A009-FDE838D2A4FA@free.fr>

but of course!

Thanks for pointing it out to me

De : Ihssane Zammou <ihssanezammou at gmail.com>
Date : lundi 10 mars 2025 Ã  17:09
Ã€ : OpenSIPS users mailling list <users at lists.opensips.org>, Alain Bieuzent <alain.bieuzent at free.fr>
Objet : Re: [OpenSIPS-Users] trigger an action if the timer reaches the end fr_timeout

Hello ,

A 408 timeout will trigger the failure_route.

You can add it there

Best regards!
z.ihssane

Le lun. 10 mars 2025, 16:33, Alain Bieuzent <alain.bieuzent at free.fr> a Ã©crit :

Hi all,

How I can run a rtpengine_delete() after expiration of the fr_timeout timer.

Thanks

Alain

_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

From tlopes at unitedworldtelecom.com  Mon Mar 10 16:49:49 2025
From: tlopes at unitedworldtelecom.com (Thiago Lopes)
Date: Mon, 10 Mar 2025 13:49:49 -0300
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
 <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
Message-ID: <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>

Hello,

I tried to change this option, change from self-signed to true certificate,
change the listeners and even change the DRouting module to Dispatcher.

Microsoft's documentation says that a SBC must send a packet to them, so
they will answer back and will send an OPTIONS packet as soon as the TLS
connection was made successfully.

So, when I send the first packet, I will act as a client TLS user. I
thought the 'client domain' part, in module configuration was the problem.
But even changing the 'server' part too, the result was the same.

 /usr/sbin/opensips[676690]: DBG:proto_tls:proto_tls_send: no open tcp
> connection found, opening new one, async = 1
>  /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff: getsockopt: snd
> is initially 16384
>  /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff: using snd
> buffer of 416 kb
>  /usr/sbin/opensips[676690]: DBG:core:init_sock_keepalive: TCP keepalive
> enabled on socket 5
>  /usr/sbin/opensips[676681]: WARNING:core:utimer_ticker: utimer task
> <tm-utimer> already scheduled 100 ms ago (now 35900 ms), delaying execution
>  /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Polling is overdue
>  /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Create connection
> for async connect
>  /usr/sbin/opensips[676690]: DBG:core:print_ip: tcpconn_new: new tcp
> connection to: 52.114.32.169
>  /usr/sbin/opensips[676690]: DBG:core:tcpconn_new: on port 5061, proto 3
>  /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_conn_init: no TLS
> client domain found
>  /usr/sbin/opensips[676690]: ERROR:core:tcp_conn_create: failed to do
> proto 3 specific init for conn 0x7f027cb1d070
> /usr/sbin/opensips[676690]: DBG:core:tcpconn_destroy: delaying
> (0x7f027cb1d070, flags 0018) ref = -1 ...
>  /usr/sbin/opensips[676690]: ERROR:core:tcp_async_connect: tcp_conn_create
> failed
>  /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_send: async TCP
> connect failed

Thank you for your help.

Regards,

On Mon, Mar 10, 2025 at 4:33â€¯AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> For the incoming TLS connections, the right TLS server domain is selected
> based either on the IP address (of OpenSIPS's listener), either on the SIP
> domain (if SNI is used).
>
> So, maybe SNI is not used in your case, so you should define a
> match_ip_address:
>
> https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_match_ip_address
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 07.03.2025 23:10, Thiago Lopes via Users wrote:
>
> Hi everyone,
>
> I'm trying to integrate Ms Teams and Opensips and I'm having some
> problems.
>
> I tried to use self signed and Letsencrypt certificates, with no success.
> I always receive a ''no TLS client domain found'.
>
>  /usr/sbin/opensips[505412]: ERROR:proto_tls:proto_tls_conn_init: no TLS
> client domain found
>  /usr/sbin/opensips[505412]: ERROR:core:tcp_conn_create: failed to do
> proto 3 specific init for conn 0x7f7220f343b0
>  /usr/sbin/opensips[505412]: ERROR:core:tcp_async_connect: tcp_conn_create
> failed
>
> Here my opensips.cfg:
>
> loadmodule "tls_mgm.so"
>
> /*#first the  server domain */
> modparam("tls_mgm", "server_domain", "default")
> modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/fullchain.pem")
> modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/inter.pem")
> modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com")
> modparam("tls_mgm", "verify_cert", "[default]0")
> #modparam("tls_mgm", "require_cert", "[default]1")
> #modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[default]SSLv23")
>
>
>  # #and the client domain
>
> modparam("tls_mgm", "client_domain", "client")
> modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/fullchain.pem")
> modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/inter.pem")
> #modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/")
> modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")
>
> modparam("tls_mgm", "verify_cert", "[client]0")
>  # modparam("tls_mgm", "require_cert", "[client]1")
>  # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[client]SSLv23")
>
> I also changed the certificates, using self signed in "server domain" only
> or "client domain" only. Same result.
>
> Using the openssl the verify the certificates, I receive a OK in console:
>
> fullchain.pem: OK
>
> The inter.pem is the file with the root and intermediate Letsencrypt
> certificates.
>
> On the Ms Teams side, I checked the FQDN used, checked the firewall ports
> etc.
>
> I followed this tutorial:
> https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/  , so I'm
> using the Dynamic Routing module to send the OPTIONS packet. The opensips
> start the communication using TLS, I see the packets using TLS in 5061
> port, but when Opensips will answer, this message appears on the console
> and the connection is closed.
>
> /usr/sbin/opensips[505398]: ERROR:tm:t_uac: attempt to send to 'sip:
> sip.pstnhub.microsoft.com' failed
> /usr/sbin/opensips[505398]: ERROR:proto_tls:proto_tls_conn_init: no TLS
> client domain found
> /usr/sbin/opensips[505398]: ERROR:core:tcp_conn_create: failed to do proto
> 3 specific init for conn 0x7f7220f4df40
>
> What I'm not seeing? Did someone pass through this problem?
> Best regards
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/7f4f2b65/attachment-0001.html>

From brett at nemeroff.com  Mon Mar 10 16:53:17 2025
From: brett at nemeroff.com (Brett Nemeroff)
Date: Mon, 10 Mar 2025 11:53:17 -0500
Subject: [OpenSIPS-Users] I need to understand how opensips behave when
 its running on eks cluster .
In-Reply-To: <06b8fc51-a5d7-42c7-b43e-bbd29051761b@opensips.org>
References: <CALf-Q46sbsxds7axbNd1WPHTd-+r8648oYGZnc+VqUADSCEkww@mail.gmail.com>
 <06b8fc51-a5d7-42c7-b43e-bbd29051761b@opensips.org>
Message-ID: <CAPwC5wzqt=h05jUXxRAA-Css0YguzktSUm_1p=bFPdy0RUX+Qw@mail.gmail.com>

I agree with Bogdan here. This is not an OpenSIPs question. It's either
your docker configuration is not correct or some other component in your
networking stack (potentially/likely even off this server) is doing that.

I frequently use OpenSIPs, with docker, with host networking. There is no
problem doing it.

On Mon, Mar 10, 2025 at 11:16â€¯AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Sasmita,
>
> Just as hint, to know where to dig further. 100% this has nothing to do
> with OpenSIPS, but with the network setup in your cloud.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 10.03.2025 11:59, Sasmita Panda wrote:
>
> Hi All ,
>
> I have opensips 3.2 deployed on a node in eks cluster . Opensips is
> running in a docker container with HostNetwork= True . I have configured
> the socket on the 5060/UDP port . As for the expectation , the incoming and
> outgoing traffic must be communicated with 5060 port.
>
> I can see in outgoing requests , when the request reaches the far end ,
> the source port which get visible to them is a random port not 5060 . What
> are  the possible reasons for this ?
>
> Is the deployment with HostNetwor : True wont work with Opensips ? Will I
> need to try some other way around ? Please do suggest  . Thanks in advance
> .
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/fdb81996/attachment.html>

From simon at softnet.si  Mon Mar 10 17:12:30 2025
From: simon at softnet.si (Simon Gajski)
Date: Mon, 10 Mar 2025 18:12:30 +0100
Subject: [OpenSIPS-Users] Call pickup issue in opensips 3.5
In-Reply-To: <ccb1430b-50cc-4eb5-ae74-b292c9ac30bd@opensips.org>
References: <4a4e5037-153c-410f-ab10-9502d8dadcc3@softnet.si>
 <ccb1430b-50cc-4eb5-ae74-b292c9ac30bd@opensips.org>
Message-ID: <700dc114-10ba-4c58-a537-6269760b7695@softnet.si>

Hi Bogdan,

its working exactly as you suggested.

Thank you!

BR
Simon

Bogdan-Andrei Iancu je 10.03.2025 ob 17:20Â napisal:
> Hi Simon,
>
> Instead of
> Â Â Â  if (lookup("location","", $avp(picker))) {
>
> try
> Â Â Â  if (lookup("location", , $avp(picker))) {
>
> Regards,
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.com
>    https://www.siphub.com
> On 10.03.2025 18:11, Simon Gajski via Users wrote:
>>
>> Hello
>>
>> I have an issue with call pickup after migration from opensips 3.2 to 3.5
>>
>> I have been trying to use "1.6.2.Â  Call pickup" script from 
>> https://opensips.org/docs/modules/3.5.x/event_routing.html
>>
>> and receiving this error that dont know how to deal with:
>> ERROR:core:fixup_named_flags: Unknown flag:
>> ERROR:core:reg_fixup_lookup_flags: Failed to parse flags
>> ERROR:core:fix_cmd: Fixup failed for param [2]
>> ERROR:core:fix_actions: Failed to fix command <lookup>
>> ERROR:core:fix_actions: fixing failed (code=-1) at 
>> /etc/opensips/opensips.cfg:1813
>> CRITICAL:core:fix_expr: fix_actions error
>> ERROR:core:main: failed to initialize routing lists!
>>
>> opensips.cfg:1813 is pointing to line "if(lookup("location","", 
>> $avp(picker))) {" of bellow function
>>
>>
>> route[handle_pickup]{
>> Â  Â  xlog("call picked by avp(picker): $avp(picker), fetching its 
>> contacts\n");
>> if(lookup("location","", $avp(picker))) {
>> # take the contacts retured by lookup() (for Charlie)
>> # and inject them into the original call, but also cancel
>> # any existing ongoing branch (ringing to Bob)
>> Â  Â  Â  Â  t_inject_branches("msg","cancel");
>> Â  Â  }
>> }
>>
>>
>> Thank you for any tips on how to fix this
>>
>> BR
>> Simon
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Lep pozdrav / Best regards!

Simon Gajski

P: +386 1 8100 100 <tel:+38618100100> E: simon at softnet.si A: Borovec 2, 
1236 Trzin, Slovenia, EU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/71302c2b/attachment.html>

From trevor at webon.co.za  Mon Mar 10 18:36:48 2025
From: trevor at webon.co.za (Trevor Steyn)
Date: Mon, 10 Mar 2025 20:36:48 +0200
Subject: [OpenSIPS-Users] opensips-cli rpm repo issues
In-Reply-To: <0eaf1d67-0889-4429-8756-7187c80e9c44@opensips.org>
References: <2955508e7be1454c88f882a862aa4fe0b0dfc975.camel@webon.co.za>
 <0eaf1d67-0889-4429-8756-7187c80e9c44@opensips.org>
Message-ID: <CANYJ1WFFMSX_b8MtmCnsTtwy6Bjneez4_rag2b-9XnNgkcOopA@mail.gmail.com>

Thanks Bogdan.

I Missed the earlier report apologies.

Regards
Trevor Steyn

On Mon, 10 Mar 2025, 18:17 Bogdan-Andrei Iancu, <bogdan at opensips.org> wrote:

> Hi Trevor,
>
> There was a problem (earlier reported here on the list) and indeed, some
> nightly builds failed to generate. The issue was addressed, the builds
> should be available by tomorrow.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 10.03.2025 16:02, trevor at webon.co.za wrote:
>
> Hi All, there seems to be an issue with opensips-cli repo as per below 404
> not found even after dnf clean all
>
> dnf download opensips-cli.noarch
> OpenSIPS CLI tool - Open Source SIP proxy/server for el9 - x86_64 5.4 kB/s
> | 3.0 kB 00:00
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
> code: 404 for
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
> (IP:)
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
> code: 404 for
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
> (IP: )
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
> code: 404 for
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
> (IP: )
> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
> code: 404 for
> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
> (IP: )
> [FAILED] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: No more
> mirrors to try - All mirrors were already tried without success
>
>
> Regards
> Trevor Steyn
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250310/6329d091/attachment-0001.html>

From razvan at opensips.org  Mon Mar 10 18:38:40 2025
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Mon, 10 Mar 2025 20:38:40 +0200
Subject: [OpenSIPS-Users] opensips-cli rpm repo issues
In-Reply-To: <CANYJ1WFFMSX_b8MtmCnsTtwy6Bjneez4_rag2b-9XnNgkcOopA@mail.gmail.com>
References: <2955508e7be1454c88f882a862aa4fe0b0dfc975.camel@webon.co.za>
 <0eaf1d67-0889-4429-8756-7187c80e9c44@opensips.org>
 <CANYJ1WFFMSX_b8MtmCnsTtwy6Bjneez4_rag2b-9XnNgkcOopA@mail.gmail.com>
Message-ID: <9c90a94c-cce4-49f6-bd53-eb4e03b68d3a@opensips.org>

Hi, Trevor!

You can try again now, the repos should be available.

Best regards,

RÄƒzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com

On 3/10/25 8:36 PM, Trevor Steyn wrote:
> Thanks Bogdan.
> 
> I Missed the earlier report apologies.
> 
> Regards
> Trevor Steyn
> 
> 
> On Mon, 10 Mar 2025, 18:17 Bogdan-Andrei Iancu, <bogdan at opensips.org> wrote:
> 
>> Hi Trevor,
>>
>> There was a problem (earlier reported here on the list) and indeed, some
>> nightly builds failed to generate. The issue was addressed, the builds
>> should be available by tomorrow.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>    https://www.opensips-solutions.com
>>    https://www.siphub.com
>>
>> On 10.03.2025 16:02, trevor at webon.co.za wrote:
>>
>> Hi All, there seems to be an issue with opensips-cli repo as per below 404
>> not found even after dnf clean all
>>
>> dnf download opensips-cli.noarch
>> OpenSIPS CLI tool - Open Source SIP proxy/server for el9 - x86_64 5.4 kB/s
>> | 3.0 kB 00:00
>> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
>> code: 404 for
>> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>> (IP:)
>> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
>> code: 404 for
>> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>> (IP: )
>> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
>> code: 404 for
>> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>> (IP: )
>> [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: Status
>> code: 404 for
>> https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>> (IP: )
>> [FAILED] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: No more
>> mirrors to try - All mirrors were already tried without success
>>
>>
>> Regards
>> Trevor Steyn
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>>
>> Thanks Bogdan.
>>
>> I Missed the earlier report apologies.
>>
>> Regards
>> Trevor Steyn
>>
>>
>> On Mon, 10 Mar 2025, 18:17 Bogdan-Andrei Iancu, <bogdan at opensips.org 
>> <mailto:bogdan at opensips.org>> wrote:
>>
>>     __
>>     Hi Trevor,
>>
>>     There was a problem (earlier reported here on the list) and
>>     indeed, some nightly builds failed to generate. The issue was
>>     addressed, the builds should be available by tomorrow.
>>
>>     Regards,
>>
>>     Bogdan-Andrei Iancu
>>
>>     OpenSIPS Founder and Developer
>>        https://www.opensips-solutions.com <https://www.opensips-solutions.com>
>>        https://www.siphub.com <https://www.siphub.com>
>>
>>     On 10.03.2025 16:02, trevor at webon.co.za
>>     <mailto:trevor at webon.co.za> wrote:
>>>     Hi All, there seems to be an issue with opensips-cli repo as per
>>>     below 404 not found even after dnf clean all
>>>
>>>     dnf download opensips-cli.noarch
>>>     OpenSIPS CLI tool - Open Source SIP proxy/server for el9 - x86_64
>>>     5.4 kB/s | 3.0 kB 00:00
>>>     [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm:
>>>     Status code: 404 for https://yum.opensips.org/cli/nightly/st/9/
>>>     noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>>>     <https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-
>>>     cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm> (IP:)
>>>     [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm:
>>>     Status code: 404 for https://yum.opensips.org/cli/nightly/st/9/
>>>     noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>>>     <https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-
>>>     cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm> (IP: )
>>>     [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm:
>>>     Status code: 404 for https://yum.opensips.org/cli/nightly/st/9/
>>>     noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>>>     <https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-
>>>     cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm> (IP: )
>>>     [MIRROR] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm:
>>>     Status code: 404 for https://yum.opensips.org/cli/nightly/st/9/
>>>     noarch/opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm
>>>     <https://yum.opensips.org/cli/nightly/st/9/noarch/opensips-
>>>     cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm> (IP: )
>>>     [FAILED] opensips-cli-0.3.1.20241129.6124cb1-1.el9.noarch.rpm: No
>>>     more mirrors to try - All mirrors were already tried without success
>>>
>>>
>>>     Regards
>>>     Trevor Steyn
>>>
>>>     _______________________________________________
>>>     Users mailing list
>>>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

From spanda at 3clogic.com  Tue Mar 11 05:19:37 2025
From: spanda at 3clogic.com (Sasmita Panda)
Date: Tue, 11 Mar 2025 10:49:37 +0530
Subject: [OpenSIPS-Users] I need to understand how opensips behave when
 its running on eks cluster .
In-Reply-To: <CAPwC5wzqt=h05jUXxRAA-Css0YguzktSUm_1p=bFPdy0RUX+Qw@mail.gmail.com>
References: <CALf-Q46sbsxds7axbNd1WPHTd-+r8648oYGZnc+VqUADSCEkww@mail.gmail.com>
 <06b8fc51-a5d7-42c7-b43e-bbd29051761b@opensips.org>
 <CAPwC5wzqt=h05jUXxRAA-Css0YguzktSUm_1p=bFPdy0RUX+Qw@mail.gmail.com>
Message-ID: <CALf-Q473BQDDkDsBCKEnXv-C2jYG6Tk2uPZ00+SrR7edYd0oqA@mail.gmail.com>

Thank you both ,

Understood . This minimizes my area of debugging .

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

On Mon, Mar 10, 2025 at 10:23â€¯PM Brett Nemeroff <brett at nemeroff.com> wrote:

> I agree with Bogdan here. This is not an OpenSIPs question. It's either
> your docker configuration is not correct or some other component in your
> networking stack (potentially/likely even off this server) is doing that.
>
> I frequently use OpenSIPs, with docker, with host networking. There is no
> problem doing it.
>
> On Mon, Mar 10, 2025 at 11:16â€¯AM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi Sasmita,
>>
>> Just as hint, to know where to dig further. 100% this has nothing to do
>> with OpenSIPS, but with the network setup in your cloud.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 10.03.2025 11:59, Sasmita Panda wrote:
>>
>> Hi All ,
>>
>> I have opensips 3.2 deployed on a node in eks cluster . Opensips is
>> running in a docker container with HostNetwork= True . I have configured
>> the socket on the 5060/UDP port . As for the expectation , the incoming and
>> outgoing traffic must be communicated with 5060 port.
>>
>> I can see in outgoing requests , when the request reaches the far end ,
>> the source port which get visible to them is a random port not 5060 . What
>> are  the possible reasons for this ?
>>
>> Is the deployment with HostNetwor : True wont work with Opensips ? Will I
>> need to try some other way around ? Please do suggest  . Thanks in advance
>> .
>>
>> *Thanks & Regards*
>> *Sasmita Panda*
>> *Senior Network Testing and Software Engineer*
>> *3CLogic , ph:07827611765*
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250311/dd20ab8f/attachment.html>

From razvan at opensips.org  Tue Mar 11 08:37:07 2025
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Tue, 11 Mar 2025 10:37:07 +0200
Subject: [OpenSIPS-Users] New releases are not published to the
 repositories (both APT and YUM)
In-Reply-To: <c2d108c3-e772-4bac-a7b1-3216f0f5787f@opensips.org>
References: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>
 <2b8feda6-7c63-40e7-963a-cc12caa54267@opensips.org>
 <c2d108c3-e772-4bac-a7b1-3216f0f5787f@opensips.org>
Message-ID: <682b6d47-3fac-4d0e-abb2-f7ad7b8912bd@opensips.org>

Hi, All!

Repositories should be fixed now, and all packages available. Please let 
us know if there's anything missing.

Best regards,

RÄƒzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com

On 3/10/25 6:13 PM, Bogdan-Andrei Iancu wrote:
> Quick update - the issue was identified and fixed, the missing builds 
> are work in progress (it takes a while the whole compiling). Tomorrow 
> they should be available.
> 
> Regards,
> 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>  Â  https://www.opensips-solutions.com
>  Â  https://www.siphub.com
> 
> On 10.03.2025 09:55, Bogdan-Andrei Iancu wrote:
>> Hi Andrew,
>>
>> Thanks for the heads-up. Indeed, I see here:
>> Â Â Â  https://apt.opensips.org/pool/bionic/3.5-releases/o/opensips/
>> we are still with the 3.5.3, the 3.5.4 is missing.
>>
>> We will check what is going on.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>> Â  https://www.opensips-solutions.com
>> Â  https://www.siphub.com
>>
>> On 10.03.2025 09:44, Andrew wrote:
>>> Hi
>>> Both release and nightly builds have not been published since the 
>>> beginningÂ of February.
>>> Could anyone please fix this?
>>>
>>> Best regards, Andrew.
>>>
>>> _______________________________________________
>>> 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

From bogdan at opensips.org  Tue Mar 11 09:47:42 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 11 Mar 2025 11:47:42 +0200
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
 <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
 <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>
Message-ID: <bc8d9862-dc78-4197-9f82-5f1606ce6e00@opensips.org>

Hi,

OK, so your opensips is client from TLS pov. So, you need to help 
OpenSIPS to figure out which TLS client domain to use. The simplest ways 
to do it is by forcing directly the name of the TLS client domain (see 
[1]) or by setting a SIP domain (see [2]) that matches 
"match_sip_domain" in your TLS client domain

[1] 
https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_client_tls_domain_avp
[2] 
https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_client_sip_domain_avp

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 18:49, Thiago Lopes wrote:
> Hello,
>
> I tried to change this option, change from self-signed to true 
> certificate, change the listeners and even change the DRouting module 
> to Dispatcher.
>
> Microsoft's documentation says that a SBC must send a packet to them, 
> so they will answer back and will send an OPTIONS packet as soon as 
> the TLS connection was made successfully.
>
> So, when I send the first packet, I will act as a client TLS user. I 
> thought the 'client domain' part, in module configuration was the 
> problem. But even changing the 'server' part too, the result was the 
> same.
>
>     Â /usr/sbin/opensips[676690]: DBG:proto_tls:proto_tls_send: no open
>     tcp connection found, opening new one, async = 1
>     Â /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff:
>     getsockopt: snd is initially 16384
>     Â /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff: using
>     snd buffer of 416 kb
>     Â /usr/sbin/opensips[676690]: DBG:core:init_sock_keepalive: TCP
>     keepalive enabled on socket 5
>     Â /usr/sbin/opensips[676681]: WARNING:core:utimer_ticker: utimer
>     task <tm-utimer> already scheduled 100 ms ago (now 35900 ms),
>     delaying execution
>     Â /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Polling
>     is overdue
>     Â /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Create
>     connection for async connect
>     Â /usr/sbin/opensips[676690]: DBG:core:print_ip: tcpconn_new: new
>     tcp connection to: 52.114.32.169
>     Â /usr/sbin/opensips[676690]: DBG:core:tcpconn_new: on port 5061,
>     proto 3
>     Â /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_conn_init:
>     no TLS client domain found
>     Â /usr/sbin/opensips[676690]: ERROR:core:tcp_conn_create: failed to
>     do proto 3 specific init for conn 0x7f027cb1d070
>     /usr/sbin/opensips[676690]: DBG:core:tcpconn_destroy: delaying
>     (0x7f027cb1d070, flags 0018) ref = -1 ...
>     Â /usr/sbin/opensips[676690]: ERROR:core:tcp_async_connect:
>     tcp_conn_create failed
>     Â /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_send: async
>     TCP connect failed
>
>
> Thank you for your help.
>
> Regards,
>
> On Mon, Mar 10, 2025 at 4:33â€¯AM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hi,
>
>     For the incoming TLS connections, the right TLS server domain is
>     selected based either on the IP address (of OpenSIPS's listener),
>     either on the SIP domain (if SNI is used).
>
>     So, maybe SNI is not used in your case, so you should define a
>     match_ip_address:
>     https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_match_ip_address
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 07.03.2025 23:10, Thiago Lopes via Users wrote:
>>     Hi everyone,
>>
>>     I'm trying to integrate Ms Teams and Opensips and I'm having some
>>     problems.
>>
>>     I tried to use self signedÂ and Letsencrypt certificates, withÂ no
>>     success. I always receive a ''no TLS client domain found'.
>>
>>     Â /usr/sbin/opensips[505412]: ERROR:proto_tls:proto_tls_conn_init:
>>     no TLS client domain found
>>     Â /usr/sbin/opensips[505412]: ERROR:core:tcp_conn_create: failed
>>     to do proto 3 specific init for conn 0x7f7220f343b0
>>     Â /usr/sbin/opensips[505412]: ERROR:core:tcp_async_connect:
>>     tcp_conn_create failed
>>
>>     Here my opensips.cfg:
>>
>>     loadmodule "tls_mgm.so"
>>
>>     /*#first the Â server domain */
>>     modparam("tls_mgm", "server_domain", "default")
>>     modparam("tls_mgm", "certificate",
>>     "[default]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem
>>     <http://sbc.mydomain.com/fullchain.pem>")
>>     modparam("tls_mgm", "private_key",
>>     "[default]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem
>>     <http://sbc.mydomain.com/privkey.pem>")
>>     modparam("tls_mgm", "ca_list",
>>     "[default]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem
>>     <http://sbc.mydomain.com/inter.pem>")
>>     modparam("tls_mgm", "match_sip_domain",
>>     "[default]sbc.mydomain.com <http://sbc.mydomain.com>")
>>     modparam("tls_mgm", "verify_cert", "[default]0")
>>     #modparam("tls_mgm", "require_cert", "[default]1")
>>     #modparam("tls_mgm", "ciphers_list",
>>     "[default]AES128-SHA256:AES256-SHA")
>>     modparam("tls_mgm", "tls_method", "[default]SSLv23")
>>
>>
>>     Â # #and the client domain
>>     modparam("tls_mgm", "client_domain", "client")
>>     modparam("tls_mgm", "certificate",
>>     "[client]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem
>>     <http://sbc.mydomain.com/fullchain.pem>")
>>     modparam("tls_mgm", "private_key",
>>     "[client]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem
>>     <http://sbc.mydomain.com/privkey.pem>")
>>     modparam("tls_mgm", "ca_list",
>>     "[client]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem
>>     <http://sbc.mydomain.com/inter.pem>")
>>     #modparam("tls_mgm", "ca_dir",
>>     "[client]/etc/letsencrypt/live/sbc.mydomain.com/
>>     <http://sbc.mydomain.com/>")
>>     modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com
>>     <http://sbc.mydomain.com>")
>>
>>     modparam("tls_mgm", "verify_cert", "[client]0")
>>     Â # modparam("tls_mgm", "require_cert", "[client]1")
>>     Â # modparam("tls_mgm", "ciphers_list",
>>     "[client]AES128-SHA256:AES256-SHA")
>>     modparam("tls_mgm", "tls_method", "[client]SSLv23")
>>
>>     I also changed the certificates, using self signed in "server
>>     domain" only or "client domain" only. Same result.
>>
>>     Using the openssl the verify the certificates, I receive a OK in
>>     console:
>>
>>     fullchain.pem: OK
>>
>>     The inter.pem is the file with the root and
>>     intermediateÂ Letsencrypt certificates.
>>
>>     On the Ms Teams side, I checked the FQDN used, checked the
>>     firewall ports etc.
>>
>>     I followed this tutorial:
>>     https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/ ,
>>     so I'm using the Dynamic Routing module to send the OPTIONS
>>     packet. The opensips start the communication using TLS, I see the
>>     packets using TLS in 5061 port, but when Opensips will answer,
>>     this message appears on the console and the connection is closed.
>>
>>     /usr/sbin/opensips[505398]: ERROR:tm:t_uac: attempt to send to
>>     'sip:sip.pstnhub.microsoft.com
>>     <http://sip.pstnhub.microsoft.com>' failed
>>     /usr/sbin/opensips[505398]: ERROR:proto_tls:proto_tls_conn_init:
>>     no TLS client domain found
>>     /usr/sbin/opensips[505398]: ERROR:core:tcp_conn_create: failed to
>>     do proto 3 specific init for conn 0x7f7220f4df40
>>
>>     What I'm not seeing? Did someone pass throughÂ this problem?
>>     Best regards
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org
>>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250311/ae8cb229/attachment-0001.html>

From andrey55555 at gmail.com  Tue Mar 11 10:22:02 2025
From: andrey55555 at gmail.com (Andrew)
Date: Tue, 11 Mar 2025 13:22:02 +0300
Subject: [OpenSIPS-Users] New releases are not published to the
 repositories (both APT and YUM)
In-Reply-To: <682b6d47-3fac-4d0e-abb2-f7ad7b8912bd@opensips.org>
References: <CA+B63qK96fEVx8UDVRu6euzEMdCk+YupVokOp6J8YOgUKutQwg@mail.gmail.com>
 <2b8feda6-7c63-40e7-963a-cc12caa54267@opensips.org>
 <c2d108c3-e772-4bac-a7b1-3216f0f5787f@opensips.org>
 <682b6d47-3fac-4d0e-abb2-f7ad7b8912bd@opensips.org>
Message-ID: <CA+B63q+P87WU1jgNPFPxCEoObnN9b8OdJ4GB9AtE8mJUhHB3eA@mail.gmail.com>

Thank you very much.
Looks like everything is fine now.

Best regards, Andrew.

Ð²Ñ‚, 11 Ð¼Ð°Ñ€. 2025â€¯Ð³. Ð² 11:39, RÄƒzvan Crainea <razvan at opensips.org>:

> Hi, All!
>
> Repositories should be fixed now, and all packages available. Please let
> us know if there's anything missing.
>
> Best regards,
>
> RÄƒzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com / https://www.siphub.com
>
> On 3/10/25 6:13 PM, Bogdan-Andrei Iancu wrote:
> > Quick update - the issue was identified and fixed, the missing builds
> > are work in progress (it takes a while the whole compiling). Tomorrow
> > they should be available.
> >
> > Regards,
> >
> > Bogdan-Andrei Iancu
> >
> > OpenSIPS Founder and Developer
> >    https://www.opensips-solutions.com
> >    https://www.siphub.com
> >
> > On 10.03.2025 09:55, Bogdan-Andrei Iancu wrote:
> >> Hi Andrew,
> >>
> >> Thanks for the heads-up. Indeed, I see here:
> >>     https://apt.opensips.org/pool/bionic/3.5-releases/o/opensips/
> >> we are still with the 3.5.3, the 3.5.4 is missing.
> >>
> >> We will check what is going on.
> >>
> >> Regards,
> >>
> >> Bogdan-Andrei Iancu
> >>
> >> OpenSIPS Founder and Developer
> >>   https://www.opensips-solutions.com
> >>   https://www.siphub.com
> >>
> >> On 10.03.2025 09:44, Andrew wrote:
> >>> Hi
> >>> Both release and nightly builds have not been published since the
> >>> beginning of February.
> >>> Could anyone please fix this?
> >>>
> >>> Best regards, Andrew.
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users at lists.opensips.org
> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >>
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250311/a106cd84/attachment.html>

From tlopes at unitedworldtelecom.com  Tue Mar 11 16:48:25 2025
From: tlopes at unitedworldtelecom.com (Thiago Lopes)
Date: Tue, 11 Mar 2025 13:48:25 -0300
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <bc8d9862-dc78-4197-9f82-5f1606ce6e00@opensips.org>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
 <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
 <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>
 <bc8d9862-dc78-4197-9f82-5f1606ce6e00@opensips.org>
Message-ID: <CABMr7hkSsFrR2dk2TPcXVuu7imP4=0sNJcZPOmLq77SOBPUXoQ@mail.gmail.com>

Hi Bogdan-Andrei,

I already did this too. The result in the log file was the same.

Actually, even with changing the tls_mgm module, or from openssl to
wolfssl, I saw that the module who answer with error is proto_tls:

 /usr/sbin/opensips[4634]: DBG:core:init_sock_keepalive: TCP keepalive
enabled on socket 5
 /usr/sbin/opensips[4634]: DBG:core:print_ip: tcpconn_new: new tcp
connection to: 52.114.76.76
 /usr/sbin/opensips[4634]: DBG:core:tcpconn_new: on port 5061, proto 3
* /usr/sbin/opensips[4634]: ERROR:proto_tls:proto_tls_conn_init: no TLS
client domain found*
 /usr/sbin/opensips[4634]: ERROR:core:tcp_conn_create: failed to do proto 3
specific init for conn 0x7f794a63d080
 /usr/sbin/opensips[4634]: DBG:core:tcpconn_destroy: delaying
(0x7f794a63d080, flags 0018) ref = -1 ...

My actual cfg file:

#loadmodule "tls_openssl.so"
loadmodule "tls_wolfssl.so"

####TLS module
loadmodule "tls_mgm.so"
 /*#first the  server domain */
modparam("tls_mgm", "server_domain", "default")
modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/fullchain.pem")
modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/privkey.pem")
modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/
sbc.mydomain.com/inter.pem")
modparam("tls_mgm", "match_ip_address", "[default]x.x.x.x:5061")
modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com")
#modparam("tls_mgm", "verify_cert", "[default]0")
#modparam("tls_mgm", "require_cert", "[default]1")
#modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[default]SSLv23")

 # #and the client domain

modparam("tls_mgm", "client_domain", "client")
modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/fullchain.pem")
modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/privkey.pem")
modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/inter.pem")
#modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/
sbc.mydomain.com/")
modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")
modparam("tls_mgm", "match_ip_address", "[client]x.x.x.x:5061")

#modparam("tls_mgm", "verify_cert", "[client]0")
 # modparam("tls_mgm", "require_cert", "[client]1")
 # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[client]SSLv23")

modparam("tls_mgm", "tls_library", "wolfssl")
#modparam("tls_mgm", "tls_handshake_timeout", 300)
modparam("tls_mgm", "client_sip_domain_avp", "sbc.mydomain.com")
modparam("tls_mgm", "client_tls_domain_avp", "sbc.mydomain.com")

loadmodule "proto_tls.so"
#modparam("proto_tls", "tls_async", 0)
modparam("proto_tls", "tls_handshake_timeout", 300)
modparam("proto_tls", "tls_send_timeout", 2000)
modparam("proto_tls", "tls_max_msg_chunks", 8)
modparam("proto_tls", "cert_check_on_conn_reusage", 1)

Enable or no the client_sip_domain_avp, client_tls_domain_avp,
match_sip_domain and match_ip_address in any order do not show any
different results;

I thought maybe make a rollback, from 3.4.11 to another version where
someone did this connection with Teams successfully .

In past versions here in this list I read that some fellows passed to the
same error. But there was an error in the cfg file. I did several
alterations in this file, modules and certificates. The only change that I
didn't make was changing the version.

Regards,

On Tue, Mar 11, 2025 at 6:47â€¯AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi,
>
> OK, so your opensips is client from TLS pov. So, you need to help OpenSIPS
> to figure out which TLS client domain to use. The simplest ways to do it is
> by forcing directly the name of the TLS client domain (see [1]) or by
> setting a SIP domain (see [2]) that matches "match_sip_domain" in your TLS
> client domain
>
> [1]
> https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_client_tls_domain_avp
> [2]
> https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_client_sip_domain_avp
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 10.03.2025 18:49, Thiago Lopes wrote:
>
> Hello,
>
> I tried to change this option, change from self-signed to true
> certificate, change the listeners and even change the DRouting module to
> Dispatcher.
>
> Microsoft's documentation says that a SBC must send a packet to them, so
> they will answer back and will send an OPTIONS packet as soon as the TLS
> connection was made successfully.
>
> So, when I send the first packet, I will act as a client TLS user. I
> thought the 'client domain' part, in module configuration was the problem.
> But even changing the 'server' part too, the result was the same.
>
>  /usr/sbin/opensips[676690]: DBG:proto_tls:proto_tls_send: no open tcp
>> connection found, opening new one, async = 1
>>  /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff: getsockopt:
>> snd is initially 16384
>>  /usr/sbin/opensips[676690]: DBG:core:probe_max_sock_buff: using snd
>> buffer of 416 kb
>>  /usr/sbin/opensips[676690]: DBG:core:init_sock_keepalive: TCP keepalive
>> enabled on socket 5
>>  /usr/sbin/opensips[676681]: WARNING:core:utimer_ticker: utimer task
>> <tm-utimer> already scheduled 100 ms ago (now 35900 ms), delaying execution
>>  /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Polling is
>> overdue
>>  /usr/sbin/opensips[676690]: DBG:core:tcp_async_connect: Create
>> connection for async connect
>>  /usr/sbin/opensips[676690]: DBG:core:print_ip: tcpconn_new: new tcp
>> connection to: 52.114.32.169
>>  /usr/sbin/opensips[676690]: DBG:core:tcpconn_new: on port 5061, proto 3
>>  /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_conn_init: no TLS
>> client domain found
>>  /usr/sbin/opensips[676690]: ERROR:core:tcp_conn_create: failed to do
>> proto 3 specific init for conn 0x7f027cb1d070
>> /usr/sbin/opensips[676690]: DBG:core:tcpconn_destroy: delaying
>> (0x7f027cb1d070, flags 0018) ref = -1 ...
>>  /usr/sbin/opensips[676690]: ERROR:core:tcp_async_connect:
>> tcp_conn_create failed
>>  /usr/sbin/opensips[676690]: ERROR:proto_tls:proto_tls_send: async TCP
>> connect failed
>
>
> Thank you for your help.
>
> Regards,
>
> On Mon, Mar 10, 2025 at 4:33â€¯AM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi,
>>
>> For the incoming TLS connections, the right TLS server domain is selected
>> based either on the IP address (of OpenSIPS's listener), either on the SIP
>> domain (if SNI is used).
>>
>> So, maybe SNI is not used in your case, so you should define a
>> match_ip_address:
>>
>> https://opensips.org/html/docs/modules/3.4.x/tls_mgm.html#param_match_ip_address
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 07.03.2025 23:10, Thiago Lopes via Users wrote:
>>
>> Hi everyone,
>>
>> I'm trying to integrate Ms Teams and Opensips and I'm having some
>> problems.
>>
>> I tried to use self signed and Letsencrypt certificates, with no success.
>> I always receive a ''no TLS client domain found'.
>>
>>  /usr/sbin/opensips[505412]: ERROR:proto_tls:proto_tls_conn_init: no TLS
>> client domain found
>>  /usr/sbin/opensips[505412]: ERROR:core:tcp_conn_create: failed to do
>> proto 3 specific init for conn 0x7f7220f343b0
>>  /usr/sbin/opensips[505412]: ERROR:core:tcp_async_connect:
>> tcp_conn_create failed
>>
>> Here my opensips.cfg:
>>
>> loadmodule "tls_mgm.so"
>>
>> /*#first the  server domain */
>> modparam("tls_mgm", "server_domain", "default")
>> modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/
>> sbc.mydomain.com/fullchain.pem")
>> modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/
>> sbc.mydomain.com/privkey.pem")
>> modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/
>> sbc.mydomain.com/inter.pem")
>> modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com")
>> modparam("tls_mgm", "verify_cert", "[default]0")
>> #modparam("tls_mgm", "require_cert", "[default]1")
>> #modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
>> modparam("tls_mgm", "tls_method", "[default]SSLv23")
>>
>>
>>  # #and the client domain
>>
>> modparam("tls_mgm", "client_domain", "client")
>> modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/
>> sbc.mydomain.com/fullchain.pem")
>> modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/
>> sbc.mydomain.com/privkey.pem")
>> modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/
>> sbc.mydomain.com/inter.pem")
>> #modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/
>> sbc.mydomain.com/")
>> modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")
>>
>> modparam("tls_mgm", "verify_cert", "[client]0")
>>  # modparam("tls_mgm", "require_cert", "[client]1")
>>  # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
>> modparam("tls_mgm", "tls_method", "[client]SSLv23")
>>
>> I also changed the certificates, using self signed in "server domain"
>> only or "client domain" only. Same result.
>>
>> Using the openssl the verify the certificates, I receive a OK in console:
>>
>> fullchain.pem: OK
>>
>> The inter.pem is the file with the root and intermediate Letsencrypt
>> certificates.
>>
>> On the Ms Teams side, I checked the FQDN used, checked the firewall ports
>> etc.
>>
>> I followed this tutorial:
>> https://blog.opensips.org/2019/09/16/opensips-as-ms-teams-sbc/  , so I'm
>> using the Dynamic Routing module to send the OPTIONS packet. The opensips
>> start the communication using TLS, I see the packets using TLS in 5061
>> port, but when Opensips will answer, this message appears on the console
>> and the connection is closed.
>>
>> /usr/sbin/opensips[505398]: ERROR:tm:t_uac: attempt to send to 'sip:
>> sip.pstnhub.microsoft.com' failed
>> /usr/sbin/opensips[505398]: ERROR:proto_tls:proto_tls_conn_init: no TLS
>> client domain found
>> /usr/sbin/opensips[505398]: ERROR:core:tcp_conn_create: failed to do
>> proto 3 specific init for conn 0x7f7220f4df40
>>
>> What I'm not seeing? Did someone pass through this problem?
>> Best regards
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250311/e0dd376f/attachment-0001.html>

From Ben.Newlin at genesys.com  Tue Mar 11 18:09:02 2025
From: Ben.Newlin at genesys.com (Ben Newlin)
Date: Tue, 11 Mar 2025 18:09:02 +0000
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <CABMr7hkSsFrR2dk2TPcXVuu7imP4=0sNJcZPOmLq77SOBPUXoQ@mail.gmail.com>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
 <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
 <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>
 <bc8d9862-dc78-4197-9f82-5f1606ce6e00@opensips.org>
 <CABMr7hkSsFrR2dk2TPcXVuu7imP4=0sNJcZPOmLq77SOBPUXoQ@mail.gmail.com>
Message-ID: <BN0PR10MB520840F849EAD99DA129539E95D12@BN0PR10MB5208.namprd10.prod.outlook.com>

The configuration values for the â€œclient_sip_domain_avpâ€ and â€œclient_tls_domain_avpâ€ modparams are supposed to be the names of AVP variables, not domain names. They also represent 2 different ways to specify the desired client. The â€œmatch_ip_addressâ€ modparam is a third way to specify the client, or can be used in conjunction with SIP domain for additional flexibility.

First, if you only have one client as in your config example then both IP and domain matching are unnecessary. You can simply specify the client to match everything and all outbound TLS will use that client:

src/main/config/forward/module.cfg:45:modparam("tls_mgm", "match_ip_address", "[ client]*")
src/main/config/forward/module.cfg:46:modparam("tls_mgm", "match_sip_domain", "[ client]*")

If you do have multiple clients or you just want to directly specify the client anyway, then you can choose one of the methods to do so.

A. SIP Domain/IP Matching (see [1], [2], [3], [4])

1. Specify the SIP domain and/or IP which matches the client uses the respective modparams:

modparam("tls_mgm", "match_ip_address", "[client]x.x.x.x:5061")
modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")

2. Specify the name of the AVP which your config script will populate with the SIP domain value to be used for matching against the client. This is only required if you want SIP Domain matching; itâ€™s not required for IP matching.

modparam("tls_mgm", "client_sip_domain_avp", "tls_client_sip")

3. In your config script, set the named AVP to the appropriate domain for the message currently being processed. This could be the Request-URI domain ($rd), Destination URI domain ($dd), or anything else you like.

$avp(tls_client_sip) := â€œsbc.mydomain.comâ€; // or $rd or $dd or whatever

B. TLS Client Name Matching (see [5])

1. Specify the TLS client domain name via the modparam:

modparam("tls_mgm", "client_domain", "client")

2. Specify the name of the AVP which your config script will populate with the TLS client name to be used:

modparam("tls_mgm", "client_tls_domain_avp",  â€œtls_client_name")

3. In your config script, set the named AVP to the name of the TLS client you wish to use for the message currently being processed.

$avp(tls_client_name) := â€œclientâ€;

[1] - https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_match_sip_domain
[2] - https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_match_ip_address
[3] - https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_client_sip_domain_avp
[4] - https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#domains-param
[5] - https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_client_tls_domain_avp

Ben Newlin

From: Users <users-bounces at lists.opensips.org> on behalf of Thiago Lopes via Users <users at lists.opensips.org>
Date: Tuesday, March 11, 2025 at 12:49â€¯PM
To: Bogdan-Andrei Iancu <bogdan at opensips.org>
Cc: OpenSIPS users mailling list <users at lists.opensips.org>
Subject: Re: [OpenSIPS-Users] MS Teams and SBC integration
 EXTERNAL EMAIL - Please use caution with links and attachments

________________________________
Hi Bogdan-Andrei,

I already did this too. The result in the log file was the same.

Actually, even with changing the tls_mgm module, or from openssl to wolfssl, I saw that the module who answer with error is proto_tls:

 /usr/sbin/opensips[4634]: DBG:core:init_sock_keepalive: TCP keepalive enabled on socket 5
 /usr/sbin/opensips[4634]: DBG:core:print_ip: tcpconn_new: new tcp connection to: 52.114.76.76
 /usr/sbin/opensips[4634]: DBG:core:tcpconn_new: on port 5061, proto 3
 /usr/sbin/opensips[4634]: ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
 /usr/sbin/opensips[4634]: ERROR:core:tcp_conn_create: failed to do proto 3 specific init for conn 0x7f794a63d080
 /usr/sbin/opensips[4634]: DBG:core:tcpconn_destroy: delaying (0x7f794a63d080, flags 0018) ref = -1 ...

My actual cfg file:

#loadmodule "tls_openssl.so"
loadmodule "tls_wolfssl.so"

####TLS module
loadmodule "tls_mgm.so"
 /*#first the  server domain */
modparam("tls_mgm", "server_domain", "default")
modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem<http://sbc.mydomain.com/fullchain.pem>")
modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem<http://sbc.mydomain.com/privkey.pem>")
modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem<http://sbc.mydomain.com/inter.pem>")
modparam("tls_mgm", "match_ip_address", "[default]x.x.x.x:5061")
modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com<http://sbc.mydomain.com>")
#modparam("tls_mgm", "verify_cert", "[default]0")
#modparam("tls_mgm", "require_cert", "[default]1")
#modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[default]SSLv23")

 # #and the client domain
modparam("tls_mgm", "client_domain", "client")
modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/sbc.mydomain.com/fullchain.pem<http://sbc.mydomain.com/fullchain.pem>")
modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/sbc.mydomain.com/privkey.pem<http://sbc.mydomain.com/privkey.pem>")
modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/sbc.mydomain.com/inter.pem<http://sbc.mydomain.com/inter.pem>")
#modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/sbc.mydomain.com/<http://sbc.mydomain.com/>")
modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com<http://sbc.mydomain.com>")
modparam("tls_mgm", "match_ip_address", "[client]x.x.x.x:5061")

#modparam("tls_mgm", "verify_cert", "[client]0")
 # modparam("tls_mgm", "require_cert", "[client]1")
 # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
modparam("tls_mgm", "tls_method", "[client]SSLv23")

modparam("tls_mgm", "tls_library", "wolfssl")
#modparam("tls_mgm", "tls_handshake_timeout", 300)
modparam("tls_mgm", "client_sip_domain_avp", "sbc.mydomain.com<http://sbc.mydomain.com>")
modparam("tls_mgm", "client_tls_domain_avp", "sbc.mydomain.com<http://sbc.mydomain.com>")

loadmodule "proto_tls.so"
#modparam("proto_tls", "tls_async", 0)
modparam("proto_tls", "tls_handshake_timeout", 300)
modparam("proto_tls", "tls_send_timeout", 2000)
modparam("proto_tls", "tls_max_msg_chunks", 8)
modparam("proto_tls", "cert_check_on_conn_reusage", 1)

Enable or no the client_sip_domain_avp, client_tls_domain_avp, match_sip_domain and match_ip_address in any order do not show any different results;

I thought maybe make a rollback, from 3.4.11 to another version where someone did this connection with Teams successfully .

In past versions here in this list I read that some fellows passed to the same error. But there was an error in the cfg file. I did several alterations in this file, modules and certificates. The only change that I didn't make was changing the version.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250311/1345d9c6/attachment-0001.html>

From tlopes at unitedworldtelecom.com  Wed Mar 12 11:43:57 2025
From: tlopes at unitedworldtelecom.com (Thiago Lopes)
Date: Wed, 12 Mar 2025 08:43:57 -0300
Subject: [OpenSIPS-Users] MS Teams and SBC integration
In-Reply-To: <BN0PR10MB520840F849EAD99DA129539E95D12@BN0PR10MB5208.namprd10.prod.outlook.com>
References: <CABMr7h=8U0K5ZGXcKT2xpLNdyVseRuhAJZOKxNj=RVZ=HC3TnA@mail.gmail.com>
 <f407795d-1cbd-4cc2-a4b6-d8fc9d028d17@opensips.org>
 <CABMr7hkQwBrHwdevBPFaXFm0Ht_Nbmg7vHxJYGfcFWy1C9VuCw@mail.gmail.com>
 <bc8d9862-dc78-4197-9f82-5f1606ce6e00@opensips.org>
 <CABMr7hkSsFrR2dk2TPcXVuu7imP4=0sNJcZPOmLq77SOBPUXoQ@mail.gmail.com>
 <BN0PR10MB520840F849EAD99DA129539E95D12@BN0PR10MB5208.namprd10.prod.outlook.com>
Message-ID: <CABMr7hm+iR5hJ=GGpJodLRuYFmBsJhZUHvJo46BfXxCKRyb3=A@mail.gmail.com>

Hey Ben,

Thank you for your email. I really misunderstood this topic and wrote it
wrong.

Now finally I have a new error. It's about the local issuer certificate.
I'm using Letsencrypt and Microsoft's using Digicert as CA

 /usr/sbin/opensips[24021]: NOTICE:tls_openssl:verify_callback: depth = 1,
verify failure
 /usr/sbin/opensips[24021]: NOTICE:tls_openssl:verify_callback: subject =
/C=US/O=Microsoft Corporation/CN=Microsoft Azure RSA TLS Issuing CA 03
 /usr/sbin/opensips[24021]: NOTICE:tls_openssl:verify_callback: issuer  =
/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Global Root G2
 /usr/sbin/opensips[24021]: NOTICE:tls_openssl:verify_callback: verify
error: unable to get local issuer certificate [error=20]
 /usr/sbin/opensips[24021]: ERROR:tls_openssl:openssl_tls_async_connect:
New TLS connection to 52.114.132.46:5061 failed

I'll troubleshoot this error, and make some tests using openssl to see what
happens here.

Thank you for your help.

Regards,

On Tue, Mar 11, 2025 at 3:09â€¯PM Ben Newlin <Ben.Newlin at genesys.com> wrote:

> The configuration values for the â€œclient_sip_domain_avpâ€ and
> â€œclient_tls_domain_avpâ€ modparams are supposed to be the names of AVP
> variables, not domain names. They also represent 2 different ways to
> specify the desired client. The â€œmatch_ip_addressâ€ modparam is a third way
> to specify the client, or can be used in conjunction with SIP domain for
> additional flexibility.
>
>
>
> First, if you only have one client as in your config example then both IP
> and domain matching are unnecessary. You can simply specify the client to
> match everything and all outbound TLS will use that client:
>
>
>
> src/main/config/forward/module.cfg:45:modparam("tls_mgm",
> "match_ip_address", "[ client]*")
>
> src/main/config/forward/module.cfg:46:modparam("tls_mgm",
> "match_sip_domain", "[ client]*")
>
>
>
> If you do have multiple clients or you just want to directly specify the
> client anyway, then you can choose one of the methods to do so.
>
>
>
> A. SIP Domain/IP Matching (see [1], [2], [3], [4])
>
>
>
> 1. Specify the SIP domain and/or IP which matches the client uses the
> respective modparams:
>
>
>
> modparam("tls_mgm", "match_ip_address", "[client]x.x.x.x:5061")
>
> modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")
>
>
>
> 2. Specify the name of the AVP which your config script will populate with
> the SIP domain value to be used for matching against the client. This is
> only required if you want SIP Domain matching; itâ€™s not required for IP
> matching.
>
>
>
> modparam("tls_mgm", "client_sip_domain_avp", "tls_client_sip")
>
>
>
> 3. In your config script, set the named AVP to the appropriate domain for
> the message currently being processed. This could be the Request-URI domain
> ($rd), Destination URI domain ($dd), or anything else you like.
>
>
>
> $avp(tls_client_sip) := â€œsbc.mydomain.comâ€; // or $rd or $dd or whatever
>
>
>
> B. TLS Client Name Matching (see [5])
>
>
>
> 1. Specify the TLS client domain name via the modparam:
>
>
>
> modparam("tls_mgm", "client_domain", "client")
>
>
>
> 2. Specify the name of the AVP which your config script will populate with
> the TLS client name to be used:
>
>
>
> modparam("tls_mgm", "client_tls_domain_avp",  â€œtls_client_name")
>
>
>
> 3. In your config script, set the named AVP to the name of the TLS client
> you wish to use for the message currently being processed.
>
>
>
> $avp(tls_client_name) := â€œclientâ€;
>
> [1] -
> https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_match_sip_domain
>
> [2] -
> https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_match_ip_address
>
> [3] -
> https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_client_sip_domain_avp
>
> [4] -
> https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#domains-param
>
> [5] -
> https://opensips.org/html/docs/modules/3.6.x/tls_mgm.html#param_client_tls_domain_avp
>
>
>
>
>
> Ben Newlin
>
>
>
> *From: *Users <users-bounces at lists.opensips.org> on behalf of Thiago
> Lopes via Users <users at lists.opensips.org>
> *Date: *Tuesday, March 11, 2025 at 12:49â€¯PM
> *To: *Bogdan-Andrei Iancu <bogdan at opensips.org>
> *Cc: *OpenSIPS users mailling list <users at lists.opensips.org>
> *Subject: *Re: [OpenSIPS-Users] MS Teams and SBC integration
>
> * EXTERNAL EMAIL - Please use caution with links and attachments *
>
>
> ------------------------------
>
> Hi Bogdan-Andrei,
>
>
>
> I already did this too. The result in the log file was the same.
>
>
>
> Actually, even with changing the tls_mgm module, or from openssl to
> wolfssl, I saw that the module who answer with error is proto_tls:
>
>
>
>  /usr/sbin/opensips[4634]: DBG:core:init_sock_keepalive: TCP keepalive
> enabled on socket 5
>  /usr/sbin/opensips[4634]: DBG:core:print_ip: tcpconn_new: new tcp
> connection to: 52.114.76.76
>  /usr/sbin/opensips[4634]: DBG:core:tcpconn_new: on port 5061, proto 3
> * /usr/sbin/opensips[4634]: ERROR:proto_tls:proto_tls_conn_init: no TLS
> client domain found*
>  /usr/sbin/opensips[4634]: ERROR:core:tcp_conn_create: failed to do proto
> 3 specific init for conn 0x7f794a63d080
>  /usr/sbin/opensips[4634]: DBG:core:tcpconn_destroy: delaying
> (0x7f794a63d080, flags 0018) ref = -1 ...
>
>
>
> My actual cfg file:
>
>
>
> #loadmodule "tls_openssl.so"
> loadmodule "tls_wolfssl.so"
>
> ####TLS module
> loadmodule "tls_mgm.so"
>  /*#first the  server domain */
> modparam("tls_mgm", "server_domain", "default")
> modparam("tls_mgm", "certificate", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/fullchain.pem")
> modparam("tls_mgm", "private_key", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[default]/etc/letsencrypt/live/
> sbc.mydomain.com/inter.pem")
> modparam("tls_mgm", "match_ip_address", "[default]x.x.x.x:5061")
> modparam("tls_mgm", "match_sip_domain", "[default]sbc.mydomain.com")
> #modparam("tls_mgm", "verify_cert", "[default]0")
> #modparam("tls_mgm", "require_cert", "[default]1")
> #modparam("tls_mgm", "ciphers_list", "[default]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[default]SSLv23")
>
>
>  # #and the client domain
>
> modparam("tls_mgm", "client_domain", "client")
> modparam("tls_mgm", "certificate", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/fullchain.pem")
> modparam("tls_mgm", "private_key", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/privkey.pem")
> modparam("tls_mgm", "ca_list", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/inter.pem")
> #modparam("tls_mgm", "ca_dir", "[client]/etc/letsencrypt/live/
> sbc.mydomain.com/")
> modparam("tls_mgm", "match_sip_domain", "[client]sbc.mydomain.com")
> modparam("tls_mgm", "match_ip_address", "[client]x.x.x.x:5061")
>
> #modparam("tls_mgm", "verify_cert", "[client]0")
>  # modparam("tls_mgm", "require_cert", "[client]1")
>  # modparam("tls_mgm", "ciphers_list", "[client]AES128-SHA256:AES256-SHA")
> modparam("tls_mgm", "tls_method", "[client]SSLv23")
>
>
>
> modparam("tls_mgm", "tls_library", "wolfssl")
> #modparam("tls_mgm", "tls_handshake_timeout", 300)
> modparam("tls_mgm", "client_sip_domain_avp", "sbc.mydomain.com")
> modparam("tls_mgm", "client_tls_domain_avp", "sbc.mydomain.com")
>
> loadmodule "proto_tls.so"
> #modparam("proto_tls", "tls_async", 0)
> modparam("proto_tls", "tls_handshake_timeout", 300)
> modparam("proto_tls", "tls_send_timeout", 2000)
> modparam("proto_tls", "tls_max_msg_chunks", 8)
> modparam("proto_tls", "cert_check_on_conn_reusage", 1)
>
>
>
>
>
> Enable or no the client_sip_domain_avp, client_tls_domain_avp,
> match_sip_domain and match_ip_address in any order do not show any
> different results;
>
>
>
> I thought maybe make a rollback, from 3.4.11 to another version where
> someone did this connection with Teams successfully .
>
>
>
> In past versions here in this list I read that some fellows passed to the
> same error. But there was an error in the cfg file. I did several
> alterations in this file, modules and certificates. The only change that I
> didn't make was changing the version.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250312/328edf06/attachment-0001.html>

From rodrigopassos at gmail.com  Wed Mar 12 18:47:28 2025
From: rodrigopassos at gmail.com (Rodrigo R Passos)
Date: Wed, 12 Mar 2025 15:47:28 -0300
Subject: [OpenSIPS-Users] Google Voice and Opensips
Message-ID: <CAF9oA8mUnJaJou7GuJ6gA4US-0TNSVW-a0+3tUs8WTQZE30yLg@mail.gmail.com>

Hi all,

Anyone made some interconnecting Opensips with Google Voice services?
If yes, could share with us some experiences about this integration and
some paths about your configuration?

BR ,

Rodrigo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250312/1c105937/attachment.html>

From tlopes at unitedworldtelecom.com  Wed Mar 12 19:41:40 2025
From: tlopes at unitedworldtelecom.com (Thiago Lopes)
Date: Wed, 12 Mar 2025 16:41:40 -0300
Subject: [OpenSIPS-Users] Google Voice and Opensips
In-Reply-To: <CAF9oA8mUnJaJou7GuJ6gA4US-0TNSVW-a0+3tUs8WTQZE30yLg@mail.gmail.com>
References: <CAF9oA8mUnJaJou7GuJ6gA4US-0TNSVW-a0+3tUs8WTQZE30yLg@mail.gmail.com>
Message-ID: <CABMr7hk7FX6JJAyGUErPrM-+P-g3LtHFRXTbsF=iO5+GoFzqbg@mail.gmail.com>

Hi Rodrigo,

Did you see this link?

https://support.google.com/a/answer/11606486?hl=en#zippy=

Basically it's the same as Microsoft Teams. There are some supported
vendors for SBC and SIP carriers, and you will need a license to be able to
connect your Workspace to any SBC.

Regards,

On Wed, Mar 12, 2025 at 3:49â€¯PM Rodrigo R Passos <rodrigopassos at gmail.com>
wrote:

> Hi all,
>
> Anyone made some interconnecting Opensips with Google Voice services?
> If yes, could share with us some experiences about this integration and
> some paths about your configuration?
>
> BR ,
>
> Rodrigo
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250312/b6a95f96/attachment.html>

From rodrigopassos at gmail.com  Wed Mar 12 20:04:40 2025
From: rodrigopassos at gmail.com (Rodrigo R Passos)
Date: Wed, 12 Mar 2025 17:04:40 -0300
Subject: [OpenSIPS-Users] Google Voice and Opensips
In-Reply-To: <CABMr7hk7FX6JJAyGUErPrM-+P-g3LtHFRXTbsF=iO5+GoFzqbg@mail.gmail.com>
References: <CAF9oA8mUnJaJou7GuJ6gA4US-0TNSVW-a0+3tUs8WTQZE30yLg@mail.gmail.com>
 <CABMr7hk7FX6JJAyGUErPrM-+P-g3LtHFRXTbsF=iO5+GoFzqbg@mail.gmail.com>
Message-ID: <CAF9oA8nyhr7ge9Le_ChmMuXYfM0RrPaOhGiR89mUGJupnQKBvg@mail.gmail.com>

Hi Thiago,

Yes, of course. Tks.

BR,
Rodrigo

Em qua., 12 de mar. de 2025 Ã s 16:45, Thiago Lopes via Users <
users at lists.opensips.org> escreveu:

> Hi Rodrigo,
>
> Did you see this link?
>
> https://support.google.com/a/answer/11606486?hl=en#zippy=
>
> Basically it's the same as Microsoft Teams. There are some supported
> vendors for SBC and SIP carriers, and you will need a license to be able to
> connect your Workspace to any SBC.
>
> Regards,
>
> On Wed, Mar 12, 2025 at 3:49â€¯PM Rodrigo R Passos <rodrigopassos at gmail.com>
> wrote:
>
>> Hi all,
>>
>> Anyone made some interconnecting Opensips with Google Voice services?
>> If yes, could share with us some experiences about this integration and
>> some paths about your configuration?
>>
>> BR ,
>>
>> Rodrigo
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250312/6893e19b/attachment.html>

From bogdan at opensips.org  Fri Mar 14 10:13:55 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 14 Mar 2025 12:13:55 +0200
Subject: [OpenSIPS-Users] OpenSIPS Summit 2025 - Call for T-Shirt design
Message-ID: <47eaacf4-fca0-47c4-8d82-7844d969179b@opensips.org>

Each year we came up with different designs for the OpenSIPS Summit 
T-shirts, to reflect the specific of the location hosting our event.

And as Open Source suits better with Open T-shirt Design, for the 2025 
Summit, we want to get the entire community involve in the designing 
process :).

If you feel inspired and what the share with us your ideas on the 
T-Shirt design, you can easily do this via this form:
 Â Â Â  https://bit.ly/opensips_summit_tshirt_2025

You can come up with ideas (text description) or images/sketches.

Eager to see your ideas :)

Best regards,

-- 
Bogdan-Andrei Iancu

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

From spce at lard.at  Fri Mar 14 15:21:08 2025
From: spce at lard.at (spce at lard.at)
Date: Fri, 14 Mar 2025 16:21:08 +0100
Subject: [OpenSIPS-Users] SIP-I: init_iam_default Empty Body
Message-ID: <5abb184a-cdef-4582-b021-4a2a187f3aa1@lard.at>

Dear people,

I've got a problem with the SIP-I module in openSIPS 3.5:

I am trying to add a IAM to the SDP-Part of a SIP-INVITE. When using 
add_isup_part() the function is adding a new ISUP section to SDP. Inside 
the ISUP section theres a header but no body part.

init_iam_default is correctly extracting Calling/Called party numbers. 
There is no error in log. I am using the function inside the default 
REQUEST_ROUTE block of the Trunking script.

Does somebody has an idea why my approach isn't working?

Thx,

Malte

> ####Â  SIP_I module
>
> loadmodule "sip_i.so"
> modparam("sip_i", "default_part_headers", 
> "Content-Disposition:signal;handling=required\r\n")
> modparam("sip_i", "country_code", "+43")
>
>
> ####### Routing Logic ########
>
> # main request routing logic
>
> route {
>
> Â Â Â  add_isup_part();
>
> Â Â Â  [default script]
>
> }
>

> --OSS-unique-boundary-42
> Content-Type: application/sdp
>
> [...]
>
> --OSS-unique-boundary-42
> Content-Type: application/ISUP;version=itu-t92+
> Content-Disposition:signal;handling=required
>
> ^^H 

> INFO:sip_i:init_iam_default: Called party number set to: 43991001
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:parse_headers: flags=3000000000
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:_parse_to: end of header reached, state=10
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:_parse_to: display={}, ruri={sip:+43771001 at xxx.at;user=phone}
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> INFO:sip_i:init_iam_default: Calling party number set to: 771001
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:sip_i:add_isup_part_cmd: Initial address message parameters set by 
> default
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:parse_headers: flags=ffffffffffffffff
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:decode_mime_type: Decoding MIME type for:[application/sdp]
> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
> DBG:core:add_body_part: adding mime 
> <application/ISUP;version=itu-t92+>, hdrs 
> <Content-Disposition:signal;handling=required
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  >, body=<>

From sylvain.daste at proton.me  Tue Mar 18 08:44:07 2025
From: sylvain.daste at proton.me (sylvain.daste at proton.me)
Date: Tue, 18 Mar 2025 08:44:07 +0000
Subject: [OpenSIPS-Users] MongoDB module install on Ubuntu 24.04.2 LTS
Message-ID: <cO_FXm5Rs0i0Gy6kD98yxdvVZTo1Gv90OZ98yLCOp8Lpwhr0KEyu8G1FbwFD3iLRmCUrbmYe6Z-SCB2seAWn_UE1mTGFIAQYFUxYcdYqnqE=@proton.me>

Hello,

After installing via APT the opensips-mongodb-module package with the official repository (opensips version 3.4), I got the following message :
dpkg-query: package 'libmongoc-1.0-0' is not installed and no information is available
The module documentation (https://opensips.org/docs/modules/3.4.x/cachedb_mongodb.html) says that the module depends on two libraries :

-

libjson-c2

-

libmongoc-1.0

However it look likes the two libs are not available with these names. Do you confirme that I should instead install : libjson-c5 (https://packages.ubuntu.com/noble/libjson-c5) and

libmongoc-1.0-0t64 (https://packages.ubuntu.com/noble/libmongoc-1.0-0t64) ?

Thank you,
Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250318/116f947d/attachment.html>

From bogdan at opensips.org  Tue Mar 18 09:02:08 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 18 Mar 2025 11:02:08 +0200
Subject: [OpenSIPS-Users] SIP-I: init_iam_default Empty Body
In-Reply-To: <5abb184a-cdef-4582-b021-4a2a187f3aa1@lard.at>
References: <5abb184a-cdef-4582-b021-4a2a187f3aa1@lard.at>
Message-ID: <a2bd3e5a-7ec5-43e1-8b7f-437e69a54506@opensips.org>

Hi Malte,

Keep in mind that the payload of the ISUP body is binary, so may not be 
human readable. Could you do a pcap capturing of the resulting INVITE 
and attach it here?

Regards,

Bogdan-Andrei Iancu

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

On 14.03.2025 17:21, spce at lard.at wrote:
> Dear people,
>
> I've got a problem with the SIP-I module in openSIPS 3.5:
>
> I am trying to add a IAM to the SDP-Part of a SIP-INVITE. When using 
> add_isup_part() the function is adding a new ISUP section to SDP. 
> Inside the ISUP section theres a header but no body part.
>
> init_iam_default is correctly extracting Calling/Called party numbers. 
> There is no error in log. I am using the function inside the default 
> REQUEST_ROUTE block of the Trunking script.
>
> Does somebody has an idea why my approach isn't working?
>
>
> Thx,
>
> Malte
>
>
>> ####Â  SIP_I module
>>
>> loadmodule "sip_i.so"
>> modparam("sip_i", "default_part_headers", 
>> "Content-Disposition:signal;handling=required\r\n")
>> modparam("sip_i", "country_code", "+43")
>>
>>
>> ####### Routing Logic ########
>>
>> # main request routing logic
>>
>> route {
>>
>> Â Â Â  add_isup_part();
>>
>> Â Â Â  [default script]
>>
>> }
>>
>
>> --OSS-unique-boundary-42
>> Content-Type: application/sdp
>>
>> [...]
>>
>> --OSS-unique-boundary-42
>> Content-Type: application/ISUP;version=itu-t92+
>> Content-Disposition:signal;handling=required
>>
>> ^^H 
>
>> INFO:sip_i:init_iam_default: Called party number set to: 43991001
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:parse_headers: flags=3000000000
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:_parse_to: end of header reached, state=10
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:_parse_to: display={}, ruri={sip:+43771001 at xxx.at;user=phone}
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> INFO:sip_i:init_iam_default: Calling party number set to: 771001
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:sip_i:add_isup_part_cmd: Initial address message parameters set 
>> by default
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:parse_headers: flags=ffffffffffffffff
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:decode_mime_type: Decoding MIME type for:[application/sdp]
>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>> DBG:core:add_body_part: adding mime 
>> <application/ISUP;version=itu-t92+>, hdrs 
>> <Content-Disposition:signal;handling=required
>> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  >, body=<>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

From bogdan at opensips.org  Wed Mar 19 10:55:17 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 19 Mar 2025 12:55:17 +0200
Subject: [OpenSIPS-Users] SIP-I: init_iam_default Empty Body
In-Reply-To: <a9ebd84e-eee0-4b5b-9441-fd5c3803a83c@lard.at>
References: <5abb184a-cdef-4582-b021-4a2a187f3aa1@lard.at>
 <a2bd3e5a-7ec5-43e1-8b7f-437e69a54506@opensips.org>
 <a9ebd84e-eee0-4b5b-9441-fd5c3803a83c@lard.at>
Message-ID: <038bb662-a64f-4478-bb84-68a5ebf7e1ab@opensips.org>

Welcome. Check out wireshark, it has a dissector able to "read" ISUP and 
to translate it for humans.

Regards,

Bogdan-Andrei Iancu

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

On 18.03.2025 20:52, Sipwise Mailinglist wrote:
> Dear Bogdan-Andrei,
>
> you are right. It's in binary and sngrep isn't able to display this. 
> Using tcpdump was all I need.
>
> The biggest problems can sometimes have the easiest solution. Thank 
> you for your great help!
>
>
> Best Regards,
>
> Malte
>
> On 18/03/2025 10:02, Bogdan-Andrei Iancu wrote:
>> Hi Malte,
>>
>> Keep in mind that the payload of the ISUP body is binary, so may not 
>> be human readable. Could you do a pcap capturing of the resulting 
>> INVITE and attach it here?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>> Â  https://www.opensips-solutions.com
>> Â  https://www.siphub.com
>>
>> On 14.03.2025 17:21, spce at lard.at wrote:
>>> Dear people,
>>>
>>> I've got a problem with the SIP-I module in openSIPS 3.5:
>>>
>>> I am trying to add a IAM to the SDP-Part of a SIP-INVITE. When using 
>>> add_isup_part() the function is adding a new ISUP section to SDP. 
>>> Inside the ISUP section theres a header but no body part.
>>>
>>> init_iam_default is correctly extracting Calling/Called party 
>>> numbers. There is no error in log. I am using the function inside 
>>> the default REQUEST_ROUTE block of the Trunking script.
>>>
>>> Does somebody has an idea why my approach isn't working?
>>>
>>>
>>> Thx,
>>>
>>> Malte
>>>
>>>
>>>> ####Â  SIP_I module
>>>>
>>>> loadmodule "sip_i.so"
>>>> modparam("sip_i", "default_part_headers", 
>>>> "Content-Disposition:signal;handling=required\r\n")
>>>> modparam("sip_i", "country_code", "+43")
>>>>
>>>>
>>>> ####### Routing Logic ########
>>>>
>>>> # main request routing logic
>>>>
>>>> route {
>>>>
>>>> Â Â Â  add_isup_part();
>>>>
>>>> Â Â Â  [default script]
>>>>
>>>> }
>>>>
>>>
>>>> --OSS-unique-boundary-42
>>>> Content-Type: application/sdp
>>>>
>>>> [...]
>>>>
>>>> --OSS-unique-boundary-42
>>>> Content-Type: application/ISUP;version=itu-t92+
>>>> Content-Disposition:signal;handling=required
>>>>
>>>> ^^H 
>>>
>>>> INFO:sip_i:init_iam_default: Called party number set to: 43991001
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:parse_headers: flags=3000000000
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:_parse_to: end of header reached, state=10
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:_parse_to: display={}, ruri={sip:+43771001 at xxx.at;user=phone}
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> INFO:sip_i:init_iam_default: Calling party number set to: 771001
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:sip_i:add_isup_part_cmd: Initial address message parameters set 
>>>> by default
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:parse_headers: flags=ffffffffffffffff
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:decode_mime_type: Decoding MIME type for:[application/sdp]
>>>> Mar 14 15:51:53 opensips-test /usr/sbin/opensips[74183]: 
>>>> DBG:core:add_body_part: adding mime 
>>>> <application/ISUP;version=itu-t92+>, hdrs 
>>>> <Content-Disposition:signal;handling=required
>>>> >, body=<>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>

From spanda at 3clogic.com  Thu Mar 20 07:17:04 2025
From: spanda at 3clogic.com (Sasmita Panda)
Date: Thu, 20 Mar 2025 12:47:04 +0530
Subject: [OpenSIPS-Users] I need some help/clarification in branch only
	lookup in opensips 3.2 .
Message-ID: <CALf-Q46ZGG6BvWA4uW=v+j-mjWyiT9J3kw1g8T0iaYTPuguUrg@mail.gmail.com>

Hi All ,

I am using opensips 3.2 . For a particular username I am doing branch only
lookup like below * lookup("location", "B") . *

*      After doing a lookup , I am calculating the queue value of each
branch and then trying to deliver calls one by one . *

*      Here the first call goes to the branch with higher q value . But
when the q value of 2 branches is the same to which branch will the call go
first ?*

*      I am seeing  randomness on this (with q value same for 2 users ) .
But I want to fix the  behaviour , i.e. the call should go in FIFO order .
i.e. the user who registers first should get the call first . *

*       How can I achieve this ? *

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

From bogdan at opensips.org  Thu Mar 20 15:00:34 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 20 Mar 2025 17:00:34 +0200
Subject: [OpenSIPS-Users] [Blog] Troubleshooting the OpenSIPS routing logic
Message-ID: <1fd34141-ec3a-43f6-9c50-4177a14a820a@opensips.org>

Who wasn't at a point in time struggling to troubleshoot an OpenSIPS 
routing script? ðŸ˜®

Well, here is your help, teaching how to do it in the right way - fast, 
simple and efficient ðŸ˜‰

https://blog.opensips.org/2025/03/20/troubleshooting-the-opensips-routing-logic/

Enjoy,

-- 
Bogdan-Andrei Iancu

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

From bogdan at opensips.org  Fri Mar 21 13:25:56 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Fri, 21 Mar 2025 15:25:56 +0200
Subject: [OpenSIPS-Users] Request for Public Discussion - improving the
 contribution process
In-Reply-To: <b2a15805-f491-4d21-afc8-47d4e4f5b637@opensips.org>
References: <b2a15805-f491-4d21-afc8-47d4e4f5b637@opensips.org>
Message-ID: <538e8c9d-817d-4665-ba46-2fe51dfdfd33@opensips.org>

heads-up, registration will close by Monday 24th of March 23:59 GMT

Regards,

Bogdan-Andrei Iancu

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

On 10.03.2025 17:37, Bogdan-Andrei Iancu wrote:
>
> Contributing is an important aspect of an Open Source project. Both 
> for the project itself and for its community.
>
> So, we want your feedback and to learn from you how do you see the 
> current process of handling the contributions and if there is anything 
> we can do to improve it. Keep in mind that the overall "contribution" 
> process is a complex one, it is more than a patch only. By 
> "contribution" we do cover eventual documentation/help in code 
> understanding, support for brainstorming codes, generating Pull 
> Requests, the reviewing process.
>
> Any one is more then welcome to provide feedback on this topic - we 
> scheduled a conference discussion (Google Meet) for 25th of March, 
> 14:00 GMT. In order to join, you have to register in advance [1]. This 
> registration is just a formality (yeah, no worries, everyone is 
> welcome) for managing the access to the conference bridge.
>
> So, please register, we are looking forward to hear your feedback on 
> this matter :)
>
> [1] https://bit.ly/contribution_conf_registration
>
> Best regards,
>

From ag at ag-projects.com  Tue Mar 25 13:28:52 2025
From: ag at ag-projects.com (Adrian Georgescu)
Date: Tue, 25 Mar 2025 10:28:52 -0300
Subject: [OpenSIPS-Users] New OpenXCAP 3.0 release
Message-ID: <29F1C262-CF29-4F52-B276-52BC198E2C30@ag-projects.com>

Hello,

OpenXCAP has been refreshed, written in Python 3 and packaged for Ubuntu Noble, Debian unstable and Debian Bookworm.

openxcap (3.0) changelog

 * Ported code to Python 3
 * Modernized code
 * Moved configuration
 * Drop Twisted Web2 and use FastAPI
 * Drop bundled xml.SAX
 * Drop unused code
 * Refactored backends to use SQLModel
 * Use async database connections
 * Updated documentation
 * Changed xml applications to work with FastAPI
 * Use async where needed
 * Reworked debian packaging
 * Added typing in python code
 * Support running behind a reverse web proxy
 * Updated copyright years
 * Updated License
 * Fixed tests

To install or upgrade see https://packages.ag-projects.com/ the package name is openxcap.

Kind regards,
Adrian

From bogdan at opensips.org  Thu Mar 27 12:43:37 2025
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 27 Mar 2025 14:43:37 +0200
Subject: [OpenSIPS-Users] OpenSIPS Summit 2025, first wave of speakers
Message-ID: <73d3c42a-2c63-46c8-b693-5d524d189eed@opensips.org>

We are still working on the final list of speakers and on the schedule, 
but here is the great lineup for now

For more, check https://summit.opensips.org/

Regards,

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20250327/984c8c64/attachment.html>

From razvan at opensips.org  Thu Mar 27 16:01:57 2025
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Thu, 27 Mar 2025 18:01:57 +0200
Subject: [OpenSIPS-Users] MongoDB module install on Ubuntu 24.04.2 LTS
In-Reply-To: <cO_FXm5Rs0i0Gy6kD98yxdvVZTo1Gv90OZ98yLCOp8Lpwhr0KEyu8G1FbwFD3iLRmCUrbmYe6Z-SCB2seAWn_UE1mTGFIAQYFUxYcdYqnqE=@proton.me>
References: <cO_FXm5Rs0i0Gy6kD98yxdvVZTo1Gv90OZ98yLCOp8Lpwhr0KEyu8G1FbwFD3iLRmCUrbmYe6Z-SCB2seAWn_UE1mTGFIAQYFUxYcdYqnqE=@proton.me>
Message-ID: <574a56c8-044b-46ae-97f8-e88bf93cdb5c@opensips.org>

Which opensips 3.4 version are you trying to install, as this should 
have been sorted out in the latest 3.4.11.

Best regards,

RÄƒzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com

On 3/18/25 10:44 AM, sylvain.daste--- via Users wrote:
> Hello,
> 
> After installing via APT the opensips-mongodb-module package with the official repository (opensips version 3.4), I got the following message :
> dpkg-query: package 'libmongoc-1.0-0' is not installed and no information is available
> The module documentation (https://opensips.org/docs/modules/3.4.x/cachedb_mongodb.html) says that the module depends on two libraries :
> 
> -
> 
> libjson-c2
> 
> -
> 
> libmongoc-1.0
> 
> However it look likes the two libs are not available with these names. Do you confirme that I should instead install : libjson-c5 (https://packages.ubuntu.com/noble/libjson-c5) and
> 
> libmongoc-1.0-0t64 (https://packages.ubuntu.com/noble/libmongoc-1.0-0t64) ?
> 
> Thank you,
> Sylvain
> 
> 
> Hello,
> 
> After installing via APT the opensips-mongodb-module package with the 
> official repository (opensips version 3.4), I got the following message :
> dpkg-query: package 'libmongoc-1.0-0' is not installed and no 
> information is available
> The module documentation (https://opensips.org/docs/modules/3.4.x/ 
> cachedb_mongodb.html <https://opensips.org/docs/modules/3.4.x/ 
> cachedb_mongodb.html>) says that the module depends on two libraries :
> 
>   *
> 
>     libjson-c2
> 
>   *
> 
>     libmongoc-1.0
> 
> However it look likes the two libs are not available with these names. 
> Do you confirme that I should instead install : libjson-c5 (https:// 
> packages.ubuntu.com/noble/libjson-c5 <https://packages.ubuntu.com/noble/ 
> libjson-c5>) and
> 
> 
>   libmongoc-1.0-0t64 (https://packages.ubuntu.com/noble/
>   libmongoc-1.0-0t64 <https://packages.ubuntu.com/noble/
>   libmongoc-1.0-0t64>) ?
> 
> Thank you,
> Sylvain
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

From ag at ag-projects.com  Thu Mar 27 22:40:58 2025
From: ag at ag-projects.com (Adrian Georgescu)
Date: Thu, 27 Mar 2025 19:40:58 -0300
Subject: [OpenSIPS-Users] OpenSIPS Summit 2025, first wave of speakers
In-Reply-To: <73d3c42a-2c63-46c8-b693-5d524d189eed@opensips.org>
References: <73d3c42a-2c63-46c8-b693-5d524d189eed@opensips.org>
Message-ID: <8A9C4BC8-C25F-4CB6-834B-23200DED9087@ag-projects.com>

It's wonderful to be in a good company!

> On 27. Mar 2025, at 09:43, Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:
> 
> 
> We are still working on the final list of speakers and on the schedule, but here is the great lineup for now
> 
> 
> 
> For more, check https://summit.opensips.org/
> 
> Regards,
> -- 
> Bogdan-Andrei Iancu
> 
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com <https://www.opensips-solutions.com/>
>   https://www.siphub.com <https://www.siphub.com/>_______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

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

From spanda at 3clogic.com  Fri Mar 28 08:06:07 2025
From: spanda at 3clogic.com (Sasmita Panda)
Date: Fri, 28 Mar 2025 13:36:07 +0530
Subject: [OpenSIPS-Users] Which is the latest stable release of opensips 3.4
	?
Message-ID: <CALf-Q46GJpnJbOMXjxeyrjDzurynH=08A5bbq3HAtLqLPC076Q@mail.gmail.com>

Hi All ,

Will I start working on openisps-3.4.1 or 3.4.11 ?
Which is the stable release without any issue and backlog .

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