[asterisk-dev] Re: branch 1.2 r12927 - /branches/1.2/apps/app_dial.c

[Greg Boehnlein]

On Fri, 17 Mar 2006, Tony Mountifield wrote:

> I'd like to offer the opinion that it would be better to revert this
> change and instead document the behaviour. Here are my reasons:
> 
> 1. It is potentially very useful to be able to distinguish easily between
> the calling and called legs of the call. For example, I have an
> application where it would be useful to use G() to transfer the caller and
> callee to a conference, but to give different MeetMe options to each. By
> putting a Goto at context^exten^priority, I can then have the two legs
> processed independently. Applications that want both legs to do the same
> just need to put NoOp there instead, and they will both continue at
> priority+1.
> 
> Without this feature, I would have to do GotoIfs on channel variables to
> distinguish, if indeed there are any suitable variables to test.
> 
> The feature was originally submitted as bug #3786 by anthm. I don't know
> whether he intended the dual-priority behaviour or whether it is a happy
> serendipity, but I think it's worth preserving.
> 
> 2. Changes to a Stable branch should not change how a dialplan is executed.
> There may be folks who discovered the actual behaviour and now rely on it.
> 
> Comments?

I would agree on all points, not that my opinion carries much weight. It 
is important to preserve behavior in a release tree, even if the behavior 
is "unintended". 

-- 
    Vice President of N2Net, a New Age Consulting Service, Inc. Company
         http://www.n2net.net Where everything clicks into place!
                             KP-216-121-ST