[Asterisk-Users] Dialling a DUNDi Route

[Douglas Garstang]

> -----Original Message-----
> From: Leif Madsen [mailto:asterisk.leif.madsen at gmail.com]
> Sent: Friday, May 12, 2006 12:27 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Dialling a DUNDi Route
> 
> 
> On 5/12/06, Florian Overkamp <florian at obsimref.com> wrote:
> > Douglas Garstang wrote:
> > > We are using a backend MySQL database for call flow, not 
> user agent
> > > registration info. Just how, exactly, is a backend 
> database going to
> > > replicate registration data between Asterisk servers? Realtime has
> > > been documented NOT to work with multiple Asterisk systems. If you
> > > like I can dig up the list messages from Kevin Fleming on this
> > > subject. Realtime also has way too many limitations.
> >
> > You're thinking inside the box. I'm not saying Kevin is 
> wrong. You can
> > probably design a database that uses a per-asterisk set of 
> tables and
> > uses triggers or a stand alone daemon to manually replicate the data
> > between machines. If realtime doesn't fit your need, consider
> > automatically generating extensions.conf etc. from databases using
> > scripts and templates.
> 
> Use func_odbc to get information from your database into the dialplan
> -- then you don't need to pass that information along through the path
> via DUNDi, you just look it up as you need it, then use it.
> 
> At least that's what I'm doing and it works great. Tilghman 
> Lesher is my hero :)

We tried something similar with the MySQL dialplan command. It didn't work. To support findme/followme, we needed to nest database lookups, and the MySQL dialplan command wasn't able to remember the state of queries as they nested.