<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">force_transfer_dialplan<div>force_transfer_context</div><div><br></div><div>You can't tell if a transfer is blind or attended.</div><div><br></div><div>/b</div><div><br><div><div>On Nov 19, 2010, at 5:04 AM, François Delawarde wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello,<br><br>I pastebined a very simple configuration for you to reproduce:<br><a href="http://pastebin.freeswitch.org/14552">http://pastebin.freeswitch.org/14552</a><br><br>We have user 100 in context "public", 101 and 102 in context "local".<br><br>Scenario:<br>1. 100 calls destination "123"<br>2. 101 answers, and transfers to 102<br><br>In step 2., if 101 does an attended transfer, it will of course use its<br>own context (local) and the transfer will work. Now if 101 does a blind<br>transfer instead, it will use the context of the other leg (100 =><br>public) and it will not work.<br><br>I think it should behave the same way for both types of transfer by<br>default. A workaround is to set force_transfer_context (uncomment the<br>line on the "public" dialplan) in the channel to be transfered, which<br>can be a pain with more complex configurations.<br><br>Thanks,<br>François.</blockquote></div><br></div></body></html>