2.2.0 Release Candidate 3 is Out!

[mflorell]

We just posted 2.2.0 RC 3 to sourceforge

https://sourceforge.net/projects/astguiclient/files/


Please test it out if you can and we should be able to do a full release in the next few days.


There are more changes relating to logging, as well as some additional script/webform variables added and other small bug fixes since RC 2.

Here is a list of the rest of the changes since 2.0.5:

http://www.vicidial.org/VICIDIALforum/v ... php?t=9854

[gmcust3]

I already have 2.0.5

I used the way u showed once on how to update using svn.

But I tried that and when i saw , it DIDNT replace the files under html.

Do I need to copy it from somewhere ?

[Alek]

Just installed Vici 2.2 rc3 at the clients. CentOS 5.4 64 bit OS. Server is controlled by C-Panel and I never had a chance to use C-Panel before. It was a challenge to get web server going (local admin helped out). Another big challenge was perl libraries. Without complete CPAN install was getting error message "There is a time synchronization problem with your system, please tell your system administrator." Installed perl components and message is gone, hopefully C-Panel will not revert to original libraries. After installation the only problem I found - all user extensions cc100 to cc400 had Asterisk Server IP 10.10.10.15. And I am sure I corrected IP to my server when running installation scripts. Overall was very easy install. Matt,thanks for good documentation.

[Michael_N]

Alek:

CentOS is not recommended to use with vicidial

http://download.vicidial.com/centos/README

[Alek]

Thanks for the note. It was my first install in past year. Lots change. I used to do VicidialNow. It is such an easy install. ANd if I remember correctly it was on CentOS. So when customer told me they have CentOS box I did not argue. It may even be better. The guy who order me an install did not pay in full. He changed all passwords on application and on the server.

[shariq]

Matt,

I downloaded 2.2.0 RC2, in which when i opened the SCRATCH INSTALL file. I found the this

This document will be depricated and not supported after the 2.2.0 release.

What does it mean??
Can we expect a big change after 2.2.0 in ViciDial

[mflorell]

Nothing like that, it just takes a lot of time to keep the SCRATCH_INSTALL doc updated, and since we haven't used it ourselves in about 2 years it doesn't make much sense to maintain. At this point all of our installs are automated with either Vicibox under Ubuntu or OpenSuSE.

[Trying]

What will really be AWESOME is a "more or less" automated Vicibox install off the CD. Prompting you during the installation for the server IP for MySQL, Webserver, additional Asterisk/Vicidial servers and recorders. Is this at all possible?

[Trying]

Sorry, what I meant is an automated install on a load balanced setup.

[mflorell]

We are working on that with the opensuse installer

[alkinjay1]

Hey Matt,

Are you planning on putting out any more release canidates or is it safe to put 2.2 into production?

[mflorell]

we are planning at least a couple more RCs to fix some minor bugs. Of course 2.2.0rc3 is safe for production as it is, the changes will be fairly minor in the official release when it comes out, and you could do an in-place upgrade because of this.

[Geil21]

With respect to the call progress codes....

Will this make ViciDial able to dispo out more of the disconnected numbers?

The biggest problem we currently have with 2.0.5 (and all prior versions) is the inability to detect those disconnected numbers while using PRIs or SIP

I have found in the past by monitoring, that we get the dis progress code and the recording from the telco is playing but vici still thinks it's ringing. Does this latest change fix that?

We currently have hundreds of thousands of NAs that we just can't get contact on, but we don't want to dump them all because there are definitely sales in there.

In fact on Friday night when I only had 2 agents working remotely, I was able to get the sales by setting the dial level to 50 with only those leads in the mix, but I just can't do that during normal hours because I just don't have the lines to support it.

I fix in Vici for this one problem would be huge, it's the only short-fall that Vici has as far as the owners are concerned.

[mflorell]

This issue is related to Asterisk's lack of call progress detection as well as the inconsistency of carriers sending proper disconnect codes(up to 30% are inaccurate). What we recommend is the Sangoma CPA(Call Progress Analysis) gateway that is paid-for software but it does a wonderful job of detecting pre-Answer codes as well as Answering Machines and Fax Machines that Asterisk has trouble with.

ViciDial fully integrates with Sangoma CPA and we are resellers of it.

[Geil21]

Yeah, I was aware of the Sangoma CPA app, but during a prior conversation with someone in your office I was told it only works with SIP, and my office uses PRIs on Digium Cards so I guess we are stuck. I see no other reason to upgrade at this time, we'll wait for the final release.

Thanks for all of your help tho Matt. You should stop by sometime if ever you are up on this end of the I4 corridor =)

[mflorell]

We have clients with only PRIs that use a relay Asterisk server to bounce the calls as SIP back to the server that has the PRIs on it. It works just fine.

[mxtreme311]

Is 2.2.0 almost ready for final release?

[mflorell]

We are getting close, just fixes a bunch of small bugs in the last couple days, should have RC4 out tonight.