<div>Hi Alex,</div>
<div> </div>
<div>This type of transfer is called as "semi attended transfer".</div>
<div>Asterisk is already supporting this feature.</div>
<div>Just you need to make sure is the phone you are using is supporting this feature or not ?</div>
<div> </div>
<div> </div>
<div><br clear="all">Santosh Chintalwar<br>+91 9949695124<br><a href="http://www.google.com/profiles/103330523519763692172">http://www.google.com/profiles/103330523519763692172</a><br><br><br></div>
<div class="gmail_quote">On Tue, Mar 2, 2010 at 5:38 AM, Alex <span dir="ltr"><<a href="mailto:ab.wmhn@gmail.com">ab.wmhn@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">2010/3/1 Leif Madsen <<a href="mailto:leif.madsen@asteriskdocs.org">leif.madsen@asteriskdocs.org</a>>:<br>
<div class="im">> Alex wrote:<br>>> Hi all!<br>>><br>>> Ext A, B and C are SIP phones.<br>>><br>>> Ext A receives a call from Ext B. Ext A wants to transfer the call to<br>>> Ext C. Ext A puts the first call on hold, dials Ext C, then simply<br>
>> hangs up as soon as the call to Ext C starts *ringing*. In other<br>>> words, Ext A wants to be sure Ext C is ringing (i.e. it is not busy or<br>>> unavailable) but doesn't want to talk to him.<br>
>><br>>> Unfortunately, as soon as Ext A hears Ext C is ringing and hangs up or<br>>> hits "Transfer", the call is closed and a *new* call from Ext B to Ext<br>>> C starts. This way, Ext C sees an unanswered call from Ext A, which is<br>
>> an unexpected behaviour.<br>>><br>>> I played with directmedia and directrtpsetup, but no success so far.<br>>> Any ideas, please?<br>><br>> Which version of Asterisk are you using? This sounds like a recent issue that<br>
> may have already been resolved.<br><br></div>I am using 1.6 from trunk. I've checked out a couple of days ago.<br>
<div class="im"><br>> I'd try the latest checkout from the branch you're currently using to determine<br>> if the issue has already been resolved. There was a commit for transfers just<br>> today from what I've heard as well.<br>
<br></div>I'll give it a try, thanks for this information. However, IMHO the<br>issue you probably refers to (bug #16816 -<br><a href="https://issues.asterisk.org/view.php?id=16816" target="_blank">https://issues.asterisk.org/view.php?id=16816</a> ) does not affect my<br>
scenario: in the case I reported, the call is transferred while the<br>3rd extension is still ringing, not after it has been already<br>answered.<br><font color="#888888"><br>Alex<br></font>
<div>
<div></div>
<div class="h5"><br>--<br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com/" target="_blank">http://www.api-digital.com</a> --<br>
<br>asterisk-dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></div>
</div></blockquote></div><br>