Park

A park operation behaves roughly like a transfer, but it doesn't alert or time out as a transfer would.

Two forms of parking a session are provided: directed call park and nondirected call park. In directed call park, the application specifies the destination address where the call is to be parked. With nondirected park, the service provider or underlying hardware determines the address and returns it to the application.

A parked session typically enters the idle state after it has been successfully parked, and the application should then release the resources associated with it. See Terminate a Session for a summary of how to do this.

If the application unparks the session, new session resources are allocated even if the application has returned the previous pointers, so failure to do proper releases can result in a variety of problems.

Some service providers can remind the user after a session has been parked for some long amount of time. The application sees an offering call with a call reason set to reminder.

Not all service providers support use of this operation.

TAPI 2: linePark, lineUnpark

TAPI 3: ITBasicCallControl::ParkDirect, ITBasicCallControl::ParkIndirect, ITBasicCallControl::Unpark