[Asterisk-Dev] ...and another option to dial()... again...

[Ed Devine]

The only caveat I would offer is that relating to speed.

Adding additional process, pre-process, or external functions would seem to
impact program execution. Since I'm using * as an alternative to a DMS phone
switch (I am routing calls using * in a CLEC environment) and digital and
analog environments are both supported (SIP and VOIP are not considerations
at present), any negative impact on grabbing and processing digits dialed is
of great importance in my environment. I'm also using an older version of
the * CVS for this very reason, primarily because many of the recent
"upgrades or changes" to CVS rendered my system unuseable. Most of the
problem with the perspicacity of the dial application could be addressed by
an indepth explaination (and possibly examples) of what options and features
are available in the dial application.
----- Original Message ----- 
From: "David Wilson" <dw at botanicus.net>
To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
Sent: Sunday, October 10, 2004 2:50 PM
Subject: Re: [Asterisk-Dev] ...and another option to dial()... again...


> On Sun, Oct 10, 2004 at 05:46:45PM +0200, Olle E. Johansson wrote:
>
> > I think it's time to begin thinkin         gonanewdesignfordial.The
> > number of options and featurese that have been added to that app
> > lately is overwhelming and it's getting rather complex to understand
> > this very critical app.
>
> > * Do we need to split it up into simpledial(), dial() and superdial() ?
> > * Can we create another construction for dialling ? Like first calling
> > pre-dial applications to set various functions and then having a
> > "go-ahead" instruction?
>
> > Maybe we could add dial-profiles to realtime configs and dial with a
> > reference to a dial profile in a database or a config file?
>
> Hello!
>
> I happened to be writing an interface to Dial() earlier on there and I
> must say I agree entirely. :)
>
> The function of Dial is beyond what it says.. although the application
> does indeed originate calls, it also handles transfers, indications,
> connection limits, and so on. It is to a great extent the single most
> used yet massively opaque function in Asterisk.
>
> The problem with moving most of the functionality out of Dial is that
> Dial is tied to Asterisk's underlying architecture, and none of the
> flags you provide it really fit sensibly elsewhere.
>
> I like the profiles idea, but trying to break up the functionality of
> Dial would probably result in architectural changes to Asterisk
> beforehand.
>
>
> -- 
> Now that my house has burned down I have a much better view of the moon.
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>