| Summary: | ASTERISK-21352: Bridge API Enhancements - refactor ParkAndAnnounce application to use the new parking bridge | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-03-29 10:39:09 | Date Closed: | 2013-06-06 11:58:59 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_parkandannounce Core/Bridging |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Now that parking is using the new bridging API, there are a number of features and applications that need to be refactored to use it. One of these is ParkAndAnnounce.
ParkAndAnnounce should still contain the logic for performing the dial operation to the destination channel receiving the announcement; however, the actual act of parking the channel that the application executes on needs to use the bridging API. Note that this is going to be a bit odd - the application needs to call the bridging API and park the channel but not be blocked by the joining of the channel to the bridge. It then needs to perform the outbound dial operation based on the success of the actual park operation. Ideally, all of this would take place without a masquerade operation (which is how the ParkAndAnnounce application currently hands off control of the channel). | ||
| Comments: | |||