Hello,
When we imported the code from both repositories into the common git
repository, we imported the full history of SER core and modules, as
well as the full history of all Kamailio modules and scripts/tools.
What we did not import is the full history of Kamailio core. We went
through Kamailio modules and selected directories one by one, but we
left the core file behind, which means that changes in Kamailio to
most core files are no accessible in the git repository history.
We put quite a bit of effort into importing everything properly,
including full history. And I wonder if we should perhaps also import
the history of Kamailio core, perhaps on a separate branch?
The history of Kamailio core would not be directly visible if one
types git log on the master branch, but it will be stored in the
repository in case someone needs to investigate it in the future.
Without that one would need to get back to the SVN repository and look
there. We also have the automatic git import of Kamailio SVN, but I
assume that we will stop that if there will be no more commits in the
SVN repository in the future.
-- Jan
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