Summary:ASTERISK-18711: Advance Call Routing Capability.
Reporter:Asad Gill (asad.gill)Labels:
Date Opened:2011-10-12 12:36:04Date Closed:2011-10-12 12:45:17
Status:Closed/CompleteComponents:Applications/app_queue Core/ManagerInterface
Versions:SVN Frequency of
is the original version of this clone:ASTERISK-18712 [patch] Advance Call Routing Capability
Environment:Attachments:( 0) advance_call_routing.patch
Description:This patch adds third-party call routing capability to the queue. It enables a system to connect to asterisk through manger interface and control call routing to the agents. Therefore external systems will be able to implement any custom call routing algorithms.

Asterisk Manager Interface changes:
Two new AMI actions are added
1. RouteSelect (instructs the queue to route a specific call to a specific agent logged into the queue)
2. RouteEnd (let the default queue routing algo route a specific call)

Two new AMI events are added
1. RouteRequest (notify that a call is ready for routing)
2. RouteResult (notify success or failure result of a RouteSelect action)

Configuration changes:
1. This advance routing feature can be enabled through queue configuration. In order to enabled it, add "advancerouting = yes" to the queues for which advance routing is required. Any queues without this configuration will not be affected.
2. A new AMI class "route" is added. The AMI users with this class will additionally receive RouteRequest and RouteResult events and will be able to issue RouteSelect and RouteEnd actions. The default queue routing algo will be operative until an AMI user with "route" class connects to asterisk.
Comments:By: Sam (sam) 2011-10-13 00:00:06.582-0500

Seems interesting!
Would you please provide one example of key values to be sent along with newly added AMI actions?