Hello
I have been facing an issue where the dialog module is showing calls as being active when in fact the call has already been completed long ago and this is giving wrong number of concurrent calls on our SNMP work station (CACTI) when polling the data from Kamailio. I realized this only started occurring after i upgraded from 3.1.2 to 3.1.5, has anyone experienced the same issue?
my config: ========
loadmodule "dialog.so" . . . . # ----------------- DIALOG MODULE PARAMETERS----------------------------------# modparam("dialog", "enable_stats", 1) modparam("dialog", "hash_size", 4096) modparam("dialog", "rr_param", "did") modparam("dialog", "dlg_flag", 4) modparam("dialog", "timeout_avp", "$avp(i:10)") modparam("dialog", "dlg_extra_hdrs", "NULL") modparam("dialog", "dlg_match_mode", 1) modparam("dialog", "detect_spirals", 1) modparam("dialog", "db_url", "mysql://openser:openserrw@localhost/openser") modparam("dialog", "db_mode", 1) modparam("dialog", "db_update_period", 60) modparam("dialog", "db_fetch_rows", 500) modparam("dialog", "table_name", "dialog") modparam("dialog", "from_uri_column", "from_uri") modparam("dialog", "from_tag_column", "from_tag") modparam("dialog", "to_uri_column", "to_uri") modparam("dialog", "to_tag_column", "to_tag") modparam("dialog", "h_id_column", "hash_id") modparam("dialog", "h_entry_column", "hash_entry") modparam("dialog", "state_column", "state") modparam("dialog", "start_time_column", "start_time") modparam("dialog", "timeout_column", "timeout") modparam("dialog", "sflags_column", "sflags") modparam("dialog", "bridge_controller", "sip:controller@kamailio.org") modparam("dialog", "default_timeout", 7200)
. . . .
route {
# MANAGE ALL DIALOGS #=================================================== if (is_method("INVITE")) { if(is_method("INVITE") && !has_totag()) { $dlg_ctx(timeout_route) = 12; $dlg_ctx(timeout_bye) = 1; }
dlg_manage();
}
Thanks Phillip
Hey Phillip,
On 16.09.2011 13:35, Phillman25 Kyriacou wrote:
Hello
I have been facing an issue where the dialog module is showing calls as being active when in fact the call has already been completed long ago and this is giving wrong number of concurrent calls on our SNMP work station (CACTI) when polling the data from Kamailio. I realized this only started occurring after i upgraded from 3.1.2 to 3.1.5, has anyone experienced the same issue?
I was *just* being notified of issues concerning dialogs not being deleted. Working on this right now to report back soon.
Thanks for the note!
Cheers,
--Timo
Hi Timo
Thanks for the update!
Regards Phillip
On Fri, Sep 16, 2011 at 3:09 PM, Timo Reimann timo.reimann@1und1.de wrote:
Hey Phillip,
On 16.09.2011 13:35, Phillman25 Kyriacou wrote:
Hello
I have been facing an issue where the dialog module is showing calls as being active when in fact the call has already been completed long ago and this is giving wrong number of concurrent calls on our SNMP work station (CACTI) when polling the data from Kamailio. I realized this only started occurring after i upgraded from 3.1.2 to 3.1.5, has anyone experienced the same issue?
I was *just* being notified of issues concerning dialogs not being deleted. Working on this right now to report back soon.
Thanks for the note!
Cheers,
--Timo
Hey Phillip,
after looking closer at what has been reported to me initially, your case may be different after all.
Could you possibly use "kamctl fifo dlg_list" to check what state the majority of dialogs that should be terminated in your opinion are in? Being given the reference counter should be useful in debugging this as well.
Thanks,
--Timo
On 16.09.2011 14:22, Phillman25 Kyriacou wrote:
On Fri, Sep 16, 2011 at 3:09 PM, Timo Reimann <timo.reimann@1und1.de mailto:timo.reimann@1und1.de> wrote:
Hey Phillip, On 16.09.2011 13:35, Phillman25 Kyriacou wrote: > Hello > > I have been facing an issue where the dialog module is showing calls as > being active when in fact the call has already been completed long ago > and this is giving wrong number of concurrent calls on our SNMP work > station (CACTI) when polling the data from Kamailio. I realized this > only started occurring after i upgraded from 3.1.2 to 3.1.5, has anyone > experienced the same issue? I was *just* being notified of issues concerning dialogs not being deleted. Working on this right now to report back soon. Thanks for the note! Cheers, --Timo
-
Phillman25 Kyriacou -
Timo Reimann