About transfer to AGI script

[marship]

Hello.
I am running goautodial-2.1 on my local server. And I am using the original vicidial server it has. The version is
VERSION: 2.4-325c BUILD: 110430-1924

I wrote a php-agi script to collect user's account and password.
The plan is:
1) Agent dial out and talk with customer.
2) when it is time for customer to input their account number.
3) Agent click "transfer" button, then input AGI extension, then "dial with customer". Then agent, customer and agi script will be in same meetme room. in agi script, i mute the agent so customer can input without disturb. After the number is collected, agi simply hang up and unmute the agent. So agent and customer can keep talking.

The problem is, after I click "dial with customer", the AGI script immediately jump in and start run. But on vicidial screen, it is still showing "waiting for ring" and soon time out. Although agent,customer and AGI are already in same room. Agent can't click anything but only can 'hang up both lines'.

I tried both goautodial agent interface and vicidial agent inteface and both work same way. So I think it is a vicidial problem.
Is this a bug?


Thanks.
Regards.
Scott

[mcargile]

The reason this is happening is that the dial with customer button assumes the call is going to go through the call_log function of the FastAGI to an external phone number not to an internal extension. The way Matt has gotten around this in most instances is to route the call through the loop back IAX connection back into the dialer. This is treated like an external phone call. Here is an example:

Code: Select all

exten => _91999NXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91999NXXXXXX,2,Dial(${TRUNKloop}/${EXTEN:2},,tTo)
exten => _91999NXXXXXX,3,Hangup


This is used by the performance test leads. This routes the call through the loop back and sends them back into the default context with the first two digits stripped off.