Re: [SR-Users] How to statelessly send a reply to custom destination?

2019-07-05 Thread Daniel-Constantin Mierla
Hello, if you want to send the reply to the source ip/port, not the address in the top Via header, then do: force_rport(); sl_send_reply(...); Cheers, Daniel On 05.07.19 10:27, George Diamantopoulos wrote: > Thank you for the reply Karsten! > > I'm afraid the options_reply() function won't wor

Re: [SR-Users] How to statelessly send a reply to custom destination?

2019-07-05 Thread George Diamantopoulos
Thank you for the reply Karsten! I'm afraid the options_reply() function won't work for me. The reason is that it seems to only handle OPTIONS where the RURI username is not set, and in my case I need to be able to handle these cases. Moreover, it is not evident from the siputils module documenta

Re: [SR-Users] How to statelessly send a reply to custom destination?

2019-07-04 Thread Karsten Horsmann
Hi George, i use something like that (shameless stolen from other configuration files within request-route). Thats for answering options to my internal kamailio. But Alex Balashov wrote an nice blog poste about NAT/OPTION Pings with kamailio: http://www.evaristesys.com/blog/server-side-nat-traver

[SR-Users] How to statelessly send a reply to custom destination?

2019-07-04 Thread George Diamantopoulos
Hello all, I've been trying to handle OPTIONS statelessly, but proper handling fails for UACs behind NAT without ALG. I thought I'd overcome this by setting the $du pseudovariable, but apparently I'm missing something. The following does not work: if ($Rp == "6050") { force_se