(solved)not able to make outbound calls on new set up

[davesdatasystems]

Let me go through a little history here, I set up a dialer, it works fine, and that is the information i am going to post, since i had to get rid of the new set up and go back with the old one. But i am hoping someone else has had this issue and would know how to resolve it, so i am sorry i can not post the new information due to the fact we was rushed and i had to get the other dialer up and running before leaving shop to be ready for the next day

as required by the great staff here;

version of vicidail 3.1.10
loadavg 1.5
no codecs
voip
opensuse O.S.
vicidial redux
VERSION: 2.2.1-237
BUILD: 100510-2015
iso install/single server/Virtual
asterisk 4.4.39
AMD Athlon(tm) II X2 245 Processor/ibuypower comp(motherboard unknown)
(this is what i have running now, I cant get a second outbound campaign to work on it, so that is why i want to upgrade)
that is my working dialer,4.0.1 is that i want to get working, sorry i dont have all the information on that, but it is from the latest stable release of vicidial ViciBox.i686-4.0.1.iso

The new version of vicidial that i wanted to work with is vicidial 4.0.1, and i seen know errors on the cli or the sip debug, but here is what happened. I set it up, everything was fine until i tried to make outbound calls. it would make around one outbound call every 30 to 45 minutes, so i tried to call from the dialer, and the results got stranger, i could make the call, but when i did, and the call went though, it connected and i was able to talk for about 2 seconds before it cut my sound out, but it did not disconnect my call, I have turned off all firewalls. All my network settings are correct, but there is just something that i am missing, sorry i cant post my cli or sip debug file due to having to run the old program, but if anyone has ran into this, and found a solution, please let me know, if i can help with any further information, please let me know.

[williamconley]

you said something about "can't get a second outbound campaign to work ..." and also you mentioned "virtual".

That means we have the issue of using a 2.9G dual processor in a Virtual server to run Vicidial. This generally does not do well past your second or third phone call.

So let's clarify this a bit:

Are you saying you are successfully running a single campaign, but cannot start a second while the first one is running?
IF so: (how many logged in agents? how many calls at one time plus calls ringing? what is your dial ratio? are you recording calls? What codec are you using?)

Or did I misinterpret that entirely?

Mostly, though: DO NOT run Vicidial in a Virtual environment. It is not supported beyond one or two calls for testing/development in a virtual system. Get a dedicated server and you'll have much more hair at the end of the week.

If, however, you "must" run in a Virtual environment, you will need a server for each campaign and you will need to start with a single agent on a single call and work your way up until you experience ... oddities. Then reduce your usage until the oddities go away and you have found your virtual server's capacity. Often this is merely a couple calls.

[davesdatasystems]

in a way you did. Let me explain, it is a office side dialer (ie not cloud based) The dialer is running fine right now on its current set up, but i cant do a second campaign. I have ran up to 18 agents and a closer campaign on the old set up, and the one i am using right now, running at a dial ratio of 7 to 10 depending on what it takes to keep everyone connected. But the issue is when i installed 4.0.1 on the same machine i ran into the issues i listed above, not being able to make the outbound calls (other then 1 every 30 minutes or so) and when i did a test call, the call would go through, connect but i would lose sound after about 2 seconds, but the phone would stay connected (with no sound going either way) firewalls are all off.

[williamconley]

iso install/single server/Virtual

We have two basic concerns. First: What does "Virtual" mean here? (I did not suggest it was a cloud server, but questioned the Virtual-ness of the server - Vicidial does not run in Virtual systems well, not supported). The location of a Virtual server (cloud or sitting on your nightstand) makes no difference; Virtual = not good for production. You might get lucky and run a specific version with a specific load for a while (and it is useful when you do so if you post the precise specifications for this, as there are several people chasing virtual solutions ... but to date no one has succeeded in a production-ready virtual Vicidial solution) ... but in practice: Virtual = bad idea for Vicidial.

Next we have: No way to troubleshoot a system that is no longer installed. However, I will say that if it was "Virtual", that was likely your problem. Unvirtual it and try it again, or build another Virtual one and only use it for a single agent on one call and see how that goes. Attempting to troubleshoot a system that no longer exists is a wild goose chase.

A question would be why you had to "delete" the new Virtual machine. Since they are virtual, you should have made a brand new machine and just ... turned it off if you didn't like it and turned this one back on. What virtualization system are you using?

[davesdatasystems]

I have resolved the issue, i made a simple mistake, i attempted to reinstall and do everything by the book. But i noticed that i needed to remove a ; in the sip.conf file, before the externalip, once i did that, everything think started working as it should