vicidial.org

Hello,

What is the normal process after an install of v1.3 (latest stable).

-Do you guys update or upgrade or do a "yum update"?
-Do you setup the ntpd?
-Do you update Asterisk 1.2 to 1.4 or 1.6?
-Do you update vTiger?

Most of all Asterisk 1.2 just has me bugging a bit.

I understand that version SVN 2.2 is still in beta?

Thanks

Version 2.2.1 has been a final release for several months now, and it is the default install on the ViciBox ISOs.

Also, we use Asterisk 1.4.27.1 on the ViciBox ISOs.

ViciDial is not compatible with Asterisk 1.6. Mostly because Digium has slated it for no further support in a few months.

Well, I just downloaded the latest version the other day and it tells me it has Asterisk 1.2 installed. Can you please post your link as to where you get your .iso?

Also, is there a process to upgrade this or is it better to download 2.2 from right place?

The page for vicidialnow is throwing me off as it shows 2.2 as beta.

***Is it okay to do yum update after install?

Thanks

ViciDialNow and ViciBox are different things. ViciBox is the official ViciDial ISO, ViciDialNow is supported by another company.

The vicibox website is http://www.vicibox.org

if you must have CentOS, you must have VicidialNOW (which is a bit behind in the version of Vicidial being installed, but can be upgraded).

For everyone else:

If you want the latest Greatest (and supported) version of Vicidial, start with Vicibox.com. It can install the latest release (2.2.1) or the latest developmers version (2.4, which is actually quite stable and in use in many centers).

PS: I don't work for either one, I'm just a technician who works on this stuff a lot.

Asterisk 1.2.30.X runs quite good. What's bugging you about this "old" version?

Yes you can do a "yum update" on your VicidialNOW system and it will update the base system (not including Asterisk and Vicidial). Just remember to boot back to the default VicidialNOW kernel if you don't want to manually recompile Zaptel.

gardo wrote:Asterisk 1.2.30.X runs quite good. What's bugging you about this "old" version?

LOL

I love 2.0.5, and I love CentOS (my first Linux systems were ALL CentOS). But ... I don't have many clients on it and honestly (my opinion) i think it should only be used for those who MUST be in the RedHat Zone for some reason.

The Vicidial Group runs this show, and they are on OpenSuSE. So we go to OpenSuSE (especially since there is no need for an upgrade after the installation).

Now ... if you were to publish a new one with 2.4 and an updated "pretty screen" ... you'd at least even the odds a bit.

hmmm...I came to this forum from vicidialnow site. So, I guess things are a bit mixed up. All right, I will try vicibox even though, I never played with OpenSuSE.

1- By no need to upgrade you mean it's already the latest version or that there is something built in that upgrades automatically?

2- Vicidial now seems to be more aesthetically presentable than regular vicidial. Is vicibox the same?

thanks

It will install (native) 2.2.X but offer to install SVN 2.4.X.

2.2.X is latest stable release, 2.4.X is developer (also presently quite stable and in use all over the place, but has some cool toys in it).

VicidialNOW has a Custom agent screen and a Private Label landing page on the root.

The custom agent screen has not been updated beyond 2.0.5, but 2.0.5 is no longer supported. the custom agent screen, however, is usable on any version of 2.0.5 and if it is updated will (in theory) be usable on any VICIdial that matches the version it's built for (VicidialNOW does not privatize the code or in any way segregate it from the main VICIdial branches, it merely allows it to run on CentOS and gardo also found a nice screen to include).

So ... if you want to use the cool screen you are stuck with 2.0.5 (any flavor). If you can part from the cool screen, you can upgrade vicidialnow to 2.2.X or 2.4.X via SVN ~OR~ you can install Vicibox Redux (presently at 2.0.2) which will install as I stated earlier.

Of course, if you're good ... YOU could upgrade that screen (do a "diff" on the 2.0.5 regular screen to the cool one and then apply the changes to the 2.4.X regular screen to get a cool 2.4.X version ... then post it back here !!)

I do not (BTW) recommend the custom landing page on the root unless you exclude yourself with a robots.txt to keep out google and similar for all other engines. You do not want anyone to know you have a "stock" dialer that may have "stock" passwords, stock ports, or ANYthing like that. It's an invitation for SSH brute force, SIP, IAX account theft. All sorts of stuff. Better to have a root web page that is just apache and does NOT link to your Vici stuff directly or obviously. (Or at all, your agents should have the link instead of needing an FQDN to go to)

But that's me. (I'm the guy they call when the firewall is broken and they're in a panic, understandably)