[asterisk-bugs] [JIRA] (ASTERISK-20725) Asterisk API stabilization - Channel Handle/UUID
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Tue Nov 27 10:40:45 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-20725:
-----------------------------------
Component/s: (was: General)
Core/Stasis
Core/ManagerInterface
Core/Channels
> Asterisk API stabilization - Channel Handle/UUID
> ------------------------------------------------
>
> Key: ASTERISK-20725
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20725
> Project: Asterisk
> Issue Type: New Feature
> Components: Core/Channels, Core/ManagerInterface, Core/Stasis
> Affects Versions: 12
> Reporter: Matt Jordan
> Labels: Asterisk12
>
> A major feature request discussed at [AstriDevCon|https://wiki.asterisk.org/wiki/display/AST/AstriDevCon+2012#AstriDevCon2012-APIs] was improving the reliability and consistency of Asterisk's APIs. A core problem with meeting this goal is the exposure of Asterisk's internal implementation details/decisions through the interfaces, e.g., masquerading of channels, bridge breaking, etc. In order to make all interfaces more robust, some core changes to Asterisk have to occur.
> This issue represents the first of those changes: create a handle to a channel that survives all operations that Asterisk may perform on said channel and exists from the time a communication path is created between Asterisk and some endpoint and when that communication path is torn down. This handle must persist even if the underlying channel object is disposed of and replaced with a different channel object. Said handle should also be globally unique across space and time, i.e., a UUID.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list