Summary:ASTERISK-21544: Bridge API Enhancements - get call pickup working
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-04-17 20:01:55Date Closed:2013-07-02 18:03:18
Status:Closed/CompleteComponents:Core/Bridging Core/Stasis Features
Versions:Frequency of
is related toASTERISK-21699 Bridge API Enhancements - handle Call Pickup in CDRs
Description:Call pickup is still going to happen with a masquerade. This means a few things:

* We need to be able to pull the call pickup related settings out of features and apply it/consume it in the appropriate places (most likely, still the channel drivers). When a pickup works or fails, we also need to make sure we are still playing those tones.
** pickupexten
** pickupsound
** pickupfailsound
* When a masquerade happens, Stasis-Core should *not* know. Instead, a call pickup message should be sent that identifies:
** The channel that was ringing that was pushed out
** The channel that did the pick up
* AMI needs to be refactored to send the necessary events (or verify that they happen). This includes the DialEnd event for the channel that was ringing, as well as the appropriate ChannelStatus/BridgeEnter events for the channels that get bridged.
* CDRs need to be updated to reflect that the dialed channel (and its CDR with the caller) ended. A new CDR should be created as a result of the bridge between the pickup channel and the caller.

Comments:By: Richard Mudgett (rmudgett) 2013-04-17 20:30:51.054-0500

One thing that would be nice for the Pickup application to have is options to play success/fail sounds like the features.conf pickup plays.  This will allow the Pickup application to do everything the features.conf version can.