[asterisk-bugs] [JIRA] (ASTERISK-17201) [patch] Create a manager event when the app_dial creates a new call with a new unique id
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Wed Jul 31 12:47:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-17201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan closed ASTERISK-17201.
----------------------------------
Resolution: Fixed
Target Release Version/s: 12
Note that this is closed out as Fixed as the problem that this patch provided information for no longer occurs.
> [patch] Create a manager event when the app_dial creates a new call with a new unique id
> ----------------------------------------------------------------------------------------
>
> Key: ASTERISK-17201
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-17201
> Project: Asterisk
> Issue Type: New Feature
> Components: Applications/app_dial
> Reporter: oelewapperke
> Target Release: 12
>
> Attachments: newuniqueidontransfer2.patch, newuniqueidontransfer.patch
>
>
> The event contains both the old and the new unique id, allowing manager applications to track what's happening.
> The problem is that all manager events after a blind call transfer carry a new unique id, and there isn't any manager event that contains both the old and new unique ids, thereby making following the call impossible for any manager applications.
> This patch intends to remedy this situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list