This is a very common source of problems with windows and fs; with fs being cross platform with *nix based environments that use the forward slash exclusively for path separators. The issue involves backslash "\" encoded escape entries. (ex. \r being an encoded return character hex 0xd or \n an encoded newline hex 0xa) there are many more examples of this too. The best way to deal with this in a cross platform way is to use windows ability to use forward slashes "/" for path separators. All releases of windows can do this without difficulty(and least for 10 years or so). All internal path handing in FreeSWITCH has been changed(last few months) to manipulate paths with forward slashes to minimize this very problem. So if you supply external paths to fs make sure you always supply them with forward slashes to avoid this problem. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Error-on-Call-Recording-Window... Sent from the freeswitch-users mailing list archive at Nabble.com.