<br><br><div class="gmail_quote">On Thu, Jun 12, 2008 at 5:51 PM, Iñaki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
El Thursday 12 June 2008 17:38:35 David Villasmil escribió:<br>
<div class="Ih2E3d">> Then...<br>
><br>
> Excuse my asking: What IS the point of doing accounting with openser,<br>
> if it will never be accurate?<br>
<br>
</div>That's not true. If you use OpenSer + Radius ACC + MediaProxy + CDRTool<br>
(optional) you can get 99% accurate: if a UAC hangs down then it will not<br>
send a BYE but neither RTP so MediaProxy will detect it and update vía Radius<br>
or SQL.<br>
<br>
Other way is using OpenSer ACC in conjunction with a B2BUA or gateways<br>
supporting Session Timers. In this case, if the UAC crashes it will not<br>
respond to the re-INVITE/UPDATE and the B2BUA/gateway will send a BYE so<br>
OpenSer will account the session properly.</blockquote><div><br>True, But this will also bring the added cost of handling rtps, right? <br></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
AFAIK those are the existintg ACC ways using accounting into a proxy.<br>
<font color="#888888"><br></font></blockquote></div><br>