Summary: | ASTERISK-09286: Unparked caller has ability to transfer | ||
Reporter: | jonh (jonh) | Labels: | |
Date Opened: | 2007-04-19 17:22:34 | Date Closed: | 2008-02-13 13:29:09.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_features |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | The fix for issue 8804 in SVN revision 51145 gives call transfer capabilities to both channels. If an outside caller calls in and I park them and then unpark them they can then park or transfer me and then do whatever they want at the resulting internal dialtone. ****** ADDITIONAL INFORMATION ****** My current fix is to comment out one of the two lines, this works ok for our usage but a better fix would be to check if their channel has transfer rights or not, but I don't know enough about the asterisk internals to know if that info is available here. My current patch: diff -u ../../asterisk-1.2.17/res/res_features.c res_features.c --- ../../asterisk-1.2.17/res/res_features.c 2007-01-16 11:36:50.000000000 -0600 +++ res_features.c 2007-04-19 17:02:27.000000000 -0500 @@ -1774,7 +1775,7 @@ 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_callee), AST_FEATURE_REDIRECT); only unparker should have tranfer capability */ ast_set_flag(&(config.features_caller), AST_FEATURE_REDIRECT); res = ast_bridge_call(chan, peer, &config); | ||
Comments: | By: Jason Parker (jparker) 2007-07-31 11:17:19 Can this issue be reproduced on 1.4? Once 1.2 goes into maintenance mode (scheduled for tomorrow - August 1st), all issues that only affect 1.2 will be closed. By: jonh (jonh) 2007-07-31 18:06:53 Yes, I was able to replicate the issue today using asterisk 1.4.9 By: Terry Wilson (twilson) 2008-01-31 12:44:28.000-0600 Can I get some feedback to see if this is fixed for you in the latest releases? I applied a patch from sergee that fixed a similar issue, but there wasn't enough information in the bug report for me to tell whether or not it fixed for this as well. Thanks. By: Terry Wilson (twilson) 2008-02-13 13:29:07.000-0600 Duplicate 11898. Closing and will put future updates at that bug. |