Olivier Krief wrote:
For the sake of behaviour consistency, maybe :
- this unified transfer method (let's say U for unified) should be
introduced in features.conf independently of previous t or T methods and
it's up developpers to reuse, factorize or rewrite existing transfer
code and as long as those 3 methods as supported,
- and previous t or T methods should be droped sometimes later on to
simplify code support.
the t or T is used to determine whether someone can transfer a call, be
it blink or attended, not HOW that transfer occurs. So the 'tT'
discussion is completely separate from the how discussion.
Don Pobanz
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
