| Summary: | ASTERISK-15801: [patch] Background application not use 'context' parameter | ||
| Reporter: | Igor Goncharovsky (igorg) | Labels: | |
| Date Opened: | 2010-03-13 04:24:26.000-0600 | Date Closed: | 2011-06-07 14:04:42 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/PBX |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) pbx.background.patch | |
| Description: | Writing application I have discovered, that Background application exit to original extension even if `context` parameter used. It exit in context specified only in case if it have one-digit exension. That patch always set context from application argument. | ||
| Comments: | By: Leif Madsen (lmadsen) 2010-03-15 11:14:59 Thanks for the submission! A developer will look at this as soon as time and resources allow. By: Mark Michelson (mmichelson) 2010-05-25 17:15:58 The current code is functioning as intended. If you look at the documentation, you'll see the following: "If a 'context' is specified, this is the dialplan context that this application will use when exiting to a dialed extension." The key words there are "dialed extension." Your patch is changing the behavior of BackGround to exit to the specified context unconditionally. The intended purpose of the parameter is to exit to that context only if we detect DTMF while the file is playing and an extension exists in the given context that matches the DTMF we received. I am closing this since this is not a bug. | ||