When one runs fix_nated_contact() from the nathelper module for it's intended purpose (it must complete successfully) and then run encode_contact() from the siputils module (it also must complete) Kamailio always core-dumps with: CRITICAL:core:del_lump: offset exceeds message size (202688 > 602) aborting...
I'm guessing this has something to do with re-writing the contact header twice and not fixing the message size the second time but I can't say for sure.
I have a core file, but it seems rather large (44M). It can be uploaded if need be. This is occurring with both the release 1.5.2tls & 1.6.0notls dev trunk.
I posted this bug to the SourceForge Bug Tracker - if this is the wrong list for bug reports on 1.5/1.6 let me know. If this should be put into a different bug tracker, I can do that as well.
Regards, Nicholas Lemberger Lakefield Communications
Hi!
Probably this wont work due to the lump processing limitations in Kamailio. (nevertheless K should not crash).
In sip-router there is new function called msg_apply_changes() http://sip-router.org/docbook/sip-router/branch/master/modules_k/textops/tex...
Which could be called between the two contact modifications.
Anyway - your solution might cause problems with some clients (e.g. some clients use a ;line=foo parameter to identifiy the registration) as it changes the URI which will be received by the SIP client.
If the registrar is Kamailio too, you better use the PATH module.
regards klaus
Nick Lemberger schrieb:
When one runs fix_nated_contact() from the nathelper module for it's intended purpose (it must complete successfully) and then run encode_contact() from the siputils module (it also must complete) Kamailio always core-dumps with: CRITICAL:core:del_lump: offset exceeds message size (202688 > 602) aborting...
I'm guessing this has something to do with re-writing the contact header twice and not fixing the message size the second time but I can't say for sure.
I have a core file, but it seems rather large (44M). It can be uploaded if need be. This is occurring with both the release 1.5.2tls & 1.6.0notls dev trunk.
I posted this bug to the SourceForge Bug Tracker - if this is the wrong list for bug reports on 1.5/1.6 let me know. If this should be put into a different bug tracker, I can do that as well.
Regards, Nicholas Lemberger Lakefield Communications
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Klaus Darilion -
Nick Lemberger