[asterisk-dev] Manger inconsistency: ASTERISK-17455

[Nicolas Gudino]

> Issue: https://issues.asterisk.org/jira/browse/ASTERISK-17455
> 
> Back in 2007 there was an attempt to make AMI more consistent. One of the changes involved changing Link/Unlink manager events to Bridge events with a Bridgestate: Link/Unlink header. One Link and one Unlink event in channel.c were converted. Unfortunately, there were two more Unlink events that were not converted. So, things have been really inconsistent in this case for 4 years now.
> 
> It's easy enough to change, but I thought I'd get people's opinions on where the change should go. I don't like making API behavior changes to released branches, so my vote is for 1.10+ being fixed and leaving 1.8 with an inconsistent API in case people have come to rely upon it. With that said, if people are using these events and they are inconsistent, it is possible that they are missing events because they are just looking for the documented behavior. There is also always the option of making a config option that is disabled by default that would present the more consistent behavior. Since it has been 4 years since the change was made and we are just now hearing about the issue, I am leaning towards not going to the trouble/complexity of adding another config option and just making the change 1.10+.

Just make the change in 1.10+ with no config options. As a developer of manager applications I have to deal with all sorts of AMI inconsistencies between asterisk versions. Having an option to enable or disable behaviour adds noise/clutter to the source/configs/admins and does not provide any real benefit, as most (if not all) manager apps should be dealing with the inconsistency already.

Best regards,

--
Nicolas Gudino