AdminGuide:Service:Call Parking

Return to AdminGuide:Service

Call Parking

Description

This service offers the option to move an ongoing call into a parking slot.

When a call is in the parking slot, the interlocutor will be put on hold while the other user can resume the call from any phone (not just the one they parked the call from). The default configuration has 10 parking slots (890-899). If the call is not resumed after 90 seconds, it will automatically be presented to the device (not the extension) that parked it.

Call parking is performed by dialing the configured on-call service code (by default #8).
KalliopePBX will reply with the number to call in order to resume the call.
The user who parked the call can now hang up and resume conversation by dialing the number provided by KalliopePBX.

This call parking mode requires Direct Media to be disabled for the ongoing call.

If Direct Media is enabled, a call can be parked out by transferring it to an extension used for the call parking service (by default 888).
In this case, once the attended transfer has been executed, KalliopePBX will reply with the number to call in order to resume the call. The user can now hang up and resume conversation by dialing the number provided by KalliopePBX.

Configuration

The service can be enabled/disabled in the PBX -> On-call services page.

The service code can be changed in the PBX -> On-call services page.

The number of parking slots and the corresponding extensions can be configured in the PBX -> numbering plan page.

Interoperability

When using the call parking service, it can be useful to have a key (with Busy Lamp Field) that lets you view whether or not each slot is occupied and, if necessary, resume the parked call.

For monitoring, KalliopePBX sends SIP NOTIFY messages to communicate changes of state. The phone must send a SIP SUBSCRIBE message to request this information.

This operation is normally executed by configuring a BLF-type function key.

The object that needs to be monitored is the extension that corresponds to the parking slot. Other than monitoring the state of occupation of the slot, it is also possible to resume the call by pressing the corresponding function key.

Examples

On SNOM:

Through the web GUI, you can configure function keys with:

Account: select the account from the drop-down (if only one account is configured on the phone, it will be the first in the list)

Type: BLF

value: <extension>

Or you can directly edit the configuration file or the template:

<fkey idx="%%id%%" context="%%line_id%%" label="" perm="">blf sip:<extension>@%%KPBX_IP_ADDRESS%%;user=phone</fkey>

where %%id%% is the ID of the key to configure and %%line_id%% is the ID of the corresponding account (1 if the account is the only one on the phone).

Example:

<fkey idx="0" context="1" label="Parking slot 890" perm="">blf sip:890@192.168.23.190</fkey>

On YEALINK:
Through the web GUI, you can configure DSS keys with:

Type BLF

Value: <extension>

Line: The line associated with the account (Line 1 if the account is the only one on the phone)

Or you can directly edit the configuration file or the template:

memorykey.%%id%%.line=%%line_id%%

memorykey.%%id%%.value=<extension>

memorykey.%%id%%.type=16

where %%id%% is the ID of the key to configure

and %%line_id%% is the ID of the corresponding account (1 if the account is the only one on the phone).

Example:

memorykey.1.line = 1

memorykey.1.value = 890

memorykey.1.type = 16

memorykey.1.pickup_value = %NULL%

memorykey.1.xml_phonebook = %NULL%