[asterisk-commits] murf: branch murf/RFCs r159893 - /team/murf/RFCs/CDRfix2.rfc.txt

[SVN commits to the Asterisk project]

Author: murf
Date: Sun Nov 30 08:48:36 2008
New Revision: 159893

URL: http://svn.digium.com/view/asterisk?view=rev&rev=159893
Log:
A little more cleanup. Get the linkedID's the same within a set; a little grammar cleanup. Hmmmm, maybe the disposition doesn't need to be specified in as many places as it is... next round.

Modified:
    team/murf/RFCs/CDRfix2.rfc.txt

Modified: team/murf/RFCs/CDRfix2.rfc.txt
URL: http://svn.digium.com/view/asterisk/team/murf/RFCs/CDRfix2.rfc.txt?view=diff&rev=159893&r1=159892&r2=159893
==============================================================================
--- team/murf/RFCs/CDRfix2.rfc.txt (original)
+++ team/murf/RFCs/CDRfix2.rfc.txt Sun Nov 30 08:48:36 2008
@@ -97,7 +97,8 @@
 when they are bridged, etc.
 
 In my examples, I just use something like 'abc123' or suchlike to
-represent the linkedID field.
+represent the linkedID field. The point is not that example linkedID
+is fake; it's that all the CDR's in a set have the same linkedID.
 
 We set up a config file element to allow you to format the linkedID 
 field when it is output to a CDR. While playing with the numeric
@@ -112,8 +113,8 @@
 Asterisk has no way to decide what's internal vs. external.
 Thus, all scenarios in this document make no distinction between
 the two. This is purely "Business Logic", and must be set up
-by the poor schmoe who has to build a billing package. Whether
-he/she/they determine external lines by channel or device name,
+by the Poor Schmoe who has to build a billing package. Whether
+he/she/they determines external lines by channel or device name,
 by billing account codes, whatever, is up to him/her/them.
 
 I would imagine that all the example scenarios could be viewed 
@@ -559,7 +560,7 @@
 	 CDR5:  B -> A  start: e6     ans: e7  end: e8   type: CALL                Party: B  linkedid: yhj47
      CDR6:  A       start: e8              end: e10  type: HOLD                Party: B  linkedid: yhj47
      CDR7:  B -> C  start: e8     ans: e9  end: e10  type: AXFER1 Disp: ANSW   Party: B  linkedid: yhj47
-     CDR8:  B -> C  start: e10    ans:     end: e11  type: AXFER2 Disp: ANSW   Party: A  linkedid: yhj47 Hung: B
+     CDR8:  B -> C  start: e10    ans:     end: e11  type: AXFER2              Party: A  linkedid: yhj47 Hung: B
      CDR9:  A       start: e11             end: e12  type: HOLD                Party: C  linkedid: yhj47
      CDR10: C -> D  start: e11    ans: e12 end: e13  type: BXFER               Party: A  linkedid: yhj47
 	 CDR11: A       start: e13    ans:     end: e15  type: PARK                Party: D  linkedid: yhj47 ParkingStall: 701 at default
@@ -580,11 +581,11 @@
  e6:  A hangs up. B&C converse
  e7:  B or C hang up.
 
-     CDR1:  A -> B  start: e1     ans: e2  end: e3   type: CALL   Disp: ANSW   Party: A  linkedid: yhj47
-     CDR2:  A       start: e3              end: e5   type: HOLD                Party: A linkedid: zzz33
-     CDR3:  A -> C; start: e3     ans: e4  end: e5   type: AXFER1 Disp: ANSW   Party: A linkedid: zzz33
-     CDR4:  A -> C; start: e5     ans:     end: e6   type: 3WAY   Disp: ANSW   Party: B linkedid: zzz33
-     CDR5:  A -> C; start: e6     ans:     end: e7   type: AXFER2 Disp: ANSW   Party: B linkedid: zzz33 Hung: A
+     CDR1:  A -> B  start: e1     ans: e2  end: e3   type: CALL   Disp: ANSW   Party: A  linkedid: utf87
+     CDR2:  A       start: e3              end: e5   type: HOLD                Party: A  linkedid: utf87
+     CDR3:  A -> C; start: e3     ans: e4  end: e5   type: AXFER1 Disp: ANSW   Party: A  linkedid: utf87
+     CDR4:  A -> C; start: e5     ans:     end: e6   type: 3WAY   Disp: ANSW   Party: B  linkedid: utf87
+     CDR5:  A -> C; start: e6     ans:     end: e7   type: AXFER2 Disp: ANSW   Party: B  linkedid: utf87 Hung: A