Hmm, now I run SER with debug=4 and grep'ed "DBG:acc" and the following
messages appear during doing a call accounting is activated for:
DBG:acc:acc_onreq: noisy_timer set for accounting
DBG:acc:acc_onreq: detected an UPSTREAM req -> flaging it
DBG:acc:core2strar: the flag UPSTREAM is set -> swap F/T
So detect_direction seems to work and tries to swap the from and to fields...
but in the acc db-table the columns from_uri and to_uri still get set wrong.
My db_extra configuration is still like this:
modparam("acc", "db_extra", "from_uri=$fu; to_uri=$tu);
Any idea what's wrong?
Robert.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Robert Borz
Sent: Monday, January 26, 2009 2:18 PM
To: [email protected]
Subject: [OpenSIPS-Users] acc-Module DB-Accounting
After solving my first issues, I'm now trying to setup db-accounting in SER. If
this works I will upgrade my configuration to work with FreeRADIUS.
So I added the acc module like this:
loadmodule "acc.so"
modparam("acc", "detect_direction", 1)
modparam("acc", "db_url", "postgres://openser:[email protected]/openser")
modparam("acc", "db_flag", 1)
modparam("acc", "db_missed_flag", 2)
modparam("acc", "db_extra", "from_uri=$fu; to_uri=$tu")
modparam("acc", "radius_config", "/etc/radiusclient-ng/radiusclient.conf")
modparam("acc", "log_flag", 1)
modparam("acc", "log_missed_flag", 2)
It doesn't matter if I set the detect_direction parameter to 0 or 1, the STOP
record always will have the uri of the guy hanging up the call.
Does the detect_direction only affect radius accounting or should I use other
pseudo variables for my db_extra configuration? Although... $fu and $tu are
looking very appropriate to me.
Thanks a lot!
Robert.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
