Welcome!
On the other hand, I don't recall any significant change on this part of
code between 4.2 and current devel (4.4), but I didn't look at the
commit history right now ...
Cheers,
Daniel
On 27/01/16 15:00, david wrote:
> ok thanks Daniel
>
> i was quite confused by seeing different things
ok thanks Daniel
i was quite confused by seeing different things on different versions
(which had sligthly configuration differences) and i though i was doing
something wrong somewhere
best regards
david
El mié, 27-01-2016 a las 14:55 +0100, Daniel-Constantin Mierla escribió:
> Hello,
>
> yes
Hello,
yes, quick connect message is ok. It is an INFO level, messages to worry
about start at level WARNING, ERROR or lower.
Cheers,
Daniel
On 27/01/16 12:41, david wrote:
> hello Daniel
>
> thanks for the explanation.
> then i understand the "quick connect" message is also normal? seen in
> v
hello Daniel
thanks for the explanation.
then i understand the "quick connect" message is also normal? seen in
version 4.2.2 or 4.4?
best regards
david
El mar, 26-01-2016 a las 12:45 +0100, Daniel-Constantin Mierla escribió:
> Hello,
>
> the pending write message is due to asynchronous tcp -
Hello,
the pending write message is due to asynchronous tcp -- practically,
even if the tcp connection is not ready, the SIP routing process is not
blocked.
If the connection is found or the connection was setup quickly, then is
not a risk of blocking and the message is sent immediately.
I guess
hello all
i'm facing some weird log from kamailio (i think they are weird) when
using sip tcp in the caller side and udp in the callee side.
seems like the tcp socket is active in the caller side and the call is
connected, since the invite transaction completes.
After that, if we receive an in-di
