|Summary:||ASTERISK-09547: Document TRANSFER_CONTEXT in extensions.conf.sample|
|Date Opened:||2007-05-30 12:06:27||Date Closed:||2011-06-07 14:10:25|
|Environment:||Attachments:||( 0) transfer_context.patch|
|Description:||Just upgraded a 1.0.x box to 1.4.x and noticed that my zap call transfers weren't working, that they couldn't find a context to transfer in (was getting things like "-- Unable to find extension '7' in context ''"). I found on the forums that setting TRANSFER_CONTEXT in the globals section of extensions.conf would fix this.|
So I've attached a patch for extensions.conf.sample to add that one line in.
|Comments:||By: Joshua C. Colp (jcolp) 2007-06-04 13:42:59|
This is already talked about in UPGRADE.txt but I'm more concerned that no context was used. Are you able to reproduce this again easily?
* Builtin (res_features) transfer functionality attempts to use the context
defined in TRANSFER_CONTEXT variable of the transferer channel first. If
not set, it uses the transferee variable. If not set in any channel, it will
attempt to use the last non macro context. If not possible, it will default
to the current context.
By: Joshua C. Colp (jcolp) 2007-06-27 18:38:55
Since there has been no response I'm suspending this for now. Grab me on IRC if you can.