On 15/04/15 15:42, Mickael Marrache wrote:

It looks like it is a real issue since CDRs are not generated on dialog timeout.

If the dialog is not in the timer list, does that mean the DLGCB_EXPIRED callbacks are not called?

The log message is not related. It pure about trying to see if the dialog is still in the timer list and remove it, failing because it was already removed -- it will not get to that state if it was not in the timer already.

Daniel

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla
Sent: Wednesday, April 15, 2015 3:22 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Inconsistent dlg timer data warning at dialog timeout

Hello,

On 15/04/15 14:04, Mickael Marrache wrote:

Hi,

I get the following warning when a dialog timeout occurs:

kamailio[18889]: WARNING: dialog [dlg_req_within.c:214]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7f422986e448 [3547:6673] with clid 'mycvJWgmbmOSD5XQrcStKAKoTfW12XeR' and tags 'C5mlsaZCdTmybNSYgvWr75MBxWa5hVyA' 'L1ZzszpZ1MYO6qlQQ3FYYRWQYtF4F75r'

Am I doing something wrong?

do you get it always when a dialog times out?

The warning is for the case when the dialog is no longer on timer list, which can happen when there are two BYEs crossing through. The situation is harmless, perhaps the log message has to be done as info not warning.

Cheers,
Daniel
-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com