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

[SVN commits to the Asterisk project]

Author: murf
Date: Mon Jan 12 12:35:08 2009
New Revision: 168504

URL: http://svn.digium.com/svn-view/asterisk?view=rev&rev=168504
Log:
After a little thought, I revised the peeraccount documentation. It's user modifiable.

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=168504&r1=168503&r2=168504
==============================================================================
--- team/murf/RFCs/CDRfix2.rfc.txt (original)
+++ team/murf/RFCs/CDRfix2.rfc.txt Mon Jan 12 12:35:08 2009
@@ -899,7 +899,8 @@
 callerid_rdnis        (user modifiable)
 callerid_dnid        (user modifiable)
 userfield   (user modifiable)
-    --- These 8 fields are set on the channel,
+peeraccount   (new)
+    --- These 9 fields are set on the channel,
         and CEL events will record snapshots of these with
         each channel event. All these values are copied 
         from channel structure storage with each event
@@ -930,6 +931,17 @@
         readable for the target extension's display. The
         callerid would then be different from one leg to
         the next...
+
+        peeraccount holds 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.) This field would normally
+        be set when the peer channel is created, from the
+        technology-specific config file. This could be
+        overridden in the dialplan via the M() or U() options
+        to Dial. How to override in the case of xfers is
+        unclear at the moment.
+
 
 answer      (timeval)
 disposition (numeric/string)
@@ -1056,12 +1068,6 @@
         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.
@@ -1501,6 +1507,7 @@
 callerid_ani        (user modifiable)
 callerid_rdnis        (user modifiable)
 callerid_dnid        (user modifiable)
+peeraccount          (user modifiable)
 userfield   (user modifiable)
     --- These 8 fields are set on the channel,
         and CEL events will record snapshots of these with
@@ -1524,6 +1531,17 @@
         at least the name & num in the callerid. When
         the channel is created, these values are set from
         the channel config files.
+
+        peeraccount holds 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.) This field would normally
+        be set when the peer channel is created, from the
+        technology-specific config file. This could be
+        overridden in the dialplan via the M() or U() options
+        to Dial. How to override in the case of xfers is
+        unclear at the moment.
+
 
 
 answer      (timeval)