Adrian Georgescu wrote:
This release includes new functionality. Your feedback is appreciated, if you wish to provide it please reply to the mailing lists.
Why is the MySQL accounting still commented out in the accounting.py module? How does one really make MySQL accounting work?
I have followed the INSTALL file exactly, including having the proper python mysql library, but the mysql code is commented out and is not documented in this file.
If I uncomment the mysql code in accounting.py and comment out the whole class RadiusAccounting(RadiusClient), I do get a connection to the mysql database but absolutely no attempt to insert a record ever occurs.
strace shows no attempt to call either the accounting.py or mysql.py when a call tears down.
proxy-2:/usr/local/mediaproxy-1.8.2# ./mediaproxy.py --no-fork Listening for commands on local socket `/var/run/mediaproxy.sock' Listening for remote commands is disabled Using IP address `[proxy-2]' for the RTP/RTCP proxy request d5a93a7e-41cf60d3@10.10.5.201 10.10.5.201:21870:audio [remote ip] proxy-2 remote [remote ip] remote Sipura/SPA942-4.1.10(e) info=from:spa941@proxy-2,to:12487249999@proxy-2,fromtag:8468d68222e2049fo0,totag: session d5a93a7e-41cf60d3@10.10.5.201: started. listening on [proxy-2]:60000 execution time: 3.15 ms lookup d5a93a7e-41cf60d3@10.10.5.201 [provider audio]:50878:audio [provider ip] proxy-2 remote proxy-2 unknown DC-SIP/1.2 info=from:spa941@proxy-2,to:12487249999@proxy-2,fromtag:8468d68222e2049fo0,totag:SDa22ff99-1a7f005a-0-1757497768 execution time: 0.44 ms session d5a93a7e-41cf60d3@10.10.5.201: called signed in from [provider ip]:50878 (RTP) (will return to [provider ip]:50878) session d5a93a7e-41cf60d3@10.10.5.201: caller signed in from [remote ip]:21870 (RTP) (will return to [remote ip]:21870) session d5a93a7e-41cf60d3@10.10.5.201: called signed in from [provider ip]:50879 (RTCP) (will return to [provider ip]:50879) delete d5a93a7e-41cf60d3@10.10.5.201 info= session d5a93a7e-41cf60d3@10.10.5.201: 697/703/1393 packets, 195160/196348/390040 bytes (caller/called/relayed) session d5a93a7e-41cf60d3@10.10.5.201: ended. execution time: 0.54 ms
I am not the only person to report this, so I don't want to hear that it is operator error or is documented somewhere, because it is not.
Jeremy McNamara