From nzdealshelp at gmail.com  Mon Jul 13 04:08:18 2026
From: nzdealshelp at gmail.com (nz deals)
Date: Mon, 13 Jul 2026 16:08:18 +1200
Subject: [OpenSIPS-Users] rtpengine_delete - failed to decode bencoded reply
	from proxy
Message-ID: <CALOQYithVWTchZewqm2h+D52aMXF8nF9b-1Ny9MH7Zj+Xh2d+A@mail.gmail.com>

Hi everyone,

Has anyone come across an issue like this before?

I'm sending rtpengine_delete requests from OpenSIPS to rtpengine, and
occasionally I receive the following error:

ERROR:rtpengine:rtpe_function_call: failed to decode bencoded reply from
proxy

The issue only affects around 2% of calls, while the remaining 98% complete
without any problems. When this happens, OpenSIPS retries the
rtpengine_delete request several times.

Has anyone seen this before or knows what might cause it? Also, is there a
way to safely ignore this error and continue processing if the delete
request fails?
I am running rtpengine Version: 13.3.1.8 and my opensips version is 3.4

Thanks

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

From ag at ag-projects.com  Mon Jul 13 14:07:34 2026
From: ag at ag-projects.com (Adrian Georgescu)
Date: Mon, 13 Jul 2026 16:07:34 +0200
Subject: [OpenSIPS-Users] New OpenXCAP 3.2.1 release
Message-ID: <ACCF24E5-E720-42BF-B268-5B02FD479A1E@ag-projects.com>

Changelog

openxcap (3.2.1)

  * Fixed traceback when attributes is not set
  * Fix adding duplicate uris at each PUT
  * Fix storing boolean attributes   
  * Added Group membership update

openxcap (3.2.0)

  * Added locking to DB for JSON API operations
  * Fixed default uri and attributes in JSON api
  * Added shutdown/stop code for the database connections
  * Refactor/optimize logging
  * Fixed multiple memory leaks
  * Fixed traceback when dburi is None
  * Added better nonce cache

To install or upgrade see https://packages.ag-projects.com/ 

The package name is openxcap

Source code is available at:

https://download.ag-projects.com/OpenXCAP/

Kind regards,
Adrian



From bogdan at opensips.org  Tue Jul 14 11:28:02 2026
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 14 Jul 2026 14:28:02 +0300
Subject: [OpenSIPS-Users] Website documentation rework
Message-ID: <7ae06b2f-88f9-4f73-8bc1-6df2e72049dc@opensips.org>

Hello all,

Here is a short heads-up explaining the avalanche on commits you may 
have noticed.

A massive work in ongoing for restructuring, improving and refactoring 
the OpenSIPS documentation - the module's docs, the OpenSIPS manual, the 
tutorials, everything - the entire documentation is refactored and moved 
to .md format, GIT stored, easy to work with, to contribute to and the 
keep the sync between code and docs.

As said, this is WIP, we will need 1-2 weeks to complete the first 
stage, but I wanted to come up with a quick explanation for the activity 
you see on the GIT repo.

Best regards,

-- 
Bogdan-Andrei Iancu

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



From tahir at ictinnovations.com  Tue Jul 14 11:34:39 2026
From: tahir at ictinnovations.com (Tahir Almas Dhesi)
Date: Tue, 14 Jul 2026 16:34:39 +0500
Subject: [OpenSIPS-Users] Website documentation rework
In-Reply-To: <7ae06b2f-88f9-4f73-8bc1-6df2e72049dc@opensips.org>
References: <7ae06b2f-88f9-4f73-8bc1-6df2e72049dc@opensips.org>
Message-ID: <CAOL0t+L_z1gdUuc5Jwh_MjWJ9dw-nQrB=qOKytgts=qWqEuFbQ@mail.gmail.com>

This is really great news. Moving everything to Markdown in Git is a big
step forward — docs living next to the code makes it so much easier to keep
them
 in sync, and honestly it lowers the barrier a lot for people like us who
spot small gaps or outdated bits while working with the modules but never
bothered with the old workflow to fix them.
Looking forward to seeing the first stage land. Once the structure settles,
would you welcome pull requests for corrections and small improvements, or
should contributions wait until the migration is complete?
 Keep up the great work!

Regards
*Tahir Almas*

Managing Partner
ICT Innovations
http://www.ictinnovations.com
Leveraging open source in ICT


On Tue, Jul 14, 2026 at 4:30 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hello all,
>
> Here is a short heads-up explaining the avalanche on commits you may
> have noticed.
>
> A massive work in ongoing for restructuring, improving and refactoring
> the OpenSIPS documentation - the module's docs, the OpenSIPS manual, the
> tutorials, everything - the entire documentation is refactored and moved
> to .md format, GIT stored, easy to work with, to contribute to and the
> keep the sync between code and docs.
>
> As said, this is WIP, we will need 1-2 weeks to complete the first
> stage, but I wanted to come up with a quick explanation for the activity
> you see on the GIT repo.
>
> Best regards,
>
> --
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.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/20260714/8b57ba4d/attachment.html>

From bogdan at opensips.org  Wed Jul 15 07:57:11 2026
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 15 Jul 2026 10:57:11 +0300
Subject: [OpenSIPS-Users] Website documentation rework
In-Reply-To: <CAOL0t+L_z1gdUuc5Jwh_MjWJ9dw-nQrB=qOKytgts=qWqEuFbQ@mail.gmail.com>
References: <7ae06b2f-88f9-4f73-8bc1-6df2e72049dc@opensips.org>
 <CAOL0t+L_z1gdUuc5Jwh_MjWJ9dw-nQrB=qOKytgts=qWqEuFbQ@mail.gmail.com>
Message-ID: <e08cf770-3c4b-42ef-8f19-37d8f0ec5154@opensips.org>

Thanks Tahir for the feedback here. As said, the work is still WIP, we 
will announce when the docs are ready and the new web URL. After that, 
contributions (via GH PRs) are more than welcome, of course :)

Regards,

Bogdan-Andrei Iancu

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


On 7/14/26 14:34, Tahir Almas Dhesi wrote:
> This is really great news. Moving everything to Markdown in Git is a 
> big step forward — docs living next to the code makes it so much 
> easier to keep them
>  in sync, and honestly it lowers the barrier a lot for people like us 
> who spot small gaps or outdated bits while working with the modules 
> but never
> bothered with the old workflow to fix them.
> Looking forward to seeing the first stage land. Once the structure 
> settles, would you welcome pull requests for corrections and small 
> improvements, or
> should contributions wait until the migration is complete?
>  Keep up the great work!
>
> Regards
> *Tahir Almas*
>
> Managing Partner
> ICT Innovations
> http://www.ictinnovations.com
> Leveraging open source in ICT
>
>
> On Tue, Jul 14, 2026 at 4:30 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hello all,
>
>     Here is a short heads-up explaining the avalanche on commits you may
>     have noticed.
>
>     A massive work in ongoing for restructuring, improving and
>     refactoring
>     the OpenSIPS documentation - the module's docs, the OpenSIPS
>     manual, the
>     tutorials, everything - the entire documentation is refactored and
>     moved
>     to .md format, GIT stored, easy to work with, to contribute to and
>     the
>     keep the sync between code and docs.
>
>     As said, this is WIP, we will need 1-2 weeks to complete the first
>     stage, but I wanted to come up with a quick explanation for the
>     activity
>     you see on the GIT repo.
>
>     Best regards,
>
>     -- 
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>     https://www.opensips-solutions.com
>     https://www.siphub.com
>
>
>     _______________________________________________
>     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/20260715/ccee6cea/attachment.html>

From richard at rikrobson.co.uk  Tue Jul 21 15:27:33 2026
From: richard at rikrobson.co.uk (Richard Robson)
Date: Tue, 21 Jul 2026 16:27:33 +0100
Subject: [OpenSIPS-Users] OpenSIPS 4.0.0 major release, beta version
In-Reply-To: <787acd77-96b4-4c49-986e-38b31674ca72@opensips.org>
References: <787acd77-96b4-4c49-986e-38b31674ca72@opensips.org>
Message-ID: <c97ec030-76c4-4965-82d5-782ad62e2dcb@rikrobson.co.uk>

Hi,

The docker image for 4.0 appears to be 4.0.0-rc2. Is this correct and if 
so when will this get pushed to 4.0.0?

https://hub.docker.com/r/opensips/opensips?tag=4.0


Richard

On 22/04/2026 17:03, Bogdan-Andrei Iancu wrote:
> Hello there !!
>
> It is that time of the year to do our iteration - one more year, one 
> more evolution step, one more OpenSIPS major release.
>
> The *4.0 version is a turning point in the OpenSIPS evolution*. This 
> is a standard release, opening the path for a new family of releases 
> with bold aims to radically change and improve legacy concepts and 
> code in OpenSIPS. Yes, 4.0 addresses old limitations, deprecated 
> designs or burning needs we accumulated across years.
>
> OpenSIPS 4.0 is about _TCP Framework_ rework, about _TLS refreshing_, 
> about _Script and Process Profiling_. A special set of improvements 
> are versatility oriented, like the _Big Scale Forking_, the _Bond 
> Interfaces_ and _Clusters with Bridge Replication_. The integration 
> chapter is as always present with _Proxy Protocol_ support, _IMS 
> interoperability_ and _Auth_web3_ support
>
> But here is the shortest possible description 
> <https://www.opensips.org/About/Version-Overview-3-6-0> of this 
> release; and be aware that it's actually not so short as nothing is 
> short about 4.0 and what it can do !
>
> Please keep in mind that 4.0.0 is still a beta release, targeting mid 
> July to become fully stable. So, we still have some testing ahead of 
> us :).
>
> Many thanks to our awesome community for contributing with ideas, 
> code, patches, tests and reports!
>
> Looking for downloading it? See the tarball 
> <http://opensips.org/pub/opensips/4.0.x> or the GIT repo 
> <https://github.com/OpenSIPS/opensips/tree/4.0>. (it may take a full 
> day to get these in place)
>
> Enjoy it,
> -- 
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>    https://www.opensips-solutions.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/20260721/1f99e106/attachment.html>

From dronord at gmail.com  Sun Jul 26 06:21:57 2026
From: dronord at gmail.com (dronord)
Date: Sun, 26 Jul 2026 09:21:57 +0300
Subject: [OpenSIPS-Users] NATed client and B2BUA module
Message-ID: <CAJTDZ97Ku8EznbUrRcbCt3Ka2=vupcwxU7wY6hv7aE+=v5QLoA@mail.gmail.com>

 Hello.

force_rport() does not work on BYE for locally generated 200 OK.

route {
....
    force_rport();
    b2b_server_new("caller");
    b2b_client_new("callee", "sip:user at host");
....
}

200 OK's Via received= correct and used, but only IP, rport missing.
When client add empty rport in BYE - reply is ok.

There are workaround to get 200 OK on nated client for BYE?)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20260726/8f674895/attachment.html>

