[asterisk-dev] [Code Review] 2657: Replace chan_agent with app_agent_pool.

rmudgett reviewboard at asterisk.org
Tue Jul 9 16:09:23 CDT 2013

This is an automatically generated e-mail. To reply, visit:

(Updated July 9, 2013, 9:09 p.m.)

Review request for Asterisk Developers.


Addressed review feedback from mmichelson.

Bugs: ASTERISK-21554

Repository: Asterisk


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
; 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,Hangup()

; Sample caller direct connect to agent 1001
exten => 800,1,AgentRequest(1001)
same => n,Hangup()

; Sample caller going through a Queue to agent 1001
exten => 900,1,Queue(agent_q)
same => n,Hangup()

Sample queues.conf
member => Local/800 at 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.

Diffs (updated)

  /trunk/CHANGES 393910 
  /trunk/UPGRADE.txt 393910 
  /trunk/apps/app_agent_pool.c PRE-CREATION 
  /trunk/channels/chan_agent.c 393910 
  /trunk/configs/agents.conf.sample 393910 
  /trunk/configs/queues.conf.sample 393910 
  /trunk/include/asterisk/bridging.h 393910 
  /trunk/include/asterisk/config_options.h 393910 
  /trunk/include/asterisk/stasis_channels.h 393910 
  /trunk/main/bridging.c 393910 
  /trunk/main/stasis_channels.c 393910 

Diff: https://reviewboard.asterisk.org/r/2657/diff/


Tested the features of agents and they work as expected.
1) Agents login and get MOH and any COLP set by the dialplan before AgentLogin().
2) Agents logging in with a local channel chain wait for the local channels to optimize out.
3) Caller channels directly running AgentRequest() are able to connect to the agent.
4) Callers going through Queue() can connect to agents via local channels.  The local channels can optimize themselves out.
5) Tested recording agent calls.  Note: Agent calls cannot be recorded currently if the caller came in on an optimizing local channel because MixMonitor audio hooks are not being handled by the optimization.
6) Caller COLP is shown to the agent before the agent accepts the call.
7) The original COLP when the agent logged in is restored while the agent is between calls.
8) Tested agent wrapup time.
9) Tested agent not acknowledging the call before autologoff time.

Many more.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20130709/5ffec73b/attachment.htm>

More information about the asterisk-dev mailing list