[asterisk-users] Dundi and Dial Arguments

Douglas Garstang dgarstang at oneeighty.com
Tue Aug 1 15:38:06 MST 2006


> -----Original Message-----
> From: Michiel van Baak [mailto:michiel at vanbaak.info]
> Sent: Tuesday, August 01, 2006 3:57 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [asterisk-users] Dundi and Dial Arguments
> 
> 
> On 15:39, Tue 01 Aug 06, Douglas Garstang wrote:
> > > -----Original Message-----
> > > From: Mitch Sharp [mailto:MSharp at BIGNetworks.com]
> > > Sent: Tuesday, August 01, 2006 3:06 PM
> > > To: asterisk-users at lists.digium.com
> > > Subject: [asterisk-users] Dundi and Dial Arguments
> > > 
> > > 
> > > Dundi question:
> > >  
> > > Is there a way to pass dial arguments to switch => DUNDi as 
> > > if you were
> > > dialing using Dial(${DUNDILOOKUP(${EXTEN})},,tTwW)?
> > >  
> > > We were going to impliment DUNDi, but realized we lost 
> the ability to
> > > use the Dial features.
> > >  
> > > I could just use the DUNDILOOKUP function, but that keeps you 
> > > from being
> > > able to use alternate routes if DUNDi returns multiple routes.
> > Yes, damn annoying that.
> 
> I suggest you use an AGI for it.
> That gives you way more options

How does AGI help? Your still calling DUNDILOOKUP inside the AGI script, and not matter how many times you call it, your still always going to get the lowest priority path returned.

Doug.



More information about the asterisk-users mailing list