[Asterisk-Users] DUNDi Not Able to Handle ComplexFailoverSituations

[Watkins, Bradley]

Is it possible for you to explain in more detail the situation involved.  I'm still thinking that what you're trying to achieve can be done at least with the help of DUNDi weights, but I still don't think I have a full grasp of the solution you're crafting.

Regards,
- Brad 

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Douglas Garstang
Sent: Thursday, June 15, 2006 10:50 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] DUNDi Not Able to Handle ComplexFailoverSituations

> -----Original Message-----
> From: Watkins, Bradley
> [mailto:asterisk-users-bounces at lists.digium.com]On Behalf Of Watkins, 
> Bradley
> Sent: Thursday, June 15, 2006 2:41 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users] DUNDi Not Able to Handle Complex 
> FailoverSituations
> 
> 
> Unless I'm misunderstanding what you're looking to do, Aaron has hit 
> the nail on the head here.  You need to set it up so that the 
> secondary, tertiary, etc. boxes are weighted differently.  That way, 
> you need not know or care about the weights directly within the 
> dialplan.

It isn't as simple as that. When a failure occurs, we only want to use a DUNDi route when it's the primary for a queue.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.