Hello,
the problem is that 10.139.90.137 does not handle properly the OPTIONS.
The request is intended to it as it seems by R-URI:
OPTIONS sip:10.139.90.137:5060 SIP/2.0
But it is sent back to 192.168.1.5, which sends it back to .137 based on
r-uri (correctly).
So probably you have some mi
Hi,
We have an ugly message looping scenario where a SIP request message received
at Kamailio is forwarded to the switch/router and back to Kamailio in a loop
until the Max-forwards header value becomes 0 or the transaction times out.
After receiving an incoming INVITE request from a local us
