Skip to content
Snippets Groups Projects
  • Richard Mudgett's avatar
    bad8caa8
    Reimplement bridging and DTMF features related channel variables in the bridging core. · bad8caa8
    Richard Mudgett authored
    * The channel variable ATTENDED_TRANSFER_COMPLETE_SOUND is no longer
    channel driver specific.  If the channel variable is set on the
    transferrer channel, the sound will be played to the target of an attended
    transfer.
    
    * The channel variable BRIDGEPEER becomes a comma separated list of peers
    in a multi-party bridge.  The BRIDGEPEER value can have a maximum of 10
    peers listed.  Any more peers in the bridge will not be included in the
    list.  BRIDGEPEER is not valid in holding bridges like parking since those
    channels do not talk to each other even though they are in a bridge.
    
    * The channel variable BRIDGEPVTCALLID is only valid for two party bridges
    and will contain a value if the BRIDGEPEER's channel driver supports it.
    
    * The channel variable DYNAMIC_PEERNAME is redundant with BRIDGEPEER and
    is removed.  The more useful DYNAMIC_WHO_ACTIVATED gives the channel name
    that activated the dynamic feature.
    
    * The channel variables DYNAMIC_FEATURENAME and DYNAMIC_WHO_ACTIVATED are
    set only on the channel executing the dynamic feature.  Executing a
    dynamic feature on the bridge peer in a multi-party bridge will execute it
    on all peers of the activating channel.
    
    (closes issue ASTERISK-21555)
    Reported by: Matt Jordan
    
    Review: https://reviewboard.asterisk.org/r/2582/
    
    
    git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@390771 65c4cc65-6c06-0410-ace0-fbb531ad65f3
    bad8caa8
    History
    Reimplement bridging and DTMF features related channel variables in the bridging core.
    Richard Mudgett authored
    * The channel variable ATTENDED_TRANSFER_COMPLETE_SOUND is no longer
    channel driver specific.  If the channel variable is set on the
    transferrer channel, the sound will be played to the target of an attended
    transfer.
    
    * The channel variable BRIDGEPEER becomes a comma separated list of peers
    in a multi-party bridge.  The BRIDGEPEER value can have a maximum of 10
    peers listed.  Any more peers in the bridge will not be included in the
    list.  BRIDGEPEER is not valid in holding bridges like parking since those
    channels do not talk to each other even though they are in a bridge.
    
    * The channel variable BRIDGEPVTCALLID is only valid for two party bridges
    and will contain a value if the BRIDGEPEER's channel driver supports it.
    
    * The channel variable DYNAMIC_PEERNAME is redundant with BRIDGEPEER and
    is removed.  The more useful DYNAMIC_WHO_ACTIVATED gives the channel name
    that activated the dynamic feature.
    
    * The channel variables DYNAMIC_FEATURENAME and DYNAMIC_WHO_ACTIVATED are
    set only on the channel executing the dynamic feature.  Executing a
    dynamic feature on the bridge peer in a multi-party bridge will execute it
    on all peers of the activating channel.
    
    (closes issue ASTERISK-21555)
    Reported by: Matt Jordan
    
    Review: https://reviewboard.asterisk.org/r/2582/
    
    
    git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@390771 65c4cc65-6c06-0410-ace0-fbb531ad65f3