[sr-dev] Re: [kamailio/kamailio] no corresponding socket found error (Issue #3583)

2023-11-30 Thread github-actions[bot] via sr-dev
Closed #3583 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#event-6747962 You are receiving this because you are subscribed to this thread. Message ID: ___ Kamailio (SER) -

[sr-dev] Re: [kamailio/kamailio] no corresponding socket found error (Issue #3583)

2023-11-16 Thread github-actions[bot] via sr-dev
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1815661344 You are receiving this because

[sr-dev] Re: [kamailio/kamailio] no corresponding socket found error (Issue #3583)

2023-10-05 Thread descartin via sr-dev
hello all I tried to set the machine default route to 87.1.1.1 but I still got messages of that kind I also tried to add force socket on cancel requests before the t_relay(), since I saw that maybe when the error generated was when we have a CANCEL request which seemed to not be processed the

[sr-dev] Re: [kamailio/kamailio] no corresponding socket found error (Issue #3583)

2023-09-27 Thread sergey-safarov via sr-dev
We have observed such messages when the default route via the network interface does not match to socket listened by Kamailio. Probable you need to output the socket you want to use for outbound message. -- Reply to this email directly or view it on GitHub:

[sr-dev] Re: [kamailio/kamailio] no corresponding socket found error (Issue #3583)

2023-09-26 Thread Daniel-Constantin Mierla via sr-dev
Can it be that the responses were delayed and the corresponding transaction didn't exist anymore? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3583#issuecomment-1735363255 You are receiving this because you are subscribed to this thread.