Hello,
append_to_reply() adds the header to the replies generated by Kamailio.
A request that is generated by UA after a 3xx does not have to preserve
any header received in 3xx, it is a completely new request, the previous
one failed. If you handle the 3xx in Kamailio, you can get the headers
of
According to a packet capture, changing append_hf() to
append_to_reply() affected a 302 message that Kamailio is forwarding
to sending to itself, but the subsequent INVITE did not keep the
header. What am I missing?
On Mon, Mar 11, 2024 at 7:28 AM Ben Kaufman via sr-users
wrote:
>
> There's also
Hi there!
I conducted some tests on the new Kamailio 5.7.3 and unfortunately, the
problem still exists.
Specifically, the problem lies in the fact that the data in the
*active_watchers* table and the *record_route* field are only updated with
initial Record-Route sets, and ignores any routing set
Hi all
I've set up a kamailio server on a public IP address to serve public clients.
- The clients REGISTER over a mix of TCP and TLS, so kamailio has
listeners on the same IP address: port 5060 for UDP/TCP and port 5061
for TLS.
- Some clients REGISTER from the same public IP address, behind the
