From: http://mediaproxy.ag-projects.com/INSTALL:

Note: In the current version of MediaProxy (1.7.2), the python-mysqldb module should be installed on all mediaproxy nodes even if they don't make use of MySQL access, but instead pass the information back to the dispatcher. If the python-mysqldb module is not installed, no media session information will be sent to the proxy dispatcher and no accounting will be done. Even if accounting is disabled, mediaproxy/proxydispatcher will write an error message to syslog about accounting being enabled but not available because the accounting module is missing. This error message is inaccurate and it means in fact that the python-mysqldb is not installed.

This is a known issue which is a leftover from an older implementation and will be fixed in the next release.

Regards, Norm

Pedro Fernandes wrote:

can you help me by saying what iam doing wrong?i just follow that INSTALL, on previous attemps, and its not working!

On 10/23/07, *Norman Brandinger* < norm@goes.com mailto:norm@goes.com> wrote:

http://mediaproxy.ag-projects.com/INSTALL

Pedro Fernandes wrote:
> Any news about that mysql issue?i have the same problem! :(
>
> mediaproxy mediaproxy]# ./mediaproxy.py --no-fork
> warning: accounting is enabled but the accounting module is
missing.
> accounting is not available!
> Listening for commands on local socket `/var/run/mediaproxy.sock'
> Listening for remote commands on `0.0.0.0:25061'
> Remote commands are allowed from: 192.168.0.187
<http://192.168.0.187>
> <http://192.168.0.187>, 127.0.0.1 <http://127.0.0.1>
<http://127.0.0.1>
> Using IP address `192.168.0.187' for the RTP/RTCP proxy
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users@openser.org <mailto:Users@openser.org>
> http://openser.org/cgi-bin/mailman/listinfo/users
>