‎Why are you using the dialog start/end hooks? They work well for standard scenarios clearly understood by the dialog module. For nonstandard scenarios, use the TM local-request route to catch and log endogenously generated BYEs.

--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Sent from my BlackBerry.
From: Mickael Marrache
Sent: Wednesday, April 15, 2015 10:28
To: sr-users@lists.sip-router.org
Reply To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] No CDR is written when dialog timeouts

I'm looking at the dlg_ontimeout function [dlg_handlers.c:1369] and I understand the code, the DLGCB_EXPIRED callbacks are not called when the send_bye parameter is set to 1.

 

I'm looking at the block 1399-1408.

 

From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Wednesday, April 15, 2015 3:53 PM
To: sr-users@lists.sip-router.org
Subject: RE: No CDR is written when dialog timeouts

 

I also confirm the cdr_on_create() [acc_cdr.c:718] function is called since I can see the debug statement "dialog '%p' created!".

 

From: Mickael Marrache [mailto:mickaelmarrache@gmail.com]
Sent: Wednesday, April 15, 2015 3:48 PM
To: sr-users@lists.sip-router.org
Subject: No CDR is written when dialog timeouts

 

Hi,

 

I'm testing the dialog timeout scenario and I see that no CDR is written.

 

This is my configuration:

 

modparam("acc", "cdr_enable", 1)

modparam("acc", "cdr_expired_dlg_enable", 1)

modparam("acc", "cdr_start_on_confirmed", 1)

modparam("acc", "cdr_log_enable", 0)

modparam("acc", "cdr_on_failed", 0)

 

I can confirm the cdr_on_expired() [acc_cdr.c:684] function is not called since I don't see the debug statement "dialog '%p' expired!\n".

 

(I precise that CDR generation works fine for regular hangup scenario.)

 

Any idea what can cause the issue?

 

Thanks,

Mickael