Hangup after on-hook inbound call

[dspaan]

Can anyone tell me how to configure vicidial so the connection is hung up after you do an on-hook inbound call? Because if i press the hangup customer button in the agent screen my hardphone keeps the line open. The result is that the next inbound call does not ring on my phone because if an agent forgets to hangup on the phone itself.

I know it should technically possible because if you work off-hook and logout the connection is disconnected properly.

[Rogger]

Hello,

Paste the Asterisk log here.

[williamconley]

To prep: (in addition to a log entry from a single occurrence as previously suggested)

Code: Select all

asterisk -V

Code: Select all

admin->servers: Asterisk Version

Code: Select all

cat /etc/astguiclient.conf | grep VARasterisk

Verify which of the sample "conf" files matches the extensions.conf from /usr/src/astguiclient/trunk/docs/conf_examples

[dspaan]

You want to see a log of when i press the hangup button in the agent screen and on-hook phone stays active?

Asterisk 11.25.3-vici

[williamconley]

Whole call. Start to finish. To see if there's anything extra or missing or errors at any stage of the call. Pretty much a standard reflex for any PBX tech. While this *may* be a javascript/AJAX/PHP miscommunication it may also be a PBX failure. Ruling out one of those is a good step. So one call, start to finish. Also, if you have a non-OnHook example that works properly for comparison, that would be equally useful.

Try to make them test calls, not during operations, not 3000 lines of unrelated data, but every line for the call in questikon.

[dspaan]

So you are telling me this is not normal? Because i just don't know any better. Every on-hook call i've ever done on every vicidial server never hangs up my phone connection when i press the hangup customer button.

[williamconley]

Dunno. I've never looked, personally.

The question is whether you are interested in resolving the bug (or adding a new feature) or just looking for an answer to the question "is this by design".

I would consider it an incomplete feature if an agent can forget to hang up and break the system. Not a bug, per se, unless it used to work and stopped.

[dspaan]

My question is, 'is this by design' and 'is there a way to make the connection hangup when you click the hangup customer button?'.

[williamconley]

Which means everything Rogger and I posted is on point. All previous posts stand.

[dspaan]

Here i simulated this behaviour, the only difference is that i did a manual outbound call instead of handling an inbound call.

This is where i dialed my own mobile phone:


Here is where i answered the call on my mobile:


Next i hangup on my mobile:


Then i press the hangup customer button in the agent screen:


Until this moment my softphone/hardphone call i still active but when i logout with the vicidial logout link this happens and my connection is cleared:

[williamconley]

1) When you post logs, don't post screen shots. Post the text and use the "code" button in this editor to enclose the code blocks. This doesn't truncate and allows search engines.

2) Don't fake it: Make the calls as expected. It's not necessary to "fake" inbound, you can just dial the number and call yourself, lol.

3) Not saying the supplied samples are invalid: I don't have time to look this morning. But when you get free support, you want to make it as simple as possible for that brain you're hoping to borrow to get to your solution. The less they have to work, the more likely you are to get that Free Advice you seek.

[dspaan]

I thought screenshots would be easier to read, oh well i'll do screendumps next time. I appreciate your responses Bill. My questions still stand in this scenario because also after an outbound call we would want to hangup after the call is done.

[blackbird2306]

You don't need to post any asterisk logs. There is nothing wrong with your setup. It is "normal" behavior, that on-hook phone stays active after hanging up customer connection. And there is no option/setting to change this "bug/behavior" without making changes in the code. And I have a "dirty", but very easy one line solution for this:
1. Make sure that "Status Display Fields" in campaign settings is set to something with "CALLID" (NAME_CALLID_LISTID is also OK)
2. Copy "vicidial.php" to "vicidialhangup.php" or whatever you like before you make any changes
3. Make your changes in the new vicidialhangup.php file:
There is a function dialedcall_send_hangup (starting about line 12238 in svn revision 3020). You need to add only one line just at the end of the function before the closing bracket (about line 12754):

function dialedcall_send_hangup(dispowindow,hotkeysused,altdispo,nodeletevdac,DSHclick)
{
...
...
ShoWTransferMain('OFF');
}
}
// ADD THIS HERE:
if(no_empty_session_warnings == 1 && document.getElementById("MainStatuSSpan").innerHTML.match(/UID: Y/) != null) { livehangup_send_hangup(agentchannel); setTimeout(function() {hideDiv('AlertBox');}, 1200);}
}

The above example will hangup only on-hook phone line after inbound call!! If you want the hangup for both inbound and outbound calls then add this line instead:
if(no_empty_session_warnings == 1) { livehangup_send_hangup(agentchannel); setTimeout(function() {hideDiv('AlertBox');}, 1200); }

Just use the vicidialhangup.php (where you made the changes) for login and be aware that this is a beta version solution. Sure there are many other ways to accomplish this (dialplan, AGI...), but this is the easiest and shortest way.

[williamconley]

Beware leaving recording or other channels in the session. May want to look at the "kill everything" code instead of just "kill agent session" code.

Just sayin' ...

Good job on the R&D

[blackbird2306]

That's a good reflection. But you need to press the "HANGUP" button to trigger this part of code, which will on the other side kill all other sessions also the recording. [UPDATE: I've tested it and the meetme conference was killed (also recording and admin monitoring channel)]

[williamconley]

That's a good reflection. But you need to press the "HANGUP" button to trigger this part of code, which will on the other side kill all other sessions also the recording. [UPDATE: I've tested it and the meetme conference was killed (also recording and admin monitoring channel)]

Did you have any monitoring in progress (any managers from the real time screen)? I prefer safety. There are so many methods of call transfers and handling in Vicidial, the "kill 'em all" when the agent leaves the room method seems much more likely to fit all situations (for OnHook agents at least).