On April 12, 2016 at 10:33:27 AM, Joshua Colp (jcolp@xxxxxxxxxx) wrote: Mark Michelson wrote:
<snip>
> I would like to propose a solution to this. Instead of having Asterisk
> automatically handle call forwards when performing an ARI dial, raise an
> event stating "Outbound channel X wants to forward the call to Y". This
> way, the ARI application writer can act on this event as desired. You
> can ignore the call forward attempt altogether. You can look up who Y is
> and forward the call manually. You can check some presence database and
> forward to Y's voicemail instead of Y. You can say "screw you X" and
> forward the call to Z instead.
>
> The upsides to this are that
> 1) It places the ARI author in complete control of the destination of
> the call. Automatic behavior from Asterisk is limited, and there will be
> no surprises.
> 2) By always dialing outbound calls from the ARI application, we can
> assure that channels are being tracked as expected and there are no
> hoops that we have to jump through internally to ensure that everything
> is set up properly.
>
> The big downside I can think of is that the current ARI originate
> command does automatically perform call forwards. This would introduce
> an inconsistency in the behaviors of the two methods of making outbound
> calls.
I think while it's inconsistent the two serve different purposes. The
existing one is very much "dial this and do stuff automagically". The
new one is very much about giving the control to the ARI developer.
Which is really what ARI is supposed to be about in the first place, no?
>
> What is the list's opinion on the proposal for handling call forwards in
> the new ARI dial command?
I'm down with it.
+1 here too! |
_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
