| Summary: | ASTERISK-21713: Bridge API Enhancements - Create a media channel for the bridging API | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-04-26 14:55:29 | Date Closed: | 2013-05-10 11:42:00 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_local Core/Bridging |
| Versions: | 12 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Currently, media operations on a bridge are performed (in ConfBridge) using specially constructed channels that are only applicable to that module. This has the following drawbacks:
# They aren't as flexible as a Local channel # Their existence 'leaks' to the outside world, breaking the bridging/channel model that we'd like to have for 12 Ideally, we would have something that was as flexible as a Local channel, but that would 'look' different, such that consumers of Stasis-Core can choose to either reflect those channels or drop them in an easy fashion. This task is to: # Have common API entry points to the bridging framework that initiate media operations # Use a new channel driver (media channels) to perform those media operations on the bridge # Refactor common code between chan_local and chan_media (or whatever we call it) to the a new framework in Asterisk. This framework would be suitable for use by virtual channel drivers. | ||
| Comments: | |||