[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-25 17:13 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0100764) murf (administrator) - 2009-02-25 17:13
 http://bugs.digium.com/view.php?id=14515#c100764 
---------------------------------------------------------------------- 
sodom-- OK, I have not been able to repeat the problem where *0 can
activate a feature when *0# is set. Just *0 times out.

And, my preliminary tests on the transferdigittimeout show that they seem
to be working as advertised for 2 and 3 key patterns. I set the timeout for
5 sec, and
counted to 4 before hitting the next key, and the transfer went OK.

Please give me more detail on how to reproduce your problems. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-25 17:13 murf           Note Added: 0100764                          
======================================================================