Re: [SR-Users] no socket found for match second RR

On 9/21/12 11:37 AM, Juha Heinanen wrote:

Daniel-Constantin Mierla writes:

...

If there will be no transport layer bridging, so no double record routing, all should go fine. Actually all should go fine anyway, just a warning message is printed because loose routing is expecting a local socket on double Route headers.

daniel,

yes, everything works fine, it is just that warning that i would like to get rid of. is it ok to change it to debug? or perhaps loose_route could have a param that tells it to skip the socket test?

the second is better in this case, because will avoid a loop through local sockets. Also, your case is very rare, the warning is good to spot if someone changed the uri in route headers.

Cheers, Daniel