tested config

listen=udp:127.0.0.1:5060
loadmodule "xlog.so"
loadmodule "pv.so"
loadmodule "http_client.so"
loadmodule "lost.so"
loadmodule "textopsx.so"

modparam("lost", "exact_type", 1)
modparam("lost", "post_request", 1)
modparam("http_client", "httpcon", "lostsrv=>http://api.example.com/api/lost");


request_route {
  $var(res) = lost_query("lostsrv", "$var(uri)", "$var(name)", "$var(err)");
  xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $var(name)\n");
}

Test with one Geolocation header.
LOST request send with HTTP headers like

POST /api/lost HTTP/1.1
Host: api.example.com
User-Agent: kamailio (5.5.0-pre0 (x86_64/linux))
Accept: */*
Content-Type: application/lost+xml;charset=utf-8
Content-Length: 526

Here may be updated

Accept: application/lost+xml

@sergey-safarov: that looks like another http_client API fix as the API call does not support to set a specific header.

Also in Kamailio console, I can see this error message when Geolocation passed as a value

 1(82) ERROR: <core> [core/parser/parse_body.c:510]: part_multipart_headers_cmp(): error code: "-9" error text: "We reached the end of the buffer".

Looks as here here "ERROR" level misslead.
My test SIPp script attached.

test_call.xml.gz

The script may be started using the command

sipp -m 1 -sf test_call.xml -p 2345 127.0.0.1

@sergey-safarov: I see the same ERROR, but I suspect it is more of a WARNING

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.