Set debug=4 and watch the logfile while receiving the ACK. If you do not
see any log messages then the ACK is not received by Kamailio (maybe
some local iptables/connection tracker problem)
regards
Klaus
On 10.05.2012 08:59, Mino Haluz wrote:
We are troubleshooting this issue almost for 2 day
Actually, sorry I misread your capture - it is using the same address so
doubt it the problem of interfaces..
Are you are not getting any logging in debug when the ACK comes in?
On Thu, May 10, 2012 at 9:08 AM, Jason Penton wrote:
> Hey Mino,
>
> From your packet captures above it looks like
Hey Mino,
>From your packet captures above it looks like your ACK is coming in another
IP address. I also see that you are doing the packet capture across all
your physical interfaces (-i any). Perhaps your Kamailio is only configured
to listen on the one interface (the one *not* getting the ACK).
We are troubleshooting this issue almost for 2 days and we did not find the
solution yet. The thing is, that it does not enter even the config file (we
have some debug messages at the start, that do not show). Otherwise we do
not have any problem with ACK, but only this particular ACK is not
forwar
Seems like a loose routing issue. Are you loose routing in your config file?
On Wed, May 9, 2012 at 4:34 PM, Stoyan Mihaylov wrote:
> You can use something like wireshark on Kamailio server to see if ACK
> packets go in right direction.
> I had problem with ACK and BYE, and I saw that in some ca
You can use something like wireshark on Kamailio server to see if ACK
packets go in right direction.
I had problem with ACK and BYE, and I saw that in some cases ACK and BYE
packets looped back in kamailio.
May be I used wrong client.
On Wed, May 9, 2012 at 5:15 PM, Efelin Novak wrote:
> Hi folk
Hi folks,
I have a strange problem when Kamailio ignores ACKs in a specific
scenario. The call flow is as follows:
A -> INVITE -> kamailio -> INVITE -> B
[omitting 100 and 180]
A <- 200 OK <- kamailio <- 200 OK <- B
A -> ACK -> kamailio
There are INVITE Xlogs, Reply ROUTE xlogs and media-proxy l
