I think this is an excellent suggestion; I have often thought it more convenient to be able to mark certain users as DTMF transfer-type users. I also think it is, as you say, necessary to keep the tT functionality there still, for in some cases you might be doing something special.<div>
<br></div><div>Regards,</div><div>Örn<br><br><div class="gmail_quote">On Wed, Nov 25, 2009 at 7:54 PM, Benny Amorsen <span dir="ltr"><<a href="mailto:benny%2Busenet@amorsen.dk">benny+usenet@amorsen.dk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">One of the really ancient features of Asterisk is that you can do<br>
transfers with DTMF -- as long as t or T is set in Dial() or Queue() as<br>
appropriate. Quite nice, as far as it goes. However, this model doesn't<br>
really fit usage at IP Vision, and the impedance mismatch is getting worse.<br>
<br>
Our customers have 3 different kinds of needs:<br>
<br>
1) SIP phones, where DTMF-initiated transfers should not be allowed<br>
(those phones have perfectly good buttons, no need to fake it)<br>
<br>
2) Mobile phones and some DECT phones where DTMF-initiated transfers are<br>
necessary, because they can't do something smarter.<br>
<br>
3) Outgoing lines where t or T must never be set.<br>
<br>
Right now we're detecting whether the caller is type 1, 2 or 3 and<br>
setting T as appropriate, and then doing the same for the callee. This<br>
is quite a bit of code (involving fun with Local channels), and it still<br>
breaks in this case:<br>
<br>
If a Pickup is done using the *8 feature, the phone who did the pickup<br>
will be able to transfer the call using DTMF if the ringing phone<br>
happened to be a mobile phone (which is wrong if the phone doing the<br>
Pickup is a SIP phone), and the opposite problem happens if a mobile<br>
phone does a Pickup from a ringing SIP phone.<br>
<br>
This would be a lot easier if the tT options were replaced with an<br>
option linked to the SIP peer/user: allowdtmftransfer=yes/no. Better<br>
names for the option are more than welcome, of course. We could set<br>
allowdtmftransfer=no for peers connecting to the outside and as long as<br>
we made sure to never use tT option (could be checked statically), we'd<br>
know that no error in the dial plan could result in outside users being<br>
able to transfer calls.<br>
<br>
For backwards compatibility and for those with more complicated needs,<br>
the tT options could be kept around.<br>
<br>
<br>
/Benny<br>
<br>
<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>
</blockquote></div><br></div>