<br><br><div class="gmail_quote">2009/6/17 Benny Amorsen <span dir="ltr"><<a href="mailto:benny%2Busenet@amorsen.dk">benny+usenet@amorsen.dk</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">John Novack <<a href="mailto:jnovack@stromberg-carlson.org">jnovack@stromberg-carlson.org</a>> writes:<br>
<br>
> I have wondered for years now why someone thought there needed to be two<br>
> different transfer functions.<br>
> Transfer should be ONE function. If one wants to speak first to the<br>
> object of the transfer, then stay until they answer, otherwise hang up<br>
> and the transfer is completed.<br>
> Two independent transfers that have to start with different codes is<br>
> just awkward and dumb and long ago needed to be fixed.<br>
> I suppose it started life because someone had a weak knowledge of basic<br>
> telephony, but I really don't know.<br>
> Learn from history and improve on it.<br>
> When one reinvents the wheel, sometimes one ends up with an ellipse.<br>
<br>
</div>You can choose to do it that way. If you teach all your users to use<br>
transfer that way, and your phone has a transfer-on-hangup setting, then<br>
it will all work fine. However, there are quite a few interesting<br>
scenarios which won't work with such a simplistic setup.</blockquote><div><br>Trouble is that it's not that easy to tune hardphones GUI to support more than a single type of transfer.<br>For instance, with Aastra, it's note easy to replace incumbent Transfer with something else though phones support custom XML menus.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Imagine this:<br>
<br>
An employee wants to transfer a call to a different employee. She dials,<br>
and gets the busy signal because the other employee is already handling<br>
a call. The original caller says that he wants to wait until the<br>
employee is available, so she does a blind transfer to the employee.<br>
Asterisk detects this blind transfer and puts the caller into a Queue or<br>
RetryDial instead of just sending a busy signal.<br>
<br>
This is only possible because blind and attended transfer are different.</blockquote><div><br>Nice one : I've never thought of this one, yet ! <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
By the way, do any of you use RetryDial?</blockquote><div><br>I don't at the moment ... <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<font color="#888888"><br>
<br>
/Benny<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-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br>