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

[SVN commits to the Asterisk project]

Author: murf
Date: Mon Jan 12 12:25:10 2009
New Revision: 168503

URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=168503
Log:
Added missing description of peeraccount field in CDR's (both Leg and Simple)

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

Modified: team/murf/RFCs/CDRfix2.rfc.txt
URL: http://svn.digium.com/svn-view/asterisk/team/murf/RFCs/CDRfix2.rfc.txt?view=diff&rev=168503&r1=168502&r2=168503
==============================================================================
--- team/murf/RFCs/CDRfix2.rfc.txt (original)
+++ team/murf/RFCs/CDRfix2.rfc.txt Mon Jan 12 12:25:10 2009
@@ -1056,6 +1056,12 @@
         channel A. The channel/dstchannel will 
         reflect B calling C.
 
+peeraccount   (new)
+    --- The account code of the peer (the dialed party).
+        (this should reasonably be expected to appear
+        on any leg that involves dialing... so, CALL,
+        BXFER, AXFER, etc.)
+
 src
     --- the name of extension that was executing when
         this channel was created.
@@ -1070,7 +1076,7 @@
         The database backend can then either ignore these,
         or set these fields in the row, as described 
         by the backends documentation.
-
+        The "CDR_" will be be removed.
 
 
 
@@ -1671,6 +1677,11 @@
         Don't be shocked if you see Dahdi/1-1<ZOMBIE>
         -- it happens with masquerading.
 
+peeraccount   (new)
+    --- The account code of the peer (the dialed party).
+        This will appear on the CDR describing the peer's
+        channel usage. 
+
 src
     --- the name of extension that was executing when
         this channel was created.
@@ -1680,5 +1691,10 @@
 
 vars        (a list of attached vars)
     --- When this is implemented, any channel variables
-        that begin with CDR_ will be sent with the event,
+        that begin with "CDR_"  will be sent with the event,
         and attached as a variable list to the CDR being posted.
+        The "CDR_" will be be removed.
+        The database backend can then either ignore these,
+        or set these fields in the row, as described 
+        by the backends documentation.
+