Asterisk cmd Park

Info about application 'Park'

Synopsis

Park yourself

Description

Park(): Used to park yourself (typically in combination with a supervised transfer to know the parking space). This application is always registered internally and does not need to be explicitly added into the dialplan, although you should include the 'parkedcalls' context (or the context specified in features.conf).

If you set the PARKINGEXTEN variable to an extension in your parking context, Park() will park the call on that extension, unless it already exists. In that case, execution will continue at next priority.

Details

Richard Mudgett in Feb. 2012

Q: I'd like each user to have three park buttons, park 1, park 2, park 3.

A: A device state check in this case is also unnecessary because Park will
continue executing dialplan if the park fails.

You could try three parkinglots with one parking space each. Each
phone park button would transfer the call to a different parkinglot.
Then all you need to do is include the parkinglot context(s) into your
dialplan context to have access to the generated parking extensions.

Please note that for Asterisk to detect an extension as a parking
extension, the first priority of the extension must be the park
application. If the park application is not the first priority of
the extension, then the transfer is treated as a normal transfer.
...

if Park fails for whatever reason, it continues executing
dialplan. With that dialplan, it is mainly going to fail if the parking
space is already in use.

> I'm not entirely sure what it means for Asterisk to detect an
> extension as a parking extension. Can you please explain how a
> parking transfer is different than a normal transfer?

If Asterisk detects the extension as a parking extension:
exten => 700,1,Park()
Asterisk can perform special processing dealing with parking the
call that may be needed for the channel driver. Also note that the
dialplan extension is *not* actually executed in this case.

For SIP, blind transferring to parking, the parking is done as part
of the transfer. If the park attempt fails, the transfer fails. A
normal blind transfer would complete the transfer and then execute
the dialplan extension on the transferred channel.

For DTMF transfers (features.conf), attended and blind transferring
to parking are identical. You will always hear the parking space
assigned. If the park attempt fails, the interrupted bridge will be
resumed.

Info about application 'Park'

Synopsis

Park yourself

Description

Park(): Used to park yourself (typically in combination with a supervised transfer to know the parking space). This application is always registered internally and does not need to be explicitly added into the dialplan, although you should include the 'parkedcalls' context (or the context specified in features.conf).

If you set the PARKINGEXTEN variable to an extension in your parking context, Park() will park the call on that extension, unless it already exists. In that case, execution will continue at next priority.

Details

Richard Mudgett in Feb. 2012

Q: I'd like each user to have three park buttons, park 1, park 2, park 3.

A: A device state check in this case is also unnecessary because Park will
continue executing dialplan if the park fails.

You could try three parkinglots with one parking space each. Each
phone park button would transfer the call to a different parkinglot.
Then all you need to do is include the parkinglot context(s) into your
dialplan context to have access to the generated parking extensions.

Please note that for Asterisk to detect an extension as a parking
extension, the first priority of the extension must be the park
application. If the park application is not the first priority of
the extension, then the transfer is treated as a normal transfer.
...

if Park fails for whatever reason, it continues executing
dialplan. With that dialplan, it is mainly going to fail if the parking
space is already in use.

> I'm not entirely sure what it means for Asterisk to detect an
> extension as a parking extension. Can you please explain how a
> parking transfer is different than a normal transfer?

If Asterisk detects the extension as a parking extension:
exten => 700,1,Park()
Asterisk can perform special processing dealing with parking the
call that may be needed for the channel driver. Also note that the
dialplan extension is *not* actually executed in this case.

For SIP, blind transferring to parking, the parking is done as part
of the transfer. If the park attempt fails, the transfer fails. A
normal blind transfer would complete the transfer and then execute
the dialplan extension on the transferred channel.

For DTMF transfers (features.conf), attended and blind transferring
to parking are identical. You will always hear the parking space
assigned. If the park attempt fails, the interrupted bridge will be
resumed.

Created by: zombie.dk, Last modification: Tue 12 of Jun, 2012 (03:25 UTC) by admin
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+