Daniel. Hi. Thanks for your answer. Yes, could it be like you mention. I’m copying part of my event-route : route { …. $sht(b=>$ci::check)=0; .. } event_route[tm:local-request] { xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Routing locally generated $rm to <$ru>"); if (is_method("BYE") && $sht(b=>$ci::check)==0) { $var(dur)=$Ts-$dlg(start_ts); xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Tiempo inicial: $(dlg(start_ts){s.ftime,%a %b %d %H:%M:%S %Y})"); xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Tiempo final: $Tf"); xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Duracion: $var(dur)"); } if($sht(b=>$ci::timeout)==0){ xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Append Hint: call too long"); append_hf("Hint: Call too long\r\n"); }else{ xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Append Hint: credit expired"); append_hf("Hint: credit expired\r\n"); } if($sht(b=>$ci::check)==1){ xlog("L_INFO", "[$ci] [LOCAL REQUEST] :: Remove hash"); sht_rm_name_re("b=>$ci::timeout"); sht_rm_name_re("b=>$ci::check"); } else { $sht(b=>$ci::check)=1; } } As you said, we have two BYEs when the timeout expires, for the first one, we print some debug with initial and final times for the call, and then for the second we try to avoid this debug information, so we have a variable “check” to do this. So, if you think this is a WARNING message causing no problem, that is ok for us. Beside this the call goes fine. Regards, Ricardo *De:* Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Enviado el:* viernes, 21 de septiembre de 2012 4:43 *Para:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List *CC:* Ricardo Martinez *Asunto:* Re: [SR-Users] Dialog Module : "inconsitent dlg timer data" Hello, that message is printed when the 200ok for a self-generated BYE is received. Since there are two BYEs and the 200ok responses came at the same time, it might be a race to remove the dialog from timer list, which should be safe if the dialog is already removed. Perhaps this warning should be printed just as debug message or try to synchronize for this operation. I will analyze a bit more and see the best option. But otherwise, apart of the warning message, all goes fine, right? Cheers, Daniel On 9/20/12 11:48 PM, Ricardo Martinez wrote: Hello. Can someone explain to me why i’m getting this error : WARNING: dialog [dlg_req_within.c:173]: inconsitent dlg timer data on dlg 0xb565c500 [2166:2082643875] with clid ' 5ed68b60-fdbe-4aa7-819e-0002a400e27c(a)64.76.155.86&#39; and tags '5e604a9ea4' 'ed505c1da4' This is the output for dlg_list_ctx kamctl fifo dlg_list_ctx dialog:: hash=2995:55475986 state:: 4 ref_count:: 2 timestart:: 1348177242 timeout:: 15084496 callid:: 33d68b60-a09a-b1dc-8198-0002a400e27c(a)64.76.155.86 from_uri:: sip:557100050994@64.76.155.86 from_tag:: 3360b198a4 caller_contact:: sip:557100050994@64.76.155.86 caller_cseq:: 226 caller_route_set:: caller_bind_addr:: udp:64.76.155.82:5060 callee_bind_addr:: udp:64.76.155.82:5060 to_uri:: sip:0267005622408596@64.76.155.82 to_tag:: ba507815a4 callee_contact:: sip:0267005622408596@64.76.155.130 callee_cseq:: 226 callee_route_set:: context:: I can’t find the problem. I’m using this dialog params : # ---- dialog params ------ modparam("dialog", "dlg_flag", 31) modparam("dialog", "profiles_with_value","gwid" ) modparam("dialog", "default_timeout",7200) modparam("dialog", "timeout_avp", "$avp(i:10)") modparam("dialog", "dlg_match_mode", 1) $avp(i:10)=10 $dlg_ctx(timeout_bye) = 4; dlg_manage(); Regards, Ricardo _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu