At 02:47 11/7/2007, CSB wrote: >Content-Type: multipart/alternative; > boundary="----=_NextPart_000_0007_01C82187.BC96F350" >Content-Language: en-nz > >How is the billsec field calculated in CDRs? > >I have a situation where billsec is being reported as 0 despite the >call being answered and a conversation occurring. An example record follows: > >'2007-11-06 21:36:50', '6495566778', '6495566778', '0116495566778', >'1100012_1', 'Local/[EMAIL PROTECTED],2', >'SIP/64.192.001.001-08893238', 'Dial', >'SIP/[EMAIL PROTECTED]||hH', 10, 0, 'ANSWERED', 3, '', >'1194338210.61', '' >
Where did you get this CDR? CDRs should look more like: http://www.asterisk.org/doxygen/1.2/AstCDR.html clid Caller ID src Source dst Destination dcontext Destination context channel Channel name dstchannel Destination channel lastapp Last app executed lastdata Last app's arguments start Time the call started. answer Time the call was answered. end Time the call ended. duration Duration of the call. billsec Duration of the call once it was answered. disposition ANSWERED, NO ANSWER, BUSY amaflags DOCUMENTATION, BILL, IGNORE etc accountcode The channel's account code. uniqueid The channel's unique id. userfield The channels uses specified field. A call can ring for 10 seconds, then be answered and hung up on (or dropped for some reason), and end up having billable seconds of zero. Where in this CDR is there evidence of a conversation having taken place? A "conversation" would at least be 15-30 seconds: "Hello?" "Yeah, It's me--Dave. I got the stuff, man." "Dave?" "Yeah. 'Dave'. It's me." "Dave's not here." Click. _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
