[asterisk-bugs] [JIRA] (ASTERISK-21977) Stop potential message ordering issues between bridge and channel manager events
Mark Michelson (JIRA)
noreply at issues.asterisk.org
Fri Jun 28 13:29:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Michelson updated ASTERISK-21977:
--------------------------------------
Description:
In main/manager_bridging.c, during initialization, there is the following BUGBUG comment:
{noformat}
/* BUGBUG - This should really route off of the manager_router, but
* can't b/c manager_channels is already routing the
* stasis_cache_update_type() messages. Having a separate router can
* cause some message ordering issues with bridge and channel messages.
*/
{noformat}
Something needs to be done to either not require the creation of a separate bridge state router or to have some other mechanism in place to ensure proper ordering of messages.
was:
In main/manager_bridging.c, during initialization, there is the following BUGBUG comment:
{no-format}
/* BUGBUG - This should really route off of the manager_router, but
* can't b/c manager_channels is already routing the
* stasis_cache_update_type() messages. Having a separate router can
* cause some message ordering issues with bridge and channel messages.
*/
{no-format}
Something needs to be done to either not require the creation of a separate bridge state router or to have some other mechanism in place to ensure proper ordering of messages.
> Stop potential message ordering issues between bridge and channel manager events
> --------------------------------------------------------------------------------
>
> Key: ASTERISK-21977
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21977
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Bridging, Core/Stasis
> Affects Versions: 12
> Reporter: Mark Michelson
>
> In main/manager_bridging.c, during initialization, there is the following BUGBUG comment:
> {noformat}
> /* BUGBUG - This should really route off of the manager_router, but
> * can't b/c manager_channels is already routing the
> * stasis_cache_update_type() messages. Having a separate router can
> * cause some message ordering issues with bridge and channel messages.
> */
> {noformat}
> Something needs to be done to either not require the creation of a separate bridge state router or to have some other mechanism in place to ensure proper ordering of messages.
--
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