[asterisk-bugs] [JIRA] Closed: (ASTERISK-20512) Manager sends a bridge/link message following a hold

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-20512.
----------------------------------

    Resolution: Not A Bug

Bridge Link/Unlink events are sent as part of the bridge loop at the channel level that occurs within the standard two party bridge.  When a feature has to be operated on the channel - such as parking, or attended transfer, or - in your case apparently, restricting the media stream - the two party bridge between the channels is broken.  Control then transfers to a higher layer, typically in features.c.  During that period of time, the two channels are technically not bridged, as frames are not being passed back and forth between the two.  That doesn't mean that the bridge is torn down; just that no media is transferred.

When the channels are able to pass media again, you should receive a new Link event.

I agree this is a little non-intuitive, but changing this behavior in a release branch would not be acceptable.  As such, having a 'bridge begin' or a 'bridge end' event would make a bit more sense as an improvement to AMI, and should be handled as such.

> Manager sends a bridge/link message following a hold
> ----------------------------------------------------
>
>                 Key: ASTERISK-20512
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20512
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels
>    Affects Versions: 1.8.11.1
>         Environment: Asterisk Now 2.02/CentOS Release 5.8 (Final)
>            Reporter: Sidney Gluckman
>         Attachments: hold_log.0
>
>
> Using a Polycom SoundPointIP 321, when I place a call on hold I get a "Hold:On" manager event followed by an "Unlink" event and a "Bridge:Link" event.  I have been using version 1.6.2.21 previously with no "Unlink" or "Bridge:Link" events.  I can understand why an "Unlink" event might get sent but a "Bridge:Link" event seems incorrect.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira