Hey Timo <br><br>Thanks for your email.<br><br>Yes dlg_manage(); has to now be called on INVITE and BYE/CANCEL messages.<br>Where would i have to call loose_route()? Only on INVITE?<br>My configuration did not change between 3.1.2 and 3.1.5.<br>
<br>Call flow example:<br>==============<br><br>Cisco PGW ===> Kamailio 3.1.5 ===> VOIP PROVIDER or ASTERISK PABX<br><br><br>The below is my configuration.<br><br><br><br> # MANAGE ALL DIALOGS<br>
#=============================<div class="im">======================<br> if (is_method("INVITE"))<br> {<br> if(is_method("INVITE") && !has_totag())<br> {<br> $dlg_ctx(timeout_route) = 12;<br>
$dlg_ctx(timeout_bye) = 1;<br> }<br><br> dlg_manage();<br><br> }<br><br><br><br> <br></div> if(is_method("BYE|CANCEL"))<br><br> {<br> <br> dlg_manage();<br>
<br><br><br><br>Please let me know if you need anything else. <br><br>Thanks <br>Phillip<br><br><br><div class="gmail_quote">On Mon, Sep 19, 2011 at 11:47 AM, Timo Reimann <span dir="ltr"><<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hey Phillip,<br>
<br>
you probably forgot to keep the mailing list in CC, I'll do that for you.<br>
<div class="im"><br>
<br>
On 19.09.2011 08:43, Phillman25 Kyriacou wrote:<br>
> You are right.<br>
><br>
> I added the function dlg_manage(); when there is a BYE or CANCEL and now<br>
> its working perfectly. Before i had this function defined only on<br>
> INVITES. The strange thing is that it was working normally before when<br>
> dlg_manage(); was defined only for INVITE messages in the route block.<br>
<br>
</div>So you are saying that before, you called dlg_manage() on INVITEs only<br>
but now, you need that function on both INVITE and BYE/CANCEL messages?<br>
<br>
That'd still qualify as a bug as the trigger to tracking the dialog<br>
(i.e., dlg_manage()) is required only once. After that, the dialog<br>
module makes sure that all dialog-related messages are properly<br>
processed. The only thing that's necessary for sequential requests to be<br>
tracked correctly is a call to loose_route() on such messages.<br>
<br>
If you are sure that your Kamailio configuration didn't change between<br>
3.1.2 and 3.1.5 w.r.t. dialog tracking or anything that could affect it,<br>
I'd be willing to take a closer look at this issue (giving you can<br>
provide me with more information on your scenario, like call flow<br>
examples or similar).<br>
<br>
<br>
Cheers,<br>
<font color="#888888"><br>
--Timo<br>
</font><div class="im"><br>
<br>
<br>
> The calls that were suppose to be terminated before where in state 3 to<br>
> answer your question. However, i still see calls in state 3 now but they<br>
> are valid.<br>
><br>
> Regards<br>
> Phillip<br>
><br>
> On Fri, Sep 16, 2011 at 8:01 PM, Timo Reimann <<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a><br>
</div><div class="im">> <mailto:<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a>>> wrote:<br>
><br>
> Hey Phillip,<br>
><br>
> after looking closer at what has been reported to me initially, your<br>
> case may be different after all.<br>
><br>
> Could you possibly use "kamctl fifo dlg_list" to check what state the<br>
> majority of dialogs that should be terminated in your opinion are in?<br>
> Being given the reference counter should be useful in debugging this as<br>
> well.<br>
><br>
><br>
> Thanks,<br>
><br>
> --Timo<br>
><br>
><br>
><br>
> On 16.09.2011 14:22, Phillman25 Kyriacou wrote:<br>
> > On Fri, Sep 16, 2011 at 3:09 PM, Timo Reimann<br>
> <<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a> <mailto:<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a>><br>
</div><div><div></div><div class="h5">> > <mailto:<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a> <mailto:<a href="mailto:timo.reimann@1und1.de">timo.reimann@1und1.de</a>>>> wrote:<br>
> ><br>
> > Hey Phillip,<br>
> ><br>
> ><br>
> > On 16.09.2011 13:35, Phillman25 Kyriacou wrote:<br>
> > > Hello<br>
> > ><br>
> > > I have been facing an issue where the dialog module is showing<br>
> > calls as<br>
> > > being active when in fact the call has already been<br>
> completed long ago<br>
> > > and this is giving wrong number of concurrent calls on our<br>
> SNMP work<br>
> > > station (CACTI) when polling the data from Kamailio. I<br>
> realized this<br>
> > > only started occurring after i upgraded from 3.1.2 to 3.1.5, has<br>
> > anyone<br>
> > > experienced the same issue?<br>
> ><br>
> > I was *just* being notified of issues concerning dialogs not being<br>
> > deleted. Working on this right now to report back soon.<br>
> ><br>
> > Thanks for the note!<br>
> ><br>
> ><br>
> > Cheers,<br>
> ><br>
> > --Timo<br>
</div></div></blockquote></div><br>