| Summary: | ASTERISK-19535: Dial/queue should handle HOLD/UNHOLD control frame similar to connected line updates. | ||
| Reporter: | Richard Mudgett (rmudgett) | Labels: | |
| Date Opened: | 2012-03-14 11:25:01 | Date Closed: | |
| Priority: | Minor | Regression? | |
| Status: | Open/New | Components: | Applications/app_dial Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Since the HOLD/UNHOLD control frames indicate a state and the call could be forked, the hold state needs to be remembered in case the winner of the forked call left the call on hold. For dial the hold state needs to be saved if single && !caller_entertained. Queue should be handled similarly. | ||
| Comments: | By: David Woolley (davidw) 2012-03-15 05:41:35.781-0500 There is, or was, a variation on this theme with local channels being channel redirected whilst the call was on hold. We forced hold to be acted on locally, rather than passed down the chain, to work round this one, but I'm not sure if there was ever a better fix in a later version. By: Richard Mudgett (rmudgett) 2012-06-28 11:19:31.770-0500 Note: The code in question was added by -r4823 when hold support was initially added to Asterisk. | ||