sr-dev March 2010

sr-dev@lists.kamailio.org

24 participants
359 discussions

[ openser-Patches-2961414 ] fix for crash when Content-length too big - ID: 281827
by SourceForge.net 01 Mar '10

01 Mar '10

Patches item #2961414, was opened at 2010-03-01 19:20 Message generated for change (Comment added) made by marcushunger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: fix for crash when Content-length too big - ID: 281827 Initial Comment: are there any valid use cases for a content-length being bigger than the rest of of the packet? i have not tested the issue with kamailio 3.0. ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 20:11 Message: so there's already a fix? i tried this on 1.5.4, and it crashed. maybe i made a mistake merging it to my branch. i am going to check this tomorrow. ---------------------------------------------------------------------- Comment By: Daniel-Constantin Mierla (miconda) Date: 2010-03-01 19:51 Message: This should not happen, as both pairs (msg_buf,msg_len) and (body,body_len) are set internally. The issue with the nathelper was because the len was taken from content-lenght header, which can be wrong. The discussion ended in whether to auto-correct the content-lenght value or return 400 bad message. In 1.5 the fix to avoid crash was to return error to script, 400 can be sent by using sanity module. ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 19:22 Message: sorry, i was not logged in while posting. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_…

1 0

[ openser-Patches-2826542 ] Add id parameter to pua_mi's send_publish
by SourceForge.net 01 Mar '10

01 Mar '10

Patches item #2826542, was opened at 2009-07-24 15:27 Message generated for change (Comment added) made by miconda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2826542&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Alex Hermann (axlh) Assigned to: Nobody/Anonymous (nobody) Summary: Add id parameter to pua_mi's send_publish Initial Comment: When using presence with dialog-info, one needs to be able to specify an id, otherwise presentity from different calls for the same presentity-uri will overwrite each other. This patch makes it possible to specify an 'id' in the MI interface for send_publish. Unfortunately it breaks backward compatibility but it's the only way to use dialog-info with MI without having to manually store a the state of the ETag in the proxy. ---------------------------------------------------------------------- >Comment By: Daniel-Constantin Mierla (miconda) Date: 2010-03-01 21:02 Message: Just saw this one again. Alex, did you commit it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2826542&group_…

1 0

xmlrpc
by Jason Penton 01 Mar '10

01 Mar '10

Hi All, I have taken the ideas from sip-router/ser/kamailio-3.0.0 regarding the XMLRPC management interface. I have used the ideas and incorporated them into kamailio 1.5 and I was wondering how useful this would be giving back to the community? If there is interest, what is the preferred way to distribute (there are a few minor changes to the core - msg_translator and receive)? I suppose a diff against the 1.5 svn would be the best? The advantages over the existing XMLRPC interface: 1. multiple processes to serve xmlrpc requests. Effectively, we use the tcp receive threads to process the xmlrpc calls. 2. no dependence on the Abyss server (this is a big plus for me) therefore, better performance and smaller footprint. ps. my motivation for this is that I had noticed performance issues and memory leaks in the existing mi_xmlrpc module in Kamailio. Cheers Jason

2 2

[ openser-Patches-2961414 ] fix for crash when Content-length too big - ID: 281827
by SourceForge.net 01 Mar '10

01 Mar '10

Patches item #2961414, was opened at 2010-03-01 20:20 Message generated for change (Comment added) made by miconda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: fix for crash when Content-length too big - ID: 281827 Initial Comment: are there any valid use cases for a content-length being bigger than the rest of of the packet? i have not tested the issue with kamailio 3.0. ---------------------------------------------------------------------- >Comment By: Daniel-Constantin Mierla (miconda) Date: 2010-03-01 20:51 Message: This should not happen, as both pairs (msg_buf,msg_len) and (body,body_len) are set internally. The issue with the nathelper was because the len was taken from content-lenght header, which can be wrong. The discussion ended in whether to auto-correct the content-lenght value or return 400 bad message. In 1.5 the fix to avoid crash was to return error to script, 400 can be sent by using sanity module. ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 20:22 Message: sorry, i was not logged in while posting. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_…

1 0

[ openser-Patches-2961414 ] fix for crash when Content-length too big - ID: 281827
by SourceForge.net 01 Mar '10

01 Mar '10

1 0

[ openser-Patches-2961414 ] fix for crash when Content-length too big - ID: 281827
by SourceForge.net 01 Mar '10

01 Mar '10

Patches item #2961414, was opened at 2010-03-01 18:20 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: fix for crash when Content-length too big - ID: 281827 Initial Comment: are there any valid use cases for a content-length being bigger than the rest of of the packet? i have not tested the issue with kamailio 3.0. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743022&aid=2961414&group_…

1 0

[ openser-Bugs-2818273 ] crash when Content-length too big
by SourceForge.net 01 Mar '10

01 Mar '10

Bugs item #2818273, was opened at 2009-07-08 01:28 Message generated for change (Comment added) made by marcushunger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2818273&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: crash when Content-length too big Initial Comment: Recently we encountered some crashes of kamailio 1.5.0 caused by messages with too big value of Content-length (more than 30000). When the parser in nathelper.c looks for old and new port it sometimes finds occurences after the real end of the message. Then the sanity check in del_lump() in data_lump.c finds that either offset or offset+len is greater than msg->len and calls abort(). ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 14:51 Message: It seems that the ERROR is not really a problem, and the crash happened on 1.5.3. ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 12:45 Message: I am afraid, this issue is not yet fixed. The latest release version (1.5.4-notls (i386/linux)) still produces: Mar 1 11:53:12 test02 /usr/sbin/kamailio[5173]: ERROR:core:anchor_lump: offset exceeds message size (1799 > 1783)... Mar 1 11:53:12 test02 /usr/sbin/kamailio[5173]: ERROR:nathelper:force_rtp_proxy: anchor_lump failed This is reproducible. I even experienced a crash: Feb 26 14:58:44 test02 /usr/sbin/kamailio[21020]: CRITICAL:core:del_lump: offset exceeds message size (1186 > 1132) aborting... To trigger this, one needs to send an invite with a content-length bigger than the actual content through force_rtp_proxy. ---------------------------------------------------------------------- Comment By: Daniel-Constantin Mierla (miconda) Date: 2009-10-05 08:54 Message: This should be fixed in 1.5.2 and latest svn, have you tried the latest 1.5 svn branch? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-07-08 17:17 Message: 'kamailio -V' says 'kamailio 1.5.0-notls (x86_64/linux)' ---------------------------------------------------------------------- Comment By: Klaus Darilion (klaus_darilion) Date: 2009-07-08 10:38 Message: Which excat version are you using? There were some bugfixes recently. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2818273&group_…

1 0

Project Update, London Meeting, March 9
by Daniel-Constantin Mierla 01 Mar '10

01 Mar '10

Hello, Tuesday, March 9, I am going to be in London and plan to organize a social networking event for folks around SIP/VoIP, Kamailio (OpenSER) & SIP Router. One is going to be the usual evening dinner/pub meeting, see pics from some past events: http://www.asipto.com/gallery/v/social_meeting_barcelona2008/ http://www.asipto.com/gallery/v/FOSDEM2009/ I addition, if there are people interested, I would like to have a session in the afternoon (2-3 hours) to give an update about Kamailio (OpenSER) 3.0, present and future development of SIP Router. Time is rather short, but I encourage attendees to prepare short presentations as well, about their products and services, to have more information exchanged there. Let me know if you wish to attend such event in order to find a proper place to host it (drop me an email). Participation is free for everybody, at the dinner, the classic rule, everyone is going to pay for himself/herself. Looking forward to meeting many of you in London. Cheers, Daniel -- Daniel-Constantin Mierla Kamailio SIP Router Masterclass, Berlin, March 22-26, 2010 * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[ openser-Bugs-2818273 ] crash when Content-length too big
by SourceForge.net 01 Mar '10

01 Mar '10

Bugs item #2818273, was opened at 2009-07-08 01:28 Message generated for change (Comment added) made by marcushunger You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2818273&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: ver 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: crash when Content-length too big Initial Comment: Recently we encountered some crashes of kamailio 1.5.0 caused by messages with too big value of Content-length (more than 30000). When the parser in nathelper.c looks for old and new port it sometimes finds occurences after the real end of the message. Then the sanity check in del_lump() in data_lump.c finds that either offset or offset+len is greater than msg->len and calls abort(). ---------------------------------------------------------------------- Comment By: Marcus Hunger (marcushunger) Date: 2010-03-01 12:45 Message: I am afraid, this issue is not yet fixed. The latest release version (1.5.4-notls (i386/linux)) still produces: Mar 1 11:53:12 test02 /usr/sbin/kamailio[5173]: ERROR:core:anchor_lump: offset exceeds message size (1799 > 1783)... Mar 1 11:53:12 test02 /usr/sbin/kamailio[5173]: ERROR:nathelper:force_rtp_proxy: anchor_lump failed This is reproducible. I even experienced a crash: Feb 26 14:58:44 test02 /usr/sbin/kamailio[21020]: CRITICAL:core:del_lump: offset exceeds message size (1186 > 1132) aborting... To trigger this, one needs to send an invite with a content-length bigger than the actual content through force_rtp_proxy. ---------------------------------------------------------------------- Comment By: Daniel-Constantin Mierla (miconda) Date: 2009-10-05 08:54 Message: This should be fixed in 1.5.2 and latest svn, have you tried the latest 1.5 svn branch? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-07-08 17:17 Message: 'kamailio -V' says 'kamailio 1.5.0-notls (x86_64/linux)' ---------------------------------------------------------------------- Comment By: Klaus Darilion (klaus_darilion) Date: 2009-07-08 10:38 Message: Which excat version are you using? There were some bugfixes recently. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=2818273&group_…

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2010