kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-09-03 11:25:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

res_parking: Update parking documentation for dynamic parking lots.

Browse Source 
* Remove duplicate res_parking.conf courtesytone config option
documentation.

ASTERISK-24596 #close
Reported by:  Philip Correia

ASTERISK-24605
Reported by:  Philip Correia
Patches:
      call_park_app_doc.patch (license #6672) patch uploaded by Philip Correia

Change-Id: I90a92a891c6494dc08173e675856afcc4764c5b5
This commit is contained in:
Philip Correia
2014-12-15 13:23:53 +02:00
committed by Richard Mudgett
parent 1555cf8951
commit e2853ae337
3 changed files with 138 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
res/parking/parking_applications.c
View File

@@ -90,6 +90,47 @@ ASTERISK_REGISTER_FILE()
call on that extension. If the extension is already in use then execution
will continue at the next priority.
</para>
<para>If the <literal>parkeddynamic</literal> option is enabled in
<filename>res_parking.conf</filename> the following variables can be
used to dynamically create new parking lots. When using dynamic parking
lots, be aware of the conditions as explained in the notes section
below.
</para>
<para>The <variable>PARKINGDYNAMIC</variable> variable specifies the
parking lot to use as a template to create a dynamic parking lot. It
is an error to specify a non-existent parking lot for the template.
If not set then the default parking lot is used as the template.
</para>
<para>The <variable>PARKINGDYNCONTEXT</variable> variable specifies the
dialplan context to use for the newly created dynamic parking lot. If
not set then the context from the parking lot template is used. The
context is created if it does not already exist and the new parking lot
needs to create extensions.
</para>
<para>The <variable>PARKINGDYNEXTEN</variable> variable specifies the
<literal>parkext</literal> to use for the newly created dynamic
parking lot. If not set then the <literal>parkext</literal> is used from
the parking lot template. If the template does not specify a
<literal>parkext</literal> then no extensions are created for the newly
created parking lot. The dynamic parking lot cannot be created if it
needs to create extensions that overlap existing parking lot extensions.
The only exception to this is for the <literal>parkext</literal>
extension and only if neither of the overlaping parking lot's
<literal>parkext</literal> is exclusive.
</para>
<para>The <variable>PARKINGDYNPOS</variable> variable specifies the
parking positions to use for the newly created dynamic parking lot. If
not set then the <literal>parkpos</literal> from the parking lot template
is used.
</para>
<note>
<para>This application must be used as the first extension priority
to be recognized as a parking access extension for blind transfers.
Blind transfers and the DTMF one-touch parking feature need this
distinction to operate properly. The parking access extension in
this case is treated like a dialplan hint.
</para>
</note>
</description>
<see-also>
<ref type="application">ParkedCall</ref>