Transfer Issue

[jamz]

I am transferring calls from fronters to an ingroup of closers. Everything works fine.

After a few hours, when the fronter transfers, they get the closer, they then leave 3 way and they remain connected to the customer and the call doesn't get to the closer.

Sometimes they will connect to the closer but remain with the client as well, hanging up hangs up the call for the closer and the customer.

When this happens I can see that there are strange entries in the vicidial_conferences table as below:

8600162 192.168.0.33 SIP/cc33016 0
8600191 192.168.0.33 SIP/cc33016 0
8600199 192.168.0.33 SIP/cc33004 0
8600178 192.168.0.33 SIP/cc33016 0
8600163 192.168.0.33 SIP/cc33016 0 2013-06-20 18:26:56
8600167 192.168.0.33 SIP/cc33016 0 2013-06-20 18:47:38
8600190 192.168.0.33 SIP/cc33016 0 2013-06-24 17:54:12
8600189 192.168.0.33 SIP/cc33016 0 2013-06-24 18:24:35
8600203 192.168.0.33 SIP/cc33006 0 2013-07-03 14:10:03
8600106 192.168.0.33 SIP/cc33003 0 2013-07-08 15:52:57
8600132 192.168.0.33 SIP/cc33016 0 2013-07-10 18:52:33
8600153 192.168.0.33 SIP/cc33016 0 2013-07-15 18:35:05
8600143 192.168.0.33 SIP/cc33016 0 2013-07-15 18:57:46
8600100 192.168.0.33 SIP/cc33003 0 2013-07-17 15:04:06
8600207 192.168.0.33 SIP/cc33005 0 2013-07-17 16:08:14
8600133 192.168.0.33 SIP/cc33016 0 2013-07-18 13:10:21
8600120 192.168.0.33 SIP/cc33016 0 2013-07-19 12:24:34
8600119 192.168.0.33 SIP/cc33016 0 2013-07-19 12:26:33
8600145 192.168.0.33 SIP/cc33016 0 2013-07-19 14:21:26
8600105 192.168.0.33 SIP/cc33003 0 2013-07-19 17:20:30
8600121 192.168.0.33 SIP/cc33016 0 2013-07-22 13:19:43
8600142 192.168.0.33 SIP/cc33016 0 2013-07-22 13:47:03
8600141 192.168.0.33 SIP/cc33016 0 2013-07-22 13:51:35
8600157 192.168.0.33 SIP/cc33016 0 2013-07-22 17:26:24
8600155 192.168.0.33 SIP/cc33016 0 2013-07-22 17:29:34
8600161 192.168.0.33 SIP/cc33016 0 2013-07-23 10:55:27
8600094 192.168.0.33 SIP/cc33003 0 2013-07-23 11:20:54
8600102 192.168.0.33 SIP/cc33003 0 2013-07-23 11:41:06
8600101 192.168.0.33 SIP/cc33003 0 2013-07-23 11:43:04
8600103 192.168.0.33 SIP/cc33003 0 2013-07-23 11:51:42
8600134 192.168.0.33 SIP/cc33016 0 2013-07-23 12:00:19
8600093 192.168.0.33 SIP/cc33003 0 2013-07-23 12:25:49
8600147 192.168.0.33 SIP/cc33016 0 2013-07-23 12:30:09
8600131 192.168.0.33 SIP/cc33016 0 2013-07-23 12:34:44
8600092 192.168.0.33 SIP/cc33003 0 2013-07-23 12:54:36
8600150 192.168.0.33 SIP/cc33016 0 2013-07-23 12:58:22
8600156 192.168.0.33 SIP/cc33016 0 2013-07-23 13:07:29
8600159 192.168.0.33 SIP/cc33016 0 2013-07-23 13:10:00
8600152 192.168.0.33 SIP/cc33016 0 2013-07-23 13:15:33


This is just a small sample of the table.

As you can see I have multiple entries for the same sip account. On my other servers this doesn't happen.

Can anyone see something obvious?

Thanks.

[williamconley]

Seriously consider an upgrade.

If you are using a clustered install, it may be a good idea (the best perhaps) to reinstall the entire cluster with Vicibox 4.0.3 and then upgrade your DB to match. You may find a lot of bugs fixed afterwards (and a lot of new toys ...).

Vicibox will cluster during your installation. You'll lose the pretty agent screen (although in theory it may be compatible now! You could bring it along for the ride perhaps). But you'll have a very up-to date Vicidial with the latest less-buggy code.

That being said, if you don't want to upgrade, we'll need to troubleshoot. The post above has an interesting list of ... something. But we'd need the agi and/or asterisk cli output or logs to find out what happened when a call failed to do what it should.

Of course, I'm sure you're rebooting your servers nightly to avoid code irregularities.

[jamz]

Thank you William.

I reboot the asterisk diallers/web servers every night, the db once a month.

It's been running fairly smoothly for 18months+ now.

I didn't want to fix it until it was broken, I guess now is the time.

I'm not keen on upgrades, I prefer to wipe and clean install.

I have a few questions if you don't mind:

I'm downloading and intalling a test version today.

1. Is the database structure the same on vicidial as it is on vicibox, I have some custom reports that need data to be in the same tables. If not is there a script that does the changes?
2. I have a couple of campaigns that I could test with vicidibox, if the DB has the same structure I could run 2 vicibox and 3 vicidial diallers? Otherwise it will be "no turning back (easily) move", I always like to have a Plan B.
3. I use webforms, will I have that functionality in the vicibox front end.
4. Will I need to recreate all campaign, inbound settings etc or will they transfer.
5. There is a 32 and 64 bit option, my hardware will run 64 bit, Why would I want to run 32bit?

Thanks for your help.

[williamconley]

1. Is the database structure the same on vicidial as it is on vicibox, I have some custom reports that need data to be in the same tables. If not is there a script that does the changes?

Vicibox is an installer. Vicidial is the software that it installs. Vicidial has lots of versions and the version you install will determine the database schema. Properly done, it is very easy to UPGRADE any existing db schema to a later version.

2. I have a couple of campaigns that I could test with vicidibox, if the DB has the same structure I could run 2 vicibox and 3 vicidial diallers? Otherwise it will be "no turning back (easily) move", I always like to have a Plan B.

Vicibox and vicidial are the same thing. Vicibox will add a 2nd/3rd/etc server to an existing server to create a cluster or expand a cluster. If you are not comfortable with this on your Live Server, either start a whole new cluster or use VMware/vSphere to create a virtual cluster (which will work nicely for a single agent for testing!).

3. I use webforms, will I have that functionality in the vicibox front end.

Vicibox is Vicidial. No difference.

4. Will I need to recreate all campaign, inbound settings etc or will they transfer.

If you bring the DB into a fresh install, and the upgrade the DB to match the db schema of the fresh install, EVERYTHING will come along for the ride. We've done this many times for many clients. You can even create a Virtual Cluster (I recommend vSphere, it's free!) and then put your DB into it and put a single agent on it for testing after the upgrade to see how it worked.

5. There is a 32 and 64 bit option, my hardware will run 64 bit, Why would I want to run 32bit?

Honestly, if you have to ask that question, just use 64 bit. When you need 32, you'll find your own reason. (Like ... the drivers for the 32 bit WORK and the 64 bit DON'T, that could do it! LOL).

[jamz]

Thank you for a comprehensive response.

I meant goautodial (installer) when I wrote vicidial, we refer to the installation as vicidial. Sorry I should have been clearer, lesson learnt.

Nice answer to my 64bit question, LOL. I planned to try 64 on the testbed and switch it if there were problems. I'll make sure it runs before I go live with it.

You suggested version 4.0.3, which I have downloaded, there is Vicibox 5 on the Vicibox site, is that too new for somone upgrading from GoAutodial? I was going to load that on a test server as well at least while I am testing.

Thanks for the help and advice, much appreciated.

[williamconley]

We do not yet have any 5.0 installs. We do have lots of 4.0.3 installs. So no opinion there. I'd give 5.0 at least another week and one more "maintenance" release. But there are rooms using it, just be sure to check the "bug" page and make the fixes recommended on it until the next maintenance release comes out if you want to use it.

We always recommend 64-bit whenever and wherever possible. 32-bit only for VM installs that don't support 64 (which can happen if you are not familiar with configuring for 64 bit in some vm situations ... and since they are the same operationally, it makes no difference for sandbox servers anyway).