[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-06-2007 09:26 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).
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 10-06-07 09:26  
---------------------------------------------------------------------- 
My thought was on applying the fix to trunk was that it was an additional
feature, and indeed, CURL with multiple lines was the reason why.

Note that if the output really is line-terminated with "\r\n", CUT will
not perform that way, even in trunk, as it accepts a single character
delimiter only. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-06-07 09:26  Corydon76      Note Added: 0071584                          
======================================================================