Skip to content
Phone Guides

Asterisk call parking and retrieval

Parking holds a call in a known slot so that an authorised user can retrieve it elsewhere. Define both how a call enters the lot and who may retrieve it. A parking button on a phone adds its own endpoint configuration requirements.

Source-reviewed, 18 October 2026. Prepared from the cited documentation. No parking or phone-button path has been independently tested by Phone Guides. Scope: Asterisk 22 with res_parking; exact endpoint controls require separate device/firmware sources.

Use the current configuration owner

Modern Asterisk parking uses res_parking.conf. Older instructions that put parking-lot configuration in features.conf describe a different implementation. The official call-parking guide explains that move and separates parking from related feature-code behaviour.

Confirm the module is loaded and identify the effective configuration before changing it. For a managed PBX, use its supported parking-lot settings rather than adding competing generated contexts.

Design a lot before its dialplan

Setting or policy Question to answer
Lot identity Which users and calls share this lot?
Parking entry and slot range Which numbers are reserved, without colliding with other routes?
Dialplan context Which callers can enter or retrieve calls through it?
Timeout How long may a call remain parked?
Return/fallback Who receives an unclaimed call, and what if that destination is unavailable?
Announcements/state display How does the user discover the slot, and what does the phone actually support?

Use the branch-22 parking module reference for the options implementing those decisions. Do not reuse a slot range from another site's example without checking its number plan.

Distinguish park from retrieve

Park() places a call into a lot. ParkedCall() retrieves a parked call. These are different applications; their exact arguments and the selected lot matter. A channel's configured lot and other selection mechanisms can affect which lot is used when a name is omitted.

The ParkedCall reference describes lot/space selection and notes that a configured parkext can cause parking extensions to be managed automatically. Inspect the resulting dialplan before adding a second set of routes for the same purpose.

If a lot's retrieval context is included in an incoming provider context, an external caller may reach more than intended. Treat the include as a permission decision, following dialplan security.

Keep endpoint controls separate

A phone may use transfer to a parking entry, a feature code, a vendor-defined parking action or a monitored slot. Do not assume these are interchangeable. Document the exact control path from the phone's firmware guide and then the Asterisk route it invokes.

A light beside a button also needs a state/subscription path. A successful parked call does not prove that the slot indication or one-touch retrieval works. Use the device-state guide for that separate question.

Reader checks

Inspect the loaded lot and its generated or explicit extensions using the installed CLI's parking help. Then, on your deployment, park an authorised call, identify its slot and retrieve it from a second authorised device. Check a full lot, an empty slot and timeout handling. Confirm an unauthorised entry context cannot retrieve a call.

Observe what happens when the original parker disconnects and when the return destination is unavailable. Keep a bounded fallback so a caller is not left indefinitely on hold. Preserve the old lot/routing configuration for reversal.

Return to Asterisk documentation.