| Summary: | ASTERISK-22034: Investigate whether or not a Local channel is appropriate during a one-touch parking feature | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-07-07 20:11:10 | Date Closed: | 2013-08-15 15:17:06 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_parking |
| Versions: | 12 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | During a one-touch parking feature transfer, a Local channel is used to move the transfer target into Parking. This may or may not be appropriate, depending on how that Local channel is being used.
If possible, it would be better if a Local channel was not involved. If an Unreal channel needs to be used in order to create a temporary channel between the transfer target's bridge and the holding bridge, that may be more appropriate to minimize the messages sent to AMI clients. Note that this addresses the BUGBUG in {{res/parking/parking_bridge_features.c}}: {noformat} /* BUGBUG Use Richard's unreal channel stuff here instead of this hack */ parkee_name = ast_strdupa(ast_channel_name(parkee)); {noformat} | ||
| Comments: | By: Matt Jordan (mjordan) 2013-08-02 11:53:25.282-0500 I'm kind of ambivalent about this. This feels very similar to using a Local channel to perform a blind transfer of a multi-party bridge. Since the party can be kicked out of the parking lot as well, we'll need a Local channel in order to execute the dialplan. I'm inclined to think we are currently doing it correctly, and this BUGBUG can be removed. | ||