2.2.0 Release Candidate 6 is Out!

Any and all non-support discussions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

2.2.0 Release Candidate 6 is Out!

Postby mflorell » Tue Mar 02, 2010 9:22 am

We just posted 2.2.0 RC 6 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 soon.

There are several bug fixes, one very important one is the change in voicemail configuration, please read below. Another change is in agent selection when doing AGENTDIRECT transfers, we changed to an AGENTS link instead of clicking on the number-to-dial field.

Changed voicemail auto-config to use voicemail.conf directly because include
files are not fully supported in voicemail.conf. If you have any custom
voicemail boxes that are NOT defined in ViciDial then you need to put
them in a custom context above the [default] context in voicemail.conf
in order to keep them. This change will update the ViciDial database if
the user changes their voicemail password through their phone. If that
user also uses that phone entry to login to vicidial.php that password
will be changed as well.

Remember that in 2.2.0 you can define Voicemail boxes by themselves right in the Admin interface(Admin -> Voicemail) without having them associated to a phone record.


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

http://www.vicidial.org/VICIDIALforum/v ... php?t=9854
Last edited by mflorell on Sun Mar 21, 2010 8:12 pm, edited 1 time in total.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mxtreme311 » Thu Mar 11, 2010 2:25 pm

We've been using 2.2.0 RC 6 on one of our installations since monday, and are running into a problem. About halfway through the day the update process start timing out with this error:

command timed-out at /usr/share/astguiclient/AST_update.pl line 442

If we restart the server the problem goes away. Any ideas?
mxtreme311
 
Posts: 93
Joined: Thu Jun 29, 2006 11:49 am

Postby mflorell » Thu Mar 11, 2010 6:39 pm

Asterisk version?

manager.conf file contents?
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mxtreme311 » Fri Mar 12, 2010 1:09 am

using asterisk 1.4.22.2 the current DAHDI package, and the manager.conf file is the one from the sample configs in the vicidial package... I'm gonna give 1.4.27 a shot and see what happens. Something somewhere is eating up all the memory on the server and this error starts to happen when the physical memory is all consumed.
mxtreme311
 
Posts: 93
Joined: Thu Jun 29, 2006 11:49 am

Postby vkalp_rg » Fri Mar 12, 2010 3:18 am

Hi Matt,
Is it possible to add Time field as well in the reports. e.g. in the
INBOUND REPORT or the Inbound SL Report, you have added a drop down calender feature to choose FROM and TO fields, do you feel you can also give us an option to put in From Date and TIme and TO date n time.

This way if I need to find out how much is my Service Level In last 3 hours then i can simply put in Mar 12 09:00 hrs till Mar 12 12:00 hrs.

Thanks. great work with 2.2 and m still testing rc4 and its running fine.

RG
vkalp_rg
 
Posts: 57
Joined: Thu Sep 17, 2009 5:35 am

Postby mflorell » Fri Mar 12, 2010 1:04 pm

Please start a new topic in features for that, and add a ticket to the issue tracker for a feature request if you get a chance.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mxtreme311 » Fri Mar 12, 2010 2:49 pm

asterisk 1.4.27 doesn't seem to be helping. it certainly seems like a memory leak somewhere. We get about 4 -5 hours of dialing in before we have to restart the server...
mxtreme311
 
Posts: 93
Joined: Thu Jun 29, 2006 11:49 am

Postby mflorell » Fri Mar 12, 2010 5:36 pm

We have the same code running at over a dozen client sites without any reporting this issue, so I'm not sure what to say.

How did you install ViciDial the first time?

Linux distro?

CPU/RAM specs?
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mxtreme311 » Tue Mar 16, 2010 9:18 am

standard Debian setup, same as all the rest of my dialers... it's a Intel Core 2 Quad with 4 GB RAM. A 1 TB hard drive for the system and a SSD for the recordings... I might switch back to asterisk 1.2.x and see if that corrects the problem. Maybe 1.4 just can't handle this...
mxtreme311
 
Posts: 93
Joined: Thu Jun 29, 2006 11:49 am

Postby mflorell » Tue Mar 16, 2010 12:04 pm

we have installed hundreds of systems over the last year that all run 1.4.21 and ViciDial and we have not seen this problem, so I don't think it's an issue of 1.4 not being able to handle it.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mxtreme311 » Mon Mar 22, 2010 12:03 pm

Could it be recording all the calls?
mxtreme311
 
Posts: 93
Joined: Thu Jun 29, 2006 11:49 am

Postby Michael_N » Mon Mar 22, 2010 12:03 pm

mxtreme311 wrote:Could it be recording all the calls?


yes it can
Michael_N
 
Posts: 687
Joined: Wed Jul 05, 2006 3:13 pm
Location: sweden


Return to General Discussion

Who is online

Users browsing this forum: Google [Bot] and 124 guests