[asterisk-users] Transfer feature dialing out after one digit

[Hose]

What you say...Hose (hose+asterisk at bluemaggottowel.com):

> Because some users have requested transfer beep confirmations I've
> switched our phones over to using the asterisk transfer feature instead
> of the built in transfer functions of the phones.  While testing it was
> working fine, but I changed something in features.conf and suddenly any
> time I hit transfer (*2), I can only enter one digit before asterisk
> immediately tries to dial that extension.  
> 
> Features.conf is extremely barebones so I'm not sure where any problems
> would come up:
> 
> [general]
> transferdigittimeout => 3 
> xfersound = beep
> 
> [featuremap]
> blindxfer => #
> atxfer => *2 
> 
> Tried change transferdigittimeout to something insanely long like 100,
> but still the same thing.  I even fully restarted asterisk (just in case
> it was some weird fluke that crept in).  
> 
> This is 1.6.2.17.2.  Someone else posted something extremely similar,
> though it's in version 1.8.2.3:
> 
> http://forums.digium.com/viewtopic.php?f=1&t=77154
> 
> hose

Looks like this might be an asterisk bug with the dial command,
specifically, the "T" option, allowing the calling user to execute
transfers.  The lowercase "t" option (allowing the *called* user to
execute transfers) works fine in all cases; the erroneous behavior of
having the calling user attempt a transfer but having it registered way
before the featureddigittimeout value expires happens whether the
lowercase t option is enabled or not.

Can anyone confirm or refute with their version?  You'd just have to add
the T option to a dial command, call / answer an extension, and then try and
execute a feature transfer from the calling extension.

hose