lost module uses the standard header parsing function. `lost_get_from_header` is just a wrapper function to return a string pointer and uses `parse_headers`, which in your case returns an error. I did use the sipp example but had no header parsing issues, see below (OS: alpine:latest docker image) ``` 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: ### ESRP - INVITE request received Sock: tcp:172.16.16.176:38763 From: sip:sipp@127.0.0.1:2345 To: sip:service@127.0.0.1:5060 ### 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: INVITE urn:service:sos SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:2345;branch=z9hG4bK-7655-1-0 From: sipp <sip:sipp@127.0.0.1:2345>;tag=7655SIPpTag001 To: service <sip:service@127.0.0.1:5060> Call-ID: 1-7655(a)127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:2345 Max-Forwards: 70 Subject: Performance Test Content-Type: application/sdp Content-Length: 129 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 6000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 6(13) WARNING: {1 1 INVITE 1-7655(a)127.0.0.1} lost [functions.c:257]: lost_held_function(): P-A-I header not found, trying From header ... 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} lost [functions.c:271]: lost_held_function(): ### HELD id [sip:sipp@127.0.0.1:2345] 6(13) WARNING: {1 1 INVITE 1-7655(a)127.0.0.1} lost [functions.c:480]: lost_held_function(): locationRequest error response: [locationUnknown] 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: ### ESRP - held request failed 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: ### ESRP - held request returned err: locationUnknown 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: ### ESRP - service urn received 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: INVITE urn:service:sos SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:2345;branch=z9hG4bK-7655-1-0 From: sipp <sip:sipp@127.0.0.1:2345>;tag=7655SIPpTag001 To: service <sip:service@127.0.0.1:5060> Call-ID: 1-7655(a)127.0.0.1 CSeq: 1 INVITE Contact: sip:sipp@127.0.0.1:2345 Max-Forwards: 69 Subject: Performance Test Content-Type: application/sdp Content-Length: 129 v=0 o=user1 53655765 2353687637 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 6000 RTP/AVP 0 a=rtpmap:0 PCMU/8000 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} <script>: ### 6(13) INFO: {1 1 INVITE 1-7655(a)127.0.0.1} lost [functions.c:891]: lost_function(): ### LOST urn [urn:service:sos] 6(13) ERROR: {1 1 INVITE 1-7655(a)127.0.0.1} lost [functions.c:923]: lost_function(): geolocation header not found ``` -- 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/2723#issuecomment-830822660

Can you share the original xml file used with sipp? -- 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/2723#issuecomment-831197935

@wkampich original XML file located here http://sipp.sourceforge.net/doc/uac.xml.html RAW format http://sipp.sourceforge.net/doc/uac.xml -- 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/2723#issuecomment-831369964

Yes, I call `lost_held_query` at the start of routing. This describes by not all headers parsed. What is connect solution here? -- 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/2723#issuecomment-831488165

This not help and errors still present. -- 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/2723#issuecomment-831886860

@wkampich: why not using the `parse_from_header()` like I suggested in my previous commit here instead of doing the commit fe6923cd8e995c400fc1838304c95142cc00273e? You try to reimplement `parse_from_header()`. The From header must be only one time in the sip message, parse_to() may be changed in the future, adding complexity to maintenance of the code, ... Unless there is a clear reason to do it like in fe6923cd8e995c400fc1838304c95142cc00273e, it should be reverted and use the `parse_from_header()`. -- 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/2723#issuecomment-832421098

`parse_headers()` is mainly breaking in `header name` and `header body`, not doing deep parsing of `header body` part for most of the headers, but only for a few. To get the From header body parsed, you have to use `parse_from_header()`, not parse it internally using parse_to(). You can still use `parse_headers(msg, HDR_EOH_F, 0)` to locate other headers, just do not expect to do deep parsing of every header, there are dedicated functions that have to be used (e.g., for Contact, Route, ...). -- 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/2723#issuecomment-832469992

I guess this can be closed. @sergey-safarov: as you seem to make many testing scenarios with sipp to reproduce issues/test features, maybe you can contribute them as units in the kamailio-tests repo: * https://github.com/kamailio/kamailio-tests Can be useful to detect regressions/changes in behaviour. -- 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/2723#issuecomment-833254558

@sergey-safarov closing this one, being aged. If you have time for a test case in the near future, just push it to repo https://github.com/kamailio/kamailio-tests . -- 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/2723#issuecomment-851635600