[asterisk-bugs] [Asterisk 0017125]: [patch] Make transfer calls more pattern friendly

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17125 
====================================================================== 
Reported By:                dmartin
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17125
Category:                   Applications/General
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 255751 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-04-01 14:15 CDT
Last Modified:              2010-04-05 15:02 CDT
====================================================================== 
Summary:                    [patch] Make transfer calls more pattern friendly
Description: 
Let these two patterns in a context:

_2XX => {
// do something
};

_X. => {
//do something else
};

If in a call between users in this context, we want to transfer the call
to a number like, eg, 210, then it match _X. pattern instead of _2XX. and
effectively tries to call extension '2'.

Tracing the code I found this may be because ast_app_dtget() looks for a
match on the dialplan in every key stroke.

This patch avoid this and only tries to transfer the call when a timeout
is reached (transferdigittimeout) or when the transferer party dials #.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-05 15:02 pabelanger     Status                   new => closed       
2010-04-05 15:02 pabelanger     Resolution               open => no change
required
======================================================================