-
- Downloads
Replace chan_agent with app_agent_pool.
The ill conceived chan_agent is no more. It is now replaced by app_agent_pool. Agents login using the AgentLogin() application as before. The AgentLogin() application no longer does any authentication. Authentication is now the responsibility of the dialplan. (Besides, the authentication done by chan_agent did not match what the voice prompts asked for.) Sample extensions.conf [login] ; Sample agent 1001 login ; Set COLP for in between calls so the agent does not see the last caller COLP. exten => 1001,1,Set(CONNECTEDLINE(all)="Agent Waiting" <1001>) ; Give the agent DTMF transfer and disconnect features when connected to a caller. same => n,Set(CHANNEL(dtmf-features)=TX) same => n,AgentLogin(1001) same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS}) same => n,Hangup() [caller] ; Sample caller direct connect to agent 1001 exten => 800,1,AgentRequest(1001) same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS}) same => n,Hangup() ; Sample caller going through a Queue to agent 1001 exten => 900,1,Queue(agent_q) same => n,Hangup() Sample queues.conf [agent_q] member => Local/800@caller,,SuperAgent,Agent:1001 Under the hood operation overview: 1) Logged in agents wait for callers in an agents holding bridge. 2) Caller requests an agent using AgentRequest() 3) A basic bridge is created, the agent is notified, and caller joins the basic bridge to wait for the agent. 4) The agent is either automatically connected to the caller or must ack the call to connect. 5) The agent is moved from the agents holding bridge to the basic bridge. 6) The agent and caller talk. 7) The connection is ended by either party. 8) The agent goes back to the agents holding bridge. To avoid some locking issues with the agent holding bridge, I needed to make some changes to the after bridge callback support. The after bridge callback is now a list of requested callbacks with the last to be added the only active callback. The after bridge callback for failed callbacks will always happen in the channel thread when the channel leaves the bridging system or is destroyed. (closes issue ASTERISK-21554) Reported by: Matt Jordan Review: https://reviewboard.asterisk.org/r/2657/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@394417 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Showing
- CHANGES 26 additions, 4 deletionsCHANGES
- UPGRADE.txt 11 additions, 2 deletionsUPGRADE.txt
- apps/app_agent_pool.c 2597 additions, 0 deletionsapps/app_agent_pool.c
- channels/chan_agent.c 0 additions, 2568 deletionschannels/chan_agent.c
- configs/agents.conf.sample 50 additions, 82 deletionsconfigs/agents.conf.sample
- configs/queues.conf.sample 2 additions, 13 deletionsconfigs/queues.conf.sample
- include/asterisk/bridging.h 7 additions, 1 deletioninclude/asterisk/bridging.h
- include/asterisk/config_options.h 1 addition, 1 deletioninclude/asterisk/config_options.h
- include/asterisk/stasis_channels.h 16 additions, 0 deletionsinclude/asterisk/stasis_channels.h
- main/bridging.c 172 additions, 58 deletionsmain/bridging.c
- main/stasis_channels.c 77 additions, 0 deletionsmain/stasis_channels.c
Loading
Please register or sign in to comment