--- Vieri [EMAIL PROTECTED] wrote:
Would it be possible to modify the API calls that
are
currently going to the AstDB code within Asterisk,
and
put a translation layer to have them use the
func_odbc
instead (or either one)?
At a lower level, for everything Asterisk does to
its
AstDB,
Hi!
So putting a translation layer so that ast_db_* API calls either go the
normal route or translate to func_odbc (or another path) would improve
functionality because both old and new apps would be able to seamlessly
take advantage of the new database backend or keep using DB1 (the *
admin
--- Bruce Reeves [EMAIL PROTECTED] wrote:
Vieri,
What values are you looking to move from astdb?
I have used realtime to store values for call
features and other
functions in the dial plan. I'm curious what you are
looking to do.
Thanks for the feedback Bruce.
What I'm trying to do
On 3/8/08, Vieri [EMAIL PROTECTED] wrote:
I've been searching the Internet for information
regarding the replacement of astdb with a modern sql
engine.
There are several reasons one would like to do this.
First of all, external applications have a hard time
reading/writing to the
On Sun, Mar 09, 2008 at 01:16:39AM -0800, Vieri wrote:
Let me give just one simple example. Suppose extension
101 dials *78 which sets DND on (in asterisk) and sets
a DB key value on pbx server 1. Then suppose server 1
goes down for some reason and extension 101
auto-registers on server 2.
, if people are really working on it.
On Sat, 2008-03-08 at 20:08 -0600,
[EMAIL PROTECTED] wrote:
Date: Sat, 8 Mar 2008 10:01:28 -0800 (PST)
From: Vieri [EMAIL PROTECTED]
Subject: [asterisk-users] replace astdb with a cluster-capable sql
databaseengine
To: asterisk-users
--- Atis Lezdins [EMAIL PROTECTED] wrote:
For your own custom data you can use Realtime engine
- it has INSERT
and DELETE support in 1.6, and it's easily
backportable to 1.4 (if
you're interested i can give you working patches).
All you have to do
is declare realtime class in
On Sunday 09 March 2008 12:26:55 Vieri wrote:
--- Atis Lezdins [EMAIL PROTECTED] wrote:
Or there's odbc module that creates permanent
connection, and allows
you to declare SQL functions with replacable
variables, but personally
i don't like having additional layer. For this you
can
To be perfectly honest, the REALTIME function is absolutely hideous when
it comes to reading data from the RealTime database. What on earth the
Asterisk developers were thinking when they replaced the perfectly
usable RealTime (which sets a channel variable for each field in the
database) with
Would it be possible to modify the API calls that are
currently going to the AstDB code within Asterisk, and
put a translation layer to have them use the func_odbc
instead (or either one)?
I came across some old code of an odbc version of
app_db which I suppose is obsolete.
I've been searching the Internet for information
regarding the replacement of astdb with a modern sql
engine.
There are several reasons one would like to do this.
First of all, external applications have a hard time
reading/writing to the now-old astdb format.
Also (and this is what interests me
Vieri,
What values are you looking to move from astdb?
I have used realtime to store values for call features and other
functions in the dial plan. I'm curious what you are looking to do.
On Sat, Mar 8, 2008 at 12:01 PM, Vieri [EMAIL PROTECTED] wrote:
I've been searching the Internet for
12 matches
Mail list logo
