NB: Accounting of "killed" dialogs is failing too - do I somehow need to
"catch" dlg_end_dlg in my config file?
Thomas Gelf schrieb:
> Hi list,
>
> I'm currently playing around with the dialog module. Current config:
>
> > loadmodule "dialog.so"
> > modparam("dialog", "enable_stats", 1)
> > modparam("dialog", "hash_size", 4096)
> > modparam("dialog", "rr_param", "rdlg")
> > modparam("dialog", "dlg_flag", FLAG_DIALOG)
> > modparam("dialog", "dlg_match_mode", 1)
> > modparam("dialog", "db_url", "mysql://DB_USER:[EMAIL PROTECTED]/DB_NAME")
> > modparam("dialog", "db_mode", 1)
>
> I had to comment out the following ones, as 1.3 (SVN rev 3864) doesn't
> like them (as af http://www.openser.org/docs/modules/1.3.x/dialog.html
> thy should work):
>
> > #modparam("dialog", "default_timeout", "7200")
> > #modparam("dialog", "db_update_period", "60")
>
> However: if I end a dialog with (example):
>
> > openserctl fifo dlg_end_dlg 162 1311477520
>
> syslog is telling me:
>
> > ... CRITICAL:dialog:next_state_dlg: bogus event 7 in state 5
>
> Both BYE's are sent out correctly, and both clients answer them (OK).
> Is this "CRITICAL" thingy the normal behaviour? Or may there something
> be wrong with my config? I'm currently running
>
> > setflag(FLAG_DIALOG);
>
> for each INVITE request - DB entries are created / modified correctly.
>
> Mediaproxy sessions are not terminated, they time out after idling
> around for a while:
>
> > ... session 7bf33c00a5793790@<ip.address>: ended (did timeout).
>
> Is there a way to cleanly stop them too?
>
> Kind regards,
> Thomas Gelf
>
>
_______________________________________________
Users mailing list
Users@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
