Page 1 of 1

Issues changing settings through admin interface

PostPosted: Fri Sep 16, 2011 1:27 pm
by Janky
Hello,

I have been a user of vicidial for a couple years now i have recently started using the new goautodial product and i must say i am excited with all the new features.

I have several systems currently running with no issue although with one in particular i am having a problem.

The system in question is running in a VM environment i have noticed when making changes in the admin interface such as creating a phone extension or updating a carrier the config is not being reloaded.

I must login to the CLI and manually run reload for my changes to take affect.

In my other setups while watching the CLI and making changes in the web interface that after a few seconds of clicking submit the reload is done automatically but that does not seem to be the case with this system.

Any input would be much appreciated. Thank You in advance.

My version information is below:

VERSION: 2.4-309a
BUILD: 110430-1642
Asterisk 1.4.39.1

PostPosted: Sat Sep 17, 2011 8:43 pm
by williamconley
Vicidial does not run well in VM environments. This and a myriad other problems can occur. It tends to work well with virtually no load, single user, but anything above that ... crash and burn.

VM valid for testing only.

also:

when you post, please post your entire configuration including (but not limited to) your installation method.

It is also a requirement to read 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 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