>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. > My apologies. The CDR records come from a database and so are ordered differently: calldate src Source dst Destination dcontext Destination context channel Channel name dstchannel Destination channel lastapp Last app executed lastdata Last app's arguments 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: This call was up for 2-3 seconds (two way audio for that time). Cameron _______________________________________________ --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
