vicidial.org

Hi guys,

I looked, albeit briefly to see if there was a thread about this already but did not see one. My apologies if there is!

We are having an issue right now where on our P1 campaign, the message either doesn't play, or there is a long delay and I think we are missing opportunities here.

This only happens with AMD on as far as I know, and it's intermittent to almost frequent.

We have test called ourselves as well as other numbers and the results are never consistent.

Any advice would be great!

Thanks

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 (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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 combine "Survey/Broadcast/Robodial" with "AMD", both of which are serious memory hogs, you risk overloading the server. So you may want to consider reducing your admin->servers "Max Trunks" value until the problem goes away and make a note that this value represents "overload". You can also check "uptime" which shows the 1/5/10 minute average server load. The value in the 1/5/10 minute average should NEVER exceed the core count, and for normal operations should not exceed HALF of the core count (for best stability and no hair pulling).