Thank you for your reply, please find the debug log attached to this message. parse_rr error happens first at line 5287 note that the same configuration, without topos, works like a charm [topos-debug.txt](https://github.com/kamailio/kamailio/files/371745/topos-de… --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/716#issuecomment-233660986

After more debugging, it seems that the Route header is not well regenerated from topos stored values. There is a wrong additional comma at the end of the `Route` header: `<sip:A.A.35.90;r2=on;lr;ftag=SD9pnva01-8c51e3a9-0001-0313-0000-0000>,` Instead of `<sip:A.A.35.90;r2=on;lr;ftag=SD9pnva01-8c51e3a9-0001-0313-0000-0000>` I tried to reduce sb size by replacing last character with \0, that makes it work `*(sb.s-1)='\0';` between these two lines ``` 638 sb.len++; 639 } ``` but leads, sometimes, to segmentation faults... There is probably another way to achieve a correct header regeneration, but i don't know how. Please let me know if i can give you more informations --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/716#issuecomment-236642671

You're welcome. After more tries, the segmentation faults don't seem to be related to my patch as : - the segmentation occurs between the database locks release and the "tps_reappend_route" function and simply adding a sleep between database locks releases and it solved (partially) my issue. - more children i use more often the segmentation occurs, and, on the contrary, less threads i use, less often the segmentation occurs - even with removing my patch if i start kamailio with, for example, more than 10 children, children dies and so kamailio exits. So, it seems the problem is more database locking/releasing related, but that would mean very complicated debugging... i would be unable to do. Maybe you have more ideas i have... let me know if you need more informations, you would probably be able to reproduce the issue has it only requires to add more children to kamailio process. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/716#issuecomment-237043962

Thank you, i'll try your patch. For the coredump, i tried to use gdb but it didn't help as kamailio exists normally... The only informations i have at "crash" are the textual information about threads memory status at "crash" moment. I'll send you these informations, you'll see what i mean... --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/716#issuecomment-237773062

OK, thanks for testing and reporting back. Open a new item when you get the segfault. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/716#issuecomment-238555854