similar to: Determining if extension exists

It seems that I am having a heck of a time explaining my attempts at distributing ACD Queues to the list. Here's one little problem, that's only a piece of the puzzle. dundi.conf: 180q => global_dundi_q_pbx1,100,IAX,dundi1:${SECRET}@${IPADDR}/${NUMBER},nopartial 180q => global_dundi_q_pbx2,200,IAX,dundi2:${SECRET}@${IPADDR}/${NUMBER},nopartial 180q =>

Anyone out there have a functional DUNDi configuration using SIP for the inter-Asterisk transport? I've gotten it to work with IAX2, but if I change it to SIP it does not pass the call over even though it knows where to send it. Thanks. The contents of this email message and any attachments are confidential and are intended solely for addressee. The information may also be legally

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@lists.digium.com

Who said I was a C programmer? -----Original Message----- From: Terry Wilson [mailto:otherwiseguy@gmail.com] Sent: Wed 6/14/2006 6:03 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Cc: Subject: Re: [Asterisk-Users] DUNDi Not Able to Handle Complex FailoverSituations pbx/pbx_dundi.c in dundifunc_read(). shouldn't be too hard to have it set some variables (i.e.

I'm using DUNDi. My lookup returns 'IAX2' for the tech, and 'dundi:q9sgTFkVMBFdmp0IDX1bYQ@xxx.187.142.204/3254101' for the destination. How do I dial this? I've tried dialling it with: "Dial" "IAX2/dundi:q9sgTFkVMBFdmp0IDX1bYQ@xxx.187.142.204/3254101" passed from my AGI script, but the other endpoint (xxx.187.142.204) is returning: May 11 09:23:41

This is driving me nuts. 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? We absolutely need this in order to perform out routing logic. It has become quite apparent to me that DUNDi is _NOT_ suited

On Fri, 2006-12-08 at 04:26 -0700, Douglas Garstang wrote: > Hi Steve. > > Thanks, but unfortunately, I can't be involved in that. We are > running Asterisk in a production environment and we're using > 1.2, not 1.4. I don't have the resources to work with 1.4. > Last time I filed a bug against 1.2 I got told off. >

Can someone show me how to set up DUNDi, I will be using it to connect 14 asterisk servers internally. I don't want to use it on the external world. If anyone has any examples of connecting 2 or 3 (if their is a difference) machines in a DUNDi co-operation that would be helpful. Johnathan Falk Network Administrator Clinton Community Schools

It seems that when you use Realtime static and possibly realtime realtime for sip users, that Asterisk fails to create the regexten context for DUNDi. Someone else had the same problem back in July. Doesn't look like they ever had a resolution. <http://lists.digium.com/pipermail/asterisk-users/2006-July/160105.html>

Does anyone have any information on how to use DUNDi precaching? Mark Spencer made a post 2 years ago where he hinted it may be possible to configure DUNDi such that you could centralise your DUNDi registration info by using precaching, instead of having each DUNDi peer meshed with every other one... http://lists.digium.com/pipermail/dundi/2004-October/000189.html However, it seems that no

Hi everyone! I'm quite a newbie at this Asterisk stuff so please bear with me. We've recently decided to start training in Asterisk via AsteriskNow! Asterisk version is 1.4.18.1 through AsteriskNow! 1.02 The box we have is paired with a Digium TE110P and we've managed to get it to the point where incoming calls via a single DID (from NTT Japan) can be received and answered

Good afternoon gentlemen (and ladies). A costumer of mine has many servers and each one maps their SIP extensions to the others via DUNDi. It works like a charm. SIP extensions can only register at one server, the one they "belong" to. In case one extension wants to call other that is registered in another server, DUNDi takes care of that by calling the other server using IAX2 and G.729

Well, this kinda sux. We have three Asterisk servers. Phones register to a single, primary server. When a phone on one wants to reach a phone on another, we use DUNDi to discover the destination pbx and IAX to transfer the call to the other Asterisk box. This seems to be a fairly common practice amongst Asterisk users, yes? Well, what about setting variables before call placement? Say you want

Has anyone got any neat solutions for Asterisk .conf file revision control? We have multiple Asterisk boxes here, that we'd like to maintain a _mostly_ common set of conf files on. They aren't all the same though. There's subtle differences. For example, in sip.conf, iax.conf etc, the bindaddr setting is different. Dundi.conf is very different between each system. At the moment I

svn trunk 31497 For the life of me, I can't get this :) I want to be able to catch the situation where the calling party hangs up *before* the call is connected to the called party. My dialplan is thus: macro DialExternal(exten) { Dial(Zap/G3/${exten},120,g,M(connected)); goto DialResult|r${HANGUPCAUSE}|1; Hangup(); }; But the goto dialresult is not executed: Executing

Hi, I'm trying to use ChanIsAvail to build a resilient 'dialout' macro. The logic is simple; try Zap/g1 (a group of two E1s), and if that fails, try locating a channel via DUNDi. Here's a massively cut down version to illustrate the problem I'm having. macro dialout ( dest ) { ChanIsAvail(Zap/g1); noop(Value of AVAILCHAN is ${AVAILCHAN});

Before I play around with this again in 1.2.1, regexten is still essentially broken, correct? The misconception seems to be that it allows you to execute a command upon registration from a SIP UA. Even the O'Reilly TFOT book erroneously states that this is what it is for. After reading the developer discussion though, it definitely seems to be broken. Is it fixed yet? Doug.

Great Email. I'm going to respond to some of the points. "Q: What are the plans for HA? A: With a configuration using DNS-SRV and DUNDi, you can create a pretty resiliant setup now." That's BS. Last time I checked, Asterisk's support of SRV was to only grab the first SRV entry. Period. If it doesn't try any more SRV hosts after the first fails, just exactly how

Does anyone know where I can find some good DUNDi docs? The ones are dundi.org are absolutely horrible. The examples in dundi.conf are pretty much useless. I still can't figure out why Digium can't write some good documentation. It's their 'baby' after all. This really drives me nuts and pisses people off in general. I've been dicking around with DUNDi for over 6 months and

> -----Original Message----- > From: Watkins, Bradley [mailto:Bradley.Watkins@compuware.com] > Sent: Thursday, June 15, 2006 10:36 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] DUNDi Not Able to > HandleComplexFailoverSituations > > > Is it possible for you to explain in more detail the > situation involved.