Daniel-Constantin Mierla writes: > It seems to be the case of a retransmission timeout: > > #17 0x00007f7dc04d4aca in acc_onreply (t=0x7f7d9e3b0650, req=0x7f7d9e357650, > reply=0xffffffffffffffff, code=408) at acc_logic.c:604 > > Code is 408 and the reply is faked value. This case is happening in > timer process.
That explains it. But isn't it risky that in this kind of situation the timer process (the only one) handles the reply and accounting? The problem is related to db_cluster/mariadb/debian. If db_cluster is not used, everything works fine. With db_cluster, accounting hangs the timer process at regular (about 2 hour) intervals. -- Juha _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
