22 Jun
2004
22 Jun
'04
6:23 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
HI again,
the log_flag will report on your syslog
the db_flag on your mysql.
I suppose your problem with log a successful call is because your ser didn't
receive the BYE message or I'm wrong?
If this is the problem... you must use a record_route() function to force BYE
messages come to your server.
about the relates with db_flag and log_flag...
look into source code :) i cannot tell you :)
it's just work... thats is enough for me.
On Tuesday 22 June 2004 17:46, VCI Help Desk wrote:
I'm sure it works properly but I don't understand the concept. How does
the db_flag relate to log_flag? This is what I have now. At the moment I
don't have any setflags anywhere in my config. From a previous test I got
the most results bny setting setflag(5) near the bottom of the config. But
it still didn't log a successful call. Using the settings I have below what
would setflag(3) do on a successful call?
modparam("acc", "log_missed_flag", 3)
modparam("acc", "log_level", 1)
modparam("acc", "log_flag", 1)
modparam("acc", "db_flag", 2)
modparam("acc", "db_missed_flag", 3)
Bill Dunn
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
- --
Regards, Kamen Sharlandjiev
System Administrator
NetBG Communication
Tel: +359 2 962 43 52
+359 2 962 53 93
- --
Public GPG key at: http://pgp.mit.edu
pub 1024D/C6347D3D 2003-03-19 Kamen Sharlandjiev (Comment) <stone(a)netbg.com>
Key fingerprint = D6AA 55BD F0CB FC6B 8C22 A13B 91D1 55C3 C634 7D3D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFA2E8BkdFVw8Y0fT0RAlQGAKDRgQFdw8Yh2fnThQTKMKFjhyipCQCg8M5B
KA7Ye942cfZAosw6e8t4HCw=
=erVU
-----END PGP SIGNATURE-----