vdad-JAM log file

[gardo]

Matt,

What's the vdad-JAM log file? I saw some in /var/log/astguiclient/. Checking the contents, it has:

2007-11-20 09:21:07|0|20071120092057| |78942|192.168.100.21|CL_SALES_I_L|LIVE|10194|1195579237.7539999|J1120920370000101
94|Local/90009*CL_SALES_I_L*CXFER*10194**2196782334*2956*@default-f057,2|1|2196782334|2007-11-20 09:20:37|IN|LIVE-16|2007-11
-20 09:20:55|NONE||
2007-11-20 09:21:07|| lagged call vdac call DELETED 1|20071120092057||

[mflorell]

That is a log file specifically for the clearing of calls that are "stuck" as LIVE calls even though they are hung up.

This is here because Asterisk is not 100% at processing the "h" exten, so you have to program something to fix that.

[gardo]

Can this be related to the issues I'm having? I'm doing a closer transfer and every fourth or fifth transfer doesn't complete. Like the channels get stuck or something and after a few minutes some of the agents get crosslines. Searching the forums and mantis, I found this: http://www.eflo.net/VICIDIALmantis/view.php?id=102. I haven't tried this solution yet.

[mflorell]

Consultative transfer or blind transfer?

[gardo]

Both. Consultative internal transfers and blind internal transfers.

[mflorell]

Blind transfers almost never cause problems on properly configured systems, but consultative transfers can cause problems sometimes. Usually the issue with them is that the agent is not waiting at least 10 seconds after the other side of the 3way picks up before they leave 3way or do something else.

There is a special log file generated in the agc web directory that logs information on consultative transfers and leave 3way that helps in debugging what may be causing you problems.

[gardo]

I doubt if my system hasn't been configured properly. It's a multi-server setup with 1 mysql/apache and 1 asterisk/vicidial.

Let me do an exclusive blind transfer calls to closers and see if that alleviates the issue.