[Asterisk-Users] DUNDi Not Able to Handle ComplexFailoverSituations

[Douglas Garstang]

> -----Original Message-----
> From: Stephen Davies [mailto:stephen.l.davies at gmail.com]
> Sent: Thursday, June 15, 2006 11:41 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] DUNDi Not Able to Handle
> ComplexFailoverSituations
> 
> 
> On 15/06/06, Douglas Garstang <dgarstang at oneeighty.com> wrote:
> > Who said I was a C programmer?
> 
> Speaking for myself, I just assumed that you understood that the
> behaviour of an open-source application was the result of contributed
> code.  Your message read to me like something of a demand that
> "someone" fixed it.  You are probably trying to do something pretty
> fancy in your dialplan and that probably brings requirements that the
> original authors didn't foresee.
> 
> They are scratching their itch.  As you said, DUNDi was Mark's
> initiative to make a "open access" call routing system, rather than to
> do with failover.
> 
> If you can hack Asterisk dialplan code, then I think if you open that
> file, take a look at other code that sets variables (search for a
> variable name you know is set, like DIALSTATUS), do some cut and paste
> and you'll discover that, guess what: you ARE a C programmer.

Actually, I'd say I'm not a C programmer. In Asterisk 1.2.7.1, in pbx_dundi.c, function dundi_lookup_exec(), I Added this line:

pbx_builtin_setvar_helper(chan, "DUNDWEIGHT", dr[x].weight);

right below the two other lines that set the DUNDTECH and DUNDDEST variables. When I execute my DundiLookup application in the dialplan, the Asterisk console bombs out. I assume it's core dumping or something. I don't know why though as I only added another line like the ones above. The DUNDTECH and DUNDDEST variables are not being referenced anywhere else in any file.

ALSO... The DundiLookup application command has been deprecated:

Jun 15 12:44:14 WARNING[2935]: pbx_dundi.c:3872 dundi_lookup_exec: This application has been deprecated in favor of the DUNDILOOKUP dialplan function.

In favour of the DUNDILookup function. The DUNDILookup function does NOT seem to set the DUNDTECH and DUNDDEST variables, so it seems we have in effect gone backwards in functionality. In any case, I guess I'll have to try and figure out how to modify the string that DUNDILookup returns, which I'm sure will be harder than adding a new variable to DundiLookup()

Doug.