On 28/10/15 15:49, Alessio Casco wrote:
> Hello!
>
> Thanks to @cezar91 we finally spot the issue, basically kamailio it's
> transforming t_code=0 (timeout) to 408 and the dispatcher module sees
> this last value.
>
> Oct 28 14:16:32 net21-test /usr/sbin/kamailio[31911]: DEBUG: tm
> [t_reply.c:13
Hello!
Thanks to @cezar91 we finally spot the issue, basically kamailio it's
transforming t_code=0 (timeout) to 408 and the dispatcher module sees this
last value.
Oct 28 14:16:32 net21-test /usr/sbin/kamailio[31911]: DEBUG: tm
[t_reply.c:1311]: t_should_relay_response(): -> T_code=0,
new
Hello,
can you want the network traffic and see if the OPTIONS requests are
sent out?
Cheers,
Daniel
On 27/10/15 18:59, Alessio Casco wrote:
> Hello Daniel!
>
> Adding the sock_avp parameter, fixes the error on the log, but the
> behaviour is the same as before.
>
>
> As you can see, with nothin
Hello Daniel!
Adding the sock_avp parameter, fixes the error on the log, but the
behaviour is the same as before.
As you can see, with nothing listening on those two servers, the
loadbalancing it's still disables.
SET: {
ID: 3
TARGETS: {
DEST: {
URI: sip:media22-test.internal:5060
FLAGS: AP
PR
Hello,
it looks like sock_avp parameter has to be set -- it is there before
4.3.0 release, as I could spot in 'git blame' for dispatcher.c:768.
Not sure is really needed for failover, I will check its usage when I
get first chance.
http://kamailio.org/docs/modules/stable/modules/dispatcher.html#
