Page 1 of 1

3-way transfer not working

PostPosted: Fri Jan 14, 2011 4:55 pm
by raysolomon
I have done quite a lot of research in vicidial forums and manual into why 3-way transfer is not working.

Nothing helped.

When the agent transfers a client to 3-way, the call gets dropped.
It affects all agents.


Need some insight.

PostPosted: Fri Jan 14, 2011 5:04 pm
by williamconley
Installer Version (name of .iso from which you installed)?

Exact method for "transfers a client to 3-way"? (Step by step, button by button, from the screens NOT from memory, on a TEST call not a live prospect so you can take your time and document it)

CLI output from that moment (please do not post 3000 lines of code!)

PostPosted: Fri Jan 14, 2011 5:28 pm
by raysolomon
vicidial/astguitclient version is in my sig.

I just sat down with an agent and documented it.

1) dialer is calling leads from the campaign
2) agent will login and click resume
3) agent will get a call
4) agent will click "transfer conference" button
5) agent will enter phone number into "number to call" box and click "dial with customer"
6) agent will eventually end call by pressing "hangup transfer" or "leave 3-way call" button.


Here is the CLI output:
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing [881602XXXXXXX@default:1] Answer("Local/881602XXXXXXX@default-de7d,2", "") in new stack
-- Executing [881602XXXXXXX@default:2] Dial("Local/881602XXXXXXX@default-de7d,2", "IAX2/ASTloop:test@127.0.0.1:40569/91602XXXXXXX||To") in new stack
-- Called ASTloop:test@127.0.0.1:40569/91602XXXXXXX
[Jan 14 15:51:02] NOTICE[767]: chan_iax2.c:7561 socket_process: Rejected connect attempt from 127.0.0.1, who was trying to reach '91602XXXXXXX@'
> Channel Local/881602XXXXXXX@default-de7d,1 was answered.
-- Executing [8600056@default:1] MeetMe("Local/881602XXXXXXX@default-de7d,1", "8600056|F") in new stack
[Jan 14 15:51:02] WARNING[769]: chan_iax2.c:7771 socket_process: Call rejected by 127.0.0.1: No authority found
-- Hungup 'IAX2/127.0.0.1:40569-3632'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [881602XXXXXXX@default:3] Hangup("Local/881602XXXXXXX@default-de7d,2", "") in new stack
== Spawn extension (default, 881602XXXXXXX, 3) exited non-zero on 'Local/881602XXXXXXX@default-de7d,2'
-- Executing [h@default:1] DeadAGI("Local/881602XXXXXXX@default-de7d,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----50-----CHANUNAVAIL----------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
== Spawn extension (default, 8600056, 1) exited non-zero on 'Local/881602XXXXXXX@default-de7d,1'
-- Executing [h@default:1] DeadAGI("Local/881602XXXXXXX@default-de7d,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
== Manager 'sendcron' logged off from 127.0.0.1



It says it is congested, but no agents are logged in right now, except for the agent showing me this.

PostPosted: Fri Jan 14, 2011 5:57 pm
by williamconley
raysolomon wrote:vicidial/astguitclient version is in my sig.
true. but neither of those is your INSTALLER version. This software can be installed in many ways. Inherent in some of those methods are specific flaws (like using a two year old installation .iso).

Also, when a "bug" is found it quite often is found when several users with the same Installer Version report a similar bug at the same time (the developer who creates that installer will often come online and help to resolve the issue).

Vicidial can be installed from scratch using several online instructions available (listing the one you used is helpful here) or via Vicibox (from Vicibox.com) or GoAutoDial.

I see from your CLI output that you are using the loopback dialplan for ... something. Perhaps you should try without it (if you were not using it on purpose, that could be an issue!). What are your settings for the campaign for 3-Way Call Dial Prefix (and the other 3-Way call settings)?

PostPosted: Fri Jan 14, 2011 6:02 pm
by raysolomon
Ah.
It is installed from scratch using scratch install instructions.


I edited my post above probably while you were replying to me.

There is virtually no load on the server.

PostPosted: Fri Jan 14, 2011 6:05 pm
by williamconley
I see from your CLI output that you are using the loopback dialplan for ... something. Perhaps you should try without it (if you were not using it on purpose, that could be an issue!). What are your settings for the campaign for 3-Way Call Dial Prefix (and the other 3-Way call settings)?