|Summary:||ASTERISK-03507: [Patch] Add settable context option for outbound Dial() calls|
|Reporter:||Ben Klang (bklang)||Labels:|
|Date Opened:||2005-02-14 00:11:13.000-0600||Date Closed:||2011-06-07 14:04:59|
|Environment:||Attachments:||( 0) outboundcontext-cvshead.patch|
|Description:||When using the transfer functionality I was thrown by the fact that my extensions were being applied to the channel default context rather than the context from which the Dial command was being issued. Since I also use macros heavily, the answer was to add an option to Dial to allow the outbound context to be set, mostly for the purposes of transferring called/calling users.|
The format is Dial(Tech/number|timeout|tc(context))
****** STEPS TO REPRODUCE ******
Attempting to use the transfer feature placed me in the channel default context (in my case 'router') rather than the context which was most useful for transfers ('internal')
****** ADDITIONAL INFORMATION ******
Patch applies cleanly to CVS HEAD. I also have a patch against stable 1.0.5. Patch has been tested to compile and work perfectly under stable and has been compile tested under HEAD.
|Comments:||By: Ben Klang (bklang) 2005-02-14 00:13:44.000-0600|
Disclaimer on file. /BAK/
By: Olle Johansson (oej) 2005-02-14 01:33:31.000-0600
Isn't this TRANSFER_CONTEXT - an existing variable?
By: Mark Spencer (markster) 2005-02-14 09:28:03.000-0600
bklang: Are you attempting to set the context for native transfers as well as '#' style transfers?
By: Ben Klang (bklang) 2005-02-14 23:57:14.000-0600
I was mostly concerned about '#' style transfers. I was previously unaware of the TRANSFER_CONTEXT variable. I'll withdraw this patch unless you see other value in it. Apologies for the momentary ignorance.
By: Mark Spencer (markster) 2005-02-15 00:20:58.000-0600
No worries, we appreciate your desire to contribute! I did double check that it's documented in README.variables.