[asterisk-bugs] [Asterisk 0010903]: CUT() won't let you cut on a carriage return

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10903 
====================================================================== 
Reported By:                blitzrage
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   10903
Category:                   Functions/func_cut
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-05-2007 17:47 CDT
Last Modified:              10-05-2007 23:32 CDT
====================================================================== 
Summary:                    CUT() won't let you cut on a carriage return
Description: 
I'm trying to read in a file into the dialplan, and then parse each line of
the file with the CUT() function, but unfortunately have been unable to
make it work.

I've tried:

Set(LINE=${CUT(ENVELOPE,\n,1)})
Set(LINE=${CUT(ENVELOPE,\\n,1)})
Set(LINE=${CUT(ENVELOPE,\\\n,1)})
Set(LINE=${CUT(ENVELOPE,\r\n,1)})
Set(LINE=${CUT(ENVELOPE,\\r\\n,1)})
Set(LINE=${CUT(ENVELOPE,\\\r\\\n,1)})

But it seems it just cut on the literal letter ('r' or 'n' in this case).
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 10-05-07 23:32  
---------------------------------------------------------------------- 
Interesting...have you attempted this in trunk? A cursory read of the code
suggests that it is taken care of in trunk. I know this won't fix things in
1.4, but it will at least give a good idea of how to backport the fix. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-05-07 23:32  putnopvut      Note Added: 0071576                          
======================================================================