[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 03:14 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0100778) sodom (reporter) - 2009-02-26 03:14
 http://bugs.digium.com/view.php?id=14515#c100778 
---------------------------------------------------------------------- 
Hi,

i attach a session log with my unpatched system to show you the *0,
disconnect problem. 

In the session i simply dial from one misdn phone to another put it on
hold via *1# (atf) and then tried to disconnect my new unconnected channel
immeadiatly with *0# again but as always the unhold happens after *0 even
though my feature conf show *0# for disconnect. I tried to spread the cli
log via empty commands, so you can read it. The disconnect event is marked
by a "kkkkkkkkkkkkkkkkk" command :)

I hope i don't run into a simple pebcac (problem exists between computer
and chair) :)

If you need my configuration files..say so, because i need to anonomeise
them first. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 03:14 sodom          Note Added: 0100778                          
======================================================================