Juha Heinanen writes:
> Thanks. I don't think that this is db related issue. Here is a
> summary:
>
> - K receives INVITE at 17:43:28 and forwards it over udp to uas
> - uas immediately responds with 183 followed by 180, which k forwards to UAC
> - at 17:44:29 uas responds again with 180 and K
On 06.02.19 09:51, Juha Heinanen wrote:
> Juha Heinanen writes:
>
>> Thanks. I don't think that this is db related issue. Here is a
>> summary:
>>
>> - K receives INVITE at 17:43:28 and forwards it over udp to uas
>> - uas immediately responds with 183 followed by 180, which k forwards to UAC
>>
Daniel-Constantin Mierla writes:
> OK. There should be no crash no matter what caused the delay. I wanted
> to sort out the freezing of entire kamailio for 15min, because that is
> rather unusual to happen for all processes and then recover.
>
> I will look more at the tm for this delay/blocking
On 06/02/2019 01.55, Laurent Schweizer wrote:
Hello,
I’m using the RTPengine with Kamailio and I have a question for a
specific case.
I have some customer that are changing the source port of the RTP
stream during the call ( no re-invite) I think it’s more a NAT issue
that a user agent iss
I got the full syslog and pcap and based on those K indeed totally froze
for about 14 minutes. Below is updated summary:
- K receives INVITE at 17:43:28 and forwards it over udp to uas
- uas immediately responds with 183 followed by 180, which k forwards to UAC
- at 17:44:29 uas responds again wi
