[asterisk-commits] seanbright: trunk r123830 - /trunk/doc/tex/queuelog.tex

SVN commits to the Asterisk project asterisk-commits at lists.digium.com
Thu Jun 19 09:28:56 CDT 2008


Author: seanbright
Date: Thu Jun 19 09:28:56 2008
New Revision: 123830

URL: http://svn.digium.com/view/asterisk?view=rev&rev=123830
Log:
Update the queuelog.tex documentation as well.

Modified:
    trunk/doc/tex/queuelog.tex

Modified: trunk/doc/tex/queuelog.tex
URL: http://svn.digium.com/view/asterisk/trunk/doc/tex/queuelog.tex?view=diff&rev=123830&r1=123829&r2=123830
==============================================================================
--- trunk/doc/tex/queuelog.tex (original)
+++ trunk/doc/tex/queuelog.tex Thu Jun 19 09:28:56 2008
@@ -106,13 +106,13 @@
 A call was answered by an agent, but the call was dropped because the
 channels were not compatible.
 
-\textbf{TRANSFER(extension$|$context$|$holdtime$|$calltime)}
+\textbf{TRANSFER(extension$|$context$|$holdtime$|$calltime$|$origposition$)}
 
 Caller was transferred to a different extension.  Context and extension
 are recorded. The caller's hold time and the length of the call are both
-recorded. PLEASE remember that transfers performed by SIP UA's by way
-of a reinvite may not always be caught by Asterisk and trigger off this
-event. The only way to be 100\% sure that you will get this event when
-a transfer is performed by a queue member is to use the built-in transfer
-functionality of Asterisk.
-
+recorded, as is the caller's entry position at the time of the transfer.
+PLEASE remember that transfers performed by SIP UA's by way of a reinvite
+may not always be caught by Asterisk and trigger off this event. The only
+way to be 100\% sure that you will get this event when a transfer is
+performed by a queue member is to use the built-in transfer functionality
+of Asterisk.




More information about the asterisk-commits mailing list