[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:                     closed
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-20 04:59 CST
Last Modified:              2009-02-26 11:57 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0100817) murf (administrator) - 2009-02-26 11:57
 http://bugs.digium.com/view.php?id=14515#c100817 
---------------------------------------------------------------------- 
Sodom-- 

As to aborting a transfer:

well, there's hanging up, which would tend to end the currently bridged
call; a call to the disconnect feature probably would be equivalent to
this!

or letting the number time out and ending the transfer, but then you'd be
still be bridged and could try again. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 11:57 murf           Note Added: 0100817                          
======================================================================