Hi all, There was a pull request last week : https://github.com/kamailio/kamailio/pull/1213 People could be interested in a backport. It's about avoiding a core dump in IMS registration scenarios, if the Client does not behave according to RFC 3261 and omits the Content-Length header. RFC 3261 (Table 2): t: The header field SHOULD be sent, but clients/servers need to be prepared to receive messages without that header field. If a stream-based protocol (such as TCP) is used as a transport, then the header field MUST be sent. Content-Length ar t t t t t t All the best Christoph -----Original Message----- From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, August 14, 2017 10:41 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>rg>; Kamailio (SER) - Devel Mailing List <sr-dev(a)lists.kamailio.org> Subject: [SR-Users] Planning Kamailio v5.0.3 Hello, I am considering to release Kamailio v5.0.3 sometime next week, therefore it is the time to backport patches with fixes from master that apply to 5.0 branch. If you are aware of such fix that has to be backported, reply here or make a pull request on github project. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.