| Summary: | ASTERISK-21977: Stop potential message ordering issues between bridge and channel manager events | ||||
| Reporter: | Mark Michelson (mmichelson) | Labels: | Asterisk12 | ||
| Date Opened: | 2013-06-28 13:27:39 | Date Closed: | 2013-07-15 16:25:56 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Core/Bridging Core/Stasis | ||
| Versions: | 12 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| 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. | ||||
| Comments: | |||||