Ah, ok. I was thinking in somewhat like mediaproxy python script does,
being called each transaction from ser.cfg
post-processing mysql data is an idea but I'm thinking in something
more dynamic, to prevent calls based on usage patterns while being
able to report usage
currently it seems to me that using RADIUS and Exec-Program-Wait
scripts with SIP parameters is the way to go. unfortunately my
RADIUS questions here in this list seems to reach a solid wall
( perhaps no-one caries to use RADIUS with SER anyway, perhaps
it would be fixed on upcoming ser 0.9, who knows?! :-) )
Thanks anyway
!3runo
Darren Nay wrote:
That script is not called from ser.cfg. It is
completely independent from
SER, other than it uses the ser mysql database to get information. Just
change that DB connection parameters in the top of the script and run it
from the command line.
Note - It does require that you have the perl DBI and MySQL modules
installed.
Darren