Daniel,
Just to make sure: did you try to define the "listen" parameters
explicitly? The problem happens only when the "listen" parameters are
defined in the Kamailio configuration. When the "listens" are not
configured then everything works correctly.
So, the problem happens when it is necessary
Hello,
I tried to reproduce a while ago on a system with many network
interfaces, but all was fine. I guess it has to do with network/ip
routing configuration there.
Open the issue, maybe other people will give some input based on their
experience.
Cheers,
Daniel
On 14.08.19 13:37, Leonid
Hello Daniel,
Should I open a bug regarding this issue?
Thank you,
Leonid
On Sun, Jul 21, 2019 at 1:26 PM Leonid Fainshtein <
leonid.fainsht...@xorcom.com> wrote:
> Hello Daniel,
> The traces and the simplified config file can be downloaded by using the
> link below:
>
>
Hello Daniel,
The traces and the simplified config file can be downloaded by using the
link below:
http://updates.xorcom.com/~xorcom/2019-jul-21.tar.gz
Regarding to an IP route from the local IP appearing in Record-Route to the
target IP. I don't have a special route for it. But the
Can you load debugger module and enable cfgtrace to see the actions
executed in config file for such INVITE - reproduce and send the log
messages. Might be an effect of something done there.
Did I asked if you have IP route from the local IP appearing in
Record-Route to the target IP address?
Yes, I have.
Best regards,
Leonid Fainshtein
Xorcom Ltd
On Thu, Jul 18, 2019 at 9:31 AM Daniel-Constantin Mierla
wrote:
> Hello,
> traveling, so not much time available ...
> I looked over the logs when expected socket is not used, I couldn't spot
> any message about selecting the socket, so
Hello,
traveling, so not much time available ...
I looked over the logs when expected socket is not used, I couldn't spot
any message about selecting the socket, so there is a route from them
"wrong" socket to the destination.
Do you have "mhomed=1" in kamailio.cfg?
Cheers,
Daniel
On Wed, Jul
Dear Daniel,
Did you have a chance to check the traces?
Best regards,
Leonid
On Wed, Jul 10, 2019 at 9:15 AM Leonid Fainshtein <
leonid.fainsht...@xorcom.com> wrote:
> Hello Daniel,
> The requested traces can be downloaded by using the link below:
>
>
Hello Daniel,
The requested traces can be downloaded by using the link below:
http://updates.xorcom.com/~xorcom/kam-tcp-problem.tar.gz
I don't use the force send socket option and doesn't route out via
dispatcher in this particular call flow.
I found that the problem happens only when the
Hello,
set debug = 3 in kamailio cfg and reproduce this case. Send here all the
log messages printed by kamailio from the moment it receives the request
till it sends it out.
Some further questions:
- do you use any force send socket option?
- do you route out via dispatcher? If yes, is the
Hello,
The source address is correct: 192.168.0.31. I see it in tcpdump and
also in sngrep.
Thank you,
Leonid
On Mon, Jul 8, 2019 at 9:02 PM Daniel-Constantin Mierla
wrote:
>
> Hello,
>
> when you look at the network traffic 9e.g., with ngrep, sngrep, ...)
> what is shown as source address for
Hello,
when you look at the network traffic 9e.g., with ngrep, sngrep, ...)
what is shown as source address for outbound leg?
Cheers,
Daniel
On 08.07.19 19:21, Leonid Fainshtein wrote:
> I just found Daniel's response to a similar question (ref.:
>
I just found Daniel's response to a similar question (ref.:
https://lists.kamailio.org/pipermail/sr-users/2019-February/104853.html):
"check the routing rules/table of the operating systems, there should be
some differences between the two servers.
If you mhomed=1 and an unexpected interface is
13 matches
Mail list logo
