Moderators: enjay, williamconley, Staydog, mflorell, MJCoate, mcargile, Kumba
vicibox-install --no-prompt --isweb --db-server=192.168.1.1 --db-defaults
vicibox-install --no-prompt --isdb --db-user=cron --db-pass=SuperS3cr3tP4ss! --db-name=asterisk --db-custom=custom --db-custom-pass=custom4321!
vicibox-install --no-prompt --isweb --isphone --db-server=192.168.1.1 --db-defaults
Kumba wrote:I've started work on ViciBox v.10. This will be based on OpenSuSE v.15.3 and Asterisk 13. This version will be moving to more packaged based maintenance items which should make updates and corrections to things like vicibox-install less problematic overall. Below are some bullet points of what is going into this version:
- OpenSuSE Leap v.15.3 with Asterisk 13 and possibly Asterisk 16
- vicibox-install and associated files moved into a package called 'vicibox-install' for ease of maintenance
- vicibox-certbot being removed for the dumpster fire it ended up being, a new vicibox-ssl being created around the acme.sh script
- vicibox-firewall and associated files moved into a package called 'vicibox-firewall' for ease of maintenance
- Dynamic portal moved into a package called 'vicibox-dynportal' for ease of maintenance
- Inclusion of more utilities like pcapsipdump
- Basic SNMP config (not asterisk-snmp) for monitoring the server's health with network monitoring utilities
- Rework of the vicibox-upgrade script to make it more usable/usefule/work/etc.
My current plan is to get the base image done so that when OpenSuSE finally moves 15.3 into a Beta state I can have you all test install the OS to make sure there's no real installer issues. I'm planning to have two ISOs with one being for a Linux MD Software RAID array and the other being the standard single-drive direct install. Currently the image has kernel 5.3.18 but that could very well change later on.
If you have any comments, requests, software additions, etc, feel free to post them below.
carpenox wrote:zaraab, kumba is quite busy with an installer for vicidial, not really concerned with vultr, why not use a dedicated server instead of virtual? and why not just do a scratch installation if you want to use vultr?
covarrubiasgg wrote:Not really a feature request, just to let you know how Im using you work ...![]()
I was trying to make the vicibox-install script able to pass arguments / parameters such as
- Code: Select all
vicibox-install --no-prompt --isweb --db-server=192.168.1.1 --db-defaults
vicibox-install --no-prompt --isdb --db-user=cron --db-pass=SuperS3cr3tP4ss! --db-name=asterisk --db-custom=custom --db-custom-pass=custom4321!
vicibox-install --no-prompt --isweb --isphone --db-server=192.168.1.1 --db-defaults
Zaraab wrote:I would like to request you to get one thing done which is, somehow Vultr( A cloud server hosting platform) is detecting the Autodialer(application/ feature) from the ISO. Though they do provide the privilege to install custom ISO but when the vicibox ISO is uploaded, they scan it and somehow they deny to upload the ISO due to the issue of unmasked existence of the "Autodialer" kind o thing in the ISO. Could you please consider the issue in your next ISO development and mask the "Autodialer" issue so that Vultr( A cloud server hosting platform) cannot detect it and let us install it?
Please!
ccabrera wrote:Is there any way to "fork" Vicibox ISO? Like instead of getting access to the final product (it being the ISO), get access to the project where you created it, and then modify a copy of it before exporting it to our own ISO?
I believe that with SuseStudio you had this option, but as for now I'm completely lost on how you are building the ISO currently.
carpenox wrote:What about having the option for a "scratch install to go" kinda thing, where you install whatever Linux distro, then it connects to a server to download the needed files from the /etc/src/astguiclient/conf directory for the vicibox-install after reaching out to the vicidial repo for dynportal,install and firewall packages and then after it grabs the needed files, proceeds with the installation....just an idea. dunno if its possible
Zaraab wrote:Kumba can you just then create & share the scratch commands or a (.sh) file through which we can run it and deploy the setup through command line
Kumba wrote:I've started work on ViciBox v.10. This will be based on OpenSuSE v.15.3 and Asterisk 13. This version will be moving to more packaged based maintenance items which should make updates and corrections to things like vicibox-install less problematic overall. Below are some bullet points of what is going into this version:
- OpenSuSE Leap v.15.3 with Asterisk 13 and possibly Asterisk 16
- vicibox-install and associated files moved into a package called 'vicibox-install' for ease of maintenance
- vicibox-certbot being removed for the dumpster fire it ended up being, a new vicibox-ssl being created around the acme.sh script
- vicibox-firewall and associated files moved into a package called 'vicibox-firewall' for ease of maintenance
- Dynamic portal moved into a package called 'vicibox-dynportal' for ease of maintenance
- Inclusion of more utilities like pcapsipdump
- Basic SNMP config (not asterisk-snmp) for monitoring the server's health with network monitoring utilities
- Rework of the vicibox-upgrade script to make it more usable/usefule/work/etc.
- vicibox-install CLI arguments for semi-automated install
My current plan is to get the base image done so that when OpenSuSE finally moves 15.3 into a Beta state I can have you all test install the OS to make sure there's no real installer issues. I'm planning to have two ISOs with one being for a Linux MD Software RAID array and the other being the standard single-drive direct install. Currently the image has kernel 5.3.18 but that could very well change later on.
If you have any comments, requests, software additions, etc, feel free to post them below.
Kumba wrote:I've started work on ViciBox v.10. This will be based on OpenSuSE v.15.3 and Asterisk 13. This version will be moving to more packaged based maintenance items which should make updates and corrections to things like vicibox-install less problematic overall. Below are some bullet points of what is going into this version:
- OpenSuSE Leap v.15.3 with Asterisk 13 and possibly Asterisk 16
- vicibox-install and associated files moved into a package called 'vicibox-install' for ease of maintenance
- vicibox-certbot being removed for the dumpster fire it ended up being, a new vicibox-ssl being created around the acme.sh script
- vicibox-firewall and associated files moved into a package called 'vicibox-firewall' for ease of maintenance
- Dynamic portal moved into a package called 'vicibox-dynportal' for ease of maintenance
- Inclusion of more utilities like pcapsipdump
- Basic SNMP config (not asterisk-snmp) for monitoring the server's health with network monitoring utilities
- Rework of the vicibox-upgrade script to make it more usable/usefule/work/etc.
- vicibox-install CLI arguments for semi-automated install
My current plan is to get the base image done so that when OpenSuSE finally moves 15.3 into a Beta state I can have you all test install the OS to make sure there's no real installer issues. I'm planning to have two ISOs with one being for a Linux MD Software RAID array and the other being the standard single-drive direct install. Currently the image has kernel 5.3.18 but that could very well change later on.
If you have any comments, requests, software additions, etc, feel free to post them below.
mflorell wrote:We have been testing PJSIP, it does things very differently as far as the configuration files goes when compared to the old chan_SIP module. So, there will need to be some code adjustments on the VICIdial side to make it work with PJSIP phone and trunk configurations, but that is on our list to do after VICIbox 10 is released. As for VICIbos 10 specifically, right now we are working on the last few associated software packages that have broken installs on the latest OpenSuSE version, so we are making progress.
Kumba wrote:ccabrera wrote:Is there any way to "fork" Vicibox ISO? Like instead of getting access to the final product (it being the ISO), get access to the project where you created it, and then modify a copy of it before exporting it to our own ISO?
I believe that with SuseStudio you had this option, but as for now I'm completely lost on how you are building the ISO currently.
I'm using Kiwi to build ViciBox. Their documentation is here: https://osinside.github.io/kiwi/index.html
After I finish ViciBox v.10, I might release the source files. I haven't really decided yet.carpenox wrote:What about having the option for a "scratch install to go" kinda thing, where you install whatever Linux distro, then it connects to a server to download the needed files from the /etc/src/astguiclient/conf directory for the vicibox-install after reaching out to the vicidial repo for dynportal,install and firewall packages and then after it grabs the needed files, proceeds with the installation....just an idea. dunno if its possible
The Open Build Service, where I'm building the new vicibox packages, support other distros like Debian, CentOS, Ubuntu, Arch, etc. In theory, these packages could be made to install on these other distros. The biggest problem is I am not testing on these distributions. So I don't know what changes or cross-distro problems would occur.
carpenox wrote:What about having the option for a "scratch install to go" kinda thing, where you install whatever Linux distro, then it connects to a server to download the needed files from the /etc/src/astguiclient/conf directory for the vicibox-install after reaching out to the vicidial repo for dynportal,install and firewall packages and then after it grabs the needed files, proceeds with the installation....just an idea. dunno if its possible
Return to ViciBox Server Install and Demo
Users browsing this forum: Google [Bot] and 261 guests