|Summary:||ASTERISK-08564: DTMF no longer recongnized on ParkedCalls|
|Reporter:||Bruce Reeves (nortex)||Labels:|
|Date Opened:||2007-01-12 09:47:05.000-0600||Date Closed:||2007-01-16 11:43:14.000-0600|
|Description:||After the issue ASTERISK-8174 was fixed, the process of transfering a call with the transfer features defined in features.conf is broken. While the issue 8406 is valid for users running SIP trunks it does not seem that there is anyway to keep Asterisk in the call. In our case what users were told to use # to transfer calls and at this point are unable to transfer or re-park a call using the # key. If there is a way in the dial plan to force Asterisk to stay in the call after parkedcalls then I need to know how.|
|Comments:||By: Matt King, M.A. Oxon. (kebl0155) 2007-01-15 07:31:51.000-0600|
Hmm I thought the fix to 8406 should only kick in when there are no enabled features on the parked call (i.e. when DTMF should have no affect anyway...).
By: Bruce Reeves (nortex) 2007-01-15 10:58:05.000-0600
I have been able to restore the functionality by putting the following back into res_features.c, per file's suggestion in IRC. I am not sure how you would disable features on the parked call if it is a feature from the pbx.
--- branches/1.2/res/res_features.c 2006/11/30 18:49:59 48153
+++ branches/1.2/res/res_features.c 2006/11/30 19:04:11 48154
@@ -1774,12 +1774,6 @@
ast_verbose(VERBOSE_PREFIX_3 "Channel %s connected to parked call %d\n", chan->name, park);
memset(&config, 0, sizeof(struct ast_bridge_config));
+ ast_set_flag(&(config.features_callee), AST_FEATURE_REDIRECT);
+ ast_set_flag(&(config.features_caller), AST_FEATURE_REDIRECT);
+ config.timelimit = 0;
+ config.play_warning = 0;
+ config.warning_freq = 0;
res = ast_bridge_call(chan, peer, &config);
/* Simulate the PBX hanging up */
By: Matt King, M.A. Oxon. (kebl0155) 2007-01-15 21:30:42.000-0600
The following features.conf completely disables all features:
; Sample Parking configuration
parkext => 700 ; What extension to dial to park
parkpos => 701-720 ; What extensions to park calls on. These needs to be
context => parkedcalls ; Which context parked calls are in
I will check to see whether native bridging of parked calls is still possible with this patch.
By: Joshua C. Colp (jcolp) 2007-01-16 11:43:13.000-0600
Fixed in 1.2 as of revision 51145, 1.4 as of revision 51148, and trunk as of revision 51149. I basically reverted what I did for the original issue - but am adding an option to trunk to allow the user to configure it.