Summary: | ASTERISK-23667: features.conf.sample is unclear as to which options can or cannot be set in the general section | ||
Reporter: | David Brillert (aragon) | Labels: | |
Date Opened: | 2014-04-24 08:49:16 | Date Closed: | 2014-06-23 09:37:10 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Documentation Features/Parking |
Versions: | 11.9.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Attachments: | ( 0) features.conf.txt ( 1) secondparkfailure.txt | |
Description: | [Edit by Rusty - Looks like the documentation is insufficient. The option being used here can't be set in the general section and the sample is not explicit]
During testing I answered an incoming call and issued Asterisk park code to park the call. Picked up at another extension and tried to park the call again and the feature code was ignored by Asterisk so I could not park the call again. Full debug including DTMF and debug verbose attached Marked as regression since I know at one time this wasn't a problem. | ||
Comments: | By: David Brillert (aragon) 2014-04-24 08:50:11.826-0500 debug log attachment By: Matt Jordan (mjordan) 2014-04-25 10:47:18.114-0500 Please attach your {{features.conf}}. Whether or not DTMF features are enabled after picking up a parked call is a function of that configuration. By: David Brillert (aragon) 2014-04-25 11:38:51.041-0500 attached By: Rusty Newton (rnewton) 2014-04-30 17:50:05.324-0500 Hi, so looking at your configuration, the {{parkedcallreparking}} option is set in the [general] section. The documentation in the sample says {noformat} ;parkedcallreparking = caller ; Enables or disables DTMF based parking when picking up a parked call. ; one of: callee, caller, both, no (default is no) ; Set per parking lot. {noformat} The "Set per parking lot" seems to say that you can *only* set it per parking lot and not in the [general] section (or default parking lot). I tested out the option, setting it both the [general] section as you have done, and also trying it in a custom parking lot. It in fact, only works in the custom parking lot. So, it doesn't look like there is a bug here, but the documentation is surely confusing as I see several options under [general] that say "Set per parking lot" {noformat} ; and increments with one for the next parked call. ; Set per parking lot. context => parkedcalls ; Which context parked calls are in (default parking lot) ; Set per parking lot. ;parkinghints = no ; Add hints priorities automatically for parking slots (default is no). ; Set per parking lot. ;parkingtime => 45 ; Number of seconds a call can be parked before returning. ; Set per parking lot. (default is 45 seconds) ;comebacktoorigin = yes ; Setting this option configures the behavior of call parking when the ; parked call times out (See the parkingtime option). The default value is 'yes'. ; Set per parking lot. {noformat} Overall, it is at least not clear which options can be set in general and which cannot. We need to fix that documentation. By: Richard Mudgett (rmudgett) 2014-04-30 18:09:57.220-0500 @Rusty: It should be effective for the default parking lot since the default lot is defined in the general section. By: David Brillert (aragon) 2014-05-01 09:29:08.970-0500 I ran a quick test and if add parkedcallreparking = both to [parkinglot_debcomainbtn] then I am able to re-park calls. This could be a bug in Asterisk that doesn't inherit general settings... or the documentation could be just wrong. I am left confused by which settings must be included to each section. For now I am including all general settings to each section, and this seems to do the job (I am no longer able to reproduce). By: Rusty Newton (rnewton) 2014-05-01 09:49:57.460-0500 Yeah.. following the point Richard made, this may be considered a bug along with the documentation issue. By: Richard Mudgett (rmudgett) 2014-05-01 10:36:16.471-0500 I put the "Set per parking lot." lines on the options in the documentation because those options can be set differently for each parking lot defined. Although, it doesn't say if setting it in the general section will affect just the default parking lot or also the default value in custom parking lots. By: Rusty Newton (rnewton) 2014-06-13 15:48:22.382-0500 https://reviewboard.asterisk.org/r/3622/ https://reviewboard.asterisk.org/r/3621/ By: Rusty Newton (rnewton) 2014-06-23 09:39:19.994-0500 Documentation fixed in branches 1.8 and 11. |