10 Mar
2008
10 Mar
'08
5:16 p.m.
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:DB_PASS@DB_HOST/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(a)<ip.address>ss>: ended
(did timeout).
Is there a way to cleanly stop them too?
Kind regards,
Thomas Gelf
10 Mar
10 Mar
5:48 p.m.
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:DB_PASS@DB_HOST/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(a)<ip.address>ss>:
ended (did timeout).
Is there a way to cleanly stop them too?
Kind regards,
Thomas Gelf
6:57 p.m.
Hi Thomas,
Basically you cannot account the BYE requests - this is an
implementation limitation. Mainly because openser has to send a request
within a dialog, so it will follow the RR set and remote target values.
Also, currently, the local generated requests are totally
transparent/invisible for the routing script.
Regards,
Bogdan
Thomas Gelf wrote:
Thomas Gelf schrieb:
NB: Accounting of "killed" dialogs is
failing too - do I somehow need to
"catch" dlg_end_dlg in my config file?
> I had to comment out the following ones, as 1.3 (SVN rev 3864) ...
>
NBB: Same behaviour using SVN rev 3921
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
7:15 p.m.
Hi Thomas,
Thomas Gelf wrote:
This is related to your later quest - acc for BYE; more or less this is
the same case - no script route is used when the BYEs are generated, so
the mediaproxy is not properly stopped.
Regards,
Bogdan
Hi list,
I'm currently playing around with the dialog module. Current config:
The parameters exist, but they take an integer value (and not a string),
so drop the quotes from the values. For "default_timeout" there was a
documentation error which I just fixed.
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:DB_PASS@DB_HOST/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):
You should not worry about this - it is a side effect of a latest fix -
the dialog goes into DELETE state when first bye is sent out . The error
you see is when the second bye is sent.... it is only about logging, but
still needs to be fixed
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(a)<ip.address>ss>:
ended (did timeout).
Is there a way to cleanly stop them too?
Kind regards,
Thomas Gelf
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users
6103
days inactive
6104
days old
4 comments
2 participants
participants (2)
-
Bogdan-Andrei Iancu -
Thomas Gelf