Page 1 of 1

New VICIDIAL 2.0.4beta1 released

PostPosted: Tue Nov 27, 2007 3:16 pm
by mflorell
Hello,

A lot of the new features you have been asking for have been added in this new release tree. We are now in debug mode as we will release the full version soon.

Please try out the beta version and post your results.

For more information on the changes, and the download link, go here:
http://www.eflo.net/VICIDIALforum/viewtopic.php?p=15095

PostPosted: Wed Nov 28, 2007 12:48 am
by ramindia
Hi


thats good news

let me test, what news in this version revert back

ram

PostPosted: Wed Nov 28, 2007 1:19 am
by mflorell
To revert back you would have to undo all of the database changes it makes, which might not be so easy.

As for testing, this ccode is running in production at some large call centers right now so I do not anticipate any major bugs or they would have found them.

PostPosted: Wed Nov 28, 2007 1:01 pm
by nobesnickr
I'll start testing it.

Is it still best to use Asterisk 1.2.x on this or is it safe for 1.4.x?

What do you recommend for mysql?

I'm going to do a scratch install this weekend so I'd like to get it all running with the most recommended for the software. Thanks!

PostPosted: Wed Nov 28, 2007 8:13 pm
by mflorell
This version will function with Asterisk 1.4(just make sure you use the right extensions.conf entries and asterisk_version variable in servers table), but Asterisk 1.4 is still not as stable or efficient as Asteirsk 1.2 and I do not recommend Asterisk 1.4 for production use.

As for MySQL, anything 4.0.27 and above seems to work just fine. I have clients using several different versions.

Let me know how your install goes.

PostPosted: Thu Nov 29, 2007 9:59 am
by shawno
mflorell wrote:Asterisk 1.4 is still not as stable or efficient as Asteirsk 1.2 and I do not recommend Asterisk 1.4 for production use.


Could this be the reason I am getting Reject Frames in the console and calls drop periodically? I've been trying to figure this problem out for weeks.

PostPosted: Thu Nov 29, 2007 10:03 am
by mflorell
There are all sorts of issues still with Asterisk 1.4 including thread locking that does not work right, all of which cause problems like those even on servers with not much load.

PostPosted: Thu Nov 29, 2007 10:05 am
by shawno
So how difficult is it to downgrade to Asterisk 1.2 while keeping my same configuration? Are there a lot of config file changes to be had?

PostPosted: Thu Nov 29, 2007 10:07 am
by mflorell
I am not really familiar with the config file changes from 1.4 to 1.2 when working from a default 1.4 config file, but they should be very similar. I would recommend doing the downgrade and then running asterisk and see what the Asterisk CLI output is when you start asterisk. It will tell you what it does not like.

PostPosted: Mon Dec 03, 2007 4:50 pm
by krondorl
shawno wrote:So how difficult is it to downgrade to Asterisk 1.2 while keeping my same configuration? Are there a lot of config file changes to be had?


Down grading is not really an issue.. We had installed the latest of the latest asterisk 1.4 and downgraded to 1.2.21 with no issues whatsoever.

PostPosted: Tue Dec 04, 2007 8:01 pm
by shawno
krondorl wrote:
shawno wrote:So how difficult is it to downgrade to Asterisk 1.2 while keeping my same configuration? Are there a lot of config file changes to be had?


Down grading is not really an issue.. We had installed the latest of the latest asterisk 1.4 and downgraded to 1.2.21 with no issues whatsoever.


Thanks I'll give it a shot and let you guys know how it goes.

PostPosted: Thu Dec 06, 2007 3:41 pm
by shawno
Successfully downgraded from 1.4 to 1.2 -- Will be running with 15 agents tonight and closely monitoring for active calls dropping. I will post the results here tomorrow...

PostPosted: Fri Dec 07, 2007 10:09 am
by shawno
After the downgrade, I'm still seeing PRI REJECT FRAME messages in the CLI of Asterisk. Agents are still complaining that the calls are dropping periodically. I wonder if I have faulty hardware?

PostPosted: Fri Dec 07, 2007 12:45 pm
by mflorell
Can you post your PRI details?

Have you called your carrier?