Will Tatam wrote: > The docs state that the AGI is run when the caller is connected but this > does not appear to be true with 1.4.21.1 > > What I see is > > 1) caller enters queue > 2) agent is found for call > 3) agent1's call begins to ring > 4) AGI is executed > 5) agent does not answer the call before timeout, call goes to next agent > 6) agent2 answers call but the AGI has already run > > Expected behaviour > > 1) caller enters queue > 2) agent is found for call > 3) agent1's call begins to ring > 4) agent does not answer the call before timeout, call goes to next agent > 5) agent2 answers call but the AGI has already run > 6) AGI is executed > > > I need the AGI to run when the actual call is connected to an agent as > my AGI is tracking which agent took the call to then fire of a jabber > message to that agent giving them them the url to access the caller's > account page. Currently the message is going to agent1 and agent2 who > actually takes the call never sees the message >
What type of channels do you use for your agents? If you're using Agent channels (the type which are configured in agents.conf), are you logging them in using AgentCallbackLogin? Mark Michelson _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
