[SR-Users] Development is open for future release of v5.9.x series
Hello, the branch 5.8 was created, therefore the master branch is open for adding new features, to be part of future release series v5.9.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.8.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.8 or 5.7. Expect that v5.8.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.9.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime during the last part of 2024 or the beginning of 2025. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Branch 5.8 has been created
Hello, the branch 5.8 has been created, to be used for releasing v5.8.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.8 cd kamailio-5.8 git checkout -b 5.8 origin/5.8 Pushing commits in this branch: git push origin 5.8:5.8 Note that 5.8 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.8 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.8 will be out, respectively Kamailio v5.8.0. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: How to keep SIP messages small, possibly below fragmentation limit?
Hello, one really effective way is the topos module. If you can not use this, you could switch to compact sip header. This way you save some bytes per header-field. But this is something that needs to be supported from the user agent as well. You could remove not needed headers and SDP inside the Kamailio, but this will probably not help you a lot. In the end the user agents need to be fixed, probably. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com > -Original Message- > From: Benoît Panizzon via sr-users > Sent: Freitag, 23. Februar 2024 16:54 > To: sr-users@lists.kamailio.org > Cc: Benoît Panizzon > Subject: [SR-Users] How to keep SIP messages small, possibly below > fragmentation limit? > > Hi > > In the process of getting rid of our commercial B2Bua SBC and handling all > clients directly via Kamailio... > > We have come across some (unfortunately many we have in use) CPE which > have an issue with fragmented packets or which simply do not allocate enough > memory to parse or create messages of a certain size. Their SIP stack just > crashes with errors like 'message to large for send buffer' > and similar. > > This affects messages with containing as little as 5 via and 4 record-route > header and a couple of codec in the SDP. > > Is there a recipe for trying to keep packets as small as possible? > > I would like to avoid using the topos module as I issues with this module > completely failing in certain situations. > > -- > Mit freundlichen Grüssen > > -Benoît Panizzon- @ HomeOffice und normal erreichbar > -- > I m p r o W a r e A G-Leiter Commerce Kunden > __ > > Zurlindenstrasse 29 Tel +41 61 826 93 00 > CH-4133 PrattelnFax +41 61 826 93 01 > Schweiz Web http://www.imp.ch > __ > __ > Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe > send an email to sr-users-le...@lists.kamailio.org > Important: keep the mailing list in the recipients, do not reply only to the > sender! > Edit mailing list options or unsubscribe: __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] How to keep SIP messages small, possibly below fragmentation limit?
Hi In the process of getting rid of our commercial B2Bua SBC and handling all clients directly via Kamailio... We have come across some (unfortunately many we have in use) CPE which have an issue with fragmented packets or which simply do not allocate enough memory to parse or create messages of a certain size. Their SIP stack just crashes with errors like 'message to large for send buffer' and similar. This affects messages with containing as little as 5 via and 4 record-route header and a couple of codec in the SDP. Is there a recipe for trying to keep packets as small as possible? I would like to avoid using the topos module as I issues with this module completely failing in certain situations. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G-Leiter Commerce Kunden __ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 PrattelnFax +41 61 826 93 01 Schweiz Web http://www.imp.ch __ __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
[SR-Users] Re: Roadmap to next major Kamailio release series v5.8.x
Hello, quick note that later today I will create the branch 5.8, notification emails will be sent once done. Cheers, Daniel On 16.02.24 08:01, Daniel-Constantin Mierla wrote: > Hello, > > hopefully the devel version is now more stabilized after the freezing, > the new components being adjusted enough not to need many more changes. > Therefore I consider to branch 5.8 out of devel version next week on > Friday, February 23, 2024, sometime around noon UTC. > > After that the master branch becomes open for new features, and branch > 5.8 has to be hammered further to build the 5.8.x series. > > Cheers, > Daniel > > On 10.01.24 10:11, Daniel-Constantin Mierla wrote: >> Hello, >> >> discussed a bit during the online Kamailio devel meeting, it is time to >> set the milestones towards the next major Kamailio release series v5.8.x. >> >> If no other suggestions that suit more developers, I would propose to >> freeze by end of this month or early February, then test for about 4 >> weeks as usual and release by end of February or during March. >> >> If anyone wants to add new features/modules, they have to be published >> till freezing date, either pushed in the git repository or proposed as >> pull request. >> >> Cheers, >> Daniel > -- > Daniel-Constantin Mierla (@ asipto.com) > twitter.com/miconda -- linkedin.com/in/miconda > Kamailio Consultancy, Training and Development Services -- asipto.com > Kamailio Advanced Training, February 20-22, 2024 -- asipto.com > Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com > -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio Advanced Training, February 20-22, 2024 -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com __ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-le...@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
