Hi Gary -
I had to make asterisk use ODBC for everything when I converted to
ODBC message storage. res_odbc and res_mysql wouldn't co-exist.
Hmm. That's odd. I've got the voicemessages table accessed through
res_odbc (of course), and the voicemail_users table accessed directly
through res_mysql. It's been working OK for us so far on our boxes.
Then again, I'm still having problems getting the voicemessages table
to replicate.
There's a php script on the wiki to load up your voicemessage table
with any messages currently on disk...
Aha! I've been looking for something like this. Thank You!
- Noah
On 5/9/06, Gary Reuter <[EMAIL PROTECTED]> wrote:
On 5/9/06, Damon Estep <[EMAIL PROTECTED]> wrote:
> I had similar concerns, but wanted to get a feel for what others are
> experiencing.
>
The extra overhead shouldn't really be a problem on a decent machine,
especially with a ramdisk-bask voicemail spool.
> The goal is to be able to extend our web portal to be able to
> view/listen/delete VM without having to put the load on the * box.
>
I have mysql database (realtime and voicemail storage), web, and ftp
(provisioning) on a seperate machine from asterisk. Rewrote the
vmail.cgi in PHP and everything works fine.
> Already using realtime mysql for VM config.
>
I had to make asterisk use ODBC for everything when I converted to
ODBC message storage. res_odbc and res_mysql wouldn't co-exist.
There's a php script on the wiki to load up your voicemessage table
with any messages currently on disk...
_______________________________________________
--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
_______________________________________________
--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
