Name the failed pickup workflow exactly
Record whether the user dialed general call pickup, dialed a directed code plus an extension, pressed a BLF, targeted a ring-group number or tried to retrieve a parked call. These are not interchangeable. Sangoma's feature-code reference says general pickup depends on matching callgroup and pickupgroup values, while directed pickup targets the ringing extension. The Ring Groups guide adds a separate option for directed pickup by group number.
Confirm the actual managed feature codes on the installed system. A printed default or phone template may be stale, disabled or shadowed by another code. Call parking retrieval is a different feature and should leave this investigation if the call was already parked.
Prove the target channel was still ringing
Reproduce with one authorized caller, one target and one requester. Record the target extension and context, ring-group branch if present, outbound PJSIP channel and its unique and linked IDs. Then capture the requester channel and exact digit string or BLF action. A handset ringing display is useful but does not prove which Asterisk channel is currently eligible.
If another member answered, Follow Me advanced, voicemail accepted, a timeout changed destination or the caller disconnected before the pickup ran, classify that transition first. Increasing groups or changing feature codes will not make a channel that is no longer ringing eligible.
Compare managed intent with live group ownership
For general group pickup, the ringing channel needs effective call-group membership and the requester needs an overlapping pickup group. FreePBX form values, generated configuration, loaded PJSIP endpoint objects and the values on the two live channels remain separate evidence. The call-group value must reach the outbound channel created toward the ringing phone.
Numeric and named groups are different namespaces, and named values are case sensitive. Do not fix a mismatch by placing every extension into one broad group. Restore the intended least-privilege department or role mapping through the supported FreePBX interface, apply configuration and confirm it on a fresh call.
Separate BLF state from pickup action
Sangoma's December 30, 2025 phone guide says a ringing extension BLF can perform directed pickup when pressed, while idle and in-use states can map to other actions. That behavior depends on the exact supported phone, template, key mode, firmware, feature code and PBX state. A blinking lamp proves neither the digits transmitted nor authorization.
Capture the key assignment and the SIP or dialed action it produces, then compare a manual directed-pickup call. If the manual code works but the key does not, keep the failure in device provisioning or key behavior. If both reach the feature but find no target, return to extension, context, group and ringing-channel evidence.
Keep ring-group pickup bounded
Sangoma documents an Enable Call Pickup setting that permits directed pickup using the ring-group number. It also says individual ringing members can still be targets for directed pickup. Preserve which destination the caller reached, the member channels actually created and whether the test targeted the group number or a member extension.
Do not transfer that behavior to queues, external Follow Me destinations or every dynamic destination. A queue agent, mobile leg and local PJSIP extension can have different channels, timing and privacy policy. Use their dedicated diagnostic paths once the call is outside the documented pickup mechanism.
Correct one demonstrated boundary and retest
Correct only the proven owner: managed feature code, phone digit map or key, extension context, ring-group pickup option, generated PJSIP groups, applied configuration or authorization design. Retest an eligible group call, directed pickup, denied requester, another member answering first, caller abandonment, timeout and the relevant BLF or ring-group shortcut.
Preserve the Asterisk Pickup event or equivalent paired channel evidence when available, plus the final bridge and two-way audio result. No FreePBX host, module, endpoint, feature code, phone, BLF, group, ring group, channel, bridge, privacy policy, compatibility, availability, price or live call was inspected or tested for this diagnostic.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Asterisk call-pickup architecture ↗
- Asterisk 22 res_pjsip pickup-group options ↗
- Asterisk certified 22.8 Pickup application ↗
- Asterisk PickupChan application ↗
- Asterisk 22 AMI Pickup event ↗
- Sangoma FreePBX feature-code descriptions ↗
- Sangoma FreePBX Ring Groups guide ↗
- Sangoma phone BLF key behavior ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.