Re: [SR-Users] no corresponding socket found for

2018-04-10 Thread Kjeld Flarup
Hi Daniel I was actually using kamailio:5069 lookup() => 12345678@kamailio:5070 forward() => kamailio:5071 t_relay()     u1@kamailio:5070 (404) I thus tried to change forward() to t_relay(), but then I found that the call was cancelled. Removing all 404 reply

Re: [SR-Users] no corresponding socket found for

2018-04-10 Thread Daniel-Constantin Mierla
Looks like the socket used for sending out is the loopback address and thus cannot send to 192.168.2.101. Do you use t_relay() for forwarding the request? Cheers, Daniel On 10.04.18 10:08, Kjeld Flarup wrote: > Listening is configured like this: > > #!define LOCALIP 192.168.2.9 >

Re: [SR-Users] no corresponding socket found for

2018-04-10 Thread Kjeld Flarup
Listening is configured like this: #!define LOCALIP 192.168.2.9 #!subst "/LOCALIP/192.168.2.9/g" listen=127.0.0.1:5069 listen=LOCALIP:5069 Kjeld 2018-04-10 9:43 GMT+02:00 Daniel-Constantin Mierla : > Hello, > > is the instance throwing the error listening only on 127.0.0.1

Re: [SR-Users] no corresponding socket found for

2018-04-10 Thread Daniel-Constantin Mierla
Hello, is the instance throwing the error listening only on 127.0.0.1 address? Cheers, Daniel On 09.04.18 23:54, Kjeld Flarup wrote: > > Hi > > I have a setup with three kamailio's in the same host but on different > ports. client ->5069 -> 5070 -> 5071 -> SIP provider > > Now I get this error