vicidial.org

Started from this thread:
http://www.vicidial.org/VICIDIALforum/v ... php?t=6958

Goal:
Make ViciDial compatible with Asterisk 1.8, including all Manager, AGI and conf file changes.

Development Stages:
1. Add compatiblity with DAHDI channels - DONE
2. Add 1.8 Manager interface compatibility(send, listen, update)
3. Add 1.8 AGI compatibility
4. Add 1.8 conf file compatibility


Cost:
Estimated at 15 hours (USD $2700)

Pledged:
$ 100 - Trying
$ 500 - middletn
$ 200 - reyhc
$1000 - mudslide567
$ 400 - Noah

Status:
Code is present on dozens of our client systems and running very stable on all of them. SIP appears to be more compatible with some carriers than in Asterisk 1.4 as well. Vicibox 5.X series has Asterisk 1.8 included by default.

I will contribute $100

Wouldn't bother with 1.6, 1.8 then yes, if the hours are the same, happy to contribute $500

regards

Is there any updates about this?
I can contribute with $200, just let me know...

Thanks! I've added you to the list.

Has any progress been made to make Vicidial compatible with Asterisk 1.8. ? If not I would like to be a part of it and help with the programming if that's needed.

Which are the enhancements if upgrading asterisk to 1.8?

We will shoot for compatibility first, enhancements second.

Several core AMI changes have happened between 1.4 and 1.8, so a lot of testing will need to be done once we figure out all of the changes that need to be made.

At this point Asterisk 1.4.21.2 and 1.4.27.1 are both extremely stable across hundreds of servers, so we will expect that level of stability before we officially recommend using 1.8 in production after we are finished with compatibility changes. Keep in mind that it took Asterisk 1.4 over 3 years to get to that level of stability, and hopefully it won't take 1.8 that long.

we can help with both testing and money if needed. is the $2700 original amount for a bounty still what is being sought? we will put up a $1000 to get this completed and would be happy to help test.

Thank you very much! I will add you to the list.

I will post here when we have started work on this project, as well as when it is ready for testing. We should begin in the next few months.

I'm in for $400

Let me know...

Thank you very much, I have added you to the list.

Hello mflorell,

We are willing to put the $500 missing to complete the $2700, but we need to know by when you will be able to have this completed?
Although we are very familiar with the Vicidial source code and Asterisk in general; I'm convince that you will do that update much-much faster than us .
If it's possible for you to provide an approximate due date, and that date is adequate for our needs, then we will be more than happy about spending those $500.

Also, will that be like a patch that can be applied to current vicidial versions or it will be a new version that will require a clean install?

Thanks

We will need to confirm that the pledges are still interested, if you notice the first one is over 2 years old.

This would be a compatibility change made in vicidial at the svn/trunk level. It would not be a single patch because it will involve a lot of code changes.

Perfect!
Let us know the results of that confirmation...

Thanks

My $100 still stands

Hi there,

I have a code to make ViciDial 2.4 working with Asterisk 1.8

My company was testing it for a month but with light load (up to 5 agents) and it was fine. Next step is to move all agents to this new configuration.

I'd like to see others using this code before moving putting full load on new ViciDial installation.

Note: this code works only for external phones, but not phones generated by ViciDial. Changes were made on top of ViciDial version 2.4-324a

Here are steps to make it work:

************************************************************
Change to /etc/asterisk/extensions.conf file:

replace

********************************
; astGUIclient conferences
exten => _86000[0-4]X,1,Meetme,${EXTEN}|q
exten => _86000[0-4]X,n,Hangup
; VICIDIAL conferences
exten => _86000[5-9]X,1,Meetme,${EXTEN}|F
exten => _86000[5-9]X,n,Hangup
exten => _8600[1-2]XX,1,Meetme,${EXTEN}|F
exten => _8600[1-2]XX,n,Hangup
; quiet entry and leaving conferences for VICIDIAL (inbound announce and SendDTMF)
exten => _78600XXX,1,Meetme,${EXTEN:1}|Fq
exten => _78600XXX,n,Hangup
; quiet monitor-only extensions for meetme rooms (for room managers)
exten => _68600XXX,1,Meetme,${EXTEN:1}|Fmq
exten => _68600XXX,n,Hangup
; quiet monitor-only entry and leaving conferences for VICIDIAL (recording)
exten => _58600XXX,1,Meetme,${EXTEN:1}|Fmq
exten => _58600XXX,n,Hangup

; voicelab exten
exten => _86009XX,1,Meetme,${EXTEN}|Fmq
; voicelab exten moderator
exten => _986009XX,1,Meetme,${EXTEN:1}


***************************
with
***************************


; astGUIclient conferences
exten => _86000[0-4]X,1,Meetme(${EXTEN},q)
;exten => _86000[0-4]X,1,ConfBridge(${EXTEN},q)
exten => _86000[0-4]X,n,Hangup
; VICIDIAL conferences
exten => _86000[5-9]X,1,Meetme(${EXTEN},F)
;exten => _86000[5-9]X,1,ConfBridge(${EXTEN},a)
exten => _86000[5-9]X,n,Hangup
exten => _8600[1-2]XX,1,Meetme(${EXTEN},F)
;exten => _8600[1-2]XX,1,ConfBridge(${EXTEN},a)
exten => _8600[1-2]XX,n,Hangup
; quiet entry and leaving conferences for VICIDIAL (inbound announce, SendDTMF and ring-agent)
exten => _78600XXX,1,Meetme(${EXTEN:1},Fq)
;exten => _78600XXX,1,ConfBridge(${EXTEN:1},mq)
exten => _78600XXX,n,Hangup
; quiet monitor-only extensions for meetme rooms (for room managers)
exten => _68600XXX,1,Meetme(${EXTEN:1},Fmq)
;exten => _68600XXX,1,ConfBridge(${EXTEN:1},mq)
exten => _68600XXX,n,Hangup
; quiet monitor-only entry and leaving conferences for VICIDIAL (recording)
exten => _58600XXX,1,Meetme(${EXTEN:1},Fmq)
;exten => _58600XXX,1,ConfBridge(${EXTEN:1},mq)
exten => _58600XXX,n,Hangup

; voicelab exten
exten => _86009XX,1,Meetme(${EXTEN},Fmq)
; voicelab exten moderator
exten => _986009XX,1,Meetme(${EXTEN:1})

********************************

also replace

exten => 8369,3,AMD(2000|2000|1000|5000|120|50|4|256)
with
exten => 8369,3,AMD(2000,2000,1000,5000,120,50,4,256)

replace

exten => 8373,3,AMD(2000|2000|1000|5000|120|50|4|256)
with
exten => 8373,3,AMD(2000,2000,1000,5000,120,50,4,256)

replace

exten => 8375,3,AMD(2000|2000|1000|5000|120|50|4|256)
with
exten => 8375,3,AMD(2000,2000,1000,5000,120,50,4,256)


***********************************************************
***********************************************************

Change the file:
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl

Replace all function calls to "DeadAGI" with "AGI"

***********************************************************

replace files:
/usr/share/astguiclient/AST_conf_update.pl
/usr/share/astguiclient/AST_manager_listen.pl
/usr/share/astguiclient/AST_update.pl

Added Nov 16, 2011:
Please, review Issue Tracker case #0000521. I have no permission to publish links.

Publish in the VICIDIAL Issue Tracker *link at top of this screen*.

It allows linked documents. Then you can put a link to that post in here and those interested can download the links.

Thanks lytnev, those are good news...

I will test it with a client we have that has around 15 agents. It will also be a server on the cloud, so I will post the results of that combination (asterisk 1.8 + virtual server)...

Thanks.

has anybody got documents on how to do this yet? i have tried the method in the issue tracker but once i have installed asterisk 1.8 and changed the files mentioned i recieve the following problem

SIP phone connects to vicidial box (SIP registered)

but when i login the agent screenthe softphone doesnt ring and i recieve a time sync message.

has anybody got info(documents) how to install this and config it from scratch ie (asterisk install/dahdi install/changes to vicidial) also when installing asterisk 1.8 do i press Y to sample files or just install the standard 1.8 without them (make samples)

Thanks in advance

Mark

Mark,

This set of updates only works if you are using external agent phone extensions (extensions sitting on another Asterisk server), but not extensions generated by ViciDial locally.

I did not have time to fix the ViciDial scripts that generate SIP and IAX2 extension configuration files, but those should be changed to be compatible with Asterisk 1.8

I do not have time right now to fix it, but I'll work on it later.

PS: This is a project board. It is for tracking those who have committed funds to complete this task. If you want support, post your request on the support board instead.

Please read the sticky before posting in each board (even a reply to a previous post needs to follow the purpose of the board it is on!)

I'm in the process of rewriting the Perl scripts to bring them up to current coding standards. My goal is to make them cleaner, more maintainable, and more efficient as well as make whatever changes are needed to work with 1.8.

I don't have a lot of free time, so progress is slow, but if anyone wants to test what I have so far, you can find them here.

Vicidial.pm
http://www.vicidial.org/VICIDIALmantis/view.php?id=535

ADMIN_restart_roll_logs.pl
http://www.vicidial.org/VICIDIALmantis/view.php?id=536

you should start a post in support or features linked to this post with this cool stuff on it! read the stickies. this board is for those wanting to pledge money against projects for The Vicidial Group to complete. Exclusively. That's all it is for.

I LIKE that The Vicidial Group lets us use this board for free ... let them have their section of it (ie: THIS section!)! and abide by the stickies/rules. Please.

Matt,

What are the statuses of the pledges and the project? The GoAutoDial team is pledging $500 for this endeavor.

We have confirmed most of the pledges, and we intend to start on this project after branching 2.4, which we have scheduled for February. So, as long as we don't get swamped again, this will be made a priority development project in March.

Would it be safe to say that more people pledging would cause more man-hours sooner (ie "Help this along")?

At this point not really. I don't want to add Asterisk 1.8 support before branching 2.4 because it will start as experimental, and that really belongs in trunk and would greatly delay branching of 2.4. Right now the most important project we have is branching 2.4, it is well overdue, as is the update to the manuals that goes with branching 2.4.

Of course, pledging more money would always be nice, after looking into some of the 1.8 issues we will have to deal with I have a feeling that we will run past our original estimates.

does 1.8 use conf bridge or is that only 11? I need conf bridge. There is little else I would see the need to upgrade asterisk for?

are there any major benefits to running on 1.8?

We will still use meetme even with Asterisk 1.8.

Once we have everything working we can look at conf_bridge, but a lot of changes will need to be made for vicidial to change to conf_bridge.

I don't think he was suggesting the use of conf_bridge, just that it is available in 1.8 and he wants it in his phone system. Then he wanted to know if there was any OTHER benefit besides conf_bridge availability.

There are several new features in Asterisk 1.8, like better SIP compatibility. We don't have it in production yet, and we have only been concentrating on getting Vicidial working, so we really haven't had a chance to try out the other new features and see how well they work.

The changes to Vicidial have just been committed for Asterisk 1.8 support. This is in the BETA testing phase currently, and is not recommended for use in production at this time. While we have performed a lot of testing, we have not tested this in production, so you have been warned.

If you choose to upgrade an existing system, please make note of the many conf file changes(extensions.conf and manager.conf) that will need to be made for Vicidial to function properly while interfacing with Asterisk 1.8. Also, make sure that the Admin -> Servers -> modify server "Asterisk Version" setting is set properly for the version you have installed on that server.

To download a version of Asterisk 1.8 that we are working from, go to:
http://downloads.vicidial.com/beta-apps/

To download the Vicidial code changes, just upgrade or download the latest svn/trunk snapshot.