Hi Stefan, Sorry for answering the wrong question. :-)
Take a look at this blog post: http://blog.csrpswitch.com/sip-udp-fragmentation-and-kamailio-the-sip-header-diet/ On July 6, 2016 6:02:26 AM EDT, Anonim Stefan <fan...@gmail.com> wrote: >Hi, > >True, I was thinking only about the "Via" and "Record-Route" added by >Kamailio. Didn't know Record-Route had no short form (I was thinking of >something like "rr" due to rr module I guess). In this case I suppose >there >is not much to gain, only from "Via". > >I'm facing some fragmentation issues. My goal is to make the SIP packet >as >small as possible while removing as less SIP headers as I can. I'd >still >like to use UDP. > >Thanks, >Stefan > > >On Wed, Jul 6, 2016 at 12:48 PM, Daniel-Constantin Mierla ><mico...@gmail.com >> wrote: > >> Record-Route has no compact name variant, afaik -- also quickly >checking >> the iana assignments, shows the same: >> >> - >> >> >http://www.iana.org/assignments/sip-parameters/sip-parameters.xhtml#sip-parameters-2 >> >> If smaller size is the target, then Via makes no big difference, so >it >> was never a goal -- the changes in code should not be big. >> >> A quick option is to redefine MY_VIA in config.h to use the compact >form. >> >> A proper option could be introducing a core parameter, adding a new >> define for the short version and use the normal or short form a >matter >> of the parameter value. The function that needs to be changed is >> via_builder(). >> >> Cheers, >> Daniel >> >> >> On 06/07/16 11:40, Olle E. Johansson wrote: >> >> On 06 Jul 2016, at 11:38, Alex Balashov ><abalas...@evaristesys.com> >> wrote: >> >> >> >> Stefan, >> >> >> >> The construction of headers is generally the province of the >> UAs/endpoints of the call. Kamailio understands compact headers, as >all >> compliant SIP stacks do, but it can't singlehandedly reformat them. >> > I think the question was about the headers added by Kamailio - Via >and >> Record-Route. Which makes the question perfectly valid :-) >> > I can’t remember such a setting anywhere and am curious on why it’s >> needed. >> > /O >> > >> > _______________________________________________ >> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >list >> > sr-users@lists.sip-router.org >> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> >> -- >> Daniel-Constantin Mierla >> http://www.asipto.com - http://www.kamailio.org >> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >> >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >list >> sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > > >------------------------------------------------------------------------ > >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users@lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com) Sent from my Google Nexus. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
