29 Jun
2006
29 Jun
'06
4:40 p.m.
Hi Ryan,
The computation is based on the last moment RTP was received, if no
RTP is received for a predefined timeout it will substract the
timeout and update the duration accordingly. At this moment the sql
query is hardcoded, which I know is not a very clever thing so a
future version will have it more flexible.
Adrian
On Jun 29, 2006, at 8:35 AM, Ryan Pagquil wrote:
Hi Adrian,
I installed mediaproxy 1.7.2 and it is working fine. The
account is also enabled. But just a few question, can I edit the
sql query on accounting.py just to make it compatible with my
existing radacct table? How does it compute for the AcctSessionTime
for every session that it closes?
Thanks,
Ryan
At 10:57 PM 6/28/2006, Adrian Georgescu wrote:
I do now know your setup but you only need to add
some extra
columns to your radacct table. Except for the time required to
apply the sql changes (your table will lock and you cannot write
to it) I am not aware of any impact on a standard freeradius
installation.
Adrian
>>>
Ok, it means that I'll just make the RTP pass through mediaproxy by
enabling the use of it on non-NATed UA's. Just a question, I have an
existing RADIUS accounting setup, would there be a problem if I
implemented the accounting feature of mediaproxy? I'm afraid because
written in the docs in the distro i need to patch the radacct table,
will it affect the existing one or alter something?
Thanks,
Ryan
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers