Documentation updates for BRIDGEPVTCALLID

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@99647 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Olle Johansson 2008-01-22 20:44:56 +00:00
parent 3d92f97722
commit b35f8d0358
2 changed files with 8 additions and 2 deletions

View File

@ -66,6 +66,10 @@ Dialplan functions
the existence of a dialplan target.
* Added two new dialplan functions, TOUPPER and TOLOWER, which convert a string to
upper and lower case, respectively.
* When bridging, Asterisk sets the BRIDGEPVTCALLID to the channel drivers unique
ID for the call (not the Asterisk call ID or unique ID), provided that the
channel driver supports this. For SIP, you get the SIP call-ID for the
bridged channel which you can store in the CDR with a custom field.
CLI Changes
-----------

View File

@ -736,6 +736,7 @@ ignored.
${CDR(accountcode)} * Account code (if specified)
${BLINDTRANSFER} The name of the channel on the other side of a blind transfer
${BRIDGEPEER} Bridged peer
${BRIDGEPVTCALLID} Bridged peer PVT call ID (SIP Call ID if a SIP call)
${CALLERID(ani)} * Caller ANI (PRI channels)
${CALLERID(ani2)} * ANI2 (Info digits) also called Originating line information or OLI
${CALLERID(all)} * Caller ID
@ -777,8 +778,9 @@ ${SYSTEMNAME} * value of the systemname option of asterisk.conf
\subsection{Application return values}
In Asterisk 1.2, many applications return the result in a variable
instead of, as in Asterisk 1.0, changing the dial plan priority (+101).
Many applications return the result in a variable that you read to
get the result of the application. These status fields are unique
for each application.
For the various status values, see each application's help text.
\begin{verbatim}
${AGISTATUS} * agi()