| Summary: | ASTERISK-21645: Bridge API Enhancements - add parking dialplan generation | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-04-18 16:23:14 | Date Closed: | 2013-06-07 11:11:03 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/Bridging Core/ManagerInterface Features/Parking |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Previously, all of the parking was done through special dialplan contexts and extensions. Those have now all disappeared.
However, there is a case to be made that the extension entry points are useful, and could still be autogenerated by parking. The dialplan would simply direct the parked calls into the parking lot created by the bridging framework (using the Park application). This would help maintain legacy dialplans that relied on this behavior. At the same time, we need dialplan for comebacktoorigin to function correctly as well. That should happen when that feature is enabled. | ||
| Comments: | |||