The Park to Server
feature allows a subscriber to transfer calls to server-side destinations (Parking Spaces
), from where they can be retreived by authorized subscribers. Once a call has been parked, the user’s line is free to originate or receive other calls. If a parked call is not retrieved before a configurable Recall Timer
expires, the parking subscriber will be recalled.
Parking is not possible if:
all Parking Spaces are occupied
a manually requested Parking Space is occupied or invalid
the call is a conference or emergency call
the party to be parked is an Attendant
the party to be parked has already been parked
On the user agent side, the Park to Server feature does not require any protocol extensions other than those for consultation and transfer.
Parking Lots and Parking Spaces
During provisioning for the Park to Server
feature, a subscriber is associated with a Parking Lot
, i.e. a named pool of server-side destinations that can be used for parking.
Each of these destinations (Parking Spaces
) is capable of holding a single call and is addressed by a number.
A Parking Lot
is a BG (Business Group) object and can be shared among subscribers within the same BG. Some subscribers may only be allowed to park calls, while others may only be allowed to retrieve calls from their associated Parking Lot
When a subscriber (with Parking allowed
permission) parks a call to his/her Parking Lot
, the parked call is associated with a Parking Space
number. Any subscriber who has been provisioned to use the same Parking Lot
with Retrieval allowed
permission and who knows the Parking Space
number, is able to retrieve the call.
The administrator has to perform the following tasks:
Parent topic: Calling Services
- Create Parking Lots for personal or shared use
This includes defining the Parking Space number range (implicitely: the Parking Lot size) and the Recall Timer for unretrieved calls.
- Provision subscribers for the Park to Server feature
This includes assigning a (previously created) Parking Lot and granting the Parking allowed and/or Retrieval allowed permissions.
As a prerequisiter, the subscribers must also be provisioned for Call Transfer.
- Create Access Codes for parking and retrieval.
Park to Server - Feature Usage
If an attendant or subscriber (provisioned for the Partk to Server feature) is on an active call, he/she can park the call at a server-side Parking Space by invoking consultation transfer, dialing the Partk to Server access code and completing the call transfer. The Parking Space selection can be performed either automatically (by the server) or manually (by subscriber input). A retrieving subscriber dials the Park Retrieve access code and has to specify the correct Parking Space number.
Park to Server Recall
A Park to Server Recall occurs when a call has been parked using the Park to Server feature, and the Recall Timer of the associated Parking Lot expires without the call being retrieved.
How to Provison a Parking Lot
This procedure describes how to provision Parking Lots at the BG (Business Group) level.
How to Delete a Parking Lot
This procedure describes how to delete Parking Lots at the BG (Business Group) level.
How to Provision a Subscriber for Park to Server
This procedure describes how to provison the Park to Server feature at the feature profile or subscriber level. Feature profiles, in turn, can be created and configured at the switch level or the BG (Business Group) level. At the subscriber level, the previously assigned feature profile can be overwritten to selectively enable, disable or modify the feature configuration for the particular subscriber.
Feature Access Codes for Park to Server
Feature access codes enable subscribers to Park and/or Retrieve calls to/from the server. A feature access code can either be dialed or it can be assigned to a function key on the subscribers' phones, providing seamless access to server-side features.