[asterisk-bugs] [Asterisk 0014515]: [patch]Timeout settings in features.conf don't work as intended

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14515 
====================================================================== 
Reported By:                sodom
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   14515
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-20 04:59 CST
Last Modified:              2009-02-26 10:33 CST
====================================================================== 
Summary:                    [patch]Timeout settings in features.conf don't work
as intended
Description: 
It seems that some of the feature.conf settings didn't work as intendet, at
least for the misdn channel.

a) I changed the code for disconnect from "*0" to "*0#" but asterisk still
disconnects with the code *0 (feature show, shows me that it is successfuly
changed to *0#)
b) I changed the timeout for featuresdigits from 500ms to 1000ms but as it
seem the timeout is not on a didgit base it's for the complete command. If
i did't finish the complete feature dial string in this time, the feature
isn't activated. (All fetures were changed to three digit numbers on our
side.)
c) I changed the timeout for transferdigit from 3 secs to 15sec as it has
the same issue as b) if i don't complete the number in the configured time,
the transfer is interrupted.
====================================================================== 

---------------------------------------------------------------------- 
 (0100798) murf (administrator) - 2009-02-26 10:33
 http://bugs.digium.com/view.php?id=14515#c100798 
---------------------------------------------------------------------- 
Hmmm, you are in the middle of an attended transfer, and are trying to use
feature sequences; that won't work. When you enter attended transfer, the
code will say "transfer", and then it calls the ast_app_dtget() routine,
which is fairly restricted in what it does. And, most certainly,
recognizing feature codes is not on the list. Most likely, it determined
that *0 is not a possible available extension, and terminated immediately.

Right now, the feature codes can only be recognized while a bridge is
active (two channels connected and trading audio). There is a bug open with
a patch that will allow the disconnect feature to be detected outside a
bridge, and it's targeted to be used in dial to allow disconnects while you
are dialing. Perhaps in at some future time this could also be done here,
but that patch has some pretty big problems, and will be going on
reviewboard, so it will be a few weeks before it makes into trunk (1.4 is
not even a possibility for that enhancement).


So, your (a) in the original bug problem description can't be done;
(b) I provide a patch for
(c) I can't reproduce-- any more details? I increased the
transferdigittimeout to 15 also, and got into attended transfer, and waited
about 13 seconds before hitting each of the next digits, and the transfer
finished just fine. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 10:33 murf           Note Added: 0100798                          
======================================================================