From a41649d66bef35d5dc9bb56632934c90844c12b8 Mon Sep 17 00:00:00 2001
From: Sean Bright <sean@malleable.com>
Date: Thu, 19 Jun 2008 14:28:56 +0000
Subject: [PATCH] Update the queuelog.tex documentation as well.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@123830 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---
 doc/tex/queuelog.tex | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/tex/queuelog.tex b/doc/tex/queuelog.tex
index daf650a266..4200e55d88 100644
--- a/doc/tex/queuelog.tex
+++ b/doc/tex/queuelog.tex
@@ -106,13 +106,13 @@ member!
 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.
-- 
GitLab