ViciBox v.5.0 Bug Fixes - Updated Oct 14 2013

[Kumba]

This thread will contain gotchas, patches, bugs, and other useful information related to ViciBox v.5.0 installs. The steps assume you are already logged in as the root user and sitting at a shell prompt.


ViciBox v.5.0.0 and under database priviledges for vicibox-upgrade to run:
1) mysql
2) use asterisk;
3) grant create,alter,index, on <database>.* to '<customuser>'@'localhost' identified by '<custompass>';
4) exit

If you are using the stock vicidial credentials then the above SQL would look like as follows:
3) grant create,alter,index on asterisk.* to 'custom'@'localhost' identified by 'custom1234';

UPDATE: ViciBox v.5.0.1+ has changed the default behaviour of vicibox-upgrade. It will now attempt to connect as the root user. If you have a root password set on your database you can set it with the flag --sqlrootpass=<PASSWORD>. You can also disable the root password behaviour and have it attempt the upgrade with the custom user by using the --non-root flag.


---------


ViciBox v.5.0.0 and under slave replication privileges for vicibox-install DB slave setup to work:
1) mysql
2) use asterisk;
3) grant replication slave,replication client,select,reload on *.* to '<slaveuser>'@'%' identified by '<slavepass>';
4) exit

If you are using the stock ViciBox credentials then the above SQL would look like as follows:
3) grant replication slave,replication client,select,reload on *.* to 'slave'@'%' identified by 'slave1234';


----------


ViciBox v.5.0.0 and under vicibox-upgrade primary DB slave credentials backwards in vicibox table
1) mysql
2) use asterisk;
3) update vicibox set field8='<slaveuser>', field9='<slavepass>' where server_type='Database' and field1=0;
4) exit

If you are using the stock ViciBox credentials then the above SQL in step 3 would look like as follows:
3) update vicibox set field8='slave', field9='slave1234' where server_type='Database' and field1=0;


---------


Only the ViciBox v.5.0.0 installer and upgrade WILL FAIL if it cannot connect to the IP discovery script located at http://www.vicidial.org/yourip.php. If your router/firewall/whatever is configured to give some sort of a browser friendly warning page this will be erroneously inserted into the vicibox table. It is recommended that you allow the web and telephony servers to contact the above address prior to doing an install. You can use wget to make sure it returns your IP successfully. ViciBox v.5.0.1 and greater will automatically fail if it finds an IP address returned that doesn't validate correctly. Will probably add a --skip-external flag to both scripts to skip the external IP check too.

UPDATE: There is a flag added to the installer and upgrade to skip external IP checks. This is not recommended but it will do it. Also added data scrubbing to the external IP. The flag is --skipexternal to not do the IP check.


---------


ViciBox v.5.0.0 Only!!! - Missing symlinks and wrong manager and extensions copied from installer
1) mkdir /var/lib/asterisk/agi-bin
2) ln -s /var/lib/asterisk/agi-bin /usr/share/asterisk/agi-bin
3) ln -s /var/lib/asterisk/sounds /usr/share/asterisk/sounds
4) ln -s /var/lib/asterisk/moh /var/lib/asterisk/mohmp3
5) cp /usr/src/astguiclient/trunk/docs/conf_examples/extensions.conf.sample-1.8 /etc/asterisk/extensions.conf
6) cp /usr/src/astguiclient/trunk/docs/conf_examples/manager.conf.sample-1.8 /etc/asterisk/manager.conf

If you have already attempted an install of ViciDial before running this bugfix, you will also need to do the following:
1) cd /usr/src/astguiclient/trunk
2) perl install.pl (hit enter to everything, we just want it to re-copy the AGI's back in place)


----------


ViciBox v.5.0.1 and under - Permission on /var/lib/asterisk not allowing apache to access it ***** THIS WAS WRONG PREVIOUSLY! THE BELOW COMMAND IS RIGHT! ***** Updated Aug 6th
1) chmod 755 /var/spool/asterisk


----------


ViciBox v.5.0.2 and under - A server deployed as an archive will not allow writing since it's chroot'd. This does not effect databases, telephony, or web servers.

1) echo "allow_writeable_chroot=YES" >> /etc/vsftpd.conf
2) rcvsftpd restart


----------


ViciBox v.5.0.3 and under - The previous packman repository has decided to go unreachable and hasn't shown signs of coming back anytime soon. So we change it to use a different packman repo.

1) sed -i '/baseurl/c baseurl=http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_12.3' /etc/zypp/repos.d/packman_12.3.repo
2) zypper refresh

[ianz2k7]

Hi Kumba,

I just installed the new Vicibox 5 Preload iso, and I got a problem.
How do I integrate Vtiger510 to the vicibox?

My Vtiger IP Address: 211.208.15.21
My Vicibox IP Address: 125.22.102.82

They are separated, how do I make this one?

Thanks!

[williamconley]

How do I integrate Vtiger510 to the vicibox?

They are separated, how do I make this one?

read this file on your server if it exists:

/usr/src/astguiclient/trunk/docs/VTIGER.txt

[Kumba]

We gave up on integrating VTiger as it was just a nightmarish pain all the way around. The integration has also not been kept up with. But if you want to attempt it, you would need to read the VTIGER document like William pointed out.

[vccsdotca]

I loaded up the V5 ISO and encountered some issues with asterisk. When logging in as an agent the audio files such as *-onlyperson.gsm was showing as unable to locate file in any format. Checked it out for a while and there was no permission issues, it looks like asterisk 1.8 was trying to pull the audio from a store that was not /var/lib/asterisk/sounds.

As well it tried to locate the agi for "Send DTMF" (also failed as shown in the CLI) which must have been renamed because the pointer path file name doesnt exist server wide.

This was done with the default ISO with 3 different attempts.

Additionally, with version 4 and 5 VICIdial will recognize a Sagnoma USB timer and install the driver, how ever it does not function at all. On v5 I was able to read the device at least as loaded (unable to test because of above issues) but it causes an issue in the v4 code where by you need to physically remove the device. I suspect most of this is in part that the driver is not compatible with DAHDI 2.6 which is the base on both v4 & 5. I assumed vici had a work around since it is a default install on detection. Is there any insight into this please?

Thank you all.

[Kumba]

I loaded up the V5 ISO and encountered some issues with asterisk. When logging in as an agent the audio files such as *-onlyperson.gsm was showing as unable to locate file in any format. Checked it out for a while and there was no permission issues, it looks like asterisk 1.8 was trying to pull the audio from a store that was not /var/lib/asterisk/sounds.

As well it tried to locate the agi for "Send DTMF" (also failed as shown in the CLI) which must have been renamed because the pointer path file name doesnt exist server wide.

This was done with the default ISO with 3 different attempts.

Additionally, with version 4 and 5 VICIdial will recognize a Sagnoma USB timer and install the driver, how ever it does not function at all. On v5 I was able to read the device at least as loaded (unable to test because of above issues) but it causes an issue in the v4 code where by you need to physically remove the device. I suspect most of this is in part that the driver is not compatible with DAHDI 2.6 which is the base on both v4 & 5. I assumed vici had a work around since it is a default install on detection. Is there any insight into this please?

Thank you all.

Yeah, read the first post in this thread. It contains the fixes you need to run on V.5.0.0 including the symlinks that need to be created so that the sounds and AGI directories can be found. If you didn't run those fixes, then your system will not work.

And yes, you need to call Sangoma and ask them when they will support DAHDI v.2.6 with their VoiceTime modules. If someone wants to port the code to run reliably on DAHDI v.2.6 when I can include it but at the time we have neither the time nor interest in doing that ourselves. Wanpipe also does not work because it doesn't support Kernel v.3.7. This was all covered in previous posts regarding ViciBox v.5. We recommend you look at a Digium card of the Amfletec PCI-Express timers if you want something that works out of the box with ViciBox v.5.0.

ViciBox v.5.0.1 is being copied with all the fixed that were v.5.0.0 related to the web server as I post this. It includes all those fixed already plus a few updates to vicibox-upgrade in regards to databases and both upgrade and install in regards to external IP checking.

[DefLeppard]

I just downloaded and installed Vicibox 5. When the agent logs in, their phone is never called. How do I fix this?

[williamconley]

1) is their phone registered?

2) phone brand?

3) asterisk cli output from an example?

[DefLeppard]

1) Yes. I am registered and am able to place calls with no problem directly from the phone.

2) Twinkle. I don't think it has anything to do with the phone.

3) There is no cli output. The IP addresses are all right, screen -ls shows 11 screens. Everything seems normal until I try to login as as an agent. FYI, the server has a local IP with DMZ. No reason for it to not work though.

Any help would be appreciated.

[williamconley]

1) Yes. I am registered and am able to place calls with no problem directly from the phone.

A fast answer to that makes me nervous: to be clear it is not evidence of registration that you can call out. Try "sip show peers" and actually verify registration for the phone.

Also: Is this an "on-hook" phone? (check for this setting in the phone definition).

[DefLeppard]

It is registered for sure. Like I said before, I am able to call from/to the soft phone with no issues.

It is not an on-hook phone.

[DefLeppard]

Just to be clear, Vicidial never calls the extension.

[DefLeppard]

Is it possible to move back to Asterisk 1.4 instead of 1.8? Some insight from Kumba would be nice

[Kumba]

I just downloaded and installed Vicibox 5. When the agent logs in, their phone is never called. How do I fix this?

You didn't bother to run any of the bug fixes in the first post of this thread. Run all the bug fixes, reboot the server, and it should work. This issue is related to the bug fixes where directories are in different locations and the wrong manager and extensions configuration file were copied over. It's like the fifth thing in the bug fix thread.

Alternatively, you can download ViciBox v.5.0.1 which has all of these fixes in it and start over if you want.

[Kumba]

Is it possible to move back to Asterisk 1.4 instead of 1.8? Some insight from Kumba would be nice

You can if you want. Although 1.8 works better then 1.4 in most situations in our testing. Crashes less, load spikes less, better SIP support, and it's not End of Life.

But just use zypper to remove the asterisk-whatever packages, remove the 1.8 repo, and then add all the asterisk- packages back (which will be 1.4). You'll then need to change the config files back to being asterisk 1.4.

[DefLeppard]

Do you have any ideas why I would have the problem I am having? I don't care about the Asterisk version as long as it works.

[Kumba]

Do you have any ideas why I would have the problem I am having? I don't care about the Asterisk version as long as it works.

Cause you didn't run the bugfix that I already told you to run? Your install has the wrong manager.conf installed. The fifth item in the first post addresses that. You might also want to run the other bugfixes too unless you just want to find them as you go along. Kind of like an easter egg hunt.

If you are not comfortable doing any of the patches, just download ViciBox v.5.0.1 and reinstall. It already has them all applied.

[DefLeppard]

It worked! I am kicking myself now!

Thanks Kumba.

[vccsdotca]

Yeah, read the first post in this thread. It contains the fixes you need to run on V.5.0.0 including the symlinks that need to be created so that the sounds and AGI directories can be found. If you didn't run those fixes, then your system will not work.

And yes, you need to call Sangoma and ask them when they will support DAHDI v.2.6 with their VoiceTime modules. If someone wants to port the code to run reliably on DAHDI v.2.6 when I can include it but at the time we have neither the time nor interest in doing that ourselves. Wanpipe also does not work because it doesn't support Kernel v.3.7. This was all covered in previous posts regarding ViciBox v.5. We recommend you look at a Digium card of the Amfletec PCI-Express timers if you want something that works out of the box with ViciBox v.5.0.

ViciBox v.5.0.1 is being copied with all the fixed that were v.5.0.0 related to the web server as I post this. It includes all those fixed already plus a few updates to vicibox-upgrade in regards to databases and both upgrade and install in regards to external IP checking.[/quote]


Looks good, thank you for the feedback.

[ciacho]

Problem with recordings - ViciBox v.5.0.1
1 server installation
VERSION: 2.8-408a
BUILD: 130711-2208
Apache/2.2.22 (Linux/SUSE)

When I tried to download recordings I got information:

Code: Select all

(13)Permission denied: access to /RECORDINGS/MP3/20130806-082239_XXXXXXXXXXX_1007_TEST_5998-all.mp3 denied

Admin/Servers
Server IP Address: 192.168.10.2
Recording Web Link: SERVER_IP

Admin/System Settings
Central Sound Control Active: 1
Sounds Web Server: 192.168.10.2

Code: Select all

crontab -e
....
### recording mixing/compressing/ftping scripts
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --MP3
#0 1 * * * /usr/share/astguiclient/AST_CRON_audio_4_ftp2.pl --ftp-server=server.ip --ftp-login=user --ftp-pass=pass --ftp-directory=/ --ftp-persistent --ftp-validate --trans$
....


Code: Select all

cat /etc/apache2/conf.d/viciarchive.conf
Alias /archive/ "/home/archive/"

<Directory "/home/archive">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
        <files *.mp3>
                Forcetype application/forcedownload
        </files>
</Directory>

Code: Select all

cat /etc/apache2/conf.d/vicirecord.conf
Alias /RECORDINGS/ "/var/spool/asterisk/monitorDONE/"

<Directory "/var/spool/asterisk/monitorDONE">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
        <files *.mp3>
                Forcetype application/forcedownload
        </files>
</Directory>

Code: Select all

chmod -R 777 /var/spool/asterisk/monitorDONE/
ls -al /var/spool/asterisk/monitorDONE/
total 560
drwxrwxrwx  9 wwwrun   root       4096 Aug  6 09:43 .
drwxr-x--- 10 asterisk asterisk   4096 Aug  3 17:11 ..
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 FTP
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 FTP2
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 GSM
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 GSW
drwxrwxrwx  2 root     root     270336 Aug  6 09:43 MP3
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 OGG
drwxrwxrwx  2 root     root     266240 Aug  6 09:43 ORIG


Slowly, I'm running out of ideas on what could be the problem. Do You have any solution?

[Kumba]

Try dunning 'chmod 755 /var/spool/asterisk' and see if that fixes it. If that does then I need to take a look at ViciBox v.5.0.1 cause I already included that fix. If not then I'll have to try and duplicate it.

[Kumba]

My bad, looks like I flubbed up that fix in 5.0.1. I had chmod 755 /var/lib/asterisk. It should be chmod 755 /var/spool/asterisk. The issue is that apache didn't have read permissiong all the way through the directory tree. So it would give up a 403 error. Just by allowing group and global read/execute permissions to /var/spool/asterisk apache can now read through that directory and get at the files.

I updated the patch thread above

[Kumba]

I released 5.0.2. It fixes the following:

using the right database connection in vicibox-upgrade.pl to enable the slave setup.
Added hostname scrubbing to both the install and upgrade script. Had someone with a hostname of 'db1.vici.local' and a domain of 'somewhere.com'. That was a first in 4+ years.
Corrected the chmod for /var/spool/asterisk
Upgraded to vicidial trunk SVN 2011

That should round out the last bit of known bugs. Until I find more.

[ciacho]

Thanks Kumba!

Now all working great.

[bronhelstrom]

The 5.0.2 preload (ViciBox5.x86_64-5.0.2.preload.iso but likely all the Vicibox 5 preloads) do not work on a fresh install. It boots from the ROM and sees the two SCSI RAID drives ("/dev/disk/by-id/scsi-xxxxx") with the size of the array, but when it tries to delete the data and load the OS it sees 0 Mbyte and says "not enough space available for this image".

Thinking it was a hardware problem, I tried to reseat everything and played with BIOS settings but always the same results. Finally I took an Ubuntu 12.04 distro that I had in my CD ROM binder and it loaded properly. I tried Vici 5.0.3 again thinking it might just be having issues partitioning but it gave me the same result. I went back to Vicidial preload 4.0.3 (ViciBox5.x86_64-5.0.2.preload.iso) and that installed properly.

I am using a Dell CS24-SC server with 4 x 140 Gbyte SAS in two mirrored RAID 1 arrays.

[williamconley]

turn off your raid and see if it works. raid is a known problem for all linux distros as the linux drivers often don't recognize the raid.

also, sometimes it works to delete all partitions with a 3rd party disk and then let the vicibox iso partition cleanly.

[bronhelstrom]

I tried turning off RAID but I got the same result. I was able to install 4.0.3 preload but not 5.0.2 on the same server. Something must have changed in the basic installation.

[williamconley]

in that case, install 4.0.3 and be happy or get a nice SSD and install on that. but if you have a specific error or fix for the RAID, let kumba know. given the odds, though, it's the SuseStudio base .iso that does not like your RAID.

[Kumba]

Try the LiveCD. The Preload is known to be finicky with hardware.

Otherwise, you would need to send us the server. We don't buy and test on all hardware bases unfortunately.

[tick]

Problem with recordings - ViciBox v.5.0.1
1 server installation
VERSION: 2.8-408a
BUILD: 130711-2208
Apache/2.2.22 (Linux/SUSE)

When I tried to download recordings I got information:

Code: Select all

(13)Permission denied: access to /RECORDINGS/MP3/20130806-082239_XXXXXXXXXXX_1007_TEST_5998-all.mp3 denied

Admin/Servers
Server IP Address: 192.168.10.2
Recording Web Link: SERVER_IP

Admin/System Settings
Central Sound Control Active: 1
Sounds Web Server: 192.168.10.2

Code: Select all

crontab -e
....
### recording mixing/compressing/ftping scripts
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --MP3
#0 1 * * * /usr/share/astguiclient/AST_CRON_audio_4_ftp2.pl --ftp-server=server.ip --ftp-login=user --ftp-pass=pass --ftp-directory=/ --ftp-persistent --ftp-validate --trans$
....


Code: Select all

cat /etc/apache2/conf.d/viciarchive.conf
Alias /archive/ "/home/archive/"

<Directory "/home/archive">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
        <files *.mp3>
                Forcetype application/forcedownload
        </files>
</Directory>

Code: Select all

cat /etc/apache2/conf.d/vicirecord.conf
Alias /RECORDINGS/ "/var/spool/asterisk/monitorDONE/"

<Directory "/var/spool/asterisk/monitorDONE">
    Options Indexes MultiViews
    AllowOverride None
    Order allow,deny
    Allow from all
        <files *.mp3>
                Forcetype application/forcedownload
        </files>
</Directory>

Code: Select all

chmod -R 777 /var/spool/asterisk/monitorDONE/
ls -al /var/spool/asterisk/monitorDONE/
total 560
drwxrwxrwx  9 wwwrun   root       4096 Aug  6 09:43 .
drwxr-x--- 10 asterisk asterisk   4096 Aug  3 17:11 ..
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 FTP
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 FTP2
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 GSM
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 GSW
drwxrwxrwx  2 root     root     270336 Aug  6 09:43 MP3
drwxrwxrwx  2 root     root       4096 Aug  3 17:11 OGG
drwxrwxrwx  2 root     root     266240 Aug  6 09:43 ORIG


Slowly, I'm running out of ideas on what could be the problem. Do You have any solution?

Next time :

Code: Select all

chown -R wwwrun:root /var/spool/asterisk/monitorDONE/

[Kumba]

The bugfix for the recordings was already addressed in the first post. It's a permission issue not a user/group issue.

[adymeblack]

I just installed v5.0.3 and i am having some issues.

I'm going to run some of the bug fixes posted at the top, but would like a bit of clarification before i proceed. Will i only need to run the packman repo fix since it is the only entry listed at my current version or do i need to run through all of them?

[williamconley]

You only need to fix the ones that annoy you for some reason. Most of the others have been resolved in 5.0.1,5.0.2 or 5.0.3.

As far as I know, the asterisk version in admin->servers is possibly still 1.4 instead of 1.8 (check your asterisk installed version ... and be sure it's right). But the rest have been resolved (which is why .0.1,.0.2,.0.3 were released ... bug fixes!)

Which means that this particular post is not likely related to Vicibox 5.0.3 ... find a later post.

[adymeblack]

That is what i was thinking. I figured it's better to ask rather than just guess.

[Robin009]

sir, i have installed vicidiall but its not connecting to putty it showing me "network connection refused"
help me out here

[williamconley]

Be SURE the vicidial server is not sharing the IP of any other computer on the network.

Be sure you can reach the workstation from Vicidial. Ping it. If you cannot reach the workstation from the vicidial server ... you can't reach the server from the workstation either.

At the workstation linux command line:

Code: Select all

ping 192.168.x.x -c 2

replace 192.168.x.x with the actual ip of the workstation.

also ping the "gateway" IP and www.irs.gov to be sure the vicidial server has full internet.

[Robin009]

Okay thanks it works....But how to configure vicidiall from the first step new password and after that what to do?

[williamconley]

Okay thanks it works....But how to configure vicidiall from the first step new password and after that what to do?

! I'm sorry, Apparently you've never gotten one of these! I feel bad, here you go:

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) In direct answer to your question: Download the Vicidial Manager's Manual (Free version if you're broke) and start at page one. When you are tempted to skip a page ... DON'T. Work from page one to the end (or until everything you want to work ... works. But DO NOT skip anything. Bring us the page and line where you hit a roadblock. Share with us what you see and what you THINK you should be seeing and any settings that are related to why you think so. We'll work you through it.

Happy Hunting!

[Robin009]

OKay sir thank you... Now i 've installed vicibox version.5.0- 32 bit standard iso and my dedicated server configuration is i3 with 4gb ram and 500gb hard disk.... Now i hve install the vicibox and its showing me the welcome page and tell me what to do next ???? And thanks for supporting me

[Robin009]

And sir i need to install asterisk separtely in vicibox??? Or it is inbuilt in that and if i need to install then tell me how to install and from where i can get this.... Sorry if you dnt mind can i get your skype id???