vicidial.org

Hello everyone, I have a pre-existing vicibox setup. My predecessor did not believe in using a firewall and was securing his job by manually accepting/denying incoming attacks.

So anyway as the story goes, he left, we got hacked, and now after all the trouble were back on line. Only thing I am having trouble with is the way Vicibox is operating on the network.

Previously it was set to 50.59.191.133/24 (network bridge) *(this is the original address for access to vici)*
and 50.59.191.129 (ipv4 gateway eth0)
virtual box 192.168.200.1 (host only adapter address) *(my network is in 192.168.111.xxx)

today i did this:

assigned 192.168.111.220 to vicidia (via yast lan) forwarded to 50.59.191.133
opened 5060 (udp) 4569 (udp) 10000-20000 (udp) & ssh for above address

so obviously its not working, any help or direction would be greatley appreciated

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) When you log in via ssh, there is a notification to update your ip with a script designed for this purpose. Execute the script (with --help if you're uncertain, but options aren't really necessary because it will quiz you). This script can be run multiple times as often as you like and does NO harm as long as the last time it is run it provides the correct NEW IP for your server.

4) Dynamic Good Guys will help to protect you from hackers. Published on Viciwiki.com. We hope one day Kumba will put it directly into Vicibox.

Happy Hunting!

Asterisk 1.4.44 - Vici
Centos 6.5
X-Lite Dialer
Virtualbox 4.2
Inside of MS Server 2008 R2 w/ 2x Xeon @ 2.40 ghz and 32 GB ram
I use rdp to get to virtual box on my server so i've never had to ssh to it and see that message.

sorry having trouble with posting, i keep getting the "message too spammy" error. Also no additional software, nothing crazy, pretty basic......just tcp/ip issues

Vicidial is designed to be accessed via ssh. One should almost never log directly into the server. Even if it is virtual.

Get used to this, as it makes things like "cut/paste" simpler. The program is PuTTY download it from chiark. (google: chiark putty ... and all you need is the executable, not an install package or anything fancy).

I've used PuTTy plenty of times in the past, currently I use Bitvise SSH Client to get to my cent os web server.

Any thoughts though on the best way to address the ip settings for this?

mdoria34 wrote:I use rdp to get to virtual box on my server so i've never had to ssh to it and see that message.

mdoria34 wrote:I've used PuTTy plenty of times in the past, currently I use Bitvise SSH Client to get to my cent os web server.

? So you'll know how to use it with your Vicidial server. Good.

Once you log in, the splash screen will give you the perl script to run.