Vicibox contact center installation requirements

    These are recommended installation requirements if you need to play with Vicibox open source scalable contact center solution:

- DB server (for up to 150 agents) - 8GB RAM, 240GB+ SSD - ALWAYS INSTALL FIRST IN CLUSTER SETUP FOLLOWING WITH ARCHIVE, WEB AND LAST TELEPHONY SERVER!

- Archive server - 2GB+ RAM, 1TB HDD

- Web server - 4GB+ RAM, 160GB HDD

- Telephony server - 4GB+ RAM, 160GB HDD

OS installation notes (assumes you already downloaded ISO from http://download.vicidial.com/iso/vicibox/server/):

root / vicidial - default login

os-install - Suse OS installation

yast lan - setup properly network and DNS properties

yast firewall - setup properly firewall inside OS

zypper up -y - install updates and reboot after that

yast timezone - setup properly timezone

Vicibox express installation:

vicibox-express - complete express setup

Vicibox cluster installation:

vicibox-install - install required component and reboot after that

Default username / password for accessing vicibox configuration - 6666 / 1234 - CHANGE AFTER INITIAL LOGIN!

Vicibox upgrade procedure:

vicibox-upgrade - start with DB following Web and Telephony server - ALWAY MAKE BACKUP FIRST!

Handy tools after complete setup for OS control:

install webmin - http://www.webmin.com/rpm.html

install htop - zypper in htop

Comments

Post a Comment

Popular posts from this blog

NSX ALB LetsEncrypt with DNS-01 challenge - BIND example

    In some of my previous posts, mentioned here LetsEncrypt script integration and Script parameter usage , I explained how useful it can be for NSX advanced load balancing solutions to utilise this kind of approach for free and automatic certificate manipulation, especially in environments with large number of web services inside. This approach utilises HTTP-01 based challenge with LetsEncrypt systems and L7 HTTP/S virtual services on NSX ALB side.     Now, from some time ago there is enhancement in this area, developed by official Avi Networks devops page, in terms of using DNS-01 challenge also. I tried on-prem option using Bind DNS as server which works very well.     Steps are pretty much similar to HTTP-01 option, which can be summarised as following:      - Create L7 virtual service with publicly available FQDN - certificates resolved can be in both options RSA or ECDSA, as configured during creation;        - Do...
Read more

VMware SD WAN - multiple locations - LAN IP address space overlapping with NAT

Image
     Different scenarios are possible in terms of routing, NAT-ing and IP overlapping setups using VMware Velocloud SD WAN technology in Customer environments.      Recently I had an PoC with my Customer for the on-prem option with this VMware solution, where different use cases were interesting to show and demonstrate - one of them is something I would like to share and it relates to possibility of LAN-side NAT on Edge (branch) locations, with purpose to have IP overlapped on these setups. Next picture is showing typical Hub&Spoke setup where it can be possible to make this type of configuration: Picture 1. VMware SD WAN lab on-prem environment     Basically thing which needs to be accomplished is appropriate NAT solution for LANs on every branch Edge which are and needs to be the same (192.168.1.0/24 in this example) - as it is shown on Picture 1.      Honestly speaking, NAT is not one of so powerful things insi...
Read more

NSX ALB (Avi Networks) HTTP policy set removal

     As I wrote on some of my previous posts, Lets Encrypt automation of certs renewal inside NSX ALB (Avi) platform is very useful for Customer environments utilising large number of web oriented services, which needs to be on free HTTPS setup. These blogs about integration could be found here LINK-1 or LINK-2 for DNS based configurations.     What I saw from some operational systems is that,  occasionally, there is small piece left under HTTP policies (for HTTP-01 based challenges), in parent-child setups of virtual services, where HTTP policy is not removed properly from parent virtual service and that prohibits further renewal of certificate when it's needed. Typical removal of that piece is making troubles because it's associated to virtual service and system is not allowing that change.     What's needed is to de-associate problematic HTTP policy set from virtual service and then it can be freely removed from system without any issue. This...
Read more