[asterisk-bugs] [JIRA] Feedback Entered: (ASTERISK-18712) [patch] Advance Call Routing Capability

Asad Gill (JIRA) noreply at issues.asterisk.org
Mon Aug 27 23:05:07 CDT 2012


     [ https://issues.asterisk.org/jira/browse/ASTERISK-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asad Gill updated ASTERISK-18712:
---------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

My license was accepted on 7/21/2011. Following email was received as a confirmation. I’m not sure why the status has been changed to not licensed.
------------
Congratulations, asad.gill,
 
Your license has been formally accepted by our legal department. You can visit https://issues.asterisk.org/jira to check the status of your issues.
 
Thanks,
Digium, Inc.


> [patch] Advance Call Routing Capability
> ---------------------------------------
>
>                 Key: ASTERISK-18712
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18712
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Applications/app_queue, Core/ManagerInterface
>    Affects Versions: SVN
>            Reporter: Asad Gill
>            Assignee: Asad Gill
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list