Remote Agent - Not Hanging Up

[roundqube]

I have a standard 1-server installation of Vicidial (SVN trunk). I am running on a dual core 2.6 Intel w/ 4G of RAM on 2.6.18-194.8.1.el5PAE.

I setup a survey campaign per the manual and its working up to the end.

1) Remote agent calls me and I press 1 to opt-in
2) Get transferred to the local DID I have setup for the remote agent transfer
3) I speak with one of the agents in another call center
4) I hang up

In step 4, the channel is not released. The remote agent shows in "QUEUE" in the real-time screen for every (as far as I can tell). I have to manually log them out to release the channel.

[williamconley]

when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, 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.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

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)

[roundqube]

Centos 5.5 Kernel 2.6.18-194.11.4.el5 | Vicidial 2.4-277 Build 100827-1535 | Asterisk 1.4.33.1 | Single Server | Sangoma USB Timing Device | No Extra Software After Installation

[williamconley]

installation method?

have you tested this with a logged in agent to see if this is related to the remote agent or just a problem with your carrier? perhaps router related?

[roundqube]

Installation method was noted in my first comment. Single server, vicidial svn trunk via the install.pl script on top of CentOS 5.5.

I will test with logged in agent to see if its a remote agent issue. Thanks.

[williamconley]

without the phrase "from script" or "from scratch" it is not known that you were not installing vicidialnow/goautodial or actually scratch installing on CentOS.

there is a fairly large difference in "success" from scratch installers vs vicidialnow. (also there is a forum specially for vicidialnow installers. so i ask to be sure.)

good luck on the test. be sure to post your resolution if you work it out, or your "experiment results" if not.

[roundqube]

William,

I failed to mention this before but when I say in Step 4 the channel is not hung up (or freed up) for another remote agent to dial, I looked at my Asterisk box and it shows the hang-up and 'show core channels' shows 0. It appears that some clean-up scripts are not running. Although I have validated the perl script ADMIN_keepalive.pl is running every minute as its supposed to.

This doesn't appear to be a carrier issue. But I'll go ahead and test with a real agent logged in rather than remote agent. How do I do survey with a real logged in user rather than auto agent?

[roundqube]

Nevermind, read that the call goes to next available agent. Regardless if its auto agent or logged in agent. Sorry.

[williamconley]

it's all learning curve. LOL

vicidial changes every day. i can't keep up. and i've been here a while.

[roundqube]

Tested with a logged in agent (not remote agent) and same thing happens. I get the call on my cell phone, I press 1 to opt in and I get transferred to that local DID I have setup.

After the transfer, I hang up and Asterisk shows no channels up but Vicidial is not cleaning up the call (after hangup) and so it appears as those I am still online. Same thing happens with the remote agent and it looks like that agent is tied up forever.

[williamconley]

you should try the vicibox DEMO cd (boot from an .iso, no changes to the computer) and see if you can find the difference.

you'll need to show the CLI from the "hangup" moment and the agi output from that same moment (please do not post 3000 lines of code! just from the hangup moment).

you may also want to post your dialplan entry for this particular carrier, and the hangup extension from your default extension context.

you could get your answer immediately if you compare those to your own demo cd that actually works (it will work quite sufficiently to handle a single line for testing, even though the version is older the CLI from hanging up a call should be virtually identical).

i have found the demo cd to be very useful for controlled situation troubleshooting.

(or you could just install vicidialnow/goautodial or vicibox and it would "just work" ...)