[Asterisk-Users] DUNDi Not Able to Handle Complex FailoverSituations

[Douglas Garstang]

> -----Original Message-----
> From: Aaron Daniel [mailto:amdtech at shsu.edu]
> Sent: Wednesday, June 14, 2006 7:10 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] DUNDi Not Able to Handle Complex
> FailoverSituations
> 
> 
> On Wed, 14 Jun 2006, Douglas Garstang wrote:
> > Why doesn't the DUNDILOOKUP function return the weight of a 
> path to a number? The CLI 'dundi lookup' command does. What 
> about the mac address and expiry period? The CLI command 
> returns those, but the DUNDILOOKUP function does not. Why?
> 
> Correct me if I'm wrong, but DUNDi is doing all the failover 
> work for you. 
> It decides based on the weights what route is best.  If you 
> want one route 
> to be higher than another, set it up that way.  That's the benefit of 
> using DUNDILOOKUP to handle it, no more work for you after 
> the initial 
> routing.

DUNDi does not handle the situation of phone failover as well as static numbers (ie queues), which is what we are trying to acheive.

> 
> If that doesn't work for you, program the routes directly into the 
> dialplan instead of using DUNDi, it seems like you'll get 
> better results 
> that way.  We did that for a while until we decided to move to DUNDi. 
> Some people will find it more suited to their needs, some won't.

There are no routes. Termination ends at the Asterisk box.