Ugh. Thanks, John.
I took another look at your example, and saw that you had a ,u at the end.
So, even though that supposedly only specifies the line format, it
also seems to act as "create if not exist".
Problem solved - thanks! I'll add that to my ever lengthening list of
Asterisk
Could it be SELinux blocking you?
If you change the path to /tmp does it work?
On Fri, Nov 4, 2016 at 3:14 PM, Jonathan H wrote:
> That's just what I'm using, John.
>
> But I'm getting (eg)
>
> [Nov 4 21:46:16] ERROR[1676][C-0003]: func_env.c:449 file2format:
>
That's just what I'm using, John.
But I'm getting (eg)
[Nov 4 21:46:16] ERROR[1676][C-0003]: func_env.c:449 file2format:
Cannot open '/home/logs/anonymous.txt': No such file or directory
[Nov 4 21:46:16] ERROR[1676][C-0003]: func_env.c:949 file_write:
File '/home/logs/anonymous.txt'
I'm able to use the FILE function to create files just fine.
Set(FILE(${CALLFILE},,,al,u)=Extension: s)
On Fri, Nov 4, 2016 at 2:26 PM, Jonathan H wrote:
> Seems I can write to an existing file, but is there really no way of
> creating a new file to log some data to,
Yes, that would also work (thanks!).
It just seems a bit hacky - STAT...GotoIf... System..,Return...FILE
Has there been any previous discussion as to why FILE can't/won't
create a file and write to it in one shot?
If so, what was the outcome? Should I suggest it?
Thanks!
On 4 November
Won't the system command do it?
On Fri, 04 Nov 2016 17:26:13 -0400,
Jonathan H wrote:
>
> Seems I can write to an existing file, but is there really no way of
> creating a new file to log some data to, without reverting to AGI?
> (will be different for each caller ID)
>
> --
>