@miconda, the problem with sip-message validation can be get round by using this strange
configuration and http-request:
```
event_route[xhttp:request] {
**$ru = "sip:1@127.0.0.1";**
async_route("TEST", "2");
}
route[TEST] {
xhttp_reply("200", "OK", "text/plain", "URL
$hu\r\n");
exit;
}
```
```
# cat ./test.sh
curl -X POST
http://192.168.3.115:8080/test \
-H "Content-Type: application/json" \
**-H "From: <sip:1@127.0.0.1>" \
-H "To: <sip:2@127.0.0.1>" \
-H "CSeq: 1 POST" \
-H "Call-ID: qwerty" \**
-d '{"test": 1}
```
You need to rewrite R-URI and add fields From, To, CSeq and Call-ID to prevent package
validation. I think, correction R-RURI and adding the required headers must be done when
creating fake_msg. What do you think?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3720#issuecomment-1902110831
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3720/1902110831(a)github.com>