Hello,
Make sure you also do the following:
- loadmodule "event_route.so", in order to have the events raised to the
route (I agree, user experience can be improved here, as this could be
automatically done, or made to throw a startup error)
- fetch your params before printing them, with "fetch_event_params".
More info in the event interface tutorial [1]
[1]: http://www.opensips.org/Documentation/Tutorials-EventInterface
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 06.03.2016 19:28, Admin wrote:
Hi all,
I want to track dialog state change using event_route but i am not
getting anything in the log file. The way i understand it is when the
dialog state changes, the event E_DLG_STATE_CHANGED is triggered, and
putting that in the event_route block, i should see it but it's not
showing in the log file.
What am i missing? Thank you.
event_route[E_DLG_STATE_CHANGED] {
xlog("Dialog state changed\n");
}
I am running opensips 2.1.2 on debian 8 64bit.
=========================================================
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 14400) # 4 hours timeout
modparam("dialog", "db_mode", 1)
modparam("dialog", "db_update_period", 60)
modparam("dialog", "db_url",
"mysql://opensips:opensipsrw@localhost/opensips") # CUSTOMIZE ME
# create dialog with timeout
if ( !create_dialog("B") ) {
send_reply("500","Internal Server Error");
exit;
}
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
