[asterisk-bugs] [Asterisk 0013772]: Default delimiter for ${CUT(var, , n)} is no longer handled

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13772 
====================================================================== 
Reported By:                jcovert
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13772
Category:                   Functions/func_cut
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-23 06:59 CDT
Last Modified:              2008-10-28 10:39 CDT
====================================================================== 
Summary:                    Default delimiter for ${CUT(var,,n)} is no longer
handled
Description: 
The default delimiter for CUT is supposed to be a "-" (as documented in
show function).

Any existing dialplan will malfunction until this is fixed.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0013470 Func CUT requires default of '-' to be ...
====================================================================== 

---------------------------------------------------------------------- 
 (0094332) Corydon76 (administrator) - 2008-10-28 10:39
 http://bugs.digium.com/view.php?id=13772#c94332 
---------------------------------------------------------------------- 
jcovert:  please update to SVN branch 1.6.0.  This was probably already
fixed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-28 10:39 Corydon76      Note Added: 0094332                          
======================================================================