Problem is those variables must be set on the channel that has to be transfered and not the channel that performs the transfer. I thought it would be more logical to use the transferer context by default (just like in attended xfers), and for those variables to be set on the transferer's side. François. On Fri, 2010-11-19 at 08:32 -0600, Brian West wrote:
force_transfer_dialplan force_transfer_context
You can't tell if a transfer is blind or attended.
/b
On Nov 19, 2010, at 5:04 AM, François Delawarde wrote:
Hello,
I pastebined a very simple configuration for you to reproduce: http://pastebin.freeswitch.org/14552
We have user 100 in context "public", 101 and 102 in context "local".
Scenario: 1. 100 calls destination "123" 2. 101 answers, and transfers to 102
In step 2., if 101 does an attended transfer, it will of course use its own context (local) and the transfer will work. Now if 101 does a blind transfer instead, it will use the context of the other leg (100 => public) and it will not work.
I think it should behave the same way for both types of transfer by default. A workaround is to set force_transfer_context (uncomment the line on the "public" dialplan) in the channel to be transfered, which can be a pain with more complex configurations.
Thanks, François.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org