[Freeswitch-users] CDR Behaviour (b_only)

[Steven Ayre]

Personally I collect both a and b legs using mod_xml_cdr.

The a leg is used for customer stats and billing. This is because we have multiple routes so the a leg represents the number of calls the customer makes and the response sent back to them.

The b legs are used so I can see which routes were tried for each a leg, and what their results were.

Both are used to generate stats and graphs showing how the service is looking inbound and outbound.

Steve on iPhone



On 12 Sep 2010, at 21:10, Ross McKillop <ross at ossiantelecom.co.uk> wrote:

> Hi,
> 
> I'm curious how others handle CDRs from FreeSWITCH.  I need them to end up in 
> a MySQL database and the easiest way I've found of achieving this is to use the
> mod_xml_cdr module to call a PHP script that inserts the row. Is there a preferred
> way of achieving this?
> 
> Also, I only need ONE cdr entry per call, for billing purposes, so what I end up doing
> is having process_cdr as "b_only" which works great for successful calls. However, 
> a call that is not successfully bridged results in two HTTP POST calls to my script
> one with is_outbound = true (as I'd expect for the b leg) but also what appears to
> be the a leg of the CDR (despite requesting b_only) 
> 
> Is this the intended behaviour of "b_only" 
> 
> Regards,
> Ross
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org