[SR-Users] Re: How to keep SIP messages small, possibly below fragmentation limit?
Good morning Henning > 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. topos requires database but not dialog, right? I remember I ran into issues with topos which I was unable to solve. We have a CPE <=> Registrar(kamailio) <=> Routing Core(kamailio) <=> IC topology Topology shall be hidden towards the CPE, not towards the core. But I didn't manage to achieve this, sometimes topology was hidden towards core causing call failure and incorrect restoring of Route/Via header. As I recall this happened in call forwarding scenarios (initiated on the registrar). Btw, is there a way to convert all header to compact header? I'm not sure if our CPE would support them, but it's worth a try. Is there a function returning, or PV containing the sip packet size to try to take actions like removing unnecessary header and codecs if a packet is over a certain size? Mit freundlichen Grüssen -Benoît Panizzon- -- 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: 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:
