Hello!<br><br>It's me again. I began a fairly large modification to my CDR proposal <br>some weeks ago, and finally yesterday and this morning got enough<br>accomplished to allow a commit and some peer review.<br><br>Check the docs out via " svn co <a href="http://svn.digium.com/svn/asterisk/team/murf/RFCs">http://svn.digium.com/svn/asterisk/team/murf/RFCs</a> "<br>
<br>This is a directory; in it you will find:<br>CDRfix2.rfc.doc<br>CDRfix2.rfc.docx<br>CDRfix2.rfc.pdf<br><br>The docx version is the one I actually edit; the doc verison<br>should be editable in both the windows and linux worlds.<br>
The PDF version is for those who just want to read it.<br><br>Basically, I modified the doc to turn Leg-based CDRs into Simple<br>CDR's with splits (both automatic and dial-plan generated). Instead<br>of a single time line for complex conversation, broken into consecutive<br>
segments, now you have N time lines (one per participating channel).<br>A Leg-based CDR system devolves into a Simple CDR system when<br>all the automatic and dial-plan splitting is turned off. This makes things<br>easier to implement and understand. At least, for me! (If I don't understand<br>
it, I doubt I can make YOU understand it!)<br><br>Also, I gave uniqueID's an overhaul based on the idea of REFERENCING.<br>I think most users have misunderstood the uniqueID field in the current<br>CDR system, and don't see the possibilities that solid referencing would<br>
open up. I introduce the idea of uniquely identifying channel 'instances', <br>which are what Asterisk creates when it creates a channel struct internally. The <br>uniqueID field on the CHANNEL struct uniquely identifies that channel instance<br>
across time for a single server. (Currently). (barring masquerades). These are what are <br>REFERENCED by my destchannel, and channel fields. I provide new fields<br>called "channel_uniqueid" and "dstchannel_uniqueid" to reference<br>
these fields; not just the channel name (dahdi/1-1 doesn't quite suffice<br>across time.) (But I left the old fields alone for those who prefer device info).<br>CDR unique ID's can/will be generated for external usage,<br>
but are not available to the dialplan or apps within Asterisk. Thus, only<br>external referencing is possible to individual CDR records. But this should be good<br>enough, I think!<br><br>This may or may not help with issues brought forward a while back<br>
by greyman and others, -- I'd appreciate hearing about it. <br><br>murf<br clear="all"><br>-- <br>Steve Murphy, Pres, Consultant<br>ParseTree Corp<br><br>